The U.S. aircraft register, updated daily
Accidents · NTSB WPR15FA081 · Final report

Amateur-built LANCAIR 320 accident near Van Nuys, California, January 9, 2015

On January 9, 2015 at about 9:13 pm local time, a 1996 amateur-built LANCAIR 320, registered N7ZL, was substantially damaged in an accident during initial climb near Van Nuys, California (Van Nuys Airport). It was a personal flight under general aviation rules (Part 91). 1 person was killed. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

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 aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
January 9, 2015 · about 9:13 pm local time
Place
Van Nuys, California · Van Nuys Airport · map
Type
Accident
Injuries
1 person was killed.
Weather
visual conditions (good weather)
Aircraft
Amateur-built LANCAIR 320 NO SERIES, built 1996
Registration
N7ZL · no longer on the register · serial 137
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

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.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Fuel exhaustion during initial climb defining event
  2. Fuel related during initial climb
  3. Off-field or emergency landing during initial climb
  4. Loss of control in flight during initial climb
  5. Collision with terrain or object (not controlled flight into terrain) during initial climb

The NTSB's findings

  • cause Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Pilot
  • cause Aircraft › Fluids/misc hardware › Fluids › Fuel › Fluid level
  • cause Aircraft › Fluids/misc hardware › Fluids › Fuel › Fluid management
  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Airspeed › Not attained/maintained
  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Angle of attack › Not attained/maintained
  • cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
  • factor Personnel issues › Psychological › Perception/orientation/illusion › Situational awareness › Pilot
  • factor Personnel issues › Action/decision › Info processing/decision › Identification/recognition › Pilot
  • factor Personnel issues › Psychological › Attention/monitoring › Task monitoring/vigilance › Pilot
  • factor Personnel issues › Psychological › Attention/monitoring › Monitoring equip/instruments › Pilot

Pilot

  • Certificate: airline transport pilot, commercial pilot
  • Ratings: multi-engine land; single-engine land; instructor: airplane multi-engine; instructor: airplane single-engine; instructor: helicopter; instructor: instrument airplane; instrument: airplane; instrument: helicopter; rotorcraft: helicopter
  • Flight time: 2,349 hours in all
  • Medical certificate: Class 1 (with waivers/limitations)
  • Seat: unk
  • Injury: fatal

The aircraft

  • Last inspection: inspection type not recorded
  • Maximum gross weight: 4,989 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Lycoming IO-320 SERIES (piston); 0 hours total

The flight

  • Departed from: VNY Van Nuys CA at 9:13 pm
  • Destination: SDL Scottsdale AZ
  • Flight plan: not recorded
  • Runway 16R, 8,001 ft by 150 ft

Weather at the time

  • Light: daylight
  • Wind: from 090° at 5 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 70°F (21°C), dew point 39°F (4°C)
  • Altimeter: 29.96 inHg
  • Observation at 8:51 pm from VNY, 1 miles away

Injuries

FatalSeriousMinorNone
Flight crew1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.