On November 14, a major runway incursion was narrowly avoided involving an Airbus A380 and Boeing 737. It sounds like the incident may have been caused by an ATC error – although an ATSB investigation is still underway.
Despite millions being spent in recent years to improve runway safety at the airport, this incident is a timely reminder that incursions can and will continue to happen in Sydney.
Here’s a look at why, and what you can do about it.
The Layout.
Sydney’s runway layout is complex. There are three runways – two parallel ones (16/34 LR) and another runway that runs perpendicular to them (07/25). The airport itself sits perched on the edge of Botany Bay, with the parallel runways extending well out over water. And all terminals and FBOs are found clustered together on the northern side of the airport, near the 16R threshold.
Which means taxis to/from all the other runways are lengthy and potentially confusing. And during those taxis, almost every aircraft will need to cross a runway. Often twice.
That’s a lot of crossing traffic when you consider that the airport processes up to eighty movements an hour at peak times – it is literally Australia’s busiest.
Mistakes Happen.
Authorities are well aware of the risk of runway incursions at Sydney airport. So much so that they have spent a commendable amount of time and money to improve runway safety.
Possibly the best advancement in recent years has been the installation of stop bar lighting at every single runway holding point, along with improved signage and markings.
And yet mistakes keep happening. The November incident is a great example – here’s what went down.
The November 14 Incident.
- In CAVOK conditions, a Boeing 737-800 was cleared to land on Runway 25. With their clearance they were informed that an Airbus A380 was holding position on Runway 34 waiting to depart.
- When the 737 had cleared the intersection of the two runways, the A380 was cleared for take-off and began to roll.
- After landing the 737 received its taxi clearance from ground which instructed them to cross runway 34L on Golf back to the domestic terminal.
- As the 737 crew approached the active runway, they were surprised to see it was still occupied with the departing A380. They queried the clearance with ATC who immediately told them to hold short.
- The closest the two aircraft came to each other was 300m (just shy of 1000’) thanks in part to the vigilance of the 737 crew. While not a particularly close shave, there was potential for this to have become a major accident. Which is why the ATSB are asking questions they are.
Here’s a simple animation of the incident with a bird’s eye view:
What can we learn from this?
Future incursions, although rare, will happen. But there are steps that all crew can take to help reduce those statistics and stay safe.
A good place to start is this. To cross a runway in Sydney always remember the ‘hat-trick.’ You know all about cricket right? Well if you’re headed to Australia, this phrase can also be used to impress Aussies at the bar over a cold Fosters (disclaimer: no one drinks it there, and whatever you do never call a prawn a shrimp). It means three successes of the same kind. Or in other words: a set of three good things.
So, there are three things that you’ll need:
- A clearance from ATC
- Confirmation that the stop bar is out
- Runway is visually clear out both sides
If any of them are missing (or uncertain), do not enter the runway.
The crew of the 737 above captured a potential accident because at least one of their hat-trick was missing.
Remember the hat-trick every time you cross a runway.
The stop bars themselves are worth a mention too. What’s more obvious than a big row of blazing hot red lights to make you get on the brakes, right? They work really well, but in their simplicity, there can be confusion.
A while back, IFALPA released some pretty good stuff that is still relevant today. You can read it here, but there are a few scenarios to take away:
The stop bar’s out, but we haven’t been cleared…
Stop. An extinguished stop bar on its own is not an indication you are cleared to cross. It may have been turned off in error, or for a preceding aircraft.
We’re cleared, but the stop bar is still lit…
Yep you guessed it, stop. And this happens really often. You’ll need to ask ATC to turn it off. Never, ever cross a lit stop bar.
But didn’t he say we were cleared?
Help from ICAO
Did you know they have a whole manual dedicated to helping controllers and pilots alike avoid runway incursions? You can download it here.
Have some stories of your own to share?
We’d love to hear from you. They don’t need to be from Sydney, but we can all learn from them. You can reach our team completely anonymously at news@ops.group.
More on the topic:
More reading:
- Latest: 2024 Flight Ops Changes: The Big Ones
- Latest: High levels of Pilot Error with NAT RCL: New Briefing and Checklist
- Latest: US FAA Improves Flight Tracking Privacy
- Safe Airspace: Risk Database
- Weekly Ops Bulletin: Subscribe
- Membership plans: Why join OPSGROUP?
Get the famous weekly 
