FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX08FA047 · Beechcraft V35B

18 Jan 2008 · Selma, CA, United States

Beechcraft V35B · Accident: aircraft structural failure during an uncontrolled descent

From KFHC · Fresno Chandler, CA to Montgomery-Gibbs Executive Airport (KMYF)

Report a problem

Event

NTSB case
LAX08FA047
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
1 · 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

Beechcraft V35B

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
N4662M
Operator
Robert G. Mollring · private individual
Onboard fatalities
Unknown
Route
From KFHC · Fresno Chandler, CATo Montgomery-Gibbs Executive Airport (KMYF), San Diego, 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
Uncontrolled descent
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
Aircraft structural failure
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

  • Aircraft › Aircraft oper/perf/capability
  • Aircraft › Aircraft structures

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The airplane was on an IFR cross-country flight in clear VFR conditions. The radar track was consistent with the flight's ATC clearance to the south-southeast in a steady 900-foot-per-minute climb. About 4 minutes after departure the pilot requested to leave the frequency for 1 minute, which the controller approved. The airplane vanished from radar 4 minutes later and entered a 5,400-foot-per-minute or greater rate of descent. A witness saw the airplane "disintegrate" in flight. The airplane wreckage was distributed along a 1,541-foot-long north-south debris field in the vicinity of the last radar return. Examination of the wreckage did not reveal any evidence of a pre-existing airframe, engine, or flight control anomaly. The pilot had a history of episodic incapacitating pain, diabetes requiring insulin, the use of multiple potentially impairing medications, and a history of alcohol abuse. The pilot had not noted the pain, the diabetes, or the medications used to treat these conditions on his most recent application for airman medical certificate. The pilot's FAA medical records did note a history of driving while intoxicated in 1992, but the FAA had not requested any additional details surrounding the pilot's alcohol use. The pilot had been drinking alcohol within hours of the flight, and the forensic toxicology report was consistent with a blood alcohol level of approximately 0.07 percent at the time of the accident, sufficient to have resulted in impairment. The toxicology report also was consistent with the use of multiple prescription medications that are potentially impairing, but no blood was available for evaluation and it was therefore not possible to estimate when the medications might have been most recently used or whether the pilot may have been impaired by the medication use or by interactions between those medications and/or alcohol.

Probable cause

The pilot's failure to maintain control resulting in the in-flight break-up of the airplane due to aerodynamic overload. Contributing factors included the pilot's impairment due to multiple medical conditions and due to recent use of alcohol.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX08FA047
Event ID
20080123X00098
Case number
LAX08FA047
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: e513f9e1eb9b14759e5607da9398daf7677bf5602d5879b98b65bf2ed3283bc2; retrieved 2026-09-13T18:53:46.615Z.