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

Cessna 172R accident near Council Bluffs, Iowa, March 24, 2012

On March 24, 2012 at about 1:22 pm local time, a Cessna 172R, registered N368ES, was substantially damaged in an accident during landing (landing roll) near Council Bluffs, Iowa (Council Bluffs Municipal 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 student pilot’s improper flare and inadequate recovery from a bounced landing, which resulted in a loss of directional control.

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

What the record shows

Date
March 24, 2012 · about 1:22 pm local time
Place
Council Bluffs, Iowa · Council Bluffs Municipal · map
Type
Accident
Injuries
No one was hurt; 1 person was on board or involved.
Weather
visual conditions (good weather)
Aircraft
Cessna 172R · all 172Rs on the register
Registration
N368ES · registry record · serial 17280022
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

The student pilot was practicing takeoffs and landings. He reported that he flared the airplane early and that it ballooned before bouncing firmly several times. The pilot subsequently lost directional control of the airplane, which then departed the side of the runway and collided with an airfield light. A postaccident examination of the airplane revealed damage to the firewall and fuselage. No other anomalies were found.

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. Abnormal runway contact during landing (flare/touchdown)
  2. Loss of control on ground during landing (landing roll) defining event
  3. Runway excursion during landing (landing roll)
  4. Collision with terrain or object (not controlled flight into terrain) during landing (landing roll)

The NTSB's findings

  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Directional control › Not attained/maintained
  • cause Personnel issues › Action/decision › Action › Incorrect action performance › Pilot
  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Landing flare › Incorrect use/operation

Dual student

  • Certificate: student
  • Flight time: 59 hours in all; 59 in this make and model
  • Medical certificate: Class 3
  • Seat: left
  • Injury: no injuries

The aircraft

  • Seats: 4
  • Landing gear: fixed
  • Engine: Lycoming IO360 SER (piston); 0 hours total
  • Operator: Advanced Air INC

The flight

  • Departed from: KCBF Council Bluffs IA at 1:00 pm
  • Destination: KCBF Council Bluffs IA
  • Flight plan: none
  • Runway 32, 3,650 ft by 60 ft

Weather at the time

  • Light: daylight
  • Wind: from 280° at 5 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 50°F (10°C), dew point 45°F (7°C)
  • Altimeter: 29.96 inHg
  • Observation at 1:15 pm from KCBF

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.

Other NTSB records under N368ES the same tail number, which may have belonged to a different aircraft at the time

2013-09-04CEN13CA529 · accident near Council Bluff, IA · substantial damage · no injuries

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.