Sunday, 25 October 2026

AUTOMATION AND THE EROSION OF PILOT COMPETENCE: A GROWING CHALLENGE TO AVIATION SAFETY

 As automation takes on more responsibility for flying the aircraft, the aviation industry must confront an uncomfortable question: Are we adequately preparing pilots to take control when technology fails?

The Paradox of the Automated Cockpit

Modern cockpit automation has transformed commercial aviation. Sophisticated Flight Management Systems (FMS), autopilots, autothrust systems and integrated flight guidance have significantly improved navigation accuracy, operational efficiency and flight safety. These advances have reduced routine workload and enabled aircraft to operate with exceptional precision.

Yet this technological progress presents a fundamental paradox. As automation becomes increasingly capable, pilots spend less time actively flying the aircraft, while the consequences of their inability to intervene effectively may become more serious.

The pilot’s role has shifted from direct aircraft control to supervising and managing complex systems. Under normal circumstances, automation performs admirably. However, when systems malfunction, disengage unexpectedly, or behave contrary to crew expectations, pilots may suddenly be required to assume control under unfamiliar and demanding conditions.

The industry must therefore confront a critical question: Has the pursuit of automation efficiency inadvertently weakened the human competencies on which aviation safety ultimately depends?

Automation Confusion: When Expectations Diverge from Reality

One of the most significant hazards in highly automated flight decks is mode confusion—when pilots misunderstand the active automation mode or mispredict how the aircraft will respond.

Modern flight guidance systems incorporate numerous lateral, vertical and thrust-control modes, each governed by specific operating logic. The Flight Mode Annunciator (FMA) displays these modes and provides essential information on active and armed automation functions.

However, simply observing the FMA does not guarantee understanding.

A pilot may believe the autothrust system is maintaining airspeed when the prevailing mode does not deliver the expected speed control. Similarly, an automatic mode transition may alter the aircraft’s vertical trajectory without the crew fully appreciating its implications.

The aircraft may be performing exactly as programmed, while the crew’s mental model of its behaviour is fundamentally flawed.

This divergence is particularly hazardous because pilots may initially attempt to correct an apparent aircraft deviation without recognising the underlying automation state.

Automation surprise, expectation bias and incomplete systems knowledge can combine to delay corrective action. Under high workload, even experienced crews may struggle to reconstruct the system logic while managing the aircraft’s flight path.

The essential discipline is therefore not simply selecting the correct mode, but continuously verifying that aircraft performance aligns with crew intentions and operational requirements.

Lessons Written in Accident Investigations

The 2013 accident involving Asiana Airlines Flight 214 at San Francisco remains a compelling illustration of automation-management failure.

During the Boeing 777’s visual approach, the crew mismanaged the flight path and the autoflight systems. The autothrottle remained in HOLD mode with thrust at idle, while the pilots incorrectly expected automatic airspeed protection. Airspeed progressively decayed without effective corrective action.

The NTSB identified deficiencies in airspeed monitoring, approach management and understanding of autoflight systems as contributing factors to the accident.

The lesson extends beyond the specific aircraft type: sophisticated automation cannot compensate for inadequate understanding of its operating limitations.

Air France Flight 447, which was lost over the Atlantic in 2009, offers a different but equally important warning.

Pitot-probe icing caused unreliable airspeed indications, leading the Airbus A330’s autopilot to disconnect and degrading flight-control protections. The crew was unexpectedly required to fly manually at high altitude under challenging conditions.

Inappropriate control inputs, failure to recognise the aerodynamic stall, and ineffective crew coordination culminated in catastrophe. AF447 was not primarily an automation mode-confusion accident. Instead, it showed the vulnerability that can arise when unexpected automation disengagement meets a crew unprepared to recognise and manage an abnormal aircraft state.

These accidents expose complementary weaknesses: inadequate understanding of automation behaviour and insufficient capability to manage the aircraft effectively when automated assistance is lost.

The Gradual Erosion of Manual Flying Skills

Commercial aviation increasingly operates in an environment where automated flight is routine and manual flying is comparatively limited.

Pilots may spend much of their careers monitoring autopilot-controlled flight, with relatively few opportunities to exercise sustained manual control, particularly in demanding flight regimes.

