FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN12LA649 · Beechcraft A23-24

19 Sept 2012 · Tell City, IN, United States

Beechcraft A23-24 · Accident: landing area overshoot

From Breckinridge County Airport (I93) to Perry County Municipal Airport (TEL)

Report a problem

Event

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

Beechcraft A23-24

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
N3629Q
Operator
Unknown
Onboard fatalities
Unknown
Route
From Breckinridge County Airport (I93), Hardinsburg, KYTo Perry County Municipal Airport (TEL), Tell City, IN
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
Landing · flare/touchdown
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
Landing area overshoot
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

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Task performance

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 reported that he made a straight-in approach to runway 31 after a short flight of about 10 minutes. He stated that there was no appreciable wind during the landing attempt with the wing flaps fully extended. He reported the airplane landed about 1/3 down the runway and that after touchdown he retracted the wing flaps and applied brake pressure in an attempt to slow the airplane. He stated that the airplane did not seem to decelerate normally during the landing roll because of the downslope of the runway. The pilot stated that although there were no anomalies with the airplane’s brake system he elected to abort the landing. He reported that as the airplane passed midfield he increased engine power for the aborted landing. He stated that although the airplane accelerated to liftoff speed while still on the runway, it did not clear a 10-foot high airport security fence located off the end of the runway. The pilot reported no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation.

A postaccident examination of the runway overrun area showed tire tracks consistent with the tire width of the accident airplane. The airplane impacted a chain-link fence located about 340 feet off the end of the runway with the nose landing gear. The postaccident examination did not reveal any anomalies with the airplane brake system that would have prevented normal operation. Landing performance calculations indicated that the airplane should have been able to stop within 1,000 feet of touchdown. Considering that the runway was 4,400 feet long, the pilot should have been able to stop the airplane on the available runway given the known weather and runway conditions.

Probable cause

The pilot’s improper touchdown point during landing and the resultant runway excursion during the aborted landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN12LA649
Event ID
20120920X73017
Case number
CEN12LA649
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. 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: 3c76a4221df6e150b4bc031238aa0f442f14e7e9fb2d38cbe4ee3bc14e26c027; retrieved 2026-09-15T19:57:39.020Z.