“It Was Only a Joke”: Why Words Carry Weight in the Cabin

 What United Flight 1681's return to Las Vegas should teach every passenger who boards with a phone in hand

Every pilot has heard the line: a passenger says something stupid at the gate or on board, the crew reacts, and the explanation comes later—it was only a joke. On Saturday night, 24 October 2026, that explanation was tested again over the Nevada desert, leaving 150 passengers to spend the night in Las Vegas.

What happened

United Airlines Flight 1681, a Boeing 737 carrying 150 passengers and six crew members, departed Las Vegas’ Harry Reid International Airport on a scheduled red-eye flight to Newark. Shortly after take-off, a flight attendant noticed a passenger’s phone screen. According to the arrest report, the passenger, 25-year-old Dante Milne of New Jersey, allegedly texted that he planned to hijack the aircraft and “crash ur row only.” The original message included an expletive.

The flight attendant alerted the captain. About 13 minutes after take-off, the crew set the transponder to an emergency code, secured the flight deck, and turned back. The aircraft landed at about 11:05 p.m., roughly 30 minutes after the emergency began. Las Vegas police met the aircraft at the gate and took the passenger into custody.

He faces one count of making threats or conveying false information about an act of terrorism, an offence punishable by one to 20 years in prison. He was released on US$10,000 bail. At his court appearance on Tuesday, 27 October, his attorney told the judge that he intends to plead not guilty. His next court date is 5 January 2027. Separately, the FAA has confirmed that it is investigating.

The crew got it right

Having spent much of my career in the left seat and as an examiner, I want to give credit where it’s due: this was a textbook example.

The crew did not confront the passenger. Radio reports indicate that the captain told controllers the passenger had no idea what was happening, the crew had gone into lockdown, and no restraint was needed because the passenger was compliant and unaware. That is exactly what you want: isolate a potential threat without alerting it, secure the flight deck, and land at a station where law enforcement is waiting.

The crew also made an airmanship decision most passengers will never appreciate. Shortly after take-off on a transcontinental flight, the 737 was well above its maximum landing weight. The crew told ATC they were overweight and chose to land anyway, using the full runway rather than holding to burn fuel. An overweight landing is a planned, trained procedure that requires a post-landing maintenance inspection. No captain would choose to circle over Las Vegas with an unresolved security threat in the cabin. The crew weighed the risks and made the right call.

“Banter between coworkers”

According to the arrest report, the passenger told investigators he had a beer and several shots at an airport bar before boarding. He then fell asleep and woke to find the aircraft returning to Las Vegas. He said he initially could not recall the messages. Asked specifically about the hijack text, he described it as poorly worded banter between colleagues. He said he never intended to take control of the aircraft and apologised.

He may have meant no harm. But every traveller needs to understand this: the crew has no way of knowing. A flight attendant who sees the words “hijack” and “crash” on a phone screen aboard a climbing aircraft cannot question the sender, check their background, or ask the recipient whether it was a joke. The risk is entirely one-sided. If the crew treats a joke as real, the cost is a diversion and a lost night. If they dismiss a real threat as a joke, the cost is unthinkable. Since 2001, the entire security system has been built on one principle: respond to the words, not the private intent of the person who said them.

The real cost of a few words

United reported that the flight was delayed overnight after the crew reached its permitted duty time, then departed for Newark the next morning. That detail matters: the security response did more than require an extra landing; it used up the crew’s legal duty day. The crew needed a fresh crew and an overnight stay, affecting aircraft rotation and connecting passengers. The crew interviewed all passengers, and baggage was offloaded and rigorously re-screened.

Consider who paid for that message. 150 passengers lost a night, missing onward connections and commitments. Six crew members had their schedules disrupted. The airline covered the costs of the diversion, the overweight landing inspection, hotel and meal provisions, re-crewing, and passenger rebooking. Police and airport resources were also deployed. The individual now faces a criminal case, legal fees, and possible consequences for his job, travel, and reputation.

The penalties can be serious. The FAA may propose civil penalties for each violation, and a single incident can lead to several. The FAA may refer cases to the FBI, which could lead to a felony conviction. Unruly behaviour can also affect a traveller’s eligibility for TSA Precheck and prompt an airline to place the passenger on its internal no-fly list. These consequences are in addition to any criminal charges brought by state or federal prosecutors.

