GAA19CA142

NTSB accident investigation · Cirrus SR22 · Tulsa, OK · February 20, 2019

Accident · No injuriesData collectionFinal report
Date
February 20, 2019, 17:00 local (23:00 UTC)
Place
Tulsa, OK
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Approach
Aircraft
N381DECirrus SR22
Defining event
Approach-VFR go-around: Loss of control in flight
Weather
Visual (VMC) · Day
Status
Completed · report September 26, 2019
Report
Approved by Office Director
NTSB office
General Aviation Accidents
Parties
FAA
FAA report
20190220010389A
Case key
99004

From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.

On this page

Probable cause

The pilot's failure to maintain a stabilized approach with a tailwind and his subsequent failure to maintain yaw control during an attempted go-around.

Findings · 4

NTSB’s coded findings. Those marked are part of the probable cause; the rest are factors or other findings. Under each, the cases with the same finding.

Performance/control parameters: descent/approach/glide pathAircraft › Aircraft oper/perf/capability · Not attained/maintainedCirrus Design SR22: 14 casesAll aircraft: 809 casesProbable cause
Performance/control parameters: yaw controlAircraft › Aircraft oper/perf/capability · Not attained/maintainedCirrus Design SR22: 2 casesAll aircraft: 149 casesProbable cause
Use of equip/info: aircraft controlPersonnel issues › Task performance · PilotCirrus Design SR22: 94 casesAll aircraft: 9,295 casesProbable cause
Wind: tailwindEnvironmental issues › Conditions/weather/phenomena · Effect on operationCirrus Design SR22: 9 casesAll aircraft: 594 cases

Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event is the one that best describes the accident. Under each, the cases with the same event anywhere in their sequence.

Analysis

The pilot reported that, while en route, he applied left rudder to stay coordinated and that he alternated his left and right legs due to muscle fatigue. He added that, during landing at the destination airport, the approach was stabilized and "felt normal" with the flaps set at 100%. During the landing flare, he used "very little rudder" to maintain centerline, and about 1 to 2 ft above the ground, the airplane suddenly yawed left about 30° to 45°. He added that there was not enough right rudder to maintain the airplane parallel with the runway, so he decided to go around. He applied power, and the airplane then yawed violently left and impacted the ground, exited the runway to the left, and came to rest in the grass left of a parallel taxiway. The airplane sustained substantial damage to the fuselage. The owner provided flight data from the accident flight. Examination of the data revealed that, within 25 seconds of the accident, the airplane descended from 782 to 619 ft mean sea level (msl) with the descent rate peaking around 1,019 ft per minute and the indicated airspeed decreasing from 86 to 60 knots. About 2 seconds before the accident, the pitch attitude peaked at 7° with a left roll of 16°. The airport elevation was about 638 ft msl. The airplane was also equipped with a crash-hardened recoverable data module (RDM). Examination of the data recovered from the RDM revealed that the airplane veered left, the power and pitch were momentarily increased, and the stall warning horn was on. The airplane manufacturer's recommended landing approach speed with flaps set to 100% was 80 to 85 knots. The aerodynamic stall speed at maximum gross weight was about 60 knots. The pilot reported that the wind was light and variable and not gusting. The RDM data revealed that the wind was from 359° at 5 knots. The pilot was landing the airplane on runway 19L. The Federal Aviation Administration inspector reported that he examined the airplane and verified rudder control continuity and noted that "everything was intact."

Factual narrative

The pilot reported that, while en route, he used left rudder to stay coordinated and alternated his left and right leg due to muscle fatigue. During landing at the destination airport, the approach was stabilized and "felt normal" with the flaps set at 100%. During the landing flare, he used "very little rudder" to maintain centerline, and, about 1 to 2 feet above the ground, the airplane suddenly yawed to the left about 30 to 45°. He added that there was not enough right rudder to maintain parallel with the runway, so he decided to go around. He applied power, the airplane yawed violently to the left, the airplane impacted the ground, exited the runway to the left, and came to rest in the grass to the left of a parallel taxiway. The airplane sustained substantial damage to the fuselage. The owner provided flight data from the accident flight. Examination of the data revealed that, within 25 seconds of the accident, the airplane descended from 782 ft mean sea level (msl) to 619 msl with descent rates peaking around 1019 ft per minute and the indicated airspeed decreased from 86 knots to 60 knots. About 2 seconds before the accident, the pitch attitude peaked at 7° with a left roll of 16°. The airport elevation was about 638 ft. The airplane was also equipped with a crash hardened Recoverable Data Module (RDM), a flight recording device installed in the tail of the airplane. Examination of the data recovered from the RDM and revealed that the airplane veered left, the power and pitch were momentarily increased, and the stall warning horn was on. The airplane manufacturer's recommended landing approach speed with flaps set to 100% was 80 to 85 knots. The aerodynamic stall speed at maximum gross weight was about 60 knots. The pilot reported that the wind was light and variable and not gusting. The RDM data revealed that the wind was from 359° at 5 knots. The pilot was landing the airplane on runway 19L. The Federal Aviation Administration inspector reported that he examined the airplane and verified rudder control continuity and that "everything was intact."

Aircraft

Registration
N381DE
Reported as
Cirrus SR22 (Undesignat)
Category
Airplane
Serial number
4526
Built
2017
Engine
Continental IO-550-N, reciprocating
Damage
Substantial damage
Flight
Business · Part 91
Airworthiness certificate
Standard, Normal
Departed
ELD · El Dorado, AR
Destination
RVS · Tulsa, OK
Flight plan
VFR
Airport
RVS · Richard Lloyd Jones Jr, runway 19L, 4,208 × 100 ft, asphalt
Equipment
Angle of attack indicator, Auto-pilot, Data recorder, Electronic multifunction display, Electronic primary flight display, Onboard weather, Stall warning system, Airframe parachute, ADS-B

Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

Flight crew

As NTSB recorded them. NTSB leaves out names.

Role
Pilot
Age
58
Injuries
None
Certificate
Private
Airplane ratings
Single-engine land
Instrument ratings
Airplane
Medical
Class 3, With waivers/limitations
Last flight review
April 17, 2017
Seat
Left
Restraint
4-point
Flight hours
1,133 total · 725 in this make and model · 1,063 as pilot in command · 81 in the last 90 days · 35 in the last 30 days · 4 in the last 24 hours

Weather

Conditions
Visual (VMC) · Day
Wind
250° at 4 knots
Visibility
10 statute miles
Lowest ceiling
None
Temperature
52 °F, dew point 30 °F
Altimeter
29.89 inHg
Observed at
KRVS

Docket · 6

The files NTSB released with the investigation on April 4, 2019, on NTSB’s docket system: statements, records, photos and specialists’ reports. 7.5 MB in all.

FAA reports on this event · 1

The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.