Northwest Airlines McDonnell Douglas DC-9-51 accident
McDonnell Douglas DC-9-51 and Airbus Industrie A-319-114 · Accident: airframe, component or system failure en route
Event
- NTSB case
- CHI05MA111
- 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
- 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
Aircraft 1 · McDonnell Douglas DC-9-51
- 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
- N763NC
- Operator
- Northwest Airlines
- Onboard fatalities
- Unknown
- Route
- From John Glenn Columbus International Airport (CMH), Columbus, OHTo Minneapolis–Saint Paul International Airport / Wold–Chamberlain Field (MSP), Minneapolis, MN
- 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
- 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
- Substantial
Aircraft 2 · Airbus Industrie A-319-114
- Aircraft type
- Airbus A-319
- 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
- N368NB
- Operator
- Northwest Airlines
- Onboard fatalities
- Unknown
- Route
- From Minneapolis–Saint Paul International Airport / Wold–Chamberlain Field (MSP), Minneapolis, MNTo San Antonio International Airport (SAT), San Antonio, TX
- 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
- Pushback/towing
- 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
Cause areas
- Pilot in command › Engine shutdown, incorrect
- Pilot in command › Planning/decision, improper
- Pilot of other aircraft › Clearance, not maintained
- Pilot of other aircraft › Engine shutdown, incorrect
- Pilot of other aircraft › Planning/decision, improper
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The DC-9 was taxiing to the gate area when it collided with a company A-319 that was being pushed back from the gate. Prior to arriving at the destination airport, the DC-9 experienced a loss of hydraulic fluid from a fractured rudder shutoff valve located in the DC-9's right side hydraulic system. The left side hydraulic system had normal hydraulic pressure and quantity throughout the flight. The flightcrew elected to continue to the scheduled destination and declared an emergency while on approach to the destination airport. After landing, the emergency was negated by the flight crew and the airplane taxied to the gate. Flight data recorder information indicates the left engine, which provides power for the left hydraulic system, was shut down during taxi. The captain stated he did not remember shutting the left engine down, and that if he had, it would have been after clearing all runways. The first officer stated that he was unaware that the left engine was shut down. Upon arrival at the gate with the left engine shut down and no hydraulic pressure from the left system and a failure of the right hydraulic system, the airplane experienced a loss of steering and a loss of brakes. The flightcrew requested company maintenance to chock the airplane since they were unable to use brakes to stop the airplane. The crew said they were going to keep the "...engines running in case we have to use reversers..." The airplane began to roll forward and the captain applied reverse thrust but the reversers did not deploy. The airplane impacted the A-319 with a speed of approximately 15.65 miles per hour to 16.34 miles per hour. Evacuation of the DC-9 was completed approximately 5:22 minutes after the collision and evacuation of the A-319 occurred approximately 13:08 minutes after the collision. Examination of the left hydraulic system revealed no anomalies and examination of the right hydraulic system revealed a fractured rudder shutoff valve that displayed features consistent with fatigue. Following the accident, the airplane manufacturer issued a service letter pertaining to the replacement of the rudder shutoff valve based upon reliability information that was reported to them. The number of reports was greater than that of the Federal Aviation Administration's Service Difficulty Reports database, and less than the operators records.
Probable cause
the Captain's decision to shutdown the left engine during taxi with no hydraulic pressure on the right side hydraulic system to effectively operate the brakes, steering, or thrust reversers. A factor was the fatigue fracture of the rudder shutoff valve which resulted in the loss of right side hydraulic pressure.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI05MA111
- Event ID
- 20051213X01965
- Case number
- CHI05MA111
- 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, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2005-05-11.
- API snapshot SHA-256: 6d4c51a7657c25ca6e889b3dab935d3d8c71a5dd3819660fac4b35b3e17a55b6; retrieved 2026-09-18T15:02:50.417Z.
- The NTSB's operator name is blank for N763NC; the operator shown is the name the NTSB's other records give its FAA operator code, NWAA.