Cessna 340A accident near Santee, California, October 11, 2021
On October 11, 2021 at about 7:14 pm local time, a 1979 Cessna 340A, registered N7022G, was destroyed in an accident during approach (IFR initial approach) near Santee, California (Montgomery-Gibbs Executive Air airport). It was a personal 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
Loss of control due to spatial disorientation.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- October 11, 2021 · about 7:14 pm local time
- Place
- Santee, California · Montgomery-Gibbs Executive Air · map
- Type
- Accident
- Injuries
- 1 person was killed.
- Weather
- visual conditions (good weather)
- Aircraft
- Cessna 340A, built 1979 · all 340As on the register
- Registration
- N7022G · registry record · serial 340A0695
- Damage
- Destroyed
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The pilot was on a cross-country flight, receiving vectors for an instrument approach while in instrument meteorological conditions (IMC). The approach controller instructed the pilot to descend to 2,800 ft mean sea level (msl) until established on the localizer, and subsequently cleared the flight for the instrument landing system (ILS) approach to runway 28R, then circle to land on runway 23. About 1 minute later, the controller told the pilot that it looked like the airplane was drifting right of course and asked him if he was correcting back on course. The pilot responded “correcting, 22G.” About 9 seconds later, the pilot transmitted “SoCal, is 22G, VFR runway 23” to which the controller told the pilot that the airplane was not tracking on the localizer and subsequently canceled the approach clearance and instructed the pilot to climb and maintain 3,000 ft. As the pilot acknowledged the altitude assignment, the controller issued a low altitude alert, and provided the minimum vectoring altitude in the area. The pilot acknowledged the controller’s instructions shortly after. At this time, recorded advanced dependent surveillance-broadcast (ADS-B) data showed the airplane on a northwesterly heading at an altitude of 2,400 ft msl. Over the course of the following 2 minutes, the controller issued multiple instructions for the pilot to climb to 4,000 ft, which the pilot acknowledged; however, ADS-B data showed that the airplane remained between 2,500 ft and 3,500 ft. The controller queried the pilot about his altitude and the pilot responded, “2,500 ft, 22G.” The controller subsequently issued a low altitude alert and advised the pilot to expedite the climb to 5,000 ft. No further communication was received from the pilot despite multiple queries from the controller. ADS-B data showed that the airplane had begun to climb and reached a maximum altitude of 3,500 ft before it began a descending right turn. The airplane remained in the right descending turn at a descent rate of about 5,000 ft per minute until the last recorded target at 900 ft msl, located about 1,333 ft northwest of the accident site. Recorded weather conditions at the pilot’s intended destination airport about 21 minutes before the accident showed that the cloud ceilings were broken at 2,127 ft msl, overcast at 3,227 ft msl. The closest weather reporting station to the accident site, which was about 1.8 miles south, showed a broken cloud layer at 3,086 ft msl. The airplane had undergone a conversion to modern avionics about 11 months before the accident. No reference to any additional training to the installed avionics was found within the provided pilot records. While the pilot had previous experience with other brands modern avionics, the investigation was unable to determine if the pilot had previous experience or training for the specific model of modern avionics installed in the airplane. The controller had cleared the flight to fly the ILS approach to runway 28R, circle to land on runway 23, and ADS-B track data showed that the airplane was about to be established on the localizer when it started to veer off course to the right, ultimately into an area with minimum vectoring altitudes that required the controller to issue instructions to the pilot to climb. During the divergence from the instrument approach, the airplane was at an altitude above the reported base of the broken cloud layer and below the base of the overcast layer at the destination airport, which most likely placed the airplane in and out of IMC conditions. Ultimately, the airplane climbed back into IMC conditions. It could not be determined if the pilot had inadvertently misconfigured the avionics for the instrument approach. Continuing the instrument approach would have afforded the pilot the opportunity to fly a stabilized approach in protected airspace and safely descend below the cloud layer prior to conducting the circle to land on runway 23. Given the airplane was maneuvering in IMC, it placed the pilot in conditions conducive to the development of spatial disorientation. The accident circumstances, including the tightening descending turn, and the subsequent high-energy impact, are consistent with the known effects of spatial disorientation. Additionally, examination of the airframe and engines revealed no evidence of any preexisting anomalies that would have precluded normal operation. Therefore, it is likely that the pilot was experiencing the effects of spatial disorientation when the accident occurred.
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
- Other weather encounter during approach (IFR initial approach)
- Loss of control in flight during approach (IFR initial approach) defining event
- Collision with terrain or object (not controlled flight into terrain) during approach (IFR initial approach)
The NTSB's findings
- Personnel issues › Psychological › Perception/orientation/illusion › Spatial disorientation › Pilot
- Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Pilot
- Environmental issues › Conditions/weather/phenomena › Ceiling/visibility/precip › Low visibility › Decision related to condition
Pilot
- Certificate: commercial pilot
- Ratings: multi-engine land; single-engine land; instrument: airplane
- Flight time: 1,566.2 hours in all; 51.8 in the last 90 days; 26.9 in the last 30 days; 1,169.8 as pilot in command
- Last flight review: August 27, 2021
- Medical certificate: Class 1 (with waivers/limitations)
- Seat: unk
- Injury: fatal
The aircraft
- Airframe total time: 2,627.3 hours
- Last inspection: annual inspection, November 6, 2020
- Seats: 6
- Landing gear: retractable
- Engine 1: Continental Motors TSIO-520-NB (piston); 0 hours total
- Engine 2: Continental Motors TSIO-520-NB (piston); 0 hours total
- Fire on the ground
The flight
- Departed from: YUM Yuma AZ at 6:21 pm
- Destination: MYF San Diego CA
- Flight plan: IFR
Weather at the time
- Light: daylight
- Wind: from 200° at 12 knots, gusting 17
- Visibility: 10 statute miles
- Sky: broken clouds at 2,700 ft
- Temperature: 66°F (19°C), dew point 55°F (13°C)
- Altimeter: 29.80 inHg
- Observation at 11:55 am from KSEE, 2 miles away
Weather report (METAR): KSEE 111855Z 20012G17KT 10SM BKN027 19/13 A2980
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
24 documents, released by the NTSB on November 8, 2023. 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.
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
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 never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
