PDA

View Full Version : Indigo A320 at Mumbai on Jan 21st 2017, rejected takeoff due to engine failure


aviatoraj320
22nd Jan 2017, 04:20
An Indigo Airbus A320-200, registration VT-ITF performing flight 6E-248 from Mumbai to Delhi (India), was accelerating for takeoff from Mumbai's runway 27 when the right hand engine (PW1127) emitted a loud bang and sparks prompting the crew to reject takeoff at low speed. The aircraft vacated the runway about 1000 meters/3300 feet down the runway and returned to the apron.

A replacement Airbus A320-200 registration VT-ITD reached Delhi with a delay of 2.5 hours.

Incident: Indigo A320 at Mumbai on Jan 21st 2017, rejected takeoff due to engine failure (http://avherald.com/h?article=4a3cfe26&opt=0)

Just curious to know what made the new Neo engine to fail just in 10 months!! Aircraft is quite new (delivered in Mar-16).

Can any one help?

vilas
22nd Jan 2017, 13:07
Loud bang suggests engine stall. There could be many reasons for it. Too early say anything.

barit1
22nd Jan 2017, 14:51
May be engine related, but not engine caused. Bird or FOD ingestion? Is this possible at BOM? :rolleyes:

Mr @ Spotty M
23rd Jan 2017, 04:16
Engine stall, a loud bang YES, flames YES, but sparks NO. :uhoh:

aviatoraj320
23rd Jan 2017, 11:52
I got this picture from unknown source of engine. Can this explain anything?