FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

USAir Boeing 737-4B7 accident

23 Oct 1991 · Boston, MA, United States

Boeing 737-4B7 · Accident: airframe, component or system failure during landing

From Baltimore/Washington International Thurgood Marshall Airport (BWI) to an unrecorded destination

Report a problem

Event

NTSB case
NYC92LA018
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-4B7

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
N441US
Operator
USAir
Onboard fatalities
Unknown
Route
From Baltimore/Washington International Thurgood Marshall Airport (BWI), Baltimore, MDTo not recorded
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
Landing · landing roll
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
Airframe, component or system failure
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

  • Miscellaneous eqpt/furnishings, storage bins/racks › Failure, total

Approximate · Estimated position: the centre of Boston, MA, the place the record names. Not the accident site.

NTSB narrative

THE BOEING 737 WAS ON LANDING ROLL WHEN A DOOR IN THE AFT GALLEY OPENED. A LIQUOR KIT ROLLED OUT TOWARD AN AFT FACING FLIGHT ATTENDANT WHO FENDED OFF THE KIT WITH HER LEFT HAND. HER HAND BENT REARWARD AND THE FLIGHT ATTENDANT RECEIVED A BROKEN WRIST. BOTH FLIGHT ATTENDANTS SEATED IN THE REAR OF THE AIRPLANE SAID THEY BELIEVED THE DOOR WAS LOCKED PRIOR TO LANDING. AFTER LANDING THE FLIGHT ATTENDANTS WERE ABLE TO OPEN THE DOOR AGAIN BY HAND AFTER IT WAS LOCKED. MAINTENANCE PERSONNEL WERE UNABLE TO DUPLICATE THE FAILURE; HOWEVER, THE LATCHES WERE REPLACED AS A PRECAUTION.

Probable cause

A LATCH FAILURE ON A DOOR IN THE AFT GALLEY WHICH ALLOWED A LIQUOR KIT TO ROLL FORWARD.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record NYC92LA018
Event ID
20001212X18378
Case number
NYC92LA018
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: d3ccf5ebe90c849bb324709a4d7cfcfc6e4f39f755fe614f6e231eeb21ebaf2c; retrieved 2026-09-18T18:51:03.811Z.