# NTSB ERA09CA373: Cessna 152, N49897, Mt. Pleasant, SC, June 28, 2009 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: June 28, 2009, 09:00 local (13:00 UTC) - Place: Mt. Pleasant, SC - Coordinates: 32.891944, -79.77639 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=32.8919&lon=-79.7764&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 September 30, 2009 - Report: Approved by Office Director - NTSB office: Eastern Region Aviation - Parties: FAA/FSDO - NTSB case key (mKey): 74168 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA09CA373 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/74168/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=74168 - Page: https://openairdocs.org/ntsb/ERA09CA373 ## Probable cause The pilot's improper 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 152, 22 cases](https://openairdocs.org/ntsb-findings/02041015/cases.md?model=2071835), [All aircraft, 1,386 cases](https://openairdocs.org/ntsb-findings/02041015/cases.md) - [Performance/control parameters: pitch control](https://openairdocs.org/ntsb-findings/01062022): Aircraft › Aircraft oper/perf/capability · Incorrect use/operation (probable cause); cases with it: [Cessna 152, 14 cases](https://openairdocs.org/ntsb-findings/01062022/cases.md?model=2071835), [All aircraft, 526 cases](https://openairdocs.org/ntsb-findings/01062022/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 152, 115 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=2071835), [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 152, 41 cases](https://openairdocs.org/ntsb-events/090/sequence.md?model=2071835), [All aircraft, 1,506 cases](https://openairdocs.org/ntsb-events/090/sequence.md) - [Landing-flare/touchdown: Landing gear collapse](https://openairdocs.org/ntsb-events/094); cases with it: [Cessna 152, 32 cases](https://openairdocs.org/ntsb-events/094/sequence.md?model=2071835), [All aircraft, 1,787 cases](https://openairdocs.org/ntsb-events/094/sequence.md) ## Analysis The pilot was flying solo in the traffic pattern for runway 35. As he approached the runway, he reduced power and added flaps to decrease the airspeed. The airplane bounced upon touchdown and the pilot added a “small amount” of power. The airplane bounced a second time, and then settled onto the runway. The third time the airplane contacted the runway, the nose gear collapsed. The winds reported at the airport about the time of the accident were from 090 degrees at 5 knots. The pilot did not report any mechanical anomalies with the airplane. ## Factual narrative The pilot was flying solo in the traffic pattern for runway 35. As he approached the runway, he reduced power and added flaps to decrease the airspeed. The airplane bounced upon touchdown and the pilot added a “small amount” of power. The airplane bounced a second time, and then settled onto the runway. The third time the airplane contacted, the runway the nose gear collapsed, substantially damaging the wing spar. The winds reported at the airport about the time of the accident were from 090 degrees at 5 knots. The pilot did not report any mechanical anomalies with the airplane. ## Aircraft - Registration: [N49897](https://openairdocs.org/deregistered/N49897-2009-08-31), registration cancelled 2009-08-31, S/N 15281379, built 1978 (OpenAirDocs) - Reported make and model: CESSNA 152 - Registry model: [Cessna 152](https://openairdocs.org/model/cessna-152) (registry code 2071835) (OpenAirDocs) - Registry engine: [Lycoming 0-235 series](https://openairdocs.org/engine/lycoming-0-235-series) (registry code 41505, 4 cycle) (OpenAirDocs) - Category: Airplane - Serial number: 15281379 - Airframe hours: 9108 - Engines: LYCOMING O-235 SERIES 115 horsepower reciprocating - Damage: Substantial damage - Flight: Instructional, Part 91 - Operator: Palmetto Air Service LLC - Registered owner: Palmetto Air Service LLC - Airworthiness certificate: Standard, Utility - Last inspection: Annual, April 16, 2009 - Departed: LRO, Mt. Pleasant, SC - Destination: LRO, Mt. Pleasant, SC - Airport: LRO, Mt. Pleasant Regional Faison, runway 35, 3,700 × 75 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Student pilot; age 44; injuries: none; student; medical: class 3, without waivers/limitations; seat: left; flight hours: 43 total, 22 in this make and model, 1 as pilot in command, 16 in the last 90 days, 6 in the last 30 days ## Weather - Conditions: Visual (VMC), Day - Wind: 90° at 5 knots - Visibility: 5 statute miles - Lowest ceiling: none - Temperature: 82 °F, dew point 75 °F - Altimeter: 29.78 inHg - Observed at: LRO ## 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 20090628047389A](https://openairdocs.org/incident/20090628047389A), Jun 28, 2009: Cessna 152, Mt. Pleasant, SC, Substantial damage. Student pilot was landing on runway 35 at Mt. Pleasant airport, (lro) near charleston, SC. The airplane bounced 3 times, the pilot added power and the airplane… ## Docket (3 files) The files NTSB released with the investigation on July 27, 2009, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=74168. 1.8 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 439 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40316160&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF - Pilot Statement (item 2, .PDF, 47 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40316161&FileExtension=.PDF&FileName=Pilot%20Statement-Redacted.PDF - Photograph # 1 - Damaged Airplane (provided by FAA) (item 3, .PDF, 1.4 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40316162&FileExtension=.PDF&FileName=Photograph%20%23%201%20-%20Damaged%20Airplane%20(provided%20by%20FAA)-Master.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.