FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Lufthansa Airlines Boeing 747-230 incident

18 Jan 1984 · Jamaica, NY, United States

Boeing 747-230 · Incident: propeller blast or jet exhaust/suction during takeoff

From an unrecorded airport to Frankfurt Main Airport (EDDF)

Report a problem

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

Event

NTSB case
NYC84IA071
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
0
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
Instrument Meteorological Cond

Boeing 747-230

Aircraft type
Boeing 747
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
DABYO
Onboard fatalities
Unknown
Route
From not recordedTo Frankfurt Main Airport (EDDF), FRANKFURT,GERM.
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 129: Foreign
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
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
Propeller blast or jet exhaust/suction
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

  • Driver of vehicle › Instructions, written/verbal, not understood
  • Driver of vehicle › Visual lookout, inadequate

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

AT THE TIME OF THE INCIDENT, RWY 31L WAS THE ONLY ACTIVE RWY. APRX 9 SNOW REMOVAL VEHICLES WERE BEING USED TO REMOVE SNOW FROM RWY 4L/22R. THE VEHICLE DRIVERS WERE INSTRUCTED TO HOLD SHORT OF RWY 31L, THEN BOEING 747, D-ABYO, WAS CLEARED FOR TAKEOFF. THE PLT BEGAN HIS TAKEOFF, BUT NOTED THAT A CAR WAS APPROACHING THE RWY. HE INITIATED AN ABORTED TAKEOFF. THE DRIVER OF THE CAR THOUGHT RWY 31L WAS CLOSED. BEFORE ENTERING THE RWY, HE SAW THE ACFT & APPLIED BRAKES, BUT THE CAR SLID ONTO THE RWY. THE ACFT & CAR DID NOT COLLIDE, BUT JET EXHAUST FROM THE ACFT OVERTURNED THE CAR & INJURED THE OCCUPANTS.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record NYC84IA071
Event ID
20001214X38659
Case number
NYC84IA071
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: 5c54ecc1e8e9ed412af96921987263dab4c07178eee2c213e38b1469bb6ea8cc; retrieved 2026-09-18T20:45:24.083Z.