Non-Movement Areas Are:
Uncontrolled
Taxiways not visible from the tower
Ares for loading and unloading passengers or cargo
Areas for parking and refueling
Maintenance areas
<-- Non-Movement Side
Movement Side -->
Movement Areas Are:
Controlled
Runways
Taxiways
Other controlled areas of an airport/heliport
While runway configuration selection is local control's (Tower's) job, you are expected to be able to select appropriate runways in use when controlling alone on ground. Picking a runway is very easy!
Aircraft are designed to take off into the wind. Just like if you were flying, send the aircraft to a runway of appropriate length and directionally based runway into the wind.
How do we know the winds?
Remember the weather bar in VRC from Unit 1? The winds are available on the top of your screen! Simply pick the runway which is most aligned with the wind.
EXAMPLE - Wind 180 @ 15KT use runway 18
Boston wind 290 @ 15 knots Altimeter 30.36
Areas of Responsibility:
As a ground controller, you are responsible for all taxiways and ramps that are IN movement areas, with the exception of runways and some special use taxiways, which are owned by local control (TWR). It is important to note that you cannot authorize an aircraft to cross any runway without authorization. In some cases local will issue a blanket (approved until said otherwise) crossing authorizations for inactive runways, however this varies with local SOP and specific controller coordination.
This diagram does a good job of showing that all ramps and some taxi ways at Dallas Love Airport are considered "non-movement" areas.
3−7−1. GROUND TRAFFIC MOVEMENT
a. Do not issue conditional instructions that are dependent upon the movement of an arrival aircraft on or approaching the runway or a departure aircraft established on a takeoff roll. Do not say, “Line up and wait behind landing traffic,” or “Taxi/proceed across Runway Three−Six behind departing/landing Citation.”
b. Do not issue unconditional instructions when authorizing movement on a runway/taxiway.
1. The following are examples of unconditional instructions and are not approved for use: “THE FIELD IS YOURS,” “CLEARED ON ALL SURFACES,” “THE AIRPORT IS YOURS,” and “PROCEED ON ALL RUNWAYS AND TAXIWAYS.”
2. “PROCEED AS REQUESTED” is not approved phraseology for instructing aircraft, vehicles, equipment, or personnel to cross or operate on a runway.
c. Do not use the word “cleared” in conjunction with authorization for aircraft to taxi or equipment/ vehicle/personnel operations. Use the prefix “taxi,” “proceed,” or “hold,” as appropriate, for aircraft instructions and “proceed” or “hold” for equipment/ vehicles/personnel.
d. Intersection departures may be initiated by a controller or a controller may authorize an intersection departure if a pilot requests. Issue the measured distance from the intersection to the runway end rounded “down” to the nearest 50 feet to any pilot who requests and to all military aircraft, unless use of the intersection is covered in appropriate directives.
3−7−2. TAXI AND GROUND MOVEMENT OPERATIONS
Issue the route for the aircraft/vehicle to follow on the movement area in concise and easy to understand terms. The taxi clearance/route must include the specific route to follow. When a taxi clearance to a runway is issued to an aircraft, confirm the aircraft has the correct runway assignment. NOTE− 1. A pilot’s read back of taxi instructions with the runway assignment can be considered confirmation of runway assignment. 2. Movement of aircraft or vehicles on nonmovement areas is the responsibility of the pilot, the aircraft operator, or the airport management.
a. When authorizing an aircraft to taxi or a vehicle to proceed on the movement area, specify the taxi instructions/route. If it is the intent to hold the aircraft/vehicle short of:
1. A runway: issue the route up to the runway hold short point. When issuing a runway crossing clearance, include specific instructions on where to cross the runway.
2. Any other point along the route, issue:
(a) the route up to the hold short point, or,
(b) the entire route and then state the hold short instructions. After issuing a crossing clearance, specify the taxi instructions/route an aircraft/vehicle is to follow, if not previously issued. NOTE− The absence of holding instructions authorizes an aircraft/vehicle to cross all taxiways that intersect the taxi route.
PHRASEOLOGY -
HOLD POSITION.
HOLD FOR (reason)
CROSS (runway), at (runway/taxiway)
TAXI/CONTINUE TAXIING/PROCEED VIA (route)
VIA (route), HOLD SHORT OF (location)
FOLLOW (traffic) (restrictions as necessary)
BEHIND (traffic).
b. When authorizing an aircraft to taxi to an assigned takeoff runway, state the departure runway followed by the specific taxi route. Issue hold short instructions, in accordance with paragraph a above, when an aircraft will be required to hold short of a runway or other points along the taxi route. NOTE− If the specific taxi route ends into a connecting taxiway with the same identifier (for example, taxiway “A” connects with Taxiway “A1”) at the approach end of the runway, the connecting taxiway may be omitted from the clearance.
PHRASEOLOGY−
RUNWAY (number), TAXI VIA (route as necessary).
RUNWAY (number), TAXI VIA (route as necessary)(hold short instructions as necessary).
c. Issue a crossing clearance to aircraft for each runway their route crosses. An aircraft must have crossed a previous runway before another runway crossing clearance may be issued. At those airports where the taxi distance between runway centerlines is 1,300 feet or less, multiple runway crossings may be issued with a single clearance.
PHRASEOLOGY− CROSS (runway) AT ( runway/taxiway), HOLD SHORT OF (runway)
d. When an aircraft/vehicle is instructed to “follow” traffic and requires a runway crossing, issue a runway crossing clearance in addition to the follow instructions and/or hold short instructions, as applicable.
g. Crossing of active runway(s) by aircraft/vehicle(s):
1. During departure operations, ensure that aircraft/vehicles intending to cross a runway do not cross the runway until the controller visually observes the departure aircraft in a turn, or the departure aircraft has passed the point where the crossing aircraft/vehicle is located.
2. During arrival operations, ensure the following:
(a) An aircraft/vehicle has completed crossing prior to the arriving aircraft crossing the landing threshold
(b) A crossing aircraft/vehicle will not cross the runway until the arrival has landed and either:
(2) The controller visually observes the aircraft exiting the runway prior to the point at which the crossing is intended
(3) The arriving aircraft has passed the point at which the crossing is intended.
h. Request a read back of runway hold short instructions when it is not received from the pilot/vehicle operator.
PHRASEOLOGY− READ BACK HOLD INSTRUCTIONS.
i. Issue progressive taxi/ground movement instructions when:
1. A pilot/operator requests.
3. Necessary during reduced visibility, especially when the taxi route is not visible from the tower.
NOTE− Progressive instructions may include step−by−step directions and/or directional turns.
3−9−1. DEPARTURE INFORMATION
Provide current departure information, as appropriate, to departing aircraft.
a. Departure information contained in the ATIS broadcast may be omitted if the pilot states the appropriate ATIS code.
b. Issue departure information by including the following:
1. Runway in use. (May be omitted if pilot states “have the numbers.”)
2. Surface wind from direct readout dial, wind shear detection system, or automated weather observing system information display. (May be omitted if pilot states “have the numbers.”)
3. Altimeter setting. (May be omitted if pilot states “have the numbers.”)
d. Issue the official ceiling and visibility, when available, to a departing aircraft before takeoff as follows:
1. To a VFR aircraft when weather is below VFR conditions.
g. Issue braking action for the runway in use as received from pilots when braking action advisories are in effect.
Practically Speaking - If the pilot does not call for taxi with the ATIS letter or "The Numbers," issue the altimeter setting with the taxi instruction. The runway in use is covered in the taxi clearance (By saying the runway), and the surface wind is usually covered by the tower.
2−1−17. RADIO COMMUNICATIONS
a. Transfer radio communications before an aircraft enters the receiving controller’s area of jurisdiction unless otherwise coordinated or specified by a letter of agreement or a facility directive.
b. Transfer radio communications by specifying the following:
1. The facility name or location name and terminal function to be contacted. TERMINAL: Omit the location name when transferring communications to another controller within your facility, or, when the tower and TRACON share the same name (for example, Phoenix Tower and Phoenix TRACON).
2. Frequency to use except the following may be omitted:
(a) FSS frequency.
(b) Departure frequency if previously given or published on a SID chart for the procedure issued.
(c) TERMINAL:
(1) Ground or local control frequency if in your opinion the pilot knows which frequency is in use.
(2) The numbers preceding the decimal point if the ground control frequency is in the 121 MHz bandwidth.
EXAMPLE− “Contact Tower.” “Contact Ground.” “Contact Ground Point Seven.” “Contact Ground, One Two Zero Point Eight.” “Contact Huntington Radio.” “Contact Departure.” “Contact Los Angeles Center, One Two Three Point Four.”
3. Time, fix, altitude, or specifically when to contact a facility. You may omit this when compliance is expected upon receipt.
PHRASEOLOGY− CONTACT (facility name or location name and terminal function), (frequency). If required, AT (time, fix, or altitude).
e. In situations where an operational advantage will be gained, and following coordination with the receiving controller, you may instruct aircraft on the ground to monitor the receiving controller ’s frequency.
EXAMPLE− “Monitor Tower.” “Monitor Ground.” “Monitor Ground Point Seven.” “Monitor Ground, One Two Zero Point Eight.”
2−4−12. INTERPHONE MESSAGE FORMAT
Use the following format for interphone intra/interfacility communications:
a. Both the caller and receiver identify their facility and/or position in a manner that ensures they will not be confused with another position.
EXAMPLE− Caller: “Albuquerque Center Sixty Three, Amarillo Departure.” Receiver: “Albuquerque Center.”
b. Between two facilities which utilize numeric position identification, the caller must identify both facility and position.
EXAMPLE− Caller: “Albuquerque Sixty Three, Fort Worth Eighty Two.”
c. Caller states the type of coordination to be accomplished when advantageous.
e. The receiver states the response to the caller’s message followed by the receiver’s operating initials.
f. The caller states his or her operating initials.
2−4−13. INTERPHONE MESSAGE TERMINATION
Terminate interphone messages with your operating initials.
3−1−4. COORDINATION BETWEEN LOCAL AND GROUND CONTROLLERS
Local and ground controllers must exchange information as necessary for the safe and efficient use of airport runways and movement areas. This may be accomplished via verbal means, flight progress strips, other written information, or automation displays. As a minimum, provide aircraft identification and applicable runway/intersection/taxiway information as follows:
a. Ground control must notify local control when a departing aircraft has been taxied to a runway other than one previously designated as active.
b. Ground control must notify local control of any aircraft taxied to an intersection for takeoff. This notification may be accomplished by verbal means or by flight progress strips.
Practically Speaking - When working ground, most of the coordination will be with the tower controller. Simply follow the same format above with your request/information.
EXAMPLE - "Rodgers tower, Rodgers gound." "Go ahead" "Request to cross FDX611 runway 17L at E6" "Approved CB" "OP"
Appendix A. Standard Operating Practice (SOP) for the Transfer of Position Responsibility
A. Preview the Position(Relieving Controller):
Observe position equipment, operational situation, and the work environment. Familiarize yourself with the weather, any NOTAMS and other pertinent information.
Listen to voice communications and observe current and pending traffic and correlate with flight movement information. Observe any other operational actions.
Advise the specialist being relieved that your preview is complete and that the briefing may begin by completing the following steps:
a. Set your primary frequency to that of the position you are about to take over.
b. Advise the specialist being relieved that the position has been reviewed, and you are ready for the brief.
B. The Briefing(Controlled Being Relieved/Relieving Controller):
The controller being relieved shall brief the relieving controller on the following:
Traffic and details about traffic operations(Current flows, aircraft in holding, aircraft waiting for release, aircraft receiving flight following etc)
Any pilot/special requests
Any agreed coordination with adjacent facilities(eg Pointouts, control agreements, special in-trail sequencing agreements etc)
Any coordination requests
Runway configurations the controller being relieved deems pertinent
Weather Trends, PIREPs and any other pertinent information(NOTAMs etc)
The relieving controller shall ask any questions he may have, to ensure smooth and efficient transfer of control. The controller being relieved shall completely answer any questions the relieving controller may have.
C. Assumption of Position Responsibility(Controlled Being Relieved/Relieving Controller):
In order to assume control of a position, the relieving controller shall state his operating initials with statement "My control". This shall indicate to the controller being relieved that the control has successfully been assumed. The controller being relieved, shall reply with statement "Your control" and his operating initials, to confirm to the relieving controller that the control has successfully been transferred.
D. Post-Transfer Review(Controlled Being Relieved):
After the brief is complete, the controller being relieved, shall continue to observe the position/s and monitor the appropriate frequencies, to ensure that nothing has been forgotten. In case something has been forgotten or needs amending, the controller being relieved shall pass the information to the relieving controller at a rate he deems necessary to ensure a speedy solution to the problem at hand. The controller being relieved may sign off once the relieving controller clearly has the required information to control the position.
Helicopter Operations
As a ground controller you are also responsible for controlling helicopters on your taxiways. There are three ways a helicopter can taxi.
Surface Taxi:
3−11−1. TAXI AND GROUND MOVEMENT OPERATION
a. When necessary for a wheeled helicopter to taxi on the surface, use the phraseology in Paragraph 3−7−2, Taxi and Ground Movement Operations.
"N123AB TAXIWAY ALPHA AT BRAVO, TAXI VIA ALPHA"
Blackhawk surface taxing at Monroe, LA
Hover Taxi:
b. When requested or necessary for a helicopter to proceed at a slow speed above the surface, normally below 20 knots and in ground effect, use the following phraseology, supplemented as appropriate with the phraseology in Paragraph 3−7−2, Taxi and Ground Movement Operations. PHRASEOLOGY− HOVER-TAXI
“Airmed 60 RUNWAY 19, HOVER TAXI VIA S"
"Airmed 40" a med-evac helicopter hover taxing down alpha at Dallas Love Field
Air Taxi:
c. When requested or necessary for a helicopter to proceed expeditiously from one point to another, normally below 100 feet AGL and at airspeeds above 20 knots, use the following phraseology, supplemented as appropriate with the phraseology in Paragraph 3−7−2, Taxi and Ground Movement Operations.
PHRASEOLOGY− AIR-TAXI:
VIA (direct, as requested, or specified route) TO (location, heliport, helipad, operating/movement area, active/inactive runway).
AVOID (aircraft/vehicles/personnel). If required,
REMAIN AT OR BELOW (altitude).
CAUTION (wake turbulence or other reasons above).
LAND AND CONTACT TOWER, or
HOLD FOR (reason− takeoff clearance, release, landing/taxiing aircraft, etc.).
"Helicopter 817MC AIR TAXI VIA DIRECT TO THE EAST GA RAMP. CAUTION THE 737 ON TAXIWAY ALPHA"