Potomac TRACON - Radar Positions
Positions
| Area | Sector | Busy Callsign |
Frequency |
ID |
Tag |
Voice Room |
| Richmond | North | RIC_N_APP |
126.800 |
1U |
U |
PCT_1U |
| * | RIC_E_APP |
126.400 |
1I |
I |
PCT_1I |
|
| * | RIC_W_APP |
134.72 |
1W |
W |
PCT_1W |
|
| Charlottesville | CHO_APP |
132.850 |
1Y |
Y |
PCT_1Y |
|
| Baltimore | East Departure | BWI_R_DEP |
124.550 |
3R |
R |
PCT_3R |
| West Departure | BWI_Y_DEP |
128.700 |
3Y |
Y |
PCT_3Y |
|
| East Arrival | BWI_Q_APP |
119.700 |
3Q |
Q |
PCT_3Q |
|
| West Arrival | BWI_W_APP |
125.52 |
3W |
W |
PCT_3W |
|
| Washington | East Departure | DCA_N_DEP |
125.650 |
4N |
N |
PCT_4N |
| * | DCA_O_DEP |
126.550 |
4O |
O |
PCT_4O |
|
| West Departure | DCA_H_DEP |
118.950 |
4H |
H |
PCT_4H |
|
| * | DCA_M_DEP |
121.050 |
4M |
M |
PCT_4M |
|
| High Departure | DCA_Z_DEP |
118.67 |
4Z |
Z |
PCT_4Z |
|
| East Arrival | DCA_K_APP |
124.200 |
4K |
K |
PCT_4K |
|
| West Arrival | DCA_J_APP |
119.850 |
4J |
J |
PCT_4J |
|
| Andrews Arrival | ADW_APP |
124.000 |
4A |
A |
PCT_4A |
|
| Dulles | North Departure | IAD_D_DEP |
125.050 |
5D |
D |
PCT_5D |
| South Departure | IAD_S_DEP |
126.550 |
5S |
S |
PCT_5S |
|
| High North Departure | IAD_A_DEP |
123.82 |
5A |
A |
PCT_5A |
|
| North Arrival | IAD_B_APP |
126.100 |
5B |
B |
PCT_5B |
|
| West Arrival | IAD_E_APP |
120.450 |
5E |
E |
PCT_5E |
|
| South Arrival | IAD_L_APP |
124.650 |
5L |
L |
PCT_5L |
* Sector not yet defined
Primary positions are bold
Radio Names
- The radio name for all _APP sectors is "Potomac Approach"
- The radio name for all _DEP sectors is "Potomac Departure"
Voice in the Callsign
- When using the primary position add a _V_ to the callsign in place of the _x_ (where x is the ARTS tag for the busy callsign)
- When using the "Busy Callsign" for any position, do not add a "_V_" to your callsign, even if using voice.
Standard Operating Procedures
Until current sector data is acquired, the primary position will cover the entire area.
- Richmond Sector
- North Radar
- East Radar *
- West Radar *
- Charlottesville Radar
- Baltimore Sector
- Washington Sector
- Dulles Sector * Sector not yet defined
Airspace
Airspace diagrams for all the sectors.
Use of ASRC Features
Temporary Altitudes
Use the temporary altitude feature for all arriving and departing aircraft within the TRACON by entering the assigned altitude into this field
Scratchpad
Use the scratchpad for assigned headings for arriving and departing aircraft that are on a vector and not direct to a fix. If the aircraft is direct to a fix then there is no need to use this field..
- use "hxx" for aircraft on a vector that are not direct to a fix because the SOP specifies a heading
- use "dxx" for aircraft that should be direct to a fix per SOP, but are not for some reason (traffic, pilot error, etc.)
Note: xx is the assigned heading minus the last zero (0)
Clearing the Temporary Fields
- Clear all fields prior to transfer of communication to the tower
- Clear all fields prior to transfer of communication to another facility (CTR or another TRACON)
Handoffs
Handoffs requests within the TRACON must be made at least 10 miles and 4000ft prior to aircraft entering another controllers sector. These requests may be made 20 miles and 8000ft in advance. The transfer of communication should be made at 5 miles and/or 1000ft from the sector boundary.
Live information will go here