Piper PA20 accident near Luray, Virginia, August 31, 2020
On August 31, 2020 at about 11:00 pm local time, a 1950 Piper PA20, registered N7323K, was destroyed in an accident during enroute (cruise) near Luray, Virginia. It was a personal flight under general aviation rules (Part 91). 1 person was killed. The weather was instrument conditions (cloud, fog or low visibility).
The NTSB's probable cause their words, unchanged
The noninstrument-rated pilot’s continued visual flight into instrument meteorological conditions, which resulted in spatial disorientation, a loss of control, and collision with terrain.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- August 31, 2020 · about 11:00 pm local time
- Place
- Luray, Virginia · map
- Type
- Accident
- Injuries
- 1 person was killed.
- Weather
- instrument conditions (cloud, fog or low visibility)
- Aircraft
- Piper PA20 135, built 1950 · all PA20s on the register
- Registration
- N7323K · no longer on the register · serial 20-268
- Damage
- Destroyed
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
Throughout the afternoon of the accident flight, the noninstrument-rated pilot had delayed his departure due to poor weather along his intended route, and despite any meaningful change in the weather conditions along the route or at the presumed destination, he decided to depart. Data obtained from the pilot’s electronic flight bag (EFB) application, in addition to a course change in the airplane’s recorded flight track, indicated that, about 20 minutes into the flight, the pilot initiated a diversion to a new airport. Although the new airport was reporting visual flight rules (VFR) conditions, instrument flight rules (IFR) conditions and mountain obscuration were present along the route of flight. Each of these conditions were forecast before the pilot’s departure. Review of the weather conditions along the route indicated that the pilot passed airports with VFR conditions but chose to continue into an area of deteriorating visibility and cloud ceilings. As the pilot approached rising terrain toward the new destination, the flight track deviated to the left and right, followed by a left 360° level turn. The 360° turn was completed in about 1 minute. The airplane then continued in a second left turn, during which its altitude began to rapidly decrease, and the turn developed into a descending spiral. The final position was recorded with the airplane about 500 ft above terrain about ¼ mile east of the accident site. The airplane’s flight track was consistent with the known effects of spatial disorientation and a subsequent loss of control and impact with terrain. The wreckage was located 40 hours after the accident in heavily wooded terrain at the bottom of a steep ravine. The fragmentation of the wreckage indicated that the airplane impacted terrain in a high speed, uncontrolled descent. A postaccident examination of the airplane did not reveal any evidence of mechanical malfunctions. The pilot did not file a flight plan, obtain an official weather briefing, nor was he receiving air traffic control services at the time of the accident. It is likely that the pilot encountered instrument meteorological conditions (IMC), which included rain, clouds, and low visibility, as he neared the rising terrain and continued flight into IMC. The pilot did not possess the qualifications to operate in IMC, and the airplane was not equipped for IFR flight. The investigation found evidence that the pilot likely relied extensively on an EFB application for GPS navigation. Photos from the pilot’s past flights showed that he had mounted the EFB in the forward windscreen area and data retrieval from the EFB application found that the pilot was actively utilizing the EFB while enroute in the accident flight. It is possible that the pilot was utilizing the application’s attitude indicator/synthetic vision feature as he entered IMC. The EFB application pilot’s guide stated that the attitude indicator/synthetic vision feature may only be used for informational purposes and cannot be used as a primary reference.
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
- VFR encounter with IMC during enroute (cruise) defining event
- Loss of control in flight during enroute (cruise)
- Collision with terrain or object (not controlled flight into terrain) during enroute (cruise)
The NTSB's findings
- Personnel issues › Experience/knowledge › Experience/qualifications › Qualification/certification › Pilot
- Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Pilot
- Personnel issues › Psychological › Perception/orientation/illusion › Spatial disorientation › Pilot
- Personnel issues › Task performance › Planning/preparation › Weather planning › Pilot
Pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 200 hours in all
- Last flight review: February 8, 2020
- Medical certificate: Class 2 (without waivers/limitations)
- Seat: left
- Injury: fatal
The aircraft
- Airframe total time: 1,945 hours
- Last inspection: annual inspection, July 3, 2020; 126 hours since
- Maximum gross weight: 1,800 lb
- Seats: 4
- Landing gear: fixed
- Engine: Lycoming O-290-D (piston); 2,085 hours total
The flight
- Departed from: 2W5 Indian Head MD at 10:19 pm
- Destination: W99 Petersburg WV
- Flight plan: none
Weather at the time
- Light: daylight
- Wind: from 360° at 4 knots
- Visibility: 7 statute miles
- Sky: overcast at 2,300 ft
- Temperature: 66°F (19°C), dew point 66°F (19°C)
- Altimeter: 30.01 inHg
- Observation at 10:55 pm from LUA, 9 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
19 documents, released by the NTSB on June 23, 2022. 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.
