# NTSB GAA19CA306: Cirrus SR22, N581SD, Denver, CO, June 2, 2019 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: June 2, 2019, 08:00 local (14:00 UTC) - Place: Denver, CO - Coordinates: 39.569999, -104.849441 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=39.5700&lon=-104.8494&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing-flare/touchdown: Hard landing](https://openairdocs.org/ntsb-events/092) - Highest injury: No injuries - Injuries: 2 uninjured - Status: Completed, report April 13, 2020 - Report: Approved by Office Director - NTSB office: General Aviation Accidents - Parties: FAA - NTSB case key (mKey): 99534 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=GAA19CA306 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/99534/pdf - Page: https://openairdocs.org/ntsb/GAA19CA306 ## Probable cause The pilot's improper control inputs on approach, which resulted in a hard landing near the runway edge, a runway excursion, and impact with runway lighting. Contributing to the accident was the flight instructor's delayed remedial action. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Use of equip/info: use of equip/system](https://openairdocs.org/ntsb-findings/02063015): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Cirrus Design SR22, 16 cases](https://openairdocs.org/ntsb-findings/02063015/cases.md?model=2130001), [All aircraft, 1,391 cases](https://openairdocs.org/ntsb-findings/02063015/cases.md) - [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Cirrus Design SR22, 94 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=2130001), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md) - [Performance/control parameters: directional control](https://openairdocs.org/ntsb-findings/01062020): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Cirrus Design SR22, 35 cases](https://openairdocs.org/ntsb-findings/01062020/cases.md?model=2130001), [All aircraft, 3,958 cases](https://openairdocs.org/ntsb-findings/01062020/cases.md) - [Action: delayed action](https://openairdocs.org/ntsb-findings/02041025): Personnel issues › Action/decision · Instructor/check pilot (probable cause); cases with it: [Cirrus Design SR22, 6 cases](https://openairdocs.org/ntsb-findings/02041025/cases.md?model=2130001), [All aircraft, 894 cases](https://openairdocs.org/ntsb-findings/02041025/cases.md) - [Object/animal/substance: runway/taxi/approach light](https://openairdocs.org/ntsb-findings/03022012): Environmental issues › Physical environment · Effect on operation (probable cause); cases with it: [Cirrus Design SR22, 2 cases](https://openairdocs.org/ntsb-findings/03022012/cases.md?model=2130001), [All aircraft, 106 cases](https://openairdocs.org/ntsb-findings/03022012/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: Miscellaneous/other](https://openairdocs.org/ntsb-events/900); cases with it: [Cirrus Design SR22, 23 cases](https://openairdocs.org/ntsb-events/900/sequence.md?model=2130001), [All aircraft, 1,556 cases](https://openairdocs.org/ntsb-events/900/sequence.md) - [Landing-flare/touchdown: Hard landing](https://openairdocs.org/ntsb-events/092) (defining event); cases with it: [Cirrus Design SR22, 11 cases](https://openairdocs.org/ntsb-events/092/sequence.md?model=2130001), [All aircraft, 2,102 cases](https://openairdocs.org/ntsb-events/092/sequence.md) - [Landing-flare/touchdown: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Cirrus Design SR22, 113 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=2130001), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) ## Analysis The pilot under instruction reported that he had recently purchased the airplane and that the accident occurred during his third dual-instruction flight in the airplane. The flight instructor requested a short approach to accomplish a simulated engine failure approach and landing. The pilot reported that ground instruction for the simulated engine failure was never accomplished. The instructor requested a simulated emergency landing on runway 17, which was denied by the tower controller due to traffic. The instructor then requested a simulated emergency landing on runway 28, which the tower controller approved. The airplane intersected the extended centerline of runway 28 at a 45° angle. The instructor told the pilot to reduce the power to idle and initiate the approach at 100 knots. The pilot recalled that, by the time glide speed was established, "we were on top of the numbers." The instructor told the pilot to turn right, but he believed that it was too late to turn and align the airplane with the runway heading. The airplane touched down hard on the left edge of the runway, exited the left side of the runway, and impacted runway lights. The flight instructor reported that he had provided the pilot ground instruction on how to execute a power-off landing at least twice. The instructor added that, when he told the pilot to start turning, he did not respond and that, after the airplane overshot the right turn point toward the runway, he took the controls, leveled the airplane, and then applied full power. After the airplane exited the left side of the runway, he pulled the power off. His hand was on top of the pilot's, who subsequently added full power. The instructor reduced the power, but the pilot added full power again. The instructor was able to steer the airplane and stop it on the runway. A review of surveillance footage of the accident provided by the Federal Aviation Administration revealed that, during the approach, the airplane converged on about a 45° angle toward runway 28. When the airplane approached the runway numbers, the right wing dropped rapidly, and the nose pitched up. Seconds later, the left wing dropped rapidly, and the airplane impacted the left side of the runway just before reaching the runway aim point markings. The airplane exited the left side of the runway and collided with runway lighting. The airplane remained upright and returned to the runway surface before coming to a stop about mid-field. The airplane sustained substantial damage to the elevator and vertical stabilizer. Both pilots reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation. ## Factual narrative The pilot under instruction, reported that he had recently purchased the airplane, and it was his third dual-instruction flight in the airplane. The flight instructor requested a short approach to accomplish a simulated engine failure approach and landing. The pilot asserted that ground instruction for the simulated engine failure was never accomplished The instructor requested a simulated emergency landing on runway 17, which was denied by the tower controller due to traffic. The request was made for runway 28 and approved by the tower controller. The airplane intersected runway 28 at a 45° angle. The instructor told the pilot to reduce the power to idle and initiate the approach at 100 knots airspeed. The pilot recalled that by the time glide speed was established "we were on top of the numbers." The pilot under instruction was told to, "turn right" but he felt that it was too late to turn and align the airplane with the runway heading. The airplane touched down hard on the left edge of runway 28, exited the left side of the runway and collided with runway lights, before the instructor steered the airplane back onto the runway and stopped. The flight instructor reported that he "had given the student ground on how to execute a power-off landing at least twice." During the approach, the airplane turned to the right and intersected a 45° angle toward the runway, the engine power was reduced, the airspeed remained within glide speed parameters, and the instructor told the pilot to, "start your turn," but he did not respond., The airplane overshot the right turn point toward the runway. The pilot applied hard right rudder, and then immediately applied hard left rudder. The instructor took the controls and leveled the airplane, and then applied full power. The airplane landed hard on the left edge of runway 28, it exited the left side of the runway and the instructor pulled the power off. His hand was on top of the pilot's, who subsequently added full power. The instructor reduced the power, but again the pilot added full power. The instructor was able to steer that airplane and bring it to a stop on the runway. Surveillance footage of the accident provided by the FAA, revealed that during approach, the airplane converged on about a 45° angle toward runway 28. When the airplane approached the runway numbers, the airplane's right wing dropped rapidly, and the nose pitched up. Seconds later, the left wing dropped rapidly, and the airplane impacted the left side of the runway, just prior to the runway aim point markings. The airplane exited the left side of the runway and collided with runway lighting. The airplane remained upright and returned to the runway surface before coming to a stop about mid-field. The airplane sustained substantial damage to the elevator, and the vertical stabilizer. Both pilot's reported that there were no mechanical malfunctions or failures with the airplane that would have precluded normal operation. ## Aircraft - Registration: [N581SD](https://openairdocs.org/aircraft/N581SD), registered now, S/N 3171, built 2008 (OpenAirDocs) - Reported make and model: Cirrus SR22 (Undesignat) - Registry model: [Cirrus Design SR22](https://openairdocs.org/model/cirrus-design-sr22) (registry code 2130001) (OpenAirDocs) - Registry engine: [Continental IO-550-N](https://openairdocs.org/engine/continental-io-550-n) (registry code 17215, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 3171 - Year built: 2008 - Airframe hours: 753 - Engines: Continental IO-550-N 315 horsepower reciprocating - Damage: Substantial damage - Flight: Instructional, Part 91 - Airworthiness certificate: Standard, Normal - Departed: APA, Denver, CO - Destination: APA, Denver, CO - Airport: APA, Centennial, runway 28, 4,800 × 75 ft, asphalt - Equipment: Electronic multifunction display, Auto-pilot, Airframe parachute, ADS-B, Stall warning system, Electronic primary flight display ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 70; injuries: none; private; airplane ratings: single-engine land; medical: class 3, without waivers/limitations; last flight review July 15, 2017; seat: left; restraint: 4-point; flight hours: 1,444 total, 7 in this make and model, 1,444 as pilot in command, 8 in the last 90 days, 7 in the last 30 days, 1 in the last 24 hours - Flight instructor; age 65; injuries: none; airline transport, commercial, flight engineer; airplane ratings: single-engine land, multi-engine land; instrument ratings: airplane; medical: class 2, with waivers/limitations; last flight review January 31, 2018; seat: right; restraint: 4-point; flight hours: 18,000 total, 67 in this make and model ## Weather - Conditions: Visual (VMC), Day - Wind: 210° at 10 knots - Visibility: 10 statute miles - Temperature: 63 °F, dew point 46 °F - Altimeter: 30.07 inHg - Observed at: KAPA ## 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 20190602005599A](https://openairdocs.org/incident/20190602005599A), Jun 2, 2019: Cirrus Design Corp SR22, Centennial, CO, Substantial damage. N581SD requested a short approach on runway 28. The approach was misjudged, and the aircraft bounced several times before coming to a rest approximately 3500FT… 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.