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

Cessna 172S accident near Indianapolis, Indiana, August 21, 2013

On August 21, 2013 at about 11:15 pm local time, a Cessna 172S, registered N45EF, was substantially damaged in an accident during approach (VFR go-around) near Indianapolis, Indiana (Indianapolis Executive airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot's inadequate monitoring on the airplane's airspeed during the go-around, resulting in a stall.

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

What the record shows

Date
August 21, 2013 · about 11:15 pm local time
Place
Indianapolis, Indiana · Indianapolis Executive · map
Type
Accident
Injuries
No one was hurt; 1 person was on board or involved.
Weather
visual conditions (good weather)
Aircraft
Cessna 172S · all 172Ss on the register
Registration
N45EF · registry record · serial 172S8982
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

During the landing flare, about 2-4 feet above the runway, the right wing dropped. The pilot advanced the throttle full forward and attempted a go-around. During the go-around the airspeed decreased below 40 knots, the airplane stalled, and landed hard. The right main landing gear collapsed which resulted in substantial damage to the firewall and fuselage. The pilot reported that the accident could have been prevented by closely monitoring and maintaining an airspeed above the stall speed.

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. Aerodynamic stall/spin during approach (VFR go-around) defining event
  2. Abnormal runway contact during landing (flare/touchdown)
  3. Hard landing during landing (flare/touchdown)

The NTSB's findings

  • cause Personnel issues › Psychological › Attention/monitoring › Task monitoring/vigilance › Pilot

Dual student

  • Certificate: student
  • Flight time: 53 hours in all; 42 in this make and model; 22 in the last 90 days; 19 in the last 30 days; 10 as pilot in command
  • Medical certificate: Class 3 (without waivers/limitations)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Airframe total time: 5,550 hours
  • Last inspection: annual inspection, August 13, 2013
  • Maximum gross weight: 2,550 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Lycoming IO-360-L2A (piston); 0 hours total

The flight

  • Departed from: KTYQ Indianapolis IN at 9:30 am
  • Destination: KTYQ Indianapolis IN
  • Flight plan: none
  • Runway 18, 5,500 ft by 100 ft

Weather at the time

  • Light: daylight
  • Wind: from 280° at 5 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 81°F (27°C), dew point 0°F (-18°C)
  • Altimeter: 30.12 inHg
  • Observation at 9:30 pm from KTYQ

Injuries

FatalSeriousMinorNone
Flight crew1

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

The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.

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 never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.