- The Wayfinder
- Tools & Triage
AI 171 Triage Failure: Why This Article Exists
Air India Flight 171 crashed shortly after takeoff on June 12, 2025. The world knew within minutes. But in the days that followed, families faced a different kind of uncertainty about identification, communication, and what legal protections applied. Some received conflicting updates. Others waited for revised confirmations. These moments didn’t just test resilience; they exposed how systems prioritise care, clarity, and responsibility under pressure.
This article uses the term triage failure not to assign blame, but to describe a breakdown in real-time prioritisation across information, support, and legal orientation. We focus on what passengers and their kin experienced, and what the law does and does not offer in such moments.
Instead of updating our earlier article on AI 171’s legal exposure, we’ve written this piece to address a distinct concern: how triage unfolded in real time, and what that means for passengers and their families.
From Tragedy to Legal Blind Spots
The crash of AI 171 triggered an immediate emergency response. Authorities confirmed the accident, and media coverage followed within minutes. But as families sought answers in the hours and days that followed, they encountered a different kind of struggle. The one shaped not by aviation systems, but by legal and procedural opacity.
This section explores how that shift unfolded: from a clearly reported tragedy to a landscape where families had to navigate unclear rights, inconsistent updates, and a legal framework that doesn’t always account for real-time harm.
Why Passengers and Families Deserve More Than Condolences
Authorities confirmed the crash of Air India Flight 171 within minutes. News channels reported it in real time. But in the days that followed, some families received conflicting updates about victim identification. In a few cases, forensics revised the DNA-based identifications. These moments, though not unusual in mass-casualty events, left families navigating uncertainty without clear timelines or legal orientation.
What This Article Will and Won’t Do
This article does not assign blame or speculate on cause. It does not question the intent of responders. Instead, it examines how the carrier and authorities prioritised information, care, and responsibility in real time, and how those choices intersect with legal protections. We use the term AI 171 triage failure to describe a breakdown in process, not a charge of misconduct.
At Travel Tools Unboxed, we aim to clarify:
- What happened after the crash, factually and procedurally
- What the Montreal Convention covers and where it remains silent
- Passengers and families can record what they observe, raise timely questions, and pursue their rights when clarity falters.
What Happened After the Crash
Investigators moved quickly after the crash of AI 171. The Aircraft Accident Investigation Bureau (AAIB) released a preliminary report that confirmed both fuel control switches had transitioned to “CUTOFF” seconds after takeoff. The report included partial cockpit voice recordings and suggested that one pilot may have shut off the fuel supply, though it offered no conclusion. This framing, paired with incomplete transcripts, shaped early public perception.
The Supreme Court stepped in months later, not as part of the investigation, but to address reputational harm. It reviewed the same cockpit data and stated clearly: “Nobody can blame him for anything.” The Court’s remarks didn’t alter the investigation, but they reframed how the public and media should interpret the crew’s actions.
This section traces those developments, what the AAIB reported, how the Supreme Court responded, and what the DGCA did to reinforce oversight. It also highlights what families faced in real time: delays, conflicting updates, and a lack of coordinated support. Together, these threads define the AI 171 triage failure not as a single lapse, but as a pattern of procedural breakdowns under pressure.
The Inquiry So Far
The official response to AI 171 unfolded across three fronts. Investigators issued a preliminary report, the Supreme Court intervened to protect reputations, and the DGCA reinforced oversight. Each action carried its own weight: the report shaped perception, the Court corrected narrative drift, and the regulator tightened compliance. This section introduces these developments and explains how they fit into the broader picture of the AI 171 triage failure.
Preliminary Report: Fuel Control Switches and the Final Moments
The AAIB documented how both fuel control switches transitioned to CUTOFF seconds after takeoff. Investigators noted the crew’s exchange: “Why did you cut off?” / “I did not”, and included partial CVR transcripts. By highlighting crew dialogue without full context, the report shaped early perception and indirectly suggested crew error. Some international media, including the Wall Street Journal, amplified this framing by portraying the event as a possible mass suicide by the captain and even began collecting circumstantial accounts from domestic helpers and security staff to suggest deteriorating mental health. This framing became one strand of the AI 171 triage failure, where incomplete information influenced public understanding.
Supreme Court: “No Blame Attributed to the Pilot”
Pushkar Raj Sabharwal, a former officer of the Directorate General of Civil Aviation (DGCA) and father of the deceased captain, Sumeet Sabharwal, filed a writ petition in the Supreme Court of India. He sought to protect his son’s reputation after early reports implied crew error. The Supreme Court reviewed the preliminary findings and cockpit data, then stated unequivocally: “Nobody can blame him for anything.” The Court criticised selective leaks and reminded the public that only the final investigation report can establish accountability. Its intervention reframed the AI 171 triage failure not only as procedural but also as reputational, underscoring how incomplete information can harm families as much as delayed clarity.
"Nobody can blame him for anything. The pilot cannot defend himself, and selective leaks impede the discovery of the root cause. Only the final report can establish accountability.”
DGCA Oversight and the Public Surveillance Plan
The DGCA responded by expanding audits and publishing its Annual Surveillance Plan. Regulators increased inspections and warned operators of enforcement actions. By taking these steps, regulators restored confidence and worked to prevent recurrence. Yet for families, oversight announcements did little to resolve immediate confusion, another dimension of the AI 171 triage failure.
What Was Missing in Real Time
Institutions moved on official timelines, but families needed clarity in the moment. The gap between rapid crash confirmation and slow, inconsistent updates defined the AI 171 triage failure. This section highlights what families actually faced in those first days: conflicting messages, delayed confirmations, and the human cost of uncertainty.
Delayed Confirmations and Conflicting Messages
Families received inconsistent updates about victim identification. Some were told one thing, only to be corrected days later with revised DNA results. These contradictions created emotional strain and legal uncertainty. The AI 171 triage failure here was not silence, but conflicting signals that undermined trust.
The Human Cost of Triage Failure
Families endured more than grief. They faced unclear rights, shifting information, and the absence of coordinated support. In this context, Air India attempted to secure full legal discharge without informing families that international law provides for unlimited liability if the final report attributes failure to airlines or equipment manufacturers. This omission compounded the AI 171 triage failure, adding legal uncertainty to emotional loss. The lack of transparent communication meant families had to navigate complex obligations and protections on their own, at the very moment they most needed clarity.
Montreal Convention: Rights and Liability Framework
The Montreal Convention governs international air carriage and sets clear rules for compensation. India is a signatory to the Montreal Convention. Under Article 21, airlines face unlimited liability if an accident results from their negligence or that of the manufacturer. The airlines should have informed the families of AI 171 victims of these protections. Yet, Air India attempted to secure full legal discharge for itself and the aircraft manufacturer without disclosing that unlimited liability applied in cases where fault could be attributed. This omission deepened the AI 171 triage failure, leaving families unaware of the legal safeguards designed to protect them. The Convention’s framework matters because it transforms grief into enforceable rights, ensuring that responsibility is not only moral but also legal.
Legal Gaps Under the Montreal Convention
The Montreal Convention provides the international framework for airline liability, protecting passengers and their families in the event of an accident. In the case of AI 171, those protections did not reach families directly. Air India attempted to secure full legal discharge without clarifying that the Convention allows unlimited liability if the final report attributes fault to the airline or its manufacturers. Families only learned of these rights through external lawyers, not through transparent disclosure by the carrier.
This section examines how the Convention should have worked, who informed the families, and why the gap between law and communication deepened the AI 171 triage failure.
Article 17: Carrier Liability Defined
Article 17 of the Montreal Convention establishes the baseline liability of airlines. It states that carriers are responsible for damage sustained in case of death or bodily injury of a passenger, if the accident occurred on board the aircraft or during embarkation or disembarkation. This provision creates a direct link between the accident and the carrier’s responsibility, regardless of fault.
In the case of AI 171, Article 17 should have been the starting point for protecting families’ rights. Yet the way the airline communicated the liability left families uncertain. The AI 171 triage failure was not only about delayed updates but also about how those responsible obscured the legal foundation of the liability.
Scope of Liability
Article 17 covers accidents that occur:
- On board the aircraft
- During embarkation
- During disembarkation
This broad scope ensures passengers are protected throughout the journey, not just in flight.
Strict Liability Principle
The Convention applies a strict liability principle, up to a certain threshold. Families do not need to prove negligence for compensation within that limit. This design simplifies claims and reduces disputes.
Application to AI 171
For AI 171, strict liability should have guaranteed immediate clarity for families. Instead, they faced uncertainty and had to rely on external lawyers to interpret their rights. This gap between law and practice reinforced the AI 171 triage failure, where protections existed on paper. Still, the airline did not communicate it in real time.
Article 21: Unlimited Liability and Its Limits
Article 21 of the Montreal Convention goes beyond the baseline liability set out in Article 17. It establishes that airlines cannot limit compensation if the accident was caused by their negligence or by the aircraft manufacturer’s negligence. This provision is critical because it shifts liability from a capped amount to unlimited liability when fault is proven.
For families of AI 171, Article 21 should have been the safeguard ensuring full accountability. Instead, the absence of clear communication meant families were unaware of the protections available to them. The AI 171 triage failure was compounded by this silence, leaving families to rely on external lawyers to uncover what international law already guaranteed.
Two‑Tier Liability System
- Tier 1: Strict liability up to 100,000 SDR (original Montreal Convention, 1999).
- Tier 1 revised: Increased to 128,821 SDR effective 28 December 2019 (ICAO adjustment).
- Tier 1 latest: Further increased to 151,880 SDR effective 28 December 2024.
- Tier 2: Unlimited liability if investigation establishes negligence or fault against the airline or manufacturer.
This evolving threshold ensures passengers and families receive compensation without delay, while also holding carriers fully accountable when fault is proven.
Application to AI 171
- The airline did not inform the families that unlimited liability would apply if the investigation found fault with Air India or the aircraft manufacturer.
- Air India attempted to secure discharge without clarifying this provision, creating a disclosure gap.
- External lawyers had to explain Article 21 to families, reinforcing the point that institutional silence deepened the triage failure.
Limits and Challenges
- Proving negligence requires access to complete investigation reports, which were delayed or selectively disclosed.
- Families faced reputational harm and legal uncertainty while waiting for final findings.
- The Supreme Court’s intervention helped protect the pilot’s reputation but did not resolve the broader liability disclosure gap.
Institutional Accountability and Oversight
The AI 171 case was not only about liability under international law, but also about how institutions discharged their responsibilities. The families expected regulators, investigators, and oversight bodies, such as the DGCA, AAIB, and international organisations such as ICAO, to provide clarity, transparency, and independence. Instead, conflicts of interest and selective disclosures undermined trust.
Families were left to question whether the investigation was impartial, whether regulators were too close to the airline, and whether oversight mechanisms were strong enough to prevent future failures. This section tests institutional accountability and shows how oversight functioned in practice, and why the AI 171 triage failure became a systemic issue rather than an isolated lapse.
DGCA and Conflict of Interest
In the AI 171 case, the Directorate General of Civil Aviation (DGCA) and the Aircraft Accident Investigation Bureau (AAIB) both operate under the Ministry of Civil Aviation (MoCA). Investigators are often drawn from the same civil service pool, with staff moving interchangeably between DGCA and AAIB as part of career progression. This structural overlap created an inherent conflict of interest. Families expected impartial oversight, yet the ministry’s dual control blurred the line between regulator and investigator, undermining credibility from the outset.
Regulator as Investigator
DGCA regulates Air India, while both DGCA and AAIB are staffed from the same shared pool under the Ministry of Civil Aviation (MoCA). This interchangeable staffing structure means the regulator is effectively investigating the airline it oversees. Independence is compromised not by individuals but by design. MoCA’s dual control blurs accountability. The result is weakened trust and an AI 171 triage failure, where oversight and investigation were never truly separated.
AAIB's Role and Limitations
The Aircraft Accident Investigation Bureau (AAIB) carried the mandate to investigate AI 171. Families expected AAIB to act independently and provide transparent findings. Instead, AAIB relied on investigators seconded from DGCA, which blurred independence and raised doubts about impartiality. By failing to separate oversight from regulation, AAIB weakened confidence in the investigation process.
Investigation Without Independence
AAIB should have delivered a clear, unbiased account of the crash. Instead, it operated with investigators drawn from DGCA, the same regulator that oversees Air India. This overlap compromised credibility. Families saw AAIB as an extension of DGCA rather than an independent body. The bureau’s reliance on selective disclosures reinforced the AI 171 triage failure, in which institutions failed to uphold transparency and accountability.
Institutional Structure of AAIB and DGCA under MoCA
For background on the Aircraft Accident Investigation Bureau (AAIB) and its institutional placement, see the Civil Aviation Ministry’s official page. For analysis of AAIB’s independence and oversight concerns, refer to Civilsdaily’s commentary.
ICAO Standards and Global Oversight
The International Civil Aviation Organisation (ICAO) sets global standards for accident investigation and liability. ICAO expects member states to maintain independent investigation bodies and to update liability thresholds under the Montreal Convention. In the AI 171 case, ICAO’s role was indirect but critical: it provided the framework that India had to follow. When institutions blurred independence, ICAO’s oversight highlighted how far practice had drifted from international standards.
Global Standards, Local Failures
ICAO requires states to separate regulators from investigators and to ensure transparency in accident reports. India signed onto these obligations, yet DGCA and AAIB operated with overlapping personnel and selective disclosures. This divergence weakened confidence in India’s compliance with ICAO norms. Families saw the gap between global standards and local practice as another layer of the AI 171 triage failure, where international oversight existed on paper but failed in execution.
Restoring Confidence and Preventing Recurrence
The AI 171 case exposed not only gaps in liability but also weaknesses in institutional oversight. Restoring confidence requires more than compensation. It demands reforms that prevent recurrence. Families, regulators, and the public need assurance that lessons have been learned and that future investigations will be transparent, independent, and aligned with international standards. This section sets out the reforms required to rebuild trust and ensure that the AI 171 triage failure does not repeat.
Transparency as the First Reform
Transparency is the cornerstone of aviation safety. Without clear communication, families remain in the dark and public trust erodes. Institutions must commit to publishing complete reports, disclosing liability rights, and clarifying investigative processes. Transparency transforms accountability from a legal concept into a lived reality.
Publishing Complete Reports
Institutions must publish final reports in full, without selective leaks or omissions. Families should not rely on external lawyers to discover their rights. When authorities withheld data, many media channels stepped in and triangulated their own timelines using CCTV footage and partial disclosures. This fragmented reporting created confusion and eroded trust. By releasing complete findings, regulators demonstrate independence and credibility.
- Action Point: Reports must be accessible online, in plain language, and translated where necessary.
- Impact: Families gain clarity, and the public sees accountability in practice.
- Global Benchmark: ICAO requires states to publish final accident reports. India must align with this standard.
For readers seeking deeper context on international aviation safety standards, consult the ICAO e‑Library of Final Reports. This resource contains official accident investigation reports submitted to ICAO, offering lessons and benchmarks that connect the AI 171 case to the global framework of transparency and accountability.