FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR15FA081 · Gibbs LANCAIR 320

9 Jan 2015 · Van Nuys, CA, United States

Gibbs LANCAIR 320 · Accident: fuel exhaustion during initial climb

From Van Nuys Airport (VNY) to Scottsdale Airport (SDL)

Report a problem

Event

NTSB case
WPR15FA081
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

Gibbs LANCAIR 320

Aircraft type
Gibbs LANCAIR 320
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
N7ZL
Operator
Unknown
Onboard fatalities
Unknown
Route
From Van Nuys Airport (VNY), Van Nuys, CATo Scottsdale Airport (SDL), Scottsdale, AZ
Aircraft age
About 19 years (built 1996)
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
Initial climb
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
Fuel exhaustion
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 › Fluids/miscellaneous hardware
  • Personnel issues › Action/decision
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The commercial pilot was taking 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.

Probable cause

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.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR15FA081
Event ID
20150109X71237
Case number
WPR15FA081
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. 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: 6955b7dfb48f16bb0b07dd0d9fb48467f192a7bc8d01364034abb91d75d57b4a; retrieved 2026-09-14T17:30:40.129Z.