ATL88DMG02 · Questair 20
Questair 20 · Accident: total loss of engine power (non-mechanical) during initial climb
From Piedmont Triad International Airport (GSO) to an unrecorded destination
Event
- NTSB case
- ATL88DMG02
- 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
- 0 · all aircraft and ground
- Ground fatalities
- 0
- 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
Questair 20
- Aircraft type
- Questair 20
- 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
- N62V
- Operator
- Questair
- Onboard fatalities
- Unknown
- Route
- From Piedmont Triad International Airport (GSO), Greensboro, NCTo not recorded
- 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
- Initial climb
- 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
- Total loss of engine power (non-mechanical)
- 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 starvation
- 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 › Starvation
- Fuel system, selector/valve › Closed
- Pilot in command › Fuel tank selector position, improper
- Pilot in command › Preflight planning/preparation, inadequate
Approximate · Estimated position: the centre of Greensboro, NC, the place the record names. Not the accident site.
NTSB narrative
SHORTLY AFTER TAKE-OFF, AT ABOUT 500 FT AGL, THE ENGINE QUIT AND THE PILOT ATTEMPTED TO RETURN TO THE AIRPORT AND LAND. THE AIRCRAFT CRASHED AND CAUGHT FIRE. THE FUEL SYSTEM WAS FOUND TO HAVE THREE FUEL SELECTORS INSTALLED. THE MAIN FUEL SELECTOR, WHICH SUPPLIES FUEL TO THE ENGINE, WAS IN THE 'ON' POSITION. THE TWO FUEL SELECTORS FROM BOTH THE RT AND LEFT FUEL CELLS WERE FOUND IN THE 'OFF' POSITIONS. THESE TWO FUEL SELECTORS MUST BE IN THE 'ON' POSITION TO SUPPLY FUEL TO THE MAIN FUEL SELECTOR. THE ACFT WAS EQUIPPED WITH A HEADER TANK WHICH HAS A CAPACITY OF APPROXIMATELY ONE HALF GALLON. THE ENGINE WAS RECOVERED AND SUCCESSFULLY RUN ON A TEST STAND.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record ATL88DMG02
- Event ID
- 20001213X32241
- Case number
- ATL88DMG02
- 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. 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: d4555fd22a80ff9a8ed06ea6fa1ae01306642440f3adab673a70c784be7f7b9f; retrieved 2026-09-22T00:42:42.862Z.