CEN14LA273 · Beech H35
Beech H35 · Accident on approach
From Monroe Regional Airport (MLU) to Monroe Regional Airport (MLU)
Event
- NTSB case
- CEN14LA273
- 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
- Unknown
- 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 H35
- 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
- N653T
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Monroe Regional Airport (MLU), Monroe, LATo Monroe Regional Airport (MLU), Monroe, LA
- Aircraft age
- About 57 years (built 1957)
- 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
- Approach
- Defining eventThe 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
- Unknown or undetermined
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Not determined › Not determined
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The commercial pilot was conducting a maintenance test flight. According to Federal Aviation Administration audio files, the pilot reported to an air traffic controller that the airplane was experiencing an unspecified fuel problem. The engine then experienced a total loss of power, and the pilot conducted a forced landing, during which the airplane collided with a tree and then impacted a parking lot. A postaccident examination of the airframe, engine, and fuel system did not reveal any preimpact anomalies that would have precluded normal operation. A review of data obtained from the airplane's engine data monitoring system did not reveal any unusual engine readings before the loss of engine power.
At the accident site, fuel was drained from each wing tank and a fuel line leading to the engine; the fuel from the fuel line was orange. Testing of the orange fuel sample revealed the presence of silicon. The tank seals and lines were intact, and the source of the silicon could not be determined. No silicon nor any white powdery deposits (the expected combustion byproducts of silicon) were found on any of the engine components. The reason for the loss of engine power could not be determined.
Probable cause
The loss of engine power for reasons that could not be determined because postaccident examination of the airframe and engine did not reveal any anomalies that would have precluded normal operation.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN14LA273
- Event ID
- 20140602X60048
- Case number
- CEN14LA273
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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, coordinates. 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: cb3f678e0c5b2bd0730ac21e1441f3e11590e297afa0e8e8b88de931405c8afc; retrieved 2026-09-15T23:42:37.770Z.