Loss of control Accident Beechcraft V35B N4662M,
ASN logo
ASN Wikibase Occurrence # 286353
 
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information.

Date:Friday 18 January 2008
Time:14:00 LT
Type:Silhouette image of generic BE35 model; specific model in this crash may look slightly different    
Beechcraft V35B
Owner/operator:Private
Registration: N4662M
MSN: D-10125
Total airframe hrs:2931 hours
Engine model:Teledyne Continental IO-520-BA14
Fatalities:Fatalities: / Occupants: 1
Aircraft damage: Substantial
Category:Accident
Location:Selma, California -   United States of America
Phase: En route
Nature:Private
Departure airport:Fresno Chandler, CA
Destination airport:San Diego-Montgomery-Gibbs Executive Airport, CA (MYF/KMYF)
Investigating agency: NTSB
Confidence Rating: Accident investigation report completed and information captured
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.

Accident investigation:
cover
  
Investigating agency: NTSB
Report number: LAX08FA047
Status: Investigation completed
Duration: 1 year
Download report: Final report

Sources:

NTSB LAX08FA047

Location

Revision history:

Date/timeContributorUpdates
03-Oct-2022 09:29 ASN Update Bot Added

Corrections or additions? ... Edit this accident description

The Aviation Safety Network is an exclusive service provided by:
Quick Links:

CONNECT WITH US: FSF on social media FSF Facebook FSF Twitter FSF Youtube FSF LinkedIn FSF Instagram

©2024 Flight Safety Foundation

1920 Ballenger Av, 4th Fl.
Alexandria, Virginia 22314
www.FlightSafety.org