code

CO

Crash of a Piper PA-46-500TP Malibu Meridian in Steamboat Springs: 1 killed

Date & Time: Dec 10, 2021 at 1812 LT
Operator:
Registration:
N744Z
Flight Type:
Survivors:
No
Site:
Schedule:
Cody – Steamboat Springs
MSN:
46-97134
YOM:
2002
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Circumstances:
The pilot, sole on board, departed Cody, Wyoming, on a private flight to Steamboat Springs. While approaching Steamboat Springs-Bob Adams Airport by night, the pilote encountered limited visibility due to low clouds. On final, the airplane impacted trees and crashed in a wooded area located on the slope of Mt Emerald, about 6 km south of airport runway 32. The aircraft was destroyed and the pilot was killed.

Crash of a Cessna 421C Golden Eagle III in Longmont

Date & Time: Jul 10, 2021 at 0920 LT
Operator:
Registration:
N66NC
Flight Phase:
Flight Type:
Survivors:
Yes
MSN:
421C-0519
YOM:
1978
Crew on board:
1
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
On July 10, 2021, about 0920 mountain daylight time, a Cessna 412C airplane, N66NC, was substantially damaged when it was involved in an accident near Longmont, Colorado. The pilot and three passengers received minor injuries. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. After the airplane lifted off from the runway, the pilot didn’t feel that the engine(s) were making full power. The airplane settled back onto the runway, then exited off the departure end of the runway. The airplane came to rest upright, and a small post-crash fire developed. Substantial damage was noted to the airplane’s fuselage and wings.

Crash of a Swearingen SA226TC Metro II in Denver

Date & Time: May 12, 2021 at 1023 LT
Type of aircraft:
Operator:
Registration:
N280KL
Flight Type:
Survivors:
Yes
Schedule:
Salida – Denver
MSN:
TC-280
YOM:
1978
Flight number:
LYM970
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
On May 12, 2021, at 1023 mountain daylight time, a Cirrus SR22, N416DJ, and a Swearingen SA226TC, N280KL, collided in flight while approaching to land at Centennial Airport (APA), Englewood, Colorado. There were no injuries on either airplane. N416DJ was operated as a Title 14 Code of Federal Regulations (CFR) Part 91 personal flight, and N280KL was operated as a Title 14 CFR Part 91 positioning flight. N416DJ departed APA for a local flight about 0921, and N280KL departed the Salida Airport (ANK), Salida, Colorado, about 0956. A review of preliminary air traffic control (ATC) communications and Automatic Dependent Surveillance-Broadcast (ADS-B) data provided by the Federal Aviation Administration (FAA) revealed that, N416DJ was performing a right-hand traffic pattern for runway 17R at APA, and N280KL was on final approach for runway 17L at APA, when the collision occurred. Both airplanes were in communication with air traffic control during their respective approaches to the airport. About 1022:43, N280KL was about 5.5 nm from APA and had completed a right turn to align with the final approach course to runway 17L. At this same time, N416DJ was on the downwind leg of the righthand traffic pattern for runway 17R just before he commenced a right turn to the base leg of the traffic pattern. N280KL continued its approach and remained aligned with runway 17L. N416DJ continued the right-hand traffic pattern through the base leg, and then began to turn toward the final approach course for the runway as depicted in Figure 1. The airplanes collided at 1023:53 when they were about 3.2 nm from APA. N280KL was aligned with runway 17L while N416DJ was turning from base to final and heading about 146° when the collision occurred. After the impact, N280KL declared an emergency, continued to APA, and landed successfully on runway 17L without further incident. The pilot of N416DL reported that the airplane was not controllable after the impact and he deployed the Cirrus Airframe Parachute System (CAPS). N416DJ came to rest about 3 nm north of APA.

Crash of an Eclipse EA500 in Leadville

