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

Piper PA-32R-300 accident near Peru, West Virginia, October 3, 2011

On October 3, 2011, a Piper PA-32R-300, registered N115CL, was substantially damaged in an accident during enroute (cruise) near Peru, West Virginia. It was a personal flight under general aviation rules (Part 91). 3 people were killed. The weather was instrument conditions (cloud, fog or low visibility).

The NTSB's probable cause their words, unchanged

The non-instrument rated pilot's improper decision to continue visual flight into instrument meteorological conditions, which resulted in spatial disorientation and subsequent in-flight collision with mountainous terrain.

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

What the record shows

Date
October 3, 2011
Place
Peru, West Virginia · map
Type
Accident
Injuries
3 people were killed.
Weather
instrument conditions (cloud, fog or low visibility)
Aircraft
Piper PA-32R-300 · all PA-32R-300s on the register
Registration
N115CL · registry record · serial 32R-7780439
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

The non-instrument-rated pilot, who was also the owner of the airplane, departed on a night visual flight rules (VFR) flight. Weather conditions at the departure airport were VFR, the weather conditions en route were a combination of marginal VFR and instrument flight rules (IFR), and the weather at the destination airport was IFR. The pilot had obtained a weather briefing earlier in the evening, during which he was informed that VFR flight was not recommended. About 30 minutes before the accident, the pilot's in-flight weather briefing indicated that instrument meteorological conditions, including low ceilings and mountain obscuration, were forecast for their intended route and at their destination. About 4 minutes before the accident, the pilot advised air traffic control personnel that "we are losing VFR, I need a deviation." Radio and radar contact were then lost. A postaccident examination of the wreckage indicated that the airplane struck the top of a tree, rolled inverted, and impacted the ground. No preimpact mechanical malfunctions or failures with the airplane that would have precluded normal operation were noted. The only navigational charts found at the accident scene were folded VFR charts and airport facility directories. No IFR charts were found. Analysis of the radar data and wreckage information revealed that the airplane made a series of erratic maneuvers, including a 360-degree heading change, before entering a descent and impacting the ground at high speed. These maneuvers took place in the last few minutes of the flight and were consistent with spatial disorientation. FAA guidance indicates that spatial disorientation can occur when there is no natural horizon or surface reference, such as a night flight in sparsely populated areas similar to that of the accident area and conditions. Although about 34 percent of the moon's disk was potentially illuminated at the time of the accident, given the cloud coverage in the area it is unlikely that the moon provided any illumination over the accident site. FAA guidance also indicates that spatial disorientation is more likely to occur if a pilot lacks proficiency in instrument flying.

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. Preflight or dispatch event during prior to flight
  2. VFR encounter with IMC during enroute (cruise) defining event
  3. Collision with terrain or object (not controlled flight into terrain) during uncontrolled descent

The NTSB's findings

  • cause Personnel issues › Psychological › Perception/orientation/illusio › Spatial disorientation › Pilot
  • cause Environmental issues › Conditions/weather/phenomena › Ceiling/visibility/precip › Below VFR minima › Decision related to condition
  • Personnel issues › Task performance › Planning/preparation › Weather planning › Pilot
  • Environmental issues › Physical environment › Terrain › Mountainous/hilly terrain › Not specified

Pilot

  • Certificate: private
  • Ratings: single-engine land
  • Flight time: 111 hours in all; 40 in this make and model
  • Last flight review: August 31, 2011
  • Medical certificate: Class 3 (with waivers/limitations)
  • Seat: left
  • Injury: fatal

The aircraft

  • Airframe total time: 4,541.1 hours
  • Last inspection: annual inspection, March 2, 2011
  • Maximum gross weight: 3,600 lb
  • Seats: 6
  • Landing gear: retractable
  • Engine: Lycoming IO-540-K1G5D (piston); 0 hours total

The flight

  • Departed from: DAN Danville VA at 11:30 pm
  • Destination: JST Johnstown PA
  • Flight plan: none

Weather at the time

  • Light: night, dark
  • Visibility: 10 statute miles
  • Sky: broken clouds at 3,600 ft
  • Temperature: 46°F (8°C), dew point 43°F (6°C)
  • Altimeter: 29.96 inHg

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers2

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.