ASN Wikibase Occurrence # 164395
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information.
If you feel this information is incomplete or incorrect, you can submit corrected information.
| Date: | Monday 3 March 2014 |
| Time: | 10:32 |
| Type: |  Piper PA-46-350P Malibu Mirage |
| Owner/operator: | Private |
| Registration: | N9281F |
| MSN: | 4636095 |
| Year of manufacture: | 1997 |
| Total airframe hrs: | 1861 hours |
| Engine model: | Lycoming TIO-540-AE2A |
| Fatalities: | Fatalities: 1 / Occupants: 2 |
| Aircraft damage: | Substantial |
| Category: | Accident |
| Location: | Near Martis Peak, 7nm SE of Truckee-Tahoe Airport (KTRK), Truckee, CA -
 United States of America
|
| Phase: | Manoeuvring (airshow, firefighting, ag.ops.) |
| Nature: | Private |
| Departure airport: | Santa Ana, CA (KSNA) |
| Truckee, CA (KTRK) | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
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.
Accident investigation:
 |
|
Sources:
NTSB
https://flightaware.com/live/flight/N9281F
Location
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 04-Mar-2014 00:16 | Geno | Added |
| 04-Mar-2014 03:07 | Geno | Updated [Registration, Nature, Source, Narrative] |
| 04-Mar-2014 20:34 | Geno | Updated [Source, Damage, Narrative] |
| 12-Mar-2014 21:52 | Geno | Updated [Time, Phase, Source, Narrative] |
| 17-Apr-2016 22:59 | Aerossurance | Updated [Location, Narrative] |
| 21-Dec-2016 19:28 | ASN Update Bot | Updated [Time, Damage, Category, Investigating agency] |
| 29-Nov-2017 13:40 | ASN Update Bot | Updated [Operator, Other fatalities, Departure airport, Destination airport, Source, Narrative] |
Corrections or additions? ... Edit this accident description
The Aviation Safety Network is an exclusive service provided by:
Quick Links:
| ASN Home | Send Correction / Feedback |
| FSF Home | Disclaimer | Copyright |
| Contact Us | Privacy Policy |
| Press / Media |
CONNECT WITH US:
©2024 Flight Safety Foundation