# NTSB ERA15CA196: Cessna 172P, N66090, Sebastian, FL, April 17, 2015 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: April 17, 2015, 14:00 local (18:00 UTC) - Place: Sebastian, FL - Coordinates: 27.813333, -80.495552 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=27.8133&lon=-80.4956&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing: Landing area overshoot](https://openairdocs.org/ntsb-events/380) - Highest injury: No injuries - Injuries: 2 uninjured - Status: Completed, report May 13, 2015 - Report: Approved by Office Director - NTSB office: Eastern Region Aviation - Parties: FAA/FSDO - NTSB case key (mKey): 91069 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA15CA196 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/91069/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=91069 - Page: https://openairdocs.org/ntsb/ERA15CA196 ## Probable cause The pilot's misjudged airspeed and glidepath, which resulted in a landing area overshoot and runway excursion. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Info processing/decision: decision making/judgment](https://openairdocs.org/ntsb-findings/02041520): Personnel issues › Action/decision · Pilot (probable cause); cases with it: [Cessna 172P, 20 cases](https://openairdocs.org/ntsb-findings/02041520/cases.md?model=2072436), [All aircraft, 3,098 cases](https://openairdocs.org/ntsb-findings/02041520/cases.md) - [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: [Cessna 172P, 4 cases](https://openairdocs.org/ntsb-findings/01062040/cases.md?model=2072436), [All aircraft, 809 cases](https://openairdocs.org/ntsb-findings/01062040/cases.md) - [Performance/control parameters: airspeed](https://openairdocs.org/ntsb-findings/01062010): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Cessna 172P, 7 cases](https://openairdocs.org/ntsb-findings/01062010/cases.md?model=2072436), [All aircraft, 1,681 cases](https://openairdocs.org/ntsb-findings/01062010/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Landing: Landing area overshoot](https://openairdocs.org/ntsb-events/380) (defining event); cases with it: [Cessna 172P, 2 cases](https://openairdocs.org/ntsb-events/380/sequence.md?model=2072436), [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: [Cessna 172P, 29 cases](https://openairdocs.org/ntsb-events/300/sequence.md?model=2072436), [All aircraft, 3,643 cases](https://openairdocs.org/ntsb-events/300/sequence.md) - [Landing-landing roll: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Cessna 172P, 45 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=2072436), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) ## Analysis The pilot stated that due to other traffic ahead in the airport traffic pattern, he purposely entered a high right base leg for runway 10, a 3,199-foot-long asphalt runway. The airplane remained high during the approach and the pilot attempted to land on the last one-half of the runway; however, the airplane was also too fast as the pilot had selected only 10 degrees of flap extension. The airplane subsequently touched down near the end of the runway, traveled over an approximate 500-foot grass area beyond the end of the runway, and struck a fence before coming to rest upright. Examination of the airplane by a Federal Aviation Administration inspector revealed substantial damage to the firewall. The inspector did not observe any preimpact mechanical malfunctions with the airplane, nor did the pilot report any. The recorded wind near the accident site, about the time of the accident, was from 040 degrees at 7 knots. ## Factual narrative The pilot stated that due to other traffic ahead in the airport traffic pattern, he purposely entered a high right base leg for runway 10, a 3,199-foot-long asphalt runway. The airplane remained high during the approach and the pilot attempted to land on the last one-half of the runway; however, the airplane was also too fast as the pilot had selected only 10 degrees of flap extension. The airplane subsequently touched down near the end of the runway, traveled over an approximate 500-foot grass area beyond the end of the runway, and struck a fence before coming to rest upright. Examination of the airplane by a Federal Aviation Administration inspector revealed substantial damage to the firewall. The inspector did not observe any preimpact mechanical malfunctions with the airplane, nor did the pilot report any. The recorded wind near the accident site, about the time of the accident, was from 040 degrees at 7 knots. ## Aircraft - Registration: [N66090](https://openairdocs.org/aircraft/N66090), registered now, S/N 17275963, built 1983 (OpenAirDocs) - Reported make and model: CESSNA 172P - Registry model: [Cessna 172P](https://openairdocs.org/model/cessna-172p) (registry code 2072436) (OpenAirDocs) - Registry engine: [Lycoming 0-320 series](https://openairdocs.org/engine/lycoming-0-320-series) (registry code 41508, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 17275963 - Year built: 1983 - Airframe hours: 14096 - Engines: LYCOMING O-320 160 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: Deland Aviation - Registered owner: Skyline Solutions Inc - Airworthiness certificate: Standard, Normal - Last inspection: Annual, March 16, 2015, 55 hours before - Departed: MTH, Marathon, FL - Destination: X26, Sebastian, FL - Airport: X26, Sebastian Municipal Airport, runway 10, 3,199 × 75 ft, asphalt - Equipment: Stall warning system, Handheld GPS ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 45; injuries: none; commercial; airplane ratings: single-engine land, multi-engine land; instrument ratings: airplane; medical: class 2, with waivers/limitations; last flight review July 7, 2014; seat: left; restraint: 3-point; flight hours: 1,168 total, 688 in this make and model, 788 as pilot in command, 37 in the last 90 days, 23 in the last 30 days, 5 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: 40° at 7 knots - Visibility: 10 statute miles - Lowest ceiling: 6,000 ft broken - Temperature: 84 °F, dew point 68 °F - Altimeter: 30.03 inHg - Observed at: VRB, 10 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 20150417005439A](https://openairdocs.org/incident/20150417005439A), Apr 17, 2015: Cessna 172P, Sebastian, FL, Substantial damage. The instrument-rated, commercial pilot of the Cessna 172 reported that he and a passenger took off in clear skies for an early morning trip from deland airport… ## Other investigations on N66090 (1) 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. - [NTSB ATL88LA001](https://openairdocs.org/ntsb/ATL88LA001), Oct 3, 1987: Cessna 172P (N66090), Hilton Head, SC, destroyed ## Docket (5 files) The files NTSB released with the investigation on May 7, 2015, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=91069. 1.0 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 343 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40426033&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF - Record of Conversation - FAA Interview Summary (item 2, .PDF, 51 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40426034&FileExtension=.PDF&FileName=Record%20of%20Conversation%20-%20FAA%20Interview%20Summary-Master.PDF - Weather Report (item 3, .PDF, 199 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40426035&FileExtension=.PDF&FileName=Weather%20Report-Master.PDF - Photo 1 - Wreckage (Courtesy of Airport Manager) (item 4, .PDF, 200 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40426036&FileExtension=.PDF&FileName=Photo%201%20-%20Wreckage%20(Courtesy%20of%20Airport%20Manager)-Master.PDF - Photo 2 - Firewall Damage (Photo Courtesy of FAA) (item 5, .PDF, 221 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40426037&FileExtension=.PDF&FileName=Photo%202%20-%20Firewall%20Damage%20(Photo%20Courtesy%20of%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.