Crash of an IAI-1125 Astra in Hot Springs: 5 killed

Date & Time: Mar 10, 2024 at 1457 LT
Type of aircraft:
Registration:
N1125A
Flight Type:
Survivors:
No
MSN:
51
YOM:
1990
Crew on board:
2
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
5
Circumstances:
The airplane departed Fort Lauderdale-Hollywood International Airport Runway 28R at 1346LT with five people on board. It continued to the north at FL390 then successively descended to FL370 and FL330 when the crew encountered an unexpected situation and elected to divert to Hot Springs-Ingalls Field, Virginia. On final approach, the airplane went out of control and crashed in a wooded area located few km short of runway 25. The airplane was totally destroyed by impact forces and a post crash fire and all five occupants were killed, among them one child.

Crash of a Beechcraft BeechJet 400A in Bentonville

Date & Time: Feb 14, 2024 at 1410 LT
Type of aircraft:
Operator:
Registration:
N95GK
Flight Phase:
Survivors:
Yes
Schedule:
Bentonville – Concord
MSN:
RK-027
YOM:
1991
Crew on board:
2
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
On February 14, 2024, about 1410 central standard time, a Beech 400A airplane, N95GK, was substantially damage when it was involved in an accident in Bentonville, Arkansas. The 2 pilots and 3 passengers were not injured and 2 passengers were seriously injured. The airplane was operated under the provisions of Title 14 Code of Federal Regulations Part 91 as a business flight. According to preliminary information, while on takeoff from the Bentonville Municipal Airport (VBT), Bentonville, Arkansas, the pilot pulled the control yoke back to rotate the airplane and the control yoke was unresponsive. He aborted the takeoff, but insufficient runway remained to stop. The airplane departed the end of runway 18 and came to rest in mud and grass. During the runway overrun, the right main landing gear collapsed, and the right wing sustained substantial damage. Inspectors from the Federal Aviation Administration responded to the accident site and visually examined the airplane. The elevator control cable was found separated in the area of the vertical stabilizer.

Crash of a Canadair CL-600-2B16 Challenger 604 in Naples: 2 killed

Date & Time: Feb 9, 2024 at 1517 LT
Type of aircraft:
Operator:
Registration:
N823KD
Survivors:
Yes
Site:
Schedule:
Columbus - Naples
MSN:
5584
YOM:
2004
Flight number:
HPJ823
Location:
Crew on board:
3
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
10525
Captain / Total hours on type:
2808.00
Copilot / Total flying hours:
24618
Copilot / Total hours on type:
138
Aircraft flight hours:
9763
Circumstances:
On February 9, 2024, about 1517 eastern standard time, a Bombardier Inc CL-600-2B16, N823KD, was destroyed when it was involved in an accident near Naples, Florida. The two airline transport pilots were fatally injured. The cabin attendant and the two passengers sustained minor injuries, and one person on the ground suffered minor injury. The airplane was operated by Ace Aviation Services (doing business as Hop-A-Jet) as a Title 14 Code of Federal Regulations Part 135 on-demand passenger flight. The airplane was returning to Naples Municipal Airport (APF), Naples, Florida, from Ohio State University Airport (OSU), Columbus, Ohio, where it had flown earlier in the day. The airplane was serviced with 350 gallons of fuel before departure from OSU. Preliminary Automatic Dependent Surveillance – Broadcast (ADS-B) flight track and air traffic control (ATC) data revealed that the flight crew contacted the ATC tower at APF while on a right downwind leg of the approach to the airport and maneuvering for a 5-mile final approach to runway 23. At 1508, the tower controller cleared the flight to land. The airplane was about 6.5 miles north of APF, about 2,000 ft geometric altitude (GEO) and 166 knots groundspeed, as it turned for the base leg of the traffic pattern. A preliminary review of the data recovered from the airplane’s flight data recorder revealed that the first of three Master Warnings was recorded at 1509:33 (L ENGINE OIL PRESSURE), the second immediately following at 1509:34 (R ENGINE OIL PRESSURE), and at 1509:40 (ENGINE). The system alerted pilots with illumination of a “Master Warning” light on the glareshield, a corresponding red message on the crew alerting system page and a triple chime voice advisory (“Engine oil”). Twenty seconds later, at 1510:05, about 1,000 ft msl and 122 kts, on a shallow intercept angle for the final approach course, the crew announced, “…lost both engines… emergency… making an emergency landing” (see figure 1). The tower controller acknowledged the call and cleared the airplane to land. At 1510:12, about 900 ft and 115 knots, the crew replied, “We are cleared to land but we are not going to make the runway… ah… we have lost both engines.” There were no further transmissions from the flight crew and the ADS-B track data ended at 1510:47, directly over Interstate 75 in Naples, Florida. Dashcam video submitted to the National Transportation Safety Board captured the final seconds of the flight. The airplane descended into the camera’s view in a shallow left turn and then leveled its wings before it touched down aligned with traffic travelling the southbound lanes of Interstate 75. The left main landing gear touched down first in the center of the three lanes, and then the right main landing gear touched down in the right lane. The airplane continued through the break-down lane and into the grass shoulder area before impacting a concrete sound barrier. The airplane was obscured by dust, fire, smoke, and debris until the video ended. This information is preliminary and subject to change. After the airplane came to rest, the cabin attendant stated that she identified that the cabin and emergency exits were blocked by fire and coordinated the successful egress of her passengers and herself through the baggage compartment door in the tail section of the airplane.

