United Airlines Boeing 737-222 incident
Boeing 737-222 · Incident: total loss of engine power (mechanical failure) during initial climb
From an unrecorded airport to Sacramento International Airport (SMF)
Event
- NTSB case
- SEA91IA081
- 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
- Visual Meteorological Cond
Boeing 737-222
- 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
- N9003U
- Operator
- United Airlines
- Onboard fatalities
- Unknown
- Route
- From not recordedTo Sacramento International Airport (SMF), Sacramento, CA
- 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
- Initial climb
- 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
- Total loss of engine power (mechanical failure)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Minor
Cause areas
- Turbine assembly, turbine blade › Fatigue
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
DURING THE INITIAL CLIMB, THE FLIGHT CREW HEARD A LOUD BANG FOLLOWED BY AIRFRAME VIBRATIONS. THE CREW WAS NOTIFIED BY THE CONTROL TOWER THAT SMOKE AND FLAME WERE EMITTING FROM THE LEFT ENGINE. THE FLIGHT CREW DECLARED AN EMERGENCY AND WAS CLEARED TO LAND. THE PILOT DISCHARGED A BANK OF FIRE EXTINGUISHING AGENT AND SHUT THE ENGINE DOWN. THE FLIGHT LANDED WITHOUT FURTHER INCIDENT. DURING THE FOLLOW-UP INVESTIGATION, IT WAS FOUND THAT A TURBINE BLADE FAILED IN FATIGUE. THE FLIGHT CREW HAD RECEIVED AN INDICTION THAT THE FIRE EXTINGUISHING AGENT HAD DISCHARGED, HOWEVER, IT WAS LATER FOUND THAT IT DIDN'T DUE TO THE INSTALLATION OF AN INCORRECT DISCHARGE OUTLET. THE REAR EMERGENCY SLIDE ON THE RIGHT SIDE WAS SLOW IN INFLATING AND WAS NOT USABLE FOR THE EVACUATION. THE SLIDE WAS INSTALLED ON A TEST STAND AND FOUND TO OPERATE WITHIN NORMAL OPERATING PARAMETERS.
Probable cause
TURBINE BLADE FAILURE FROM FATIGUE. FACTORS TO THE INCIDENT WERE INOPERATIVE ENGINE FIRE EXTINGUISHER, INADEQUATE SERVICE OF AIRCRAFT AND DELAYED DEPLOYMENT OF EMERGENCY SLIDE.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA91IA081
- Event ID
- 20001212X16879
- Case number
- SEA91IA081
- 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. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1991-04-10.
- API snapshot SHA-256: cf54942f7648509cf621e0f5869ac33377db94b60875b8c3663cf4c161bbf033; retrieved 2026-09-18T18:55:37.155Z.