FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA24FA072 · Hawker Beechcraft Corp G36

21 Dec 2023 · Buford, GA, United States

Hawker Beechcraft Corp G36 · Accident en route

From DeKalb Peachtree Airport (PDK) to an unrecorded destination

Report a problem

Event

NTSB case
ERA24FA072
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
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

Hawker Beechcraft Corp G36

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
N23VS
Operator
Unknown
Onboard fatalities
Unknown
Route
From DeKalb Peachtree Airport (PDK), Atlanta, GATo not recorded
Aircraft age
About 15 years (built 2008)
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
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
Unknown or undetermined
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 power plant

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The pilot departed for a local flight shortly before the accident occurred. Recorded data showed that about 10 minutes into the flight, while about 3,000 ft mean sea level, groundspeed began to slow considerably, which was followed by a descent towards a large lake. The flight track continued over the lake and the loss of groundspeed and altitude also continued. A witness located near the accident site observed the airplane flying low over the water and then enter a right bank towards a tree line along the shoreline. The witnesses did not recall hearing any engine sounds. The airplane impacted the trees, then abruptly descended and impacted a parking lot. The airplane exploded on impact, and a large fire developed around the entire airplane. A distant surveillance camera captured the final moments of flight, which showed the airplane in a flight path consistent with the witness reports. Examination of the airframe and engine revealed no evidence of preimpact mechanical malfunctions or failures. Extensive thermal damage prevented the investigation from fully evaluating the airplane’s fuel system. About 10 gallons of fuel was recovered from the right main fuel tank. The other tanks were breached, destroyed, or empty of fuel. The fuel selector was not recovered. The thermal damage also prevented the recovery of any non-volatile memory stored in the cockpit primary and multi-function displays. Based on the available evidence, it is likely that the airplane’s engine lost power; however, here was no evidence that the engine experienced a catastrophic mechanical failure and there was sufficient fuel on-board. Due to the thermal damage sustained to the airplane, the reason for the loss of power could not be determined. The pilot’s severe coronary artery disease placed him at increased risk of a distracting, distressing, impairing, or incapacitating cardiovascular event, such as angina, arrhythmia, or heart attack. There is no autopsy evidence that such an event occurred, but such an event does not leave reliable autopsy evidence if it occurs just before death. Overall, there is insufficient evidence to determine whether the pilot’s severe coronary artery disease contributed to the accident.

Postimpact fire provides a plausible explanation for the pilot’s carboxyhemoglobin result, particularly considering the possibility of some passive carbon monoxide absorption into cavity blood after death. The cyanide level in the pilot’s cavity blood likely was due to exposure to fire smoke, and was not likely due to engine exhaust exposure, because cyanide typically is produced by combustion of nitrogen-containing polymers. Overall, available postmortem evidence provides no clear indication that preimpact carbon monoxide or cyanide poisoning occurred, that in-flight fire occurred, or that the pilot breathed during the known fire.

Probable cause

A loss of engine power for reasons that could not be determined due to significant thermal damage from postimpact fire.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA24FA072
Event ID
20231222193555
Case number
ERA24FA072
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, coordinates, 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: ed3bbfe4e3e4eeeaa0e192e296106bed36e1f0c91a28da7467b608e254810d25; retrieved 2026-09-15T08:09:32.352Z.