Date & Time: Dec 13, 2020 at 2000 LT
Type of aircraft:
Operator:
Registration:
N686TM
Flight Type:
Survivors:
Yes
Schedule:
San Diego – Leadville
MSN:
221
YOM:
2008
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
5300
Captain / Total hours on type:
31.00
Aircraft flight hours:
1740
Circumstances:
The pilot reported that, while conducting a night landing on a runway contaminated with ice and patchy packed snow, the airplane overshot the touchdown zone. The pilot tried to fly the airplane onto the runway to avoid floating. The airplane touched down firm and the pilot applied moderate braking, but the airplane did not decelerate normally. The airplane went off the end of the runway and collided with several Runway End Identifier Lights (REILs) and a tree. The airplane sustained substantial damage to the left and right wings. The pilot reported that he did not feel modulation in the anti-lock braking system (ABS) and felt that might have contributed to the accident. An examination of fault codes from the airplane’s diagnostic storage unit indicated no ABS malfunctions or failures. An airport employee reported that he saw the airplane unusually high on the final approach and during the landing the airplane floated or stayed in ground effect before it touched down beyond the midpoint of the runway. The airplane’s long touchdown was captured by an airport surveillance video, which is included in the report docket.
Probable cause:
The pilot’s failure to maintain proper control of the airplane, which led to an unstabilized approach and a long landing on a runway contaminated with ice and patchy packed snow resulting in a runway excursion.
Final Report:

Crash of a Piper PA-61 Aerostar (Ted Smith 601) in Powder Wash: 1 killed

Date & Time: Apr 23, 2020 at 2130 LT
Registration:
N601X
Flight Phase:
Flight Type:
Survivors:
No
Site:
MSN:
61-0393-117
YOM:
1977
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Circumstances:
On April 23, 2020, at 2139 mountain daylight time (MDT), radar contact was lost with a Piper Aerostar 601X, N601X. The airplane was destroyed when it was involved in an accident near Craig, Colorado. The uncertificated (student rated) pilot sustained fatal injuries. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. The airplane was not equipped with automatic dependent surveillance-broadcast (ADS-B), which was required for operations in airspace that included class E airspace at or above 10,000 ft. The flight had not been operating on a flight plan and had no communications with air traffic control as required when it operated in class A airspace above 18,000 ft. Aircraft maintenance logbooks showed that the airplane received it last regulatory annual inspection dated November 21, 2019, and its last altimeter inspection, up to 30,000 ft, was dated June 27, 2014. Radar track data indicated that N601X departed Jersey Shore Airport (P96), Jersey Shore, Pennsylvania, about 1119 MDT, flying westbound at a cruise altitude of about 3,500 feet msl and had an average ground speed of about 180 - 190 kts until stopping at Findlay Airport (FDY), Findlay, Ohio, about 1251 MDT. Track data indicates N601X departed FDY about 1337 MDT, flying westbound at an altitude of about 3,500 ft, climbed once to about 5,500 ft, then descended to about 3,500 ft until later climbing to a cruise altitude of between 8,500-9,500 ft before descending into and landing at Red Oak Municipal Airport (RDK), Red Oak, Iowa, about 1618 MDT. Track data indicates N601X likely departed RDK about 1708 MDT, continuing westbound again, climbing to a maximum cruise altitude of about 9,500 ft, then descended and landed at Northern Colorado Regional Airport (FNL), Ft Collins/Loveland, Colorado, about 1949 MDT. A line service technician employed by a fixed base operator (FBO) at FNL stated that he was sitting in the line shack when he saw N601X taxi from the runway. He said the airplane's right engine was not running, and the pilot was trying to start it. The engine did not restart, and the airplane continued to taxi to the ramp. He asked the pilot if everything was "okay," and the pilot said, "yeah cut it a little close on fuel." He said the airplane was leaning "quite a bit" toward the right, which he attributed to a fuel imbalance. The line service technician said there was "a lot" of fuel staining under the right wing and on top of the wing. He did not look at the left wing and did not know if the left wing had fuel stains. He said he looked in the airplane and did not see it equipped with ADS-B; he said that he did not know how the pilot was going to fly over the mountains. He said the airplane was equipped with a panel mounted Garmin 430 and a transponder with round knobs. He said he saw an oxygen tank in the airplane and did
not know the amount of oxygen that was present in the tank. The line service technician said the airplane did not have a pressurization system. The line service technician said he topped of all three fuel tanks: left wing, right wing and fuselage tank. He said during fueling of left tank, he had to push up the right wing up because it was leaning downward. The pilot told him to make sure that the fuel tank cap on the fuselage was on tight because "the thing leaks." The line service technician said he double checked the fuselage fuel tank cap, and it was on "tight." The line service technician said the engines sounded fine except for the pilot running out of fuel during the after-landing taxi. He did not think the airplane was in "very good" condition. A customer service representative at the FBO stated the pilot told her he purchased the airplane in New York and was "going to try to get over the mountains." The pilot said he flew on a commercial flight from California and on the same day he purchased the airplane. He said he had to go over the mountains and through Utah and was destined to California. She said the pilot was "really tired" and did not have cash to buy Red Bull, so she made him coffee. The pilot told her that he left New York later than he wanted too because he was talking with the former airplane owner. He told her the airplane was his fifth airplane that he owned. Radar track data indicates N601X departed FNL about 2037 MDT turning westbound, climbing through about 12,000 ft, and made a left, almost 360° turn, continuing to climb throughout the turn, then flying west/southwest bound and reaching about 16,000 ft. The airplane continued west/southwest for a little over 40 miles climbing again and reaching about 22,000 ft, then turning right about 90° flying northbound, momentarily, before turning left and heading west/northwest and descending to about 20,000 ft, then back up again to about 22,000 ft, briefly, then back down to about 20,000 ft. The airplane then turned left to the southwest, then southbound, entering erratic flight climbing to over 23,000 ft, momentarily, before beginning to descend, entering a tight looping turn to the left and losing altitude rapidly, then showing a west/northwest heading in the final segment before track data was lost at about
2139 MDT. An alert notice was issued, and the airplane wreckage was located by the Colorado State Highway Patrol on April 24, 2020, about 0336 MDT, about 15 miles west of Craig, Colorado.

