CHI06LA243 · Frick Questair Q20
Frick Questair Q20 · Accident: loss of engine power en route
From Fairfield County Airport (FDW) to Frankfort Dow Memorial Field (FKS)
Narrative check · The NTSB narrative appears to contradict this record's location. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- CHI06LA243
- 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
Frick Questair Q20
- Aircraft type
- Frick QUESTAIR Q20
- 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
- N2QV
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Fairfield County Airport (FDW), Winnsboro, SCTo Frankfort Dow Memorial Field (FKS), Frankfort, MI
- Aircraft age
- Not recorded
- 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
- First occurrenceThe 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 engine power
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Fuel exhaustion; Tree(s)
- 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
- Fluid, fuel › Exhaustion
- Pilot in command › Fuel supply, inadequate
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The airplane impacted trees and the ground during a forced landing following a loss of engine power during cruise flight. The flight was operating on an instrument flight rules flight plan. The pilot reported the loss of engine power to air traffic control and was attempting to divert when the accident occurred. Examination of the airplane following the accident revealed no mechanical anomalies. No fuel or evidence of a fuel spill was found at the accident site.
Probable cause
The pilot's failure to ensure an adequate fuel supply, which resulted in the exhaustion of the fuel supply and the subsequent loss of engine power. The trees that the airplane struck during the forced landing were a factor.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI06LA243
- Event ID
- 20060901X01276
- Case number
- CHI06LA243
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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, coordinates. 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: 976f0233998f1de6b8be1037920aa37744c1b2bc18ec3fe9f752c5ddb9158cda; retrieved 2026-09-20T17:05:01.966Z.