eFlight
Accidents · NTSB CEN26LA322 · Preliminary: the investigation is not finished

Cessna 172M accident near Hanover, Indiana, September 16, 2026

On September 16, 2026 at about 11:05 pm local time, a 1976 Cessna 172M, registered N9909Q, was substantially damaged in an accident during takeoff near Hanover, Indiana (Lee Bottom Airport). It was a personal flight under general aviation rules (Part 91). 2 people had minor injuries. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The NTSB has not yet published a probable cause for this accident. Investigations usually take one to two years; this page updates when the final report is released.

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

What the record shows

Date
September 16, 2026 · about 11:05 pm local time · cases in 2026
Place
Hanover, Indiana · Lee Bottom Airport · cases near this airport · map
Type
Accident
Injuries
2 people had minor injuries.
Weather
visual conditions (good weather)
Aircraft
Cessna 172M, built 1976 · all 172Ms on the register
Registration
N9909Q · registry record · serial 17265853
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

On September 16, 2026, about 1905 eastern daylight time, a Cessna 172M airplane, N9909Q, was substantially damaged when it was involved in an accident near Hanover, Indiana. The pilot and passenger sustained minor injuries. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. The pilot reported that the purpose of the flight was to fly with a friend to and from Lee Bottom Airport. The pilot stated that she was familiar with the airport's grass runway and previously operated there during flight training. After landing at Lee Bottom, the pilot taxied back for departure from runway 18. During the initial takeoff the pilot noted that the airplane was not performing as expected and discontinued the takeoff. The pilot taxied back and initiated a second takeoff attempt using 10° flaps. The pilot reported that, during the second takeoff, the airplane became airborne and remained in ground effect to gain airspeed, and then the pilot established a climb. As the airplane approached trees beyond the departure end of the runway, the pilot reported that the trees appeared to be getting closer and attempted to clear them. The pilot then observed a decrease in airspeed and lowered the nose. The airplane subsequently contacted the tops of trees, continued through the trees, impacted a residence, and then impacted terrain. The airplane came to rest inverted. There were no injuries reported on ground. The pilot and passenger exited the airplane after the accident with minor injuries. The fuselage and wings sustained substantial damage and the airplane was retained for further examination.

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. Loss of engine power (partial) during takeoff defining event

The aircraft

  • Airframe total time: 8,590.4 hours
  • Last inspection: annual inspection, September 19, 2025
  • Maximum gross weight: 2,300 lb
  • Seats: 4
  • Landing gear: fixed
  • Operator: Ck Aviation LLC

The flight

  • Departed from: 64I Hanover IN at 11:05 pm
  • Destination: KJVY Jeffersonville IN
  • Flight plan: none
  • Runway 18, 4,080 ft by 100 ft

Weather at the time

  • Light: daylight
  • Wind: from 220° at 3 knots
  • Visibility: 10 statute miles
  • Sky: a few clouds at 11,000 ft
  • Temperature: 79°F (26°C), dew point 77°F (25°C)
  • Altimeter: 30.26 inHg
  • Observation at 7:05 pm from KIMS, 7 miles away

Weather report (METAR): METAR KIMS 170015Z AUTO 22003KT 10SM FEW110 26/25 A3026 RMK AO2 T02610252=

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers1

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

The NTSB has not released the docket for this case yet. The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), is usually released when the investigation is nearly complete, and the list here is refreshed when it appears. Check at the NTSB.

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/CEN26LA322.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.

Aircraft

By kindModelsMakersEnginesFleetsWhat changed

Fly

Plan a flightAirportsLive mapRoutes and flightsFuels

Training and work

TrainingFlight schoolsGround schoolsPilot examinersMedical examinersJobs

Companies

DirectoryCharter operatorsFBOsRepair stationsClaim your listing

Safety and data

AccidentsRecords checkAnalyticsSAFxCHANGEThe graphAbout

Colours follow your device's light or dark setting.