code

FL

Crash of a Beechcraft 200 Super King Air in Buckingham

Date & Time: May 20, 2024 at 1103 LT
Operator:
Registration:
N762MC
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Buckingham - Buckingham
MSN:
BJ-16
YOM:
1980
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
While taking off from runway 32 at Buckingham Airport, the twin engine airplane went out of control, veered off runway to the left, lost its nose gear and left main gear and came to rest. Both crew members evacuated safely.

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 Quest Kodiak 100 in Lorida

Date & Time: Jan 19, 2024 at 1715 LT
Type of aircraft:
Operator:
Registration:
N5799
Flight Type:
Survivors:
Yes
Schedule:
Tavernier - Lorida
MSN:
100-0277
YOM:
2019
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The single engine airplane departed Tavernaero Park in Tavernier (Florida Keys) in the afternoon on a private flight to Lorida, carrying six people. After touchdown in a grassy area, the airplane overturned and came to rest upside down. All six occupants were rescued, among them three were injured.

Crash of a Rockwell Shrike Commander 500S off Key West

Date & Time: Aug 13, 2023 at 1019 LT
Operator:
Registration:
N62WE
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Orlando - Key West
MSN:
500-3317
YOM:
1978
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Approaching Key West-Intl Airport on a flight from Orlando, the airplane suffered an engine failure and was ditched about 25 km northeast of the destination. The pilot was rescued and was uninjured while the airplane sank and was lost.

Crash of a Piper PA-46-350P Malibu Mirage in Saint Augustine

Date & Time: Mar 23, 2023
Registration:
N280KC
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Saint Augustine – Jacksonville
MSN:
46-36219
YOM:
1999
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Shortly after takeoff from Saint Augustine Airport, while in initial climb, the airplane contacted trees and crashed in a wooded area, bursting into flames. Both occupants and their dog escaped with minor injuries. The airplane was destroyed by a post crash fire.

Crash of a Piper PA-46-310P Malibu in Port Orange

Date & Time: Feb 2, 2023 at 1200 LT
Registration:
N864JB
Flight Phase:
Flight Type:
Survivors:
Yes
MSN:
46-08009
YOM:
1986
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Shortly after takeoff from Port Orange-Spruce Creek Airport Runway 23, the single engine airplane encountered difficulties to gain height, impacted trees and crashed on a golf course located south of the airfield. Both occupants were rescued, among them one was slightly injured. The airplane was destroyed.

Crash of an Antonov AN-2 in the Everglades National Park

Date & Time: Nov 14, 2022 at 1330 LT
Type of aircraft:
Operator:
Registration:
CU-A1885
Flight Phase:
Flight Type:
Survivors:
Yes
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The single engine airplane landed last October at Dade-Collier Airport, in the center of the Everglades National Park, following a flight from Sancti Spíritus, Cuba. The pilot defected Cuba and landed safely in the US. On November 14, in unclear circumstances, maybe while being transferred to Opa Locka Airport, the airplane crashed in a marshy area located 25 km west of Opa Locka Airport. Both occupants were uninjured and the aircraft was damaged beyond repair.

Crash of a Cirrus Vision SF50 in Kissimmee

Date & Time: Sep 9, 2022 at 1502 LT
Type of aircraft:
Operator:
Registration:
N77VJ
Flight Type:
Survivors:
Yes
Schedule:
Miami - Kissimmee
MSN:
88
YOM:
2018
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
982
Captain / Total hours on type:
325.00
Aircraft flight hours:
645
Circumstances:
The pilot obtained multiple preflight weather briefings that resulted in him delaying the flight’s departure until the afternoon. After departure, while near his intended destination, the pilot was twice advised by air traffic controllers of adverse weather, including heavy to extreme precipitation along the intended final approach. While in visual meteorological conditions the pilot requested an RNAV approach to his destination airport. While flying towards the final approach fix at a low thrust setting the autopilot attempted to maintain 2,000 ft while pitching up and slowing to about 100 knots, causing an airspeed aural warning. The pilot applied partial thrust and while in instrument meteorological conditions the flight encountered extreme precipitation and turbulence associated with the previously reported thunderstorm. The pilot turned off the autopilot; the airplane then climbed at a rate that was well beyond the performance capability of the airplane, likely caused by updrafts from the mature thunderstorm and application of takeoff thrust. The High Electronic Stability & Protection (ESP) engaged, pitching the airplane nose-down coupled with the pilot pushing the control stick forward. The airplane then began descending followed by pitching up and climbing again. The pilot pulled the Cirrus Airframe Parachute System (CAPS) and descended under canopy into a marsh but the airplane was dragged a short distance from wind that inflated the CAPS canopy. Post accident examination of the recovered airplane revealed substantial damage to the front pressure bulkhead and to both sides of the fuselage immediately behind the front pressure bulkhead. There was no evidence of preimpact failure or malfunction of the flight controls for roll, pitch, or yaw. Data downloaded from the Recoverable Data Module (RDM) revealed no faults with the autopilot or stability protection systems until the CAPS system was activated, when those recorded faults would have been expected. Further, there were no discrepancies with the engine. Although the pilot perceived a malfunction of the autopilot at several times during the final portion of the flight, the perceived autopilot discrepancies were likely normal system responses based on the autopilot mode changes.
Probable cause:
The pilot’s continuation of the instrument approach into known extreme precipitation and turbulence associated with a thunderstorm, resulting in excessive altitude deviations that required him to activate the Cirrus Airframe Parachute System.
Final Report:

