FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX84LA122 · Boeing 737-200

25 Dec 1983 · Phoenix, AZ, United States

Boeing 737-200 · Accident: propeller blast or jet exhaust/suction while standing

From an unrecorded airport to Harry Reid International Airport (LAS)

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
LAX84LA122
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
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
Visual Meteorological Cond

Boeing 737-200

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
N133AW
Operator
Unknown
Onboard fatalities
Unknown
Route
From not recordedTo Harry Reid International Airport (LAS), Las Vegas, NV
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 · engine(s) operating
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

  • Ground personnel › Procedures/directives, not followed
  • Ground personnel › Visual lookout, inadequate

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

NTSB narrative

THE ACFT WAS STANDING WITH ENGINES RUNNING AND A BAGGAGE HANDLER WAS BLOWN OFF HIS FEET WHEN HE WENT BEHIND THE ACFT. THE ACFT HAD BEEN CALLED BACK TO THE RAMP BECAUSE AN ACCESS DOOR WAS OPEN. THE BAGGAGE HANDLER APPROACHING THE ACFT FROMTHE REAR TO CLOSE THE DOOR FAILED TO SIGNAL THE CREW TO SHUT DOWN THE ENGINES. HE SAID HE BELIEVED HE HEARD THE RIGHT ENGINE SPOOLING DOWN. THE BAGGAGE HANDLER WAS THROWN ABOUT 8-10 FT AND LANDED ON HIS KNEE. HIS KNEE CAP WAS BROKEN. THE FLT CREW WAS UNAWARE OF THE ACCIDENT UNTIL INFORMED BY THE COMPANY.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record LAX84LA122
Event ID
20001214X45346
Case number
LAX84LA122
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: 993ab12d6204f81cd14598cc614c8a74ee49ab29327ab33c398de887147ae97b; retrieved 2026-09-18T20:46:33.149Z.