BFO92FA135 · Beech G35
Beech G35 · Accident: loss of engine power en route
From Richmond International Airport (RIC) to Twin County Airport (HLX)
Event
- NTSB case
- BFO92FA135
- 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
- 2 · 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 G35
- 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
- N4526D
- Operator
- Patrick Johnson
- Onboard fatalities
- Unknown
- Route
- From Richmond International Airport (RIC), Richmond, VATo Twin County Airport (HLX), Hillsville, VA
- 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
- Loss of engine power
- 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
- Stall/spin
- 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
- Pilot in command › Airspeed, not maintained
- Pilot in command › Stall/spin, inadvertent
- Reason for occurrence undetermined
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT WAS 1 HOUR 24 MINUTES INTO THE FLIGHT AT A CRUISE ALTITUDE OF 8000 FEET WHEN HE REPORTED TO AIR TRAFFIC CONTROL (ATC) THAT HE HAD LOST ENGINE POWER. HE WAS APPROXIMATELY 12 MILES FROM THE CLOSEST AIRPORT AT A FIELD ELEVATION OF 2693 FEET, AND WAS PROVIDED VECTORS TO THAT AIRPORT. HE RADIOED ATC 3 MINUTES LATER ADVISING THEM THAT HE WAS DESCENDING AT A RATE OF 600-700 FEET PER MINUTE AND WAS UNSURE WHETHER HE COULD MAKE IT TO THE AIRPORT. ONE MINUTE LATER HE CONTACTED ATC AND ADVISED THAT HE WAS GOING TO TRY TO LAND ON THE HIGHWAY. THERE WAS NO FURTHER RADIO COMMUNICATION. A WITNESS REPORTED SEEING THE AIRCRAFT WITHOUT ENGINE POWER DESCENDING TO THE SOUTH IN A STEEP ANGLE. SHE REPORTED THAT THE AIRCRAFT MADE A SUDDEN LEFT TURN AND FELL TO THE GROUND. THE WRECKAGE WAS LOCATED 3.5 MILES NORTH OF THE AIRPORT WHERE IT CAME TO REST ON A DIRT ROAD. EXAMINATION OF THE AIRPLANE DID NOT DISCLOSE EVIDENCE OF MECHANICAL MALFUNCTION.
Probable cause
LOSS OF ENGINE POWER FOR AN UNDETERMINED REASON AND FAILURE OF THE PILOT TO MAINTAIN AIRSPEED, WHICH RESULTED IN A STALL/SPIN.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record BFO92FA135
- Event ID
- 20001211X15604
- Case number
- BFO92FA135
- 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: 34f7f6621754c693189442f6bb9fd51b2c11f1b0906b8685afae6ec3136b9408; retrieved 2026-09-21T00:57:16.238Z.