Automation is unquestionably valuable and often operationally necessary. The concern is not that pilots should routinely abandon automation, but that prolonged dependence may diminish the proficiency and confidence required when manual intervention becomes essential.

Manual flying involves far more than manipulating a sidestick or control column. It demands an intuitive grasp of aircraft attitude, energy state, aerodynamic performance, thrust requirements and flight-path control.

Theoretical knowledge alone cannot sustain these competencies indefinitely.

Like other complex psychomotor skills, they require deliberate practice and periodic reinforcement.

An equally serious concern is the erosion of active monitoring skills. When automation performs reliably for extended periods, pilots may become accustomed to confirming expected behaviour rather than critically assessing actual aircraft performance.

This is a form of automation complacency, compounded by the well-known human difficulty of maintaining sustained vigilance during prolonged periods of low workload.

The danger is not simply that pilots may lose some manual flying proficiency. They may also become less effective at recognising when manual intervention is necessary.

These two vulnerabilities can compound each other, particularly during unexpected system failures or rapidly deteriorating flight conditions.

Fatigue and Stress: Multipliers of Automation Risk

The psychological and physiological pressures of contemporary airline operations further complicate the management of automation.

Irregular duty patterns, extended flight periods, circadian disruption, insufficient restorative sleep and cumulative operational stress can significantly degrade vigilance, working memory, information processing and decision-making.

These cognitive functions are essential for interpreting automation behaviour, detecting anomalies, and initiating timely corrective action.

Automation may reduce workload during routine flight, but an unexpected malfunction can abruptly shift the crew from low workload to cognitive overload.

A fatigued crew may suddenly have to interpret multiple alerts, identify an unfamiliar automation state, assess aircraft energy, execute corrective procedures, and coordinate actions under severe time pressure.

Personal stress, psychological strain and organisational pressures can further erode the cognitive reserves available to manage such situations.

The resulting safety risk is systemic rather than merely individual.

Prescriptive Flight Duty Time Limitations provide necessary safeguards, but compliance does not automatically establish fitness for duty. Effective Fatigue Risk Management Systems (FRMS) must address cumulative fatigue, disruptive scheduling, circadian effects and the realities of operational workload.

Airlines must also create an environment where fatigue and psychological unfitness can be reported without fear of unjustified consequences.

A fatigued pilot supervising complex automation is not necessarily protected by the technology's sophistication. When that technology demands sudden intervention, fatigue may become the decisive vulnerability.

Training Must Evolve Beyond Procedural Competence

The industry’s training philosophy must keep pace with the evolving demands of highly automated flight.

Traditional recurrent training has understandably focused on procedural compliance, systems knowledge and prescribed abnormal or emergency scenarios.

However, proficiency in executing rehearsed procedures does not necessarily demonstrate the ability to recognise and manage unexpected combinations of automation failures, rapidly changing aircraft states and high cognitive workload.

Training should therefore place greater emphasis on understanding system behaviour, anticipating mode transitions, and recognising when automation no longer delivers the intended flight path.

Evidence-Based Training (EBT) and scenario-based simulator exercises should incorporate realistic automation surprises, misleading indications, degraded flight-control modes, and unexpected transitions to manual flight.

Pilots must be trained to simplify automation when appropriate, select more basic guidance modes, or decisively assume manual control when circumstances require it. However, disconnecting automation should never become a reflex. Sound judgement requires understanding whether manual intervention will actually improve safety in the prevailing situation.

Training must also preserve core aircraft-handling skills through structured manual-flying opportunities, both in simulators and during suitable line operations.

The objective should be to produce pilots who can operate sophisticated automation confidently without becoming dependent on it.

Crew Resource Management: The Last Line of Defence

Automation management is fundamentally a two-pilot responsibility.

The Pilot Flying (PF) must maintain control of the aircraft’s flight path, while the Pilot Monitoring (PM) provides independent surveillance, verifies automation behaviour and identifies deviations from intended performance.

Effective monitoring requires more than routine callouts or mechanical acknowledgement of FMA indications. Both pilots must understand the operational consequences of the displayed modes and stay alert for inconsistencies between selected guidance and the aircraft's actual behaviour.

