ERA20LA305 · Piper PA20 135
Piper PA20 135 · Accident: VFR encounter with IMC en route
From Maryland Airport (2W5) to Grant County Airport (W99)
Event
- NTSB case
- ERA20LA305
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 1 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Instrument Meteorological Cond
Piper PA20 135
- Aircraft type
- Piper PA20
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N7323K
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Maryland Airport (2W5), Indian Head, MDTo Grant County Airport (W99), Petersburg, WV
- Aircraft age
- About 70 years (built 1950)
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- En route · cruise
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- VFR encounter with IMC
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Personnel issues › Action/decision
- Personnel issues › Experience/knowledge
- Personnel issues › Psychological
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
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.
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.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA20LA305
- Event ID
- 20200902X44047
- Case number
- ERA20LA305
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status, cause areas. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 085445ae9a2a6419cad532a22c0dd9cfdae0289fb58f75181344a89ed0a83ca8; retrieved 2026-09-15T07:19:09.804Z.