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

Bellanca 17-30A accident near Carson City, Nevada, March 1, 2017

On March 1, 2017 at about 8:50 pm local time, a 1973 Bellanca 17-30A, registered N39894, was substantially damaged in an accident during initial climb near Carson City, Nevada (Carson Airport). It was a personal flight under general aviation rules (Part 91). 1 person was seriously injured. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

A total loss of engine power due to internal corrosion of the fuel manifold valve. Also causal was the pilot's decision to return to the runway following the loss of engine power shortly after takeoff, and his exceedance of the airplane's critical angle of attack during the turn, which resulted in an aerodynamic stall.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
March 1, 2017 · about 8:50 pm local time
Place
Carson City, Nevada · Carson Airport · map
Type
Accident
Injuries
1 person was seriously injured.
Weather
visual conditions (good weather)
Aircraft
Bellanca 17-30A, built 1973 · all 17-30As on the register
Registration
N39894 · no longer on the register · serial 73-30544
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

The airline transport pilot was conducting the airplane's first flight after about 1 1/2 years of inactivity and the completion of an annual inspection. A witness reported that the airplane took off normally, but the retractable landing gear remained extended. As the airplane neared the end of the runway, about 300 ft above ground level, the engine sounded as though it "decreased to idle." The airplane entered a right, 180o turn and descended rapidly before impacting the ground. During a postaccident test run, the engine operated normally at both idle and full power settings and during abrupt changes between idle and full power. However, it operated inconsistently at 2,100 rpm for about 30 seconds before stabilizing at that power setting. During this time, the fuel pump pressure fluctuated. Following the test run, the fuel manifold valve was disassembled, revealing rust on the screen, lower housing, and plunger, consistent with exposure to water. The diaphragm was removed and a small amount of fuel was found on the "dry" side of the valve; the vent extending from this section was examined and clear of debris. Examination of the airframe and engine maintenance logs revealed that the airplane flew a total of 73 hours and underwent 3 annual inspections in the previous 8 years. It is likely that water accumulated in the fuel system sometime during the airplane's prolonged periods of disuse, resulting in corrosion of the fuel manifold valve's internal components. Because the corrosion was internal, it would not have been detected without disassembly of the fuel manifold, which is not part of the annual inspection procedure. It is likely that this corrosion caused the manifold valve plunger to temporarily stick, which restricted fuel flow to the engine and resulted in the anomalous operation during the postaccident test run as well as the loss of power on the accident flight. Following the loss of engine power, the pilot initiated a turn back to the runway, during which the airplane exceeded its critical angle of attack and experienced an aerodynamic stall.

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 related during initial climb defining event
  2. Loss of engine power (total) during initial climb
  3. Off-field or emergency landing during initial climb
  4. Aerodynamic stall/spin during landing
  5. Collision with terrain or object (not controlled flight into terrain) during landing

The NTSB's findings

  • cause Aircraft › Aircraft systems › Fuel system › Fuel distribution › Fatigue/wear/corrosion
  • cause Aircraft › Aircraft systems › Fuel system › Fuel distribution › Malfunction
  • cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot

Pilot

  • Certificate: airline transport pilot, flight engineer
  • Ratings: multi-engine land; multi-engine sea; single-engine land; single-engine sea; instrument: airplane; rotorcraft: glider
  • Flight time: 22,000 hours in all
  • Medical certificate: Class 1 (without waivers/limitations)
  • Seat: left
  • Injury: serious injuries

The aircraft

  • Airframe total time: 3,394 hours
  • Last inspection: annual inspection, February 24, 2017; 1 hours since
  • Seats: 4
  • Landing gear: fixed
  • Engine: Cont Motor IO 520 SERIES (piston); 3,394 hours total

The flight

  • Departed from: CXP Carson City NV at 8:50 pm
  • Destination: CXP Carson City NV
  • Flight plan: none
  • Runway 9, 6,100 ft by 75 ft

Weather at the time

  • Light: daylight
  • Wind: from 100° at 4 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 45°F (7°C), dew point 16°F (-9°C)
  • Altimeter: 30.40 inHg
  • Observation at 8:55 pm from CXP

Injuries

FatalSeriousMinorNone
Flight crew1

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

9 documents, released by the NTSB on October 30, 2017. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

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.