Crash of a Beechcraft 60 Duke in Loveland: 1 killed

Date & Time: May 15, 2019 at 1248 LT
Type of aircraft:
Operator:
Registration:
N60RK
Flight Type:
Survivors:
No
Schedule:
Broomfield – Loveland
MSN:
P-79
YOM:
1969
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
7000
Captain / Total hours on type:
100.00
Aircraft flight hours:
3119
Circumstances:
The commercial pilot was relocating the multiengine airplane following the completion of an extensive avionics upgrade, which also included the installation of new fuel flow transducers. As the pilot neared the destination airport, he reported over the common traffic advisory frequency that he had "an engine out [and] smoke in the cockpit." Witnesses observed and airport surveillance video showed fire emanating from the airplane's right wing. As the airplane turned towards the runway, it entered a rightrolling descent and impacted the ground near the airport's perimeter fence. The right propeller was found feathered. Examination of the right engine revealed evidence of a fire aft of the engine-driven fuel pump. The fuel pump was discolored by the fire. The fire sleeves on both the fuel pump inlet and outlet hoses were burned away. The fuel outlet hose from the fuel pump to the flow transducer was found loose. The reason the hose was loose was not determined. It is likely that pressurized fuel sprayed from the fuel pump outlet hose and was ignited by the hot turbocharger, which resulted in the inflight fire.
Probable cause:
A loss of control due to an inflight right engine fire due to the loose fuel hose between the engine-driven fuel pump and the flow transducer.
Final Report:

Crash of a Cessna 500 Citation I in Gunnison

Date & Time: Dec 4, 2016 at 1853 LT
Type of aircraft:
Operator:
Registration:
N332SE
Flight Type:
Survivors:
Yes
Schedule:
San Jose – Pueblo
MSN:
500-0332
YOM:
1975
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
2267
Captain / Total hours on type:
142.00
Aircraft flight hours:
5218
Circumstances:
The commercial pilot of the jet reported that he initially requested that 100 lbs of fuel be added to both fuel tanks. During the subsequent preflight inspection, the pilot decided that more fuel was needed, so he requested that the airplane's fuel tanks be topped off with fuel. However, he did not confirm the fuel levels or check the fuel gauges before takeoff. He departed on the flight and did not check the fuel gauges until about 1 hour after takeoff. He stated that, at that time, the fuel gauges were showing about 900-1,000 lbs of fuel per side, and he realized that the fuel tanks had not been topped off as requested. He reduced engine power to conserve fuel and to increase the airplane's flight endurance while he continued to his destination. When the fuel gauges showed about 400-500 lbs of fuel per side, the low fuel lights for both wing fuel tanks illuminated. The pilot reported to air traffic control that the airplane was low on fuel and diverted the flight to the nearest airport. The pilot reported that the airplane was high and fast on the visual approach for landing. He misjudged the height above the ground and later stated that the airplane "landed very hard." The airplane's left main landing gear and nose gear collapsed and the airplane veered off the runway, resulting in substantial damage to the left wing. The pilot reported no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation.
Probable cause:
The pilot's failure to fly a stabilized approach and his inadequate landing flare, which resulted in a hard landing. Contributing to the accident was the pilot's failure to ensure that the airplane was properly serviced with fuel before departing on the flight.
Final Report:

