WPR14FA127 · Piper PA 46 350P
Farnell R Richard Trustee Piper PA 46 350P · Accident: loss of control in flight on approach
From John Wayne Orange County International Airport (KSNA) to Truckee Tahoe Airport (KTRK)
Event
- NTSB case
- WPR14FA127
- 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
Piper PA 46 350P
- Aircraft type
- Piper PA-46
- 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
- N9281F
- Operator
- Farnell R Richard Trustee
- Onboard fatalities
- Unknown
- Route
- From John Wayne Orange County International Airport (KSNA), Santa Ana, CATo Truckee Tahoe Airport (KTRK), Truckee, CA
- Aircraft age
- About 17 years (built 1997)
- 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
- 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
- Personnel issues › Action/decision
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The commercial pilot was conducting a personal flight. The airplane was en route to the destination airport from the south and was cleared via the initial approach fix for the published GPS approach. The pilot reported that he had the weather at the airport, which was overcast at 3,000 ft above ground level. For all arrivals except from the west, the GPS approach diagram depicts a racetrack procedure turn at the initial approach fix (IAF) to align with the final approach course. The air traffic controller instructed the pilot to cross the IAF and then cleared him for the GPS approach into the airport. The airplane crossed the IAF and made a right turn to parallel the final approach course, which was not the required procedure turn, and the pilot did not slow the airplane's airspeed. The controller terminated radar services.
The airplane then made a heading correction to intercept the final approach course but did not descend and continued to maintain its speed. The airplane remained northeast of the final approach course and 2,000 ft above the minimum descent altitude (MDA) all the way to the missed approach point. The pilot did not slow the airplane to an appropriate airspeed for the approach nor configure the airplane for landing. The pilot then announced that he had a missed approach to air traffic control (ATC) and made a left turn toward the depicted holding fix to the north. Instead of proceeding directly to the holding fix, the airplane continued its left turn for about 270 degrees and proceeded away from the fix. The pilot asked ATC for vectors to the holding fix. A controller replied that the airplane was below the minimum vectoring altitude and advised the pilot to proceed to the west toward lower terrain. The pilot stated that he was in instrument meteorological conditions and was picking up ice. Moments later, during the last minute of flight, the airplane entered a series of progressively lower altitude excursions southeast of the airport descending 1,300 ft, then climbing 700 ft, then descending 2,000 ft, then climbing 1,600 ft, and finally descending 1,300 ft and impacting terrain. The fact that the pilot did not execute the procedure turn after crossing the IAF, did not slow the airplane down, did not descend to the MDA, and did not climb to the required altitude or proceed in the direction of the holding fix after the missed approach point all indicate that the pilot had decreased situational awareness. Further, the final series of extreme altitude excursions are consistent with the pilot experiencing spatial disorientation.
After the accident, the pilot could not recall the events leading up to the accident. He did state that he normally approached the airport from the west. In that case, a right turn at the IAF to directly align with the final approach course would be the normal procedure. The pilot had an iPad that contained the approach plate for the approach being flown, and the approach had been displayed on the device 30 minutes before the execution of the approach, but it was not displayed any time after that. The pilot stated that he normally used the panel-mounted GPS navigation system in the airplane to conduct instrument approaches and that he was using that system at the time of the accident. Pilot records show that the he had not performed the required six instrument approaches within the 6 calendar months preceding the flight; thus, he was not instrument current to operate as pilot-in-command under instrument flight rules conditions.
Probable cause
The pilot’s failure to properly execute the missed approach in instrument conditions. Contributing to the accident were the pilot’s lack of instrument proficiency, as demonstrated by his failure to execute the required procedure turn to align with the final approach course and to configure the airplane for the approach, and his loss of situational awareness and the onset of spatial disorientation during the missed approach.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR14FA127
- Event ID
- 20140304X52659
- Case number
- WPR14FA127
- 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, coordinates. 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: f879e820aaf94f77d7f98fa68df6f0deb5fb2f89df6320c56d345a371728bc74; retrieved 2026-09-14T16:11:25.921Z.