Accident Piper PA-46-350P Malibu Mirage N35CX,
ASN logo
ASN Wikibase Occurrence # 43715
 
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 6 August 2007
Time:12:55
Type:Silhouette image of generic PA46 model; specific model in this crash may look slightly different    
Piper PA-46-350P Malibu Mirage
Owner/operator:Private
Registration: N35CX
MSN: 4636127
Year of manufacture:1997
Total airframe hrs:2042 hours
Engine model:Pratt & Whitney Canada PT6A-35
Fatalities:Fatalities: 4 / Occupants: 4
Aircraft damage: Destroyed
Category:Accident
Location:Sitka, AK -   United States of America
Phase: Approach
Nature:Private
Departure airport:Victoria, (CYYJ)
Destination airport:Sitka, AK (PASI)
Investigating agency: NTSB
Confidence Rating: Accident investigation report completed and information captured
Narrative:
The private, instrument-rated pilot, was on an IFR cross-country flight, and had been cleared for a GPS approach. He reported that he was 5 minutes from landing, and said he was circling to the left, to land the opposite direction from the published approach. The traffic pattern for the approach runway was right traffic. Instrument meteorological conditions prevailed, and the weather conditions included a visibility of 3 statute miles in light rain and mist; few clouds at 400 feet, 1,000 feet overcast; temperature, 55 degrees F; dew point, 55 degrees F. The minimum descent altitude, either for a lateral navigation approach, or a circling approach, was 580 feet, and required a visibility of 1 mile. The missed approach procedure was a right climbing turn. A circling approach north of the runway was not approved. Witnesses reported that the weather included low clouds and reduced visibility due to fog and drizzle. The airplane was heard, but not seen, circling several times over the city, which was north of the runway. Witnesses saw the airplane descending in a wings level, 30-45 degree nose down attitude from the base of clouds, pitch up slightly, and then collide with several trees and an unoccupied house. A postcrash fire consumed the residence, and destroyed the airplane. A review of FAA radar data indicated that as the accident airplane flew toward the airport, its altitude slowly decreased and its flight track appeared to remain to the left side (north) of the runway. The airplane's lowest altitude was 800 feet as it neared the runway, and then climbed to 1,700 feet, where radar contact was lost, north of the runway. During the postaccident examination of the airplane, no mechanical malfunction was found. Given the lack of any mechanical deficiencies with the airplane, it is likely the pilot was either confused about the proper approach procedures, or elected to disregard them, and abandoned the instrument approach prematurely in his attempt to find the runway. It is unknown why he decided to do a circle to land approach, when the tailwind component was slight, and the shorter, simpler, straight in approach was a viable option. Likewise, it is unknown why he flew towards rising terrain on the north side of the runway, contrary to the published procedures. From the witness statements, it appears the pilot was "hunting" for the airport, and intentionally dove the airplane towards what he perceived was an area close to it. In the process, he probably saw trees and terrain, attempted to climb, but was too low to avoid the trees.
Probable Cause: The pilot's failure to maintain altitude/distance from obstacles during an IFR circling approach, and his failure to follow the instrument approach procedure. Contributing to the accident was clouds.

Accident investigation:
cover
  
Investigating agency: NTSB
Report number: ANC07FA073
Status: Investigation completed
Duration:
Download report: Final report

Sources:

NTSB: https://www.ntsb.gov/_layouts/ntsb.aviation/brief.aspx?ev_id=20070816X01192&key=1

Location

Revision history:

Date/timeContributorUpdates
28-Oct-2008 00:45 ASN archive Added
21-Dec-2016 19:24 ASN Update Bot Updated [Time, Damage, Category, Investigating agency]
04-Dec-2017 18:49 ASN Update Bot Updated [Operator, Other fatalities, Departure airport, Source, Narrative]

Corrections or additions? ... Edit this accident description

The Aviation Safety Network is an exclusive service provided by:
Quick Links:

CONNECT WITH US: FSF on social media FSF Facebook FSF Twitter FSF Youtube FSF LinkedIn FSF Instagram

©2024 Flight Safety Foundation

1920 Ballenger Av, 4th Fl.
Alexandria, Virginia 22314
www.FlightSafety.org