Is bad behaviour on the rise?

It’s tempting to say things are getting worse, but the data tells a more nuanced story. The FAA recorded a peak of 5,973 unruly passenger reports in 2021. The figure fell to 2,096 in 2024 and 1,621 in 2025. Through August 2026, there were 1,163 reports, slightly ahead of last year’s pace. The FAA told the Associated Press that the 2026 count had topped 1,400. Globally, IATA data shows the rate improving from one incident per 307 flights in 2024 to one per 355 in 2025.

The honest picture isn’t a runaway trend. It’s a stubborn baseline that hasn’t gone away, with alcohol repeatedly appearing as an accelerant, as it allegedly did here. Threat “jokes” are a distinct and much more serious category than general unruliness: when the words imply danger to the aircraft, the response shifts from cabin management to a security emergency.

What has changed is the medium. Ten years ago, someone had to overhear a careless remark. Today, it appears on a glowing screen, visible to anyone in the next seat or along the aisle—and, in some cases, flagged by people beyond the aircraft.

A cautionary tale from Europe

In July 2022, an 18-year-old British student sent a Snapchat message joking about blowing up a plane to a private group of friends before boarding an easyJet flight from London Gatwick to Menorca. UK security services flagged the message, prompting the Spanish Air Force to scramble F-18 fighters to escort the aircraft. A search found nothing. Police arrested the young man upon arrival, and he spent time in a police cell.

In January 2024, a Spanish court acquitted him, ruling that the message was sent in a strictly private setting and that he could not have expected it to be intercepted. Even so, he had already endured arrest, custody, and roughly 18 months of legal proceedings. Prosecutors had sought a €22,500 fine, plus €94,800 in damages to the Spanish Ministry of Defence to cover the cost of deploying the fighter.

The lesson is clear: even if a court ultimately accepts that it was a joke, the process itself is the punishment.

The bottom line

Airports and aircraft aren’t ordinary public spaces. They’re security-sensitive environments where certain words trigger an immediate response, and the people responding are trained to take no chances. Words such as hijack, bomb, crash, gun or explosive—and any phrase suggesting harm to an aircraft, its passengers or its facilities—will be taken at face value, whether spoken aloud, typed on a screen or posted online.

My advice to the travelling public is simple: leave the dark humour at home. Don’t joke about it at security, in the cabin or in your group chat, and don’t drink so much that you can’t keep your thumbs in check. The crew’s job is to protect everyone on board, and that’s exactly what they’ll do. The consequences are real: arrest, prosecution, and imprisonment; high legal and financial costs; job loss; reputational damage; being barred from flying; and the disruption and expense imposed on hundreds of innocent people.

A few careless words can cost you far more than you bargained for. In aviation, there is no such thing as “just a joke.”

G R Mohan

The Much-Awaited AI 171 Report: Will We Get Answers, or Just Another Sealed Envelope?

 At the July 28 hearing, Solicitor General Tushar Mehta, representing the government, assured the Supreme Court that the AAIB would complete its work by mid-September, with a buffer extending through the end of October 2026. The AAIB’s affidavit confirmed that it expected to submit the draft final report by October. The court accepted this timeline and deferred any decision on an independent investigation or a Court of Inquiry until it received the report. We are now at the end of that buffer. 

The phrase to watch is “draft final report.” Under ICAO Annex 13, the investigating State circulates a draft to accredited representatives, including the NTSB, BEA, and AAIB-UK, for comment before finalising the report. The AAIB has said the October target reflects the time needed for technical analysis and international consultation before the public release. Whatever lands on the bench may be substantive, but it is not the final word. The final report may still be months away.

The court has also deliberately held back. It deferred the petitions seeking a Court of Inquiry without dismissing them, saying it would consider them once it had assessed the AAIB’s findings for credibility and completeness. The court also directed the AAIB to consider the Federation of Indian Pilots’ technical submission regarding the timing of the RAT deployment.

