Standard Operating Procedures
Jacksonville TRACON
General
Jacksonville international positions (JAX APP, TWR, GND, and DEL) will adhere
to the following general guidelines when operating the field on the VATSIM network:
- The calm wind runway designation at KJAX is runway 7. It shall be used if
the winds at KJAX are 4kts or less, otherwise the tower controller shall
choose a runway most closely aligned with the winds. Runway 7 approach is
CAT II which also designates it as the foul weather preferred runway if
wind direction and strength permit.
- JAX_TWR and JAX_APP shall coordinate all operations per the standard facility
coordination procedures.
- KJAX is a Class C Airspace area. As such, all aircraft leaving the
immediate area of the field will be assigned a discreet squawk code per
current code assignments.
- Military operations are allowed in the JAX_APP airspace. Controllers will
adhere to current FAA regulations regarding proper phraseology and direction
of military jets and aircraft within their assigned airspace. Questions
on those specific procedures can be addressed to the ATM, TA, or
instructors by email.
- All arrivals to KJAX or other fields within the airspace of JAX_APP shall
be descended to 2000' MSL for final approach course or ILS intercept.
Airspace Delegation
The above diagram outlines the boundaries for JAX_APP. Airspace for JAX TRACON
positions is segmented into three areas for airspace allocation:
- The northern area (surrounding KJAX, KCRG, KVQQ and KSGJ) is allocated from the surface to
(but not including) 15,000 MSL.
- The central area (between the two dashed lines, surrounding KGNV and the
POGIE intersection) is allocated from the surface to (but not including)
13,000 MSL.
- The southern area (surrounding KOCF) is allocated from the surface to
(but not including) 10,000 MSL.
All TRACON positions must review and adhere to the CTR / TRACON Hand-off
Procedures located in the general guidelines section of the website.
Arrivals to Daytona Beach International will transit airspace. Those aircraft
will be received directly from Center over KJAX at 15000. They should be
routed direct SGJ and descended to 11000 and handed off to DAB_APP prior to the
published TRACON boundary.
Split Operations
The JAX TRACON may be split in order to be staffed by two approach controllers.
The boundaries to be used for split operations shall depend on the currently
active runway(s). There are two such "flows" available to KJAX and JAX_APP:
- E/SE Split: The
E/SE split shall be used if the active runway(s) for arrivals and departures
is currently runway 7 or runway 13.
- W/NW Split: The
W/NW split shall be used if the active runway(s) for arrivals and departures
is currently runway 25 or runway 31.
Hand-offs to the neighboring JAX TRACON controller in any situation will be
initiated within 2nm of the boundary.
Each controller is responsible for all outlying fields within their allocated airspace.
The JAX TRACON controller allocated the airspace on the departure end of KJAX
will serve as the departure controller for their allocated airspace.
Additional coordination is left to the controllers discretion but may not
supercede those procedures above.
E/SE Split Operations
The following diagram illustrates the airspace allocations for JAX_W_APP and
JAX_E_APP when the E/SE Flow is in use:
JAX_W_APP is allocated the airspace as shown above, and is responsible for
aircraft from the surface to (but not including) 15,000 MSL.
- This controller will operate all VFR and IFR approaches to runway 7
and 13.
- This controller will receive all arrivals from the TAY2 and AMG2 arrivals
from Jacksonville Center.
- This controller will receive all arrivals from the SSI3 and POGIE1
arrivals from E_APP.
JAX_E_APP is allocated the airspace as shown above, and is responsible for
aircraft from the surface to (but not including) 15,000 MSL in the northern
area, from the surface to (but not including) 13,000 MSL in the central area,
and from the surface to (but not including) 10,000 MSL in the southern area.
In this flow configuration, JAX_E_APP is responsible for all operations within
the GNV/OCF area.
- This controller will receive all aircraft on the POGIE1 and SSI3 arrivals from Jacksonville Center.
- This controller will operate all departures from runways 7 and
13.
- This controller will operate the missed approach procedures for runway 7 and
13.
W/NW Split Operations
The following diagram illustrates the airspace allocations for JAX_W_APP and
JAX_E_APP when the W/NW Flow is in use:
JAX_W_APP is allocated the airspace as shown above, and is responsible for
aircraft from the surface to (but not including) 15,000 MSL in the northern
area, from the surface to (but not including) 13,000 MSL in the central area,
and from the surface to (but not including) 10,000 MSL in the southern area.
In this flow configuration, JAX_W_APP is responsible for all operations within
the GNV/OCF area.
- This controller will receive all aircraft on the AMG2 and TAY2 arrivals from Jacksonville Center.
- This controller will operate all departures from runways 25 and 31.
- This controller will operate the missed approach procedures for runway 25 and 31.
JAX_E_APP is allocated the airspace as shown above, and is responsible for
aircraft from the surface to (but not including) 15,000 MSL, and from the
surface to (but not including) 13,000 MSL in the northeast corner of the central
area surrounding the POGIE intersection.
- This controller will operate all VFR and IFR approaches into runways 25 and 31.
- This controller will receive all aircraft on the POGIE1 and SSI3 arrivals from Jacksonville Center.
- This controller will receive all aicraft on the AMG2 and TAY2 arrivals
from W_APP.
