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

 Actions

A319, Casablanca Morocco, 2011

From SKYbrary Wiki

Summary
On 8 August 2011 an Air France Airbus A319 crew failed to correctly identify the runway on which they were cleared to land off a visual approach at Casablanca and instead landed on the parallel runway. ATC, who had already cleared another aircraft to cross the same runway, did not notice until this other aircraft crew, who had noticed the apparently abnormal position of the approaching aircraft and remained clear of the runway as a precaution, advised what had happened. Investigation was hindered by the stated perception of the Air France PIC that the occurrence was not a Serious Incident.
Event Details
When August 2011
Actual or Potential
Event Type
HF, RE
Day/Night Day
Flight Conditions VMC
Flight Details
Aircraft AIRBUS A-319
Operator Air France
Domicile France
Type of Flight Public Transport (Passenger)
Origin Paris/Charles de Gaulle Airport
Intended Destination Casablanca/Mohammed V International Airport
Flight Phase Landing
LDG
Location - Airport
Airport Casablanca/Mohammed V International Airport
General
Tag(s) Event reporting non compliant
HF
Tag(s) Distraction
Ineffective Monitoring
Manual Handling
Procedural non compliance
Ineffective Monitoring - SIC as PF
Outcome
Damage or injury No
Causal Factor Group(s)
Group(s) Aircraft Operation
Safety Recommendation(s)
Group(s) Aircraft Operation
Air Traffic Management
Investigation Type
Type Independent

Description

On 8 August 2011, the crew of an Airbus A319 (F-GRXC) being operated by Air France on a scheduled passenger flight from Paris CDG to Casablanca as AF 1896 carried out an approach to and landed on the wrong runway at destination in day VMC. The error was reported to ATC by the crew of an aircraft which had been cleared to cross the runway on which the Air France aircraft landed but had noticed the apparently abnormal position of the Air France aircraft in relation to the clearance it had received and decided not to do so.

Investigation

An Investigation was carried out by the Moroccan DGCA BEA. It was hindered by the failure of the Air France crew to follow prescribed reporting and other procedures after such a Serious Incident. The aircraft commander involved stated that as far as he was concerned “this incident was by no means serious, since it had not compromised safety, and that it did not justify the triggering of a serious incident procedure”. The relevant DFDR data was successfully recovered but the crew had continued as scheduled after the event and so the CVR was overwritten. No ASR was filed following the event and by the time the Investigation was able to interview the crew, they had stated that “given the date of the incident, they could not remember the precise details referred to in the interview” and “they agreed to review certain statements made….after consulting the transcripts of the radio communications”.

It was noted that Casablanca APP had initially cleared the inbound flight to descend to FL050 and anticipate guidance to runway 35L. With the First Officer designated as PF, the approach briefing had been conducted accordingly and was not subsequently revised. A few minutes later, the A319 crew reported ‘field in sight’ and, in answer to a request made by the aircraft commander, were re-cleared to position visually to runway 35L. This was repeated when transferring the flight to TWR a minute later and when landing clearance was subsequently given by TWR for 35L, it was correctly read back. It was concluded that both pilots had been “well rested” and had “showed no sign of fatigue”.

It was established that the prevailing weather conditions had been compatible with a visual approach and a request for one by the flight crew had been approved by ATC. It was considered that “the crew complied with the minimum (VMC) stabilisation height defined by Air France, which on the date of the incident was 500 feet”. However, it was noted that the localiser of the runway 35L ILS which should have been displayed would have been at Full Scale Deflection at the ‘fly left’ position throughout the approach and also that approach stabilisation criteria at the time included that “the aircraft is on the published flight path (horizontal flight and glide slope)”.

The testimony of the flight crew included their opinion that “as regards cockpit resource management…there was nothing to report and that the cockpit was not autocratic”. The First Officer “stated that he had been overconfident during the approach, even though he was not enthusiastic about visual approaches” and that he had “gone along with” the PIC's decision to seek and accept a visual approach. However, he accepted that “he had perhaps been unable to express his viewpoint strongly enough to revert to the initial scenario envisaged during the (approach) briefing and once on the visual approach he was always playing catch-up despite the fact that he was the PF (and) was so focused on the minimum stabilisation height that everything else went unnoticed”. The aircraft commander stated that during the final approach, he had been focusing on the ILS GS display, which according to him was OK, and “had at no time looked at the ILS LOC”.

Runway 35L with runway 35R (designated for take offs) adjacent and the terminal and taxiway on the extreme right (reproduced from the Official Report)

The formally-stated Conclusions of the Investigation included the following:

  • The aircraft was flying high and quickly in relation to the nominal approach path.
  • Owing to the absence of the recordings of the conversations in the cockpit during this incident, it has not been possible to clarify certain details of the incident, in particular the conducting of the pre approach briefing.
  • The attitude of the PIC was not in line with sound practice in terms of crew resource management in the cockpit.
  • The aircraft landed on a runway which had not been assigned to it (runway 35R instead of runway 35L).
  • The PIC failed to apply the instructions of Air France (AF) in the event of a serious incident, which meant that it was impossible to use the CVR data for the time in question.

The Probable Causes were determined as:

  • A visual approach was not anticipated by the crew during their arrival briefing.
  • Cockpit resource management was inappropriate.
  • The aircraft deviated slightly from the nominal approach path.
  • The serious incident was due to confusion between runways by the crew during a visual approach.

Two Contributory Factors were also identified:

  • The change of approach strategy was not discussed (between the pilots) either during the arrival briefing or subsequently.
  • The configuration of Casablanca airport presents a known risk of confusion between the two runways or between a runway and the taxiway.

Three Safety Recommendations were made as a result of the Investigation, at its conclusion, as follows:

  • that Casablanca Mohammed V Airport should remind air traffic controllers of the importance of how they respond and the action they take in the event of air incidents, in line with the regulatory requirements in force.
  • that the French DGAC should raise the awareness of the flight crews of French operators of the types of operational incident requiring application of relevant procedures, in particular those concerning preservation of flight recorder data.
  • that the French DGAC should raise the awareness of the flight crews of French operators serving Casablanca Mohammed V airport of the specific details of this airport, in particular in respect of the possibility of confusion between the runways between the runways and the taxiway.

A reminder was also issued in respect of an earlier Safety Recommendation which had been made:

  • that the ANSP responsible for Casablanca Mohammed V Airport should carry out a Safety Study into the contributory factors which have led to incidents arising from confusion by landing aircraft crews of different airlines in the presence of two parallel runways and a parallel taxiway with no buildings in between.

The Final Report of the Investigation was issued in a French language version only on 22 August 2012 and is also available here on SKYbrary in an [unofficial English language translation].


Editor's Note:

At the time of upload, the Official Investigation Report incorrectly described the aircraft involved as an AIRBUS A-320. It also referred to the Royal Air Maroc aircraft which observed and reported the wrong runway landing to ATC after holding clear of the runway involved despite holding a clearance to cross it as (variably) either RAM560 or AT560 - these being respectively the ICAO and IATA airline designations.

Further Reading