Piedmont Airlines Boeing 767-201 accident
Boeing 767-201 · Accident while standing
From Los Angeles International Airport (LAX) to Baltimore/Washington International Thurgood Marshall Airport (BWI)
Event
- NTSB case
- LAX89LA144
- 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 767-201
- Aircraft type
- Boeing 767
- 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
- N645US
- Operator
- Piedmont Airlines
- Onboard fatalities
- Unknown
- Route
- From Los Angeles International Airport (LAX), Los Angeles, CATo Baltimore/Washington International Thurgood Marshall Airport (BWI), Baltimore, MD
- 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) not 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
- Miscellaneous/other
- 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
- Copilot/second pilot › Equipment, other, improper use of
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
DUE TO THE SUSPICIOUS BEHAVIOR OF A PASSENGER THAT ELECTED TO DEPLANE BEFORE THE FLIGHT DEPARTED AND WAS LATER QUESTIONED BY AUTHORITIES, THE CAPTAIN ELECTED TO RETURN AND LAND. DURING AN EMERGENCY EVACUATION, THE FIRST OFFICER OPTED TO EVACUATE THE AIRPLANE VIA THE EMERGNECY ROPE LOCATED IN THE COCKPIT. THE FIRST OFFICER DID NOT FULLY EXTEND THE ROPE FROM THE STOWED POSITON. WHEN HIS WEIGHT WAS PUT ON THE ROPE IT UNRAVELLED RAPIDLY. THE FIRST OFFICER WAS UNABLE TO HANG ON AND DROPPED TO THE GROUND SUSTAINING SERIOUS INJURY. ONE OTHER PASSENGER BROKE HER ANKLE DURING THE EVACUATION.
Probable cause
THE FIRST OFFICER DID NOT PROPERLY EVACUATE THE AIRPLANE.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX89LA144
- Event ID
- 20001213X28113
- Case number
- LAX89LA144
- 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: a81510a4f497519127852f41fe407c55dc0f449cf7d4b4801476da7471c678d5; retrieved 2026-09-18T19:12:51.199Z.