ART-2025 • Module 7 • Case Study: Delhi Runway Incursion
GoAir A320 VT-GOK vs IAF AN-32 VU-DBL • VIDP • 02 Oct 2013

Runway Incursion — VT-GOK / VU-DBL High-risk event, no injury

  Basic Facts Runway Incursion
  • Date / Time (UTC): 02 Oct 2013, ~09:06:32 UTC.
  • Location: IGI Airport, Delhi (VIDP).
  • Civil Aircraft: GoAir A320 VT-GOK, callsign GOW336, Delhi → Mumbai, ~136 pax on board.
  • Military Aircraft: IAF AN-32 VU-DBL, Chandigarh → Delhi, taxiing inbound to technical area.
  • Phase: VT-GOK was on takeoff roll RWY 09. VU-DBL was crossing RWY 09 at same time.
  • Outcome: Tower ordered “STOP”; GoAir aborted takeoff at ~100 kt. Collision avoided. No damage, no injuries.
  • Weather / Serviceability: No significant weather issue. No aircraft technical failure. Radios later checked serviceable.

This is a real runway incursion with an airliner at high speed and another aircraft physically crossing the same runway. We escaped with zero damage only because ATC caught it in time and the A320 stopped.

Why we are teaching this in ART-2025
  • It shows how fast “normal + busy” can become “catastrophic in 5 seconds.”
  • It is not about fancy automation. It is about frequency discipline, runway ownership, and situational awareness.
  • It exposes weak points in coordination between Ground / Tower / Military traffic during high workload.
  • It maps directly to how we run high-density, mixed-use airfields today.

Airport Context & Stressors System already under stress

  Local Situation at Delhi High Workload
  • VVIP movement (“VIP 1”): Runway 28 / apron 1 departures were restricted earlier. Departures built up and got delayed.
  • After the VIP departed at 08:51 UTC, ATC tried to clear the jam fast by starting simultaneous use of multiple runways (“3-runway operation”).
  • Runway 09 had mostly been used like a taxi / crossing surface under Surface Movement Control (SMC North). Suddenly it was switched live as a departure runway, under Tower (North).
  • This means control authority changed mid-traffic: RWY 09 moved from Ground/SMC to Tower.
  • Frequencies were already busy, reports mention arguments / non-ideal R/T on frequency and high density of traffic.
  • Strip runner / support staff was not available, so SMC(N) had to physically move to collect and update strips. That splits attention.

Translation: this was not a calm sterile environment. The unit was in catch-up mode, with a runway changing role in real time.

  Stress Build-up Chain
VVIP restriction → departures stack up → pressure to “clear backlog quickly”
“3-runway operation” started → procedures deviate from routine
RWY 09 switched from “SMC crossover surface” to “live departure runway”
Frequencies noisy + staffing stretched + controller multitasking
Perfect setup for a single clearance to become a runway incursion

Timeline Playback 09:02 → 09:07 UTC

  Minute-by-minute ATC / Crew Actions
  1. 09:02:17 IAF AN-32 VU-DBL lands RWY 10 Delhi, vacates via Taxiway F. Comes to SMC(N) on Ground 121.75. Cleared via Taxiway E, hold short E2.
  2. 09:03:28 GoAir GOW336 (VT-GOK) released by SMC(N) to Tower(N) for RWY 09 departure. RWY 09 is now being used for departures to clear backlog.
  3. 09:05:21 VU-DBL reports near E2 and asks for further taxi.
  4. 09:05:32 SMC(N) clears VU-DBL: taxi via E, cross RWY 09, proceed toward A2 / technical area. → This is the critical clearance. → SMC(N) momentarily treats RWY 09 like it’s still under his control, not as an active departure runway.
  5. 09:06:18 ~46 seconds later, SMC(N) realizes: RWY 09 is active, GoAir is rolling. Calls VU-DBL “HOLD POSITION!” on 121.75. No reply.
  6. 09:06:21 SMC(N) again: “HOLD POSITION, HOLD POSITION!” Still no response from VU-DBL.
  7. 09:06:20–09:06:30 SMC(N) physically shouts / alerts Tower(N): “Stop the departure!” Tower(N) transmits stop instruction. GoAir aborts takeoff at ~100 kt.
  8. 09:06:39 / 09:07:22 VU-DBL later transmits they are at A2 “in contact with Base Ops.” They basically believed they taxied correctly and were now clear.

We were seconds from a 100-knot impact between an A320 and an AN-32 on the active runway.

  Error Chain Snapshot
SMC(N) clears AN-32 to cross RWY 09 (thinking in “old mode”: RWY 09 is still his surface)
RWY 09 already active for departures under Tower (new mode)
AN-32 continues to cross → not listening back to SMC(N)
GoAir rolling for takeoff on same RWY
SMC(N) realises, alerts Tower → Tower stops GoAir → abort at ~100 kt

Human Factors Not equipment — humans

  ATC (SMC North) COMPLETE
Situational awareness break:
SMC(N) forgot, momentarily, that RWY 09 had just been transferred to Tower and was now live for departures.
High workload / distraction:
He was handling heavy post-VVIP congestion, simultaneous runway ops, and another traffic conflict (SEJ869 vs SEJ2384). No “traffic hand / strip runner,” so he was physically juggling strips as well.
Frequency noise:
Frequency was already busy and tense. That degrades clarity and mental bandwidth.
Rapid configuration change:
RWY 09 changed role mid-traffic. This creates an easy trap: the mental model lags behind reality.
  IAF AN-32 Crew (VU-DBL) COMPLETE
Followed a valid taxi clearance:
They were told “cross RWY 09,” so they proceeded.
But… radio monitoring dropped:
When SMC(N) tried twice to say “HOLD POSITION,” there was no response. They were not on Ground frequency anymore, and they were not listening to Tower either (118.75).
Awareness gap:
They did not know RWY 09 had just become active for departures. ATIS still mentioned 10/11 use, not that 09 was live.
Confirmation bias:
“We are cleared to cross, so runway must be safe.” That mindset reduces active threat scanning.
  GoAir Crew (VT-GOK) COMPLETE
Immediate compliance:
Tower said “stop,” they rejected takeoff at ~100 kt. This fast response was the last safety barrier.
Energy state:
High-speed A320 on the roll. Braking that late is not trivial. This was very close.
  System-Level Human Factors
Mixed civil + military ops
Pressure to “clear backlog now” after VIP restriction
Runway 09 ownership change (SMC → Tower) mid-traffic
Missing ATIS update, so pilots not aware 09 is active departure runway
Ground controller multitasking admin + R/T at same time
Result: Single clearance nearly creates an accident

Investigation Findings Probable Cause

  What the report said Official view
  • Delhi ATC activated “three-runway operation” to decongest after a VIP restriction.
  • RWY 09, normally used for taxi/crossing under SMC(N), was made active for departures and transferred to Tower(N).
  • SMC(N), still under heavy load and resolving other conflicts, cleared the IAF AN-32 to cross RWY 09 after that handover.
  • IAF AN-32 accepted and started crossing, but was no longer effectively monitoring SMC(N) frequency, and was not listening to Tower either.
  • SMC(N) realized the error and warned Tower(N), who immediately cancelled VT-GOK’s takeoff. VT-GOK rejected at ~100 kt.

Probable cause (plain language):

1. Ground (SMC North) cleared the AN-32 across RWY 09 even though RWY 09 had just been activated for departures by Tower.
2. The AN-32 continued to cross while not monitoring the correct frequency and without awareness that RWY 09 was now “live.”
3. Procedures, staffing, ATIS update, and frequency discipline under high traffic density were not robust enough to prevent this slip.

Key point

Nobody “broke an engine.” The system broke coordination. The only thing between “serious accident” and “training case study” was one correct rejected takeoff.

Lessons for Our ATC Ops What we must internalize

  Actionable Points COMPLETE
Runway status change must be explicit:
When a runway switches controller (SMC → Tower) or role (“just taxi” → “active departure”), that must be stated clearly on position and to all concerned. Silent assumptions kill.
Positive control of crossings:
“Hold short RWY XX.” “Cross RWY XX now.” “RWY vacated.” All with readback. Aircraft crossing an active runway must remain on (and listening to) the frequency that can still stop them.
Do not overload one controller with admin + ops:
If the controller is simultaneously doing strip-running, solving traffic conflicts, and managing crossings, we are designing in failure. Provide support or slow the rate – safety beats “on-time push.”
Frequency discipline is part of separation:
Arguments, side chatter, and unclear R/T on a busy frequency erode safety margin. We must protect clarity, especially during abnormal ops (VIP movement, weather diversions, simultaneous runway config, etc.).
Empower “STOP TAKEOFF NOW” culture:
Tower must feel free to cancel a takeoff even at high speed, and flight crew must act instantly. That authority saved 136+ lives here.
One-line takeaway

This was not ‘bad luck.’ This was predictable under stress.
Our job is to break that chain earlier — before we are shouting “STOP!” at 100 knots.