The U.S. aircraft register, updated daily
Accidents · NTSB WPR23FA027 · Final report

Cirrus Design CORP SR20 accident near San Diego, California, November 5, 2022

On November 5, 2022 at about 7:00 pm local time, a 2020 Cirrus Design CORP SR20, registered N700YZ, was substantially damaged in an accident during approach (VFR go-around) near San Diego, California (Montgomery-Gibbs Exec airport). It was an instructional flight under general aviation rules (Part 91). 1 person was killed. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

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.

Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.

What the record shows

Date
November 5, 2022 · about 7:00 pm local time · cases in 2022
Place
San Diego, California · Montgomery-Gibbs Exec · cases near this airport · map
Type
Accident
Injuries
1 person was killed.
Weather
visual conditions (good weather)
Aircraft
Cirrus Design CORP SR20, built 2020
Registration
N700YZ · registry record · serial 2599
Damage
Substantial damage
Flight
Instructional flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

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.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Loss of control in flight during approach (VFR go-around) defining event
  2. Aerodynamic stall/spin during approach (VFR go-around)
  3. Collision with terrain or object (not controlled flight into terrain) during approach (VFR go-around)

The NTSB's findings

  • Personnel issues › Task performance › Use of equip/info › Aircraft control › Student/instructed pilot
  • Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Angle of attack › Not attained/maintained

Dual student

  • Certificate: student
  • Flight time: 83 hours in all; 64.4 in this make and model
  • Medical certificate: Class 2 (without waivers/limitations)
  • Seat: left
  • Injury: fatal

The aircraft

  • Airframe total time: 1,147.3 hours
  • Last inspection: annual inspection, October 3, 2022; 48 hours since
  • Maximum gross weight: 3,150 lb
  • Seats: 5
  • Landing gear: fixed
  • Engine: Lycoming IO-390-C3B6 (piston); 818 hours total
  • Operator: Coast Air Center

The flight

  • Flight plan: none
  • Runway 28R, 4,598 ft by 150 ft

Weather at the time

  • Light: daylight
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 72°F (22°C), dew point 34°F (1°C)
  • Altimeter: 30.05 inHg
  • Observation at 11:53 am from KMYF

Weather report (METAR): KMYF 051853Z VRB05KT 10SM CLR 22/01 A3005 RMK AO2 SLP174 T02220011

Injuries

FatalSeriousMinorNone
Flight crew1

Photographs from the investigation 4 pictures from the NTSB's docket, as the NTSB released them

The NTSB's photographs with the NTSB's captions, at screen size. Open a picture to see it full size or to report one that should not be shown.

Documents from the investigation the NTSB's docket: the evidence folder behind the report

22 documents, released by the NTSB on May 16, 2024. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

#DocumentWhat it is
1 Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 PDF, 11 pages · our copy View Download
2 Flight Instructor Statement PDF, 1 page · our copy View Download
3 CFI Record of Conversation PDF, 1 page · our copy View Download
4 Witness Statement PDF, 2 pages · our copy View Download
5 Witness E-mail Record of Correspondence PDF, 2 pages · our copy View Download
6 Pilot Logbook ForeFlight Summary PDF, 1 page · our copy View Download
7 Operator Provided Video MOV file · our copy Download
8 Local Leo Video video · our copy View Download
9 Photo Array PDF, 4 pages · our copy View Download
10 Accident Site Examination PDF, 11 pages · our copy View Download
11 Airframe and Engine Examination PDF, 6 pages · our copy View Download
12 Pitch and Roll Servo Exams PDF, 5 pages · our copy View Download
13 Pitch and Roll Trim Switch Exams PDF, 7 pages · our copy View Download
14 Air Traffic Control Transcripts PDF, 4 pages · our copy View Download
15 Autopsy Memo for Record PDF, 1 page · our copy View Download
16 Toxicological Report PDF, 1 page · our copy View Download
17 Electronic Devices - Specialist's Factual Report PDF, 19 pages · our copy View Download
18 Attachment 1 to Electronic Devices - Specialist's Factual Report data file · our copy Download
19 Cirrus Statement of Party Representatives to NTSB Investigation PDF, 1 page · our copy View Download
20 Lycoming Statement of Party Representatives to NTSB Investigation PDF, 14 pages · our copy View Download
21 Release of Aircraft Wreckage, NTSB Form 6120.15 PDF, 1 page · our copy View Download
22 Evidence Control Forms PDF, 6 pages · our copy View Download

The same docket at the NTSB.

Connections how this case links to the rest of the register

Aircraft
Place

The whole map of how records connect · these connections as data: /graph/accident/WPR23FA027.json.

The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.