ERA20FA063 · Vans VANS RV-6 Undesignat
Vans VANS RV-6 Undesignat · Accident: fuel exhaustion during initial climb
From Cullman Regional Airport-Folsom Field (CMD) to Cullman Regional Airport-Folsom Field (CMD)
Event
- NTSB case
- ERA20FA063
- 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
Vans VANS RV-6 Undesignat
- Aircraft type
- Vans RV-6
- 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
- N420PW
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Cullman Regional Airport-Folsom Field (CMD), Cullman, ALTo Cullman Regional Airport-Folsom Field (CMD), Cullman, AL
- Aircraft age
- About 6 years (built 2014)
- 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
- Initial climb
- 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
- Fuel exhaustion
- 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
- Aircraft › Fluids/miscellaneous hardware
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
Witnesses reported that, during the airplane’s initial climb, when it reached about 350 ft above the ground, they heard loud “pop” and a loss of engine power. The witnesses watched as the airplane entered an immediate “sharp left banking turn” in what appeared to be an attempt to return to the airport. The airplane “stalled and went into a left spiral downward turn.” The airplane completed two turns before impacting the ground on airport property adjacent to the taxiway. The position of the airplane’s fuel selector as found would have supplied fuel to the engine from the left fuel tank; however, both of the airplane’s fuel tanks were breached during the accident and no evidence of fuel was found in either. There was no post-crash fire and there was no residual fuel noted at the accident site. The traces of fuel that were recovered from the airplane’s fuel system were absent of water. Otherwise, no evidence of preimpact mechanical failure or malfunction was noted during the examination of the recovered airframe and engine. The airplane’s recent fueling and flight history could not be definitively determined from available evidence other than that the airplane had last been fueled at the accident airport just over 1 month before the accident, and that the pilot had flown it on at least one trip in the intervening time. Toxicology testing performed on the pilot identified cocaine in urine, but there was no evidence that any active cocaine remained in the pilot’s body. THC, the primary psychoactive component of cannabis, was not found; however, its active metabolite was in urine at very low levels. Therefore, the pilot was not directly impaired by his drug use at the time of the accident; whether he was feeling any effects from withdrawal could not be determined. Overall, it is unlikely that the pilot’s drug use contributed to the circumstances of this accident. Based on the available information, the circumstances of the accident are consistent with a loss of engine power due to fuel exhaustion, and the pilot’s subsequent exceedance of the airplane’s critical angle of attack during an attempted return to the runway, which resulted in an aerodynamic stall/spin.
Probable cause
The pilot’s inadequate planning, which resulted in fuel exhaustion and a total loss of engine power during the initial climb. Also causal was the pilot’s exceedance of the airplane’s critical angle of attack while attempting to return to the runway after takeoff, which resulted in an aerodynamic stall/spin, loss of control, and impact with terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA20FA063
- Event ID
- 20200105X53312
- Case number
- ERA20FA063
- 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: 763b86733c0a8e4cd1ce7e67da26af52fe7a69e1b274f860eebd3bb35d6a8926; retrieved 2026-09-15T07:10:14.234Z.