FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Midwest Airlines McDonnell Douglas DC-9-14 incident

21 Mar 1999 · Grand Rapids, MI, United States

McDonnell Douglas DC-9-14 · Incident: airframe, component or system failure en route

From Newark Liberty International Airport (EWR) to General Mitchell International Airport (MKE)

Report a problem

Event

NTSB case
CHI99IA115
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
0
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

McDonnell Douglas DC-9-14

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
N600ME
Onboard fatalities
Unknown
Route
From Newark Liberty International Airport (EWR), Newark, NJTo General Mitchell International Airport (MKE), Milwaukee, WI
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
Airframe, component or system failure
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

  • Flt control syst, elevator control › Frozen

Approximate · Estimated position: the centre of Grand Rapids, MI, the place the record names. Not the accident site.

NTSB narrative

On two separate flights, the flight crews determined that the elevator would not respond to control input. During the first occurrence, the flight crew continued to fly the airplane using pitch trim and descended to a lower altitude where elevator control returned. During the second occurrence, the flight crew applied elevator backpressure until the elevator '...bump[ed} free and control was restored.' After the first occurrence, maintenance personnel found ice accretions in the elevator control bay of the vertical stabilizer. They also found debris obstructing the drain holes in this area. Maintenance personnel were unable to find any anomalies after the second occurrence. On both occasions, the airplane departed in rain showers with surface temperatures of 46 degrees (F) and 39 degrees (F) respectively.

Probable cause

the frozen elevator control. Factors were the rain and the low temperatures.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI99IA115
Event ID
20001205X00277
Case number
CHI99IA115
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (5)
  • 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 1999-03-22.
  • API snapshot SHA-256: 8e67a3b0002141bef0b5bbfb2b1c4a5d1c3b1ff1346f51549f118af9105939cd; retrieved 2026-09-18T16:58:01.188Z.
  • The NTSB's operator name is blank for N600ME; the operator shown is the name the NTSB's other records give its FAA operator code, MWEA.