LAX85FA238 · Beech V35A
Beech V35A · Accident: fire while taxiing
From Santa Monica Municipal Airport (SMO) to Richfield Municipal Airport (RIF)
Event
- NTSB case
- LAX85FA238
- 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
Beech V35A
- Aircraft type
- Beechcraft 35
- 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
- N4RW
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Santa Monica Municipal Airport (SMO)To Richfield Municipal Airport (RIF), Richfield, UT
- 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
- Taxi · from runway
- 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
- 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
- Engine assembly, other › Fire
- Fluid, fuel › Leak
- Fuel system › Undetermined
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
AFTER DEPTG & CLIMBING TO 4500', THE PLT & HIS PLT RATED PAX NOTED A FUEL ODOR & RETURNED TO THE ARPT TO LAND. BFR LNDG,THE PLT CALLED THE TOWER (TWR), BUT DIDN'T ADVISE TWR PSNL OF THE FUEL ODOR OR OF A PSBL PRBLM. AS THE ACFT WAS TURNING OFF THE RWY, FIRE & SMOKE ERUPTED IN THE ENG COMPARTMENT & SPREAD BEYOND THE FIREWALL TO THE COCKPIT. THE PLT & BOTH PAXDEPLANED. A TWR CONTROLLER SAW THE SMOKE & INITIATED FIRE/RESCUE RESPONSE, BUT DIDN'T USE PROPER TERMINOLOGY. FIRE DEPT PSNL WERE DISPATCHED APRX 1 MIN LATER. BY THE TIME THEY ARRIVED, THE ACFT WAS BADLY DAMAGED. MOST OF THE ENG'S FIRE DAMAGE WAS ON ITS LEFT SIDE. WHEN TESTED, SVRL FUEL LINES/COMPONENTS LEAKED, BUT THEY HAD FIRE DAMAGE & THE EXACT IN-FLTFUEL LEAK WAS NOT VERIFIED. FUEL STAIN/DISCOLORATION WAS NOTED WHERE THE AIR THROTTLE METERING UNIT LEAKED AT AN O-RING.THERE WAS A FUEL LEAK AT THE IDLE FUEL ADJUSTMENT SCREW, ALTHO IT WAS 'FROZEN' IN A FIXED PSN. ALSO, BEECH HAD RCMDD REPLACING THE FUEL LINES EVERY 5 YRS, BUT NO RECORD WAS FND OF THEIR REPLACEMENT DURING THE LAST 5 YRS.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record LAX85FA238
- Event ID
- 20001214X36485
- Case number
- LAX85FA238
- 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. 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: 7d84f29847f9611cb8273c2ba9309e45504620a34eec66825c74394d3383932e; retrieved 2026-09-23T17:50:16.615Z.