Crash of a Hawker 900XP near Bitter Creek: 2 killed

Date & Time: Feb 7, 2024 at 1047 LT
Type of aircraft:
Operator:
Registration:
N900VA
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Grand Junction - Tacoma
MSN:
HA-0020
YOM:
2007
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Circumstances:
The airplane departed Grand Junction Airport at 1037LT on a positioning flight to Tacoma, carrying a crew of two. About 10 minutes later, it entered an uncontrolled descent and crashed in a uninhabited area located near the Bitter Creek River, eastern Utah, near the border with Colorado. The airplane was destroyed by impact forces and a post crash fire and the wreckage was found about 17 km west northwest from the Mack-Mesa Airport located in Colorado. Both occupants were killed.

Crash of a Beechcraft C99 Airliner in Londonderry

Date & Time: Jan 26, 2024 at 0726 LT
Type of aircraft:
Operator:
Registration:
N53RP
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Manchester - Presque Isle
MSN:
U-195
YOM:
1982
Flight number:
WIG1046
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The twin engine airplane departed Manchester-Boston Regional Airport Runway 06 at 0709LT on a cargo service (flight WIG1046) to Presque Isle. After takeoff, the airplane entered a left turn and climbed to 2,700 feet when the pilot reported problems to ATC. He followed several circuits over Manchester, Auburn and Merrimack with erratic courses and varying altitude and speed. Finally, the airplane entered a right turn and crashed in a forest located near Londonderry, about 8 km south of Manchester Airport. The accident occurred 17 minutes after departure. The pilot was seriously injured and the airplane was destroyed.

Crash of a Quest Kodiak 100 in Lorida

