eFlight
Accidents · NTSB WPR18LA194 · Final report

Piper PA32 accident near Salisbury, North Carolina, June 29, 2018

On June 29, 2018 at about 8:03 pm local time, a 1976 Piper PA32, registered N8440F, was substantially damaged in an accident during enroute (cruise) near Salisbury, North Carolina (Rowan County airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 3 people were on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

A total loss of engine power due to fuel starvation for reasons that could not be determined based on the available information.

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

What the record shows

Date
June 29, 2018 · about 8:03 pm local time · cases in 2018
Place
Salisbury, North Carolina · Rowan County · cases near this airport · map
Type
Accident
Injuries
No one was hurt; 3 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft
Piper PA32 300, built 1976 · all PA32s on the register
Registration
N8440F · registry record · serial 32-7740023
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

The pilot departed with his passengers on a cross-country flight with the main and auxiliary fuel tanks at full capacity. About 2 hours and 18 minutes into the flight, the engine lost total power. The pilot was unable to restart the engine and declared an emergency. The controller provided vectors to a nearby airport, where the airplane landed hard, resulting in substantial damage. First responders reported that they drained about 55 gallons of fuel from the airplane after the accident and an additional, unquantified amount spilled onto the ground; however, the fuel was drained before the airplane could be examined and the amount of fuel onboard and its distribution at the time of the accident could not be confirmed. Data retrieved from an onboard engine monitoring system showed erratic fuel flow indications concurrent with a sudden decrease in exhaust gas temperatures. These erratic fuel flow indications suggest the possibility that the transducer was pulling in air due to an interruption in fuel flow, which may have been the result of fuel starvation or an introduction of air within the fuel system upstream of the transducer. The fuel lines were not tested, as they had been cut by recovery personnel. A postaccident examination of the engine revealed no fuel in the line between the engine-driven fuel pump and the fuel servo, which typically captures and retains unused fuel destined for the engine. A subsequent engine run revealed no anomalies of the engine. Given the available information, it is likely that the loss of engine power was the result of fuel starvation; however, whether the fuel starvation was the result of fuel mismanagement or an introduction of air into the fuel system could not be determined.

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 enroute (cruise) defining event
  2. Loss of engine power (total) during enroute (cruise)
  3. Collision with terrain or object (not controlled flight into terrain) during landing

The NTSB's findings

  • cause Aircraft › Fluids/misc hardware › Fluids › Fuel › Not specified other cases naming the fuel system
  • cause Aircraft › Aircraft power plant › Engine (reciprocating) › (general) › Failure other cases naming the engine
  • cause Not determined › Not determined › (general) › (general) › Unknown/Not determined

Pilot

  • Certificate: private
  • Ratings: single-engine land
  • Flight time: 457 hours in all; 38 in this make and model; 4 in the last 90 days; 4 in the last 30 days; 391 as pilot in command
  • Last flight review: September 12, 2017
  • Medical certificate: Class 3 (with waivers/limitations)
  • Seat: left
  • Injury: no injuries

Passenger

  • Seat: left
  • Injury: no injuries

Passenger

  • Seat: rgt
  • Injury: no injuries

The aircraft

  • Airframe total time: 3,661.7 hours
  • Last inspection: annual inspection, September 16, 2017; 81 hours since
  • Maximum gross weight: 3,400 lb
  • Seats: 6
  • Landing gear: fixed
  • Engine: Lycoming IO-540-KIG5 (piston); 3,661 hours total
  • Operator: Skyhigh Flyers Flying Club, Inc.

The flight

  • Departed from: KSBY Salisbury MD at 5:50 pm
  • Destination: 14A Lake Norman NC
  • Flight plan: VFR

Weather at the time

  • Light: daylight
  • Visibility: 10 statute miles
  • Sky: broken clouds at 7,000 ft; scat at 6,000 ft
  • Temperature: 90°F (32°C), dew point 66°F (19°C)
  • Observation at 8:15 pm from KRUQ, 3 miles away

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers2

Photographs from the investigation 3 pictures from the NTSB's docket, as the NTSB released them

The NTSB's photographs with the NTSB's captions, at screen size. Open a picture to see it full size or to report one that should not be shown.

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

11 documents, released by the NTSB on March 17, 2021. 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.

Connections how this case links to the rest of the register

Aircraft
Place

The whole map of how records connect · these connections as data: /graph/accident/WPR18LA194.json.

The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.

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 does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.

Aircraft

By kindModelsMakersEnginesFleetsWhat changed

Fly

Plan a flightAirportsLive mapRoutes and flightsFuels

Training and work

TrainingFlight schoolsGround schoolsPilot examinersMedical examinersJobs

Companies

DirectoryCharter operatorsFBOsRepair stationsClaim your listing

Safety and data

AccidentsRecords checkAnalyticsSAFxCHANGEThe graphAbout

Colours follow your device's light or dark setting.