ANC07FA073 · Piper PA-46-350P
Piper PA-46-350P · Accident: in flight collision with object on approach
From Victoria International Airport (CYYJ) to Sitka Rocky Gutierrez Airport (PASI)
Event
- NTSB case
- ANC07FA073
- 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
- 4 · 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
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
- N35CX
- Operator
- Robert Hendrickson
- Onboard fatalities
- Unknown
- Route
- From Victoria International Airport (CYYJ), VictoriaTo Sitka Rocky Gutierrez Airport (PASI), Sitka, AK
- 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 · circling (IFR)
- 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
- In flight collision with object
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- 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 › Altitude/clearance, not maintained
- Pilot in command › IFR procedure, not followed
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB 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.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ANC07FA073
- Event ID
- 20070816X01192
- Case number
- ANC07FA073
- 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: 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: c53f1c03cc3416aa4431114920d4f8881bb0c34b4157d77ae3cec972415acb02; retrieved 2026-09-20T16:23:07.387Z.