If you wish to contribute or participate in the discussions about articles you are invited to join SKYbrary as a registered user

 Actions

A320, Toronto ON Canada, 2017

From SKYbrary Wiki

Summary
On 25 February 2017, an Airbus A320 left the side of the landing runway at Toronto when, for undetermined reasons, the Captain, as Pilot Flying, set up a drift to the right just before touchdown. This was then followed by a lateral runway excursion into wet grass in rain-reduced visibility which continued for 1,650 metres before the aircraft regained the runway and stopped. The Investigation noted that both the absence of runway centreline lighting and the aircraft operator’s policy of not activating the aircraft rain repellent system or applying the alternative hydrophobic windshield coating may have increased the excursion risk.
Event Details
When February 2017
Actual or Potential
Event Type
Human Factors, Runway Excursion
Day/Night Night
Flight Conditions On Ground - Low Visibility
Flight Details
Aircraft AIRBUS A-320
Operator Air Canada
Domicile Canada
Type of Flight Public Transport (Passenger)
Origin Halifax Stanfield International Airport
Intended Destination Toronto/Lester B. Pearson International Airport
Take off Commenced Yes
Flight Airborne Yes
Flight Completed Yes
Flight Phase Landing
LDG
Location - Airport
Airport Toronto/Lester B. Pearson International Airport
HF
Tag(s) Manual Handling,
Plan Continuation Bias
RE
Tag(s) Late Touchdown,
Off side of Runway,
Continued Landing Roll
WX
Tag(s) Precipitation-limited IFV
AW
System(s) Ice and Rain Protection
Outcome
Damage or injury Yes
Aircraft damage Major
Non-aircraft damage Yes
Causal Factor Group(s)
Group(s) Aircraft Operation,
Airport Operation
Safety Recommendation(s)
Group(s) None Made
Investigation Type
Type Independent

Description

On 25 February 2017, an Airbus A320 (C-FDRP) being operated by Air Canada on a scheduled domestic passenger flight from Halifax to Toronto as flight 62 made a night Cat 1 ILS approach in reduced visibility due to rain which resulted in a late touchdown near the edge of the 60 metre-wide 2,770 metre-long runway 15R. The aircraft subsequently departed the runway onto the adjacent grass. It then paralleled the runway for over half its length before regaining it and coming to a stop. After the engines had been shut down and inspection showed that there was damage to the landing gear and engines, passengers were disembarked to buses.

Investigation

An Investigation was carried out by the Canadian TSB. Relevant data was successfully recovered from the FDR.

It was found that the Captain, who was PF for the investigated flight, had been employed by Air Canada for 20 years and had accumulated over 18,000 total flying hours including 14,800 hours on type. The First Officer had been employed by Air Canada for 11 years and had accumulated 11,500 total flying hours including over 2,700 hours on type.

It was established that runway 15R was in use as the landing runway at Toronto and that only a Cat 1 ILS approach was available in conditions of reduced visibility in rain. The aircraft being flown was equipped for autoland off a Cat 1 approach but as the reported RVR was almost twice the applicable minimum, the crew, having noted the absence of centreline lighting on the runway concerned, nevertheless decided that the AP would be disengaged once below DA for a manual landing in surface winds that were light and variable.

The PF had the approach lights in sight when the PM called “Minimums” at 200 feet agl and responded with “Landing”. At 100 feet agl, he disengaged the AP. The aircraft crossed the displaced runway threshold at a recorded height of 39 feet agl on the ILS LOC and GS. Then, descending through 26 feet agl, the PF made a brief but large right roll input - approximately 75% of the maximum available sidestick deflection - which produced a 4° right bank and the aircraft began to drift to the right of centreline and then immediately reduced the thrust to idle. At a recorded 8 feet agl, the aircraft was 10 metres to the right of the centreline of the 60 metre wide runway and PM called out that the aircraft was drifting to the right. The PF responded with a left roll command and left rudder but although the wings returned to level, the drift to the right continued due to the aircraft’s momentum. The left main gear touched down on the paved surface some 680 metres past the displaced runway threshold followed almost straight away by a minor bounce of the right main gear during which the outboard wheel was just 6 metres from the edge of the runway.

The aircraft continued drifting to the right following the bounce and when the right main gear touched down again it was off the runway in wet grass. After a further 85 metres during which there was further movement to the right, the nose landing gear also touched down on the grass and struck one of the runway edge lights. The out board left main gear wheel and left engine cowling then each struck two runway edge lights and the outboard left wheel tyre was damaged and deflated. The Captain then selected reverse thrust and both engines began to ingest debris. Once the aircraft had slowed down, he steered it back onto the paved surface and brought it to a stop 1653 metres from the displaced threshold and 938 metres from the end of the runway. The PM advised ATC that the aircraft was stopped on the runway and had undergone a runway excursion and requested ARFF to attend and inspect the aircraft for damage which was deemed sufficient to require no attempt to taxi in and the passengers were disembarked onto buses and taken to the terminal.

Further examination of the engines found denting to the left engine cowling and sufficient internal damage to both engines caused by use of reverse thrust whilst on the grass for both to have to be replaced. A total of 5 runway edge lights, which were located in the grass 1.5m metres beyond the runway edge, were damaged by impact with either the landing gear or the left engine cowling.

The Investigation was unable to determine why, as the aircraft was flared from an on-centreline position, the Captain had made a right roll command input, which initiated the drift to the right. It was noted that although a previous review of lateral excursions by Airbus had found that this type of destabilisation often occurred when the AP was disconnected or as the transition from instrument to visual flight was being made, in the event under investigation, destabilisation occurred much later than both of these and was also closer to the ground. It was also noted that the fact that the aircraft was drifting had to be pointed out to the Captain by the PM First Officer and that the former’s response to the alert, was insufficient to counteract the lateral momentum of the aircraft.

