FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN13CA423 · Beech C23

20 Jul 2013 · Augusta, KS, United States

Beech C23 · Accident: collision during takeoff/landing

From Augusta Municipal Airport (3AU) to Captain Jack Thomas El Dorado Airport (EQA)

Report a problem

Event

NTSB case
CEN13CA423
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 C23

Aircraft type
Beechcraft 23
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
N377TT
Onboard fatalities
Unknown
Route
From Augusta Municipal Airport (3AU), Augusta, KSTo Captain Jack Thomas El Dorado Airport (EQA), El Dorado, KS
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
Takeoff
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
Collision during takeoff/landing
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

  • Personnel issues › Miscellaneous

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The flight instructor and student pilot were performing a soft field takeoff from a 2,340 foot grass runway. During the takeoff the airplane did not accelerate as expected. The flight instructor stated that the airplane lifted off, but the trees at the end of the runway were approaching quickly. The instructor then made a slight turn, aiming for some shorter trees to the right. The airplane did not climb out of ground effect and struck a barbed wire fence. The airplane then impacted the ground just beyond the fence and came to a stop in the upright position. Examination of the airplane revealed substantial damage to the airplane’s fuselage and wings. A review of the airplane’s Pilot Operating Handbook (POH) indicated from grass field, no wind, flaps up, 2000 feet mean sea level, and 88 degree Fahrenheit, the airplane would have a 1,700 foot ground roll and would need 2,827 feet to clear a 50 foot obstacle. The instructor added that the airplane did not perform as the POH indicated. Based on a soft field takeoff technique of having flaps extended and nose high attitude, it’s likely the airplane did not reach the grass field performance data indicated in the POH. The soft field, nose high attitude and an over rotation of the nose, to compensate for the rapidly approaching runway end, likely degraded the airplane’s takeoff performance.

Probable cause

The pilot did not obtain adequate airspeed and clearance from obstructions during a grass field takeoff.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN13CA423
Event ID
20130722X83742
Case number
CEN13CA423
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. 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: 48440a7ee532e4e0d09c70d1e48a0e5942d315210366c072f823d43cdbe2ffb0; retrieved 2026-09-15T22:17:15.244Z.