1. Training
2. Clearance Delivery/Ground
3. Pre-Departure Clearances

Pre-Departure Clearances

I. Preface

Note: This document is and may not be used for real-world ATC training. It is intended for use by controllers in the VATSIM network.

Purpose: This Standard Operating Procedure (SOP) outlines the procedures to be used by all ZSE controllers to understand the use and how to use Pre-Departure Clearances.

This page provides some examples of commands located in our alias file. Before you use them, remember the following:

1. Most importantly, you must check the flight plan first for errors and assign the squawk code before sending the PDC.
2. In an alias command, the $ followed by a number, ie. $1, $2, is an item that must be included after the alias command or it will be blank.
3. The examples listed below should be edited to suit each airport/departure.
4. You don't need to open a pm to send a PDC with the commands listed below. All you need to do is select the aircraft, type in the PDC command followed by any manual entries and it will send the pilot a PDC.

Our alias file has PDC commands for most major airports. The format is:

.pdc<name of sid without number> <departure controller ID>

If you don't include the departure controller's ID it will use your frequency as the departure frequency. Add a u to the end of the command name if there is no departure controller online. Some departures are unique, such as the SUMMA where you must add s or n to the command to specify whether the flow is south or north. The aliases should let you know if you forget that kind of detail.

Example: .pdcwhamy
Pilot will get a PDC for the WHAMY departure, and your frequency for departure

Example: .pdcsummas 1w
Pilot will get a PDC for the SUMMA departure, south flow, and the combined SEA_APP frequency 125.6

Example: .pdcbangr 1w .pdcexpect 16L
Pilot will get a PDC for the BANGR departure, the combined SEA_APP frequency of 125.6, and a short blurb that they should expect runway 16L for departure.

Additional examples of PDC commands for KPDX can be found Here, and KSEA Here.

II. Background

Pre Departure Clearances are text type clearances passed to an aircraft either via text or chat used to mitigate controller workload.  The use of them is not restricted in any way as of this writing, and are completely optional. S1 controllers may not use PDC's as part of their training and must solely use standard clearances (although, we will teach about PDC's in S1 training and their uses and functionality).  The PDC format may be altered as needed but must contain the following minimum information.  

The following information is required:

• CALLSIGN: AS APPROPRIATE
• A/C: AS APPROPRIATE
• BEACON: AS ASSIGNED
• ORIGIN: AS APPROPRIATE
• DESTINATION: AS APPROPRIATE
• ROUTE: AS APPROVED
• APPROVED ALTITUDE: AS APPROVED, CORRECT FOR DIRECTION OF FLIGHT
• DEPARTURE FREQ: IF NO RADAR ONLINE, 122.800
• ALTITUDE RESTRICTIONS: APPROPRIATE FOR (DP) DEPARTURE PROCEDURE AND/OR FACILITY.  

III. Application

Here is an example of a PDC the HAROB6 departure at KSEA - .pdcharob 1w .pdcexpect 16L

*** THIS CLEARANCE *MAY* CONTAIN INFORMATION CHANGED AFTER THE FLIGHT PLAN WAS FILED. PLEASE READ THE ENTIRE CLEARANCE CAREFULLY. *** PRE-DEPARTURE CLEARANCE START | CALLSIGN: DAL123 | TYPE: B739 | DEP: KSEA | ARR: KSFO | TRANSPONDER: 1601 | CRZ ALT: 37000 | APPROVED ROUTE: HAROB6 ERAVE Q1 ETCHY MLBEC BDEGA3 | *CLIMB VIA SID EXCEPT MAINTAIN 7k* | DEP 125.600 | ADDITIONAL INFO: >>PUSHBACK AT PILOT'S DISCRETION. CONTACT APPROPRIATE CONTROLLER WITH CURRENT ATIS FOR TAXI.<< THIS MESSAGE SERVES AS YOUR PRE-DEPARTURE CLEARANCE. NO NEED TO REPLY UNLESS YOU HAVE QUESTIONS -END- *** EXPECT RUNWAY 16L FOR DEPARTURE ***

Next, let's take a look at a PDC that does not utilize "Climb via SID" phraseology - .pdccascd 3a .pdcexpect 10L@E

*** THIS CLEARANCE *MAY* CONTAIN INFORMATION CHANGED AFTER THE FLIGHT PLAN WAS FILED. PLEASE READ THE ENTIRE CLEARANCE CAREFULLY. *** PRE-DEPARTURE CLEARANCE START | CALLSIGN: DAL123 | TYPE: B739 | DEP: KPDX | ARR: KLAX | TRANSPONDER: 1602 | CRZ ALT: 31000 | APPROVED ROUTE: CASCD2 CHISM JUDAH JUNEJ Q7 JAGWA BURGL IRNMN2 | *MAINTAIN 7k* | DEP 124.350 | ADDITIONAL INFO: >>CONTACT APPROPRIATE CONTROLLER WITH CURRENT ATIS FOR TAXI. PUSH ONTO TWY K OR T REQ ATC CLNC.<< THIS MESSAGE SERVES AS YOUR PRE-DEPARTURE CLEARANCE. NO NEED TO REPLY UNLESS YOU HAVE QUESTIONS -END- *** EXPECT RUNWAY 10L@E FOR DEPARTURE ***

Next, let's take a look at a PDC that does not have a departure controller online- .pdccascdu

*** THIS CLEARANCE *MAY* CONTAIN INFORMATION CHANGED AFTER THE FLIGHT PLAN WAS FILED. PLEASE READ THE ENTIRE CLEARANCE CAREFULLY. *** PRE-DEPARTURE CLEARANCE START | CALLSIGN: DAL123 | TYPE: B739 | DEP: KPDX | ARR: KLAX | TRANSPONDER: 1602 | CRZ ALT: 31000 | APPROVED ROUTE: CASCD2 CHISM JUDAH JUNEJ Q7 JAGWA BURGL IRNMN2 | *MAINTAIN 7k* | DEP OFFLINE | ADDITIONAL INFO: >>CONTACT APPROPRIATE CONTROLLER WITH CURRENT ATIS FOR TAXI. PUSH ONTO TWY K OR T REQ ATC CLNC.<< THIS MESSAGE SERVES AS YOUR PRE-DEPARTURE CLEARANCE. NO NEED TO REPLY UNLESS YOU HAVE QUESTIONS -END-

As you can see, all information as outlined above has been used, and some have also been added, including a runway to expect. Controllers can feel free to take discretion with PDC's, but the format and minimum information as outlined above must be utilized per ZSE Training Administration.