United Airlines Flight 984
Boeing 767-322 · Incident while standing
From Miami International Airport (MIA) to Chicago O'Hare International Airport (ORD)
Event
- NTSB case
- MIA94IA043
- 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 767-322
- 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
- N648UA
- Operator
- United Airlines
- Onboard fatalities
- Unknown
- Route
- From Miami International Airport (MIA)To Chicago O'Hare International Airport (ORD), Chicago, IL
- 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
- 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
- Unqualified person › Emergency procedure, initiated
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE AIRPLANE HAD BEEN PUSHED FROM THE GATE AND THE #1 ENGINE HAD BEEN STARTED. DURING ENGINE START OF THE #2 ENGINE, A HIGH FUEL FLOW WAS OBSERVED BY THE FLIGHT CREW AND A PASSENGER IN THE RIGHT SIDE OF THE AIRPLANE OBSERVED A FLAME AFT OF THE EXHAUST. THE PASSENGER SHOUTED 'FIRE', OPENED THE #2L DOOR AND DEPLOYED THE EMERGENCY ESCAPE SLIDE. THE PASSENGERS BEGAN AN UNCOMMANDED EVACUATION OF THE AIRPLANE. THE CAPTAIN WAS ADVISED BY A FLIGHT ATTENDANT THAT THE REMAINING PASSENGERS WANTED TO EVACUATE THE AIRPLANE AND THE CAPTAIN DIRECTED THAT THE #1L AND #1R DOORS BE OPENED AND THE EMERGENCY ESCAPE SLIDES UTILIZED. THE CAPTAIN SECURED THE ENGINES, ENTERED THE CABIN AND THEN STOPPED THE EVACUATION OF THE REMAINING 24 PEOPLE.
Probable cause
EMERGENCY PROCEDURE INITIATED BY AN UNQUALIFIED PERSON.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA94IA043
- Event ID
- 20001206X00659
- Case number
- MIA94IA043
- 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: 368cc8860cbde5853f62715e1c184c0f13c7af08648a99c58abf37c5d450d7b1; retrieved 2026-09-18T18:24:04.569Z.