Clear communication, explicit confirmation of mode changes and assertive intervention are indispensable.

Cockpit authority gradients can further undermine these safeguards. A junior pilot who identifies an automation anomaly or deteriorating flight condition must feel empowered to challenge the captain and intervene when necessary.

A strong safety culture must encourage such intervention rather than regard it as insubordination.

Two pilots in the cockpit provide meaningful redundancy only when both remain cognitively engaged and professionally empowered.

The Industry Must Accept Greater Responsibility

It would be simplistic and unfair to attribute automation-related accidents solely to pilot error.

Manufacturers, regulators, airlines and training organisations collectively shape the environment in which pilots operate.

Aircraft systems must be designed around human cognitive capabilities and limitations. Automation mode transitions should be intuitive, annunciations unambiguous, and system protections sufficiently transparent to support informed decision-making.

Airlines must resist treating extensive automation use as a substitute for maintaining manual flying proficiency.

Regulators should ensure training standards assess genuine competence in automation management and aircraft handling, not just procedural completion.

Flight Data Monitoring, confidential safety reporting and Line Operations Safety Audits should be used proactively to identify recurring misunderstandings about automation, monitoring weaknesses and training deficiencies.

Equally, fatigue management, operational scheduling and the psychological well-being of flight crews must be recognised as integral to flight safety, not peripheral personnel matters.

The industry has invested enormously in making aircraft systems more capable and reliable. A comparable commitment is now required to preserve and strengthen the competence of the human operators entrusted with their supervision.

Conclusion: Technology Must Enhance, Not Replace, Airmanship

Automation has unquestionably made aviation safer. Its continued evolution is both inevitable and desirable.

However, the industry’s confidence in technology must not obscure the operational reality that automated systems have limitations, can behave unexpectedly and may require immediate human intervention.

The pilot remains responsible for understanding aircraft behaviour, recognising deviations, exercising sound judgement and taking control when necessary.

That responsibility cannot be discharged effectively without sustained manual flying proficiency, comprehensive systems knowledge, effective crew coordination and adequate cognitive readiness.

The challenge is not to choose between automation and human skill, but to ensure that technological advances do not progressively erode the competencies needed to manage their failures.

Ultimately, aviation safety depends on maintaining the right balance between machine capability and human judgement.

The measure of successful automation is not how completely it removes the pilot from the task of flying, but how effectively it enables a knowledgeable, proficient and alert pilot to remain in command.

The industry must ensure that pilots do not become highly qualified supervisors of systems they are increasingly less prepared to control when those systems cease to function as expected.

Author: G. R. Mohan

Thursday, 22 October 2026

Manipur: A National Crisis That Demands Statesmanship, Not Scorekeeping

 Manipur is bleeding again, and the political class is once more trading blame instead of building peace. The question is not only who failed, but who is willing to help fix it.

On 21 October 2026, Congress President Mallikarjun Kharge took to X to condemn the killing of four civilians in the latest outbreak of violence, blaming what he called the BJP's "incompetence" (UNI). He asked Prime Minister Modi and Home Minister Amit Shah three questions. He asked what had become of the Supreme Court-appointed Justice Gita Mittal Committee's recommendations and of the Court's observations on 31 unnatural deaths in relief camps (Northeast News; India Today NE). He also questioned the political churn of the past two years: President's Rule from February 2025, a change of Chief Minister, and the return of a BJP-led government under Yumnam Khemchand Singh in February 2026 (Newstrack).

These are fair questions. By Kharge's own count, more than 300 people have died since the conflict erupted in May 2023, and thousands remain displaced. But his statement invites an equally fair counter-question: what sustained, constructive role have Congress, the INDIA bloc and the wider opposition played in ending this conflict?

Criticism is legitimate, but it is not a peace plan

In a parliamentary democracy, the opposition has both the right and the duty to hold the government to account. Accountability and cooperation, however, are not mutually exclusive.

The Meitei and Kuki-Zo conflict did not begin with the present government. It is rooted in decades of competing claims over land, tribal status, political representation, identity, security and administrative autonomy. Governments of every stripe have struggled with these fault lines.

