ASN logo
ASN Wikibase Occurrence # 206908
Last updated: 13 December 2018
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.

Time:c. 18:40 LT
Type:Silhouette image of generic A20N model; specific model in this crash may look slightly different
Airbus A320-271N
Registration: VT-ITJ
C/n / msn: 6967
Fatalities:Fatalities: 0 / Occupants:
Other fatalities:0
Aircraft damage: Unknown
Location:Mumbai-Chhatrapati Shivaji International Airport (BOM/VABB) -   India
Phase: Initial climb
Nature:Domestic Scheduled Passenger
Departure airport:Mumbai-Chhatrapati Shivaji International Airport (BOM/VABB)
Destination airport:Kolkata-Netaji Subhas Chandra Bose International Airport (CCU/VECC)
IndiGo flight 6E395, an Airbus A320neo, returned to land at Mumbai-Chhatrapati Shivaji International Airport in India after suffering engine issues on departure. The aircraft took off from runway 27 at 18:39 hours (13:09 UTC). It circled back and performed a safe landing back on runway 27 at 18:58.
Initially, local media reported that the engine issues were a result of bird ingestion.
The Times of India reported that IndiGo said that the flight had to return to Mumbai "due to a technical glitch (oil chip in one engine) in the aircraft". At the same time, there were strong vibrations and compressor stalls in engine no. 1.
Vibration, compressor surge and stall and chip captions are all symptoms associated with engine bird ingestion.



Revision history:

01-Mar-2018 15:52 harro Added
01-Mar-2018 15:53 harro Updated [Photo, ]
01-Mar-2018 18:02 harro Updated [Operator, Source, Narrative]
02-Mar-2018 06:23 Crabfat Updated [Narrative]
17-Mar-2018 18:46 harro Updated [Aircraft type, Registration, Cn, Source, Narrative]
13-Jul-2018 19:10 harro Updated [Narrative]

Corrections or additions? ... Edit this accident description