USAir Boeing 727-281 accident
Boeing 727-281 · Accident: airframe, component or system failure en route
From Charlotte Douglas International Airport (CLT) to an unrecorded destination
Event
- NTSB case
- ATL90FA135
- 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 727-281
- Aircraft type
- Boeing 727
- 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
- N743US
- Operator
- USAir
- Onboard fatalities
- Unknown
- Route
- From Charlotte Douglas International Airport (CLT), Charlotte, NCTo 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
- En route · descent
- 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
- Passenger › Emergency equipment, improper use of
Approximate · Estimated position: the centre of Charleston, SC, the place the record names. Not the accident site.
NTSB narrative
WHILE PASSING 10,000 FEET MSL ON THE DESCENT FOR A NIGHT LANDING, THE NUMBER TWO ENGINE FIRE WARNING LIGHT AND BELL ACTIVATED. FOLLOWING ACCOMPLISHMENT OF ALL CHECKLIST PROCEDURES, THE FIRE WARNING INDICATIONS REMAINED ON. THE CAPTAIN ORDERED AN EMERGENCY EVACUATION ON THE RUNWAY AFTER THE AIRPLANE LANDED. DURING THE EVACUATION, ONE PASSENGER WAS KNOCKED OFF OF THE WING BY AN OVERZEALOUS PASSENGER AND WAS SERIOUSLY INJURED. ANOTHER PASSENGER WITH TWO SMALL CHILDREN REQUESTED ASSISTANCE FROM THE FLIGHT ATTENDANT. WHILE THE FLIGHT ATTENDANT WAS SEEKING HELP, THE PASSENGER PUT ONE CHILD ON THE SLIDE WITHOUT WAITING FOR ASSISTANCE, AND THE CHILD RESISTED. THE CHILD FELL FROM THE SLIDE AND WAS SERIOUSLY INJURED. POST-FLIGHT EXAMINATION OF THE AIRPLANE REVEALED A FAULTY FIRE DETECTION ELEMENT ON THE NUMBER TWO ENGINE, AND NO EVIDENCE OF INFLIGHT FIRE WAS OBSERVED.
Probable cause
IMPROPER UTILIZATION OF THE EMERGENCY EQUIPMENT.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL90FA135
- Event ID
- 20001212X23320
- Case number
- ATL90FA135
- 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: local date, investigation status, damage. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1990-06-22.
- API snapshot SHA-256: 592c7b51cdd0d30b71655adb51c4f9eb389fe754523fdd49afac6372cc4d5f6d; retrieved 2026-09-18T19:01:42.700Z.