NTSB Issues Probable Cause Report From 2015 Accident In Van Nuys, CA | Aero-News Network
Aero-News Network
RSS icon RSS feed
podcast icon MP3 podcast
Subscribe Aero-News e-mail Newsletter Subscribe

Airborne Unlimited -- Most Recent Daily Episodes

Episode Date

Airborne-Monday

Airborne-Tuesday

Airborne-Wednesday Airborne-Thursday

Airborne-Friday

Airborne On YouTube

Airborne-Unlimited-04.29.24

Airborne-Unlimited-04.23.24

Airborne-Unlimited-04.24.24 Airborne-FltTraining-04.25.24

Airborne-Unlimited-04.26.24

Fri, Dec 22, 2017

NTSB Issues Probable Cause Report From 2015 Accident In Van Nuys, CA

JPL Scientist Was Fatally Injured In The Accident

The NTSB has released its probable cause report from an accident which occurred in January, 2015 that fatally injured Dr. Alberto Behar, a scientist with NASA's Jet Propulsion Laboratory in California. The Board cited pilot error as the probable cause of the accident.

According to the report, Behar had just taken off for a personal, cross-country flight. Several witnesses reported that, shortly after takeoff, when the airplane was about 400 ft above the ground, they heard the engine "pop" at least twice, sputter, and then go silent, consistent with a loss of engine power. About this time, the pilot reported to the tower controller very quickly but not very clearly that "I have an engine failure I think." The tower controller subsequently issued the pilot the current altimeter setting and attempted to contact the pilot but did not receive any further radio transmissions. The airplane continued straight, turned right, and then spun to the ground. A postaccident examination of the airframe and engine did not reveal any anomalies that would have precluded normal operation. The airplane was last refueled before its previous flight in Flagstaff, Arizona, 4 days before the accident; the airplane was then flown from Flagstaff to the Van Nuys Airport, Van Nuys, California. Although a narrow stream of what smelled like gasoline and engine oil was found near the wreckage, there was no fuel remaining in the fuel tanks.

The airplane was equipped with an electronic flight instrument system (EFIS), which has a low fuel alert that is set by the pilot or a mechanic. When fuel decreases to the specified amount, an alert pops up front and center on the EFIS, and it will not disappear until the pilot acknowledges it. Given that the pilot mostly conducted his own maintenance, it is highly likely he was familiar with the EFIS and knew that the airplane was low on fuel and how much fuel remained but decided to take off anyway. As a result of his decision, the engine lost engine power shortly after takeoff due to fuel exhaustion at too low of an altitude for the pilot to recover from the stall and subsequent spin.

A friend of the pilot reported that the pilot texted him about 1249 when he arrived at the airport. He said that the pilot normally arrived about 1230. The pilot seemed to be in a rush that day because he was supposed to fly home the day before, and apparently he and his wife had argued about the issue. In addition, the pilot's friend noted that the pilot had recently become more conscious about where he bought fuel. Based on the directions the pilot received from the air traffic controller to stay below 2,000 ft if flying to Burbank, the friend believes it is likely the pilot was attempting to fly to Whiteman Airport about 5 nautical miles away that had cheaper fuel before continuing to his destination.

According to the air traffic control recordings, the pilot first contacted the ground and tower controllers about 1308, and he was cleared for takeoff at 1311. Just before takeoff, the pilot's work e-mail documented nine messages, three of which were sent by the pilot, the last of which was sent at 1311. In the emails, the pilot indicated confusion about an issue, which may have been a further distraction to him. The evidence indicates that the pilot was rushed and sending e-mails, which likely distracted him during the taxi and takeoff and decreased his vigilance about the airplane's fuel status.

The National Transportation Safety Board determines the probable causes of this accident to be the pilot's improper decision to take off despite low fuel alerts, which resulted in a total loss of engine power due to fuel exhaustion, his subsequent failure to maintain adequate airspeed and his exceedance of the airplane's critical angle of attack, which led to an aerodynamic stall and loss of control at too low of an altitude to recover. Contributing to the accident was the pilot's distraction due to his sending e-mails and being rushed during taxi and takeoff, which resulted in reduced vigilance about the airplane's fuel status.

(Source: NTSB. Image from accident docket)

FMI: Full Report

Advertisement

More News

ANN's Daily Aero-Term (04.26.24): DETRESFA (Distress Phrase)

DETRESFA (Distress Phrase) The code word used to designate an emergency phase wherein there is reasonable certainty that an aircraft and its occupants are threatened by grave and i>[...]

Aero-News: Quote of the Day (04.26.24)

"General aviation is at the forefront of developing and introducing innovative technologies that will transform the entire aviation industry..." Source: Kyle Martin, Vice President>[...]

ANN's Daily Aero-Term (04.27.24): Direct

Direct Straight line flight between two navigational aids, fixes, points, or any combination thereof. When used by pilots in describing off-airway routes, points defining direct ro>[...]

ANN's Daily Aero-Linx (04.27.24)

Aero Linx: Women in Corporate Aviation Women in Corporate Aviation support individuals seeking career advancement and professional development in the business aviation industry. Me>[...]

Aero-News: Quote of the Day (04.27.24)

“We would like to thank the many volunteers that help throughout the year to pull off the event, as well as the several reviewers, judges, and SURVICE staff that provide team>[...]

blog comments powered by Disqus



Advertisement

Advertisement

Podcasts

Advertisement

© 2007 - 2024 Web Development & Design by Pauli Systems, LC