Crash of a McDonnell Douglas MD-82 in Miami

Date & Time: Jun 21, 2022 at 1738 LT
Type of aircraft:
Operator:
Registration:
HI1064
Survivors:
Yes
Schedule:
Santo Domingo - Miami
MSN:
53027/1805
YOM:
1990
Flight number:
L5203
Crew on board:
10
Crew fatalities:
Pax on board:
130
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
14388
Captain / Total hours on type:
1400.00
Copilot / Total flying hours:
822
Copilot / Total hours on type:
269
Aircraft flight hours:
69838
Aircraft flight cycles:
36990
Circumstances:
Following an uneventful flight from Santo Domingo-Las Américas Airport, the crew was cleared to land on runway 09 at Miami-Intl Airport. The first officer recalled that the airplane touched down smoothly on the right and then the left main landing gear and that the airplane was slightly to the right of the centerline, which he corrected after touching down. Shortly afterward, the flight crew felt a vibration on the left side of the airplane. The vibration increased, and the airplane veered to the left despite the crew’s efforts to maintain the airplane on the runway centerline. The airplane subsequently departed the paved runway surface and impacted the glideslope equipment building for runway 30, which was located to the left of runway 09, causing the nose landing gear and the right main landing gear to collapse. A post crash fire began on the right wing after the fuel tank on that wing was breached, after which the airplane came to a stop. Nevertheless, fire was quickly extinguished and all 140 occupants evacuated safely, among them four passengers were taken to Jackson Hospital.
Probable cause:
The collapse of the left main landing gear during the landing roll resulted in a runway excursion due to a loss of controllability on the runway, during which the aircraft impacted a small equipment building, breaching the right-wing fuel tank and causing a post-crash fire. The performance of the crew was thoroughly evaluated during this investigation and found to be appropriate for the circumstances of the accident.
The focus of this analysis is the cause of the left main landing gear collapse. Particularly
(1) the left shimmy damper’s failure to adequately dampen vibration during landing and
(2) the failure of the left main gear downlock mechanism due to excessive vibration.
The structural failure of the left main landing gear downlock following ineffective shimmy dampening during the landing roll which caused the collapse of the left main landing gear, resulting in a runway excursion and post-flight fire.
Final Report:

Crash of a Cessna 207 Skywagon off Marathon

Date & Time: Dec 29, 2021 at 1622 LT
Operator:
Registration:
N1596U
Flight Phase:
Survivors:
Yes
Schedule:
Marathon - Naples
MSN:
207-0196
YOM:
1971
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
1463
Captain / Total hours on type:
176.00
Aircraft flight hours:
13496
Circumstances:
Shortly after departure, the engine lost total power and the pilot was forced to ditch in open water; the occupants egressed and were subsequently rescued by a recreational vessel. Examination of the engine revealed a fracture hole near the n°2 cylinder, which was likely the result of the n°2 cylinder connecting rod fracturing in fatigue as a result of high heat and high stress associated with failure of the n°2 bearing. The fatigue fracture displayed multiple origins consistent with relatively high cyclic stress, which likely occurred as excessive clearances developed between the bearing and the crankshaft journal. The n°2 connecting rod bearing may have failed due to a material defect in the bearing itself or due to a disruption in the oil lubrication supply to the bearing/journal interface. Either situation can cause similar damage patterns to develop, including excessive heating and subsequent bearing failure.
Probable cause:
A total loss of engine power due to the failure of the No. 2 bearing, which resulted in the n°2 connecting rod failing due to fatigue, high heat, and stress.
Final Report: