FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA20LA312 · Quad City CHALLENGER II

10 Sept 2020 · Sweetwater, TN, United States

Quad City CHALLENGER II · Accident: loss of control in flight during initial climb

Report a problem

Event

NTSB case
ERA20LA312
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
Visual Meteorological Cond

Quad City CHALLENGER II

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
N56906
Operator
Unknown
Onboard fatalities
Unknown
Route
From not recordedTo not recorded
Aircraft age
About 16 years (built 2004)
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
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
Substantial

Cause areas

  • Not determined › Not determined
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

Despite being told by the airplane owner that he could taxi, but not fly, the airplane, the pilot conducted a high-speed taxi and took off. About 250 to 300 ft above ground level, the airplane suddenly nosed over. The owner, who witnessed the takeoff, stated that the engine was not seized, and the propeller was still spinning when the airplane disappeared behind trees. Examination revealed no anomalies with the airframe or engine that would have precluded normal operation, and damage signatures and witness accounts indicated that the engine was producing power at the time of the accident. Toxicology testing detected THC-COOH, the inactive metabolite of THC, in the pilot’s liver and lung tissue. Gabapentin, promethazine, norchlorcyclizine, duloxetine, citalopram, its metabolite n-desmethylcitalopram, and trazodone were detected in the pilot’s liver tissue; except for trazodone, these compounds were also detected in the pilot’s muscle tissue. Since only the inactive metabolite of THC was detected, it is unlikely that the effects from the pilot’s use of cannabis were a factor in this accident. Autopsy findings did not show evidence of any potentially sudden incapacitating event. Thus, it is unlikely that the pilot’s medical conditions or his use of detected prescription medications contributed to the accident. Although the circumstances of the accident are consistent with a loss of control, the reason for the loss of control could not be determined based on the available information.

Probable cause

A loss of control for reasons that could not be determined based on the available information.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA20LA312
Event ID
20200910X75243
Case number
ERA20LA312
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: 42202be3fc60ecec5c24c7e3c2af89c126895053b394dc4ead33b5b27e028a70; retrieved 2026-09-15T07:19:33.551Z.