The two most contentious issues are unlikely to be settled publicly any time soon. The first concerns the CVR. The AAIB has argued that there is an “absolute statutory prohibition” on releasing cockpit voice and airborne image recordings to any external committee or the public. That is correct for the raw recordings. But Annex 13 is equally clear that portions of the record pertinent to the analysis belong in the final report, and only those not essential to it remain protected. The AAIB has already exercised that latitude once. The preliminary report placed the fuel control switches moving from RUN to CUTOFF about three seconds after liftoff and quoted a single exchange in which one pilot asked the other why he had cut off, and the other denied it. That one line has fuelled more than a year of speculation. Now that it has been released, the AAIB owes the families and the profession context. Take-off is a sterile-cockpit phase, during which only matters pertinent to the flight should be discussed. A transcript extract from the take-off roll to the end of the recording would therefore contain little private information and almost nothing that isn’t pertinent. The final report should include it. Anything less leaves a narrative built on one sentence.

The backdrop has not helped. On August 4, AI 2379, an A320neo flying from Phuket to Delhi, briefly lost all three hydraulic systems at FL360. The aircraft climbed 372 ft, stalled for two seconds, then dropped 292 ft, injuring 24 people. The AAIB’s preliminary report found that the captain tested positive for a psychoactive substance and described this as a serious concern requiring priority action by the DGCA. Air India terminated him that same day. However, the report found no causal link between the test result and the hydraulic event. Investigators are still determining whether pressure was actually lost or whether the indications were erroneous. The first officer, who was flying the aircraft, tested negative.

Weeks later, on September 30, flydubai FZ1073 (Dubai–Tel Aviv) turned into a nightmare. The UAE prosecutor general said the co-pilot attacked the Indian captain, Smit Machchhar, with the crash axe and attempted to seize control of the aircraft. The prosecutor characterised the incident as an attempted terrorist act. Reports suggest Oman had previously barred the co-pilot from flying over concerns about radical views. However, the motive has not been officially established.

So here is the question I keep returning to. With pilot conduct under this kind of global scrutiny, will the AAIB be willing to state its findings on AI 171 categorically? If the evidence points to the flight deck, there will be enormous pressure to soften the language. That pressure would come from the families, the pilot community, and a court that has already called the selective early leaks irresponsible. If the evidence points to the aircraft, the pressure would run the other way, towards Boeing, GE, and the entire 787 fleet. Either way, the credibility of Indian accident investigation is on the line. An ambiguous report would satisfy no one and achieve nothing.

Hopefully, we’ll have some clarity in the next couple of weeks, if the Supreme Court decides to make the report—or at least its findings—public.

Author: G R Mohan

Closing the Loop: Accident Investigation and Safety Recommendation Follow-Up in India

 An accident investigation is only as useful as what happens after the report is published. India has built a sound framework for investigating accidents, but follow-up on safety recommendations lacks public visibility, and that gap limits the system's ability to show that lessons are being learned.

This paper examines how India's Aircraft Accident Investigation Bureau (AAIB) and the Directorate General of Civil Aviation (DGCA) handle recommendations once a report is closed. It draws on AAIB's published procedures, its final reports, parliamentary committee findings, ICAO audit results and court filings. The aim is constructive: to identify where the loop between investigation and implementation can be closed, using practices already proven elsewhere.

The framework

1. On paper, India's process for closing safety recommendations aligns with the ICAO model. The addressee must reply within 90 days; AAIB must assess whether the reply is adequate and track progress.

2. AAIB is a relatively young institution. Before 2012, DGCA or a Court of Inquiry investigated major accidents; for example, the 2010 Mangalore accident was investigated by a Court of Inquiry because AAIB did not yet exist (Deccan Herald). AAIB functions as an attached office of the Ministry of Civil Aviation (MoCA), which also oversees DGCA (ICAO COSCAP presentation).

3. The legal basis was updated in November 2025. The Aircraft (Investigation of Accidents and Incidents) Rules, 2025, framed under the Bharatiya Vayuyan Adhiniyam, 2024, replaced the 2017 Rules framed under the Aircraft Act, 1934 (AMS Shardul). AAIB investigates all accidents and serious incidents involving aircraft above 2,250 kg or turbojet aircraft, while DGCA investigates serious incidents involving aircraft of 2,250 kg or less (SCC Online).

