# NTSB SEA00LA040: Cessna 310R, N87338, Columbia Falls, MT, January 27, 2000 - Type: NTSB accident investigation - Classification: Accident · Serious injuries · Limited investigation · Final report - Date: January 27, 2000, 08:36 local (15:36 UTC) - Place: Columbia Falls, MT - Coordinates: 48.41082, -114.149108 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=48.4108&lon=-114.1491&mi=10 - Phase of flight: [Maneuvering](https://openairdocs.org/ntsb-phases/450) (OpenAirDocs' grouping) - Highest injury: Serious injuries - Injuries: 1 serious - Status: Completed, report December 4, 2000 - Report: Approved by Office Director - NTSB case key (mKey): 48588 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=SEA00LA040 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/48588/pdf - Page: https://openairdocs.org/ntsb/SEA00LA040 ## Probable cause Failure of the pilot-in-command to follow the prescribed instrument approach missed approach procedure. ## Analysis 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. ## Factual narrative On January 27, 2000, at 0836 mountain standard time, a Cessna 310R, N87338, was destroyed when it collided with terrain while maneuvering near Columbia Falls, Montana, after declaring a missed approach at Glacier International Airport, about nine miles southwest of the accident site. The airline transport pilot was the sole occupant of the airplane, which was conducting a check-hauling cargo flight under 14 CFR 135; an instrument flight plan had been filed for the flight. Instrument meteorological conditions prevailed in the vicinity at the time of the accident. The ELT actuated, and was instrumental in locating the crash site. The airplane burned after impact. The pilot was hypothermic at the time he was rescued, after about 1400. Sheriff's office personnel observed that the airplane came to rest at about 4330 feet MSL, at 48 24.58N; 114 07.77W. The wreckage distribution path was approximately 75 yards, up-slope, with a slope of 45 degrees up, transitioning to approximately 60 degrees up-slope. After he was hospitalized, the pilot stated to sheriff's office personnel that he had seen vegetation, and had applied full aft elevator before impact. In an interview conducted by FAA inspectors, the pilot stated that he had been cleared for the VOR runway 30 approach, flew that approach, and-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, a Cessna 208, 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 told FAA inspectors 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, and tuned the number one nav 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 nav was tuned to the VOR frequency. He said he did not remember centering the CDI for navigation to the VOR for the missed approach, nor does he remember the localizer needle (nav one) being centered. He offered no explanation as to how the aircraft wound up about eight miles north of the airport on the mountainside. The published instrument approach procedure for runway 30 calls for tracking outbound from the VOR on the 316 radial, to a missed approach point 6.4 nautical miles from the VOR, with a descent to a minimum descent altitude of 3480 feet for a straight-in approach. Missed approach calls for a climbing left turn direct to the VOR/DME. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - In flight collision with terrain/water, maneuvering - missed approach - not followed, pilot in command (cause) ## Aircraft - Registration: [N87338](https://openairdocs.org/deregistered/N87338-2000-07-06), registration cancelled 2000-07-06, S/N 310R0518 (OpenAirDocs) - Reported make and model: Cessna 310R - Registry model: [Cessna 310R](https://openairdocs.org/model/cessna-310r) (registry code 2074245) (OpenAirDocs) - Category: Airplane - Serial number: 310R0518 - Airframe hours: 5085 - Engines: Continental IO-520M 285 horsepower reciprocating - Damage: Destroyed - Fire: On-Ground - Flight: Part 135 - Registered owner: Exec Air - Airworthiness certificate: Standard, Normal - Last inspection: 100 hour, December 7, 1999, 89 hours before - Departed: GTF, GREAT FALLS, MT - Destination: FCA, KALISPELL, MT - Flight plan: IFR ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 50; airline transport; airplane ratings: multi-engine land, single-engine land; instrument ratings: airplane; medical: class 2, valid medical--w/ waivers/lim; seat: left; flight hours: 6,700 total, 1,550 in this make and model, 6,100 as pilot in command, 183 in the last 90 days, 53 in the last 30 days, 3 in the last 24 hours ## Weather - Conditions: Instrument (IMC), Day - Wind: 230° at 3 knots - Visibility: 2.5 statute miles - Lowest ceiling: 2,600 ft broken - Temperature: 27 °F, dew point 27 °F - Altimeter: 30.00 inHg - Observed at: KFC, 9 nm away ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20000127008319A](https://openairdocs.org/incident/20000127008319A), Jan 27, 2000: Cessna 310R, Kalispell, MT, No damage. (-23) After arriving at map during VOR-30 approach to fca, pilot failed to execute missed approach, manuevering a/c inimc in an attempt to locate airport… From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.