FTW02LA191 · Beech BE-V35B
Beech BE-V35B · Accident: loss of engine power on approach
From Baton Rouge Metropolitan Airport (BTR) to Baton Rouge Metropolitan Airport (BTR)
Event
- NTSB case
- FTW02LA191
- 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 BE-V35B
- Aircraft type
- Beechcraft BE-V35B
- 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
- N1SU
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Baton Rouge Metropolitan Airport (BTR), Baton Rouge, LATo Baton Rouge Metropolitan Airport (BTR), Baton Rouge, LA
- 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
- Approach · VFR pattern final
- 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
- Loss of engine power
- 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
- Reason for occurrence undetermined
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
During the turn to final approach to the runway, the pilot attempted to increase engine power; however, there was no response from the engine. The pilot applied full throttle with the auxillary fuel pump turned ON; however, there was still no change in engine power. The pilot realized he would not make the runway and initiated a forced landing to a field. During the forced landing, the airplane impacted trees and a roadway ditch, crossed a road, and came to rest upright short of the airport. At the manufacturer's facilities, the engine was examined and test run. The engine was test run for 40 minutes at various power settings. According to the manufacturer, "No discrepancy was found on this engine inspection that would have caused a power loss."
Probable cause
the loss of engine power for undetermined reasons. A contributing factor was the lack of suitable terrain for the forced landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW02LA191
- Event ID
- 20020627X00982
- Case number
- FTW02LA191
- 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, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2002-06-27.
- API snapshot SHA-256: b5274da7d53678ffa5b9faf674b73cb4992cc807b02513135c5b388fdd5b3f2e; retrieved 2026-09-21T19:41:08.566Z.