FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA01FA119 · Beech A-45/T-34A

10 Apr 2001 · Claxton, GA, United States

Beech A-45/T-34A · Accident during initial climb

From Claxton Evans County Airport (CWV) to Danville Regional Airport (DAN)

Report a problem

Event

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

Beech A-45/T-34A

Aircraft type
Beechcraft A-45
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
N340JB
Operator
Unknown
Onboard fatalities
Unknown
Route
From Claxton Evans County Airport (CWV), Claxton, GATo Danville Regional Airport (DAN), Danville, VA
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
Miscellaneous/other
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/mush; 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

A witness stated that she heard an aircraft flying low, with its engine operating "fast", pass over her house, so she ran out of the house for fear it would hit the house. She further stated that she then saw the airplane, just above treetop level, in the direction of the Claxton-Evans County Airport, in an extreme nose low pitch attitude. She said the airplane had been "falling fast, and the engine sounded wide open, or full throttle." She also said that "the wings were rocking, and it was obvious to her that the pilot was fighting hard to keep the airplane stable and level." According to the witness, she then saw the airplane drop into the trees, and heard the crash. She said she then got into her car and sped to the airport, and as she approached the airport, she saw the airplane at the edge of the trees. The witness said that she then saw an explosion, followed by a fireball which shot about 300 feet into the air, followed by a column of black smoke. She then ran into the airport manager's office and reported the accident. When she returned, she saw a man emerging from the woods, who had been badly burned. The pilot/owner of the accident airplane received fatal injuries as a result of the accident. The pilot rated passenger who survived the accident and who went through an extensive period of hospitalization later stated that his memory is fragmented, but that he remembered the run-up and takeoff, and that everything was normal until they were in the air when he saw fuel streaming back over the left wing. He said he could not see the fuel cap to see what the trouble was, and he remembers asking the pilot/owner if he needed some help, but did not remember the pilot/owner's answer, or if he gave any assistance to the pilot in handling the airplane. He said the next thing he remembered was telling the pilot "we're not going to make it", followed by the impact. Examination of the airplane revealed that the left fuel cap had separated from the wing, and it was found in the area of the airplane's initial impact with trees while the pilot had been returning to land at the airport he had just departed from. No preaccident failures or malfunctions were noted to the airplane's structure flight controls, or engine as a result of the postcrash examination.

Probable cause

The pilot in command's failure to maintain airspeed while performing an emergency landing after having just taken off with an unsecured fuel cap, which resulted in an inadvertent stall mush, an uncontrolled descent, and an impact with trees.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA01FA119
Event ID
20010418X00774
Case number
MIA01FA119
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: e00281051bd82d25a6d6921eaee68deba84fdc8c30ebabbf1463c048f034d0c3; retrieved 2026-09-20T20:35:58.322Z.