Indigo Airbus A320 271N incident
Airbus A320 271N · Incident: powerplant system/component malfunction/failure during initial climb
From Dehradun Jolly Grant Airport (DED) to Kempegowda International Airport Bengaluru (BLR)
Narrative check · The NTSB narrative appears to contradict this record's date. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- ENG19WA028
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Incident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Unknown · led by another country; figures from NTSB notifications
- Event fatalities
- Unknown
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- Airline
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Not recorded
Airbus A320 271N
- Aircraft type
- Airbus A320
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- VT-ITP
- Operator
- Indigo
- Onboard fatalities
- Unknown
- Route
- From Dehradun Jolly Grant Airport (DED), DehradunTo Kempegowda International Airport Bengaluru (BLR), Bangalore
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Non-U.S., Commercial
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Initial climb
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Powerplant system/component malfunction/failure
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- None
Cause areas
No findings designated as a cause are recorded in the NTSB data yet.
Not plotted · Location withheld: coordinates are missing, conflicting, invalid, or have no accepted acquisition method. No substitute location has been invented.
NTSB narrative
The government of India has notified the NTSB of an incident involving a AIRBUS A320 airplane that occurred on June 26, 2019. An Indigo Airbus A320 powered by two Pratt & Whitney PW1127G-JM geared turbofan engines experienced issues with the No. 1 (left) engine during climb from Dehradun, Indian to Bangalore, India. During climb, the flight crew heard a loud bang followed by a No. 1 engine stall and indications of high exhaust gas temperature and high engine vibrations. The airplane was diverted to Delhi, Indian for an uneventful landing. Post landing engine inspection of the No. 1 engine confirmed damage to that engine.
The NTSB has appointed a U.S. Accredited Representative as the state of manufacturer of the engine to assist the government of India's investigation under the provisions of ICAO Annex 13. All investigative information will be released by the government of India.
Verbatim NTSB factual narrative from the NTSB dataset
Sources
NTSB record ENG19WA028
- Event ID
- 20190710X94859
- Case number
- ENG19WA028
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: damage. Values present in the bulk record are kept.
- The date is the UTC date the NTSB stores; the local time zone is not recorded, so the local date may differ by a day.
- API snapshot SHA-256: 8ab320bab2abbca44d2fa85d6c536bfe5a56532a9dca77316c45e12e6b6107fa; retrieved 2026-09-16T09:23:50.610Z.