
Was Air India crash mechanical, accidental or…? FAQs answered
Q. Why wasn't the risk flagged by the FAA over six years ago fixed on the Air India plane that crashed?A. That critical FAA warning was only an advisory, not a mandatory directive. Air India had the throttle-control module of this plane replaced twice (2019 and 2023), but maintenance logs show that no inspections for the faulty latch mechanism were performed either time. However, the advisory was that in some 737 (not 787) aircraft, it had been found that those switches were installed with faulty locking. The 787 series of aircraft was also mentioned in the FAA advisory because its switches were similar. From images of the wreckage, it would seem that was not the case with Flight AI171. Then again, deeper material analysis is underway to conclude either way.Q. What was so crucial about the FAA advisory?A. To quote a portion of it: 'The Boeing Company (Boeing) received reports from operators of Model 737 airplanes that the fuel-control switches were installed with the locking feature disengaged The fuel control switch has a locking feature to prevent inadvertent operation that could result in unintended switch movement between the fuel supply and fuel cut-off positions. In order to move the switch from one position to the other under the condition where the locking feature is engaged, it is necessary for the pilot to lift the switch up while transitioning the switch position.If the locking feature is disengaged, the switch can be moved between the two positions without lifting the switch during transition, and the switch would be exposed to the potential of inadvertent operation. Inadvertent operation of the switch could result in an unintended consequence, such as an in-flight engine shutdown.'The advisory also says that based on the limited data at that time, it was considered not to turn it into a mandatory check for airline operators. Now, India's Directorate General of Civil Aviation (DGCA) has asked all airlines that have aircraft mentioned in that advisory to carry out an inspection and furnish a report of the findings by July 21.advertisementQ. Could the highly experienced pilots have accidentally shut off the fuel supply?A. Both the pilots' credentials and flying experience, as well as common sense strongly suggest otherwise. The two pilots were highly experienced on this specific plane. The cockpit voice recorder data has one of them expressing shock when the plane lost upward thrust and questioning the fuel switch cut-off, while the other denies doing so.Critically, the physical thrust levers were found jammed full forward (take-off position), supporting flight data showing maximum power was commanded until impact. The switches themselves were found in 'RUN' mode after the crash. This combination makes a simple pilot error of bumping the switches incredibly unlikely.Q. Why do modern aircraft, especially the Dreamliner, allow cut off of fuel supply manually when the aircraft is airborne? Isn't there failsafe tech to prevent such a thing?A. Experts cite a variety of reasons. For example, the pilot might need to switch off fuel to one or both engines during landing, based on the dynamic landing environment. The engine does not need full power during taxiing. So, the fuel is cut off then as well. Then there is the scenario of an engine catching fire. In such a case, the pilot might have to cut off fuel supply to that engine to save the aircraft. So the existence of the switches and the behaviour of the aircraft are not in question.advertisementThe switches are designed in a way that makes the act of turning them a deliberate, 2-3 second job. Moreover, metal guards are installed on either side of the switches to prevent accidental bumping. Some experts have also talked about failure/malfunction of a chip (microprocessor) linked to the GE engine of the Air India plane. But the report does not talk about such a thing.Q. If not a mechanical malfunction or something accidental, what other reason could be attributed to the switches turning off?A. In that case, only one possibility remains—human error. Some global aviation experts seem to be veering towards this theory. Captain Steve Scheibner, a commercial pilot and leading aviation expert with a wide following on YouTube, is of the view that the only way the switches could be off is if someone manually switched them off, and not by accident. He also points out that India's Aircraft Accident Investigation Bureau has onboarded, among others, an 'aviation psychologist'—perhaps to assess the mental health and stress levels of the Flight AI171 pilots during flight.advertisementThe switches are designed in a way that it takes three fingers and a bit of force to turn them. Thus, it's being argued that it's unusual for them to change position because of cockpit vibration or turbulence. The aviation community is also often quoting the infamous Germanwings Flight 9525 crash of 2015.Q. What happened in the Germanwings crash? Are there similarities to the Air India tragedy?A. On March 24, 2015, Germanwings Flight 9525, from Barcelona to Dsseldorf, had crashed into the French Alps, killing all 150 people on board. Investigations revealed that co-pilot Andreas Lubitz intentionally caused the crash.After the captain left the cockpit, Lubitz locked him out and then deliberately set the autopilot to descend rapidly into the mountains. Despite efforts by the captain to regain entry and calls from air traffic control, Lubitz maintained control and drove the plane into the ground. It was later discovered that Lubitz had a history of severe depression and had concealed his mental health issues from his employer.There is no direct similarity of the Germanwings tragedy to the Flight AI171 crash. However, investigators and experts are drawing parallels in terms of exploring all possibilities, including pilot intent or mental state. The Airline Pilots Association of India has rejected insinuations of suicide or human error and termed such theories as biased. Their argument is also that the pilots are being made to take the fall because they are not around to defend themselves. In any case, a deeper analysis is underway, with a definite outcome of the investigation at least months away.advertisementSubscribe to India Today Magazine- EndsTrending Reel

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


News18
an hour ago
- News18
Patna-Bound IndiGo Flight Aborts Landing, Performs Go-Around Before Safe Touchdown
Last Updated: An IndiGo flight from Delhi to Patna avoided a major accident after an unstable approach forced a go-around at Jay Prakash Narayan Airport. The pilot ensured a safe landing. A Patna-bound IndiGo flight narrowly escaped a major accident after it performed a go-around during its first landing attempt at the city's Jay Prakash Narayan International Airport after the pilot detected an unstable approach. The incident took place on Tuesday around 9 pm when IndiGo flight 6E 2482 travelling from Delhi to Patna narrowly escaped a failed landing attempt. The aircraft with 173 passengers aboard was unable to land in its first attempt due to the short runway and was forced to abort the attempt. As per the reports, the aircraft arrived at Patna airport around 9 pm. However, moments before landing, it took off again, circling three or four times in the air before attempting a second landing. While the landing was successful, the unexpected double landing caused distress among the passengers. The crew members subsequently reassured the passengers that there was no emergency and that the second take-off was due to technical reasons. According to sources, the go-around was a standard safety procedure and was carried out as a precaution. 'It was a normal and safe maneuver. The pilot opted for the go-around to ensure a stable landing approach," a source familiar with the matter said. The eyewitnesses and aviation sources confirmed that the runway, often considered among the more challenging in the country due to its limited length, posed a significant risk during the landing. The pilot's response averted not just a potential crash, but also a collision with the densely populated Polo Road area nearby, which houses several government ministers and senior officials. This incident came just a week after another IndiGo flight, 6E 5009 from Patna to Delhi, returned mid-air following a bird strike on July 9. That aircraft was grounded for maintenance checks, and the flight was cancelled. Passengers were offered a full refund or alternative arrangements, according to the airline. view comments First Published: July 16, 2025, 16:20 IST Disclaimer: Comments reflect users' views, not News18's. Please keep discussions respectful and constructive. Abusive, defamatory, or illegal comments will be removed. News18 may disable any comment at its discretion. By posting, you agree to our Terms of Use and Privacy Policy.


Time of India
2 hours ago
- Time of India
IndiGo flight from Delhi performs go-around before safe landing in Patna
An IndiGo flight from Delhi to Patna performed a go-around while attempting to land at the Jay Prakash Narayan International Airport on Tuesday, sources said. The flight, IndiGo 6E 2482, was carrying 173 passengers when the pilot initiated a go-around due to an unstabilised approach during the first attempt to land. There was no touchdown during the initial approach, and the aircraft landed safely on the second attempt. According to sources, the go-around was a standard safety procedure and was carried out as a precaution. "It was a normal and safe maneuver. The pilot opted for the go-around to ensure a stable landing approach," a source familiar with the matter said. Go-arounds are commonly practised in aviation when pilots determine that the approach does not meet safety or stability parameters. Weather conditions or other operational factors may prompt such decisions. Earlier on July 9, a Delhi-bound IndiGo flight 6E 5009 was forced to turn back mid-air and return to Patna on Wednesday due to a bird strike, the airline's spokesperson informed. Live Events The spokesperson said that the flight has been cancelled for the day to carry out proper maintenance of the aircraft, and the passengers have been offered a full refund or provided with alternative arrangements for their travels. "IndiGo flight 6E 5009 operating from Patna to Delhi on 09 July 2025 turned back to Patna due to a bird strike. Due to the requirement of necessary inspection and maintenance of the aircraft, the flight has been cancelled for the day," the IndiGo spokesperson said. The passengers were subsequently offered refreshments, a full refund on the flight or alternative arrangements for travel. "We are doing our best to minimise inconvenience to our customers, including offering them refreshments, a full refund on cancellation and/or making alternate arrangements for their travel. The inconvenience caused due to this unforeseen situation is deeply regretted. Safety and security of our customers and crew remains our topmost priority," the spokesperson said.


