Subject: A quick tip for handling Manila (RPLL) Terminal 3 Ground Flow
Hey everyone, just wanted to throw out a general tip for managing the ground movement around Terminal 3, especially when you’re solo-ing both Tower and Ground and traffic starts picking up.
Recently, we had a bit of a gridlock in the T3 alleyway. Cathay 930 and Malaysian 983 were stuck at the gates for quite a while because taxiing traffic (Japan Air 746 and Cebu 521PR) was sent down Taxiway November, completely blocking the pushback zones. I had to re-quest pushback because ground flow had been temporarily forgotten (assuming Malaysian being told “I’m Sorry”).
When T3 gets busy, routing taxiing aircraft down November almost always guarantees a bottleneck.
Here’s a much smoother alternative that real-life Manila controllers use:
- Use the G12/G13 Links: Instead of letting traffic coast down November, instruct them to use G12 or G13 to get onto Taxiway Delta. Real-life operation uses taxiway near to the runway for Departures letting inner taxiway (relatives to the terminal) for Arrivals
- Save November for Pushbacks: Keeping November clear gives the departures room to push, start engines, and get out of the way without choking the entire alleyway. Which may reduce “forgotten” pushback approval.
- Proactive over Reactive: It’s always easier to issue a progressive taxi instruction onto Delta early than it is to untangle a three-plane gridlock later while you’re also trying to manage the runway.
Managing solo top-down traffic is a massive juggling act, but keeping the T3 alleyway clear by utilizing Delta makes life a whole lot easier for both the controller and the pilots. I am no ATC, yet this is a basic real-world principle that helps keep ground movements smooth and realistic. This feedback may apply to other Airports. Safe flying!