4. AAIB's published procedure for safety recommendations, which cites Rule 8(3)(h) of the 2017 Rules, works as follows:

a) AAIB forwards each recommendation to DGCA or the relevant authority.

b) The addressee informs AAIB within 90 days of the action taken or under consideration or explains why no action will be taken.

c) AAIB evaluates the response. If it is inadequate, AAIB consults the addressee and seeks justification.

d) AAIB monitors progress and maintains a database of recommendations and the action taken on each.

Open question: whether the 2025 Rules carry forward the 90-day reply and adequacy assessment unchanged, and whether they add any duty to publish.

What the published record shows

AAIB's final reports are public, but follow-up on their recommendations is not. My review of AAIB's published final reports found the following:

Measure	Count
Final reports reviewed (since [start year])	129
Safety recommendations in those reports	606
Recommendations addressed to DGCA	259
Reports noting that earlier recommendations were still not implemented	11
DGCA replies or AAIB adequacy assessments published	0

AAIB states that it maintains a database of recommendations and the actions taken on each. That record exists but has not been published.

The reports themselves show why these matters. In its final report on the March 2024 accident at Guna involving a Cessna 172S training aircraft, AAIB cited the absence of timely communication from air traffic control as a contributory factor (Deccan Chronicle). The report notes that AAIB had already recommended that DGCA mandate the recording of radio communications between aircraft and ATC, and that "the same recommendation is still pending".

In 2020, AAIB was asked, under the Right to Information Act, what action it had taken on its findings regarding DGCA in two fatal accidents. For both, the reply was: "Matter pertains to DGCA." The reply was procedurally correct, since DGCA is the implementing authority. But it illustrates the gap: once a recommendation leaves AAIB, the public record shows no indication of whether it was accepted, implemented, or closed.

Method notes counts cover only final reports. A recommendation addressed to DGCA jointly with other agencies is counted once under DGCA.

Case study: tabletop runways, 2010 to 2026

The sequence from Mangalore to Kozhikode illustrates how long it took to implement runway safety measures and why a public tracking record would help. AAIB itself noted that the events at Kozhikode mirrored the 2010 Mangalore accident (Udayavani/PTI).

Year	Event
2010	Air India Express B737-800 overruns at Mangalore; 158 fatalities. An expert panel recommends EMAS on tabletop runways (Onmanorama).
2011	A member of DGCA's Civil Aviation Safety Advisory Council writes to senior officials about the adequacy of Kozhikode's runway safety provisions in wet conditions (Gulf News/Bloomberg).
2011, 2017	RESA developed at Kozhikode; EMAS not installed (Onmanorama).
2020	Air India Express B737-800 overruns at Kozhikode; 18 fatalities (Onmanorama).
2021	AAIB publishes its final report with 43 safety recommendations. MoCA forms a high-level panel to examine them and to review implementation of the Mangalore recommendations (Udayavani/PTI).
2023	MoCA states that providing RESA would take about three years after land is handed to AAI (Aviation A2Z).
2024	Environmental clearance recommended for extending RESA from 90 m to 240 m at both ends (Onmanorama).

Many of the delays had genuine causes, including land acquisition, cost, and coordination between central and state governments. The point is not that agencies were inactive. Instead, sixteen years after Mangalore, no single public source shows which recommendations were completed, when, and which remain open. The 2021 review panel's task of establishing the status of the Mangalore recommendations would have been simpler with such a record.

Open question: current completion status of the 240 m RESA at Kozhikode.

Capacity, timeliness and external oversight

Parliament has repeatedly flagged that both the investigator and the implementing regulator are under-resourced. Closing recommendations depend on capacity at both levels.

In 2022, the Standing Committee on Transport, Tourism and Culture noted that AAIB's 2022–23 budget of ₹1 crore fell short of its projected need of ₹4 crore, recommended bringing AAIB's methods and technology up to global standards, and observed that reports sometimes took too long to finalise (PRS India). Its March 2025 report recorded vacancies of 53.8% in DGCA, 34.7% in BCAS and 17% in AAI (Vision IAS). AAIB's own Kozhikode report recommended strengthening AAIB with full-time investigators, a permanent aviation medicine specialist and a flight recorder laboratory (The News Minute/PTI).

