
Air India Crash Probe Focusing On Movement Of Engine Fuel Control Switches: Report
A report in the well-regarded aviation journal, The Air Current says "the ongoing investigation into the cause of the June 12 crash of Air India flight 171 has narrowed its focus to the movement of the engine fuel control switches."
The article, which attributes its information to "multiple people with knowledge of the investigation," comes in a week when India's Aircraft Accident Investigation Board (AAIB) is expected to make public the preliminary report of its AI-171 investigation.
At the time of publication of this report, neither the AAIB nor the Civil Aviation Ministry have announced the precise date on which the preliminary report will be published, though India, as a member of the International Civil Aviation Organisation (ICAO), is expected to release the report within 30 days of the incident. It is, therefore, widely believed that the preliminary report will be released on July 11, if not earlier.
260 people were killed when AI-171 on a flight from Ahmedabad to London-Gatwick on June 12 crashed within 35 seconds of taking off. 241 people onboard the Dreamliner were killed. The other fatalities were on the ground. One passenger on the Dreamliner had a miraculous escape.
While the article in The Air Current doesn't explicitly say as much, any focus on the fuel-control switches of the Boeing 787 points to the possibility of pilot error.
Aviation experts not related to the crash investigation have told NDTV that in the event of a single-engine failure on AI-171 shortly after take-off, it is conceivable that one of the pilots accidentally switched off the fuel supply to the wrong engine, in other words, the engine which was still operational. In certain situations, including an in-flight engine failure, pilots are expected to switch off fuel flow to a malfunctioning engine as part of operating procedures to 'secure' this unit.
Put simply, if AI-171 had suffered an engine failure on one of its two General Electric Aerospace GEnx-1B engines, the last thing pilots should have been doing is switching off fuel flow to the only operational power plant.
Restarting ('relighting') an engine inflight is not an instant process and needs the pilots to work through a brief set of procedures. With no altitude, and therefore no time available, it may have been impossible for the pilots to have restarted the operational engine on AI-171 and fly out of danger if they realised they had accidentally switched off the wrong one.
NDTV cannot independently verify the accuracy of the report in The Air Current nor confirm that pilot error was, in any way, a primary cause for the crash of AI-171.
The Air Current report additionally points out that ''the lack of any kind of advisory warning from Boeing or GE operators, known as a multi-operator message (MOM) or all-ops wire, in the 13 days that have followed the initial black box reading in Delhi by the AAIB on June 25 is a key signal that a mechanical failure is not immediately suspected as the likely cause of the crash.''
It is still unclear when the final crash report will be published or whether the much-anticipated preliminary report will reveal the likely causes of the first-ever Boeing 787 crash.

Try Our AI Features
Explore what Daily8 AI can do for you:
Comments
No comments yet...
Related Articles


NDTV
11 hours ago
- NDTV
Air India Pilots Cancel Take-Off, Hit Brakes When Plane Was At 155 Km/Hr On Runway In Delhi
New Delhi: An Air India flight from Delhi to Kolkata aborted a take-off while the aircraft was accelerating down the runway due to a technical issue detected just in time. The pilots applied brakes to stop the aircraft, which was travelling at 155 km per hour. Flight AI2403 was scheduled to take off at 5:30 pm today for Kolkata, but a technical issue was detected and the pilots, "following a Standard Operating Procedure", decided not to go ahead with the take-off. The airline in a statement said, "Flight AI2403 operating from Delhi to Kolkata on 21 July 2025 has been rescheduled to depart later this evening, necessitated by a technical issue detected during the take-off roll. The cockpit crew decided to discontinue the take-off, following Standard Operating Procedures." "All passengers have disembarked, and our ground colleagues in Delhi are extending support to them. Inconvenience caused to the passengers due to this unforeseen disruption is sincerely regretted. At Air India, the safety and wellbeing of our passengers remain top priority," they added. This is the second incident involving an Air India aircraft today. In Mumbai, a flight flying in from Kochi had a close shave at the airport while landing after it veered off the rain-soaked runway. Pictures accessed by NDTV show a clump of grass stuck to the rear part of the aircraft and signs of damage on one of the engines. The runway, too, has been damaged. All passengers aboard the aircraft are safe, airport authorities have said. Government sources said that the plane, after landing, made a runway excursion to one side of the runway. "Marking of one wheel of aircraft went into the grassy area on the side of the runway," a source said. Three signage boards and four runway edge lights were found broken after the incident. According to Air India, the aircraft has been grounded for checks, and the inspection is underway. The two pilots have been derostered pending an inquiry into what led to the scare. Notices To Air India Civil Aviation ministry informed Rajya Sabha today in response to a series of queries from MPs that nine show cause notices have been issued to Air India in connection with five identified safety violations in the last six months. Minister of State for Civil Aviation Murlidhar Mohol said over the last six months, no adverse trend was reported in reliability reports of Air India in terms of crashes. But over the last six months, nine show cause notices have been issued to Air India in connection with five identified safety violations. "Enforcement action has been completed in respect of one violation," the minister said in response to queries from CPM member John Brittas, but did not reveal specific details. Last month, an Air India flight from Ahmedabad to London crashed just after taking off, killing 260 people, including 241 passengers. Only 1 passenger on seat 11A survived. The aircraft crashed into a building adjacent to the hospital. Post the AI171 crash, one of the deadliest in recent history, has prompted more scrutiny and exhaustive checks in the aircraft.


