Home / Case Files / KLM 747 Declares Fuel Emergency After Air France Crash Closes Toronto Airport (2005)

KLM 747 Declares Fuel Emergency After Air France Crash Closes Toronto Airport (2005)

📅2 Aug 2005✈️B747, A340✈️AMS (Amsterdam)🏷️Emergency, Crash, Fuel
Advertisement
Accident timeline for KLM 747 Declares Fuel Emergency After Air France Crash Closes Toronto Airport (2005)
Accident-specific timeline reconstructed from the documented sequence; diagram not to scale.
Timeline
Toronto arrival
1.
Air France runway overrun closes airport
2.
KLM fuel margin falls
3.
Alternate discussion
4.
Fuel emergency
5.
Safe landing at Syracuse
6.

KLM 691's Approach Into a Suddenly Closed Toronto Pearson

KLM Flight 691 was a Boeing 747-400 approaching Toronto Pearson on 2 August 2005 when a major accident suddenly closed the airport. Air France Flight 358 had overrun the runway in severe weather, and the resulting emergency response made Toronto unavailable to arriving traffic.

KLM 691 had already committed to the Toronto arrival when the closure became known. The crew reported that they were becoming short on fuel and declared an emergency, with roughly 30 minutes remaining. The aircraft was eventually diverted to Syracuse Hancock International Airport in New York, where it landed safely.

Managing an Unplanned Diversion, Not a Crash

The incident is not a crash investigation. It is an emergency-management case showing how quickly a normal arrival can become a fuel-critical diversion when an airport closes unexpectedly.

The ATC sequence is valuable because it shows the changing options. KLM was being vectored toward Toronto when controllers informed the crew that the airport was closed. Hamilton was suggested as an alternative, but the crew evaluated their fuel situation and requested Syracuse instead.

That choice illustrates an important principle: the closest airport is not automatically the best airport. Pilots must consider runway suitability, weather, traffic, fuel burn to the alternate and the certainty of being able to land there.

The ATC record shows the operational decision point. Hamilton was discussed as an alternative, but the crew assessed the fuel remaining and selected Syracuse instead. The aircraft then declared a fuel emergency and was given priority routing. The important fact is that the crew did not wait until the engines were at risk of flameout; they converted the fuel concern into an explicit emergency early enough for ATC to act.

Why the Fuel-Emergency Declaration Mattered

By declaring a fuel emergency, the KLM crew also made the seriousness of the situation explicit. That gives ATC a clear operational priority and allows controllers to coordinate the most direct routing possible.

The emergency developed because the destination became unavailable after the flight had already entered the terminal area. That is different from poor fuel planning at departure, although the event still demonstrates why fuel reserves are designed to provide time for unexpected delays and diversions.

Toronto’s closure created a chain reaction: arriving aircraft needed alternate destinations, holding became undesirable, and fuel margins began to matter. KLM’s crew recognized that waiting was no longer a safe option.

The aircraft eventually landed safely at Syracuse and later continued to Toronto. The case is therefore a useful study in how a destination closure can create a fuel emergency even when the original flight plan was reasonable. The safety margin comes from making the diversion decision while there are still multiple airports and routing options available.

Investigation and findings

The flight landed at Syracuse around 4:30 p.m. local time. Passengers remained on board for several hours while the operational situation was resolved. Later that evening, the aircraft departed Syracuse and continued to Toronto, arriving around 9:40 p.m.

Research and reconstruction

Flight Follower Editorial Team

This reconstruction was researched from official investigation records where they exist, the original air traffic control recording, and contemporary reporting. The aircraft movement, timeline and written account were assembled independently by Flight Follower. Where an investigation is open or no probable cause has been published, the account says so rather than offering one.

About the Flight Follower team · Editorial policy · Corrections

Sources and investigation material

Accident Facts

Incident date
2 Aug 2005
Aircraft
B747, A340
Airports
AMS (Amsterdam)
Category
Emergency, Crash, Fuel
Reconstruction
8:29
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