# NTSB ERA13CA016: Cessna 172P, N97757, Cedar Key, FL, October 8, 2012 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: October 8, 2012, 12:00 local (16:00 UTC) - Place: Cedar Key, FL - Coordinates: 29.134166, -83.050277 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=29.1342&lon=-83.0503&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing-flare/touchdown: Landing area overshoot](https://openairdocs.org/ntsb-events/380) - Highest injury: No injuries - Injuries: 2 uninjured - Status: Completed, report March 13, 2013 - Report: Approved by Office Director - NTSB office: Eastern Region Aviation - Parties: FAA\FSDO - NTSB case key (mKey): 85300 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA13CA016 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/85300/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=85300 - Page: https://openairdocs.org/ntsb/ERA13CA016 ## Probable cause The pilot's failure to attain the proper touchdown point, which resulted in a runway excursion. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Performance/control parameters: descent/approach/glide path](https://openairdocs.org/ntsb-findings/01062040): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [All aircraft, 809 cases](https://openairdocs.org/ntsb-findings/01062040/cases.md) - [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Pilot (probable cause); cases with it: [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: Landing area overshoot](https://openairdocs.org/ntsb-events/380) (defining event); cases with it: [All aircraft, 400 cases](https://openairdocs.org/ntsb-events/380/sequence.md) - [Landing-landing roll: Runway excursion](https://openairdocs.org/ntsb-events/300); cases with it: [All aircraft, 3,643 cases](https://openairdocs.org/ntsb-events/300/sequence.md) ## Analysis The pilot reported that the airplane was too high during his first approach to the 2,355-foot-long asphalt runway, so he performed a go-around. During his second approach, the airplane touched down normally; however, the pilot was not able to stop the airplane before the end of the runway. The airplane veered off the left side of the runway about 100 feet before the end and came to rest, nose down, in a marshy area. The airplane sustained substantial damage to its nose gear and firewall. Examination of the airplane did not reveal any preaccident mechanical malfunctions or failures that would have precluded normal operation. Based on the tire marks on the runway, which were continuous and began about 600 feet before the departure end of the runway and then veered off the left side of the runway, it is likely that the pilot landed long on the relatively short runway and was unable to stop the airplane on the remaining pavement. ## Factual narrative The pilot reported that the airplane was too high during his first approach to the 2,355-foot-long, 100-foot-wide, asphalt runway, and he performed a go-around. During his second approach, the airplane touched down normally; however, he was not able to stop before the end of the runway. The airplane veered off the left side of the runway, about 100-feet prior to the end and came to rest in a marsh area. The airplane sustained substantial damage to its nose gear and firewall. Examination of the airplane, which included an examination of the left and right brakes by a Federal Aviation Administration inspector, did not reveal any mechanical malfunctions or failures that would have precluded normal operation. Tire marks which corresponded to the airplane were observed to begin at a point that was about 600 feet prior to the end of the runway. ## Aircraft - Registration: N97757 (not matched to a registry record) - Reported make and model: CESSNA 172P - Category: Airplane - Serial number: 17276227 - Airframe hours: 3631 - Engines: LYCOMING O-320 SERIES 180 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: Ultimate Air Academy - Registered owner: Ultimate Air Academy - Airworthiness certificate: Standard, Normal - Last inspection: Annual, September 24, 2012 - Departed: 28J, Palatka, FL - Destination: CDK, Cedar Key, FL - Airport: CDK, Cedar Key, runway 23, 2,355 × 100 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 19; injuries: none; private; airplane ratings: single-engine land; medical: class 1; last flight review August 17, 2011; seat: left; flight hours: 131 total, 40 in this make and model, 56 as pilot in command, 2 in the last 90 days, 2 in the last 30 days, 1 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: 130° at 3 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 79 °F, dew point 73 °F - Altimeter: 30.03 inHg - Observed at: CTY, 30 nm away ## 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 20121008023179A](https://openairdocs.org/incident/20121008023179A), Oct 8, 2012: Cessna 172P, Cedar Key, FL, Substantial damage. 10/10/2012ASSIGNED to investigate this accident. Arrived at Cedar Key and found aircraft being prepared for recovery. Aircraft was approximately 20 feet off… ## Docket (5 files) The files NTSB released with the investigation on February 4, 2013, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=85300. 5.6 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 1.0 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40381097&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF - FAA Inspector Statement (item 2, .PDF, 132 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40381099&FileExtension=.PDF&FileName=FAA%20Inspector%20Statement-Redacted.PDF - Flight Manifest (item 3, .PDF, 218 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40381098&FileExtension=.PDF&FileName=Flight%20Manifest-Redacted.PDF - Photograph # 1 – Airplane as it came to rest (Provided by Operator) (item 4, .PDF, 254 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40381088&FileExtension=.PDF&FileName=Photograph%20%23%201%20%E2%80%93%20Airplane%20as%20it%20came%20to%20rest%20(Provided%20by%20Operator)-Master.PDF - Photograph # 2 – Tire marks on runway(Provided by Operator) (item 5, .PDF, 4.0 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40381089&FileExtension=.PDF&FileName=Photograph%20%23%202%20%E2%80%93%20Tire%20marks%20on%20runway(Provided%20by%20Operator)-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.