ASN Wikibase Occurrence # 216077
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: | Tuesday 18 September 2018 |
Time: | 16:25 LT |
Type: | Airbus A320-214 (WL) |
Owner/operator: | Air Arabia |
Registration: | A6-ANV |
MSN: | 5984 |
Year of manufacture: | 2014 |
Engine model: | CFMI CFM56-5B4/P |
Fatalities: | Fatalities: 0 / Occupants: 48 |
Aircraft damage: | None |
Category: | Serious incident |
Location: | Sharjah Airport (SHJ/OMSJ) -
United Arab Emirates
|
Phase: | Take off |
Nature: | Passenger - Scheduled |
Departure airport: | Sharjah Airport (SHJ/OMSJ) |
Destination airport: | Salalah Airport (SLL/OOSA) |
Investigating agency: | GCAA |
Confidence Rating: | Accident investigation report completed and information captured |
Narrative:Air Arabia flight ABY111, an Airbus A320, took off from the wrong runway at Sharjah Airport, UAE.
There were 42 passengers and six crew members on board. The copilot, under training, was the pilot flying (PF) and occupied the right cockpit seat. The commander on the flight was a training captain and occupied the left seat.
As part of the copilot’s training, the commander had briefed that a rolling takeoff would be conducted. The responsibility for engine start was the commander’s. The copilot taxied the aircraft whereas the commander was on the radio communications.
Tower air traffic control gave clearance for an intersection takeoff from taxiway Bravo 14 for runway 30, which required a left turn for the correct runway. Thereafter, the before takeoff checklist ‘below the line’ items were completed by the flight crew.
Instead of steering the aircraft left following runway 30 lead-on lines from Bravo 14 intersection, the copilot steered the aircraft right for runway 12. The copilot called out that RWY was not showing on the flight mode annunciation (FMA) after the thrust levers were moved to the FLX/MCT detent. As the aircraft accelerated through 57 knots, the commander realized that the aircraft was on the wrong runway and immediately took over control. His decision to continue the
takeoff was based on his perception that there was insufficient available runway for rejecting the takeoff. The commander advanced the thrust levers to TOGA detent and nine seconds after, changed the aircraft flap setting from 1+F to flap 2 position. The aircraft lifted off 20 to 40 meters beyond the end of runway 12. No. 3 main wheel tire received cuts when it struck one approach light during the liftoff.
The Tower controller did not detect that the aircraft had turned unto runway 12 and only noticed when the aircraft was about eight seconds before liftoff.
The commander handed over controls to the copilot and the flight continued uneventfully to the planned destination.
Causes:
The Air Accident Investigation Sector of United Arab Emirates (AAIS) determines that the cause of the runway confusion was the Copilot steering the Aircraft right onto the wrong runway during a rolling takeoff.
Entry to the wrong runway was due to degraded situation awareness of the Aircraft direction by both flight crewmembers due to lack of external peripheral visual watch and runway confirmation.
Contributing Factors to the Serious Incident:
A contributing factor to the Incident was that the air traffic controller did not monitor the Aircraft movement after take-off clearance was given.
Accident investigation:
|
| |
Investigating agency: | GCAA |
Report number: | |
Status: | Investigation completed |
Duration: | 3 years and 3 months |
Download report: | Final report |
|
Sources:
https://www.bea.aero/en/investigation-reports/notified-events/detail/event/incident-grave-de-lairbus-a320-immatricule-a6-anv-et-exploite-par-air-arabia-survenu-le-18092018/ Images:
Graphic: GCAA
Revision history:
Date/time | Contributor | Updates |
06-Oct-2018 14:26 |
harro |
Added |
10-Jan-2022 18:15 |
harro |
Updated [Time, Total occupants, Narrative, Accident report, Photo] |
10-Jan-2022 18:19 |
harro |
Updated [Narrative] |
The Aviation Safety Network is an exclusive service provided by:
CONNECT WITH US:
©2024 Flight Safety Foundation