Clearance delivery is the position that issues route clearances to aircraft before they commence taxiing.

These contain details of the route that the aircraft is expected to fly after departure. This position will, if necessary, coordinate with the en-route center and national command center or flow control to obtain releases for aircraft. Often however such releases are given automatically or are controlled by local agreements allowing "free-flow" departures. When weather or extremely high demand for a certain airport or airspace becomes a factor, there may be ground "stops" (or "slot delays") or re-routes may be necessary to ensure the system does not get overloaded. The primary responsibility of the clearance delivery position is to ensure that the aircraft have the proper route and slot time. This information is also coordinated with the en-route center and the ground controller in order to ensure the aircraft reaches the runway in time to meet the slot time provided by the command center. At some airports the clearance delivery controller also plans aircraft pushbacks and engine starts and is known as Ground Movement Planner (GMP): this position is particularly important at heavily congested airports to prevent taxiway and apron gridlock.

Importancies
There are a few important things you need to know when you start controlling on delivery. - East and west flightlevels: In the USA aircraft flying westbound are assigned even flight levels, aircraft flying east odd flightlevels. - Squawk range: From 4101 4201 1200 2000 4501 1201 to 4177 4277

East West VFR IFR uncontrolled Overflying/inbound VFR controlled

4577 1277

- Flightplan: Is the aircraft flying in RVSM airspace (above FL290 up to and including FL410), but does the flightplan states NORVSM? Advise the pilot to tick the W in 10. equipment in their flightplan. Is their first fix in the sended flightplan 1000 nm away? Advise/give him a new routing. These are just a few examples of mistakes often happen in flightplans. Please advise the pilot what he is doing wrong, and why. - Information: Check they have your current information.

Radar Facilities
The phraseology for delivery is quite straight-forward. We use an abbreviation to create clearances. This makes all the clearances equal and easy to understand. C-R-A-F-T: C R A F T Clearance Route Altitude Frequency Transponder 'as filed' 'via SID' initial and final flightlevel departure frequency Squawk code

Cleared to destination ... as filed, via (SID), initial ... , expect ... one-zero minutes after departure, departure frequency xxx.xx, sq. xxxx

Standard Instrument Departure

Name HEDLY ONE WINCO ONE MNATE ONE EONNS ONE PADUS ONE SKIPS ONE VALLY ONE Direction Download N N/W N/W S S/W S S/E E N/E E S/E N/E

Initial Altitudes
Airport KMIA KFLL KPBI KTPA KRSW KSRQ Altitude (ft) 5,000 3,000 4,000 6,000 4,000 3,000

I.

II.

III. IV.

V.

The controller will provide the following ATC services: a. Ground Control services at the airport represented by the ICAO Code which was used to login. b. Clearance Delivery services at the airport represented by the ICAO Code which was used to login when a Delivery controller is not online. The controller staffing Ground shall provide, when required in the absence of a Delivery controller at the airport represented by the ICAO Code which was used to login, Clearance Delivery to pilots who are not yet airborne. Ground shall provide Ground services at the airport at which he is logged in. Ground shall provide Ground services in accordance with FAA 7110.65 this means: A. Ground will transfer communications as follows: b. To the Tower Controller (when available) before an aircraft crosses any active runway. c. If there is no other ATC online, to UNICOM (122.800) before the aircraft is holding short of the assigned takeoff runway. Traffic informations of the vincinity are recommened. d. In the absence of Tower, to the controller handling takeoff clearance before the aircraft is holding short of the assigned takeoff runway. Runway 8L/26R at Miami International Airport is not included in the default scenery of Microsoft Flight Simulator , Runway 8L/26R shall be considered closed unless a pilot indicates it is present in his scenery and offers its use. The controller will provide the following ATC services:

I.

Ground Control services at the airport represented by the ICAO Code which was used to login. b. Clearance Delivery services at the airport represented by the ICAO Code which was used to login when a Delivery controller is not online. II. The controller staffing Ground shall provide, when required in the absence of a Delivery controller at the airport represented by the ICAO Code which was used to login, Clearance Delivery to pilots who are not yet airborne. III. Ground shall provide Ground services at the airport at which he is logged in. IV. Ground shall provide Ground services in accordance with FAA 7110.65 this means: A. Ground will transfer communications as follows: b. To the Tower Controller (when available) before an aircraft crosses any active runway. c. If there is no other ATC online, to UNICOM (122.800) before the aircraft is holding short of the assigned takeoff runway. Traffic informations of the vincinity are recommened. d. In the absence of Tower, to the controller handling takeoff clearance before the aircraft is holding short of the assigned takeoff runway. V. Runway 8L/26R at Miami International Airport is not included in the default scenery of Microsoft Flight Simulator , Runway 8L/26R shall be considered closed unless a pilot indicates it is present in his scenery and offers its use. VI. The controller will provide the following ATC services: . Tower services at the airport represented by the ICAO Code which was used to login. a. Ground Control services at the airport represented by the ICAO Code which was used to login when a Ground controller is not online. b. Clearance Delivery services at the airport represented by the ICAO Code which was used to login when a Ground or Delivery controller is not online. VII. The controller staffing Tower shall provide, when required in the absence of a Ground controller and Delivery controller at the airport represented by the ICAO Code which was used to login, Clearance Delivery to pilots who are not yet airborne. VIII. Tower shall provide, when required in the absence of a Ground controller at the airport represented by the ICAO Code which was used to login, Ground Control services to all aircraft requesting such services, but only at the airport where you are logged in. IX. Tower shall provide Tower services at the airport at which he is logged in. X. Tower shall provide Tower services in accordance with FAA 7110.65 this means: . Maintain Separation minimums. a. Wake Turbulence Separation Procedures and Advisories. XI. Tower has the final authority to declare runways in use and the direction of traffic flow at the airport. XII. Tower shall coordinate arrival runways with the controller providing Approach Control service (when online). XIII. Tower shall coordinate departure runways and departure headings and routes with the controller providing Departure/Approach Control service (when online). XIV. Tower is responsible for the initial separation between departing aircraft. XV. Tower will have to coordinate with the Ground controller e.g. Information about active RWYs etc.. XVI. Tower is responsible for aircraft ground movement on all active runways. XVII. If an aircraft executes a missed approach, or is instructed by either to execute a missed approach or go-around, he has to inform APP or DEP immediately. XVIII. Tower will transfer Aircrafts as follows: . To the Ground Controller (when available) after an aircraft is clear of an active runway and no other active runways will be crossed as the aircraft taxis to parking. a. To the controller providing DEP/APP Control services when Tower observes a positive rate of climb and before the aircraft reaches 1,000 ft. Above Ground Level (AGL). b. In the absence of any further ATC, to UNICOM (122.800) as soon as practical after the aircraft becomes airborne. Aircraft will be instructed to resume their own navigation at this time. XIX. Runway 8L/26R at Miami International Airport is not included in the default scenery of Microsoft Flight Simulator , Runway 8L/26R shall be considered closed unless a pilot indicates it is present in his scenery and offers its use. XX. VFR operations outside of Class B or Class C airspace: . Tower will advise all VFR aircraft of wind direction and velocity, and of runways in use. a. Tower will advise VFR traffic remaining in the pattern of the traffic pattern direction of the runway for takeoff and landing (left traffic or right traffic). b. Tower will advise all VFR traffic of any other aircraft operating in the traffic pattern, making a published approach for landing, or intending to takeoff, including the traffic leg that defines the position of the other aircraft in the pattern. c. VFR departures will be instructed to switch to UNICOM (122.800) as they are departing. d. VFR arrivals will be instructed to report turning base for final if applicable. XXI. VFR operations within Class B or Class C airspace: . Tower will advise all VFR aircraft of wind direction and velocity, and of runways in use. a. All VFR aircraft will be issued a discreet transponder code.

a.

b. All VFR departures from Class B or C airspace will be instructed to maintain an altitude at or below 2,500ft. until clear of Class B or C airspace, unless: I. The measured ceiling observation is lower than the recommended assigned altitude and more than 1,000 ft., in which case the controller will issue an assigned altitude below the measured ceiling and issue a departure heading which will expedite the VFR departure from Class B or C airspace. II. The measured ceiling observation is below 1,000 ft., in which case the airport will be closed for VFR operations due to weather. c. All VFR departures from Class B or C airspace will be issued takeoff clearance with the followingheadings: I. If the departing aircraft will be transferred to a controller providing Departure service, the pilot will be instructed to maintain runway heading. II. If the departing aircraft will be switching to UNICOM (on 122.800) after takeoff, the pilot will be issued a departure heading in a cardinal direction appropriate to the direction of the destination (i.e. NORTH, NORTHWEST, SOUTH, SOUTHEAST, etc.), and which will expedite an exit of Class B or C airspace. d. All VFR arrivals will be asked to report traffic pattern entry and/or position in the traffic pattern, if necessary. e. In the absence of further ATC, departing VFR aircraft will be instructed to squawk VFR ( 1-2-0-0) and informed that no further ATC service is available. XXII. As a part of all landing clearances, Tower will issue current winds for the arrival airport. XXIII. Do not connect as ATC unless you are sure you can stay controlling for at least 30 minutes. XXIV. 2. ATC must respect the controlled area and sector-borders. For example - do not control outside of your assigned airspace. If you expect new ATC to arrive, hand over to new ATC when he/she is ready. XXV. 3. When observing it is not allowed to use 'valid' callsign extensions (CTR, APP, TWR etc.) Append _OBS to the facility's callsing. Ex: KORD_OBS. To staff a position, use a valid callsign. It contains the 4-letter code of the airport, a underline and the 3-letter code of the position. In case of staffing a Centerposition, use the 4-letter code of the ARTCC. XXVI. 4. ATC positions should be manned in this order: CTR, APP, TWR, GND - if you are capable of handling. In other words - staff the highest position you can handle (DEP only when a lot of departing traffic expected, else APP will handle departures) XXVII. 5. Control of aircraft may only be transferred by co-ordination and handoff with the other ATC. Using guard or private messages to ask a pilot to transfer from another controller's control ("stealing") is not acceptable. XXVIII. 6. Always be ethical in your communication. Use proper language and follow proper procedures for issuing clearances. This will avoid misunderstandings between pilots and controllers. Remember that pilots come from many different countries and simple slang could be confusing. XXIX. 7. Controllers are not required to accept a SID/STAR that they don't have a description for, thus they may offer vectors thru that portion of flight. XXX. 8. The controller may/may not accept a SID/STAR made for SB FMS that may have altitude changes as this may conflict with other aircraft. XXXI. 9. When accepting a SID/STAR made for SB FMS or published by the FAA, the controller is required to use the phrase "as published", meaning that the pilot is allowed altitude and heading changes without prior approval to the initial approach fix. If the required altitudes differ from the published procedure, the controller is required to advise he will issue altitude changes to the SID/STAR. XXXII. 10. Each facility should have its own channel in Teamspeak. Multiple facilities on one frequency is not allowed.