FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR23FA027 · Cirrus Design Corp SR20

5 Nov 2022 · San Diego, CA, United States

Coast Air Center Cirrus Design Corp SR20 · Accident: loss of control in flight on approach

Report a problem

Event

NTSB case
WPR23FA027
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
1 · 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 Design Corp SR20

Aircraft type
Cirrus SR20
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
N700YZ
Onboard fatalities
Unknown
Route
From not recordedTo not recorded
Aircraft age
About 2 years (built 2020)
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 solo student pilot was conducting pattern work at the accident airport. Video footage from around the airport as well as witness statements showed the accident airplane overfly the runway at a low altitude and high rate of speed. While over the runway the airplane made several pitch up and down oscillations and, when it neared the departure end of the runway, the airplane pitched up and entered into a steep right roll, followed by the nose dropping and the airplane impacting the ground.

Review of recorded communication at the accident airport revealed that when the accident airplane was on final approach to land, the controller instructed the accident pilot to sidestep to the left and go around. There was no response from the accident pilot, and the controller repeated the instruction to go around, without a response. During this timeframe, a radio transmission about a trim problem, thought to be from the accident pilot, was heard on frequency. It is likely that while on final approach to land, with the airplane’s flaps at 50%, and the airplane’s indicated air speed reaching 140 knots, the increased camber from flap deflection increased lift, primarily on the rear portion of the wing and produced a nose-down pitching moment which may have caused the airplane to pitch down. However, with no change in the airplane’s trim position, it mistakenly led the pilot to believe there was a malfunction with the trim, which resulted in the pitch oscillations observed in the witness-provided video and the recoverable data module (RDM).

Postaccident examination of the airframe and engine revealed no evidence of a mechanical failure or malfunction that would have precluded normal operation.

A review of the RDM data showed that while on final approach to land, the indicated flap position changed from 100% to the 50% position and the airplane’s airspeed continued to increase gradually, reaching a maximum of 140 knots indicated. The recorded data showed that, when the airplane was near the departure end of the runway, with an indicated air speed of 125 knots, the airplane pitched up 20° and banked 13°. The airplane then entered a steep right roll, the electronic stability and protection (ESP) system activated in roll mode as the airplane exceeded a 20° pitch down attitude and 70° bank, the stall warning sounded, and the recording ended. The student pilot likely exceeded the airplane’s critical angle of attack during a turn, which resulted in an aerodynamic stall and an impact with terrain.

Probable cause

The student pilot’s exceedance of the critical angle of attack during a go-around, resulting in an aerodynamic stall and impact with terrain following a non-stabilized approach to land.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR23FA027
Event ID
20221105106252
Case number
WPR23FA027
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, cause areas. 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: 412ba51e23b89a44688f7605041aba9d19422998db057e3d28f499a07696ae47; retrieved 2026-09-15T07:53:58.179Z.