Loss of control Accident McDonnell Douglas DC-9-82 (MD-82) HK-4374X, Tuesday 16 August 2005
ASN logo
 

Date:Tuesday 16 August 2005
Time:03:00
Type:Silhouette image of generic MD82 model; specific model in this crash may look slightly different    
McDonnell Douglas DC-9-82 (MD-82)
Owner/operator:West Caribbean Airways
Registration: HK-4374X
MSN: 49484/1315
Year of manufacture:1986
Total airframe hrs:49494 hours
Cycles:24312 flights
Engine model:Pratt & Whitney JT8D-217A
Fatalities:Fatalities: 160 / Occupants: 160
Other fatalities:0
Aircraft damage: Destroyed, written off
Category:Accident
Location:near Machiques -   Venezuela
Phase: En route
Nature:Passenger - Non-Scheduled/charter/Air Taxi
Departure airport:Panama City-Tocumen International Airport (PTY/MPTO)
Destination airport:Fort de France-Lamentin Airport (FDF/TFFF)
Investigating agency: JIAAC Venezuela
Confidence Rating: Accident investigation report completed and information captured
Narrative:
The MD-82 arrived at Panama City-Tocumen after a flight from Medellín-José María Córdova Airport (MDE). The plane was then prepared to carry out a flight to the Caribbean island of Martinique.
Flight WCW 708 departed Panama City at about 06:00 UTC and climbed to its cruising altitude of FL310.
This altitude was reached at about 06:25 UTC. Sixteen minutes later the airplane began a normal climb to FL330. At 06:49 the speed began to steadily decrease from Mach 0.76. The horizontal stabilizer moved from about 2 units nose up to about 4 units nose up during this deceleration. At 06:51 UTC the crew reported at FL330 over the SIDOS waypoint, over the Colombian/Venezuelan border, and requested a direct course to the ONGAL waypoint. The controller instructed the crew to continue on the present heading and to await further clearance direct to ONGAL. The flight crew meanwhile discussed weather concerns that included possible icing conditions and the possible need to turn on engine and airfoil anti-ice.
At 06:57 UTC the flight crew requested permission to descend to FL310, which was approved. The autopilot was disconnected and the airplane started to descend. As the airplane descended past about FL315, the airspeed continued to decrease and the engine EPR decreased to about flight idle. Two minutes later a further descent to FL290 was requested, but the controller at Maiquetía did not understand that this was a request from flight 708 and asked who was calling. Flight 708 responded and immediately requested descent to FL240. The controller inquired about the state of the aircraft, to which they responded that both engines had flamed out. The controller then cleared the flight to descent at pilot's discretion.
In the meantime, the altitude alert warning had activated, followed by the stick shaker and the aural stall warning alert. The airspeed had reached a minimum of about 150 indicated air speed (IAS) knots at about FL250. The crew reported descending through FL140 and reported that they were not able to control the airplane. The aircraft descended at 7000 ft/min, and finally crashed in a swampy area.
The entire descent from FL330 had taken approx. 3 minutes and 30 seconds.

CAUSE (translated from Spanish):
Given the aerodynamic and performance conditions, the aircraft was taken to a critical state, which led to this loss of lift.
Consequently, the cockpit resource management (CRM) and decision-making during the development of emergency were misguided. This was caused by the following:
a) Awareness of environment (or situational awareness) insufficient or improper that allowed the cockpit crew, not being full and timely aware of what was happening regarding the performance and behavior of the aircraft.
b) Lack of effective communication between the cockpit crew that limited, within the decision making process, the possibility to timely choose appropriate alternatives and options and to set respective priorities in the actions taken at the time when it was established that there was a critical or emergency situation (stall condition at high altitude).

It is found that the cause of the accident is determined by the absence of appropriate action to correct the stall of the aircraft, and also in the emergency up to the impact with the ground, at an inappropriate hierarchy of priorities in implementing the procedures.
Subsequently, the operations were conducted outside of the limits and parameters set by the manufacturer's manual performance, together with an inadequate flight planning by failing to consider meteorological aspects, in addition a misinterpretation and late of the energy state of the aircraft by the flight crew. Therefore, the evidence shows the classification of "Human Factor" as a cause of this accident.

Accident investigation:
cover
  
Investigating agency: JIAAC Venezuela
Report number: JIAAC-9-058-2005
Status: Investigation completed
Duration: 4 years and 12 months
Download report: Final report

Sources:

SKYbrary 
El Colombiano
El Tiempo
NTSB
rescate
Globovision, Notisar ORH, El Nacional

Statistics

  • worst accident in 2005
  • worst accident of this aircraft type
  • worst accident of this aircraft type at the time

Location

Images:


photo (c) Werner Fischdick; San José-Juan Santamaria International Airport (SJO); 01 April 2005


photo (c) Werner Fischdick; San José-Juan Santamaria International Airport (SJO); 01 April 2005


photo (c) Willem Alberto; Medellín-José María Córdova Airport (MDE); 07 July 2005


photo (c) Willem Alberto; Medellín-José María Córdova Airport (MDE); 07 July 2005


photo (c) Willem Alberto; Medellín-José María Córdova Airport (MDE); 07 July 2005

Revision history:

Date/timeContributorUpdates

The Aviation Safety Network is an exclusive service provided by:
Quick Links:

CONNECT WITH US: FSF on social media FSF Facebook FSF Twitter FSF Youtube FSF LinkedIn FSF Instagram

©2024 Flight Safety Foundation

1920 Ballenger Av, 4th Fl.
Alexandria, Virginia 22314
www.FlightSafety.org