eFlight
Accidents · NTSB WPR11FA248 · Final report

Piper PA-24-250 accident near Astoria, Oregon, June 5, 2011

On June 5, 2011, a Piper PA-24-250, registered N511FS, was substantially damaged in an accident during approach (VFR pattern base) near Astoria, Oregon (Astoria Regional airport). It was an instructional 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 student pilot’s failure to maintain adequate airspeed while maneuvering for landing, which resulted in a stall/spin. Contributing to the accident were the pilot's distraction and anxiety from a reported failure of the airplane's electrical system.

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

What the record shows

Date
June 5, 2011 · cases in 2011
Place
Astoria, Oregon · Astoria Regional · cases near this airport · map
Type
Accident
Injuries
1 person was killed.
Weather
visual conditions (good weather)
Aircraft
Piper PA-24-250 · all PA-24-250s on the register
Registration
N511FS · no longer on the register · serial 24-1483
Damage
Substantial damage
Flight
Instructional flight · general aviation rules (Part 91)

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

According to the flight instructor, the student pilot called him while en route during a solo cross-country instructional flight and reported observing an electric current discharge of 10 amperes on the amp meter. The pilot also reported hearing a pulsating tone on the radio. During a subsequent call to the instructor, the student reportedly stated that the airplane had experienced a total electrical failure. The instructor said that he advised the student to immediately extend the airplane's electrically activated landing gear while the airplane still had remaining battery power. During the next hour, the student called his instructor four additional times and a pilot acquaintance three times. Both the instructor and the acquaintance reported that the student sounded extremely disturbed and anxious about the ongoing situation during these calls. The instructor was located at the home airport when the student flew overhead between about 800 and 1,000 feet above the ground, and he observed that the airplane's landing gear appeared to be extended only halfway. He advised the student to climb to 3,000 feet, and he then instructed the student in detail on how to extend the landing gear using the emergency extension procedure. The instructor estimated that the student flew in the vicinity for about 45 minutes until he stated, “I’ve got it,” which he thought meant that the gear was down and that the student intended to land. The instructor then lost track of the airplane as it flew away from his line of sight. Minutes later, he heard emergency vehicle sirens in the distance. A witness observed the airplane rapidly descending until his view of it was obscured by intervening terrain or vegetation as it approached ground level. The witness said that the airplane was descending with its nose pointed nearly straight down and that it was turning (rolling about its longitudinal axis). He reported that no fire or smoke was trailing from the airplane. The wreckage signatures and ground scar evidence were consistent with a stall-spin type accident sequence and an impact with the ground at a 45-degree nose-down angle. The landing gear was found in the down-and-locked position. No preimpact mechanical malfunctions or failures were found with the airplane control systems or engine that would have precluded normal operation. The electrical generating and storage components were removed for examinations and tests. Impact damage precluded functional tests of the alternator, over voltage relay, and spike guard capacitor; however, the units passed electrical continuity checks. An output wire on the alternator was found half severed, with the ends of the strands oxidized, indicating a preexisting condition. However, the electrical component examinations could not determine the failure mode of the charging system. It is likely that the student pilot remained distracted by the reported failure of the electrical power system and failed to maintain airspeed while preparing for landing, which resulted in the subsequent stall/spin to ground impact.

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. Electrical system malf/failure during enroute (cruise)
  2. Loss of control in flight during approach (VFR pattern base) defining event
  3. Aerodynamic stall/spin during approach (VFR pattern base)
  4. Collision with terrain or object (not controlled flight into terrain) during uncontrolled descent

The NTSB's findings

  • factor Personnel issues › Psychological › Mental/emotional state › Anxiety/panic › Student pilot
  • cause Personnel issues › Action/decision › Action › Incorrect action performance › Student pilot
  • cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Student pilot
  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Airspeed › Not attained/maintained
  • factor Personnel issues › Psychological › Attention/monitoring › Task monitoring/vigilance › Student pilot
  • factor Aircraft › Aircraft systems › Electrical power system › AC regulator › Not specified other cases naming the electrical power

Dual student

  • Certificate: student
  • Flight time: 113 hours in all; 67 in this make and model; 25 in the last 90 days; 15 in the last 30 days; 71 as pilot in command
  • Medical certificate: Class 3
  • Seat: left
  • Injury: fatal

The aircraft

  • Airframe total time: 5,967 hours
  • Last inspection: annual inspection, June 3, 2011; 7 hours since
  • Maximum gross weight: 3,000 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Lycoming O-540-A1C5 (piston); 0 hours total

The flight

  • Departed from: S10 Chelan WA
  • Destination: AST Astoria OR
  • Flight plan: none
  • Runway 31, 4,996 ft by 100 ft

Weather at the time

  • Light: daylight
  • Wind: from 320° at 15 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 72°F (22°C), dew point 50°F (10°C)
  • Altimeter: 29.87 inHg

Injuries

FatalSeriousMinorNone
Flight crew1

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

19 documents, released by the NTSB on April 30, 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/WPR11FA248.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.