Piper PA20 N7323K
31 August 2020 · Luray, Virginia, United States · Fatal
Summary
On 31 August 2020 at about 23:00 local time, a Piper PA20 registered N7323K was involved in an accident near Luray, Virginia, United States. One person was on board and one died. The aircraft was destroyed. The NTSB has published a probable cause for this accident; it is quoted in full below.
The record
- Date
- at 23:00
- Classification
- Accident
- Location
- Luray, Virginia, United States
- Coordinates
- 38.6404, -78.3072
- Aircraft
- Piper PA20
- Registration
- N7323K
- Category
- Airplane
- Year built
- 1950
- Engines
- 1
- Operator
- Not recorded
- Operating rule
- Part 91: General Aviation
- Purpose of flight
- Personal
- Phase of flight
- Not recorded
- Route
- Indian Head → Petersburg
- Aircraft damage
- Destroyed
- Weather
- IMC
- Light
- Day
- NTSB number
- ERA20LA305
People
1 person died.
| On board | Died | Serious | Minor | Uninjured |
|---|---|---|---|---|
| 1 | 1 | 0 | 0 | 0 |
Probable cause
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.
Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.
Read the full NTSB narrative
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.
Quoted verbatim from the NTSB record.
Other Piper PA20 accidents
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 27 Jun 2022 | Piper PA20 | Challis, Idaho, United States | - | Fatal | 2 |
| 18 Jun 2026 | Piper PA20 | Cordova, Alaska, United States | Micael Grimes | Fatal | 1 |
| 3 Aug 2014 | Piper PA20-UNDESIGNAT | Dayton, Oregon, United States | Graham L Goad | No injuries | - |
| 2 Jan 2026 | Piper PA20 | Bloemfontein, South Africa | - | Fatal | 1 |
| 9 Apr 2009 | Piper PA20 | Scranton, Pennsylvania, United States | Thomas John Malinchak | No injuries | - |
| 9 Jan 1965 | Piper PA20 | San Carlos Calif, California, United States | - | Fatal | 3 |
Other accidents in this area
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 30 Dec 2020 | Taylorcraft BC12 | Topping, Virginia, United States | - | No injuries | - |
| 1 Oct 2020 | Fokker DR1 | Wake, Virginia, United States | Forgotten Heroes Foundation | No injuries | - |
| 1 Jul 2020 | Cessna 172 | Chesapeake, Virginia, United States | Epix Services LLC | No injuries | - |
| 11 May 2020 | Schempp Hirth VENTUS 2CT | Stuarts Draft, Virginia, United States | - | Minor injuries | - |
| 28 Aug 2020 | Tecnam P92 | Charlottesville, Virginia, United States | Heart of Virginia Aviation Inc | No injuries | - |
| 10 Jul 2020 | Piper PA22 | Culpeper, Virginia, United States | Richard S. Simpson | No injuries | - |