Date & Time: Jan 19, 2024 at 1713 LT
Type of aircraft:
Operator:
Registration:
N5799
Flight Type:
Survivors:
Yes
Schedule:
LaBelle – Lakeport
MSN:
100-0277
YOM:
2019
Crew on board:
1
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
80
Captain / Total hours on type:
80.00
Circumstances:
The pilot reported, “upon touchdown, the plane jumped back up as I reduced power all the way back.” He said that the airplane bounced twice on the grass runway, resulting in the nose wheel separating from the airplane. Subsequently, the nose landing gear strut dug into the ground, and the airplane nosed over. The airplane’s fuselage, wings, and empennage were substantially damaged. The pilot reported that there were no preimpact mechanical malfunctions or failures of the airplane that would have precluded normal operation.
Probable cause:
The improper recovery from a bounced landing, which resulted in a hard landing and subsequent noseover.
Final Report:

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
Captain / Total flying hours:
31800
Captain / Total hours on type:
800.00
Copilot / Total flying hours:
1726
Copilot / Total hours on type:
9
Aircraft flight hours:
14135
Circumstances:
The pilot in command of the airplane reported that, while on an instrument GPS approach, they listened to the automated surface observing system several times and determined that they would be landing with a “light quartering tailwind” on an upsloping runway. Once clear of clouds and with the runway in sight, the pilot canceled the instrument flight rules clearance, announced their position over the airport’s common traffic advisory frequency and received a reply with a report of 1/4 inch of dry snow covering the runway, unplowed. During the landing roll, they applied brakes, extended spoilers, and thrust reversers. Initially the airplane slowed; however, about halfway down the runway, the airplane’s antiskid system was functioning continuously, and the airplane’s rate of deceleration decreased. The pilot was unsure if the thrust reversers deployed, and he cycled the thrust reversers and did not feel any effects. The pilot stated that, in his experience, the airplane’s thrust reversers do not feel very effective. The pilot considered aborting the landing, started to clean up the airplane but thought it was too late. The airplane overran the departure end of the runway, onto a grass covered area and into a deep ravine, resulting in substantial damage to the fuselage and both wings. The pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation. The automated weather observation station located on the airport reported that, about 44 minutes before the accident, the wind was from 090° at 12 knots. The same automated station reported that, about 16 minutes after the accident, the wind was from 090° at 12 knots. The airplane landed on runway 22. The fixed based operator owner reported that, on the day of the accident, his review of the runway conditions at the airport appeared to be around an inch of snow on the runway surface. Additionally, plowing at the airport so far this year had been “abysmal.” Big windrows and ice chunks have been left; taxiway corners had been built up to the point there could be an occurrence should an airplane be taxiing by. Earlier this year, several departures were delayed due to the runway not being plowed. According to the chairman of the airport board, there is no formal process to conduct runway assessments. However, an airport board member lives in the area and routinely visits the airport to conduct runway assessments. The runway assessments and frequency of the observations are not documented but are conveyed verbally to the airport board via cell phone. To the best of his knowledge, there is no formal snow or ice removal plan. When the runway is required to be cleared, a board member will use county provided equipment to clear the runway. The frequency of the snow removal is not documented. The airport snow removal equipment is limited to clear substance to ½ inch of the runway surface. On the day of the accident, he was not aware of a Notice to Air Misson (NOTAM) issued for the conditions of the runway environment. According to the airplane manufacturer, the estimated landing distance on a dry runway was about 3,350 ft, with loose snow and no tailwind the estimated landing distance was about 6,700 ft, and on loose snow with tailwind, the estimated landing distance was 7,531 ft. According to the Federal Aviation Administration, the airport is not required to have a snow and ice control plan. However, the airport was provided federal funds (grant) to purchase/acquire a snowplow to maintain the airport surfaces during inclement weather conditions. There may be times where issues arise, and action is delayed. In that case it is expected that a NOTAM be issued as outlined in the grant agreement.
Probable cause:
The flight crew’s decision to land on a snow-covered runway with a tailwind, resulting in a runway excursion and subsequent impact with terrain. Contributing to the accident, was the failure of the airport authority to plow the runway.
Final Report:

Crash of a Piper PA-46R-350RT Malibu Matrix in Lake Norman Airpark: 1 killed

Date & Time: Dec 31, 2023 at 1215 LT
Operator:
Registration:
N539MA
Flight Type:
Survivors:
No
Schedule:
Lake Norman Airpark - Lake Norman Airpark
MSN:
46-92139
YOM:
2010
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Circumstances:
The pilot departed Lake Norman Airpark Runway 32 at 1152LT on a local flight. After takeoff, he continued to the northwest for about 10 minutes then initiated a turn to the left and a descent back to the airfield. On short final, the single engine airplane crashed nearby a wooded area located near Adrian Lane, about 1,200 metres short of runway 14. The airplane was destroyed and the pilot, sole on board, was killed.

Crash of a Pilatus PC-12/45 near San Angelo: 2 killed

Date & Time: Dec 14, 2023 at 1318 LT
Type of aircraft:
Operator:
Registration:
N188PC
Flight Type:
Survivors:
No
Schedule:
Jacksonville – San Angelo
MSN:
188
YOM:
1997
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Circumstances:
While on final approach to San Angelo-Mathis Field, the single engine airplane entered a rapid descent with a rate of 5,058 feet per minute then crashed in an open field located about 12 km south of the airport. The airplane was totally destroyed and both occupants were killed.

Crash of a Socata TBM-850 in Ludington: 2 killed

Date & Time: Nov 26, 2023 at 1000 LT
Type of aircraft:
Operator:
Registration:
N850JH
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Ludington - Angola
MSN:
448
YOM:
2008
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Circumstances:
The airplane departed Ludington-Mason County Airport on a private flight to Angola-Tri State Steuben County Airport, Indiana. Two people leaving in Angola were on board with their two dogs. After takeoff from runway 08, while in initial climb, the twin engine airplane went out of control and crashed nearby a forest. The airplane was destroyed and both occupants were killed. The visibility at the time of the accident was limited due to snow falls.