Blaming today's government alone for the conflict's origins ignores history. Equally, the BJP cannot escape responsibility for failing to contain the violence and to restore effective governance since May 2023. Both statements are true, and any honest discussion must hold them together.

What a constructive opposition could have done

There is a strong case that Congress and the INDIA bloc could have shown more initiative in reconciliation, not just in criticism.

They could have pressed the Union government for, and committed themselves to, a genuinely representative all-party peace effort. That means bringing in respected Meitei, Kuki-Zo, and Naga leaders, civil society, and independent mediators. Such an effort could focus on the things that actually move the needle:

1. Humanitarian relief and the safe return of displaced families

2. Prosecution of perpetrators, whoever they are

3. Disarmament of unlawful groups and recovery of looted weapons

4. Confidence-building measures between communities

None of this requires the opposition to stop criticising the government. A responsible opposition is judged not only by how well it exposes failure, but also by how much it contributes to fixing a crisis that affects the whole nation.

Rhetoric must not deepen the divide

When communal tensions are already acute, inflammatory language, selective blame and the pursuit of electoral advantage can erode what little trust remains.

Still, we should distinguish political criticism from deliberate incitement. Kharge's statement criticises the government's handling of the crisis. On its own, it does not show that Congress or the INDIA bloc has sought to inflame hostility between communities. Any charge of actively stoking ethnic conflict, against any party, should rest on demonstrable statements or actions, not on political disagreement.

The broader principle applies to everyone: exploiting communal grievance for votes is incompatible with responsible national leadership..

What the opposition has actually done

In fairness, the opposition has not been idle. The record shows several early attempts to engage, most of them in 2023:

Date

Who

What

Nov 2023

Ten Manipur opposition parties

Met Governor Anusuiya Uikey with a memorandum, calling the PM the "only hope" and asking her to arrange a meeting (The Wire)

Jul 2023

INDIA bloc

A delegation of 21 MPs visited Manipur and called for an all-party approach

Jun 2023

Ten Manipur opposition parties, led by Congress

Sought a meeting with the PM from 10 June; handed a peace memorandum to the PMO on 20 June when none was granted (Morung Express)

30 May 2023

Congress, led by Kharge

Gave President Murmu a 12-point memorandum, pledging support for "any initiative" to restore peace (Deccan Herald)

 

On the government side, the Union Home Ministry set up a Governor-led peace committee in June 2023 to facilitate dialogue between the communities.

These efforts deserve recognition, but they also raise an uncomfortable question for both sides: did they last beyond delegations, memoranda, parliamentary speeches, and press conferences? Three years on, with violence flaring again, the evidence suggests not.

Why the national interest must come first

Manipur lies along a sensitive stretch of India's border with Myanmar. Prolonged ethnic hostility there is not only a humanitarian tragedy. It fuels armed militancy, the circulation of illegal weapons, cross-border instability and a slow erosion of public faith in democratic institutions.

That is why national security demands a unified political response. The Union government must lead by providing security, ensuring impartial administration, and creating credible conditions for dialogue. The opposition should actively support reconciliation while continuing to scrutinise the government's performance.

Neither side can resolve this alone. And neither has the right to speak for the Meitei or Kuki-Zo communities without their genuine participation in shaping a settlement they can accept.

The bottom line

Manipur should be treated as a national challenge that calls for bipartisan statesmanship, not as another arena for political point-scoring.

It would be unfair to say the opposition has done nothing but criticise; the record shows otherwise. Yet after more than three years of bloodshed, every party, in government and opposition, deserves scrutiny for failing to sustain a credible, inclusive reconciliation process. The people of Manipur have waited long enough for their leaders to stop keeping score.


Author: GR Mohan

Saturday, 17 October 2026

Air India AI2030: The Mystery of the 7500 Hijack Alert

 The incident involving Air India flight AI2030, a Boeing 787-9 operating from Frankfurt to Delhi on 14 October 2026, raises important questions about transponder operation, human factors, the integrity of ATC surveillance, and how security alerts are handled.

According to reports, Mumbai ATC detected transponder code 7500, indicating unlawful interference. The pilots reportedly denied selecting the code and stated that the flight was operating normally. Nevertheless, the aircraft was diverted to Jaipur, where extensive security checks found no evidence of hijacking.

