19 Feb 2021: LEARJET 55 C — ROYAL AIR FREIGHT INC

19 Feb 2021: LEARJET 55 C (N559RA) — ROYAL AIR FREIGHT INC

No fatalities • Jeffersonville, IN, United States

Probable cause

The flight crew’s failure to verify the correct runway for landing, which resulted in a landing on a snow contaminated runway and resulting damage to the airplane. The illumination of the lights associated with the closed runway contributed to the accident.

— NTSB Determination

Accident narrative

On February 18, 2021, about 1905 central standard time, a Gates Learjet 55, N559RA, was substantially damaged when it was involved in an accident near Jeffersonville, Indiana. The captain and first officer were not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 135 on-demand cargo flight.

The Royal Air Cargo flight, was being operated on an instrument flight rules flight plan from Southwest Florida International Airport, Fort Myers, Florida, to Clark Regional Airport (JVY), Jeffersonville, Indiana. The airplane sustained damage to the landing gear, lower fuselage, wings and ventral strakes. According to the airplane manufacturer the strakes are critical for aerodynamic stability and would adversely affect the flying characteristics of the airplane.

The captain reported that the takeoff, climb, and en route portions of the flight were normal, with the first officer acting as the pilot flying. As they approached the destination, he and the first officer briefed and set up for the instrument landing system approach (ILS) to runway 18, expecting to break out of the overcast cloud layer and execute a visual approach to runway 36 due to more favorable winds. Upon exiting the overcast, he activated the airport’s pilot-controlled lighting system and the first officer saw the runway. Both pilots stated that they believed the runway that they saw was runway 36. They maneuvered the airplane visually toward the runway that was in-sight and executed a landing. The captain stated that, upon touchdown, it became clear that they had inadvertently landed on runway 32. In his report, the captain said that both he and the first officer were aware that runway 14-32 was closed. The first officer stated that while flying to JVY they activated the pilot-controlled lighting and saw a runway light up. They visually lined up and landed on the runway that they saw and believed to be runway 36; however, it was actually runway 32.

Both pilots reported that the only runway lights that they saw during the approach were the lights on runway 32, and there were no visible indications that the runway they approached was closed. Both pilots also stated that, during the visual approach, they did not verify that the final approach course was aligned with the intended runway.

The airport manager confirmed that runway 32 was closed and that a notice to airmen (NOTAM) had been issued to that effect. In addition, the Automated Weather Observing System recording, available to the pilots via the aircraft communication radio, was appended with the runway closure information. The runway was closed due to the large amount of snow that they had received. About 4 inches of snow that had yet to be cleared from the runway. The airport manager noted that the runway lights were on due to the snowplow operations as an aid in determining the location of the runway edge. There were no plow trucks on runway 32 at the time of the accident because they had stopped for a dinner break, but he confirmed that the runway lights were left on during this time. He noted that, depending on the direction the airplane was coming from, the lights for runway 36 may not have been visible due to the snow berms along the runway edge obstructing their view from the side.

Information from the Federal Aviation Administration (FAA) confirmed that a NOTAM referencing the closure of runway 14/32 was in effect at the time of the accident.

Contributing factors

  • Flight crew
  • Contributed to outcome
  • Contributed to outcome

Conditions

Weather
VMC, wind 330/03kt, vis 10sm

Loading the flight search…

What you can do on Flight Finder

  • Search flights between any two airports with live fares.
  • By aircraft — pick a plane model (e.g. Boeing 787, Airbus A350) and see every route it flies from your origin.
  • Route map — click any airport worldwide to explore its destinations, or draw a radius to find nearby airports.
  • Global aviation safety — aviation accident database, 5,200+ records since 1980, with map and rankings by aircraft and operator.
  • NTSB safety feed — recent U.S. aviation accidents and incidents from the official NTSB CAROL database, updated daily.

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.

Which aircraft types can I filter by?

We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.

Is FlightFinder free to use?

Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.

Where does the route data come from?

Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.