ATL06CA037 · Beech BE-76
Beech BE-76 · Accident: loss of control in flight on approach
From DeKalb Peachtree Airport (PDK) to Liberty County Airport (2J2)
Event
- NTSB case
- ATL06CA037
- 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
- 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
Beech BE-76
- Aircraft type
- Beechcraft BE-76
- 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
- N6697N
- Operator
- Vincent G. Cacho · private individual
- Onboard fatalities
- Unknown
- Route
- From DeKalb Peachtree Airport (PDK), Chamblee, GATo Liberty County Airport (2J2), Hinesville, GA
- 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
- Approach · VFR go-around
- 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 control in flight
- 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
- Stall; 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
- Destroyed
Cause areas
- Pilot in command › Airspeed, not maintained
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 was completing an instrument cross-country flight when the accident occurred. Upon arrival at the destination airport, the pilot was cleared for a visual approach by air traffic control. The pilot stated that during the landing phase to runway 14, with a light right crosswind, he heard a popping noise after touchdown and the airplane veered left. The pilot initiated a go-around as the airplane departed the runway surface into the grass. The pilot reported that while attempting to clear trees, the stall warning horn sounded. He stated that he retracted the landing gear and then retracted the flaps. He reported that after flap retraction, the airplane’s left wing dropped, and the airplane lost altitude and collided with trees. Witnesses stated that the airplane climbed steeply and then banked to the left. According to witnesses, the airplane leveled, then the nose pitched up, rolled left, and nosed down into the trees. The pilot received serious injuries and the airplane was destroyed by impact forces and a postimpact fire. A postaccident examination of the wreckage determined that the landing gear was down and locked. The tires were consumed by fire. Other than the “popping” sound reported by the pilot several days after his initial statement, no mechanical problems were reported by the pilot or found during the postaccident examination of the airplane.
Probable cause
The pilot's failure to maintain airspeed which resulted in an inadvertent stall and subsequent impact with trees.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL06CA037
- Event ID
- 20060209X00184
- Case number
- ATL06CA037
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (5)
- 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: f16ec87a8bc6dea6df8c0d5eca89fa3d7f45655e9e6fb03b6f73487e11eae8be; retrieved 2026-09-21T09:00:34.304Z.
- Corrected after a review of the NTSB narrative, which states these values explicitly: damage. The narrative states "the airplane was destroyed by impact forces and a postimpact fire".