My principal observation is that the investigation must distinguish between the aircraft actually transmitting code 7500 and an erroneous indication generated within the ground surveillance system. The probability of inadvertent selection is approximately one in a trillion.

However, three possibilities must be distinguished:

Inadvertent crew selection: A human input error, such as entering an incorrect code, cannot be dismissed merely because it involves multiple digits.

Aircraft system malfunction: An avionics or transponder fault could cause the aircraft to transmit a code that differs from the code the crew selected. Such a failure would require technical evidence.

Ground surveillance malfunction: The aircraft could transmit its assigned code correctly, while the surveillance processing or display system erroneously associates code 7500 with the aircraft.

Modern surveillance systems receive, correlate and process aircraft identification and transponder information from multiple sources. Statistically, I have not encountered spurious emergency-code transmissions from the aircraft or triggers in ground-based systems. 

Investigators should therefore examine the original surveillance recordings. If independent surveillance sensors confirm that the aircraft transmitted 7500, attention should shift to cockpit selection, avionics operation and transponder integrity.

Author: GR Mohan

What Flydubai FZ1073 Means for Every Passenger

 On 30 September 2026, the most dangerous person aboard Flydubai flight FZ1073 was not in the cabin. He was in the right-hand seat. Two and a half weeks later, UAE prosecutors described it as an attempted terrorist act, not the breakdown of a troubled pilot. That shift matters to everyone who buys an airline ticket.

When I first wrote about this incident, the working assumption was that a mentally disturbed pilot was acting alone. The evidence has since shifted, and so has my concern. This piece sets out what is verified, what remains speculation, and what it means for the travelling public.

What happened on FZ1073

The flight was a Boeing 737 MAX 8 from Dubai to Tel Aviv, carrying roughly 180 people. As it approached Israel, the co-pilot attacked the captain, and the aircraft descended by thousands of feet. The captain, Indian national Smit Machchhar, was badly wounded but managed to open the flight deck door. Passengers and off-duty Flydubai crew on board then restrained the attacker. The pilots diverted and landed safely at Tabuk, Saudi Arabia. A replacement Flydubai aircraft took the passengers on to Tel Aviv the same day.

Israeli Prime Minister Benjamin Netanyahu said the captain had "managed to prevent a 9/11 disaster". On the evidence released so far, that is not an exaggeration.

What we know, and what we don't

The evidence supports a premeditated terrorist act by an insider. It does not yet support a state-directed or organised campaign. These are two distinct stories, and readers deserve to know which one is proven.

What officials have stated on the record:

· UAE Attorney General Hamad Saif Al Shamsi says the co-pilot attempted a terrorist act. He says the co-pilot attacked the captain with the flight deck crash axe and tried to seize the flight controls. The UAE leads the investigation because the aircraft is UAE-registered.

· A Middle East official told NBC News that the co-pilot planned to fly the aircraft into Ben Gurion Airport.

· Reuters and AP, citing people familiar with the case, identify him as Hamam al-Hammami., an Omani national born in the UAE. He has not been officially identified.

What remains unproven:

1. Iranian involvement. US President Donald Trump said the attacker could be linked to Iran but provided no evidence. A senior US official briefed on the Israeli investigation told NBC there were no indications that Iran directed or took part in the attack.

2. An organised network. Multiple US officials and a former Israeli security official told NBC that early indications point to a lone actor. Israel's UN ambassador said Israel could not yet link the attack to any state or group.

3. The radicalisation pathway. Netanyahu says the co-pilot underwent radical Islamist indoctrination. He has not said what evidence supports this.

The most defensible reading today is of a radicalised lone insider, with the question of who radicalised him still open. That is not reassuring. A lone actor leaves no network to intercept and no communications to monitor. He simply has to show up for work.

One caution for readers following the coverage: political statements have repeatedly outpaced the investigators. Treat any claim not attributed to the UAE investigation with care until the final findings are published.

Israel's response: screening by passport

