After the Neo engine of IndiGo flight number 6E 293 started malfunctioning, the flight was forced to do a technical landing at Port Blair, where firefighters were kept ready for an emergency situation
New Delhi: After two glitches in October, the Neo engine of another aircraft reportedly stopped working after take off. The stricken aircraft belonged to IndiGo and was travelling from Hyderabad to Port Blair on Tuesday.
As one of the engines of IndiGo flight number 6E 293 failed, the aircraft tilted sharply, causing panic among the passengers.
A full emergency was declared and the aircraft was forced to make a technical landing at Port Blair. Fire tenders were kept ready at the airport, but thankfully all the passengers were safely evacuated.
The airline, however, has rubbished the reports. In a statement trying to play down the incident, IndiGo said, "The pilot observed a minor engine sensor issue which did not warrant any automated caution. Hence, the pilot continued the flight and made a normal landing at Port Blair."
Aviation regulator Directorate General of Civil Aviation (DGCA) is probing the matter. But the incident raises a question on not only the aircraft engine that has come under global scanner, but also the timid action by the DGCA while dealing with incidents of mid-air Neo engine failures.
Neo engines worldwide are under the lens due to their faulty sensor. In India, however, the alacrity to deal with the situation has been missing. Last month itself there were at least two Neo-related glitches. On October 15, an IndiGo flight that was on its way from Ahmedabad to Bangalore experienced trouble with one of its Neo engines soon after take off. Later that month, a GoAir flight from New Delhi to Male had to be called back after a technical glitch.
Read Exclusive COVID-19 Coronavirus News updates, at MyNation.
Last Updated 22, Nov 2018, 6:33 PM