Ariana Afghan Airlines Runway Excursion Exposes Deep Safety Crisis

Ariana Afghan Airlines' Boeing 737-400 runway excursion in Kabul reveals systemic fleet age problems, repeated incidents, and a crisis communications failure that cited a fatal crash as deflection.

When an airline's official response to a runway excursion involves pointing at a fatal crash and saying 'see, it happens everywhere,' the problem runs far deeper than wet pavement. Ariana Afghan Airlines' March 25 incident at Kabul International Airport, where a Boeing 737-400 skidded off Runway 29 into the grass with enough force to damage the left wing, was serious on its own terms. The airline's subsequent statement, which invoked the Air Canada LaGuardia collision that killed two pilots just three days earlier as evidence that 'such incidents are common in the world,' transformed a survivable accident into a reputational catastrophe that reveals everything wrong with how this carrier approaches safety culture.

The Incident: More Than a Wet Runway

The facts are straightforward but concerning. Registration YA-PIC, a Boeing 737-4Y0 formerly operated by Turkish Airlines, was on approach to Kabul's Runway 29 during heavy rain on March 25. The aircraft touched down, lost directional control, departed the right side of the runway, crossed a taxiway, and came to rest in grass with structural damage to the left wing. All passengers and crew evacuated via emergency slides. No injuries were reported.

Aquaplaning on a rain-soaked runway is a known hazard with well-established mitigations. Grooved runway surfaces channel water away from tire contact patches. Proper approach speed management, correct flap configuration, and immediate deployment of thrust reversers and spoilers on touchdown all reduce the risk. Pilots operating into airports with known drainage issues are expected to add speed corrections and plan for longer stopping distances. The question is whether all of these protocols were followed, and whether the runway surface at Kabul meets the standards that make them effective.

Kabul International Airport's Runway 11/29 supports medium and wide-body operations, but the facility has operated under reduced maintenance standards since 2021. While the Taliban's Civil Aviation Authority has completed some infrastructure projects, including a new main gate and fiber optic installation in 2025, these are cosmetic compared to the runway surface maintenance, drainage systems, and instrument landing calibrations that directly affect landing safety. The terminal shows visible wear, and many international-standard amenities remain limited or unavailable.

This matters because runway excursions are not random events. They cluster around airports with degraded surfaces, inadequate drainage, and limited precision approach aids. Kabul's 3,511-meter runway is long enough for 737 operations with generous margins, which means stopping distance was not the primary constraint. The aircraft departing the side of the runway, rather than overrunning the end, points toward directional control failure during the ground roll, a scenario where tire condition, anti-skid system performance, and runway surface friction all interact.

A Pattern, Not an Anomaly

This is where the airline's 'these things happen' defense collapses entirely. The March 2026 Kabul excursion was not an isolated event. Just seven months earlier, in August 2024, another Ariana 737-400, registration YA-PID, overran the runway during takeoff at Khost Airport. That aircraft plowed through the airport perimeter fence before becoming airborne, then diverted to Kabul with cracks in both mounts of the vertical stabilizer and severe aft fuselage damage. One hundred and ten passengers were aboard.

The Khost incident involved a different failure mode (takeoff performance rather than landing deceleration) but the same fleet type and the same airline. Two runway excursions in under eight months from an operator with only five active 737-400s is not statistical noise. It is a pattern that demands investigation into maintenance practices, crew training, and operational decision-making.

Zoom out further and the pattern becomes starker. In 2014, YA-PIB overran the runway at Kabul and was destroyed. That same year, YA-PIE suffered a gear collapse on landing at Kabul. The Aviation Safety Network database lists 13 hull-loss events for Ariana across its history, seven of them fatal, including the 1998 Boeing 727 crash on approach to Kabul that killed all 45 aboard. These are not ancient history for a carrier operating just six airframes. They represent a rate of attrition that would ground any airline operating under ICAO-compliant regulatory oversight.

Which brings up the uncomfortable reality: Ariana has been banned from European Union airspace since October 2006. The EU initially allowed a single France-registered Airbus A310 to continue service in March 2006, then extended the prohibition to the entire fleet six months later. Twenty years on, the ban remains in place. The EU Air Safety List exists specifically to flag carriers where regulatory oversight is insufficient to ensure safe operations. Ariana's continued presence on that list is not bureaucratic inertia. It reflects ongoing deficiencies that have never been adequately resolved.

The Fleet Problem No One Can Fix