Crash of a Travel Air 4000 in Palmer Lake: 2 killed

Date & Time: Mar 2, 2016 at 0800 LT
Type of aircraft:
Registration:
N6464
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Longmont – Casa Grande
MSN:
785
YOM:
1928
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
5000
Circumstances:
The commercial pilot and the pilot-rated passenger were flying the biplane to a fly-in gathering in another state. Witnesses saw the airplane flying over a frozen lake at a low altitude and low airspeed. One witness saw the airplane "listing" left and right before it entered a left turn, and he lost sight of it. Other witnesses saw the airplane turn left and nose-dive into the ground. A postimpact fire consumed most of the airplane. Damage to the wreckage indicated that the airplane impacted the ground in a nose down attitude. The examination did not reveal evidence of any preimpact anomalies with the airframe, engine, or the control system of the airplane. A witness reported that, at the time of the accident, the wind was from the south about 30 miles per hour. However, a burnt area extending east from the airplane's impact point indicated the wind was from the west. Additionally, although wind information from nearby weather stations varied in direction and intensity. One station, about 14 miles west-northwest of the accident site reported calm wind., However, another station, located about 11 miles south of the accident site, recorded wind from the west at 11 knots with gusts to 27 knots about the time of the accident and wind from the west at 33 knots with gusts to 48 knots about an hour after the accident. Further, the forecast for the accident area called for wind gusts to 40 knots from the west-northwest. Therefore, it is likely that strong gusty west winds prevailed in the accident area at the time of the accident. Although some witnesses speculated that the pilot may have been attempting to land the airplane on the frozen lake, the airplane was not equipped to land on ice, and the reason the pilot was maneuvering at a low altitude in strong gusty winds could not be determined. Based on the witness observations and the damage to the wreckage, it is likely that the pilot allowed the airspeed to decrease to a point where the critical angle of attack was exceeded, and the airplane entered an aerodynamic stall/spin. Although the pilot was known to have heart disease, it is unlikely that his medical condition contributed to the accident. The witness observations indicate that the pilot was actively flying the airplane before the loss of control. Toxicology testing showed the presence of chlorpheniramine in the pilot's blood at a level that was likely in the therapeutic range. Chlorpheniramine is a sedating antihistamine available in a number of over the counter products, and it carries the warning, "May impair mental and/or physical ability required for the performance of potentially hazardous tasks (e.g., driving, operating heavy machinery)." Because of its sedating effect, chlorpheniramine may slow psychomotor functioning and cause drowsiness. It has also been shown in a driving simulator (after a single dose) to suppress visual-spatial cognition and visual-motor coordinating functions when compared to placebo. Such functions would have been necessary for the pilot to maintain control of the airplane while maneuvering close to the ground in the strong gusty wind conditions. Therefore, it is likely that the pilot's ability to safely operate the plane was impaired by the effects of chlorpheniramine.
Probable cause:
The pilot's failure to maintain sufficient airspeed while maneuvering at low altitude in strong gusting winds, which resulted in exceedance of the airplane's critical angle of attack and an aerodynamic stall/spin. Contributing to the accident was the pilot's impairment due to the effects of a sedating antihistamine.
Final Report:

Crash of a Beechcraft BeechJet 400A in Telluride

