# NTSB CEN13CA007: Cirrus Design SR20, N750SR, Eden Prairie, MN, October 2, 2012 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: October 2, 2012, 18:38 local (23:38 UTC) - Place: Eden Prairie, MN - Coordinates: 44.823055, -93.455276 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=44.8231&lon=-93.4553&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: 1 uninjured - Status: Completed, report December 19, 2012 - Report: Approved by Office Director - NTSB office: Central Region - Parties: Minneapolis FSDO - NTSB case key (mKey): 85270 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=CEN13CA007 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/85270/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=85270 - Page: https://openairdocs.org/ntsb/CEN13CA007 ## Probable cause The pilot’s inadequate braking action and decision to abort the landing near the departure end of the runway. Contributing to the accident was the pilot’s attempt to land near the midpoint of the runway. ## 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: [Cirrus Design SR20, 12 cases](https://openairdocs.org/ntsb-findings/02041520/cases.md?model=2130000), [All aircraft, 3,098 cases](https://openairdocs.org/ntsb-findings/02041520/cases.md) - [Action: incorrect action performance](https://openairdocs.org/ntsb-findings/02041015): Personnel issues › Action/decision · Pilot (probable cause); cases with it: [Cirrus Design SR20, 7 cases](https://openairdocs.org/ntsb-findings/02041015/cases.md?model=2130000), [All aircraft, 1,386 cases](https://openairdocs.org/ntsb-findings/02041015/cases.md) - [Personnel issues](https://openairdocs.org/ntsb-findings/02060000): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Cirrus Design SR20, 1 case](https://openairdocs.org/ntsb-findings/02060000/cases.md?model=2130000), [All aircraft, 137 cases](https://openairdocs.org/ntsb-findings/02060000/cases.md) - [Landing gear system: brake](https://openairdocs.org/ntsb-findings/01023242): Aircraft › Aircraft systems · Incorrect use/operation; cases with it: [Cirrus Design SR20, 1 case](https://openairdocs.org/ntsb-findings/01023242/cases.md?model=2130000), [All aircraft, 297 cases](https://openairdocs.org/ntsb-findings/01023242/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: [Cirrus Design SR20, 4 cases](https://openairdocs.org/ntsb-events/380/sequence.md?model=2130000), [All aircraft, 400 cases](https://openairdocs.org/ntsb-events/380/sequence.md) - [Landing: Attempted remediation/recovery](https://openairdocs.org/ntsb-events/060); cases with it: [Cirrus Design SR20, 13 cases](https://openairdocs.org/ntsb-events/060/sequence.md?model=2130000), [All aircraft, 1,422 cases](https://openairdocs.org/ntsb-events/060/sequence.md) - [Landing-landing roll: Runway excursion](https://openairdocs.org/ntsb-events/300); cases with it: [Cirrus Design SR20, 22 cases](https://openairdocs.org/ntsb-events/300/sequence.md?model=2130000), [All aircraft, 3,643 cases](https://openairdocs.org/ntsb-events/300/sequence.md) ## Analysis The pilot reported that he flew a visual approach and landed near the midpoint of a 2,691-foot-long runway. The wind was at 5 knots and aligned with the runway, which was dry. After landing, the pilot applied “light/normal braking” but noticed his deceleration rate was inadequate to stop on the remaining runway. The pilot subsequently applied heavier braking, but the brakes “seemed to have no effect.” Realizing he was not going to stop the airplane on the remaining runway, the pilot attempted a go-around near the departure end of the runway. The airplane never became airborne, departed the runway, and impacted an airport perimeter fence. Substantial damage to the airplane included impact damage to both wings and ailerons. Skid marks from the accident airplane were documented near the departure end of the runway. A postaccident examination of the braking system of the airplane revealed no mechanical malfunctions that would have precluded normal operation. ## Factual narrative The pilot reported that he flew a visual approach and landed near the midpoint of a 2,691 foot runway. The wind was at 5 knots and aligned with the runway, which was dry. After landing, the pilot applied “light/normal braking”, but noticed his deceleration rate was inadequate to stop on the remaining runway. The pilot subsequently applied heavier braking, but the brakes “seemed to have no effect.” Realizing he was not going to stop the airplane on the remaining runway, the pilot attempted a go-around near the departure end of the runway. The airplane never became airborne, departed the runway, and impacted an airport perimeter fence. Substantial damage to the airplane included impact damage to both wings and ailerons. A post-accident examination conducted by Federal Aviation Administration (FAA) personnel documented skid marks from the accident airplane near the departure end of the runway. FAA personnel also conducted a post-accident examination of the braking system of the airplane, with no abnormal findings. ## Aircraft - Registration: [N750SR](https://openairdocs.org/deregistered/N750SR-2021-07-31), registration cancelled 2021-07-31, S/N 1874 (OpenAirDocs) - Reported make and model: CIRRUS DESIGN CORP SR20 - Registry model: [Cirrus Design SR20](https://openairdocs.org/model/cirrus-design-sr20) (registry code 2130000) (OpenAirDocs) - Registry engine: [Continental IO-360-ES](https://openairdocs.org/engine/continental-io-360-es) (registry code 17160, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 1874 - Airframe hours: 870 - Engines: CONT MOTOR IO-360-ES 210 horsepower reciprocating - Damage: Substantial damage - Flight: Business, Part 91 - Operator: Hummingbird Ventures LLC, doing business as Hummingbird Venture LLC - Registered owner: Wozniak Daniel D Jr - Airworthiness certificate: Standard, Normal - Last inspection: 100 hour, June 29, 2012 - Departed: KLVN, Airlake, MN - Destination: KFCM, Flying Cloud, MN - Flight plan: VFR - Airport: KFCM, Flying Cloud, runway 18, 2,691 × 75 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 50; injuries: none; private; airplane ratings: single-engine land; medical: class 3, with waivers/limitations; last flight review March 12, 2012; seat: left; flight hours: 133 total, 60 in this make and model, 76 as pilot in command, 30 in the last 90 days, 4 in the last 30 days ## Weather - Conditions: Visual (VMC), Day - Wind: 170° at 5 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 64 °F, dew point 36 °F - Altimeter: 29.84 inHg - Observed at: KFCM ## 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 20121002022779A](https://openairdocs.org/incident/20121002022779A), Oct 2, 2012: Cirrus Design Corp SR20, Eden Prairie, MN, Substantial damage. Aircraft was landing on runway 18 and touched down approximately 1100 feet past the threshold. Length of runway 18 is 2691 feet. After touchdown the pilot… ## Docket (4 files) The files NTSB released with the investigation on October 25, 2012, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=85270. 4.5 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 1.1 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40379536&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF - Record of Conversation from Pilot (item 2, .PDF, 31 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40379537&FileExtension=.PDF&FileName=Record%20of%20Conversation%20from%20Pilot-Redacted.PDF - Flying Cloud Airport Diagram (item 3, .PDF, 121 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40379538&FileExtension=.PDF&FileName=Flying%20Cloud%20Airport%20Diagram-Master.PDF - Photo of skid marks at departure end of Runway 18 (item 4, .PDF, 3.3 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40379539&FileExtension=.PDF&FileName=Photo%20of%20skid%20marks%20at%20departure%20end%20of%20Runway%2018-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.