ERA20FA002 · Piper PA28 180
Piper PA28 180 · Accident: loss of control in flight while maneuvering
From Knoxville Downtown Island Airport (DKX) to Asheboro Regional Airport (HBI)
Event
- NTSB case
- ERA20FA002
- 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
- 2 · 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
- Visual Meteorological Cond
Piper PA28 180
- Aircraft type
- Piper PA28
- 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
- N2FB
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Knoxville Downtown Island Airport (DKX), Knoxville, TNTo Asheboro Regional Airport (HBI), Asheboro, NC
- Aircraft age
- About 53 years (built 1966)
- 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
- Maneuvering
- 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
- Loss of control in flight
- 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
- Aircraft › Aircraft oper/perf/capability
- Environmental issues › Conditions/weather/phenomena
- Personnel issues › Experience/knowledge
- Personnel issues › Psychological
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The private pilot and a student pilot passenger were returning to their home airport in dark night visual meteorological conditions. The pilot reported on the airport’s common traffic advisory frequency that he intended to overfly the runway from west to east and turn left onto the downwind leg of the airport traffic pattern for a landing to the southwest. Instead, the airplane turned right after crossing the airport and proceeded south. Radar data revealed that the airplane completed a right 360° turn about 2 miles south of the airport, where witnesses saw the airplane circling over a local high school football game. Witnesses reported that the airplane then entered a steep, nose-down descent and the engine continued to run at high speed during the descent. The last radar target was over the area of the accident site. The accident site was located in a rural, wooded area, and fragmentation of the wreckage at the site was consistent with a high-energy impact. Examination of the airframe and engine did not reveal evidence of a preimpact mechanical malfunction or anomaly.
Another pilot, who flew the accident airplane earlier on the day of the accident, reported that the vacuum pump was inoperative and that the vacuum instruments were unreliable and would drift during flight. Due to extensive impact damage to the flight instruments and vacuum system, the condition of the flight instruments and whether they may have contributed to the accident could not be determined. An unidentified instrument gyro exhibited signs of rotation at impact.
The pilot, who owned the airplane, did not have a current flight review, and his most recent night flight experience was recorded over 10 years before the accident. The dark night conditions present at the time of the accident and the pilot’s lack of recent night flying experience were conducive to the development of spatial disorientation, and the airplane’s high-speed impact was consistent with the known effects of spatial disorientation.
Toxicology testing of the pilot revealed the primary psychoactive metabolite of marijuana only in liver tissue and its inactive metabolite in liver and kidney tissue samples. While tissue analysis cannot be used to determine recent usage and possible effects, the concentrations suggested that the pilot was not a chronic user; the distribution of metabolites also suggested that his marijuana use was not very recent. Given the known circumstances of the accident, it is unlikely that the pilot’s use of marijuana contributed to the accident. Toxicology also identified the presence of ethanol in tissue samples from both the pilot and passenger; however, it is likely that some or all of the identified ethanol was the result of postmortem production.
Based on the available information, it is likely that, while maneuvering over sparsely populated terrain in dark night conditions, the pilot experienced spatial disorientation, which resulted in a subsequent loss of airplane control.
Probable cause
The pilot’s loss of airplane control due to spatial disorientation, which resulted in a collision with terrain. Contributing to the accident was the pilot’s lack of recent night flight experience.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA20FA002
- Event ID
- 20191005X13313
- Case number
- ERA20FA002
- 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: local date, investigation status, cause areas. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2019-10-05.
- API snapshot SHA-256: 69b8210976a3fbccff6a5dbd99a058c5666680612f41b7440a8d50bfe7e3dca5; retrieved 2026-09-15T07:06:25.352Z.