ASN Wikibase Occurrence # 121202
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: | Saturday 19 March 2011 |
Time: | 16:05 |
Type: | Cessna T310R |
Owner/operator: | Private |
Registration: | N4914A |
MSN: | 310R1400 |
Year of manufacture: | 1978 |
Total airframe hrs: | 4259 hours |
Engine model: | Continental TSIO-520 |
Fatalities: | Fatalities: 1 / Occupants: 1 |
Aircraft damage: | Substantial |
Category: | Accident |
Location: | West of Montana Tech and north of Interstate 90 -
United States of America
|
Phase: | En route |
Nature: | Private |
Departure airport: | Great Falls, MT (GTF) |
Destination airport: | Butte, MT (BTM) |
Investigating agency: | NTSB |
Confidence Rating: | Accident investigation report completed and information captured |
Narrative:Shortly before embarking on the flight, the instrument-rated pilot filed an instrument flight plan and checked the weather using a computer-based filing system. At that time, the destination airport was reporting visual meteorological conditions, with similar conditions forecast for the planned arrival time. The pilot did not list an alternate airport in the flight plan. About halfway through the flight, the pilot contacted the air traffic controller responsible for the destination airport’s airspace. By that time, the weather conditions at the destination had deteriorated, with reports of snow and fog and visibility below the instrument approach minimums. The controller provided updated weather information and asked the pilot if he wanted to continue with the initial approach. He responded that he did and that he would divert to an alternate airport if necessary. The pilot was then cleared for the approach, and the airplane began to descend toward the initial approach fix (IAF).
Shortly thereafter, a scheduled air carrier airplane destined for the same airport contacted the same controller. The controller relayed the weather information, and the crew of that airplane responded that they would delay the approach to see if the weather conditions improved. About that time, the accident airplane reached the IAF and began the approach. The air carrier pilot then requested and received approval to divert to an alternate airport due to the weather conditions. The accident pilot most likely did not hear this exchange because he had switched to the airport frequency. Due to limitations in radar coverage, the air traffic controller was not able to see the airplane once it had descended to the approach altitude.
About 4 minutes after the air carrier airplane began to divert, the accident pilot reported that he was performing a missed approach. The controller provided missed approach instructions and asked for the pilot's intentions. The pilot read back the instructions but did not state his intentions. The controller asked if he would like to divert to the alternate airport, and, after a series of delayed and partial responses from the pilot, a call of "Mayday Mayday" was heard on the controller's frequency. For the next 35 minutes, the controller unsuccessfully attempted to contact the pilot. During that period, an air medical flight also canceled a landing approach into the airport due to deteriorating weather conditions. Multiple witnesses reported the sounds of a loud, low-flying airplane northwest of the airport about the time of the landing attempt. The witnesses reported the sudden onset of a gusting wind, heavy snow, low visibility, and ice accumulations during that period.
The airplane wreckage was located a few miles from the witnesses, about midway between the airport and the missed approach hold location. The wreckage distribution and flight instrument readings were indicative of a high-speed, steep nose-down, left-turning descent into the ground, with a heading almost opposite the direction of the missed approach route. Engine instrument indications, and both the engine and propeller damage signatures, were consistent with the engines producing similar amounts of power at the time of impact. The airplane was equipped with instruments and systems required for flight in instrument meteorological conditions (IMC) and flight into known icing. Additional equipment included an autopilot and a global positioning system (GPS) navigation and communication transceiver capable of receiving and displaying current weather information via satellite. Impact damage prevented a determination of the operational status of those systems.
Available ground-based radar tracking data indicated smooth heading and altitude changes and minimal altitude deviations prior to the pilot being cleared for the approach, consistent with autopilot use. According to the prior owner of the airplane, the autopilot was susceptible to becoming disengaged during turbulent conditions, and, as such, it is possible that at some point during the appr
Probable Cause: The pilot's loss of airplane control during the missed approach for undetermined reasons. Contributing to the accident was the rapid and unforecast deterioration of the weather conditions to below the landing minimum and the pilot's decision to attempt the approach despite his knowledge of those conditions.
Accident investigation:
|
| |
Investigating agency: | NTSB |
Report number: | WPR11FA170 |
Status: | Investigation completed |
Duration: | 1 year 1 month |
Download report: | Final report |
|
Sources:
NTSB
FAA register:
http://billingsgazette.com/news/state-and-regional/montana/article_2b0478c8-c8d7-5850-b155-19d41260f29c.html http://mtstandard.com/news/local/article_f6b02e88-529f-11e0-b3b2-001cc4c002e0.html http://registry.faa.gov/aircraftinquiry/NNum_Results.aspx?NNumbertxt=N4914A Location
Revision history:
Date/time | Contributor | Updates |
20-Mar-2011 06:28 |
gerard57 |
Added |
20-Mar-2011 08:00 |
Alpine Flight |
Updated [Aircraft type, Registration, Cn, Operator, Other fatalities, Departure airport, Destination airport, Source] |
21-Dec-2016 19:25 |
ASN Update Bot |
Updated [Time, Damage, Category, Investigating agency] |
27-Nov-2017 16:45 |
ASN Update Bot |
Updated [Operator, Other fatalities, Departure airport, Destination airport, Source, Narrative] |
The Aviation Safety Network is an exclusive service provided by:
CONNECT WITH US:
©2024 Flight Safety Foundation