FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Midwest Airlines Flight 490

12 May 2005 · Union Star, MO, United States

Boeing 717-200 · Incident: in flight encounter with weather en route

From Kansas City International Airport (MCI) to Ronald Reagan Washington National Airport (DCA)

Report a problem

Event

NTSB case
NYC05MA083
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
Instrument Meteorological Cond

Boeing 717-200

Aircraft type
Boeing 717
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
N910ME
Onboard fatalities
Unknown
Route
From Kansas City International Airport (MCI), Kansas City, MOTo Ronald Reagan Washington National Airport (DCA), Washington, DC
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 · climb to 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
In flight encounter with weather
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

  • Flight/nav instruments, airspeed indicator › Ice

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

After departure, the incident airplane was climbing toward its cruising altitude in a stratified region of precipitation within a convective system, and in conditions which were favorable for the accumulation of structural icing. At some point, the pitot/static system began accumulating ice because the air data heat system had not been activated or was not functioning. The condition first manifested itself as a "RUDDER LIMIT FAULT" warning due to icing of the rudder limiting system pitot tube. The icing continued to accumulate on the other probes of the air data system, degrading its ability to reliably determine the airplane's airspeed. About 19,000 feet, the flight crew disengaged the autopilot and pushed the pitch control column forward, and the airplane entered a descent. The flight crew initially applied uncoordinated control inputs, in the process reaching nearly 100 pounds of differential force on the pitch control column, while attempting to recover the airplane. During this period, airplane's pitch continued to oscillate through 5 cycles, for duration of 8 minutes, reaching altitudes as low as 10,600 feet and as high as 23,300 feet. During the oscillations the airplane's indicated airspeed varied greatly, between 54 and 460 knots; however, the airplane systems tests and aircraft performance data show that the recorded, as well as the displayed, airspeed indications were adversely affected by the icing conditions. Once regaining control of the airplane, the crew diverted and made an uneventful landing. Post-incident testing of the airplane's mechanical and electronic systems revealed no abnormalities that would have accounted for the unreliable airspeed indications or the loss of control reported by the flight crew. Post-incident computer modeling also confirmed that the airplane performed in a manner consistent with all deviations from normal flight having been initiated or exacerbated by the control inputs of the flight crew. Review of flight data recorder, cockpit voice recorder, and flight crew interviews revealed that the flight crew's actions during the event were in part contradictory with operator's training and operational procedures. Specifically, the crew initially failed to properly identify and respond to the erroneous airspeed indications that were presented and failed to coordinate their recovery of the airplane to controlled flight.

Probable cause

A loss of reliable airspeed indication due to an accumulation of ice on the air data/pitot sensors. Contributing to the incident was the flight crew's improper response to the erroneous airspeed indications, their lack of coordination during the initial recovery of the airplane to controlled flight, and icing conditions.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record NYC05MA083
Event ID
20050523X00653
Case number
NYC05MA083
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: local date, investigation status, damage. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2005-05-13.
  • API snapshot SHA-256: 7b03149d80db47aa030708cb34c7cffe9965428c9f923a4bb86161b615001fed; retrieved 2026-09-18T15:02:42.288Z.