FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Flight 970 · McDonnell Douglas MD-82

4 Jun 2002 · Wichita, KS, United States

McDonnell Douglas MD-82 · Incident: loss of engine power en route

From Denver International Airport (DEN) to Fort Lauderdale Hollywood International Airport (FLL)

Report a problem

Event

NTSB case
CHI02IA151
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Incident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
Airline
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

McDonnell Douglas MD-82

Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N823NK
Operator
Unknown
Onboard fatalities
Unknown
Route
From Denver International Airport (DEN), Denver, COTo Fort Lauderdale Hollywood International Airport (FLL), Fort Lauderdale, FL
Aircraft age
Not recorded
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 121: Air Carrier
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
En route · cruise
First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Loss of engine power
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Stall
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
None

Cause areas

  • Flightcrew › Airspeed, not recognized
  • Flightcrew › Engine instrument, not verified
  • Flightcrew › Powerplant controls, not verified

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The airplane experienced a roll back of engine power on both engines and subsequently stalled while in cruise flight at flight level 330. The airplane was operating on autopilot with the autothrottles engaged. The flight crew was able to restart the engines and a precautionary landing was made without further incident. Examination of the airplane and its systems revealed no anomalies that could be attributed to the loss of power. The weather conditions were consistent with the presence of ice crystals at the cruise altitude. The engine inlet probes became blocked due to the ice crystals resulting in a false engine pressure ratio (EPR) indication and subsequent retarding of the throttles by the autothrottle system. This is evidenced by the data from the digital flight data recorder (DFDR) which showed that the EPR indication increased while the airspeed decreased, the pitch attitude increased, the altitude remained the same, and the autothrottles had reached the EPR limit. The DFDR data showed that the power reduction, the corresponding reduction in airspeed, and the increase in pitch occurred over the course of about 5 minutes prior to the roll back of the engines. Over this time period, the airspeed dropped from 271.75 to 209.25 knots, and the pitch increased from 0.9 to 4.91 degrees. The DFDR data also shows that during the 24 seconds after the roll back of the engines, the airspeed continued to drop to as low as 187 knots. The only engine performance parameter recorded by the DFDR is EPR. Interviews of the pilots show that their first indication of a problem occurred just before the airplane stalled. The pilots also said in their interviews that engine anti-ice was not used prior to the loss of engine power.

Probable cause

The flightcrew's failure to verify the engine instrument indications and powerplant controls while on autopilot with the autothrottles engaged, and their failure to recognize the drop in airspeed which led to an aerodynamic stall associated with the reduction in engine power. Factors were the presence of ice crystals at altitude, and the icing of the engine inlet probes resulting in a false engine pressure ratio indication.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI02IA151
Event ID
20020612X00866
Case number
CHI02IA151
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates, damage. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 588b2326d8f13e3c86804af60d32bb656c5af5701551c6a85fdf59c886e5a0ed; retrieved 2026-09-18T16:02:04.706Z.