Serious incident Airbus A320-251N VT-EXM,
ASN logo
ASN Wikibase Occurrence # 245451
 
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:Friday 13 November 2020
Time:15:50 UTC
Type:Silhouette image of generic A20N model; specific model in this crash may look slightly different    
Airbus A320-251N
Owner/operator:Air India
Registration: VT-EXM
MSN: 8056
Year of manufacture:2018
Engine model:CFMI CFM LEAP-1A26E1
Fatalities:Fatalities: 0 / Occupants: 167
Aircraft damage: None
Category:Serious incident
Location:Chennai Airport (MAA/VOMM) -   India
Phase: Take off
Nature:Passenger - Scheduled
Departure airport:Chennai Airport (MAA/VOMM)
Destination airport:Delhi-Indira Gandhi International Airport (DEL/VIDP)
Investigating agency: AAIB India
Confidence Rating: Accident investigation report completed and information captured
Narrative:
Air India flight AI554, an Airbus A320neo, was advised by ATC (Ground) to expect runway 25 for departure before it was given pushback and start-up clearance. The same was also acknowledged by the crew. The aircraft was then given taxi clearance to the holding point for runway 25 via taxiway ‘E’, ‘B’ and ‘C’. The crew, however, requested an ‘A’ intersection departure. Accordingly, ATC (Ground) revised taxi clearance as taxi via ‘B’ and ‘A’ holding point runway 30 on ‘A’.
The ATC (Ground) then handed over the aircraft to ATC (Tower). ATC (Tower) then gave take-off clearance from runway 25. The aircraft, however, lined up on runway 30 and started rolling for take-off. On observing this, ATC (Tower) immediately instructed the aircraft to cancel take-off, hold position and instructed to stop immediately. The flight crew rejected the take-off at a speed of 67 knots. The crew then requested ATC that they would like to return to the bay. Accordingly, ATC (Tower) gave taxi clearance to vacate via ‘Q1’, ‘Q’ holding point runway 07 and the same was readback by crew. After vacating the runway via Q1, the pilot took a wrong turn and entered taxiway N (not a full taxiway) instead of continuing straight for Q. ATC then instructed the aircraft to hold position and appraised them of the situation.

PROBABLE CAUSE:
The incident occurred due to loss of situational awareness of the flight crew, wherein, the PF started rolling the aircraft on the unassigned runway without ascertaining the intended runway with the available visual cues and improper monitoring of the instruments for the intended runway by PM.
Contributory Factors:
• Not discussing Hotspots (Hotspot 4) during the taxi briefing.
• Crew not observing the aircraft ‘Heading’ when lining up the aircraft on runway 30 (heading 299°) which was not in line with the intended runway 25 (Heading 251).
• The crew in a hurry to complete the flight and return home due to festival in mind.
• Crew also showing urgency to clear the runway as at the back of their mind they had that there is another aircraft on finals for landing.
• Take-off from runway 25/runway30 intersection which crew were not aware at that time.
• Take-off clearance was given (for runway 25 not runway 30) when the PF was lining up the aircraft on unassigned runway i.e., Runway 30 which added to the PFs belief that it was the intended runway.

Accident investigation:
cover
  
Investigating agency: AAIB India
Report number: 
Status: Investigation completed
Duration: 1 year and 4 months
Download report: Final report

Sources:

https://www.bea.aero/en/investigation-reports/notified-events/detail/decollage-depuis-une-piste-non-assignee-arret-decollage/

History of this aircraft

Other occurrences involving this aircraft
19 May 2022 VT-EXM Air India 0 Mumbai-Chhatrapati Shivaji International Airport (BOM/VABB) min
Engine failure

Images:


Chennai aerodrome chart section (AIP)

Revision history:

Date/timeContributorUpdates
08-Dec-2020 20:14 harro Added
07-Apr-2022 08:41 harro Updated [Time, Total occupants, Location, Narrative, Accident report]
07-Apr-2022 08:51 harro Updated [Narrative, Category, Photo]

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