# NTSB ERA16CA229: Cessna 182T, N892BV, Crystal River, FL, June 23, 2016 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: June 23, 2016, 10:25 local (14:25 UTC) - Place: Crystal River, FL - Coordinates: 28.866945, -82.567779 - Nearby events: https://openairdocs.org/map.md?lat=28.8669&lon=-82.5678&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 April 10, 2017 - Report: Approved by Office Director - NTSB office: Eastern Region Aviation - Parties: FAA FSDO - NTSB case key (mKey): 93441 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA16CA229 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/93441/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=93441 - Page: https://openairdocs.org/ntsb/ERA16CA229 ## Probable cause The pilot's failure to execute a go-around following an unstabilized approach, which resulted in a bounced landing and 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: [Cessna 182T, 5 cases](https://openairdocs.org/ntsb-findings/01062040/cases.md?model=2072703), [All aircraft, 809 cases](https://openairdocs.org/ntsb-findings/01062040/cases.md) - [Info processing/decision: decision making/judgment](https://openairdocs.org/ntsb-findings/02041520): Personnel issues › Action/decision · Pilot (probable cause); cases with it: [Cessna 182T, 11 cases](https://openairdocs.org/ntsb-findings/02041520/cases.md?model=2072703), [All aircraft, 3,098 cases](https://openairdocs.org/ntsb-findings/02041520/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 182T, 26 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=2072703), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md) - [Terrain](https://openairdocs.org/ntsb-findings/03021000): Environmental issues › Physical environment · Contributed to outcome; cases with it: [Cessna 182T, 2 cases](https://openairdocs.org/ntsb-findings/03021000/cases.md?model=2072703), [All aircraft, 267 cases](https://openairdocs.org/ntsb-findings/03021000/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Approach-VFR pattern final: Abrupt maneuver](https://openairdocs.org/ntsb-events/270); cases with it: [Cessna 182T, 3 cases](https://openairdocs.org/ntsb-events/270/sequence.md?model=2072703), [All aircraft, 346 cases](https://openairdocs.org/ntsb-events/270/sequence.md) - [Landing-flare/touchdown: Abnormal runway contact](https://openairdocs.org/ntsb-events/090) (defining event); cases with it: [Cessna 182T, 6 cases](https://openairdocs.org/ntsb-events/090/sequence.md?model=2072703), [All aircraft, 1,506 cases](https://openairdocs.org/ntsb-events/090/sequence.md) - [Landing-flare/touchdown: Runway excursion](https://openairdocs.org/ntsb-events/300); cases with it: [Cessna 182T, 10 cases](https://openairdocs.org/ntsb-events/300/sequence.md?model=2072703), [All aircraft, 3,643 cases](https://openairdocs.org/ntsb-events/300/sequence.md) - [Landing-landing roll: Loss of control on ground](https://openairdocs.org/ntsb-events/230); cases with it: [Cessna 182T, 9 cases](https://openairdocs.org/ntsb-events/230/sequence.md?model=2072703), [All aircraft, 4,585 cases](https://openairdocs.org/ntsb-events/230/sequence.md) - [Landing-landing roll: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Cessna 182T, 17 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=2072703), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) - [Landing-flare/touchdown: Landing gear collapse](https://openairdocs.org/ntsb-events/094); cases with it: [Cessna 182T, 4 cases](https://openairdocs.org/ntsb-events/094/sequence.md?model=2072703), [All aircraft, 1,787 cases](https://openairdocs.org/ntsb-events/094/sequence.md) ## Analysis The pilot stated that she had executed four full-stop, taxi-back landings to runway 09 and one full-stop, taxi-back landing to runway 27. She departed runway 27, remained in the traffic pattern for that runway, but while on short final approach, she realized that the airplane was lined up with the taxiway. She maneuvered to the left in an attempt to salvage the approach, and the airplane then touched down and bounced. The airplane travelled off the left side of the runway onto grass and collided with a ditch, which resulted in substantial damage to the firewall. The pilot reported that there were no preimpact mechanical malfunctions or failures with the airplane that would have precluded normal operation. She also stated that the accident could have been prevented if she had conducted a go-around. ## Factual narrative The pilot stated that she had executed four full-stop taxi back landings to runway 09, and one full-stop taxi back landing to runway 27. She departed runway 27, remained in the traffic pattern for that runway, but while on short final approach realized she was lined up with the taxiway. She maneuvered to the left in an attempt to salvage the approach, and touched down then bounced. The airplane travelled off the left side of the runway onto grass and collided with a ditch, resulting in substantial damage to the firewall. The pilot reported that there were no preimpact mechanical malfunctions or failures with the airplane that would have precluded normal operation. She also stated that the accident could have been prevented by execution of a go-around. ## Aircraft - Registration: [N892BV](https://openairdocs.org/aircraft/N892BV), registered now, S/N 18281329, built 2004 (OpenAirDocs) - Reported make and model: CESSNA 182T (T) - Registry model: [Cessna 182T](https://openairdocs.org/model/cessna-182t) (registry code 2072703) (OpenAirDocs) - Registry engine: [Lycoming IO-540 series](https://openairdocs.org/engine/lycoming-io-540-series) (registry code 41530, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 18281329 - Year built: 2004 - Airframe hours: 1040 - Engines: LYCOMING IO-540-AB1A5 230 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Standard, Normal - Last inspection: Annual, October 28, 2015 - Departed: CGC, Crystal River, FL - Destination: CGC, Crystal River, FL - Airport: CGC, Crystal River Airport, runway 27, 4,557 × 75 ft, asphalt - Equipment: Auto-pilot, Electronic multifunction display, Electronic primary flight display, Stall warning system ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 61; injuries: none; private; airplane ratings: single-engine land; medical: class 3, with waivers/limitations; last flight review December 2, 2015; seat: left; restraint: 3-point; flight hours: 400 total, 75 in this make and model, 207.6 as pilot in command, 70.6 in the last 90 days, 46.2 in the last 30 days, 1.5 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: 250° at 4 knots - Visibility: 10 statute miles - Lowest ceiling: 7,000 ft broken - Temperature: 86 °F, dew point 75 °F - Altimeter: 30.14 inHg - Observed at: CGC ## 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 20160623007289A](https://openairdocs.org/incident/20160623007289A), Jun 23, 2016: Cessna 182T, Crystal River, FL, Substantial damage. During approach to runway 27 pilot inadvertantly lined up on taxi way, realized mistake and while correcting for runway lost control of aircraft on landing.… ## Docket (4 files) The files NTSB released with the investigation on March 17, 2017, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=93441. 2.7 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 1.5 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40450107&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Master.PDF - Weather Reports and Records (item 2, .PDF, 82 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40450108&FileExtension=.PDF&FileName=Weather%20Reports%20and%20Records-Master.PDF - Record of NTSB Conversation (item 3, .PDF, 54 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40450109&FileExtension=.PDF&FileName=Record%20of%20NTSB%20Conversation-Master.PDF - Investigative Photographs (item 4, .PDF, 1.0 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40450110&FileExtension=.PDF&FileName=Investigative%20Photographs-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.