Sky Lease Cargo 747 Overran Halifax Runway 14

Advertisement
Timeline
1
7 November 2018 — KYE4854 departed Chicago O'Hare for Halifax.
2
Approach — The crew conducted the ILS approach to Runway 14.
3
1 min 21 sec before threshold — The crew recognized a tailwind but did not recalculate landing performance.
4
05:06 local / 09:06Z — The 747 landed on Runway 14.
5
Landing roll — The aircraft failed to stop, overran the runway and crossed the localizer antenna.
6
Final position — The aircraft stopped roughly 200 metres beyond the runway end.
7
Investigation — TSB identified multiple operational and organizational contributing factors.

The runway choice narrowed before landing

Sky Lease Cargo Boeing 747-412F N908AR was operating flight KYE4854 from Chicago O'Hare to Halifax/Stanfield International Airport on 7 November 2018. The aircraft carried three crew members and one passenger. The crew conducted an ILS approach to Runway 14 at night.

A tailwind appeared late in the approach

The crew became aware of a tailwind about one minute and 21 seconds before the threshold. They did not recalculate the landing performance to confirm that the available distance remained acceptable. The investigation found that the way NOTAM information was presented had led the crew to believe the longer Runway 23 was unavailable.

The aircraft did not stop

The 747 touched down on the wet runway and continued beyond the runway end. It went down a slope and through the localizer antenna before stopping about 200 metres beyond the runway end. The aircraft sustained damage severe enough to become a hull loss. The four occupants survived, with minor injuries reported.

Fatigue and performance calculations compounded the problem

The TSB identified several contributing factors: the crew's sleep-related fatigue, use of unfactored landing-distance information, an approach-speed calculation using a larger wind additive than recommended, the late recognition of the tailwind and inadequate deceleration performance. The investigation also identified a momentary thrust-lever mishandling and a lateral deviation that diverted attention from braking.

The runway was not the only issue

The investigation did not reduce the event to a single mistake. Information presentation, runway availability assumptions, performance calculation, fatigue, wind, speed and aircraft handling interacted during the approach and landing. That combination explains why a large aircraft that had completed an otherwise routine instrument approach could still leave the runway with substantial energy remaining.

The TSB's findings show why the runway overrun cannot be reduced to tailwind alone. The crew had information that Runway 23 was not available, even though the runway was the longer and more suitable option. The crew also did not meet the pre-departure landing-weight requirement for Runway 14 with the selected flap setting, used unfactored landing-distance data and calculated a higher-than-recommended wind additive. Sleep-related fatigue further degraded performance. During the landing roll, attention was also diverted by a lateral deviation and thrust-lever handling, while braking proved insufficient to stop the aircraft before the runway end. The result was a chain of interacting factors rather than a single calculation error.

The TSB also noted that the aircraft stopped beyond the runway after passing through the localizer antenna area. The runway environment therefore became part of the damage sequence, not merely a location. The four occupants survived, but the aircraft was sufficiently damaged to become a hull loss. This outcome is important when describing the event as an accident rather than a routine runway excursion.

The TSB report states: “The unexpected tailwind resulted in a greater landing distance required, but this distance did not exceed the length of the runway.”

Accident Facts

Aircraft
Boeing 747-412F N908AR
Date
7 November 2018
Location
Halifax, Nova Scotia
Category
Accident

Sources

Audio from the original air traffic control recording, sourced from public recordings and released investigation records. The reconstruction, animation and written account are our own.
Advertisement

The weekly incident