eFlight
Accidents · NTSB WPR13LA011 · Final report

Cirrus Design CORP SR20 accident near Parker, Arizona, October 15, 2012

On October 15, 2012 at about 6:31 pm local time, a 2005 Cirrus Design CORP SR20, registered N499SF, was substantially damaged in an accident during enroute (cruise) near Parker, Arizona (Parker airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 2 people were on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot's failure to perform an adequate preflight inspection, which resulted in inadequate fuel for the flight and the subsequent fuel exhaustion and a total loss of engine power. Contributing to the accident was the pilot's failure to land the airplane at the first indication of low fuel.

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

What the record shows

Date
October 15, 2012 · about 6:31 pm local time · cases in 2012
Place
Parker, Arizona · Parker · cases near this airport · map
Type
Accident
Injuries
No one was hurt; 2 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft
Cirrus Design CORP SR20, built 2005
Registration
N499SF · no longer on the register · serial 1540
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

Prior to the first flight of the day, the pilot visually established the fuel quantity through the filler necks, observing what he believed to be full tanks. He subsequently checked the fuel gauges, which indicated that the wing tanks were each under half full. Surmising that the gauges were faulty, he departed on a short flight to a local airport to collect a passenger. After picking up the passenger, they departed for a cross-country flight. He did not service the airplane with fuel prior to departure, and after travelling for about 90 minutes the airplane ran out of fuel. Examination of recorded data recovered from the airplane's flight displays revealed that its fuel consumption was appropriate for the flight profile. Subsequent examination of the airframe revealed that both fuel tanks were empty, and neither the engine nor airframe exhibited indications of a fuel leak. The data further revealed that the airplane was approaching an airport as one of the tanks ran dry. The engine lost power; however, rather than landing, the pilot continued the flight after switching to the other tank. The other tank ran dry a short time later, and he performed a forced landing into a rocky outcropping, where the airplane sustained substantial damage.

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

The NTSB's findings

  • cause Aircraft › Fluids/misc hardware › Fluids › Fuel › Fluid level other cases naming the fuel system
  • cause Personnel issues › Task performance › Inspection › Preflight inspection › Pilot
  • factor Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Pilot

Pilot

  • Certificate: private
  • Ratings: single-engine land; instrument: airplane
  • Flight time: 2,480 hours in all; 50 in this make and model; 11 in the last 90 days; 8.5 in the last 30 days
  • Last flight review: May 29, 2012
  • Medical certificate: Class 3 (with waivers/limitations)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Airframe total time: 1,714 hours
  • Last inspection: 100-hour inspection, October 10, 2012; 2 hours since
  • Maximum gross weight: 3,050 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Cont Motor IO-360 SER (piston); 0 hours total

The flight

  • Departed from: KSNA Santa Ana CA at 4:59 pm
  • Destination: KPRC Prescott AZ
  • Flight plan: none

Weather at the time

  • Light: daylight
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 81°F (27°C), dew point 43°F (6°C)
  • Altimeter: 29.95 inHg
  • Observation at 4:52 pm from KBLH, 39 miles away

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers1

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

9 documents, released by the NTSB on November 13, 2013. 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/WPR13LA011.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.