Pensacola Tracon SOP
Table of Updates
| Date | Revision | Items Revised |
|---|---|---|
| TBD | A | Initial Re-Release. Update Primary Sectors and Frequencies, Splits |
Area Information
| ICAO Code | Airport Name | Airspace | IFR Beacon Codes | VFR Beacon Codes |
|---|---|---|---|---|
| P31 | Pensacola Tracon |
Purpose:
This document prescribes the procedures to be utilized for providing air traffic control services at the Pensacola Tracon. The procedures described herein are supplemental to the Jacksonville ARTCC Facility Operating Guidelines and FAA Order JO 7110.65, as well as any published FAA guidelines or procedures.
Distribution:
This order is distributed to all Jacksonville ARTCC personnel.
Tracon Positions
| Position | Sector Name | Callsign | Symbol | Frequency |
|---|---|---|---|---|
| P-AR | Approach P-AR | PNS_P_APP | 1P | 118.600 (Updated Frequency) |
| E-AR | Approach E-AR | PNS_E_APP | 1E | 119.000 |
Note: * If the controller is ONLY providing Departure Services, the callsign selected should be _DEP. ARL, ARB, and all Tier 1 sectors must be online before these sectors shall only provide services DEP.
Sectorization Flow Chart
Description:
General Information
Handoffs: P31 shall complete any a radar handoff for arriving aircraft to tower. All other internal and external handoffs shall be initiated as soon as the aircraft are clear of conflict.
Departure Release: Unless otherwise coordinated, F11 shall give automatic departure releases to all traffic from PNS. All other airports within P31 shall request a departure release for traffic receiving radar services. Upon receipt of the departure release, the release shall remain valid for five (5) consecutive minutes. Upon issuance of the takeoff clearance, a rolling call notification message shall be sent to the appropriate F11 radar controller. This notification should include the callsign of the aircraft and the departure runway the aircraft is departing from.
Rolling Calls:PNS ATCT will ensure datatag auto acquires and will not send rolling calls to P31 departure controllers unless one of the following criteria is met:
a. The F11 departure controller requests rolling calls.
b. The departure scratchpads are not completed.
c. The departing aircraft is issued a departure heading not outlined in the PNS ATCT Standard Operating Procedures.
Runway Change Procedures: When changing runways, LC must verbally coordinate with the appropriate F11 position(s) for the last departure/arrival off the previously used runway and the first departure/arrival off the newly selected active runway(s). Notify P31 of the new runway configuration and last departure and arrivals. When notified by P31, stop all departures on the present configuration. When P31 is ready for the new configuration, F11 will notify LC. Upon completion of notification, departures may resume with the new configuration. Ensure ATIS has been updated to reflect the new configuration.
Approach Scratchpads: P31 uses a three letter format consisting of XYY where X identifies the type of approach and YY consists of the runway truncated to two characters. For example, Runway 18R would be 8R. Therefore, an ILS approach to Runway 18R would be represented by I8R.