Accident Details
Probable Cause and Findings
The pilots’ failure to attain a proper landing flare and touchdown point, which resulted in a hard landing short of the runway.
Aircraft Information
Registered Owner (Current)
Analysis
On February 11, 2023, at 1250 eastern standard time, a Gates Learjet Corp 55, N600C, was substantially damaged when it was involved in an accident near Rochester, New York. The airline transport pilots, three adult passengers, and an infant child were not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.
The crewmembers were interviewed by Federal Aviation Administration (FAA) aviation safety inspectors. They each stated that their individual inspections of the airplane revealed there were no mechanical deficiencies with the airplane before departure from Palm Beach International Airport (PBI), West Palm Beach, Florida. The copilot described the flight as “uneventful” and reported that the airplane landed in the touchdown zone “firmly, but not exceptionally so.” He did not realize that the airplane was damaged until after landing, when he saw fuel leaking from the airplane after deplaning.
In a written statement, the pilot, who was flying the airplane, described a “stable approach” and stated that the landing was “firm,” but that after landing, the crew could “tell something was wrong as the aircraft was leaning to the left.” Once they deplaned, they “found the left strut assembly collapsed, damage to the [landing gear] attach point, damage to the left wing, and damage to the fuel tank.”
In written and verbal statements provided to the National Transportation Safety Board, the FAA, and their insurance company days after the accident, the pilot said that during the departure roll at PBI he “noticed the left wing was down,” applied aileron to compensate, and “didn’t think much of it at the time.” The copilot also “noticed” and provided a nearly identical statement.
Review of surveillance video showed the airplane parked on the ramp at PBI through its engine start, and taxi from parking to the taxiway. The airplane was in a level attitude, no damage to the wings was evident, and the airplane was not leaking any fluids while parked or during taxi.
In a telephone interview, one passenger stated that she had previously flown on the accident airplane with a different flight crew. The accident crew was contracted by the airplane’s owner from Canandaigua Air Center, LLC. She said the normal convention was for one pilot to “work the iPad” while the other flew the airplane. She noticed that captain was “preoccupied with the iPad” but was also in control of the airplane. He later handed the iPad to the copilot.
During the approach, the passenger said that she could hear altitudes called out, which sounded automated, and just before touchdown, she heard “too fast, too fast, which sounded like a person.” She stated that the airplane “slammed” onto the runway, the oxygen masks deployed, compartments inside the airplane opened, and the baby started screaming. The airplane bounced, and the second landing was “very bumpy.” She said the pilot shouted an expletive after landing, was “apologizing profusely” as they deplaned, and that they were “rushed” to their van because the airplane was leaking fuel.
A review of airport surveillance video revealed that the airplane touched down around the runway 28 displaced threshold before the landing surface of the runway, bounced, and continued about 270 ft before it touched down and rolled out on the runway (see Figure 1).
Figure 1 - View of Ground Scars and Rubber Transfer Marks Consistent with Left Main Landing Gear
Examination of photographs revealed skid marks, ground scars, and fractured and broken parts associated with the left main landing gear wheel assembly, the retaining system for its brakes, a fractured piece from the strut cylinder and a fractured piece of its snap ring (retainer) (see Figure 2).
Figure 2 - View of Fractured Landing Gear Leg and Fractured Brake Caliper Retention Caps
The initial ground scar and skid marks, which were consistent with the dimensions of the left main landing gear tires, began in the displaced threshold about 110 ft before the landing surface of the runway. The fractured parts were scattered over and beyond the ground scars and tire markings. One of the FAA inspectors described the structural and skin damage to the left wing and provided photographs of the torn structure, fractured hardware, and “sheared-off” rivets of the left-wing aft spar. Visual examination of the fracture surfaces depicted in the photographs revealed signatures consistent with overstress.
The pilot held an airline transport pilot certificate with a rating for airplane multi-engine land. He held multiple type ratings, including one for the accident airplane. He was issued an FAA second-class medical certificate on December 9, 2022. The pilot reported 13,550 total hours of flight experience, of which 300 hours were in the accident airplane make and model.
The copilot held an airline transport pilot certificate with a rating for airplane multi-engine land. He was issued an FAA second-class medical certificate on June 13, 2022. The copilot reported 17,000 total hours of flight experience, of which 30 were in the accident airplane make and model. He was not type-rated in the accident airplane make and model.
Airport firefighters were dispatched when the ground operations supervisor heard a “loud bang” as the airplane landed and saw what he thought was smoke coming from the landing gear. Upon reaching the airplane, firefighters observed an active fuel leak as the passengers were deplaning. A statement from the fire department indicated that fuel was “pouring” from the area just forward of the left main landing gear well. The fuel spill was estimated at 25 gallons. Firefighting personnel also reported a “trail of fuel” from runway 28 to the ramp where the airplane parked, and tire marks as well as multiple pieces of metal debris in the displaced threshold.
Data Source
Data provided by the National Transportation Safety Board (NTSB). For more information on this event, visit the NTSB Records Search website. NTSB# ERA23LA126