New Indian Express
12 hours ago
- New Indian Express
Air India pilot aborts flight just before take-off from Delhi to Kolkata due to technical snag
NEW DELHI: An Air India flight carrying 160-plus passengers from Delhi to Kolkata was steered back to its starting point by the pilots just before take-off on Monday evening due to a techical glitch. The passengers were deplaned and the flight is expected to take-off by late night. Flight No AI 2403 was taxiing for take-off from Terminal 3's runway at 5.51 pm when the incident happened. The flight, an Airbus 321 Neo model was running 20 minutes behind its scheduled time. According to an airport source, 'The flight rejected take-off -- which means the pilot decided to vacate the runway after the pushback – due to some technical issue. Confirming the incident, Air India in a statement said, 'Flight AI2403 operating from Delhi to Kolkata on 21 July has been rescheduled to depart later this evening, necessitated by a technical issue detected during the take-off roll. The cockpit crew decided to discontinue the take-off, following Standard Operating Procedures. All passengers have disembarked and our ground colleagues in Delhi are extending support to them.' AI 2403 returned along its runway path and then headed to the taxiway and returned to the parking bay. The flight is expected to take-off around 9.30 pm on Monday, four hours behind its scheduled start time. This marks a series of flights of Air India suffering technical problems before or after take-off within the last seven weeks. On May 31, a Delhi to Singapore Air India flight (AI 2382) was aborted twice before take-off due to a techncial glitch with passengers stuck inside flight for four hours before they were deplaned. On June 17, an Air India Express Boeing flight (IX 1113) from Delhi to Ranchi, developed a technical issue midair and returned to the Indira Gandhi international Airport. On June 15, an Air India flight (AI 819) from Delhi to Vadodara returned to Delhi after technical issues immediately after take-off.


Time of India
16 hours ago
- Time of India
AI171 crash: Centre issued nine notices to Air India for safety violations in six months; investigation under way
Air India 171 crash NEW DELHI: Over the last six months, Air India has received nine show cause notices linked to five different safety violations, according to minister of state for civil aviation Murlidhar Mohol in the Rajya Sabha. Enforcement action has been completed in one case, while investigations continue into others. A major focus of concern is the tragic crash of Air India Flight AI171 on June 12, 2025. The flight, a Boeing 787-8 Dreamliner en route to London Gatwick, crashed shortly after takeoff from Ahmedabad, killing 260 people. The aircraft went down into a medical hostel complex near the airport, leaving just one survivor out of the 241 people on board. The director general of the Aircraft Accident Investigation Bureau (AAIB) has ordered a formal investigation under Rule 11 of the Aircraft (Investigation of Accidents & Incidents) Rules, 2017. A preliminary report, published after a month of the incident, outlines initial findings, including mid-air engine failure, cockpit confusion, and failed recovery attempts within seconds of takeoff. — ANI (@ANI) Union civil aviation minister Rammohan Naidu addressed the issue on the first day of the Parliament's Monsoon Session, reaffirming the government's commitment to a thorough probe. Despite the incident, MoS Mohol mentioned that no adverse reliability trends have been found in recent reports related to the crashed aircraft. The full investigation is ongoing to determine the root causes and contributory factors behind the deadly crash.