Time of India
4 hours ago
- Time of India
Air India crash: Pilots slam 'deliberate' ambiguity in report timeline
Air India crash KOLKATA: Serving and retired pilots have expressed concern over what they term "deliberate" ambiguity in the timeline mentioned in the preliminary probe report prepared by the Aircraft Accident Investigation Bureau (AAIB) into the AI 171 crash. They allege this has been done to absolve the aircraft manufacturer of any responsibility in the accident and pin the blame on the dead pilots. They also point out that the word "transition" of fuel switches used in the report attempts to insinuate that they were manually moved. "This is an American expression. In India, it would normally have been written: The switches were moved. It is the fuel valves that transition while the switches can move from RUN to CUT OFF or vice versa," a veteran pilot pointed out. While several timelines are mentioned in the report, it is unclear during the crucial phase immediately after takeoff when the two engines momentarily shut down after fuel flow stopped, leading to the crash. The AAIB provides the timestamp to the exact second for a number of actions. The aircraft started rolling at 8:07:37 UTC (13:37:37 IST, i.e., 37 seconds past 1:37 pm). The aircraft and ground sensors recorded the liftoff at 08:08:39 UTC (13:38:39 IST). It then states the aircraft achieved the maximum recorded airspeed of 180 knots (333 km/h) at about 08:08:42 UTC (13:38:42 IST). Thereafter, the timelines become unclear. It says immediately thereafter, engine 1 and engine 2 fuel cutoff switches transitioned from RUN to CUTOFF position one after another with a time gap of 01 second. It then states, 'In the cockpit voice recording, one of the pilots is heard asking the other why he cut off. The other pilot responded that he did not do so.' You Can Also Check: Kolkata AQI | Weather in Kolkata | Bank Holidays in Kolkata | Public Holidays in Kolkata "When did all of this happen and in which sequence? That is a crucial segment of the flight when something catastrophic happened that took down the plane. It is not possible to move both switches from RUN to CUT OFF in a second. The SOP as laid down in the manual for reviving engines during a dual engine failure is to move the switches from RUN to CUT OFF and back to RUN. The pilots in the ill-fated aircraft did so and we know the engines revived but the plane crashed because it did not gain enough altitude to clear the buildings," another experienced captain explained. The report goes on to state that CCTV footage obtained from the airport showed the Ram Air Turbine (RAT) getting deployed during the initial climb immediately after lift-off, but the time is not mentioned. The next timestamp is when the RAT hydraulic pump began supplying hydraulic power at about 08:08:47 UTC (13:38:47 IST). A pilot pointed out that since the RAT takes around 7-8 seconds from auto deployment to begin functioning, then the plane should have lost the engines around 08:08:40 UTC (13:38:40 IST). "If that is so, then how did the plane achieve the maximum airspeed 2 seconds later at 08:08:42 UTC (13:38:42 IST)?" he questioned. Another pilot said it is critical to know the exact conversation that took place in the cockpit from the start of the takeoff run to the Mayday call to know what the pilots were experiencing in the cockpit before the crash. "This is not just for the sake of learning why flight AI 171 crashed but to ensure that another flight does not meet the same fate in the future," a pilot said. Another captain also pointed out that both pilots in the ill-fated flight were wearing headsets and they spoke on different channels, as is the mandatory procedure during takeoff. "Then why is there no clarity on who said what because it's available in the Cockpit Voice Recorder (CVR)?" he questioned.