RPLC - Clark International Airport¶
General¶
The Clark International Airport has 1 commercial Runway and 1 general aviation runway, 2 passenger terminals, 1 military airbase and 1 maintenance hangar
- Terminal 1 - Unused
- Terminal 2 - International and Domestic Flights
The airport caters passenger and cargo flights, as well as general and military aviation.
Charts¶
Frequency List¶
| Designator | Callsign | Frequency | Remarks |
|---|---|---|---|
| RPLC_DEL | Delivery | 125.200 | |
| RPLC_RMP | Clark Ramp | 121.650 | |
| RPLC_GND | Clark Ground | 124.300 | |
| RPLC_TWR | Clark Tower | 118.700 | |
| RPLC_APP | Clark Approach | 119.200 |
Stand Assignments¶
Bay assignments, are strictly implemented virtually, and are based on the latest real-world operations.
All Domestic and International flights will park at Terminal 2. Any cargo flights will park at M or N Ramp. Virtual and other real-world airlines that are not listed will park at terminal 2.
Runways¶
Clark currently only has 1 Runway. Below is a table of the Take-Off Run available
Take-off Run Available.
| Intersection | TORA ft (m) |
|---|---|
| F1 | 8,432 (2570) |
| F2 | 6,480 (1975) |
| F5 | 7,808 (2380) |
Routes¶
Local flights within RPHI and some international flights are to use routes given below. Simbrief also give a standard route which looks like this
If your route is still invalid, a controller will send you a private message with your new route. Routes within RPHI are to follow the half-moon principle in both RVSM and non-RVSM conditions. During events you will have 5 minutes between the time you request clearance and the time you request pushback, or you will have to wait until a new slot is available.
Warning
During events it is important that you put your EOBT in your flight plan as controllers will use that to determine your takeoff slot.
Waypoint Restrictions¶
Waypoint Restrictions¶
| FIR | Waypoint | Airway | Altitude (FL) |
|---|---|---|---|
| HONG KONG | NOMAN / SABNO | A583 / A461 / M501 | 300 / 340 / 380 |
| SINGAPORE | TEGID | M767 | 310 / 320 / 350 / 360 / 390 / 400 |
| LAXOR | L649 | 300 / 380 | |
| M772 | 300 / 380 | ||
| N884 | 320 / 360 / 400 | ||
| HO CHI MINH | PANDI / ARESI | M765 / L628 | 280 / 340 |
| N500 | 300 | ||
| MIGUG | N892 | 310 / 320 / 350 / 360 / 390 / 400 |
Clearance¶
On first contact with the controller that will issue your clearance, it is recommended for you to give the following information:
- Your bay number
- Your aircraft type
- The ATIS information letter
Phraseology
SRQ6355: Clearance Delivery, SRQ6355, stand 205, A-T-R 72, with Information Alpha, request clearance El Nido
Warning
Radio Checks on first contact are discouraged when building communication with the controller. It's best to greet or ask the controller, should you need any help before clearance issuance.
Be straightforward and concise as possible when communicating within a controlled frequency.
Once you have requested for clearance, the controller will either tell you to standby, or give your clearance on the spot. Clearances include your routing, flight level restrictions, departure instructions and your squawk.
You must read back the clearance in full. Listen carefully to all details that the controller gives you, and if you are unsure about your clearance, let the controller know.
Phraseology
GAP2010: Clearance Delivery, GAP2010, Stand 208, Q-400 with information A, request clearance Mactan
RPLC_DEL: GAP2010, cleared Mactan, W16 MIA B462 IPATA W25 BATAY, RUNWAY 02 OLIVA2E, Climb 4000, Squawk 4250
GAP2010: Clearance Delivery, GAP2010, Stand 208, Q-400 with information A, request clearance Mactan
RPLC_DEL: GAP2010, cleared Mactan, W16 MIA B462 IPATA W25 BATAY, RUNWAY 02, fly runway heading, climb 4000ft, expect radar vectors OLIVA, squawk 4250
Pushback¶
Warning
- Do not preplan your pushback!
- Connect the tug first!
Phraseology
GAP2010: Clark Ramp, GAP2010, Stand 208, request push and start
RPLC_RMP: GAP2010, push and start approved, face south
Departure¶
The departure procedure is decided by an online Approach (APP) or En-route Controller (CTR). When both are offline, Standard Instrument Departures (SIDs) are given by the aerodrome controllers (TWR, GND or DEL). When either APP or CTR is online, they decide if departures will be given radar vectors (climb and heading instructions) to the TMA exit points or will be following a SID.
When APP or CTR is online, after passing 2000 feet or 5 DME from RPLL, report your passing altitude to APP or CTR. This is to help them identify you successfully in their radar screens.
Phraseology
GAP2010: Manila Departure, GAP2010, on runway heading, passing 2000 climbing 4000
RPLC_APP: GAP2010, radar identified, continue climb 7000
Arrival¶
When arriving in to Clark, it is best for you to be in between 7,000ft and FL140 when reaching the border of the TMA or the start of the STAR. On initial contact with Clark Approach (RPLC_APP), report your current level.
Phraseology
GAP2024: Clark Approach, GAP2024, FL160, inbound MALIB
APP will then issue your arrival clearance including the type of approach to expect to the active runway. APP either gives you radar vectors to final or gives you descent clearances via a STAR. By default, controllers will vector you to the final approach.
Phraseology
RPLC_APP: GAP2024, radar contact, cleared Clark expect radar vectors ILS 02
GAP2024: Cleared Clark expect radar vectors ILS 02, GAP2024
RPLC_APP: GAP2024, maintain present heading, descend 10,000, QNH 1011
GAP2024: maintain present heading, descend 10,000, QNH 1011, GAP2024
Warning
If APP didn’t give you any turns after you have passed the last waypoint on your routing, maintain your present heading.
Vacating¶
You must vacate the runway as fast as possible in order for TWR to make best use of the runway.
You have not vacated the runway until you have fully passed the runway stop bar, so DO NOT STOP UNTIL YOU ARE FULLY ON A TAXIWAY or you might cause a go around.
The controller may give you a taxi instruction to vacate and some might not. If so, keep moving until you are vacated and hold position until GND has given you further instructions to taxi.
