LAX91FA386 · Cessna 172K
Sheble Aviation Cessna 172K · Accident: fire/explosion en route
From Harry Reid International Airport (LAS) to BUT · Blythe, CA
Event
- NTSB case
- LAX91FA386
- 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
- General aviation
- 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
Cessna 172K
- Aircraft type
- Cessna 172
- 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
- N7031G
- Operator
- Sheble Aviation
- Onboard fatalities
- Unknown
- Route
- From Harry Reid International Airport (LAS), Las Vegas, NVTo BUT · Blythe, 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 91: General Aviation
- 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 · cruise
- 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
- Fire/explosion
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Electrical system › Overload
- Electrical system › Shorted
- Electrical system, circuit breaker › Inadequate
- Manufacturer › Insufficient standards/requirements, manufacturer
Approximate · Estimated position: the centre of Bullhead City, AZ, the place the record names. Not the accident site.
NTSB narrative
THE ATP CERTIFICATED PILOT AND HIS WIFE HAD BEEN AIRBORNE FOR ABOUT 35 MINUTES AND WERE APPROACHING AN AIRPORT FOR LANDING WHEN SHE STATED THAT THEY HAD AN INFLIGHT CABIN FIRE. THE NIGHT FLIGHT ORIGINATED AT LAS VEGAS, NEVADA, WHERE THEY HAD JUST BEEN MARRIED. PRIOR TO REACHING THE INTENDED AIRPORT, SHE STATED THE FIRE ORIGINATED IN THE OVERHEAD LIGHT CONSOLE WHICH HOUSES 2 RHEOSTATS AND A LIGHT SWITCH. THE FIRE BEGAN TO BURN THE HEADLINER AND PLASTIC CONSOLE. THE BURNING PLASTIC WAS DRIPPING ONTO THEIR BODIES. THE AIRCRAFT CRASHED OUT OF CONTROL NEAR THE RUNWAY IN THE DIRT AND WAS DESTROYED. THE CABIN FIRE WAS EXTINGUISHED BY THE LOCAL FIRE DEPARTMENT. A DUPLICATE CONSOLE WAS TESTED. WHEN THE DOOR POST LIGHT WAS SHORTED, THE LIGHTING RHEOSTAT IN THE CONSOLE REACHED IN EXCESS OF 1425 DEGREES FAHRENHEIT AT A CIRCUIT LOAD 6 AMPS MAXIMUM. THE CIRCUIT IS PROTECTED BY A 10 AMP BREAKER. THE OVERHEAD CABIN PLASTIC MATERIAL WAS FOUND TO READILY BURN.
Probable cause
1) A SHORT CIRCUIT, 2) ELECTRICAL OVERLOAD WHICH IGNITED THE CABIN INTERIOR, 3) INADEQUATE ELECTRICAL CIRCUIT PROTECTION, AND 4) INSUFFICIENT ELECTRICAL SYSTEM DESIGN STANDARDS.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX91FA386
- Event ID
- 20001212X18104
- Case number
- LAX91FA386
- 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-09-08.
- API snapshot SHA-256: b0af2ffec8995cd66f011b91bbff44a91d051e3e4e94cb3606dabb20e0630e51; retrieved 2026-09-21T15:20:47.084Z.