Israel moved within 24 hours, but the measure is narrower than many headlines suggest. On 1 October, the Ministry of Transport told foreign airlines that pilots and cabin crew flying into Israeli airspace must not hold the nationality or dual nationality of any state without diplomatic relations with Israel. The list reportedly covers 31 countries, including Iran, Oman, Saudi Arabia and Pakistan. Air France and United Airlines have reportedly adjusted crew rosters to comply.

Crew from those states were already barred. The practical change is that dual nationals are now included.

Having audited airline security programmes, I see three problems with relying on this.

1. The existing control was already leaking. Under the earlier directive, foreign airlines checked their own crews against the restricted list. Reports suggest that more than 1,200 crew members from barred countries still entered Israel. A rule on paper is not a control in practice.

2. Nationality is a poor proxy for intent. A radicalised holder of a "friendly" passport passes straight through. The Germanwings co-pilot was German. An Israeli security expert quoted by the Jerusalem Post made the same point: the problem is not only pilots from hostile countries.

3. The friction is real. An Ethiopian Airlines cargo flight was reportedly turned back because of an Indonesian pilot's nationality. Lawyers have warned that carriers applying the rule in Europe may face discrimination claims.

Israel's action is understandable as an immediate containment measure. As a long-term defence, it treats the symptom and leaves the vulnerability unaddressed.

Why more passenger screening will not fix this

The post-9/11 security model was built to stop an outsider carrying a weapon onto an aircraft and forcing a way forward. FZ1073 defeated none of that, because none of it was relevant. The weapon was already mounted in the flight deck. The attacker was legitimately at the controls.

That is my central concern for the travelling public. The instinctive political response to an aviation attack is to add friction at the checkpoint. Longer queues, more pat-downs and tighter liquid rules do nothing to stop a qualified pilot already behind a locked door. Passengers would pay for security theatre aimed at the wrong people.

The reinforced flight deck door is an uncomfortable paradox. Introduced after 9/11, it protects the flight deck from the cabin, not from itself. On Germanwings 9525, it locked the captain out while the co-pilot flew the aircraft into the Alps. On FZ1073, the outcome was averted only because the wounded captain reached the door and opened it.

Pilot-initiated events are not new. What has changed is the motive. Previous cases were largely linked to personal or psychological factors; FZ1073 is alleged to be ideological.

Date

Flight

Outcome

Finding

30 Sep 2026

Flydubai FZ1073

No fatalities; diverted to Tabuk

Alleged terrorist act by co-pilot (UAE investigation ongoing)

24 Mar 2015

Germanwings 9525

150 killed

Deliberate act by co-pilot (BEA)

29 Nov 2013

LAM 470

33 killed

Deliberate act by captain (Mozambique and Namibia investigators)

31 Oct 1999

EgyptAir 990

217 killed

Deliberate inputs by relief first officer (NTSB; disputed by Egypt)

19 Dec 1997

SilkAir 185

104 killed

Deliberate pilot action (NTSB; Indonesian report inconclusive)

Findings as stated in the published accident reports. MH370 (2014) is excluded because its cause remains undetermined.

What the industry should do instead

The burden of the response lies with the crew side of the operation, not the passenger queue. After Germanwings, Europe introduced psychological assessments before line flying and required pilot peer-support programmes. These measures target mental-health decline. FZ1073 shows we now need the equivalent for radicalisation.

Based on my years in flight operations, safety management and IOSA auditing, I would prioritise the following measures:

a) Continuous vetting, not one-off vetting. Most background checks occur at hiring and are refreshed infrequently. Radicalisation can occur years into a career. Periodic re-checks and information-sharing between states and airlines need to close that gap.

b) Insider-threat programmes built into the SMS. Airlines already run just-culture reporting for safety concerns. Crews need a confidential, trusted route to report behavioural red flags about a colleague, handled by trained security staff.

c) A fresh look at two-persons-on-the-flight-deck policies. Europe recommended the rule after Germanwings, then relaxed it to a risk-based approach. Operators flying into contested regions should revisit that risk assessment now.

d) Flight deck equipment as a threat. The crash axe exists for fire and emergency access. Manufacturers and regulators should review its stowage and accessibility.

e) Rapid door-access and incapacitation drills. FZ1073 ended well because the captain reached the door. Cabin crew procedures for a hostile or incapacitated pilot should be trained, not improvised.

