Overview
Airspace
The following oceanic FIRs are owned by VATPAC and are covered under the Pacific Oceanic Letter of Agreement
YBBB - Brisbane Oceanic
YMMM - Melbourne Oceanic
NFFF - Nadi Oceanic
AGGG - Honiara FIR
ANAU - Nauru FIR
Other FIRs which are covered under the Pacific Oceanic Agreement are:
NZZO - Auckland Oceanic
NZCM - McMurdo Oceanic
KZAK - Oakland Oceanic
NTTT - Tahiti Oceanic
RJTG - Fukuoka Oceanic
Information
Auckland, McMurdo and Tahiti Oceanic are owned and operated by VATNZ, Fukuoka Oceanic is owned and operated by VATJPN, and Oakland Oceanic is owned and operated by the Oakland ARTCC.
Under the agreement, a controller holding an oceanic endorsement may control positions within any of these FIRs.
Control Positions
Sector | Callsign | Frequency | Logon Identifier |
---|---|---|---|
KZAK - Oakland Oceanic | San Francisco Radio | 11.282 (129.400) | ZAK_FSS |
YBBB - Brisbane Oceanic (Tasman) | Brisbane Radio | 17.904 (124.650) | BN-TSN_FSS |
YMMM - Melbourne Oceanic (Indian) | Brisbane Radio | 5.634 (129.250) | ML-IND_FSS |
NZZO - Auckland Oceanic | Auckland Radio | 8.867 (129.000) | NZZO_FSS |
NZCM - McMurdo Oceanic | McMurdo Radio | 9.032 (128.700) | NZCM_FSS |
NFFF - Nadi Oceanic | Nadi Radio | 8.846 (123.600) | NFFF_FSS |
NTTT - Tahiti Oceanic | Tahiti Radio | 9.116 (125.500) | NTTT_FSS |
RJTG - Fukuoka Oceanic | Toyko | 2.932 (126.700) | RJTG_FSS |
Indian (IND) and Tasman (TSN) have their own detailed Local Instructions. Refer to the links for more information.
Note
KZAK oceanic positions may be further subdivided by the shift supervisor, in which case the subsector shall add a numeral to the callsign. For example, ZAK_1_FSS. It is discouraged to only control a portion of KZAK in non-event periods. For more information on KZAK procedures, head to their SOPs here.
Recency Requirements
- A Participating Organisation must require a permitted controller to log 1 hour on a permitted oceanic position, within the previous 3 months, for them to be considered active, and
- A permitted controller who does not meet the hour requirement specified above, will be considered inactive; and
- An inactive permitted controller may become active again, by performing a buddy session with a permitted controller who is approved to do so by that PO; and
- Any additional currency or activity requirements imposed by a PO on local or visiting controllers do not apply to permitted controllers.