Serious incident Airbus A320-214 (WL) OE-IJF,
ASN logo
ASN Wikibase Occurrence # 238943
 
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information.

Date:Monday 20 July 2020
Time:07:19 LT
Type:Silhouette image of generic A320 model; specific model in this crash may look slightly different    
Airbus A320-214 (WL)
Owner/operator:easyjet Europe
Registration: OE-IJF
MSN: 6675
Year of manufacture:2015
Engine model:CFMI CFM56-5B4/P
Fatalities:Fatalities: 0 / Occupants: 155
Aircraft damage: None
Category:Serious incident
Location:Paris-Charles de Gaulle Airport (CDG/LFPG) -   France
Phase: Take off
Nature:Passenger - Scheduled
Departure airport:Paris-Charles de Gaulle Airport (CDG/LFPG)
Destination airport:Málaga-Costa del Sol Airport (AGP/LEMG)
Investigating agency: BEA
Confidence Rating: Accident investigation report completed and information captured
Narrative:
An easyJet Europe Airbus A320-214 (OE-IJF) and a United Airlines Boeing 787-10 (N16009) were involved in a runway incursion incident at Paris-Charles de Gaulle Airport, France.
The A320, easyJet flight U23955 to Malaga, Spain, was cleared to line up on runway 09R for departure. At the same time the B787, United flight UA57, was on approach to runway 09L. The crew of N16009 was then cleared to land on runway 09R. The crew read back and offset to land on runway 09R. The crew of the OE-IJF, cleared to line up on runway 09R for take-off, detected the situation and reported it on the frequency. The crew of N16009 aborted the approach and overflew the A320 at an height of about 100 m.

Contributing factors
The following factors may have contributed to both the controller’s lapsus leading to a landing clearance being given for an occupied runway, and to her not checking the read-back:
- The controller chiefly managing traffic on runway 09R at this time (one landing, two upcoming departures and two crossings on this runway).
- The controller having her mind on the change of position from NE LOC to NW LOC.
- The controller’s lack of practice linked to the reduction in traffic during the COVID-19 health crisis period.
- The Boeing 787 crew’s use of the non-standard expression “understand” instead of the expression “confirm” which might have attracted more attention from the controller.
The day of the occurrence, the NW LOC position in the control tower, normally occupied by a LOC controller when easterly operations are in force was initially not operational.
From the NE LOC position used as a fallback position, the LOC controller did not have direct sight of the thresholds of runways 09. This situation may have contributed to the Boeing 787’s change in flight path during the final approach not being identified and the resulting conflict with the Airbus A320 cleared to line up on the same runway.
The vigilance of the two crews, in particular the Airbus A320 crew’s check of the final approach path before lining up and the Boeing 787 crew’s identification of the plane lining up on the runway contributed to a potential collision on the runway being avoided. At the same moment, the PREFLIGHT/GROUND controller also acquired sight of the Boeing 787 carrying out a sidestep.

Accident investigation:
cover
  
Investigating agency: BEA
Report number: 
Status: Investigation completed
Duration:
Download report: Final report

Sources:

https://www.bea.aero/en/investigation-reports/notified-events/detail/event/serious-incident-to-the-boeing-787-registered-n16009-operated-by-united-and-to-the-airbus-a320-regis/

Revision history:

Date/timeContributorUpdates
01-Aug-2020 11:53 harro Added
25-Jul-2021 10:51 harro Updated [Total occupants, Destination airport, Narrative, Accident report]
03-Dec-2021 20:54 harro Updated [Narrative, Accident report]

Corrections or additions? ... Edit this accident description

The Aviation Safety Network is an exclusive service provided by:
Quick Links:

CONNECT WITH US: FSF on social media FSF Facebook FSF Twitter FSF Youtube FSF LinkedIn FSF Instagram

©2024 Flight Safety Foundation

1920 Ballenger Av, 4th Fl.
Alexandria, Virginia 22314
www.FlightSafety.org