USAir Boeing 737-300LR accident
Boeing 737-300LR · Accident: on ground/water collision with object during pushback
From LaGuardia Airport (KLGA) to Tampa International Airport (KTPA)
Event
- NTSB case
- NYC93LA040
- 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
- 1 · all aircraft and ground
- Ground fatalities
- 1
- 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-300LR
- 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
- N516AU
- Operator
- USAir
- Onboard fatalities
- Unknown
- Route
- From LaGuardia Airport (KLGA)To Tampa International Airport (KTPA), Tampa, FL
- 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
- On ground/water collision with object
- 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
- Ground personnel › Clearance, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE B737 WAS BEING PUSHED BACK USING A 2 MAN GROUND CREW. THE TUG DRIVER WAS SEATED ON THE LEFT SIDE OF THE TUG. THE WALKER WAS FORWARD OF THE TUG, ON THE LEFT SIDE OF THE AIRPLANE, USING A 15 FT HEADSET CORD WHICH RESTRICTED HIS ABILITY TO STAY CLEAR OF THE NOSEWHEEL, TUG, AND TOWBAR. THE TUG DRIVER SAID THAT IN HIS PERIPHERAL VISION, HE SAW THE WALKER FALL AND STOPPED THE TUG IMMEDIATELY; HOWEVER, THE TUG WAS NOT STOPPED PRIOR TO STRIKING THE FALLEN WALKER WHO WAS FATALLY INJURED. NO WITNESSES WERE FOUND WHO COULD SAY WHY THE WALKER FELL. EXAMINATION OF COMPANY PROCEDURES REVEALED THEY ISSUED A MAINTENANCE TRAINING BULLETIN IN 12/89. THE BULLETIN REFERENCED A 'REQUIREMENT' TO STAY CLEAR OF THE AIRPLANE NOSEWHEEL. ALTHOUGH SENT TO ALL STATIONS, THE BULLETIN WAS NOT MANDATORY READING AND IT WAS NOT DETERMINED IF THE WALKER WAS AWARE OF ITS CONTENT. IN ADDITION, THE REQUIREMENTS OF THE BULLETIN WERE NOT IMPLEMENTED INTO THE GENERAL MAINTENANCE MANUAL.
Probable cause
A LACK OF ADEQUATE CLEARANCE BETWEEN THE WALKER AND TUG WHICH RESULTED IN THE WALKER BEING STRUCK BY THE TUG WHEN HE FELL FOR UNKNOWN REASON(S). A FACTOR RELATED TO THE ACCIDENT WAS THE LACK OF A POLICY TO STAY CLEAR OF THE TUG, TOWBAR, AND NOSEWHEEL OF THE AIRPLANE, WHILE PUSHBACK OPERATIONS ARE IN MOTION.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC93LA040
- Event ID
- 20001211X16222
- Case number
- NYC93LA040
- 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, damage. 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: 0e609f2734b62b38a8184145950d235716a8bb8b721f660f4b439ce1ff36ac7c; retrieved 2026-09-18T18:42:29.049Z.