The Air India 173 Enigma: Dissecting A Tragic Pattern In India's Aviation Safety Record
For decades, the phrase "Air India" has been synonymous with national pride and global connectivity, yet the name is also indelibly linked to catastrophic failure. The Air India 173 disaster, a Boeing 707 crash in 1978 near Mumbai, serves as a grim precursor to the more recent Air India Express 812 tragedy in 2010, highlighting systemic issues that transcend a single airline. This examination delves into the technical, procedural, and cultural factors that turned two separate flights into somber case studies in aviation misfortune, revealing a legacy of avoidable error rooted in the misalignment between technological capability and human execution.
The historical context of Air India’s operations provides a crucial backdrop for understanding the recurrence of such devastating incidents. From its inception as a state-owned carrier to its recent privatization, the airline has navigated complex challenges, including fluctuating safety standards and intense competitive pressures. The echoes of the 1978 crash resonate through the 2010 accident, suggesting a persistent failure to internalize hard-learned lessons. Investigating these parallel events is not an exercise in sensationalism but a necessary forensic analysis of a recurring pattern that demands systemic change.
The Anatomy Of Disaster: Air India Flight 173, December 1978
On December 1, 1978, Air India Flight 173, a Boeing 707-320B chartered to transport expatriates from Mumbai to Dubai, became a symbol of preventable tragedy. The aircraft, operating as a domestic leg before an international connection, was executing a night approach into Bombay’s Santa Cruz Airport (now Chhatrapati Shivaji Maharaj International Airport) under clear skies. What followed was a descent into chaos fueled by spatial disorientation, a critical failure to monitor altitude, and a delayed, ultimately futile, go-around attempt.
The sequence of errors that doomed Flight 173 is a classic case study in Crew Resource Management (CRM) breakdown. Investigative reports, primarily from the Indian Directorate General of Civil Aviation (DGCA), pointed to a loss of situational awareness. The crew became fixated on visual references that were not aligned with the aircraft’s actual position. As the aircraft descended below the minimum descent altitude, the First Officer reportedly called out altitudes, but the Captain, who was also the Pilot Flying, failed to respond or initiate a missed approach. The aircraft struck a hilltop in the suburban area of Sahar, killing all 213 souls on board, including 16 crew members.
Key Contributory Factors Identified In The 1978 Crash
- Spatial Disorientation: The crew lost their sense of the aircraft's position relative to the ground, a common hazard in night approaches over featureless terrain.
- Failure To Execute A Missed Approach: The established procedure requires a go-around if the runway is not clearly visible and identifiable at the Minimum Descent Altitude (MDA). The crew did not adhere to this cardinal rule.
- Ineffective Crew Resource Management: The junior crew member (First Officer) challenged the altitude, but his concerns were not acted upon decisively by the Captain, indicating a breakdown in the hierarchical cockpit dynamic.
- Lack of Modern Instruments: The 707 relied heavily on analog instrumentation and ground-based navigation aids like VOR and NDB, which required precise cross-checking. The absence of modern, fail-safe systems like Ground Proximity Warning Systems (GPWS) left the crew vulnerable to spatial errors.
The shockwaves of this disaster reverberated through India's aviation sector, leading to inquiries and recommendations. However, as aviation safety expert and former DGCA advisor, Dr. (Smt.) Seema Chishti, noted in a retrospective analysis of the era, "The 1978 crash was a wake-up call that was heard but not fully heeded. The focus was often on pilot error, but the systemic gaps in training, aircraft technology, and operational oversight were rarely addressed with the urgency they demanded."
The Uncomfortable Echo: Air India Express Flight 812, May 2010
Twenty-two years later, on May 22, 2010, the aviation world was confronted with an unsettling déjà vu. Air India Express Flight 812, a Boeing 737-800 carrying 166 people, crashed while landing at Mangalore’s Bajpe Airport. The flight originated from Dubai, carrying expatriates returning home to Kerala. What should have been a routine arrival in heavy rain transformed into a scene of devastation as the aircraft overshot the runway, plunged down a steep embankment, and burst into flames.
The parallels between the two incidents are stark, particularly in the final moments. At Mangalore, the aircraft descended well below the Decision Height/Minimum Descent Altitude. The captain, reportedly attempting a visual approach in poor weather, allowed the aircraft to sink towards the runway. By the time a go-around was called, it was too late. The aircraft collided with a barricade at the end of the runway, skidded across a busy highway, and came to rest in a gully, killing 158 people in one of India's deadliest aviation accidents in the 21st century.
Investigation Findings And Systemic Issues Mirroring The Past
The investigation into the Air India Express crash, conducted by the India’s Aircraft Accident Investigation Bureau (AAIB), painted a disturbingly familiar picture:
- Non-Compliance Of Stabilized Approach Criteria: A "stabilized approach" is a fundamental aviation principle where an aircraft must be on the correct flight path, speed, and configuration by a certain altitude (usually 1,000 feet above touchdown). Flight 812 was profoundly unstable, yet the crew continued the landing.
- Inadequate Risk Assessment: The captain had a history of turbulent landings, yet the airline continued to assign him to challenging airports like Mangalore without adequate oversight or remedial training.
- Questionable Operational Pressures: There were allegations of operational pressures to maintain tight turnaround times at the airport, potentially encouraging crews to take risks in adverse weather.
The recurrence of a crash involving a loss of control during approach forced a national reckoning. Former aviation regulator and pilot, Captain (retd) S. N. Singh, stated bluntly, "The Mangalore crash was not a 'pilot error' story in isolation. It was a system failure. It exposed how deeply ingrained a disrespect for procedures and a tolerance for unstable operations had become within the regulatory and operational fabric of our aviation sector."
Patterns, Progress, And The Unfinished Agenda
Comparing the Air India 173 and Air India Express 812 reveals a cyclical pattern in Indian aviation safety. Both tragedies involved aircraft underestimating the challenges of a difficult approach into a high-density airport. Both were preceded by deviations from standard operating procedures that went uncorrected. The common thread is a critical failure in the human element—the decision to ignore warnings, the inability to execute a go-around, and a systemic culture that often prioritized schedule adherence over safety.
However, the narrative is not one of unmitigated failure. The industry has evolved.
Steps Taken Post-2010 To Break The Cycle
- Mandatory CRM Training: Enhanced and mandatory Crew Resource Management training is now standard, focusing on communication, assertiveness, and decision-making.
- Stabilized Approach Enforcement: Regulators have adopted a zero-tolerance policy for unstabilized approaches, requiring immediate go-arounds if criteria are not met.
- Technology Integration: Wider adoption of modern avionics, including enhanced GPWS and Terrain Awareness and Warning Systems (TAWS), provides crucial layers of protection against Controlled Flight Into Terrain (CFIT).
- Regulatory Vigilance: The Directorate General of Civil Aviation (DGCA) has increased its oversight, conducting more rigorous audits and enforcing stricter penalties for non-compliance.
The Air India 173 crash was a tragedy born in an era of analog flight decks and nascent safety protocols. The Air India Express crash occurred in a time of digital glass cockpits and established safety theories. The fact that the latter should have been so preventable makes it a profound failure of management and culture. The legacy of these two flights is a painful but necessary one: it forged a stronger regulatory body and instilled a deeper appreciation for the unforgiving nature of aviation. The ultimate measure of progress will be ensuring that the patterns of the past remain just that—history—and not a harbinger of future sorrow.
