The U.S. aircraft register, updated daily
Accidents · NTSB CEN12LA649 · Final report

Beechcraft A23-24 accident near Tell City, Indiana, September 19, 2012

On September 19, 2012 at about 2:10 pm local time, a Beechcraft A23-24, registered N3629Q, was substantially damaged in an accident during landing (flare/touchdown) near Tell City, Indiana (Perry County Municpal Airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 3 people were on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

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

Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.

What the record shows

Date
September 19, 2012 · about 2:10 pm local time · cases in 2012
Place
Tell City, Indiana · Perry County Municpal Airport · cases near this airport · map
Type
Accident
Injuries
No one was hurt; 3 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft
Beechcraft A23-24 · all A23-24s on the register
Registration
N3629Q · no longer on the register · serial MA-224
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

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.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Landing area overshoot during landing (flare/touchdown) defining event
  2. Runway excursion during landing (aborted after touchdown)
  3. Collision during takeoff/land during landing (aborted after touchdown)

The NTSB's findings

  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Descent/approach/glide path › Incorrect use/operation
  • cause Personnel issues › Task performance › Use of equip/info › (general) › Pilot

Pilot

  • Certificate: commercial pilot
  • Ratings: multi-engine land; single-engine land; instrument: airplane
  • Flight time: 2,040 hours in all; 739 in this make and model; 4 in the last 90 days; 3 in the last 30 days; 1,908 as pilot in command
  • Last flight review: June 20, 2012
  • Medical certificate: Class 3 (with waivers/limitations)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Airframe total time: 1,615 hours
  • Last inspection: annual inspection, June 8, 2012
  • Maximum gross weight: 2,550 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Lycoming IO-360-A2B (piston); 0 hours total

The flight

  • Departed from: I93 Hardinsburg KY at 2:00 pm
  • Destination: TEL Tell City IN
  • Flight plan: none
  • Runway 31, 4,400 ft by 75 ft

Weather at the time

  • Light: daylight
  • Wind: from 160° at 4 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 57°F (14°C), dew point 45°F (7°C)
  • Altimeter: 30.19 inHg
  • Observation at 2:15 pm from HNB, 21 miles away

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers2

Documents from the investigation the NTSB's docket: the evidence folder behind the report

7 documents, released by the NTSB on November 6, 2013. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Connections how this case links to the rest of the register

Aircraft
Place

The whole map of how records connect · these connections as data: /graph/accident/CEN12LA649.json.

The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.