ASN Wikibase Occurrence # 30261
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: | Thursday 27 January 2000 |
| Time: | 08:36 |
| Type: |  Cessna 310R |
| Owner/operator: | Exec Air |
| Registration: | N87338 |
| MSN: | 310R0518 |
| Total airframe hrs: | 5085 hours |
| Engine model: | Continental IO-520M |
| Fatalities: | Fatalities: 0 / Occupants: 1 |
| Aircraft damage: | Destroyed |
| Category: | Accident |
| Location: | near Columbia Falls, 9 miles SW of Glacier Park IAP, Montana -
 United States of America
|
| Phase: | Approach |
| Nature: | Unknown |
| Departure airport: | Great Falls, MT (GTF) |
| Kalispell, MT (FCA) | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
The pilot stated that he had been cleared for and had flown the VOR runway 30 approach. Upon his arrival at the missed approach point, he did not have the runway or the airport environment in sight. He said he had heard that an aircraft that had preceded him to the airport had reported the weather to be better to the south and west of the airport, and had reported seeing the airport from the west side of the airport. The pilot stated that after he arrived at the missed approach point and did not have the runway or airport environment in sight, he continued to the west side of the airport and made a left turn, for a 'downwind for runway 02,' saying he intended to use the localizer frequency to help him find the runway. He then tuned the number one navigation receiver to the localizer frequency for the ILS runway 02 approach. He said he thought a left turn would align the aircraft with runway 02 and, if he did not see the runway, the left turn would place him back near the missed approach point and he would begin the missed approach from that point. The pilot told FAA inspectors that he did not acquire the runway or airport environment visually. He said the number two navigation receiver was tuned to the VOR frequency. He said he did not remember centering the CDI 9course deviation indicator) for navigation to the VOR for the missed approach, nor does he remember the localizer needle (navigation receiver number one) being centered. He offered no explanation as to how the aircraft wound up about eight miles north of the airport on the mountainside.
Probable Cause: Failure of the pilot-in-command to follow the prescribed instrument approach missed approach procedure.
Accident investigation:
 |
|
Sources:
NTSB: https://www.ntsb.gov/_layouts/ntsb.aviation/brief.aspx?ev_id=20001212X20433&key=1
FAA register: 2. http://registry.faa.gov/aircraftinquiry/NNum_Results.aspx?nNumberTxt=87338
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 27-Sep-2008 01:00 | ASN archive | Added |
| 12-Jun-2014 03:01 | Dr. John Smith | Updated [Time, Operator, Total fatalities, Total occupants, Other fatalities, Location, Country, Phase, Nature, Departure airport, Destination airport, Source, Damage, Narrative] |
| 12-Dec-2017 18:17 | ASN Update Bot | Updated [Time, Operator, Nature, 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