f) Intelligence-led risk assessment over nationality lists. Passports are easy to screen and easy to defend politically. Behaviour, associations and access patterns are harder to assess and far more predictive.

None of these measures would add a single minute to a passenger's journey.

For the travelling public: perspective and practical steps

The risk to any individual passenger remains extremely small. Pilot-initiated events number a handful across decades and hundreds of millions of flights. Commercial aviation remains among the safest ways to travel. What has been damaged is confidence, not the statistics.

That loss of confidence is real, and I understand it. For years, we told passengers the threat came from a stranger in seat 23C. Now it can come from the person we trust most on board. Travel that once felt like a pleasure is starting to feel, for some, like an exercise in anxiety..

You cannot vet your pilots. You can still travel sensibly:

1. Keep your seatbelt fastened whenever you are seated. FZ1073 lost thousands of feet in moments. Loose passengers are injured in any sudden manoeuvre, whatever the cause.

2. Know that your crew are trained for emergencies and follow their instructions. In a crisis, the fastest safe outcome comes from crew-directed action, not individual heroics.

3. If the crew ask for help, help. On FZ1073, passengers and off-duty crew acted together under the captain's lead. That cooperation saved the aircraft.

4. Report anything that genuinely concerns you to a crew member rather than discussing it in the cabin or online.

5. Expect disruption on some routes. Crew nationality rules may change schedules on flights to Israel. Check your airline's advisories and your insurance cover before you fly.

6. Judge the response, not just the incident. Ask whether airlines and regulators are strengthening crew vetting or merely lengthening the security queue.

Closing thoughts

FZ1073 did not end in tragedy thanks to a wounded captain, alert passengers, and off-duty crew who happened to be on board. As on United 93, ordinary people became the last line of defence. Who sits in the cabin is not a security system.

The industry now faces a choice. It can respond with visible measures that inconvenience millions of passengers and do little to deter an insider. Or it can do the harder, quieter work of securing the flight deck from within. The travelling public should expect, and demand, the second.

The investigation is ongoing, and I will update this piece as the UAE's findings are published.

Author: GR Mohan

Thursday, 8 October 2026

Eighteen Seconds at 168 Knots: What the VN34 Munich Interim Report Tells Us

 

A Take-off that used 4,000 metres of runway, and then some

On 15 August 2026, a Vietnam Airlines Boeing 787-9 departed from Munich for Hanoi and became airborne from grass beyond the end of runway 26L. Runway 26L is 4,000 metres long, and the afternoon was clear with light, variable winds.

The tail struck the ground; the main gear and tail took out 20 approach lights, and the crew returned two hours later with damaged tyres. All 287 people walked away. The aircraft did not walk away as cleanly; the BFU classifies it as an accident with substantial damage.

The German BFU published its interim report on 28 September. It names no cause yet, and neither will I. But the recorder data already tells a story every airline pilot, training captain, and safety manager should read closely. Here is my take, as someone who has spent a career on both sides of the check-ride table.

What the interim report says

The setup was hot and heavy, but nothing exotic. Munich sits at 1,487 ft. The temperature was 33°C, and the take-off mass was 240,857 kg, against a maximum of 247,207 kg. The crew calculated V1 at 169 kt, Vr at 175 kt and V2 at 180 kt.

On board were 271 passengers, 12 cabin crew and four pilots. The captain on take-off was 64, with 27,182 hours, including 7,795 as a 787 captain. The pilot monitoring had 12,375 hours. The operator's nominated pilot in command sat in the left jump seat.

The key moments from the flight recorders, in local time:

Time

What the recorders show

13:56:12

Take-off mode engaged

13:56:15

Both left-seat brake pedals move; brake command 15% left, 6% right

13:57:03

Airspeed stalls near 168 kt and stays there for about 18 seconds

13:57:12

Brake command peaks at about 27% left, 17% right

13:57:14

AUTOMATION AND THE EROSION OF PILOT COMPETENCE: A GROWING CHALLENGE TO AVIATION SAFETY

  As automation takes on more responsibility for flying the aircraft, the aviation industry must confront an uncomfortable question: Are we ...