TWA Flight 427
Trans World Airlines McDonnell Douglas DC-9-82 and Superior Aviation Cessna 441 · Runway incursion due to pilot error of the Cessna and ATC error
Event
- NTSB case
- CHI95MA044
- 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
- Accident
- 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
- Event fatalities
- 2 · all aircraft and ground
- Ground fatalities
- 0
- Occupants
- 142
- Survivors
- 140
- InjuriesFatal: death within 30 days. Serious: over 48 hours in hospital within a week, most broken bones, severe bleeding, nerve or organ damage, or serious burns. Minor: anything less. Glossary
- 8
- 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
Aircraft 1 · McDonnell Douglas DC-9-82
- Flight
- TW427
- Aircraft type
- McDonnell Douglas DC-9
- 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
- N954U
- Operator
- Trans World Airlines
- Onboard fatalities
- Unknown
- Occupants
- 140
- Survivors
- 140
- InjuriesFatal: death within 30 days. Serious: over 48 hours in hospital within a week, most broken bones, severe bleeding, nerve or organ damage, or serious burns. Minor: anything less. Glossary
- 8
- Route
- From St. Louis Lambert International Airport, Bridgeton, MissouriTo Denver International Airport (DEN), Denver, CO
- 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
- Takeoff · roll/run
- 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
- Collision between aircraft (not in flight)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Aircraft 2 · Cessna 441
- Aircraft type
- Cessna 441
- 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
- N441KM
- Operator
- Superior Aviation
- Onboard fatalities
- Unknown
- Occupants
- 2
- Survivors
- 0
- InjuriesFatal: death within 30 days. Serious: over 48 hours in hospital within a week, most broken bones, severe bleeding, nerve or organ damage, or serious burns. Minor: anything less. Glossary
- None · no survivors
- Route
- From St. Louis Lambert International Airport (STL)To Ford Airport (IMT), Iron Mountain, MI
- 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 91: General Aviation
- 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
- Standing · engine(s) operating
- 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
- Collision between aircraft (not in flight)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Pilot in command › Wrong runway, selected
- Pilot of other aircraft › Wrong runway, selected
Approximate · Coordinates from the Wikipedia article; not checked against an investigation report.
From the Wikipedia article
On November 22, 1994, TWA Flight 427, operated using a McDonnell Douglas MD-82, struck a Cessna 441 Conquest II during its take-off roll, killing both of its occupants. The collision took place at St. Louis Lambert International Airport (STL) in Bridgeton, Missouri.
Accident
Flight 427 was scheduled to depart STL at 21:34 Central Standard Time but pushed back from the gate about 15 minutes late. Apart from the delay, ground operations were routine. Flight 427 was given instructions to taxi to Runway 30R. At 22:01, the first officer advised local controllers that Flight 427 was ready for departure from Runway 30R.
The Cessna arrived in STL and, at about 21:40, taxied to the charter aviation terminal to drop off its passenger. At 21:58, the Cessna's pilot advised ground control that he was ready to taxi back to the runway for departure. The ground controller instructed the Cessna to "back-taxi into position" and hold on Runway 31, and then advise the controller when in position for departure. Although not a formally defined aviation term, "back-taxiing" generally referred to using a runway to taxi in a direction opposite the direction of departing or landing traffic in order to reach the takeoff position further down the runway. Although the ground controller specifically stated Runway 31, the Cessna pilot did not repeat the runway number when acknowledging his instructions. After being cleared to back-taxi on Runway 31, the Cessna pilot instead taxied onto Runway 30R, which Flight 427 was preparing to depart from.
At 22:01:23, Flight 427 was cleared for takeoff from Runway 30R, and the MD-82 taxied onto Runway 30R, with Speed at the controls. Flight 427 began accelerating down the runway at 22:02:27. Two seconds later, the Cessna's pilot advised the local controller that he was "ready to go on the right side." At 22:02:40, Carr called out reaching an airspeed of 80 knots; 2-3 seconds later, Richardson yelled, "There's an airplane!" Simultaneously, both Speed and Carr saw the Cessna and applied braking, and Carr applied hard left rudder in an attempt to direct their aircraft around the Cessna. About 2-3 seconds after they first saw the Cessna, the flight crew of Flight 427 felt the Cessna impact the right side of their plane. Flight 427's flight crew aborted their takeoff, and brought the plane to a stop on the left side of Runway 30R.
The right wing of the MD-82 tore the horizontal and vertical stabilizers off the fuselage of the Cessna, and sheared off the top of the Cessna's fuselage and cockpit; both occupants of the Cessna were killed. The MD-82's cockpit and cabin were not damaged, and no one on board the MD-82 was killed in the collision. Carr shut down the MD-82's engines and immediately called for emergency vehicles. Carr then asked the tower for help determining if there was a fire; the controller asserted he did not see flames, then asserted that the Cessna was not supposed to be on Runway 30R, telling Carr, "He was supposed to be on runway three one. I did not see the aircraft on that runway." Carr responded, "All that later, I just want to make sure everything's safe here."
Due to a large amount of spilled jet fuel, a fire hazard existed and an immediate evacuation was necessary. Eight passengers sustained minor injuries in the evacuation of the aircraft. The airport authority did not officially close the airport after the accident. Aircraft continued to land on runway 30L and taxi nearby during passenger evacuation.
Investigation and cause
Investigation
The resulting National Transportation Safety Board (NTSB) investigation determined that the Cessna had recently flown in from Iron Mountain, Michigan. It had landed on runway 30R and dropped off a passenger before preparing for the return flight. A commercial-rated pilot and a pilot-rated passenger, married to an employee of Superior Aviation, were on board as it left the ramp. The NTSB could not determine the reason the Cessna's pilot taxied onto the wrong runway, but considered multiple theories, including fatigue from the late hour and anxiety to beat deteriorating weather at the Cessna's destination. Ultimately, the NTSB concluded that the pilot likely had formed a preconceived notion that he would be using Runway 30R, which he had used on arrival, rather than Runway 31.
The Automatic terminal information service (ATIS) information broadcast to all pilots advised that runways 30L and 30R were in use for arrivals and departures. Although runway 31 was routinely used in these conditions for general-aviation aircraft, this information was not included on the hourly ATIS broadcast. The NTSB believed that if the ATIS broadcasts mentioned Runway 31 as an active runway, the Cessna pilot might have been more attentive to the mention of Runway 31 in the ground controller's taxi instructions. In addition, the NTSB criticized the ground controller's use of non-standard phrasing and failure to require the Cessna pilot to repeat back the runway he was cleared to.
According to a NTSB spokesman, Flight 427's pilots averted a major disaster by pulling the aircraft to the left before impact, a maneuver that "avoided what would have been a much worse accident."
Text from the Wikipedia article “TWA Flight 427” (revision 1339314095, retrieved 2026-09-18) by its authors, under CC BY-SA 4.0. Extracted as plain text: references, tables, images and some sections are left out. Read the article
NTSB narrative
During the takeoff roll on runway 30R, the MD-82, N954U, collided with the Cessna 441, N441KM, which was positioned on the runway waiting for takeoff clearance. The pilot of the Cessna acted on an apparently preconceived idea that he would use his arrival runway, runway 30R, for departure. After receiving taxi clearance to back-taxi into position and hold on runway 31, the pilot taxied into a position at an intersection on runway 30R, which was the assigned departure runway for the MD-82. The ATIS current at the time the Cessna pilot was operating in the Lambert-St. Louis area listed runways 30R and 30L as the active runways for arrivals and departures; there was no mention of the occasional use of runway 31. Air traffic control personnel were not able to maintain visual contact with the Cessna after it taxied from the well-lighted ramp area into the runway/taxiway environment of the northeast portion of the airport. An operational ASDE-3, particularly ASDE-3 enhanced with AMASS, could be used to supplement visual scan of the northeast portion of the airport.
Probable cause
The Cessna 441 pilot's mistaken belief that his assigned departure runway was runway 30R, which resulted in his undetected entrance onto runway 30R, which was being used by the MD-82 for its departure. Contributing to the accident was the lack of Automatic Terminal Information Service and other air traffic control (ATC) information regarding the occasional use of runway 31 for departure. The installation and utilization of Airport Surface Detection Equipment (ASDE-3), and particularly ASDE-3 enhanced with the Airport Movement Area Safety System (AMASS), could have prevented this accident. (NTSB Report AAR-95/05)
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
Wikipedia article: TWA Flight 427
- Article
- TWA Flight 427
- Revision
- 1339314095 · 2026-02-19 · retrieved 2026-09-18
- Wikidata
- Q7672515
- Licence
- Text CC BY-SA 4.0, by the article's authors; Wikidata CC0; town positions GeoNames (CC BY 4.0)
NTSB record CHI95MA044
- Event ID
- 20001206X02586
- Case number
- CHI95MA044
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Where each value comes from
- Record
- Wikipedia article "TWA Flight 427" (page 17843868, revision 1339314095); merged with NTSB case CHI95MA044 (events / aircraft)
- Date
- NTSB record CHI95MA044: NTSB API eventDate, eventTimeUtc and eventTimeUtcOffsetHours (local date)
- Place and country
- Wikipedia infobox: site; country from NTSB record CHI95MA044
- Map position
- Wikipedia: Wikipedia article coordinates
- Aircraft, operator and route
- NTSB record CHI95MA044: aircraft; gaps from Wikipedia infobox: aircraft type, registration, operator, origin and destination; route airports from the linked airport articles' Wikidata codes (OurAirports)
- Operation
- NTSB record CHI95MA044: operated under Part 121: Air Carrier, Part 91: General Aviation
- Fatalities
- NTSB record CHI95MA044: NTSB API totalFatal
- Ground fatalities
- NTSB record CHI95MA044: NTSB API ongroundFatal
- Summary
- Wikipedia infobox: summary
Source notes (3)
- One occurrence in two sources, merged: the Wikipedia article "TWA Flight 427" and NTSB case CHI95MA044, matched by the same aircraft registration and date. For this US event the NTSB's values are used where the two differ; each value names its source.
- Filled from the NTSB case API where the bulk record had no value: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1994-11-23.