FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

GAA19CA142 · Cirrus SR22 Undesignat

20 Feb 2019 · Tulsa, OK, United States

Cirrus SR22 Undesignat · Accident: loss of control in flight on approach

From South Arkansas Regional Airport at Goodwin Field (ELD) to Tulsa Riverside Airport (RVS)

Report a problem

Event

NTSB case
GAA19CA142
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Cirrus SR22 Undesignat

Aircraft type
Cirrus SR22
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N381DE
Operator
Unknown
Onboard fatalities
Unknown
Route
From South Arkansas Regional Airport at Goodwin Field (ELD), El Dorado, ARTo Tulsa Riverside Airport (RVS), Tulsa, OK
Aircraft age
About 2 years (built 2017)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Approach · VFR go-around
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Loss of control in flight
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

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."

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.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record GAA19CA142
Event ID
20190220X00053
Case number
GAA19CA142
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: b49f4c25b4d32a0366dfbf9b771fcae9b144f4618238a64c595b8c06deffeede; retrieved 2026-09-16T08:36:19.166Z.