# NTSB CHI06CA135: Cessna 172SP, N409TA, Indianapolis, IN, May 23, 2006

- Type: NTSB accident investigation
- Classification: Accident · No injuries · Data collection · Final report
- Date: May 23, 2006, 10:30 local (14:30 UTC)
- Place: Indianapolis, IN
- Coordinates: 39.830554, -86.294166
- Nearby events: https://openairdocs.org/map.md?lat=39.8306&lon=-86.2942&mi=10
- Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping)
- Highest injury: No injuries
- Injuries: 1 uninjured
- Status: Completed, report August 29, 2006
- Report: Approved by Office Director
- NTSB case key (mKey): 63805
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=CHI06CA135
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/63805/pdf
- Page: https://openairdocs.org/ntsb/CHI06CA135

## Probable cause

The pilot's improper flare during landing.

## Sequence of events

In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf).

- Hard landing, landing
  - flare - improper, pilot in command (cause)
  - recovery from bounced landing - performed, pilot in command
  - aborted landing - performed, pilot in command

## Analysis

The airplane sustained substantial damage during a hard landing.  The airplane was configured with full flaps and 80 knots on final.  The pilot reported that the airplane was about 20 - 25 feet above the runway as it was "floating down the runway" and bleeding off airspeed.  He reported, "Suddenly it seemed that the plane just dropped."  The pilot reported the airplane ballooned so he added full throttle and aborted the landing.  He returned to the departure airport and landed without incident.  The inspection of the airplane revealed that the stall warning system operated.  An avionics technician inspected the airspeed indicator and it indicated the correct airspeeds.  The post accident inspection of the airplane revealed no preexisting anomalies that could be associated with a pre-impact condition.

## Factual narrative

The airplane sustained substantial damage during a hard landing.  The airplane was configured with full flaps and 80 knots on final.  The pilot reported that the airplane was about 20 - 25 feet above the runway as it was "floating down the runway" and bleeding off airspeed.  He reported, "Suddenly it seemed that the plane just dropped."  The pilot reported the airplane ballooned so he added full throttle and aborted the landing.  He returned to the departure airport and landed without incident.  The inspection of the airplane revealed that the stall warning system operated.  An avionics technician inspected the airspeed indicator and it indicated the correct airspeeds.  The post accident inspection of the airplane revealed no preexisting anomalies that could be associated with a pre-impact condition.

## Aircraft

- Registration: N409TA (not matched to a registry record)
- Reported make and model: Cessna 172SP
- Category: Airplane
- Serial number: 172S9040
- Engines: Lycoming IO-360-L2A reciprocating
- Damage: Substantial damage
- Flight: Personal, Part 91
- Registered owner: Indianapolis Aviation Inc.
- Airworthiness certificate: Standard, Normal
- Departed: UMP, Indianapolis, IN
- Destination: EYE, Indianapolis, IN
- Airport: EYE, Eagle Creek Airport, runway 03

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 50; private; airplane ratings: single-engine land; medical: class 3; flight hours: 223 total, 172 in this make and model, 223 as pilot in command, 3 in the last 90 days, 1 in the last 30 days

## Weather

- Conditions: Visual (VMC), Day

## FAA reports on this event (1)

The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs).

- [Accident 20060523011089A](https://openairdocs.org/incident/20060523011089A), May 23, 2006: Cessna 172S, Indianapolis, IN, Substantial damage. (-23) Pilot departed metro (ump) and damaged the aircraft while attempting to land at Eagle Creek. Landed hard, bounced and touched down hard a second time,…

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.