At the core of Ariana's operational risk sits a fleet with an average age of 32.8 years. The five Boeing 737-400s that form the backbone of domestic and regional operations are airframes that most carriers retired a decade ago. The 737-400, a second-generation Classic variant that entered service in 1988, was superseded by the Next Generation 737-700 and 737-800 in the late 1990s. Major operators phased out their -400 fleets by the mid-2010s. Finding certified replacement parts, qualified maintenance technicians with type experience, and serviceable engines for these aircraft becomes more difficult and expensive with each passing year.

Ariana's January 2026 acquisition of a 737 engine from Serbia underscores the scarcity problem. When you are sourcing powerplants from the secondary market in southeastern Europe, your supply chain is operating at the margins. Every aging airframe requires exponentially more inspection hours, more structural repairs, and more component replacements to remain airworthy. The economic pressure to defer non-critical maintenance items intensifies when the airline operates under sanctions constraints that limit access to international capital markets, OEM support channels, and insurance underwriters willing to cover high-risk operations.

The airline announced intentions in August 2025 to acquire two Airbus A330s and two additional Boeing 737s. As of early 2026, those acquisitions remain pending. Fleet modernization for a sanctioned carrier operating under Taliban governance is not simply a matter of writing a purchase order. Export controls, financing restrictions, and the reluctance of lessors to place assets in jurisdictions without reliable legal frameworks for repossession all create barriers that good intentions cannot overcome.

Compare this to the competitive landscape. Kam Air, Afghanistan's private carrier, operates a mixed fleet of Airbus and Boeing types with a somewhat younger average age and has maintained service to destinations across the region. Neither airline can access Western maintenance facilities or OEM support at full capacity, but the structural disadvantage falls harder on a state-owned carrier whose balance sheet depends on a government with frozen international reserves.

Crisis Communications as a Safety Signal

The most revealing element of the entire episode was not the excursion itself but Ariana's official statement afterward. The airline told media that 'according to international standards of aviation, such incidents are common in the world,' then cited the Air Canada collision at LaGuardia on March 22 as their supporting example.

This is worth unpacking because it reveals a fundamental misunderstanding of safety culture at the organizational level. First, the Air Canada incident at LaGuardia was not a runway excursion. It was a collision between an aircraft and an emergency ground vehicle that killed two pilots and injured dozens. The failure modes, causes, and contributing factors are entirely different. Citing it as a comparable event demonstrates either ignorance of basic accident taxonomy or a deliberate attempt to conflate dissimilar events for rhetorical cover.

Second, using a tragedy that killed two people three days earlier as rhetorical ammunition to minimize your own safety incident is not just tone-deaf. It is a signal that the organization views safety events primarily as public relations problems to be managed rather than operational failures to be investigated and corrected. Airlines with mature safety cultures issue statements that acknowledge the severity of the event, outline the investigation process, and commit to transparency. They do not shop for worse accidents to make their own look acceptable by comparison.

Third, the claim that runway excursions are 'common' is factually misleading. The International Air Transport Association tracks runway excursions as one of the highest-risk categories in commercial aviation precisely because they are not supposed to be routine. IATA's Runway Excursion Risk Reduction toolkit exists because the industry treats every excursion as a serious safety event requiring root cause analysis. The normalization of these events within an airline's official communications is one of the clearest red flags in aviation safety.

What This Means for Travelers

Afghanistan's aviation market is constrained by geography, politics, and economics in ways that leave passengers with limited alternatives. Ariana and Kam Air together handle the bulk of domestic routes connecting Kabul to Herat, Mazar-i-Sharif, Kandahar, and regional international destinations. For travelers who must fly within or through Afghanistan, the options are narrow.

The practical calculus is uncomfortable but straightforward. An airline operating 30-plus-year-old aircraft, banned from EU airspace for two decades, with two runway excursions in eight months and an institutional reflex to minimize safety events is carrying elevated operational risk. No amount of 'everyone walked away' framing changes the underlying trajectory. The margin between a survivable excursion and a catastrophic one is measured in speed, terrain, obstacles, and luck. Luck is not a safety system.

For international travelers connecting through the region, routing choices matter. Carriers operating into Kabul from Dubai, Istanbul, and other hubs bring their own safety standards and fleet types to the equation. Selecting a codeshare or connecting itinerary that places the Afghanistan domestic segment on a carrier with verifiable maintenance oversight and modern fleet types, where available, is a rational risk management decision.

The broader lesson extends beyond Afghanistan. When an airline responds to a safety incident by pointing fingers at someone else's fatal accident, that tells you everything about how they process risk internally. Safety culture is not a document or a policy. It is revealed in what an organization says and does when things go wrong. Ariana's response to the March 25 excursion revealed an organization that has not internalized the foundational principle of modern aviation safety: every incident is an opportunity to prevent the next accident, not an inconvenience to be explained away.