Northwest Airlines Flight 620
Boeing 757-351 and Delta Air Lines Boeing 737-832 · Accident: ground collision during pushback
Event
- NTSB case
- WPR09FA068
- 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 · Boeing 757-351
- Aircraft type
- Boeing 757
- 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
- N585NW
- Operator
- Northwest Airlines
- Onboard fatalities
- Unknown
- Route
- From Seattle–Tacoma International Airport (SEA), Seattle, WATo 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
- Pushback/towing · engine start-up
- Defining eventThe 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
- Ground collision
- 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 · Boeing 737-832
- Aircraft type
- Boeing 737
- 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
- N397DA
- Operator
- Delta Air Lines
- Onboard fatalities
- Unknown
- Route
- From Seattle–Tacoma International Airport (SEA), Seattle, WATo Cincinnati Northern Kentucky International Airport (CVG), Covington, KY
- 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
- Defining eventThe 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
- Ground collision
- 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
- Personnel issues › Psychological
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
A Boeing 757-351 and a Boeing 737-832 were substantially damaged when the tails of both airplanes collided during the pushback process from two opposing terminal gates during night visual meteorological conditions. The flight crew and ground crew of the Boeing 737-832 reported that they had stopped, were in a static position, and in the final stages of disconnecting the tug when the collision occurred. The ground crew of the Boeing 757-351 reported that they never observed the Boeing 737-832 during their pushback process. Review of recorded communications tapes between the flight crews of both aircraft and the ramp controller revealed that the Boeing 757-351 was cleared to be pushed into the alleyway with its tail to the south. About 9 seconds later, the Boeing 737-832 was cleared for pushback into the alleyway with its tail to the north. The recorded communications tapes revealed that the ramp controller did not advise either aircraft of the opposing pushback operations. The controller stated that she thought that the Boeing 737-832 was requesting to push back from a different gate than they had requested; however, the recorded communications tapes clearly have flight crew of the Boeing 737 stating their correct gate in their initial call for a pushback clearance.
Probable cause
The failure of the tug operator and wing walker of this airplane to maintain clearance with the other aircraft during the pushback process in dark night. Also causal was the ramp controller's misinterpretation of the other airplane's gate location and her improper clearance for both airplanes to simultaneously push back from nearly opposing gates.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR09FA068
- Event ID
- 20081228X25156
- Case number
- WPR09FA068
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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. 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: eecb29ef6e215b537d4fe8c9b1b6f5137114b42987b261f0dd2353001536a820; retrieved 2026-09-13T18:15:02.588Z.