FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Flight 977 · Boeing 737-823

13 Sept 2002 · Miami, FL, United States

Boeing 737-823 · Incident: collision between aircraft (not in flight) while standing

From Miami International Airport (KMIA) to MPTY · Panama City

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's aircraft involved. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
MIA02IA167
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
Visual Meteorological Cond

Boeing 737-823 Narrative disagrees

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
N939AN
Operator
Unknown
Onboard fatalities
Unknown
Route
From Miami International Airport (KMIA), MiamiTo MPTY · Panama City
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
Standing
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
Minor

Cause areas

  • Driver of vehicle › Clearance, not maintained
  • Driver of vehicle › Communications, not possible

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

Prior to the incident date, the tow tug driver had not towed an airplane in 6 years. Additionally, prior to the incident tow he had not received recurrent tow training since being away from the ramp for the previous 6 years. On the date of the incident, he towed 4 airplanes before the incident tow. Additionally, he had never received training in, nor towed the incident make and model airplane prior to the incident tow. American Airline’s procedures did not require tow training for a Boeing 777 airplane if the tow was conducted for maintenance, and the person had wide body tow training. The tow training curriculum for a Boeing 777 was not in place at the time of the incident. Additionally, the tow tug driver reported that he was not familiar with markings on the ramp which specified wide body airplanes were required to use spot 6C, not 6S, or 6N, which was covered by a NOTAM issued in August 2001. The purpose of the tow was to reposition the Boeing 777 airplane from a gate to a maintenance hangar; the tow tug driver did not brief the tow crew about the tow. Just before the tow began, the American Airlines Tower Coordinator (Tower Coordinator) advised the brake rider that the airplane was cleared to push 6 center out. The brake rider reportedly relayed the same instructions to the tow tug driver but he (tow tug driver) reported he was not advised what route to follow. The tow began with wing walkers, then as forward motion began, they left the tow. The airplane began following the line 6S and at that time, communication between the Tower Coordinator and brake rider began; the Tower Coordinator advising the brake rider that the airplane was being towed on line 6S instead of 6C. The brake rider advised the Tower Coordinator he knew, and had attempted to communicate with the tow tug driver and also flashed the airplanes landing and taxi lights numerous times in an attempt to get the tow tug drivers attention. The tow continued on line 6S, and the tow tug driver elected to stop the airplane short of spot 6, as he had not heard from the brake rider. He got out of the tug and noted the headset cord was lying on the ground, the male end was still connected to the airplane. He was then advised of damage to the tow airplane and damage to the rudder of an Boeing 737 airplane parked at gate E34 with passengers on-board awaiting pushback. The captain of the Boeing 737 parked at the gate reported that he and the first officer were going through the checklist and with the parking brake engaged, they felt a movement. He then had the jet bridge brought back in position, exited the airplane for inspection, and noted the damage to the rudder. He also noted the Boeing 777 was 150 feet west of his airplane on the "south tow line.' The passengers were then deplaned from his airplane.

Probable cause

The failure of the tug driver to maintain wingtip clearance with a parked airplane, and the inability of the tug driver to communicate with the brake rider during a tow operation following failure of the headset cord. Contributing factors in the incident were the inadequate aircraft/equipment by the airplane manufacturer for failure to provide a strain relief point for the headset cord and failure of American Airlines to disseminate information to the tug driver related to markings on the ramp.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA02IA167
Event ID
20020923X05202
Case number
MIA02IA167
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: investigation status, coordinates. 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: 6e60330029fd5e3e82ecf54fff5881d4051dbdfeb5fbe8215d34a99a4b10de98; retrieved 2026-09-18T15:58:09.362Z.