The preliminary report into the Air India Boeing 787 accident in Ahmedabad made one thing painfully clear to crews and operators: configuration checks at takeoff are not a paperwork exercise. The AAIB’s early findings show the aircraft experienced an almost immediate loss of thrust when both engine fuel-control switches moved from RUN to CUTOFF seconds after liftoff, a sequence that left the crew no time to recover. These are the hard facts investigators published and the ones every flight crew needs to internalize.

From an operational perspective the physical layout and design of those switches matters. On the 787 the fuel control switches sit on the central pedestal, just below the thrust levers. They are spring loaded and require a deliberate pull up before a change of position, a mechanical feature intended to prevent accidental movement. That design detail is important because it means any in-flight change is highly unusual and therefore should be treated as a high-consequence anomaly in procedures and training.

We can split the lessons into three practical tiers: immediate cockpit practice, airline SOP and training changes, and organisational maintenance and oversight.

Cockpit practice

  • Make critical-item callouts explicit. Add a discrete verbal confirmation to the Before Takeoff or Line Up flow that calls out the fuel control switch position in plain language. For example: PM to call “Fuel switches RUN” and PF to acknowledge “Checked, RUN.” That simple verbal cross check buys a second of shared attention during a high workload phase.

  • Reinforce tactile verification and hand placement. When the PM makes the call, physically glance and, if appropriate to the SOP, place a finger near the top of the pedestal to confirm the switch detent. On crews and types where hand positions naturally rest close to the pedestal, standardise a safe hand posture so unintended contact is minimized.

  • Monitor engine indications, not just switch position. Thrust lever position and N1 or EPR response are the ultimate confirmation of thrust. If a thrust lever is at the takeoff setting and engines do not follow expected indications, treat it as an immediate abnormal and follow the appropriate non-normal flows without delay.

Those three items are simple and practical. They do not change the aircraft or the hardware. They do change crew behaviour and reduce the time between an anomalous condition and recognition.

Airline SOP and training

  • Insert a focused config item into the flow. Airlines should consider amending the Before Takeoff/Line Up checklist to include an explicit, short callout that references the fuel switch positions and a required acknowledgement. If operators prefer a single-word callout, keep it unambiguous and practiced.

  • Run realistic simulator scenarios that emulate rapid, unexpected loss of thrust caused by fuel isolation or abrupt engine cutoff. High fidelity simulation of startle and recovery under low altitude, high workload conditions forces crews to rehearse priorities: fly the airplane, maintain energy, and run immediate memory items. Training should stress the PM role in cross checking and the PF role in flying first.

  • Crew resource management refreshers must cover cross-control risks. When controls and essential switches sit close to the pilots’ natural hand positions, small variations in technique, gloves, logging in or reaching for checklists can become causal factors. SOPs should standardise exact hand and arm positions during critical phases.

Maintenance and organisational actions

  • Do the recommended inspections and log the results. The AAIB preliminary material referenced a 2018 FAA advisory that recommended inspecting the locking feature of specific fuel cutoff switches. Regulators and operators should ensure the relevant inspections, even when not mandated, are tracked and documented. Transparency matters.

  • Treat ergonomic design questions seriously. The placement of critical controls under the thrust levers has operational advantages. It also concentrates risk. Operators should work with manufacturers and regulators to assess whether simple, low-cost mitigations are appropriate, for example supplementary guards or more prominent tactile feedback on the switch.

  • Use flight data and technical reports to target recurrent risks. The routine analysis of flight data monitoring and technical logs should flag outliers where control actuation during critical phases appears anomalous. Early detection of trends lets maintenance and training intervene before a crisis.

Why this matters now

The public reporting around the Ahmedabad accident has rightly focused investigators on those fuel-control switches but the lesson for line pilots is broader. Takeoff is short on time and long on consequences. Every checklist item exists because someone decided the risk justified the task. A single additional explicit readback, one standardised tactile habit, and recurrent simulator practice for rapid engine-loss scenarios can materially increase the margin between safe and catastrophic.

A final point on causation and tone. Investigations publish preliminary data to narrow the field of inquiry. The AAIB report did not, and must not, jump to final causal statements in the early pages. Pilots should not use preliminary findings as an occasion for speculation about motive or blame. Instead use them as a prompt to re-examine our normal flows and to make small, direct changes that reduce the chance of an unlikely but deadly error.