Disoriented Pilots Crash Airplane in Nepal

Advertisement
Accident timeline for Disoriented pilots crash airplane in Nepal. #realatc
Accident-specific timeline reconstructed from the documented sequence; diagram not to scale.
Timeline
Event 1 —
Dhaka departure
1.
Event 2 —
Kathmandu approach
2.
Event 3 —
Runway/approach confusion
3.
Event 4 —
Loss of situational awareness
4.
Event 5 —
Terrain impact / runway excursion
5.
Event 6 —
Post-crash fire
6.

The event in context

On 12 March 2018, US-Bangla Airlines Flight 211, a Bombardier Q400 turboprop carrying 71 people from Dhaka to Kathmandu, crashed on approach to Tribhuvan International Airport. Fifty-one people died; twenty survived, several with severe injuries.

Captain Abid Sultan had been cleared to land on runway 02, but as the aircraft neared the airport, he abruptly changed his mind and asked to land from the opposite direction instead, on runway 20. Other pilots in the area, listening on the radio, could hear something was wrong — one radioed in that the US-Bangla aircraft sounded disoriented. Investigators later found Sultan had been under serious personal and professional stress in the weeks before the flight, and had been smoking in the cockpit throughout. As he fixated on switching runways, his awareness of the aircraft's actual position, altitude, and configuration broke down.

The Q400 came in unstable, banking hard, well off the centerline. It struck the ground short of the runway, skidded through the airport's perimeter fence, and came to rest in a field, engulfed in fire. Rescue crews reached the wreckage within minutes, but for many aboard it was already too late.

The final Nepal investigation into US-Bangla Flight 211 provides far more detail than the original article. The Q400 was approaching Tribhuvan International Airport on March 12, 2018 when the crew became increasingly disorganized during the approach. The aircraft ultimately crashed near the runway, and the post-impact fire greatly affected survivability.

Reconstructing this flight

Nepal's official investigation placed the cause primarily on the captain's loss of situational awareness and psychological state, though it also found procedural lapses by the control tower — and Bangladeshi investigators pushed back, arguing Kathmandu's air traffic control should have intervened more forcefully once other pilots flagged that something was wrong. Both countries' investigators agreed on one thing: this was a survivable landing that went wrong in the final minutes, not a mechanical failure.

Final report released by Nepal's Aircraft Accident Investigation Commission, 27 Jan 2019. Probable cause centered on the captain's loss of situational awareness and psychological distress during an unstabilized approach; Bangladeshi investigators separately faulted Kathmandu ATC for inadequate intervention.

The investigation relied heavily on CVR, FDR, EGPWS and other recorded data. The report also examined crew behavior, cockpit workload and the interaction between the crew and ATC. The final report concluded that the accident was driven by loss of situational awareness and flight crew performance during the approach, with organizational and operational factors also considered.

What the evidence establishes

The survival section is important: the report states that the impact forces were survivable for many occupants, but the rapidly spreading post-crash fire prevented escape for others. That distinction matters because it separates the crash dynamics from the survivability problem and shows why emergency response time and aircraft evacuation pathways can determine the final number of fatalities.

The Kathmandu Approach and Loss of Situational Awareness

The reconstructed sequence can be read as a chain of six decision points: Dhaka departure → Kathmandu approach → Runway/approach confusion → Loss of situational awareness → Terrain impact / runway excursion → Post-crash fire. Each step changed the aircraft’s available options. The important analytical point is not to isolate the final impact from the preceding events; the final outcome was produced by the accumulation of the earlier changes in aircraft state, position, workload and available escape options.

The ATC/radar perspective is most useful when it is synchronized with the aircraft evidence. In this case the critical transition is the move from dhaka departure to post-crash fire. Once the aircraft reached the later stages of the sequence, the crew had fewer safe alternatives than they had at the beginning. That is the operational value of reconstructing the event rather than describing it only from the final crash scene.

Additional evidence and analysis

The official Nepal report also gives the accident a stronger operational context than the earlier draft. The Q400 was approaching Kathmandu, an airport where terrain, approach procedures and runway-direction changes can create a high workload. The investigation examined not only the crew’s actions but also the ATC environment and the way the approach was managed as the aircraft moved toward the runway.

The final report also matters because it gives the reconstruction a way to distinguish radio drama from evidence. The CVR and FDR provided the investigators with objective information about what the crew said and what the aircraft actually did. When those two sources diverged, the investigators could reconstruct the loss of situational awareness more reliably than a radio-only account could.

The Approach-Confusion Chain

The decisive safety issue in this incident was specific to the sequence: Kathmandu approach; Runway/approach confusion; Loss of situational awareness. Treating those events as isolated anomalies would miss the way they interacted.

Sources and investigation material

Accident Facts

Incident date
12 Mar 2018
Registration
S2-AGU
Aircraft
Bombardier Q400 (DHC-8-402)
Airports
DAC (Dhaka) to KTM (Kathmandu Tribhuvan)
Fatalities
51 of 71 aboard (20 survivors)
Investigation status
Final report released by Nepal's Aircraft Accident Investigation Commission, 27 Jan 2019
Category
Crash, Fatal
Reconstruction
4:34
Audio from the original air traffic control recording, sourced from public recordings and released investigation records. The reconstruction, animation and written account are our own.
Advertisement

The weekly incident