Grand Strand Aviation Beech A36 accident
Beech A36 · Accident: total loss of engine power (non-mechanical) en route
From DeKalb Peachtree Airport (PDK) to Grand Strand Airport (CRE)
Event
- NTSB case
- ATL82DA165
- 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
- Charter & commuter
- 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
Beech A36
- Aircraft type
- Beechcraft 36
- 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
- N1691W
- Operator
- Grand Strand Aviation
- Onboard fatalities
- Unknown
- Route
- From DeKalb Peachtree Airport (PDK), Atlanta, GATo Grand Strand Airport (CRE), Myrtle Beach, SC
- 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 135: Air Taxi & Commuter
- 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 · descent
- 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
- Destroyed
Cause areas
- Fluid, fuel › Starvation
- Pilot in command › Fuel supply, improper use of
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
AS THE PILOT APPROACHED HIS DESTINATION, HE DESCENDED FROM 9000 FT MSL AND LEVELED AT 1600 FT MSL. AT ABOUT THE TIME HE LEVELED, THE ENGINE QUIT ABRUPTLY. HE STATED THAT HE SWITCHED THE FUEL SELECTOR TO THE RIGHT TANK AND TRIED TO START THE ENGINE, BUT WAS NOT SUCCESSFUL. AN EMERGENCY LANDING WAS MADE IN AN OPEN FIELD BEYOND A LINE OF TREES. HOWEVER, AFTER CROSSING OVER THE TREES, HE WAS UNABLE TO FLARE DUE TO A LOSS OF AIRSPEED AND CRASH LANDED. AN INVESTIGATION REVEALED THAT THERE WAS 10 TO 15 GALLONS OF FUEL REMAINING IN THE RIGHT FUEL TANK. FUEL CALCULATIONS INDICATED THAT ALL OR MOST OF THE USABLE FUEL IN THE LEFT TANK WOULD HAVE BEEN CONSUMED.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record ATL82DA165
- Event ID
- 20020917X02751
- Case number
- ATL82DA165
- 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: a0b4ad702d13838d9f4ea297902df08dd3fd9e800d465cbcdd8401eb40605071; retrieved 2026-09-18T21:09:07.958Z.