# NTSB WPR15CA028: Cessna 172 - S, N564AT, Hawthorne, CA, October 23, 2014

- Type: NTSB accident investigation
- Classification: Accident · No injuries · Data collection · Final report
- Date: October 23, 2014, 13:00 local (20:00 UTC)
- Place: Hawthorne, CA
- Coordinates: 33.910884, -118.340393 (estimated)
- Nearby events: https://openairdocs.org/map.md?lat=33.9109&lon=-118.3404&mi=10
- Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping)
- Defining event: [Landing-flare/touchdown: Abnormal runway contact](https://openairdocs.org/ntsb-events/090)
- Highest injury: No injuries
- Injuries: 1 uninjured
- Status: Completed, report January 12, 2015
- Report: Approved by Office Director
- NTSB office: Western Pacific Region
- Parties: Federal Aviation Administration
- NTSB case key (mKey): 90319
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR15CA028
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/90319/pdf
- NTSB docket: https://data.ntsb.gov/Docket?ProjectID=90319
- Page: https://openairdocs.org/ntsb/WPR15CA028

## Probable cause

The pilot's improper flare which resulted in a loss of aircraft control and subsequent hard landing.

## Findings

NTSB's coded findings; those marked are part of the probable cause.

- [Performance/control parameters: landing flare](https://openairdocs.org/ntsb-findings/01062041): Aircraft › Aircraft oper/perf/capability · Incorrect use/operation (probable cause); cases with it: [Cessna 172S, 99 cases](https://openairdocs.org/ntsb-findings/01062041/cases.md?model=2072439), [All aircraft, 1,285 cases](https://openairdocs.org/ntsb-findings/01062041/cases.md)
- [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Cessna 172S, 206 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=2072439), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md)

## Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event best describes what happened.

- [Landing-flare/touchdown: Abnormal runway contact](https://openairdocs.org/ntsb-events/090) (defining event); cases with it: [Cessna 172S, 77 cases](https://openairdocs.org/ntsb-events/090/sequence.md?model=2072439), [All aircraft, 1,506 cases](https://openairdocs.org/ntsb-events/090/sequence.md)

## Analysis

The pilot reported that during landing he flared too high, which resulted in the airplane bouncing hard three times. A postaccident examination of the airplane revealed that the firewall had sustained substantial damage. The pilot reported no preimpact mechanical malfunctions or failures with the airplane that would have precluded normal operation.

## Factual narrative

The pilot reported that during landing he flared too high, which resulted in the airplane bouncing hard three times. A postaccident examination of the airplane revealed that the firewall had sustained substantial damage. The pilot reported no preimpact mechanical malfunctions or failures with the airplane that would have precluded normal operation.

## Aircraft

- Registration: [N564AT](https://openairdocs.org/aircraft/N564AT), registered now, S/N 172S10020, built 2005 (OpenAirDocs)
- Reported make and model: CESSNA 172 - S (S)
- Registry model: [Cessna 172S](https://openairdocs.org/model/cessna-172s) (registry code 2072439) (OpenAirDocs)
- Registry engine: [Lycoming IO-360-L2A](https://openairdocs.org/engine/lycoming-io-360-l2a) (registry code 41597, reciprocating) (OpenAirDocs)
- Category: Airplane
- Serial number: 172S10020
- Year built: 2005
- Airframe hours: 3674
- Engines: Lycoming IO-360-L2A 180 horsepower reciprocating
- Damage: Substantial damage
- Flight: Instructional, Part 91
- Operator: Pacific Air flight School
- Registered owner: Uvalde Flight Center Inc.
- Airworthiness certificate: Standard, Normal
- Last inspection: 100 hour, September 17, 2014, 42 hours before
- Departed: HHR, Hawthorne, CA
- Destination: HHR, Hawthorne, CA
- Airport: HHR, Hawthorne Municipal Airport, runway 25, 4,956 × 100 ft, asphalt
- Equipment: Auto-pilot, Electronic multifunction display, Electronic primary flight display, Stall warning system

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 46; injuries: none; student; medical: class 3, with waivers/limitations; seat: left; restraint: 3-point; flight hours: 51 total, 51 in this make and model, 0.2 as pilot in command, 51 in the last 90 days, 51 in the last 30 days, 3 in the last 24 hours

## Weather

- Conditions: Visual (VMC), Day
- Wind: 260° at 4 knots
- Visibility: 10 statute miles
- Lowest ceiling: none
- Temperature: 72 °F, dew point 61 °F
- Altimeter: 29.98 inHg
- Observed at: HHR

## 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 20141023019869A](https://openairdocs.org/incident/20141023019869A), Oct 23, 2014: Cessna 172S, Hawthorne, CA, Substantial damage. Student pilot first solo, upon landing aircraft bounced 3 times and landed hard on nose gear, prop struck ground. Was able to taxi. Damage to prop, gear, skin…

## Docket (3 files)

The files NTSB released with the investigation on December 19, 2014, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=90319. 5.2 MB in all.

- Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 4.5 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40420252&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF
- Record of Conversation – Chris Miller (item 2, .PDF, 18 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40420253&FileExtension=.PDF&FileName=Record%20of%20Conversation%20%E2%80%93%20Chris%20Miller-Master.PDF
- Release of Wreckage, NTSB Form 6120.15 (item 3, .PDF, 708 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40420254&FileExtension=.PDF&FileName=Release%20of%20Wreckage,%20NTSB%20Form%206120.15-Redacted.PDF

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.