The aircraft ground track in relation to the landing runway. [Reproduced from the Official Report]

Although their relevance to the accident could not be directly validated, two aspects of potential relevance to the excursion were considered at some length as follows:

  1. Flight Crew External Visibility in Rain
    • It was noted that wiper system performance can be affected by both the condition of the wiper blade and the amount of tension exerted by the blade against the windshield. A post-event inspection of the aircraft found that neither windshield wiper met the minimum tension specified in the corresponding Airbus inspection procedure.
    • There had been no recent inspections of or maintenance to the accident aircraft’s wiper system and neither Airbus nor Air Canada require periodic inspection of the wiper.
    • The rain repellent system installed on the aircraft when delivered to Air Canada in 1990 was deactivated in 1996 because use of the repellent involved was prohibited for environmental reasons. When a replacement fluid was made in 1998, Air Canada decide not to reactivate it or to apply the Airbus-approved hydrophobic windshield coating which provides protection characteristics similar to those of liquid repellent which was made available in 1997.
  2. Absence of Runway Centreline Lighting
    • It was noted that runway 15R was the only one of Toronto’s three parallel runways not to be equipped with centreline lighting and that there was no requirement for it to be so equipped.
    • Runway 15R had edge lights at 60 metre intervals. When it was certified, its lighting complied with Canadian regulatory standards in effect at that time, although there was an associated recommendation that runway centreline lights should be provided on a runway such as 15R when that runway was “used by aircraft with high landing speeds or where the width between the runway edge lights is greater than 50 metres”. This associated recommendation was subsequently removed and was not applicable at the time of the excursion.
    • ICAO Annex 14 includes Recommendations as well as Standards and the relevant current Recommendation continues to use the same words as the ones removed from the relevant Canadian Regulatory Guidance Manual quoted above. In connection with the usefulness of centreline lighting, the ICAO ‘Aerodrome Design Manual' (Doc 9157 Part 4 – Visual Aids) 4th Edition, 2004, states that “in normal circumstances, a pilot can maintain the track of the aircraft within approximately 1 to 2 metres of the runway centreline with the aid of this lighting cue” and notes that this guidance is more precise than that possible by pilot assessment of the degree of asymmetry between the lighting along each runway edge, adding that the greater distances involved viewing runway edge lighting and the need for the pilot to look immediately ahead of the aircraft during a landing ground roll “also contribute to the requirements for a well-lit runway centreline”.

More generally, it was noted that the TSB had previously investigated a number of lateral runway excursions during landing in which directional control issues developed in reduced visibility conditions such as the ones here with both the lack of centreline lighting on wide runways and Air Canada’s policy to not either have functioning rain repellent systems or apply the alternative windshield hydrophobic coatings. It was noted that two of these earlier investigations, to an Airbus A340-300 at Toronto in 2005 and to an Airbus A330-300 at Montreal in 2014 had been identified as events where the lack of a rain repellent system or the alternative windshield hydrophobic coating was likely to have raised the lateral runway excursion risk. A third of these earlier TSB-investigated events, involving an Airbus A320 of another Canadian operator at Varadero, Cuba in 2005 had identified the same reduced visibility risk but not because a rain repellent system was not installed but because it was and the flight crew were unaware of the fact.

A 2015 review by Airbus of ‘Lateral runway excursions upon landing’ was referenced on the wider subject of the circumstances in which pilots destabilise their aircraft late in the approach. This review included the advice that since an aircraft will be stable when flying with the AP engaged, once it has been disconnected, no sidestick inputs should be made until the pilot has had time to assess the aircraft trajectory.

The formally stated Findings as to Causes and Contributing Factors were as follows:

  1. For undetermined reasons, during the transition to flare, while the aircraft was on the runway centreline, the pilot flying made a right roll command input, which resulted in the aircraft entering a shallow right bank and beginning to drift to the right.
  2. The flight crew had limited visual cues available to accurately judge the aircraft's lateral position given the weather conditions, reduced windshield wiper capability and lack of runway centreline lighting.
  3. Once over the runway surface, the flight crew had to judge the aircraft’s lateral position based solely on their assessment of the degree of asymmetry between the runway edge lights. As a result, the onset of drift was not initially noticed.
  4. The severity of the drift was not recognized until the aircraft was less than 10 feet above ground level and rapidly approaching the runway edge, leaving limited time to correct the aircraft’s trajectory before the aircraft contacted the surface.
  5. Once the flight crew recognised that the aircraft would exit the paved runway surface, the pilot flying continued the landing roll as opposed to executing a go-around following contact with unknown terrain and objects.

The formally stated Findings as to Risk were as follows:

  1. There is an increased risk that visual cues may be reduced while flying in precipitation if fitted rain repellent systems are not used.
  2. If the distance between runway edge lights is greater than 50m and runways are not equipped with centreline lighting, there is a risk that visual cues will be insufficient for flight crews to detect lateral drift soon enough to prevent an excursion, while operating aircraft at night during periods of reduced visibility.

Safety Action taken by Air Canada as a result of the excursion and made known to the Investigation included:

  • instituting routine inspection of windshield wiper tensions.
  • adding a “drift training scenario” to pilot full flight simulator training options.
  • extending testing of the hydrophobic windshield coatings introduced in 1996 on other aircraft types to determine its “viability” has been extended to include the A320.

The Final Report of the Investigation was authorised for release on 28 March 2018 and it was officially released on 25 April 2018. No Safety Recommendations were made.

Related Articles

Further Reading