Bert Mooney International Airport
Aircraft Accident/Incident Report

Butte, Montana 59701
Saturday, March 19, 2011 16:05 MDT

NTSB Narrative Summary Released at Completion of Accident

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 approach the pilot was forced to revert to flying the airplane manually. Under such circumstances, the pilot's workload would have rapidly increased. Additionally, the likely accumulation of ice on the airplane's airframe would have reduced flight performance and added to his workload as he attempted to monitor the ice accumulation and operate the deice system. The pilot had recently purchased the airplane and likely had minimal solo experience flying it in IMC. The airplane was about 2 months overdue for its annual inspection, and 12 months overdue for its transponder, static, and altitude reporting systems check. However, postaccident examination of the airframe remnants did not reveal any failures or malfunctions which would have precluded normal operation. The engines exhibited indications of wear that would have resulted in a gradual reduction in engine power over its life, rather than a sudden loss of power. Although the severe weather conditions were not forecast, the pilot was accurately advised of the deteriorating conditions by the controller prior to the approach, and he would have had access to airport terminal reports via the airplane's radio and his GPS navigation system. The lack of a filed alternate airport indicates that the pilot was not prepared for the severity of the weather conditions. The airplane was carrying ample reserves of fuel, with enough to return to the departure airport if necessary.

NTSB Probable Cause Narrative

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.

Event Information

Type of Event Accident
Event Date 3/19/2011
Event Day of the Week Saturday
Time of Event 1605
Event Time Zone Mountain Daylight Time
Event City Butte
Event State MONTANA
Event Country --
Zipcode of the event site 59701
Event Date Year 2011
Event Date Month 3
MidAir Collision Indicator No
On Ground Collision occurred ? No
Event Location Latitude 460033n
Event Location Longitude 1123501w
Event Location Airport Bert Mooney International
Event Location Nearest Airport ID BTM
Indicates whether the acc/inc occurred off or on an airport Off Airport/Airstrip
Distance from airport in statute miles 6
Degrees magnetic from airport --
Airport Elevation 5550
Weather Briefing Completeness --
Investigator's weather source Weather Observation Facility
Time of the weather observation 1553 Mountain Daylight Time
Direction of event from weather observation facility (degrees) 130
Weather Observation Facility ID BTM
Elevation of weather observation facility 5550
Distance of event from weather observation facility (units?) 6
Time Zone of the weather observation MDT
Lighting Conditions Day
Lowest Ceiling Height 400
Lowest Non-Ceiling Height --
Sky/Lowest/Cloud Conditions --
Sky Condition for Lowest Ceiling Broken
Visibility Runway Visual Range (Feet) --
Visibility Runway Visual Value (Statute Miles) --
Visibility (Statute Miles) 0
Air Temperature at event time (in degrees celsius) -1
Dew Point at event time (in degress fahrenheit) -2
Wind Direction (degrees magnetic) 300
Variable Wind Indicator Wind direction could be determined
Wind Speed (knots) 8
Wind Velocity Indicator --
Wind Gust Indicator Not Gusting
Wind Gust (knots) --
Altimeter Setting at event time (in. Hg) 29.63
Density Altitude (feet) --
Intensity of Precipitation --
METAR weather report --
Event Highest Injury Fatal
On Ground, Fatal Injuries --
On Ground, Minor Injuries --
On Ground, Serious Injuries --
Injury Total Fatal 1
Injury Total Minor --
Injury Total None --
Injury Total Serious --
Injury Total All 1
Investigating Agency NTSB
NTSB Docket Number (internal use) 29697
NTSB Notification Source FAA ROC
NTSB Notification Date --
NTSB Notification Time --
Fiche Number and/or location -used to find docket information --
Date of most recent change to record Mar 2 2012 2:30PM
User who most recently changed record coos
Basic weather conditions Instrument Meteorological Cond
FAA District Office --

Aircraft Involved

Aircraft #1

Aircraft Registration Number N4914A
NTSB Number WPR11FA170
Missing Aircraft Indicator --
Federal Aviation Reg. Part Part 91: General Aviation
Type of Flight Plan filed IFR
Flight plan Was Activated? Yes
Damage Substantial
Aircraft Fire Ground
Aircraft Explosion None
Aircraft Manufacturer's Full Name CESSNA
Aircraft Model T310R
Aircraft Series Identifier --
Aircraft Serial Number 310R1400
Certified Max Gross Weight 5680
Aircraft Category Airplane
Aircraft Registration Class --
Aircraft is a homebuilt? No
Flight Crew Seats --
Cabin Crew Seats --
Passenger Seats --
Total number of seats on the aircraft 6
Number of Engines 2
Fixed gear or retractable gear Retractable
Aircraft, Type of Last Inspection Annual
Date of Last Inspection Dec 11 2009 12:00AM
Airframe hours since last inspection 150
Airframe Hours 4259
ELT Installed Yes
ELT Activated No
ELT Aided Location of Event Site No
ELT Type C91-A
Aircraft Owner Name DAEDALUS HOLDINGS LLC
Aircraft Owner Street Address --
Aircraft Owner City Butte
Aircraft Owner State MT
Aircraft Owner Country USA
Aircraft Owner Zipcode 59701
Operator is an individual? Yes
Operator Name David G Gates
Operator Same as Owner? No
Operator Is Doing Business As --
Operator Address Same as Owner? No
Operator Street Address --
Operator City Butte
Operator State MT
Operator Country USA
Operator Zip code 59701
Operator Code --
Owner has at least one certificate None
Other Operator of large aircraft? No
Certified for Part 133 or 137 Operation --
Operator Certificate Number --
Indicates whether an air carrier operation was scheduled or not --
Indicates Domestic or International Flight --
Operator carrying Pax/Cargo/Mail --
Type of Flying (Per_Bus / Primary) Personal
Second Pilot on Board No
Departure Point Same as Event No
Departure Airport Code GTF
Departure City Great Falls
Departure State MT
Departure Country USA
Departure Time 1520
Departure Time Zone MDT
Destination Same as Local Flt crash at destination city
Destination Airport Code BTM
Destination City Butte
Destination State MT
Destination Country USA
Specific Phase of Flight --
Report sent to ICAO? --
Evacuation occurred --
Date of most recent change to record Mar 2 2012 2:30PM
User who most recently changed record coos
Since inspection or accident Last Inspection
Event Location Runway Number and Location 15
Runway Length 9001
Runway Width 150
Sight Seeing flight No
Air Medical Flight No
Medical Flight --