Date & Time: Dec 23, 2015 at 1415 LT
Type of aircraft:
Operator:
Registration:
XA-MEX
Survivors:
Yes
Schedule:
Monterrey – El Paso – Telluride
MSN:
RK-396
YOM:
2004
Crew on board:
2
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
7113
Captain / Total hours on type:
1919.00
Copilot / Total flying hours:
8238
Copilot / Total hours on type:
1412
Aircraft flight hours:
5744
Circumstances:
The pilots were conducting an international chartered flight in the small, twin-engine jet with five passengers onboard. Since the weather at the destination was marginal, the flight crew had discussed an alternate airport in case weather conditions required a missed approach at their destination. As the airplane neared the non-towered destination airport, the flight crew received updated weather information, which indicated that conditions had improved. Upon contacting the center controller, the crew was asked if they had the weather and NOTAMS for the destination airport. The crew reported that they received the current weather information, but did not state if they had NOTAM information. The controller responded by giving the flight a heading for the descent and sequence into the airport. The controller did not provide NOTAM information to the pilots. About 2 minutes later, airport personnel entered a NOTAM via computer closing the runway, effective immediately, for snow removal. Although the NOTAM was electronically routed to the controller, the controller's system was not designed to automatically alert the controller of a new NOTAM; the controller needed to select a display screen on the equipment that contained the information. At the time of the accident, the controller's workload was considered heavy. About 8 minutes after the runway closure NOTAM was issued, the controller cleared the airplane for the approach. The flight crew then canceled their instrument flight plan with the airport in sight, but did not subsequently transmit on or monitor the airport's common traffic advisory frequency, which was reportedly being monitored by airport personnel and the snow removal equipment operator. The airplane landed on the runway and collided with a snow removal vehicle about halfway down the runway. The flight crew reported they did not see the snow removal equipment. The accident scenario is consistent with the controllers not recognizing new NOTAM information in a timely manner due to equipment limitations, and the pilots not transmitting or monitoring the common traffic advisory frequency. Additionally, the accident identifies a potential problem for flight crews when information critical to inflight decision-making changes while en route, and problems when controller workload interferes with information monitoring and dissemination.
Probable cause:
The limitations of the air traffic control equipment that prevented the controller's timely recognition of NOTAM information that was effective immediately and resulted in the issuance of an approach clearance to a closed runway. Also causal was the pilots' omission to monitor and transmit their intentions on the airport common frequency. Contributing to the accident was the controller's heavy workload and the limitations of the NOTAM system to distribute information in a timely manner.
Final Report:

Crash of a Cessna 404 Titan II in Englewood: 1 killed

Date & Time: Dec 30, 2014 at 0429 LT
Type of aircraft:
Operator:
Registration:
N404MG
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Denver - Denver
MSN:
404-0813
YOM:
1981
Flight number:
LYM182
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
2566
Captain / Total hours on type:
624.00
Aircraft flight hours:
16681
Circumstances:
The pilot was conducting an early morning repositioning flight of the cargo airplane. Shortly after takeoff, the pilot reported to air traffic control that he had “lost an engine” and would return to the airport. Several witnesses reported that the engines were running rough and one witness reported that he did not hear any engine sounds just before the impact. The airplane impacted trees, a wooden enclosure, a chain-linked fence, and shrubs in a residential area and was damaged by the impact and postimpact fire. The airplane had been parked outside for 5 days before the accident flight and had been plugged in to engine heaters the night before the flight. It was dark and snowing lightly at the time of the accident. The operator reported that no deicing services were provided before the flight and that the pilot mechanically removed all of the snow and ice accumulation. The wreckage and witness statements were consistent with the airplane being in a right-winglow descent but the airplane did not appear to be out of control. Neither of the propellers were at or near the feathered position. The emergency procedures published by the manufacturer for a loss of engine power stated that pilots should first secure the engine and feather the propeller following a loss of engine power and then turn the fuel selector for that engine to “off.” The procedures also cautioned that continued flight might not be possible if the propeller was not feathered. The right fuel selector valve and panel were found in the off position. Investigators were not able to determine why an experienced pilot did not follow the emergency procedures and immediately secure the engine following the loss of engine power. It is not known how much snow and ice had accumulated on the airplane leading up to the accident flight or if the pilot was successful in removing all of the snow and ice with only mechanical means. The on-scene examination of the wreckage and the teardown of both engines did not reveal any preimpact mechanical malfunctions or failures. While possible, it could not be determined if water or ice ingestion lead to the loss of engine power at takeoff.
Probable cause:
The loss of power to the right engine for reasons that could not be determined during postaccident examination and teardown and the pilot’s failure to properly configure the
airplane for single-engine flight.
Final Report: