# NTSB WPR09CA273: Cessna 172S, N6048Z, Compton, CA, October 6, 2008

- Type: NTSB accident investigation
- Classification: Accident · No injuries · Data collection · Final report
- Date: October 5, 2008, 20:30 local (Oct 6, 2008, 03:30 UTC)
- Place: Compton, CA
- Coordinates: 33.887222, -118.23944 (estimated)
- Nearby events: https://openairdocs.org/map.md?lat=33.8872&lon=-118.2394&mi=10
- Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping)
- Defining event: [Landing-flare/touchdown: Hard landing](https://openairdocs.org/ntsb-events/092)
- Highest injury: No injuries
- Injuries: 2 uninjured
- Status: Completed, report September 30, 2009
- Report: Approved by Office Director
- NTSB office: Western Pacific Region
- Parties: Federal Aviation Administration FSDO
- NTSB case key (mKey): 73940
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR09CA273
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/73940/pdf
- NTSB docket: https://data.ntsb.gov/Docket?ProjectID=73940
- Page: https://openairdocs.org/ntsb/WPR09CA273

## Probable cause

The pilot's improper flare and inadequate recovery from a bounced landing.

## Findings

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

- [Action: incorrect action performance](https://openairdocs.org/ntsb-findings/02041015): Personnel issues › Action/decision · Pilot (probable cause); cases with it: [Cessna 172S, 32 cases](https://openairdocs.org/ntsb-findings/02041015/cases.md?model=2072439), [All aircraft, 1,386 cases](https://openairdocs.org/ntsb-findings/02041015/cases.md)
- [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: Hard landing](https://openairdocs.org/ntsb-events/092) (defining event); cases with it: [Cessna 172S, 102 cases](https://openairdocs.org/ntsb-events/092/sequence.md?model=2072439), [All aircraft, 2,102 cases](https://openairdocs.org/ntsb-events/092/sequence.md)
- [Landing-flare/touchdown: Abnormal runway contact](https://openairdocs.org/ntsb-events/090); 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 private pilot reported that the airplane bounced during landing. The airplane then began to porpoise and after the third bounce the pilot pushed the control yoke forward. The propeller then struck the runway surface. The pilot stated that he initially believed the airplane damage was limited to the propeller. Subsequent inspection revealed that the airplane sustained substantial damage to the firewall and forward fuselage structure. The extent of the damage was not reported to the NTSB until June 1, 2009. The pilot reported no mechanical failures or malfunctions with the airframe or engine prior to the accident.

## Factual narrative

The private pilot reported that the airplane bounced during landing. The airplane then began to porpoise and after the third bounce the pilot pushed the control yoke forward. The propeller then struck the runway surface. The pilot stated that he initially believed the airplane damage was limited to the propeller. Subsequent inspection revealed that the airplane sustained substantial damage to the firewall and forward fuselage structure. The extent of the damage was not reported to the NTSB until June 1, 2009. The pilot reported no mechanical failures or malfunctions with the airframe or engine prior to the accident.

## Aircraft

- Registration: [N6048Z](https://openairdocs.org/aircraft/N6048Z), registered now, S/N 172S10217, built 2006 (OpenAirDocs)
- Reported make and model: CESSNA 172S
- 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: 172S10217
- Airframe hours: 1078
- Engines: LYCOMING IO-360-L2A 180 horsepower reciprocating
- Damage: Substantial damage
- Flight: Personal, Part 91
- Airworthiness certificate: Standard, Utility; Standard, Normal
- Departed: CPM, Compton, CA
- Destination: CPM, Compton, CA
- Flight plan: VFR
- Airport: CPM, Compton, runway 25L, 3,322 × 60 ft, asphalt

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 28; injuries: none; private; airplane ratings: single-engine land; medical: class 1, with waivers/limitations; seat: left; flight hours: 60 total, 60 in this make and model

## Weather

- Conditions: Visual (VMC), Night/dark
- Wind: calm
- Visibility: 10 statute miles
- Lowest ceiling: none
- Temperature: 66 °F, dew point 59 °F
- Altimeter: 29.93 inHg
- Observed at: HHR, 5 nm away

## Docket (2 files)

The files NTSB released with the investigation on June 19, 2009, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=73940. 2.5 MB in all.

- Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 446 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40314915&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF
- Maintenance Records: Excerpts (item 2, .PDF, 2.0 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40314930&FileExtension=.PDF&FileName=Maintenance%20Records%3A%20Excerpts-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.