LEVEL 3 Final report

Based on the investigation authority's final report.

Date
Show source
Occurrence
Runway overrun and fire
Location
Runway 24L and the Etobicoke Creek ravine, Toronto Pearson, Ontario
Show source
Operator
Air France
Show source
Aircraft
Airbus A340-313
Show source
Registration
F-GLZQ
Show source
Route
Paris Charles de Gaulle to Toronto Pearson
Show source
People aboard
309: 297 passengers and 12 crew
Show source
Fatalities
0
Show source
Survivors
309, all occupants
Show source
Topics
Delayed reverse thrust, Thunderstorm approach, Long touchdown, Runway end terrain, Carry-on baggage

This photograph is cropped for the banner. See the full photograph, credit, licence and what it shows.

Photographs and geographic context

Air France Airbus A340-313 F-GLZQ landing before the accident

F-GLZQ landing on 31 July 2005, two days before the Toronto accident.

Photo: Frank Robitaille, CC0 1.0 Universal

Image info

The accident aircraft, photographed on 31 July 2005 before the accident.

Image source

Original photograph unchanged. Responsive WebP copies resized without cropping.

Geographic context

Geographical orientation for Air France 358Paris Charles de Gaulle, departure; Toronto Pearson, destination; Etobicoke Creek ravine, accident site. Approximate airport markers and the accident location reported by the TSB.123NORTH UP / SCHEMATIC / NOT A RECORDED FLIGHT TRACK
  1. Paris Charles de Gaulle, departure
  2. Toronto Pearson, destination
  3. Etobicoke Creek ravine, accident site
Approximate airport markers and the accident location reported by the TSB. Basemap: Natural Earth, public domain.
Read supporting evidence

What happened

A tailwind, increased thrust and loss of forward visibility extended the flare. The aircraft touched down about 3800 feet along Runway 24L, then left its far end at about 80 knots after delayed reverse-thrust selection.

Read the full incident Follow what happened, from the flight to the investigation findings.

What investigators concluded

The TSB found that the severe, rapidly changing thunderstorm, excess aircraft energy, long touchdown, delayed reverse thrust and inadequate landing-distance assessment contributed to the overrun. Terrain beyond the runway increased the damage and injuries.

Evidence behind this explanation

A thunderstorm landing at Toronto

1,552 words / about 8 minutes to read. Based on the investigation records cited below.

Extra fuel for a difficult arrival

Air France Flight 358 left Paris Charles de Gaulle at 1153 UTC on 2 August 2005 for Toronto Pearson. The Airbus A340-313, F-GLZQ, carried 297 passengers and 12 crew members. The arrival forecast included thunderstorms, so the captain ordered an additional 3000 kg of fuel. That allowance was intended to provide another 23 minutes of holding at Toronto. The captain flew the takeoff and the first part of the journey. At 1617 UTC, the pilots exchanged flying duties, leaving the first officer to fly the approach and landing.

The aircraft crossed the Atlantic on a track north of its original flight plan and at a lower altitude than planned. The crew received a revised operational flight plan through the aircraft's data link. They also requested weather for Toronto and potential diversion airports. Several forecast requests returned a TAF NIL message because the crew selected the short forecast format, while those airports supplied long forecasts. Updated weather observations continued to arrive. The TSB found that the missing updated forecasts did not affect the outcome because the Toronto forecast had changed little from the preflight information.

By 1849 UTC, the pilots were considering Ottawa as a diversion destination. They calculated that 7300 kg would be needed to divert there, including final reserve fuel. As delays developed near Toronto, they repeatedly sought weather and traffic updates and obtained vectors around storms. At 1933 UTC they selected Ottawa as the alternate, with six minutes of holding fuel available at Toronto. The aircraft ultimately landed with 7630 kg aboard, enough for a missed approach and the planned diversion.

Sources for this section

Runway 24L in changing weather

The pilots briefed a windshear escape at 1919 UTC and later prepared for the instrument landing system approach to Runway 24L. Their approach briefing omitted runway length, the missed approach procedure and landing-distance calculations for a wet or contaminated runway. They correctly discussed the runway's 2743 m length two minutes before landing. The operational flight plan supplied a maximum landing weight based on the aircraft's structural limit, but contained no contaminated-runway landing distances for Toronto.

Storm-related equipment outages narrowed the available landing options. The localizer for Runway 24R became unserviceable, followed by the glideslope for Runway 23. Runway 24L remained available with an instrument approach aligned into the wind. It was 9000 feet long. Aircraft ahead of Flight 358 landed successfully, although two regional jets reported poor braking. One reported that braking improved below 60 knots. The tower passed those reports to the Air France crew.

At 1958 UTC, the tower's wind instruments were unavailable after a thunderstorm-related failure. Controllers passed wind reports from landing aircraft. Flight 358's pilots increased the autobrake setting from low to medium and reviewed go-around calls. In the cockpit, the normal challenge and response pre-landing checklist was delayed because the landing memo had not appeared on the electronic display. Its individual items had nevertheless been completed through the cockpit flow. The runway looked shiny with water, and the aircraft's radar showed heavy precipitation moving toward it from the northwest.

Sources for this section

Above the glide path

While the autopilot and autothrust were engaged, the A340 followed the localizer and glideslope at its target approach speed of 140 knots. At 2001:18 UTC, passing 323 feet above ground, the first officer disconnected the autopilot. Two seconds later he disconnected autothrust. He sensed falling airspeed and a sink, and increased engine thrust from about 42 percent to about 82 percent N1. The recorder showed a small airspeed decrease. The added power then increased the aircraft's energy, and it began moving above the glide path.

At roughly the same stage, the wind shifted toward a tailwind. The TSB's cause findings describe a change from a headwind component to a 10-knot tailwind component, which increased groundspeed and altered the flight path. The aircraft crossed the runway threshold about 40 feet above the normal crossing height. It then entered an intense downpour. Forward visibility deteriorated sharply, and lightning was visible around the runway and beyond its far end.

The pilots increasingly relied on the side windows to judge the aircraft's position. The TSB found that the severe weather overwhelmed them and reduced their airspeed scanning. Near the threshold, they became committed to landing and believed a go-around was no longer available. The captain was concerned about thunderstorms and lightning in the missed approach path. During the flare, excess speed and the difficulty of seeing the runway prolonged the float. Significant pitch and roll inputs showed the first officer's workload as he tried to control the aircraft.

Sources for this section

Too little runway left

The main landing gear touched down at 2001:53 UTC, about 3800 feet beyond the threshold. The A340 was slightly left of the centreline and crabbed about six degrees to the right. Its recorded airspeed was about 143 knots. The spoilers deployed automatically, and the pilots applied manual braking while working to align the aircraft with the runway. The recorder showed maximum braking demand by about five seconds after touchdown. Water contamination reduced the braking action available, while the crosswind exceeded the aircraft's contaminated-runway landing limit.

Idle reverse was selected 12.8 seconds after touchdown and full reverse at 16.4 seconds. The captain omitted the standard spoiler and reverser calls. The TSB attributed the delayed reverse selection to task overload during touchdown, with the first officer occupied by directional control in the crosswind and poor visibility. The delay increased the distance needed to stop. The aircraft left the runway at 2002:19 UTC at approximately 80 knots, crossed the roads beyond the runway and descended into the Etobicoke Creek ravine.

The investigators found that the remaining runway was insufficient for the touchdown conditions. Airbus calculations gave a stopping distance after touchdown of 6674 feet using the recorded speed, tailwind and reverse-thrust timing. Selecting full reverse according to the flight manual reduced that calculated distance to 5938 feet. Using both the recommended touchdown speed and normal reverse timing reduced it to 5574 feet. Each calculation exceeded the approximately 5100 feet remaining in the TSB's findings. Systems examination and brake testing found the braking system serviceable, and the TSB found no mechanical malfunction contributing to the accident.

Sources for this section

Escape before the fire spread

The aircraft bounced through several impacts before stopping. Baggage fell from overhead compartments, fittings detached and the L2 door opened while the aircraft was still moving. Fuel-system damage developed after the aircraft crossed Convair Drive. Fire intensified when the aircraft stopped in the ravine. Smoke entered the cabin, and the cabin crew began an evacuation within seconds. Three public-address announcements were made before that system failed, while the evacuation alert system also failed to operate. Both systems depended on emergency power in the vulnerable avionics bay.

Fire made the left-side L3 and L4 exits unusable. The L2 slide failed to deploy, and the R3 slide deflated after contacting wreckage. At least 16 passengers left through L2, where two suffered serious injuries after jumping or being pushed from the exit. Cabin attendants initially judged R1 and R2 unsafe because of the creek outside. As smoke increased, they reassessed the danger and opened those routes. Two crew members were needed to open R4. About two-thirds of the passengers escaped through that exit.

The evacuation took a little more than two minutes. The first officer and two cabin crew members searched the cabin and lavatories, returning along the opposite aisle to confirm that everyone had left. The first officer was the final person to exit, jumping through L1 because its slide was only partially deployed. All 309 occupants survived. Twelve sustained serious injuries, nine during the impacts and three during evacuation. Thirty-three people went to hospital by ambulance; 21 were treated for minor injuries and released. The TSB credited the training and actions of the whole cabin crew with the successful escape before fire engulfed the fuselage.

Sources for this section

Landing margins and safety action

Despite fire damage to the recorders, investigators recovered the cockpit voice recording and the full 45 hours of flight data. The flight data recorder's external connectors and interface cards had suffered heat damage, but its memory board remained in pristine condition. A TSB team travelled to France for the repair and download with BEA assistance. Investigators used the recovered data to calculate the touchdown position, reconstruct aircraft performance and prepare an animation for interviews with the pilots. Those interviews helped locate the points where the weather and visibility had deteriorated.

Firefighters at the south fire hall saw the landing and responded before the tower sounded its crash alarm. The first vehicle reached the scene within one minute of that alarm. Heavy rain diluted the firefighting foam and reduced its effectiveness against the fuel-fed fire, which destroyed most of the aircraft. The TSB found that the terrain beyond the runway's compliant overrun area contributed to aircraft damage and occupant injuries. It also found that the pilots had not calculated the required landing distance and were unaware that the tailwind eliminated their available margin.

Air France subsequently changed its policy so either pilot could call for a missed approach. It added rain-repellent information and procedures in September 2005 and revised its thunderstorm guidance. Airbus replaced the approach call 'landing' with 'continue'. The TSB issued seven recommendations: limits on approaches and landings in convective weather, better pilot decision training in deteriorating weather, calculation of landing-distance margins, a 300 m runway end safety area or equivalent stopping protection, and clear passenger directions to leave carry-on baggage behind. Nearly half the passengers had retrieved baggage during the evacuation, impeding escape.

Sources for this section

Return to the short summary / Source status and limitations

How the sequence developed

Follow the main stages, then open the evidence beneath each step.

  1. Weather deteriorates

    A shifting tailwind and intense rain affect the final seconds of the approach.

    Read supporting evidence
  2. Aircraft energy increases

    The flying pilot adds thrust after sensing a speed decrease and a sink; the aircraft moves above the glide path.

    Read supporting evidence
  3. The flare uses runway

    Excess speed and poor visual references extend the float to a touchdown about 3800 feet along the runway.

    Read supporting evidence
  4. Stopping distance grows

    Water contamination limits braking, and delayed reverse thrust increases the required stopping distance.

    Read supporting evidence
  5. Impact and fire

    The aircraft enters the ravine, sustains fuel-system damage and burns. Cabin crew direct the escape.

    Read supporting evidence

A simplified reading of the investigation findings. The sequence does not replace the full report or imply that every contributing factor is shown.

Sequence of events

Times are UTC. Toronto local time was eastern daylight time, four hours behind UTC. Expand an event to see its evidence.

  1. 1153Departure from Paris

    Flight 358 departs for Toronto with 297 passengers and 12 crew.

  2. 1933Ottawa selected as alternate

    The crew chooses Ottawa and calculates six minutes of holding fuel at Toronto.

  3. 1958Poor braking reports

    The tower passes poor-braking information; the crew selects autobrake medium.

  4. 2001:18Manual flight on short final

    The autopilot is disconnected at 323 feet; autothrust is disconnected two seconds later.

  5. 2001:53Long touchdown

    The main gear touches down about 3800 feet along Runway 24L.

  6. 12.8 seconds after touchdownIdle reverse selected

    Full reverse follows at 16.4 seconds after touchdown.

  7. 2002:19Runway excursion

    The aircraft leaves the runway at about 80 knots and comes to rest in a ravine.

  8. After the aircraft stopsEvacuation

    All occupants escape before the fire consumes most of the fuselage.

Search the report evidence

Search extracted report prose, with original page references. Short results link to the full document.

Questions readers ask

Why was the touchdown long?

The TSB found that excess speed caused a float while intense rain and lightning made the runway difficult to see. A tailwind and high threshold crossing increased the distance used.

Would earlier reverse thrust have stopped the aircraft?

Airbus calculated 5938 feet after touchdown with normal full-reverse timing at the actual speed, and 5574 feet with normal timing and recommended speed. The TSB found about 5100 feet remained.

How did everyone survive?

Cabin crew began evacuating within seconds, reassessed exits as smoke increased and directed passengers to available routes. The TSB credited their training and actions with the successful evacuation.

Was enough fuel available to divert?

The aircraft landed with 7630 kg of fuel. The TSB calculated that 7300 kg was required for the missed approach, diversion to Ottawa and final reserve.

What the evidence can and cannot establish

Simulator limits

The training simulator provided qualitative handling results. It could not fully reproduce the evolving weather and visibility, and the TSB drew no conclusion from those trials about the pilots' go-around judgment.

Read supporting evidence

Safety follow-up

Actions and recommendations are described at the dates of the cited records. A recommendation is not proof of implementation.

Air France changes in 2005

Air France amended its captain-only missed approach policy to permit either pilot to call for a go-around. It added rain-repellent guidance on 1 September 2005 and revised thunderstorm procedures on 29 September 2005.

Read supporting evidence

Thunderstorm limits and training

Recommendations A07-01 and A07-02 called for limits on approaches and landings in convective weather. A07-03 and A07-04 called for pilot training to improve landing decisions in deteriorating weather.

Read supporting evidence

Classifications, with reasons

These labels organise the evidence. They are not a ranking of causes. A shared label means a shared research topic, not an identical mechanism.

Contributing factorThunderstorm approach

The crew landed amid a severe, rapidly changing thunderstorm that sharply reduced visibility.

Contributing factorLong touchdown

Touchdown about 3800 feet along the runway left approximately 5100 feet for stopping.

Contributing factorDelayed reverse thrust

Idle and full reverse selections were delayed, and the monitoring pilot omitted deployment calls.

Injury and damage factorRunway end terrain

The ravine and terrain beyond the compliant overrun area increased damage and injuries.

Risk findingCarry-on baggage

Nearly half the passengers retrieved carry-on baggage, impeding evacuation.

Read alongside

These comparisons connect specific research topics. Shared circumstances do not establish identical causes. Evidence from both investigations is provided below.

Further investigation records

Explore the records below for additional context. They open on the publisher's site and are not all included in our report search. Source reuse terms apply.

Sources and transparency

8 October 2026

Source limitations

The flight recorder stopped before the aircraft came to rest, so the maximum impact forces could not be determined.

Aviation Investigation Report A05H0002: Runway Overrun and Fire, Air France

Transportation Safety Board of Canada
Final report, authorized 16 October 2007; released 12 December 2007

Official report PDF, hosted by tsb.gc.ca

Open source document

153 PDF pages.

Crown copyright, Minister of Public Works and Government Services Canada, 2007. Report text and photographs remain subject to Crown copyright and third-party rights.

Read the extraction, classification and review methodology.

Suggest a correction to this dossier

Editorial record

Kevin Murphy writes the incident accounts on AirlineIncidents.com, out of a long interest in aviation safety and the lessons each investigation leaves behind.

Prepared by
AirlineIncidents editorial desk
Report citation check
Independent expert review
Not completed

Citation checks compare supporting text with the indexed report pages. They do not constitute independent expert review. How these pages are prepared.

Revision history

: TSB final report A05H0002.

Source-based corrections are reviewed before changes appear here. Suggest a correction to this dossier.