TSB Investigator Blames Slick Runway For Toronto Mishap | Aero-News Network
Aero-News Network
RSS icon RSS feed
podcast icon MP3 podcast
Subscribe Aero-News e-mail Newsletter Subscribe

Airborne Unlimited -- Most Recent Daily Episodes

Episode Date

Airborne-Monday

Airborne-Tuesday

Airborne-Wednesday Airborne-Thursday

Airborne-Friday

Airborne On YouTube

Airborne-Unlimited-05.06.24

Airborne-NextGen-04.30.24

Airborne-Unlimited-05.01.24 Airborne-AffordableFlyers--05.02.24

Airborne-Unlimited-05.03.24

Mon, Aug 08, 2005

TSB Investigator Blames Slick Runway For Toronto Mishap

Safety Board Focuses On Long Landing And Effects Of Weather

New information from Canada's TSB indicates the Air France Airbus A340 that ran off the end of the runway in Toronto and burned last week land long and fast -- with a tailwind.

As ANN reported last week, Air France Flight 358 landed in the midst of a severe thunderstorm, rolling off the end of Runway 24L at Pearson International Airport while still going approximately 100 mph. Remarkably, none of the 309 passengers and crew aboard the aircraft was killed.

"I am pretty convinced that there was no way the aircraft was going to stop before the end with the water on the runway and the (poor) braking action," TSB lead investigator Real Levasseur told a Toronto news conference. "There was no way that aircraft was going to stop before the end (of the runway)."

Because of the water accumulated on the runway, and the fact that the A340 didn't even touch down until approximately halfway down the runway, Levasseur told reporters his team is now trying to determine the rate of deceleration once the aircraft was on the ground.

"Definitely because of the weather conditions, deceleration would have been much slower than it would be for a dry runway with maximum braking."

Levasseur seemed particularly alarmed at the failure of two emergency egress systems on board the Airbus. Although there are four cabin exits on an A340, investigators found the passengers aboard Flight 358 used only four of them. There were two reasons, he said. First, the cabin crew noticed a fire on one side of the aircraft, so they directed passengers to exit on the other side. But on one door, the emergency chute didn't inflate. On another, the chute didn't deploy at all, he said.

"If we find that they malfunctioned as a result of the accident, then I can accept that," he said. "But if we find there was a malfunction prior to the accident, then we'd want to do something about that."

FMI: www.tsb.gc.ca

Advertisement

More News

ANN's Daily Aero-Term (05.09.24): Hold Procedure

Hold Procedure A predetermined maneuver which keeps aircraft within a specified airspace while awaiting further clearance from air traffic control. Also used during ground operatio>[...]

ANN's Daily Aero-Term (05.06.24): Altitude Readout

Altitude Readout An aircraft’s altitude, transmitted via the Mode C transponder feature, that is visually displayed in 100-foot increments on a radar scope having readout cap>[...]

ANN's Daily Aero-Linx (05.06.24)

Aero Linx: European Hang Gliding and Paragliding Union (EHPU) The general aim of the EHPU is to promote and protect hang gliding and paragliding in Europe. In order to achieve this>[...]

Airborne-NextGen 05.07.24: AI-Piloted F-16, AgEagle, 1st 2 WorldView Sats

Also: Skydio Chief, Uncle Sam Sues, Dash 7 magniX, OR UAS Accelerator US Secretary of the Air Force Frank Kendall was given a turn around the patch in the 'X-62A Variable In-flight>[...]

Aero-News: Quote of the Day (05.07.24)

"The need for innovation at speed and scale is greater than ever. The X-62A VISTA is a crucial platform in our efforts to develop, test and integrate AI, as well as to establish AI>[...]

blog comments powered by Disqus



Advertisement

Advertisement

Podcasts

Advertisement

© 2007 - 2024 Web Development & Design by Pauli Systems, LC