FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX05FA193 · Mooney M20C

1 Jun 2005 · Van Nuys, CA, United States

Mooney M20C · Accident: loss of control in flight on approach

From John Wayne Orange County International Airport (KSNA) to Van Nuys Airport (KVNY)

Report a problem

Event

NTSB case
LAX05FA193
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
Instrument Meteorological Cond

Mooney M20C

Aircraft type
Mooney M20
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
N6574U
Operator
Yian Chang
Onboard fatalities
Unknown
Route
From John Wayne Orange County International Airport (KSNA), Santa Ana, CATo Van Nuys Airport (KVNY), Van Nuys, CA
Aircraft age
Not recorded
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 · IFR missed approach
First occurrenceThe 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
Destroyed

Cause areas

  • Pilot in command › Aircraft control, not maintained
  • Pilot in command › Operation with known deficiencies in equipment, performed
  • Pilot in command › Spatial disorientation

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

NTSB narrative

The airplane departed from controlled flight during a missed approach and collided with hilly terrain. The non-instrument rated private pilot departed, at night, to an airport located about 40 miles to the north. While en route, the pilot contacted the terminal radar approach control (TRACON) specialist on duty and was subsequently advised that weather conditions were IFR at the pilot's intended destination airport. The pilot responded by saying he was going to try to find a VFR route. A review of archived radar data revealed that the accident airplane flew to various locations around the accident airport at altitudes above the underlying overcast cloud layer. The pilot then contacted the TRACON specialist and requested the ILS runway 16R approach at the accident airport. A review of air-to-ground communications tapes, transcripts, and archived radar data, revealed that the accident pilot was unable to intercept the glide slope and localizer for the ILS approach to runway 16R, or to maintain an assigned altitude or heading. Examination of the radar data for the pilot's attempted ILS approach showed that the airplane crossed the final approach course, 161 degrees, from the west between the initial approach fix and the outer marker. The airplane's track overshot the final approach course to the east and then corrected back so that it was on course at the outer marker. The track then deviated to the east again and corrected back to the final approach course, which was then followed by a 90-degree turn away from the final approach course to the west. The track proceeded westerly for 27 seconds, climbing from 2,100 to 2,500 feet and then down to 2,400 feet. The track turned south for 32 seconds, climbing from 2,400 feet to 3,000 feet. The last leg of the track proceeded northwesterly for the final 12 seconds, and the altitude descended from 3,000 feet to 2,600 feet, to 2,400 feet, to the accident elevation at 1,253 feet. Impact forces destroyed the airplane. According to the airplane's owner, the attitude gyro indicated a 10-degree left angle of bank when the airplane was in level flight. No preaccident mechanical anomalies were discovered during the investigation. At the time of the accident the reported weather was 1,400 feet overcast, with tops estimated at 3,000 feet. The weather forecast products available at the time of the pilot's departure predicted marginal VFR to IFR conditions at the destination, with ceilings occasionally below 1,000 feet and visibilities below 3 miles.

Probable cause

The pilot's decision to attempt flight into instrument meteorological conditions, which resulted in the pilot's loss of aircraft control due to spatial disorientation. Factors in the accident were haze and low ceilings, the night lighting condition, an undetermined attitude gyro problem, and the pilot's lack of qualification/experience for flight in instrument conditions.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX05FA193
Event ID
20050610X00750
Case number
LAX05FA193
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: local date, investigation status. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2005-06-02.
  • API snapshot SHA-256: 67d62a5cfda71e3ce01d1aa60f1ef4476c81813297d3295e4b0aba714ebb2e38; retrieved 2026-09-20T18:01:55.566Z.