code

MT

Crash of a Learjet 55 Longhorn in Livingston

Date & Time: Jan 11, 2024 at 0837 LT
Type of aircraft:
Operator:
Registration:
N558RA
Flight Type:
Survivors:
Yes
Schedule:
Pontiac - Livingston
MSN:
55-086
YOM:
1983
Flight number:
RAX698
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The crew departed Pontiac-Oakland County Airport on a cargo service to Livingston-Mission Field Airport (flight RAX698). After touchdown on runway 22, the airplane was unable to stop within the remaining distance and overran. It went down into a ravine, lost its undercarriage and came to rest with both engines torn off. Both crew members evacuated safely.

Crash of a Beechcraft B200 Super King Air in Poplar

Date & Time: Jan 18, 2023 at 0818 LT
Operator:
Registration:
N200EJ
Survivors:
Yes
Schedule:
Billings - Poplar
MSN:
BB-1884
YOM:
2004
Location:
Crew on board:
2
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
4242
Captain / Total hours on type:
2068.00
Copilot / Total flying hours:
10301
Copilot / Total hours on type:
4137
Aircraft flight hours:
4538
Circumstances:
The pilot reported that while on approach for landing, the airplane started to lose altitude quickly. After the co-pilot noticed the high decent rate and the slow airspeed, he advised the pilot to add power. However, the airplane continued to descend and impacted terrain in a right wing and nose low attitude, about 30 yards short of the runway approach threshold, which resulted in substantial damage to the right wing. The pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation.
Probable cause:
The pilot’s failure to maintain adequate airspeed and descent rate during the landing approach, which resulted in an impact with terrain short of the runway threshold.
Final Report:

Crash of a Piper PA-42-1000 Cheyenne 400LS in Lewistown

Date & Time: Dec 13, 2022 at 1006 LT
Type of aircraft:
Operator:
Registration:
C-GZPU
Survivors:
Yes
Schedule:
Great Falls – Lewistown
MSN:
42-5527011
YOM:
1984
Crew on board:
2
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
After landing on runway 08 at Lewistown Airport, the twin engine airplane started to skid then veered off runway to the left. While contact a snow covered terrain, it slid for few dozen metres and came to rest with its left wing severely damaged. All three occupants evacuated safely.

Crash of a Cessna 425 Conquest I in Helena

Date & Time: Aug 11, 2021 at 0900 LT
Type of aircraft:
Operator:
Registration:
N783MB
Flight Type:
Survivors:
Yes
Schedule:
Faribault - Missoula
MSN:
425-0103
YOM:
1982
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
6000
Captain / Total hours on type:
800.00
Aircraft flight hours:
9576
Circumstances:
The pilot stated that on the morning of the accident he filled both wing fuel tanks to full. After takeoff, he climbed to his planned cruise altitude of 24,000 ft mean sea level (msl). While en route to his destination, the pilot reported that the left engine experienced a flame-out. The pilot opted to divert from the originally planned destination and descended. When the airplane was about 7,900 ft msl, the pilot reported that the right engine experienced a loss of power and that he was not going to be able to make it to the airport. Shortly thereafter, the airplane collided with trees and the airplane came to rest with the right wing and empennage severed from the fuselage.
Probable cause:
A flameout of both engines due to fuel starvation for reasons that could not be determined due to the airplane’s damage. There was fuel in the wing tanks at the time of the impact. Postaccident examination of the wreckage did not reveal any anomalies. A partial amount of fuel was found in both of the filter bowls, but it is unknown if fuel was able to reach the engines. A complete examination of the fuel system could not be completed due to the damage incurred to the airplane at impact. Both engines flaming out within a short time of one another is likely indicative of a fuel supply or delivery issue; however, the nature of the problem could not be identified during postaccident examination.
Final Report:

Crash of a Piper PA-31T Cheyenne I in Billings: 1 killed

Date & Time: Apr 20, 2020 at 0950 LT
Type of aircraft:
Operator:
Registration:
N926K
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Billings - Billings
MSN:
31-8004046
YOM:
1980
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
12955
Aircraft flight hours:
4696
Circumstances:
Air traffic control communications revealed that the pilot requested to take off from the departure runway so that he could perform traffic pattern work and return for a landing on the left adjacent runway. Shortly after takeoff and while departing to the west, the pilot was instructed twice to enter the left traffic pattern, with no response. Radar data showed the airplane departing the runway and remaining on runway centerline heading for the length of the flight. The airplane climbed to about 100 ft above ground level and the airplane’s groundspeed increased to 81 knots soon after departure then decreased to 70 knots before dropping off radar. Witnesses reported seeing the airplane depart the airport at a low climb rate and slow airspeed. Shortly after, the airplane flew out of view and a column of smoke was seen on the horizon. Accident site documentation identified symmetrical propeller strikes on the ground consistent with the airplane impacting the ground in a shallow, nose-up, wings level attitude. Examination of the airframe and both engines did not reveal any evidence of a preaccident mechanical failure or malfunction that would have precluded normal performance to allow for sufficient airspeed and climb rate after takeoff. Both the engines exhibited damage signatures consistent with the engines producing symmetrical power at impact. The pilot’s most recent flight in the accident airplane was 2 months before the accident. The pilot was reported to have problems with understanding the accident airplane’s avionics system; however, it is unknown if he was having these problems during the accident flight. Review of the pilot’s medical history revealed no significant medical concerns or conditions that could pose a hazard to flight.
Probable cause:
The degraded airplane performance after takeoff for reasons that could not be determined from available evidence.
Final Report: