| On 24 February 2010, a Garuda Boeing 737-800 misunderstood the runway exit instruction issued during their landing roll at Perth and turned onto an intersecting active runway. An expeditious exit from this runway followed and no actual conflict resulted. The phraseology used by air traffic control was open to incorrect interpretation by the flight crew and led to their premature turn off the landing runway despite a prior briefing on exit options.
| Event Details
|| February 2010
| Actual or Potential
| AGC, HF, RI
| Flight Conditions
|| On Ground - Normal Visibility
|| Inappropriate ATC Communication,|
|| Accepted ATC Clearance not followed,|
Incursion after Landing,
| Damage or injury
| Causal Factor Group(s)
|| Aircraft Operation,|
Air Traffic Management
| Safety Recommendation(s)
|| None Made
| Investigation Type
On 24 February 2010, a Boeing 737-800 being operated by Garuda on a scheduled passenger flight from Denpasar, Indonesia to Perth failed to follow the runway exit instruction given by ATC after a daylight landing in normal visibility on runway 03 at destination and instead turned right directly onto intersecting active runway 06. ATC then instructed an expeditious exit of this runway to the right via taxiway S and no actual conflict occurred.
An Investigation was carried out by the ATSB. It was established that no runway exit instructions had been given to the aircraft prior to touchdown and that an instruction to “take taxiway November, second on your right now’ had been issued as the aircraft decelerated on the landing roll prior to taxiway ‘P’.
Perth Aerodrome layout. Source:
It was noted that the flight crew briefing for the approach and landing had identified taxiways P and N as the first and second exits from the landing runway.
The Final Report AO-2010-011 of the Investigation was published on 29 June 2010