# NTSB ERA10CA350: Cessna 172S, N2373K, Salisbury, MD, June 25, 2010 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: June 25, 2010, 11:42 local (15:42 UTC) - Place: Salisbury, MD - Coordinates: 38.340278, -75.505554 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=38.3403&lon=-75.5056&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing: Abnormal runway contact](https://openairdocs.org/ntsb-events/090) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report December 20, 2010 - Report: Approved by Office Director - NTSB office: Eastern Region Aviation - Parties: FAA/FSDO - NTSB case key (mKey): 76538 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA10CA350 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/76538/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=76538 - Page: https://openairdocs.org/ntsb/ERA10CA350 ## Probable cause The student pilot's improper recovery from a bounced landing. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [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) - [Performance/control parameters: landing flare](https://openairdocs.org/ntsb-findings/01062041): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (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) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Landing: 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 According to the student pilot, he had conducted a 1.5-hour solo cross country flight and was landing at the destination airport. The student pilot stated that the airplane was "too high and too fast" on the landing approach, and the airplane "bounced" on touchdown. The student pilot "dove for the runway" in an attempt to recover, the airplane's nose landing gear contacted the runway, and the tire "blew." Postaccident examination by a Federal Aviation Administration inspector revealed substantial damage to the engine firewall. The student pilot reported there were no mechanical malfunctions or anomalies He also reported 54 hours of total flight experience. ## Factual narrative According to the student pilot, he had conducted a 1.5-hour solo cross country flight and was landing at the destination airport. The student pilot stated that the airplane was "too high and too fast" on the landing approach, and the airplane "bounced" on touchdown. The student pilot "dove for the runway" in an attempt to recover, the airplane's nose landing gear contacted the runway, and the tire "blew." Postaccident examination by a Federal Aviation Administration inspector revealed substantial damage to the engine firewall. The student pilot reported there were no mechanical malfunctions or anomalies He also reported 54 hours of total flight experience. ## Aircraft - Registration: [N2373K](https://openairdocs.org/aircraft/N2373K), registered now, S/N 172S8074, built 1999 (OpenAirDocs) - Reported make and model: CESSNA 172S - Registry model: [Cessna 172S](https://openairdocs.org/model/cessna-172s) (registry code 2072439) (OpenAirDocs) - Registry engine: [Lycoming I0360 series](https://openairdocs.org/engine/lycoming-i0360-series) (registry code 41515, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 172S8074 - Airframe hours: 2319 - Engines: LYCOMING IO-360 SER 180 horsepower reciprocating - Damage: Substantial damage - Flight: Instructional, Part 91 - Operator: Reading Aero Club Inc - Registered owner: Reading Aero Club Inc - Airworthiness certificate: Standard, Normal - Last inspection: Annual, March 3, 2010 - Departed: RDG, Reading, PA - Destination: SBY, Salisbury, MD - Airport: SBY, Salisbury-Ocean City, runway 05, 5,000 × 100 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 61; injuries: none; student; medical: class 3, with waivers/limitations; seat: left; flight hours: 54 total, 53 in this make and model, 11 as pilot in command, 17 in the last 90 days, 6 in the last 30 days, 0 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: 100° at 6 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 82 °F, dew point 64 °F - Altimeter: 30.04 inHg - Observed at: SBY ## 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 20100625037109A](https://openairdocs.org/incident/20100625037109A), Jun 25, 2010: Cessna 172S, Salisbury, MD, Substantial damage. Pilot made hard landing and bounced twice on runway 05 at Wicomico Regional Airport (sby) in Salisbury, MD at 1300 on 06/25/10 striking the propeller, blowing… ## Docket (2 files) The files NTSB released with the investigation on September 19, 2010, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=76538. 467 KB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 456 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40333112&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF - Weather Reports and Records (item 2, .PDF, 11 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40333118&FileExtension=.PDF&FileName=Weather%20Reports%20and%20Records-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.