The ICAO audit result is often cited as evidence of a strong system. India's overall Effective Implementation score rose to 85.65% in November 2022, up from 69.95% in 2018 (Vajiram & Ravi). However, the 2022 mission did not audit accident investigation (AIG) or air navigation services; the overall score used earlier results for those two areas (The Pioneer). Therefore, the AIG assessment predates 2022.

The AI171 investigation has brought these questions before the Supreme Court. Petitions seeking a court-monitored inquiry were filed in 2025, and AAIB has opposed a parallel investigation, arguing that Annex 13 and Indian law provide a complete framework (Deccan Herald). The court chose to await AAIB's report, which the government said it would file in a sealed cover in early October 2026 (Business Today). The investigation is complex, and international practice allows final reports to take longer than a year, provided it issues interim statements.

Open question: outcome of the 13 October 2026 hearing.

Transparency of investigation material

Protecting cockpit voice recordings is essential, but a well-established middle ground exists between releasing audio and releasing nothing.

AAIB has told the Supreme Court that Rule 17(5) of the 2025 Rules prohibits public disclosure of CVR audio and airborne image recordings (Outlook). This protection is sound. Pilots accept cockpit recording because authorities use the audio only for safety investigations, and very few authorities release it.

Transcripts are treated differently. Under Rule 17, the Central Government may disclose protected records, including CVR transcripts, if it determines disclosure is necessary, despite its impact on investigations (Asianet Newsable). ICAO Annex 13 also permits the parts of a CVR record pertinent to the analysis to be included in the final report. Peer investigation authorities routinely publish relevant transcript excerpts in their final reports, while withholding personal or irrelevant conversation.

Two refinements would strengthen confidence without compromising protection. First, final reports could include timestamped transcript excerpts relevant to the analysis, as peer authorities do. Second, an independent body outside the ministry that oversees the regulator, such as a judicial authority, could make the disclosure-balancing decision, as several states have arranged.

How other investigation bodies close the loop

Several established investigation authorities make recommendations for follow-up public, and their models could be adopted without new legislation.

Authority	Public follow-up practice
NTSB (United States)	Publishes each recommendation, the recipient's response and a status classification, searchable online
AAIB (United Kingdom)	Publishes recommendation responses and its assessment of them; sits within the Department for Transport yet is widely regarded as independent in practice
European Union (Regulation 996/2010)	90-day reply requirement similar to India's; recommendations and responses recorded in a central EU database
ATSB (Australia)	Publishes responses and the current status of each recommendation

The UK example is instructive. Administrative location within a ministry does not, by itself, determine credibility. Publishing responses and a consistent practice of candour carry most of the weight.

Open question: confirm the current details of each practice against the authorities' own websites before citing.

Recommendations

Five measures would make follow-up visible, ordered from simplest to most involved. The first three require no changes to the law.

1. Publish the existing database. For each recommendation, display the addressee, the reply, AAIB's adequacy assessment, and the current status, as AAIB already records them.

2. Report annually to Parliament on open recommendations, including how long each has been open, to ensure long-pending items receive attention.

3. Include relevant CVR transcript excerpts in final reports, as permitted by Annex 13 and practised by peer authorities, while continuing to protect audio and personal conversation.

4. Place the disclosure-balancing decision under Rule 17 with an authority independent of the regulator's parent ministry, such as a judicial authority.

5. Strengthen AAIB's structural independence and capacity, including a direct reporting line outside the ministry that oversees DGCA, full staffing, and responsibility for investigating serious incidents involving light aircraft.

Conclusion

India's investigators produce detailed reports and make substantial recommendations. What is missing is the final step: a public record showing that each recommendation has been addressed, assessed and closed.

The information already exists within AAIB. Publishing it would cost little, credit agencies that have acted, and let the public, Parliament, and the industry see where work remains. It would also strengthen confidence in AAIB at a time when its largest investigation is under scrutiny. Every investigation aims to ensure the same accident does not happen twice. A transparent closure record shows that a system has learned.

Author: G R Mohan

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

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