The Switch That Keeps Slipping, Dreamliner Fuel Controls, Recurring Anomalies, and the Erosion of Aviation Certainty
On February 1, 2026, an Air India Boeing 787-8 Dreamliner, scheduled to operate flight AI 132 from London Heathrow to Bengaluru, was preparing for departure. In the cockpit, as the crew conducted their pre-flight checks, an observation was made that would trigger a cascade of inquiries, regulatory interventions, and renewed anxiety about one of the world’s most advanced commercial aircraft. One of the two fuel control switches had moved from the ‘Run’ to the ‘Cutoff’ position.
The crew attempted to reseat the switch. It slipped again. A second attempt produced the same result. Only on the third attempt did the switch remain positively latched in the ‘Run’ position. The crew, after consulting available guidance and assessing the aircraft’s engine parameters—which remained normal throughout—elected to continue the flight. The 8,000-kilometre journey to Bengaluru was completed without further incident. The aircraft was inspected on arrival, cleared for operations, and departed for Delhi on February 5.
On its face, this is a story of successful risk management: a crew identified an anomaly, followed procedures, consulted manufacturer guidance, and completed a safe flight. The regulator conducted an investigation, issued findings, and recommended corrective actions. The airline inspected its fleet and circulated operating procedures. No one was harmed. No accident occurred.
Yet the incident has generated far more scrutiny than its operational outcome would ordinarily warrant. The reason is not what happened on February 1, but what happened on June 12, 2025: the crash of Air India flight 171, another Boeing 787-8, operating from Ahmedabad to London Gatwick. That accident, still under investigation, also involved the aircraft’s fuel control system. The precise relationship between the two events remains unclear, but the similarity is impossible to ignore. A fuel control switch moved unexpectedly. An aircraft was placed in jeopardy. Questions about design, maintenance, training, and regulation that were supposed to have been answered remain disturbingly open.
The recurrence of this anomaly, eight months after a fatal accident and multiple rounds of precautionary inspections, raises questions that extend far beyond the specific technical characteristics of a particular switch on a particular aircraft model. It raises questions about whether the aviation industry’s safety architecture—the interlocking systems of manufacturer design, operator maintenance, crew training, and regulatory oversight—has adequately absorbed the lessons of previous failures. It raises questions about the relationship between Boeing, an original equipment manufacturer still recovering from the 737 MAX crisis, and its airline customers, who must balance safety imperatives against commercial pressures. And it raises questions about the Directorate General of Civil Aviation, India’s aviation regulator, whose response to the February 1 incident has been characterised by some observers as defensive and dismissive rather than inquisitive and precautionary.
The Incident: A Technical Narrative
The Directorate General of Civil Aviation’s official account of the February 1 incident, contained in a detailed “Rejoinder on News Item,” provides the most authoritative technical narrative available. The switch, according to the DGCA, “did not remain positively latched in the ‘Run’ position when light vertical pressure was applied but latched correctly in ‘Run’ and was stable during the third attempt.” The crew “physically verified that the switch was fully and positively latched” and “unnecessary contact with the switch was avoided” for the duration of the flight. Engine parameters remained normal throughout. No cautions, warnings, or system messages were observed.
The DGCA’s account is notable for its precision and defensiveness. It is a “Rejoinder”—a formal response to a previously published report—suggesting that the regulator perceived itself to be responding to criticism rather than proactively investigating an anomaly. Its emphasis on the crew’s successful management of the situation, the absence of adverse engine indications, and the satisfactory performance of subsequent inspections all serve to minimise the significance of the event. The switch moved; the crew fixed it; the aircraft flew; no harm resulted.
This framing is not incorrect, but it is incomplete. It does not address the question that has haunted aviation safety investigations since the 737 MAX crashes: why did the switch move in the first place? The DGCA’s account describes the switch’s behaviour but does not explain it. It notes that Boeing recommended checks and that Air India’s engineering department found both switches functioning satisfactorily, but it does not identify the root cause of the anomaly or explain why a switch that was found to be functioning satisfactorily on the ground had failed to remain latched in the cockpit. It prescribes the circulation of Boeing’s recommended operating procedures to crew members but does not mandate design changes, fleet-wide modifications, or enhanced inspection protocols.
The contrast with the response to the June 2025 accident is instructive. That event, which resulted in a crash and remains under investigation by multiple authorities, has not produced a final public report. Its findings remain incomplete, its causes contested, its lessons unlearned. The February 2026 incident is not the same event, but it is connected to it through the common thread of fuel control switch anomalies. An investigation that does not address this connection, that treats each incident as an isolated occurrence rather than a potential pattern, is an investigation that has already decided its conclusions.
The Historical Context: FAA Safety Alert 2018
The Safety Matters Foundation, an independent aviation safety think tank, placed the February 2026 incident in a disturbing historical context. In 2018, the U.S. Federal Aviation Administration issued Safety Alert for Operators SAIB NM-18-33, warning that certain fuel control switches, including those on Boeing 787s, “could malfunction in this exact manner, increasing the risk of accidental engine shutdown.”
This is not a retrospective reinterpretation of an ambiguous alert. The FAA’s 2018 warning was explicit, specific, and directed at the very aircraft type and component involved in both the June 2025 accident and the February 2026 incident. It identified a known risk—a design vulnerability or manufacturing defect that could cause fuel control switches to move from ‘Run’ to ‘Cutoff’ without pilot action. It recommended inspections, operational procedures, and reporting requirements designed to mitigate that risk.
The recurrence of the anomaly in 2025 and 2026, despite the FAA’s 2018 alert and the precautionary measures implemented by operators and regulators in its wake, suggests one of three possibilities. First, that the FAA’s alert was insufficiently forceful or insufficiently specific, failing to compel the design changes or fleet-wide modifications necessary to eliminate the underlying defect. Second, that the corrective actions taken by Boeing, Air India, and other stakeholders in response to the alert and the subsequent accident were incomplete or inadequately implemented. Third, that the anomaly is caused by a different mechanism than the one identified in 2018—a new failure mode requiring new analysis and new remedies.
Each possibility carries troubling implications. The first suggests a failure of regulatory authority—the FAA, the world’s most influential aviation regulator, issuing an alert that did not produce meaningful corrective action. The second suggests a failure of operator and manufacturer implementation—Air India, Boeing, and others responding to known risks with measures that proved insufficient. The third suggests that the problem is more complex and less understood than previously appreciated—that eight months after a fatal accident, investigators still do not fully understand why fuel control switches move when they should remain stationary.
The Regulatory Response: Defensive or Diligent?
The DGCA’s handling of the February 2026 incident has drawn criticism from some observers who perceive it as defensive and dismissive. The regulator’s “Rejoinder” format, its emphasis on the absence of adverse outcomes, its acceptance of Boeing’s recommended procedures as sufficient corrective action, and its apparent reluctance to mandate more aggressive inspections or design changes have all been cited as evidence of an organisation more concerned with protecting its reputation than with pursuing the truth about a recurring safety anomaly.
This criticism may be overstated. The DGCA did investigate the incident, did document its findings, did require Air India to circulate Boeing’s procedures to crew members, and did oversee post-incident inspections of the airline’s 787 fleet. Its response was not, as some have suggested, a cover-up or a whitewash. It was a routine regulatory response to a routine operational anomaly—the kind of response that occurs hundreds of times annually across the global aviation system without attracting public attention or generating controversy.
Yet the February 2026 incident was not routine. It occurred eight months after a fatal accident involving the same aircraft type and the same system component. It occurred on an aircraft operated by the same airline, maintained by the same engineering department, flown by pilots trained under the same procedures. It occurred despite the FAA’s 2018 alert, despite Air India’s post-accident precautionary inspections, despite the multiple layers of safety assurance that are supposed to make commercial aviation the safest form of transportation ever devised.
In this context, a routine regulatory response is inadequate. The recurrence of an anomaly that was supposed to have been addressed requires not procedural reiteration but fundamental inquiry. It requires asking not only what happened on February 1 but why the measures implemented after June 12 failed to prevent it. It requires examining not only Air India’s compliance with Boeing’s recommended procedures but the adequacy of those procedures themselves. It requires considering not only the performance of the specific switch on the specific aircraft but the possibility of a fleet-wide design vulnerability that no amount of procedural reinforcement can eliminate.
The DGCA’s response, whatever its procedural correctness, does not appear to have engaged with these deeper questions. It has treated the February 2026 incident as an isolated event, not as a data point in a disturbing pattern. It has accepted Boeing’s assurances without independent verification. It has prescribed procedural remedies for what may be a design problem. And it has done so with a defensive posture that suggests sensitivity to criticism rather than openness to inquiry.
The Manufacturer’s Role: Boeing’s Recurring Credibility Challenge
Boeing’s response to the February 2026 incident has been characteristically cautious and circumspect. The company’s statement—”We are in contact with Air India and are supporting their review of this matter”—is the standard formulation used by manufacturers when they wish to appear cooperative without committing to specific actions or accepting responsibility. It is notable for what it does not say: that Boeing has identified the root cause of the anomaly, that it has developed a design modification to prevent recurrence, that it is mandating fleet-wide inspections or retrofits, or that it is cooperating with regulatory investigations beyond routine technical support.
This circumspection is understandable given Boeing’s recent history. The 737 MAX crisis, which resulted in two fatal crashes, a 20-month grounding of the world’s most popular narrow-body aircraft, and billions of dollars in financial losses and reputational damage, has made the company deeply risk-averse in its public communications. Every statement is vetted by multiple layers of legal and public relations review. Every commitment is hedged with qualifiers and contingencies. The company that once prided itself on engineering excellence and safety leadership has become an organisation perpetually on the defensive, more concerned with limiting liability than with advancing knowledge.
Yet this defensive posture is itself a safety risk. The investigation of the June 2025 accident remains incomplete; the root causes of the fuel control switch anomalies remain unidentified; the recurrence of the same problem on a different aircraft suggests that whatever corrective actions were taken after the accident were insufficient. In this environment, Boeing’s reticence is not prudent; it is obstructive. The company possesses technical knowledge about the design, manufacture, and performance of its fuel control switches that no other entity can replicate. Its failure to share this knowledge transparently, to acknowledge potential design vulnerabilities, and to mandate aggressive corrective actions across its global fleet is a failure of its fundamental responsibility as an original equipment manufacturer.
The Human Factor: Pilots at the Interface
Professor David Cirulli of Embry-Riddle Aeronautical University, commenting on the fuel switch issue, emphasised the importance of human factors in aviation safety. “The industry thrives on creating the best and safest means of transportation,” he noted. “One item of focus is the human factor. This study and area of expertise covers a broad range of items, but one in particular is the human-to-machine interface.”
Cirulli’s observation is both reassuring and unsettling. It is reassuring because it reminds us that aircraft design is not a static achievement but an iterative process of continuous improvement, informed by operational experience and evolving understanding of human capabilities and limitations. The multiple movements required to actuate fuel control switches—pull, twist, lock—are not arbitrary; they are deliberate design features intended to prevent inadvertent operation. The industry has learned, through decades of accidents and incidents, that switches controlling safety-critical functions must be protected against unintended activation.
It is unsettling because it suggests that the February 2026 incident may represent not a design failure but a human-machine interface failure—a mismatch between the switch’s design characteristics and the pilots’ operational interaction with it. The crew reported that the switch moved when “light vertical pressure was applied.” This description raises questions about the force required to move the switch, the clarity of its latching feedback, and the training provided to pilots on proper switch handling techniques. If the switch can be moved from ‘Run’ to ‘Cutoff’ by light vertical pressure, is it adequately protected against inadvertent activation? If pilots are not trained to recognise when a switch is not fully latched, is their training adequate? If the switch’s design requires multiple attempts to achieve positive latching, is the design appropriate for its safety-critical function?
These questions are not answered by the DGCA’s rejoinder, Boeing’s supportive statement, or Air India’s procedural compliance. They require independent, transparent, and sustained investigation—the kind of investigation that the June 2025 accident should have triggered but that, eight months later, remains incomplete.
Conclusion: The Pattern and the Precedent
The February 1, 2026 incident on Air India flight 132 was, in operational terms, a successful management of an anomalous situation. The crew identified the problem, applied appropriate procedures, completed a safe flight, and reported the incident for subsequent investigation. No one was harmed. No accident occurred.
Yet the incident is also, in systemic terms, a failure of the safety architecture that is supposed to prevent such anomalies from recurring. The FAA identified this risk in 2018. The aviation industry had eight years to analyse it, understand it, and eliminate it. The June 2025 accident provided a catastrophic demonstration of its potential consequences. And yet, on February 1, 2026, a Boeing 787 Dreamliner preparing for a transcontinental flight experienced the same fuel control switch anomaly that had been documented, warned about, and supposedly addressed.
This is not a coincidence. It is a pattern. And patterns in aviation safety are not merely statistical phenomena; they are indictments of the systems that permit their persistence. Every recurrence of a known anomaly is evidence that the corrective actions taken after its previous occurrence were insufficient. Every recurrence of a known anomaly is an opportunity to ask why the lessons of the past have not been learned. Every recurrence of a known anomaly is a reminder that the aviation industry’s commitment to safety is not measured by its responses to accidents but by its capacity to prevent the same accident from happening twice.
The fuel control switch on the Boeing 787 Dreamliner is a small component in a vast and sophisticated machine. Its movement from ‘Run’ to ‘Cutoff’ is a minor deviation in the normal operation of a highly reliable system. But its recurrence, despite warnings, accidents, and investigations, is a major indictment of the institutions—manufacturers, operators, regulators—responsible for ensuring that such deviations do not persist. The switch that slipped on February 1 is not merely a technical problem awaiting an engineering solution. It is a symptom of a deeper malaise—an erosion of the vigilance, humility, and relentless inquiry that have made commercial aviation the safest form of transportation in human history. Until that malaise is diagnosed and treated, the switch will continue to slip, and the question that haunts every recurrence—why did this happen again?—will remain unanswered.
Q&A Section
Q1: What exactly happened on Air India flight 132 on February 1, 2026, and how did the crew respond?
A1: On February 1, 2026, Air India flight AI 132, a Boeing 787-8 Dreamliner scheduled to operate from London Heathrow to Bengaluru, was preparing for departure when the crew observed that one of the two fuel control switches had moved from the ‘Run’ to the ‘Cutoff’ position. The crew attempted to reseat the switch; it slipped again. A second attempt produced the same result. Only on the third attempt did the switch remain positively latched in the ‘Run’ position. The crew then “physically verified that the switch was fully and positively latched,” according to the DGCA, and elected to continue the flight after confirming that all engine parameters were normal and no cautions, warnings, or system messages were present. The 8,000-kilometre flight was completed without further incident. The aircraft was inspected on arrival in Bengaluru, cleared for operations, and departed for Delhi on February 5. The incident is significant not for its operational outcome—which was successful—but for its similarity to the June 12, 2025 crash of Air India flight 171, another 787-8, which also involved the aircraft’s fuel control system and remains under investigation.
Q2: What is the significance of the FAA’s 2018 Safety Alert (SAIB NM-18-33) in understanding the February 2026 incident?
A2: The FAA’s 2018 Safety Alert is significant because it establishes that the risk of fuel control switches moving inadvertently from ‘Run’ to ‘Cutoff’ was known to regulators and manufacturers eight years before the February 2026 incident. The alert specifically warned that certain switches on Boeing 787s “could malfunction in this exact manner, increasing the risk of accidental engine shutdown.” The recurrence of the anomaly in 2025 and 2026 suggests one of three troubling possibilities: (1) the FAA’s alert was insufficiently forceful to compel necessary design changes or fleet-wide modifications; (2) corrective actions taken by Boeing, Air India, and other stakeholders were incomplete or inadequately implemented; or (3) the anomaly is caused by a different mechanism than the one identified in 2018, requiring new analysis and new remedies. Each possibility implies a failure of the safety architecture that is supposed to identify, communicate, and eliminate known risks. The Safety Matters Foundation explicitly invoked this historical context in its critique, describing the February 2026 incident as “alarming as it mirrors a known risk previously identified by the U.S. Federal Aviation Administration.”
Q3: How did India’s aviation regulator, the DGCA, respond to the February 2026 incident, and what criticisms have been directed at its response?
A3: The DGCA’s response took the form of a detailed “Rejoinder on News Item” —a formal, technical account of the incident that emphasised the crew’s successful management of the situation, the absence of abnormal engine parameters, and the satisfactory performance of subsequent inspections. The regulator required Air India to “circulate the Boeing recommended procedure for the operation of Fuel Cut Off switch to its crew members” and oversaw post-incident inspections of the airline’s 787 fleet. Criticisms of the DGCA’s response include: (1) its defensive framing as a “Rejoinder” suggests sensitivity to criticism rather than openness to inquiry; (2) its failure to address root causes—the note describes the switch’s behaviour but does not explain why it moved or why it failed to remain latched; (3) its acceptance of procedural remedies (circulating Boeing’s procedures) for what may be a design problem requiring engineering modification; (4) its treatment of the incident as isolated rather than as a data point in a disturbing pattern connecting to the June 2025 accident; and (5) its apparent reluctance to mandate more aggressive inspections, design changes, or fleet-wide modifications. Critics argue that a routine regulatory response is inadequate for an incident that recurs eight months after a fatal accident involving the same aircraft type and system component.
Q4: What is Boeing’s position regarding the fuel control switch issue, and how has the company’s recent history shaped its response?
A4: Boeing’s official statement—”We are in contact with Air India and are supporting their review of this matter”—reflects a cautious, circumspect posture characteristic of the company’s communications since the 737 MAX crisis. The statement is notable for what it does not say: that Boeing has identified the root cause of the anomaly, developed a design modification, mandated fleet-wide inspections or retrofits, or accepted responsibility for the recurring problem. This defensiveness is understandable given Boeing’s recent history: two fatal 737 MAX crashes, a 20-month fleet grounding, billions in losses, and enduring reputational damage. The company has become permanently risk-averse in its public communications, prioritising liability limitation over transparent information sharing. However, this defensive posture is itself a safety risk. The June 2025 accident investigation remains incomplete; the root causes of fuel control switch anomalies remain unidentified; the recurrence of the same problem suggests insufficient corrective action. Boeing possesses unique technical knowledge about its switch design and manufacturing; its failure to share this knowledge transparently, acknowledge potential design vulnerabilities, and mandate aggressive corrective actions constitutes a failure of its fundamental responsibility as an original equipment manufacturer.
Q5: Why does the article describe the February 2026 incident as a “failure of the safety architecture” rather than a successful management of an anomalous situation?
A5: The article makes this characterisation because it evaluates the incident systemically rather than operationally. Operationally, the incident was a success: the crew identified the problem, followed procedures, completed a safe flight, and reported the anomaly. However, systemically, the incident represents failure because it should never have occurred at all. The FAA identified this risk in 2018. The aviation industry had eight years to analyse it, understand it, and eliminate it. The June 2025 accident provided a catastrophic demonstration of its potential consequences and should have triggered comprehensive root cause analysis, design review, and fleet-wide corrective action. The recurrence of the same anomaly on a different aircraft, operated by the same airline, eight months after the accident, demonstrates that the corrective actions taken were insufficient. A safety architecture that permits known, documented, accident-linked anomalies to recur is not functioning as intended. The article argues that measuring safety only by the absence of accidents is insufficient; a robust safety culture also measures its capacity to learn from incidents and prevent their recurrence. By this metric, the February 2026 incident is not a success but an indictment of the manufacturers, operators, and regulators who allowed a known problem to persist.
