Order 7110.65P Air Traffic Control
This document is cancelled. It may have been replaced. Check the official source before relying on it.
Order 7110.65PAir Traffic Control
•
•
Basic Eff...,tive
February 19,2004 - Au!:ust 4, 2004
U.S. Department of Transportation
Federal Aviation Administration
Order 7110.65P
Air Traffic Control
Orlando Airport Traffic Control Tower
An electronic version of this publication is on the internet at
http://www.faa.gov/atpubs
Distribution: ZAT-710 February 19, 2004 Initiated By: ATP-I00
7110.65P DIRECTIVE NO. 1 _ RECORD OF CHANGES
CHANGE SUPPLEMENTS CHANGE SUPPLEMENTS TO OPTIONAL TO OPTIONAL BASIC BASIC
..
.
FAA Form 1320-5 (6-80) USE PREVIOUS EDmON
Order 7110.65PAir Traffic Control › Foreword
~r--------
Date: November 3. 2003
Foreword
Air Traffic Control
7110.65P
David B. Johnson
Director of Air Tra
This order prescribes air traffic control procedures and phraseology for use by personnel providing air
traffic control services. Controllers are required to be familiar with the provisions of this order that
pertain to their operational responsibilities and to exercise their best judgment if they encounter
situations n red by.
~W e.:"J.+.l.L1..ft(r~
•
Order 7110.65PAir Traffic Control › Explanation of Changes
Air Traffic Control Explanation of Changes
Direct questions through appropriate facility/region staff
to the Office of Primary Interest (OPI)
711O.65P
a. 1-2-6. ABBREVIATIONS
Adds the following abbreviations to Table 1-2-1: GS Ground Stop (ATT-200) SID Standard Instrument Departure (ATP-120) WAAS Wide Area Augmentation System (ATP-104)
b. 2-1-6. SAFETY ALERTS
Makes editorial changes. (ATP-120)
c. 2-1-10. NAVAID MALFUNCTIONS
Adds phraseology to hroadcaslthe anomaly report to other aircraft. It requiresATCto determine availability ofWAAS service when receiving reports of a WAAS anomaly. (ATP-I04)
d. 2-2-6. IFR FLIGHT PROGRESS DATA
Removes reference to the special aircraft type prefixes B, L, T, and F, which denote TCAS equipment and/or B757 type aircraft. It also includes the requirementto forward the number of aircraft, if more than one, which had been omittedfrom earlierversions ofthis paragraph. (ATP-110)
e. 2-3-2. EN ROUTE DATA ENTRIES
Removes reference to the special aircraft type prefix "F' and deletes the now unused prefix "T" from the completed flight progress strip example. (ATP-ll0)
f. 2-3-3. TERMINAL DATA ENTRIES
Removes reference to the special aircraft type prefix "F." (ATP-120)
g. 2-6-4. WEATHER AND CHAFF SERVICES
Includes microburst as significant weather. (ATP-120)
h. 3-7-3. GROUND OPERATIONS
Advises controllers to exercise caution when taxiing smaller aircraft/helicopters in the vicinity oflarger aircraft. (ATP-120)
i. 3-8-1. SEQUENCE/SPACING APPLICATION
Adds the requirement to issue additional instructions as necessary to aircraft performing the go-around maneuver. (ATP-120)
Explanation of Changes
j. 3-9-1. DEPARTURE INFORMATION
Includes microburst as significant weather. (ATP-120)
k. 3-10-1. LANDING INFORMATION
Includes microburst as significant weather. (ATP-120)
I. 4-2-1. CLEARANCE ITEMS
Reinstates the term SID that may be used when referring to certain instrument departure procedures. (ATP-120)
m, 4-3-2. DEPARTURE CLEARANCES
Reinstatesthe term SID that may be used when referring to certain instrument departure procedures. (ATP-120)
n, 4-3-3. ABBREVIATED DEPARTURE CLEARANCE
Reinstates the term SID that may be used when referring to certain instrument departure procedures. (ATP-120)
o. 4-3-4. DEPARTURE RESTRICTIONS, CLEARANCE VOID TIMES, HOLD FOR RELEASE, AND RELEASE TIMES
Requires aircraft to depart within 5 minutes of the EDCT, or for facilities to coordinate with the ATCSCC for a new departure time. (ATT-200)
p. 4-3-5. GROUND STOP
Adds new paragraph to provide additional guidance about ground stops. (ATT-200)
q. 4-8-9. MISSED APPROACH
Inserts the phrase "or appropriate military form." (ATP-120)
r, 5-5-4. MINIMA
Makes editorial formatting changes. (ATP-120)
s, 5-7-3. MINIMA
Affords the controllers the option to assign speeds helow the minima recommended. It will he the pilot's responsibility to advise ATC if he/she is unable to comply with the speed assignment. (ATP-120)
E ofC-l
t. 5-9-1. VECTORS TO FINAL APPROACH COURSE
Defines the minimum distance from the approach gate an RNAVaircraftcanbevectoredto interceptthefinalcourse. (ATP-I04)
u. 10-1-6. AIRPORT GROUND EMERGENCY
Adds a requirement, workload permitting, to monitor the progress of emergency responders on the airport to help direct them to an accident scene. (ATP-120)
v. APPENDIXA. AIRCRAFT INFORMATION
Adds andcorrectsinformationon aircrafltypedesignators, aircraft models, and performance data for selected fixed-wing aircraft. (ATP-120)
EofC-2
w. Graphics throughout this order were replaced for uniformity. Revision bars were not used. (ATP-120)
x. Changes the abbreviation of Micro-EARTS (M-EARTS) to read "MEARTS" throughout this order. (ATP-I00)
y. Removes the apostrophe throughout this order in cases when it was used to show the plural form of most acronyms or abbreviations. Revision bars were not used. (ATA-lO)
z, Editorial/format changes were made where necessary. Revision bars were not used due to the insignificant nature of the changes. (ATA-I0)
Explanation of Changes
•
•
Table of Contents › Chapter 2. General Control
Table of Contents
Chapter 1. Introduction
Section 1. General
Paragraph 1-1-1. PURPOSE . 1-1-2. DISTRIBUTION . 1-1-3. CANCELLATION . 1-1-4. EXPLANATIONOFMAJORCHANGES . 1-1-5. EFFECTIVEDATE . 1-1-6. RECOMMENDATIONS FOR PROCEDURAL CHANGES . 1-1-7. PUBLICATION AND DELIVERY DATES . 1-1-8. PROCEDURAL LETTERS OF AGREEMENT . 1-1-9. CONSTRAINTS GOVERNING SUPPLEMENTS AND PROCEDURAL DEVIATIONS .
Section 2. Terms of Reference
1-2-1. WORD MEANINGS . 1-2-2. COURSE DEFINITIONS . 1-2-3. NOTES . 1-2-4. REFERENCES . 1-2-5. ANNOTATIONS . 1-2-6. ABBREVIATIONS .
Chapter 2. General Control
Section 1. General
2-1-1. ATCSERVICE . 2-1-2. DUTY PRIORITY . 2-1-3. PROCEDURAL PREFERENCE . 2-1-4. OPERATIONAL PRIORITY . 2-1-5. EXPEDITIOUS COMPLIANCE . 2-1-6. SAFETY ALERT . 2-1-7. INFLIGHTEQUIPMENTMALFUNCTIONS . 2-1-8. MINIMUM FUEL . 2-1-9. REPORTING ESSENTIAL FLIGHT INFORMATION . 2-1-10. NAVAIDMALFUNCTIONS . 2-1-11. USEOFMARSA . 2-1-12. MILITARY PROCEDURES . 2-1-13. FORMATION FLIGHTS . 2-1-14. COORDINATE USE OF AIRSPACE . 2-1-15. CONTROL TRANSFER . 2-1-16. SURFACEAREAS . 2-1-17. RADIO COMMUNICATIONS TRANSFER . 2-1-18. OPERATIONAL REQUESTS . 2-1-19. WAKE TURBULENCE . 2-1-20. WAKE TURBULENCE CAUTIONARY ADVISORIES . 2-1-21. TRAFFIC ADVISORIES . 2-1-22. BIRD ACTIVITY INFORMATION .
Table of Contents
711O.65P
Page 1-1-1 1-1-1 1-1-1 1-1-1 1-1-1 1-1-1 1-1-1 1-1-2
1-1-2
1-2-1 1-2-2 1-2-2 1-2-3 1-2-3 1-2-3
2-1-1 2-1-1 2-1-1 2-1-2 2-1-3 2-1-3 2-1-4 2-1-4 2-1-5 2-1-5 2-1-5 2-1-6 2-1-6 2-1-6 2-1-7 2-1-7 2-1-7 2-1-8 2-1-9 2-1-9 2-1-9 2-1-10
711O.65P
Paragraph 2-1-23. TRANSFEROFPOSITIONRESPONSIBIUTY . 2-1-24. WHEELS DOWN CHECK . 2-1-25. SUPERVISORY NOTIFICATION . 2-1-26. PILOTDEVIATlONNOTIFICATION . 2-1-27. TCAS RESOLUTlON ADVISORlES .
Section 2. Flight Plans and Control Infonnation
2-2-1. RECORDINGINFORMATlON . 2-2-2. FORWARDING INFORMATION . 2-2-3. FORWARDING VFR DATA . 2-2-4. MIUTARY DVFR DEPARTURES . 2-2-5. IFR TO VFR FUGHT PLAN CHANGE . 2-2-6. IFR FLIGHT PROGRESS DATA . 2-2-7. MANUAL INPUT OF COMPUTER-ASSIGNED BEACON CODES . 2-2-8. ALTRVINFORMATION . 2-2-9. COMPUTER MESSAGE VERlFICATION . 2-2-10. TRANSMIT PROPOSED FUGHT PLAN . 2-2-11. FORWARDING AMENDED AND UTM DATA . 2-2-12. AIRBORNE MIUTARY FLIGHTS . 2-2-13. FORWARDING FLIGHT PLAN DATABETWEEN U.S. ARTCCs AND CANADIAN ACes . 2-2-14. TELETYPE FUGHT DATAFORMAT- U.S. ARTCCs - CANADIAN ACCs . 2-2-15. NORTH AMERlCAN ROUTE PROGRAM (NRP) INFORMATION
Section 3. Flight Progress Strips
2-3-1. GENERAL . 2-3-2. ENROUTEDATAENTRlES . 2-3-3. TERMINALDATAENTRlES . 2-3-4. AIRCRAFT IDENTITY . 2-3-5. AIRCRAFT TYPE . 2-3-6. USAF/USN UNDERGRADUATE PILOTS . 2-3-7. AIRCRAFT EQUIPMENT SUFFIX . 2-3-8. CLEARANCE STATUS . 2-3-9. CONTROL SYMBOLOGY .
Section 4. Radio and Interphone Communications
2-4-1. RADlO COMMUNICATIONS . 2-4-2. MONITORING . 2-4-3. PILOT ACKNOWLEDGMENTjREAD BACK . 2-4-4. AUTHORlZED INTERRUPTIONS . 2-4-5. AUTHORlZED TRANSMISSlONS . 2-4-6. FALSE OR DECEPTIVE COMMUNICATlONS . 2-4-7. AUTHORIZED RELAYS . 2-4-8. RADlO MESSAGE FORMAT . 2-4-9. ABBREVIATED TRANSMISSIONS . 2-4-10. INTERPHONE TRANSMISSlONPRlORlTIES . 2-4-11. PRlORITY INTERRUPTlON .
Page 2-1-11 2-1-11 2-1-11 2-1-11 2-1-11
2-2-1 2-2-1 2-2-1 2-2-1 2-2-1 2-2-1 2-2-2 2-2-2 2-2-2 2-2-3 2-2-3 2-2-4
2-2-4
2-2-4 2-2-5
2-3-1 2-3-3 2-3-5 2-3-8 2-3-9 2-3-9 2-3-9 2-3-9 2-3-9
2-4-1 2-4-1 2-4-1 2-4-1 2-4-1 2-4-1 2-4-2 2-4-2 2-4-2 2-4-2 2-4-2
•
•
•
ii Table of Contents
Paragraph 2-4-12. INTERPHONE MESSAGE FORMAT . 2-4-13. INTERPHONE MESSAGE TERMINATION . 2-4-14. WORDS AND PHRASES . 2-4-15. EMPHASIS FOR CLARITY . 2-4-16. ICAO PHONETICS . 2-4-17. NUMBERS USAGE ····· 2-4-18. NUMBER CLARIFICATION . 2-4-19. FACILITY IDENTIFICATION . 2-4-20. AIRCRAFT IDENTIFICATION . 2-4-21. DESCRlPTION OF AIRCRAFT TYPES . 2-4-22. AIRSPACE ClASSES .
Section 5. Route and NAVAID Description
2-5-1. AIRWAYS AND ROUTES . 2-5-2. NAVAIDTERMS . 2-5-3. NAVAIDFIXES .
Section 6. Weather Information
2-6-1. FAMILIARlZATION . 2-6-2. HAZARDOUS INFLIGHT WEATHER ADVISORY SERVICE (HIWAS) .. 2-6-3. PIREP INFORMATION . 2-6-4. WEATHER AND CHAFF SERVICES . 2-6-5. CALM WIND CONDITIONS . 2-6-6. REPORTING WEATHER CONDITIONS . 2-6-7. DISSEMINATING WEATHER INFORMATION .
Section 7. Altimeter Settings
2-7-1. CURRENT SETTINGS . 2-7-2. ALTIMETER SETTING ISSUANCE BELOW LOWEST USABLE FL
Section 8. Runway Visibility Reporting- Terminal
2-8-1. FURNISH RVR/RVV VALUES . 2-8-2. ARRlVAUDEPARTURERUNWAYVISIBILITY . 2-8-3. TERMINOLOGY .
Section 9. Automatic Terminal Information
Service Procedures
2-9-1. APPLICATION . 2-9-2. OPERATING PROCEDURES . 2-9-3. CONTENT .
Table of Contents
Page 2-4-3 2-4-4 2-4-4 2-4-4 2-4-5 2-4-5 2-4-8 2-4-8 2-4-8 2-4-11 2-4-11
2-5-1 2-5-1 2-5-2
2-6-1 2-6-1 2-6-1 2-6-2 2-6-3 2-6-3 2-6-4
2-7.-1 2-7-1
2-8-1 2-8-1 2-8-1
2-9-1 2-9-1 2-9-1
iii
Section 10. Team Position Responsibilities
Table of Contents › Chapter 3. Airport Traffic Control - Terminal
Paragraph 2-10-1. EN ROUTE SECTOR TEAM POSITION RESPONSIBILITIES . 2-10-2. TERMINALRADAR/NONRADAR TEAM POSITION RESPONSIBILITIES . 2-10-3. TOWER TEAM POSITION RESPONSIBILITIES .
Chapter 3. Airport Traffic Control- Terminal
Section 1. General
3-1-1. PROVIDE SERVICE . 3-1-2. PREVENTIVE CONTROL . 3-1-3. USE OF ACTIVE RUNWAYS . 3-1-4. COORDINATION BETWEEN LOCAL AND GROUND CONTROLLERS. 3-1-5. VEHICLES/EQUIPMENT/PERSONNELONRUNWAYS . 3-1-6. TRAFFIC INFORMATION . 3-1-7. POSITION DETERMINATION . 3-1-8. LOW LEVEL WIND SHEAR ADVISORIES . 3-1-9. USE OF TOWER RADAR DISPLAYS . 3-1-10. OBSERVED ABNORMALITIES . 3-1-11. SURFACE AREA RESTRICTIONS . 3-1-12. VISUALLYSCANNING RUNWAYS . 3-1-13. ESTABLISHING TWO-WAYCOMMUNICATIONS . 3-1-14. GROUND OPERATIONS WHEN VOLCANIC ASH IS PRESENT .
Section 2. Visual Signals
3-2-1. LIGHT SIGNALS . 3-2-2. WARNING SIGNAL . 3-2-3. RECEIVER-ONLY ACKNOWLEDGMENT .
Section 3. Airport Conditions
3-3-1. LANDING AREA CONDITION . 3-3-2. CLOSED/UNSAFE RUNWAY INFORMATION . 3-3-3. TIMELY INFORMATION . 3-3-4. BRAKING ACTION . 3-3-5. BRAKING ACTION ADVISORIES . 3-3-6. ARRESTING SYSTEM OPERATION . 3-3-7. FAR FIELD MONITOR (PPM) REMOTE STATUSUNIT .
Section 4. Airport Lighting
3-4-1. EMERGENCY LIGHTING . 3-4-2. RUNWAYEND IDENTIFIER LIGHTS . 3-4-3. VISUAL APPROACH SLOPE INDICATORS (VASI) . 3-4-4. APPROACH LIGHTS . 3-4-5. ALS INTENSITY SETTINGS . 3-4-6. SEQUENCED FLASHING LIGHTS (SFL) . 3-4-7. MALSR/ODALS . 3-4-8. ALSF-2/SSALR .
Page 2-10-1
2-10-2 2-10-4
3-1-1 3-1-1 3-1-1 3-1-2 3-1-2 3-1-2 3-1-3 3-1-3 3-1-4 3-1-5 3-1-5 3-1-5 3-1-5 3-1-6
3-2-1 3-2-1 3-2-1
3-3-1 3-3-1 3-3-1 3-3-2 3-3-2 3-3-3 3-3-4
3-4-1 3-4-1 3-4-1 3-4-1 3-4-2 3-4-2 3-4-2 3-4-3
•
•
iv Table of Contents
Paragraph 3-4-9. RUNWAY EDGE LIGHTS . 3-4-10. HIGH INTENSITY RUNWAY, RUNWAY CENTERLINE, AND TOUCHDOWN ZONE LIGHTS . 3-4-11. HIRL ASSOCIATED WITH MALSR . 3-4-12. HIRL CHANGES AFFECTING RVR . 3-4-13. MEDIUM INTENSITY RUNWAY LIGHTS . 3-4-14. SIMULTANEOUS APPROACH AND RUNWAY EDGE LIGHT OPERATION . 3-4-15. HIGH SPEED TURNOFF LIGHTS . 3-4-16. TAXIWAYLIGHTS . 3-4-17. OBSTRUCTION LIGHTS . 3-4-18. ROTATING BEACON .
Section S. Runway Selection
3-5-1. SELECTION ······························· 3-5-2. STOL RUNWAYS . 3-5-3. TAILWIND COMPONENTS .
Section 6. Airport Surface Detection Procedures
3-6-1. EQUIPMENT USAGE . 3-6-2. INFORMiITIONUSAGE . 3-6-3. IDENTIFICATION ···· 3-6-4. AMASS ALERT RESPONSES .
Section 7. Taxi and Ground Movement Procedures
3-7-1. GROUND TRAFFIC MOVEMENT . 3-7-2. TAXI AND GROUND MOVEMENT OPERATIONS . 3-7-3. GROUND OPERATIONS . 3-7-4. RUNWAY PROXIMITY . 3-7-5. PRECISION APPROACH CRITICAL AREA .
Section 8. Spacing and Sequencing
3-8-1. SEQUENCE/SPACING APPLICATION . 3-8-2. TOUCH-AND-GO OR STOP-AND-GO OR LOW APPROACH . 3-8-3. SIMULTANEOUS SAME DIRECTION OPERATION . 3-8-4. SIMULTANEOUS OPPOSITE DIRECTION OPERATION .
Section 9. Departure Procedures and Separation
3-9-1. DEPARTURE INFORMATION . 3-9-2. DEPARTURE DELAY INFORMATION . 3-9-3. DEPARTURE CONTROL INSTRUCTIONS . 3-9-4. TAXI INTO POSITION AND HOLD (TIPH) . 3-9-5. ANTICIPATING SEPARATION . 3-9-6. SAME RUNWAY SEPARATION . 3-9-7. WAKE TURBULENCE SEPARATION FOR INTERSECTION DEPARTURES .
Table of Contents
Page 3-4-3
3-4-3 3-4-3 3-4-4 3-4-4
3-4-4 3-4-4 3-4-4 3-4-5 3-4-5
3-5-1 3-5-1 3-5-1
3-6-1 3-6-1 3-6-1 3-6-1
3-7-1 3-7-1 3-7-3 3-7-4 3-7-4
3-8-1 3-8-1 3-8-1 3-8-2
3-9-1 3-9-1 3-9-1 3-9-2 3-9-3 3-9-3
3-9-5
v
Table of Contents › Chapter 4. IFR
Paragraph 3-9-8. INTERSECTING RUNWAY SEPARATION . 3-9-9. TAKEOFF CLEARANCE . 3-9-10. CANCELLATION OF TAKEOFF CLEARANCE .
Section 10. Arrival Procedures and Separation
3-10-1. LANDING INFORMATION . 3-10-2. FORWARDING APPROACH INFORMATION BY NONAPPROACH CONTROL FACILITIES . 3-10-3. SAME RUNWAY SEPARATION . 3-10-4. INTERSECTING RUNWAY SEPARATION . 3-10-5. LANDING CLEARANCE . 3-10-6. ANTICIPATING SEPARATION . 3-10-7. LANDING CLEARANCE WITHOUT VISUAL OBSERVATION . 3-10-8. WITHHOLDING LANDING CLEARANCE . 3-10-9. RUNWAY EXITING . 3-10-10. ALTITUDE RESTRICTED LOW APPROACH . 3-10-11. CLOSED TRAFFIC . 3-10-12. OVERHEAD MANEUVER . 3-10-13. SIMULATED FLAMEOUT (SFO~APPROACHES/EMERGENCY
~.ill¥I~JnW'J,~i~2J~:r.1~~.S~~~~~~~ .
Section 11. Helicopter Operations
3-11-1. TAXI AND GROUND MOVEMENT OPERATION . 3-11-2. HELICOPTER TAKEOFF CLEARANCE . 3-11-3. HELICOPTER DEPARTURE SEPARATION . 3-11-4. HELICOPTERARRIVALSEPARATION . 3-11-5. SIMULTANEOUS LANDINGS OR TAKEOFFS . 3-11-6. HELICOPTER LANDING CLEARANCE .
Section 12. Sea Lane Operations
3-12-1. APPLICATION . 3-12-2. DEPARTURE SEPARATION . 3-12-3. ARRIVAL SEPARATION .
Chapter 4. IFR Section 1. NAVAID Use Limitations
4-1-1. ALTITUDE AND DISTANCE LIMITATIONS . 4-1-2. EXCEPTIONS . 4-1-3. CROSSING ALTITUDE . 4-1-4. VFR-ON-TOP . 4-1-5. FIXUSE .
Page 3-9-6 3-9-7 3-9-8
3-10-1
3-10-1 3-10-2 3-10-3 3-10-6 3-10-6 3-10-7 3-10-7 3-10-7 3-10-8 3-10-8 3-10-8
3-10-9
3-11-1 3-11-1 3-11-2 3-11-3 3-11-3 3-11-4
3-12-1 3-12-1 3-12-1
4-1-1 4-1-2 4-1-2 4-1-2 4-1-2
•
• vi Table of Contents
Section 2. Clearances
Paragraph 4-2-1. CLEARANCE ITEMS . 4-2-2. CLEARANCE PREFIX . 4-2-3. DELIVERY INSTRUCTIONS . 4-2-4. CLEARANCE RELAY . 4-2-5. ROUTE OR ALTITUDE AMENDMENTS . 4-2-6. THROUGH CLEARANCES . 4-2-7. ALTRV CLEARANCE . 4-2-8. IFR-VFR AND VFR-IFR FLIGHTS . 4-2-9. CLEARANCE ITEMS .
Section 3. Departure Procedures
4-3-1. DEPARTURE TERMINOLOGY . 4-3-2. DEPARTURE CLEARANCES . 4-3-3. ABBREVIATED DEPARTURE CLEARANCE . 4-3-4. DEPARTURE RESTRICTIONS, CLEARANCE VOID TIMES, HOLD FOR RELEASE, AND RELEASE TIMES . 4-3-5. GROUND STOP . 4-3-6. DELAY SEQUENCING . 4-3-7. FORWARD DEPARTURE DELAY INFORMATION . 4-3-8. COORDINATION WITH RECEIVING FACILITY . 4-3-9. VFR RELEASE OF IFR DEPARTURE . 4-3-10. FORWARDING DEPARTURE TIMES .
Section 4. Route Assignment
4-4-1. ROUTE USE · 4-4-2. ROUTE STRUCTURE TRANSITIONS . 4-4-3. DEGREE-DISTANCE ROUTE DEFINITION FOR MILITARY OPERATIONS . 4-4-4. ALTERNATIVE ROUTES . 4-4-5. CLASS G AIRSPACE .
Section 5. Altitude Assignment and Verification
4-5-1. VERTICAL SEPARATION MINIMA . 4-5-2. FLIGHT DIRECTION . 4-5-3. EXCEPTIONS . 4-5-4. LOWEST USABLE FLIGHT LEVEL . 4-5-5. ADJUSTED MINIMUM FLIGHT LEVEL . 4-5-6. MINIMUM EN ROUTE ALTITUDES .. 4-5-7. ALTITUDE INFORMATION . 4-5-8. ANTICIPATED ALTITUDE CHANGES . 4-5-9. ALTITUDE CONFIRMATION- NONRADAR .
Table of Contents
711O.65P
Page 4-2-1 4-2-1 4-2-1 4-2-1 4-2-1 4-2-2 4-2-2 4-2-2 4-2-3
4-3-1 4-3-1 4-3-3
4-3-5 4-3-6 4-3-6 4-3-6 4-3-6 4-3-7 4-3-7
4-4-1 4-4-2
4-4-2 4-4-3 4-4-3
4-5-1 4-5-1 4-5-2 4-5-2 4-5-2 4-5-3 4-5-3 4-5-7 4-5-7
vii
71m65P
Section 6. Holding Aircraft
Paragraph 4-6-1. CLEARANCE TO HOLDING FIX . 4-6-2. CLEARANCE BEYOND FIX . 4-6-3. DELAyS . 4-6-4. HOLDING INSTRUCTIONS . 4-6-5. VISUAL HOLDING POINTS . 4-6-6. HOLDING FLIGHT PATH DEVIATION . 4-6-7. UNMONITORED NAVAIDs . 4-6-8. ILS PROTECTION/CRITICAL AREAS .
Table of Contents › Chapter 5. Radar
Section 7. Arrival Procedures
4-7-1. CLEARANCE INFORMATION . 4-7-2. ADVANCE DESCENT CLEARANCE . 4-7-3. SINGLE FREQUENCY APPROACHES (SFA) . 4-7-4. RADIO FREQUENCY AND RADAR BEACON CHANGES FOR MILITARY AIRCRAFT .. 4-7-5. MILITARY TURBOJET EN ROUTE DESCENT . 4-7-6. ARRIVAL INFORMATION . 4-7-7. WEATHER INFORMATION . 4-7-8. BELOW MINIMA REPORT BY PILOT . 4-7-9. TRANSFER OF JURISDICTION . 4-7-10. APPROACH INFORMATION . 4-7-11. ARRIVAL INFORMATION BYAPPROACH CONTROL FACILITIES . 4-7-12. AIRPORT CONDITIONS . 4-7-13. SWlTCHING ILS/MLS RUNWAYS .
Section 8. Approach Clearance Procedures
4-8-1. APPROACH CLEARANCE . 4-8-2. CLEARANCE LIMIT . 4-8-3. RELAYED APPROACH CLEARANCE . 4-8-4. ALTITUDE ASSIGNMENT FOR MILITARY HIGH ALTITUDE INSTRUMENT APPROACHES . 4-8-5. SPECIFYING ALTITUDE . 4-8-6. CIRCLING APPROACH . 4-8-7. SIDE-STEP MANEUVER . 4-8-8. COMMUNICATIONS RELEASE . 4-8-9. MISSED APPROACH . 4-8-10. APPROACH INFORMATION . 4-8-11. PRACTICE APPROACHES . 4-8-12. LOW APPROACH AND TOUCH-AND-GO .
Chapter 5. Radar
Section 1. General
5-1-1. PRESENTATION AND EQUIPMENT PERFORMANCE . 5-1-2. ALIGNMENT ACCURACY CHECK . 5-1-3. RADAR USE . 5-1-4. BEACONRANGEACCURACY .
Page 4-6-1 4-6-2 4-6-2 4-6-3 4-6-3 4-6-3 4-6-3 4-6-3
4-7-1 4-7-1 4-7-1
4-7-2 4-7-2 4-7-3 4-7-3 4-7-3 4-7-4 4-7-4 4-7-4 4-7-5 4-7-6
4-8-1 4-8-4 4-8-4
4-8-4 4-8-4 4-8-4 4-8-4 4-8-5 4-8-5 4-8-5 4-8-5 4-8-6
5-1-1 5-1-1 5-1-1 5-1-2
•
•
• viii Table of Contenls
Paragraph 5-1-5. ECM/ECCMACTIVITY . 5-1-6. SERVICE UMITATIONS . 5-1-7. ELECTRONIC CURSOR . 5-1-8. MERGING TARGET PROCEDURES . 5-1-9. HOLDING PATTERN SURVEILLANCE · 5-1-10. DEVIATION ADVISORIES ···· 5-1-11. RADAR FIX POSTING . 5-1-12. POSITION REPORTING . 5-1-13. RADAR SERVICE TERMINATION ..
Section 2. Beacon Systems
5-2-1. ASSIGNMENT CRITERIA · .. 5-2-2. DISCRETE ENVIRONMENT . 5-2-3. NONDISCRETE ENVIRONMENT . 5-2-4. MIXED ENVIRONMENT . 5-2-5. RADAR BEACON CODE CHANGES . 5-2-6. FUNCTION CODE ASSIGNMENTS . 5-2-7. EMERGENCY CODE ASSIGNMENT . 5-2-8. RADIO FAILURE . 5-2-9. VFR CODE ASSIGNMENTS . 5-2-10. BEACON CODE FOR PRESSURE SUIT FLIGHTS AND FLIGHTS ABOVE FL 600 . 5-2-11. AIR DEFENSE EXERCISE BEACON CODE ASSIGNMENT . 5-2-12. STANDBY OR LOW SENSITIVITY OPERATION . 5-2-13. CODE MONITOR . 5-2-14. FAILURE TO DISPLAY ASSIGNED BEACON CODE OR INOPERATIVE/MALFUNCTIONING TRANSPONDER . 5-2-15. INOPERATIVE OR MALFUNCTIONING INTERROGATOR . 5-2-16. FAILED TRANSPONDER IN CLASS A AIRSPACE . 5-2-17. VALIDATION OF MODE C READOUT . 5-2-18. ALTITUDE CONFIRMATION- MODE C . 5-2-19. ALTITUDE CONFIRMATION-NON-MODE C . 5-2-20. AUTOMATIC ALTITUDE REPORTING . 5-2-21. INFUGHT DEVIATIONS FROM TRANSPONDER/MODE C REQUIREMENTS BETWEEN 10,000FEET AND 18,000FEET . 5-2-22. BEACON TERMINATION . 5-2-23. ALTITUDE FILTERS .
Section 3. Radar Identification
5-3-1. APPLICATION . 5-3-2. PRIMARY RADAR IDENTIFICATION METHODS . 5-3-3. BEACON IDENTIFICATION METHODS . 5-3-4. TERMINAL AUTOMATION SYSTEMS IDENTIFICATION METHODS .. 5-3-5. QUESTIONABLE IDENTIFICATION . 5-3-6. POSITION INFORMATION . 5-3-7. IDENTIFICATION STATUS . 5-3-8. TARGET MARKERS . 5-3-9. TARGET MARKERS .
Table of Contents
Page 5-1-2 5-1-3 5-1-3 5-1-3 5-1-3 5-1-4 5-1-4 5-1-4 5-1-4
5-2-1 5-2-1 5-2-1 5-2-1 5-2-2 5-2-2 5-2-3 5-2-3 5-2-3
5-2-4 5-2-4 5-2-5 5-2-5
5-2-5 5-2-6 5-2-6 5-2-6 5-2-7 5-2-7 5-2-7
5-2-8 5-2-8 5-2-8
5-3-1 5-3-1 5-3-1 5-3-2 5-3-2 5-3-2 5-3-2 5-3-3 5-3-3
ix
Section 4. Transfer ofRadar Identification
Paragraph 5-4-1. APPLICATION . 5-4-2. TERMS . 5-4-3. METHODS , . 5-4-4. TRAFFIC . 5-4-5. TRANSFERRINGCONTROLLERHANDOFF . 5-4-6. RECEIVING CONTROLLER HANDOFF . 5-4-7. POINT OUT . 5-4-8. AUTOMATED INFORMATION TRANSFER (AIT) . 5-4-9. INTERFACILITY AUTOMATED INFORMATION TRANSFER . 5-4-10. PREARRANGED COORDINATION .
Section 5. Radar Separation
5-5-1. APPLICATION . 5-5-2. TARGET SEPARATION . 5-5-3. TARGET RESOLUTION . 5-5-4. MINIMA . 5-5-5. VERTICAL APPLICATION . 5-5-6. EXCEPTIONS . 5-5-7. PASSING OR DIVERGING . 5-5-8. ADDITIONAL SEPARATION FOR FORMATION FLIGHTS . 5-5-9. SEPARATION FROM OBSTRUCTIONS . 5-5-IO. ADJACENT AIRSPACE . 5-5-11. EDGE OF SCOPE . 5-5-12. BEACON TARGET DISPLACEMENT . 5-5-13. GPAI02/103 CORRECTIONFACTOR .
Section 6. Vectoring
5-6-1. APPLICATION . 5-6-2. METHODS . 5-6-3. VECTORS BELOW MINIMUM ALTITUDE .
Section 7. Speed Adjustment
5-7-1. APPLICATION .. 5-7-2. METHODS . 5-7-3. MINIMA . 5-7-4. TERMINATION .
Section 8. Radar Departures
5-8-1. PROCEDURES . 5-8-2. INITIAL HEADING . 5-8-3. SUCCESSIVE OR SIMULTANEOUS DEPARTURES . 5-8-4. DEPARTUREANDARRIVAL . 5-8-5. DEPARTURES AND ARRIVALS ON PARALLEL OR NONINTERSECTING DIVERGING RUNWAYS .
Page 5-4-1 5-4-1 5-4-1 5-4-2 5-4-2 5-4-3 5-4-4 5-4-5 5-4-5 5-4-5
5-5-1 5-5-1 5-5-1 5-5-2 5-5-3 5-5-3 5-5-4 5-5-4 5-5-5 5-5-5 5-5-5 5-5-5 5-5-6
5-6-1 5-6-1 5-6-2
5-7-1 5-7-2 5-7-3 5-7-3
5-8-1 5-8-1 5-8-1 5-8-3
5-8-3
•
• x Table of Contents
Section 9. Radar Arrivals
Paragraph 5-9-1. VECTORS TO FINAL APPROACH COURSE . 5-9-2. FINAL APPROACH COURSE INTERCEPTION . 5-9-3. VECTORS ACROSS FINAL APPROACH COURSE . 5-9-4. ARRIVAL INSTRUCTIONS . 5-9-5. APPROACH SEPARATIONRESPONSIBILITY . 5-9-6. PARAUELDEPENDENTILS/MLSAPPROACHES ., . 5-9-7. SIMULTANEOUS INDEPENDENT ILS/MLS APPROACHES- DUAL & TRIPLE . 5-9-8. SIMULTANEOUS INDEPENDENT DUAL ILS/MLS APPROACHESmGH UPDATE RADAR .
Section 10. Radar Approaches- Terminal
5-10-1. APPLICATION ·············· 5-10-2. APPROACH INFORMATION . 5-10-3. NO-GYRO APPROACH . 5-10-4. LOST COMMUNICATIONS . 5-10-5. RADAR CONTACT LOST . 5-10-6. LANDING CHECK . 5-10-7. POSITION INFORMATION . 5-10-8. FINAL CONTROLLER CHANGEOVER . 5-10-9. COMMUNICATIONS CHECK . 5-10-10. TRANSMISSION ACKNOWLEDGMENT . 5-10-11. MISSED APPROACH . 5-10-12. LOW APPROACH AND TOUCH-AND-GO . 5-10-13. TOWER CLEARANCE · .. · 5-10-14. FINAL APPROACH ABNORMALITIES . 5-10-15. MILITARY SINGLE FREQUENCY APPROACHES .
Section 11. Surveillance Approaches- Terminal
5-11-1. ALTITUDE INFORMATION . 5-11-2. VISUAL REFERENCE REPORT . 5-11-3. DESCENT NOTIFICATION . 5-11-4. DESCENT INSTRUCTIONS . 5-11-5. FINALAPPROACHGUIDANCE .. 5-11-6. APPROACH GUIDANCE TERMINATION .
Section 12. PAR Approaches- 'Ierminal
5-12-1. GLIDEPATHNOTIFICATION .. 5-12-2. DECISION HEIGHT (DH) NOTIFICATION . 5-12-3. DESCENT INSTRUCTION . 5-12-4. GLIDEPATHANDCOURSEINFORMATION . 5-12-5. DISTANCE FROM TOUCHDOWN . 5-12-6. DECISION HEIGHT . 5-12-7. POSITION ADVISORIES . 5-12-8. APPROACH GUIDANCE TERMINATION . 5-12-9. COMMUNICATION TRANSFER .
Table of Contents
Page 5-9-1 5-9-1 5-9-2 5-9-2 5-9-5 5-9-5
5-9-8
5-9-9
5-10-1 5-10-1 5-10-2 5-10-2 5-10-3 5-10-3 5-10-3 5-10-3 5-10-4 5-10-4 5-10-4 5-10-4 5-10-4 5-10-5 5-10-5
5-11-1 5-11-1 5-11-1 5-11-1 5-11-2 5-11-2
5-12-1 5-12-1 5-12-1 5-12-1 5-12-1 5-12-1 5-12-1 5-12-2 5-12-2
xi
Table of Contents › Chapter 6. Nonradar
Paragraph 5-12-10. ELEVATIONFAlLURE . 5-12-11. SURVEILLANCE UNUSABLE .
Section 13. Use of PAR for Approach Monitoring- Terminal
5-13-1. MONITOR ON PAR EQUIPMENT . 5-13-2. MONITOR AVAlLABILITY . 5-13-3. MONITOR INFORMATION .
Section 14. Automation- En Route
5-14-1. CONFLICT ALERT (CA) AND MODE C INTRUDER (MCI) ALERT . 5-14-2. EN ROUTE MINIMUM SAFE ALTITUDE WARNING (E-MSAW) . 5-14-3. COMPUTER ENTRY OF ASSIGNED ALTITUDE . 5-14-4. ENTRY OF REPORTED ALTITUDE . 5-14-5. SELECTED ALTITUDE LIMITS . 5-14-6. SECTOR ELIGIBILITY . 5-14-7. COASTTRACKS . 5-14-8. CONTROLLER INITIATED COAST TRACKS .
Section 15. Automated Radar Terminal
Systems (ARTS)- Terminal
5-15-1. APPLICATION . 5-15-2. RESPONSIBILITy . 5-15-3. FUNCTIONAL USE . 5-15-4. SYSTEM REQUIREMENTS . 5-15-5. INFORMATION DISPLAYED . 5-15-6. CA/MCI . 5-15-7. INHIBITING MINIMUM SAFE ALTITUDE WARNING (MSAW) . 5-15-8. TRACK SUSPEND FUNCTION .
Section 16. TPX-42- Terminal
5-16-1. APPLICATION . 5-16-2. RESPONSIBILITy . 5-16-3. FUNCTIONAL USE . 5-16-4. SYSTEM REQUIREMENTS . 5-16-5. INFORMATION DISPLAYED . 5-16-6. INHIBITING LOW ALTITUDE ALERT SYSTEM (LAAS) .
Chapter 6. Nonradar
Section 1. General
6-1-1. DISTANCE . 6-1-2. NONRECEIPT OF POSITION REPORT . 6-1-3. DUPLICATE POSITION REPORTS . 6-1-4. ADJACENT AlRPORT OPERATION . 6-1-5. ARRIVAL MINIMA .
Page 5-12-2 5-12-3
5-13-1 5-13-1 5-13-1
5-14-1 5-14-1 5-14-2 5-14-2 5-14-2 5-14-2 5-14-2 5-14-3
5-15-1 5-15-1 5-15-1 5-15-1 5-15-1 5-15-2 5-15-2 5-15-2
5-16-1 5-16-1 5-16-1 5-16-1 5-16-1 5-16-1
6-1-1 6-1-1 6-1-1 6-1-1 6-1-1
•
•
• xii Table of Contents
Section 2. Initial Separation of Successive
Departing Aircraft
Paragraph 6-2-1. MINIMA ON DIVERGING COURSES . 6-2-2. MINIMA ON SAME COURSE .
Section 3. Initial Separation of Departing
and Arriving Aircraft
6-3-1. SEPARATION MINIMA .
Section 4. Longitudinal Separation
6-4-1. APPUCATION . 6-4-2. MINIMA ON SAME, CONVERGING, OR CROSSING COURSES . 6-4-3. MINIMA ON OPPOSITE COURSES . 6-4-4. SEPARATION BY PILOTS . 6-4-5. RNAV AIRCRAFr ALONG VOR AIRWAYSjROUTES .
Section 5. Lateral Separation
6-5-1. SEPARPJIONMETHODS . 6-5-2. MINIMA ON DIVERGING RADIALS . 6-5-3. DME ARC MINIMA . 6-5-4. MINIMA ALONG OTHER THAN ESTABUSHED AIRWAYS OR ROUTES . 6-5-5. RNAV MINIMA- DIVERGING/CROSSING COURSES .
Section 6. Vertical Separation
6-6-1. APPUCATION . 6-6-2. EXCEPTIONS . 6-6-3. SEPARATION BY PILOTS .
Section 7. Timed Approaches
6-7-1. APPUCATION . 6-7-2. APPROACH SEQUENCE . 6-7-3. SEQUENCE INTERRUPTION . 6-7-4. LEVEL FUGHT RESTRICTION . 6-7-5. INTERVAL MINIMA . 6-7-6. TIME CHECK . 6-7-7. MISSED APPROACHES .
Table of Contents
711O.65P
Page 6-2-1 6-2-3
6-3-1
6-4-1 6-4-1 6-4-5 6-4-6 6-4-6
6-5-1 6-5-1 6-5-2
6-5-2 6-5-4
6-6-1 6-6-1 6-6-1
6-7-1 6-7-1 6-7-2 6-7-2 6-7-2 6-7-2 6-7-2
xiii
Table of Contents › Chapter 7. Visual
Chapter 7. Visual
Section 1. General
Paragraph 7-1-1. CLASSA AIRSPACE RESTRICTIONS . 7-1-2. VFRCONDITIONS . 7-1-3. APPROACH CONTROL SERVICE FOR VFRARRIVINGAIRCRAFT . 7-1-4. VISUAL HOLDING OF VFR AIRCRAFT .
Section 2. Visual Separation
7-2-1. VISUAL SEPARATION .
Section 3. VFR-on-Top
7-3-1. VFR-ON-TOP . 7-3-2. ALTITUDE FOR DIRECTION OF FUGHT .
Section 4. Approaches
7-4-1. VISUAL APPROACH . 7-4-2. VECTORS FOR VISUAL APPROACH . 7-4-3. CLEARANCE FOR VISUAL APPROACH . 7-4-4. APPROACHES TO MULTIPLE RUNWAYS . 7-4-5. CHARTED VISUAL FLIGHT PROCEDURES (CVFP). USNUSN NOT APPUCABLE . 7-4-6. CONTACT APPROACH .
Section 5. Special VFR (SVFR)
7-5-1. AUTHORIZATION . 7-5-2. PRIORITy . 7-5-3. SEPARATION . 7-5-4. ALTITUDE ASSIGNMENT . 7-5-5. LOCAL OPERATIONS . 7-5-6. CUMBTOVFR . 7-5-7. GROUND VISIBIUTY BELOW ONE MILE . 7-5-8. FLIGHT VISIBIUTY BELOW ONE MILE .
Section 6. Basic Radar Service
to VFR Aircraft- Terminal
7-6-1. APPUCATION . 7-6-2. SERVICEAVAILABIUTY .. 7-6-3. INITIAL CONTACT . 7-6-4. IDENTIFICATION . 7-6-5. HOLDING . 7-6-6. APPROACH SEQUENCE .. 7-6-7. SEQUENCING . 7-6-8. CONTROL TRANSFER .. 7-6-9. ABANDONEDAPPROACH .
Page 7-1-1 7-1-1 7-1-1 7-1-1
7-2-1
7-3-1 7-3-1
7-4-1 7-4-1 7-4-1 7-4-2
7-4-3 7-4-3
7-5-1 7-5-1 7-5-2 7-5-2 7-5-2 7-5-3 7-5-3 7-5-3
7-6-1 7-6-1 7-6-1 7-6-1 7-6-1 7-6-1 7-6-1 7-6-2 7-6-2
•
xiv Table of Contents
Table of Contents › Chapter 8. Offshore/Oceanic Procedures
Paragraph 7-6-10. VFRDEPARTUREINFORMATION . 7-6-11. TERMINATION OF SERVICE . 7-6-12. SERVICE PROVIDED WHEN TOWER IS INOPERATIVE .
Section 7. Terminal Radar Service
Area (TRSA)- Terminal
7-7-1. APPLICATION . 7-7-2. ISSUANCEOFEFC . 7-7-3. SEPARATION . 7-7-4. HELICOPTER TRAFFIC . 7- 7-5. ALTITUDE ASSIGNMENTS . 7-7-6. APPROACH INTERVAL . 7-7-7. TRSADEPARTUREINFORMATION .
Section 8. Class C Service- Terminal
7-8-1. APPLICATION . 7- 8-2. CLASS C SERVICES . 7-8-3. SEPARATION . 7-8-4. ESTABLISHING TWO-WAYCOMMUNICATIONS . 7-8-5. ALTITUDE ASSIGNMENTS . 7-8-6. EXCEPTIONS . 7-8-7. ADJACENT AIRPORT OPERATIONS . 7-8-8. TERMINATION OF SERVICE .
Section 9. Class B Service Area- Terminal
7-9-1. APPLICATION . 7-9-2. VFRAIRCRAFTINCLASSBAIRSPACE . 7-9-3. METHODS . 7-9-4. SEPARATION . 7-9-5. TRAFFIC ADVISORIES . 7-9-6. HELICOPTER TRAFFIC . 7-9-7. ALTITUDE ASSIGNMENTS . 7-9-8. APPROACH INTERVAL .
Chapter 8. Offshore/Oceanic Procedures
Section 1. General
8-1-1. ATCSERVICE . 8-1-2. OPERATIONS IN OFFSHORE AIRSPACE AREAS . 8-1-3. VFRFLIGHTPLANS . 8-1-4. TYPES OF SEPARATION . 8-1-5. ALTIMETER SETTING . 8-1-6. RECEIPT OF POSITION REPORTS . 8-1-7. OCEANIC NAVIGATIONAL ERROR REPORTING (ONER) PROCEDURES . 8-1-8. USE OF CONTROL ESTIMATES .
Table of Contents
Page 7-6-2 7-6-2 7-6-3
7-7-1 7-7-1 7-7-1 7-7-1 7-7-1 7-7-1 7-7-1
7-8-1 7-8-1 7-8-1 7-8-1 7-8-1 7-8-2 7-8-2 7-8-2
7-9-1 7-9-1 7-9-1 7-9-2 7-9-2 7-9-2 7-9-2 7-9-2
8-1-1 8-1-1 8-1-1 8-1-1 8-1-1 8-1-1
8-1-1 8-1-1
xv
Section 2. Coordination
Paragraph 8-2-1. GENERAL . 8-2-2. TRANSFER OF CONTROL AND COMMUNICATIONS . 8-2-3. AIR TRAFFIC SERVICES INTERFACIUTY DATACOMMUNICATIONS (AIDC) .
Section 3. Longitudinal Separation
8-3-1. APPUCATION . 8-3-2. SEPARATION METHODS . 8-3-3. MACH NUMBER TECHNIQUE .
Section 4. Lateral Separation
8-4-1. APPUCATION . 8-4-2. SEPARATION METHODS . 8-4-3. REDUCTION OF ROUTE PROTECTED AIRSPACE . 8-4-4. TRACK SEPARATION .
Section 5. Offshore/Oceanic Transition
Procedures
8-5-1. ALTITUDE/FLIGHT LEVEL TRANSITION . 8-5-2. COURSE DIVERGENCE . 8-5-3. OPPOSITE DIRECTION . 8-5-4. SAME DIRECTION .
Section 6. Separation from Airspace Reservations
8-6-1. TEMPORARY STATIONARYAIRSPACE RESERVATIONS . 8-6-2. REFUSAL OF AVOIDANCE CLEARANCE . 8-6-3. TEMPORARY MOVING AIRSPACE RESERVATIONS .
Section 7. North Atlantic ICAO Region
8-7-1. APPUCATION . 8-7-2. VERTICAL SEPARATION . 8-7-3. LONGITUDINAL SEPARATION . 8-7-4. LATERALSEPARATION . 8-7-5. PROCEDURES FOR WEATHER DEVIATIONS IN NORTH ATLANTIC (NAT) AIRSPACE .
Section 8. Caribbean ICAO Region
8-8-1. APPUCATION . 8-8-2. VERTICAL SEPARATION . 8-8-3. LONGITUDINAL SEPARATION . 8-8-4. LATERAL SEPARATION . 8-8-5. VFR CUMB AND DESCENT .
Page 8-2-1 8-2-1
8-2-1
8-3-1 8-3-1 8-3-2
8-4-1 8-4-1 8-4-3 8-4-4
8-5-1 8-5-1 8-5-1 8-5-2
8-6-1 8-6-1 8-6-1
8-7-1 8-7-1 8-7-1 8-7-2
8-7-3
8-8-1 8-8-1 8-8-1 8-8-3 8-8-3
•
• xvi Table of Contents
Table of Contents › Chapter 9. Special Flights
Section 9. Pacific ICAO Region
Paragraph 8-9-1. APPLICATION . 8-9-2. VERTICAL SEPARATION . 8-9-3. LONGITUDINAL SEPARATION . 8-9-4. LATERAL SEPARATION . 8-9-5. COMPOSITE SEPARATION MINIMA . 8-9-6. COMPOSITE SEPARATION ALTITUDE ASSIGNMENT . 8-9-7. COMPOSITE SEPARATION APPLICATION . 8-9-8. VFR CLIMB AND DESCENT . 8-9-9. PROCEDURES FOR WEATHER DEVIATIONS AND OTHER CONTINGENCIES IN OCEANIC CONTROLLED AIRSPACE .
Section 10. North American
ICAO Region- Arctic CTA
8-10-1. APPLICATION . 8-10-2. VERTICAL SEPARATION . 8-10-3. LONGITUDINAL SEPARATION . 8-10-4. LATERAL SEPARATION .
Chapter 9. Special Flights
Section 1. General
9-1-1. GENERAL . 9-1-2. SPECIALHANDLING . 9-1-3. FLIGHT CHECK AIRCRAFT .
Section 2. Special Interest Flights
9-2-1. GENERAL . 9-2-2. APPLICATION . 9-2-3. EMERGENCY OR UNSCHEDULED LANDINGS .
Section 3. Special Operations
9-3-1. AIRCRAFT CARRYING DANGEROUS MATERIALS . 9-3-2. CELESTIAL NAVIGATION TRAINING . 9-3-3. DEPARTMENT OF ENERGY (DOE) SPECIAL FLIGHTS . 9-3-4. EXPERIMENTAL AIRCRAFT OPERATIONS . 9-3-5. FAA RESEARCH AND DEVELOPMENT FLIGHTS . 9-3-6. FLYNET . 9-3-7. IFR MILITARY TRAINING ROUTES . 9-3-8. INTERCEPTOR OPERATIONS " 9-3-9. SPECIAL INTEREST SITES . 9-3-10. LAW ENFORCEMENT OPERATIONS BY CIVIL AND MILITARY ORGANIZATIONS . 9-3-11. MILITARY AERIAL REFUELING . 9-3-12. MILITARY OPERATIONS ABOVE FL600 . 9-3-13. MILITARY SPECIAL USE FREQUENCIES . 9-3-14. AVOIDANCE OF AREAS OF NUCLEAR RADIATION .
Table of Contents
711O.65P
Page 8-9-1 8-9-1 8-9-1 8-9-1 8-9-1 8-9-1 8-9-2 8-9-2
8-9-3
8-10-1 8-10-1 8-10-1 8-10-1
9-1-1 9-1-1 9-1-1
9-2-1 9-2-1 9-2-2
9-3-1 9-3-1 9-3-1 9-3-2 9-3-2 9-3-2 9-3-2 9-3-4 9-3-4
9-3-4 9-3-5 9-3-6 9-3-7 9-3-7
xvii
Table of Contents › Chapter 10. Emergencies
Paragraph 9-3-15. SAMP . 9-3-16. AWACS/NORAD SPECIAL FLIGHTS . 9-3-17. WEATHER RECONNAISSANCE FLIGHTS . 9-3-18. EVASIVE ACTION MANEUVER . 9-3-19. NONSTANDARD FORMATION/CELL OPERATIONS . 9-3-20. OPEN SKIES TREATY AIRCRAFT .
Section 4. Special Use and ATe Assigned Airspace
9-4-1. APPLICATION . 9-4-2. SEPARATION MINIMA . 9-4-3. VFR-ON-TOP . 9-4-4. TRANSITING ACTIVE SUNATCAA .
Section 5. Fuel Dumping
9-5-1. INFORMATION REQUIREMENTS . 9-5-2. ROUTING . 9-5-3. ALTITUDE ASSIGNMENT . 9-5-4. SEPARATION MINIMA . 9-5-5. INFORMATION DISSEMINATION .
Section 6. Jettisoning of External Stores
9-6-1. JETTISONING OF EXTERNAL STORES .
Section 7. Unmanned Free Balloons
9-7-1. APPLICATION . 9-7-2. DERELICT BALLOONS .
Section 8. Parachute Operations
9-8-1. COORDINATION . 9-8-2. CLASS A, CLASS B, AND CLASS C AIRSPACE . 9-8-3. CLASS D AIRSPACE . 9-8-4. OTHER CONTROL AIRSPACE .
Section 9. Unidentified Flying Object (UFO) Reports
9-9-1. GENERAL .
Chapter 10. Emergencies
Section 1. General
10-1-1. EMERGENCY DETERMINATIONS . 10-1-2. OBTAINING INFORMATION . 10-1-3. PROVIDING ASSISTANCE . 10-1-4. RESPONSIBILITy .
Page 9-3-7 9-3-7 9-3-8 9-3-8 9-3-9 9-3-9
9-4-1 9-4-1 9-4-1 9-4-2
9-5-1 9-5-1 9-5-1 9-5-1 9-5-1
9-6-1
9-7-1 9-7-2
9-8-1 9-8-1 9-8-1 9-8-1
9-9-1
10-1-1 10-1-1 10-1-1 10-1-1
•
•
•
xviii Table of Contents
Paragraph 10-1-5. COORDINATION . 10-1-6. AIRPORT GROUND EMERGENCy . 10-1-7. INFUGHT EMERGENCIES INVOLVING MIUTARY FIGHTER-TYPE AIRCRAFT .
Section 2. Emergency Assistance
10-2-1. INFORMATION REQUIREMENTS . 10-2-2. FREQUENCY CHANGES . 10-2-3. AIRCRAFT ORIENTATION . 10-2-4. ALTITUDE CHANGE FOR IMPROVED RECEPTION . 10-2-5. EMERGENCY SITUATIONS . 10-2-6. HIJACKED AIRCRAFT . 10-2-7. VFRAIRCRAFTINWEATHERDIFFICULTY . 10-2-8. RADAR ASSISTANCE TO VFR AIRCRAFT IN WEATHER DIFFICULTY 10-2-9. RADAR ASSISTANCE TECHNIQUES . 10-2-10. EMERGENCY LOCATOR TRANSMITTER (ELT) SIGNALS . 10-2-11. AIRCRAFT BOMB THREATS . 10-2-12. EXPLOSIVEDETECTIONK-9TEAMS . 10-2-13. EMERGENCY AIRPORT RECOMMENDATION . 10-2-14. GUIDANCE TO EMERGENCY AIRPORT . 10-2-15. EMERGENCY OBSTRUCTION VIDEO MAP (EOVM) . 10-2-16. VOLCANICASH .
Section 3. Overdue Aircraft
10-3-1. OVERDUE AIRCRAFT . 10-3-2. INFORMATION TO BE FORWARDED TO ARTCC . 10-3-3. INFORMATION TO BE FORWARDED TO RCC . 10-3-4. ALNOT . 10-3-5. RESPONSIBIUTY TRANSFER TO RCC . 10-3-6. AIRCRAFT POSITION PLOTS . 10-3-7. ALNOT CANCELLATION .
Section 4. Control Actions
10-4-1. TRAFFIC RESTRICTIONS . 10-4-2. LIGHTING REQUIREMENTS . 10-4-3. TRAFFIC RESUMPTION . 10-4-4. COMMUNICATIONS FAILURE .
Section 5. Miscellaneous Operations
10-5-1. NAVY FLEET SUPPORT MISSIONS . 10-5-2. EXPLOSIVE CARGO .
Section 6. Oceanic EmergencyProcedures
10-6-1. APPLICATION . 10-6-2. PHASES OF EMERGENCY . 10-6-3. ALERTING SERVICE AND SPECIAL ASSISTANCE .
Table of Contents
Page 10-1-2 10-1-2
10-1-2
10-2-1 10-2-1 10-2-1 10-2-1 10-2-1 10-2-2 10-2-2 10-2-3 10-2-3 10-2-3 10-2-4 10-2-5 10-2-6 10-2-6 10-2-6 10-2-6
10-3-1 10-3-1 10-3-1 10-3-2 10-3-2 10-3-2 10-3-2
10-4-1 10-4-1 10-4-1 10-4-1
10-5-1 10-5-1
10-6-1 10-6-1 10-6-1
xix
Table of Contents › Chapter 13. Decision Support Tools
711O.65P
Paragraph 10-6-4. INFLIGHT CONTINGENCIES . 10-6-5. SERVICES TO RESCUE AIRCRAFT .
Section 7. Ground Missile Emergencies
10-7-1. INFORMATION RELAY . 10-7-2. IFR AND SVFRMINIMA . 10-7-3. VFRMINIMA . 10-7-4. SMOKE COLUMN AVOIDANCE . 10-7-5. EXTENDED NOTIFICATION .
Chapter 11. Traffic Management Procedures
Section 1. General
11-1-1. DUTY RESPONSIBILITy . 11-1-2. DUTIES AND RESPONSIBILITIES .
Chapter 12. Canadian Airspace Procedures
Section 1. General Control
12-1-1. APPLICATION . 12-1-2. AIRSPACE CLASSIFICATION . 12-1-3. ONE THOUSAND-ON-TOP . 12-1-4. SEPARATION . 12-1-5. DEPARTURE CLEARANCE/COMMUNICATION FAILURE . 12-1-6. PARACHUTE JUMPING . 12-1-7. SPECIAL VFR (SVFR) .
Chapter 13. Decision Support Tools Section 1. User Request Evaluation Tool (URET) - En Route
13-1-1. DESCRIPTION . 13-1-2. CONFLICT DETECTION AND RESOLUTION . 13-1-3. TRIAL PLANNING . 13-1-4. URET-BASED CLEARANCES . 13-1-5. THE AIRCRAFT LIST (ACL) AND FLIGHT DATAMANAGEMENT . 13-1-6. RECORDING OF CONTROL DATA . 13-1-7. ACKNOWLEDGEMENT OF AUTOMATED NOTIFICATION . 13-1-8. CURRENCY OF TRAJECTORY INFORMATION . 13-1-9. DELAYREPORTING . 13-1-10. OVERDUE AIRCRAFT . 13-1-11. USE OF GRAPIDCS PLAN DISPLAY (GPD) . 13-1-12. FORECAST WINDS . 13-1-13. INTERFACILITYCONNECTIVITY . 13-1-14. HOST OUTAGES .
Page 10-6-2 10-6-3
10-7-1 10-7-1 10-7-1 10-7-1 10-7-1
11-1-1 11-1-1
12-1-1 12-1-1 12-1-1 12-1-1 12-1-2 12-1-2 12-1-2
13-1-1 13-1-1 13-1-1 13-1-1 13-1-2 13-1-2 13-1-2 13-1-2 13-1-2 13-1-3 13-1-3 13-1-3 13-1-3 13-1-3
•
•
xx Table of Contents
Table of Contents › Appendices
Section 2. Ocean21 - Oceanic
Paragraph 13-2-1. DESCRIPTION . 13-2-2. CONFLICT DETECTION AND RESOLUTION . 13-2-3. INFORMATION MANAGEMENT . 13-2-4. CONTROLLER PILOT DATALINK COMMUNICATIONS (CPDLC) . 13-2-5. COORDINATION . 13-2-6. TEAM RESPONSIBILITIES - MULTIPLE PERSON OPERATION .
Appendices
APPENDIX A. AIRCRAFT INFORMATION . APPENDIX B. AIRCRAFT INFORMATION HELICOPTERS/ROTORCRAFTS . APPENDIX C. AIRCRAFT INFORMATION SPECIFIC
HOMEBUILT/EXPERIMENTAL AIRCRAFT . APPENDIX D. STANDARD OPERATING PRACTICE (SOP) FOR THE
TRANSFER OF POSITION RESPONS1BILlTY .
PILOT/CONTROLLER GLOSSARY . INDEX . OFFICES OF PRIMARY INTEREST .
Table of Contents
711O.65P
Page 13-2-1 13-2-1 13-2-2 13-2-3 13-2-4 13-2-4
A-I B-1
C-l
D-l
PCG-1 I-I OPI-l
xxi
Section 1. General › 1-1-7. PUBLICATION AND DELIVERY DATES
Chapter 1. Introduction
Section 1. General
711O.65P
1-1-1. PURPOSE
This order prescribes air traffic control procedures and phraseology for use by persons providing air traffic control services. Controllers are required tobe familiar with the provisions of this order that pertain to their operational responsibilities and to exercise their best judgment if they encounter situations that are not covered by it.
1-1-2. DISTRIBUTION
This order is distributed to selected offices in Washington Headquarters, Regional Offices, the Technical Center, and the Aeronautical Center. Also, copies are sent to all air traffic control facilities, all international aviation field offices, and the interested aviation public.
1-1-3. CANCELLATION
FAA Order 711O.65N, Air Traffic Control, dated February 21, 2002, and all changes to it are canceled.
1-1-4. EXPLANATION OF MAJOR CHANGES
The significant changes to this order are identified in the Explanation of Changes pagers).It is advisable to retain the pagers) throughoutthe duration of the basic order. If further information is desired, direct questions through the appropriatefacility/region staff to the office shown in parentheses following the change.
1-1-5. EFFECTIVE DATE
• This order is effective February 19,2004.
1-1-6. RECOMMENDATIONS FOR PROCEDURAL CHANGES
a. Personnel should submit recommended changes in procedures to facility management.
General
b. Recommendations from other sources should be submitted through appropriate FAA, military, or industry/user channels to Headquarters, FAA, Director ofAir Traffic, AAT-1, attention: ATP-I00.
1-1-7. PUBLICATION AND DELIVERY DATES
a. This order and its changes are scheduled to be published according to TBL 1-1-1.
TBL 1-1-1 Publications Timetable
Basic or Cutoff Date for EffectiveDate Change Submission of Publication 7110.65P Basic 8n/03 2/19/04 Change 1 2/19/04 8/5/04 Change 2 8/5/04 2/17/05 Change3 2/17/05 8/4/05 7110.65R Basic 8/4/05 2/16106
b. If an FAA facility has not received the order/changes at least 30 days before the above effective dates, the facility shall notify its regional distribution officer.
c. If a military facility has not received the order/changes at least 30 days before the above effective dates, the facility shall notify its appropriate military headquarters. (See TBL 1-1-2.)
TBLI-I-2 Military Distribution Contacts
Military DSN Commercial Headquarters U.S.Army 656-4868 (703)806-4868 USAASA U.S.Air Force Contact Local•NIMA CustomerAccount Representative U.S.Navy 224-2710 (703)614-2710 CNO(N885F)
*NIMA-National Imagery andMapping Agency
Section 1. General › 1-1-9. CONSTRAINTS GOVERNING SUPPLEMENTS AND PROCEDURAL DEVIATIONS
1-1-8. PROCEDURAL LEITERS OF AGREEMENT
Procedures/minima which are applied jointly or otherwise require the cooperation or concurrence of more than one facility/organization must be documented in a letter ofagreement. Letters ofagreement only supplement this order. Any minima they specify must not be less than that specified herein unless appropriatemilitary authorityhas authorizedapplication of reduced separation between military aircraft.
REFERENCE- FAAO7110.65,A1L Service, Para 2-1-1. FAAO7210.3, Letters o/Agreement, Para 4-3-1.
1-1-9. CONSTRAINTS GOVERNING SUPPLEMENTS AND PROCEDURAL DEVIATIONS
a. Exceptional or unusual requirements may dictate procedural deviations or supplementary procedures to this order. Prior to implementing supplemental or any procedural deviation that alters the level, quality, or degree of service, obtain prior approval from the Director of Air Traffic, AAT-l.
b. Ifmilitary operations or facilities are involved, prior approval by the following appropriate headquarters is required for subsequent interface with FAA. (See TBL 1-1-3.)
TBL 1-1-3 Military Operations Interface Offices
Branch Address U.S.Navy CNO Officeof the Chiefof Naval Operations (N885F) 2000 The Pentagoo Washington,D.C. 20350-2000 U.S.Air Force HQAFFSNXA 1535 Command Drive Suite0302 AndrewsAFB,MD20762-7002 U.S.Array Director USAASA (MOAS-AS) 9325 Gunston Road, Suite N319 Ft. Belvoir, VA 22060-5582
NOTE-
Terminal: Headquarters USAF has delegated to MajorAir Command, Directors of Operations (MAJCOMIDOs) authority to reduce same runway separation standards for military aircraft. These are specified and approved by affected ATC and user units. When applied, appropriate advisoriesmay be required; e.g., "(AIC call sign) continue straightaheadon right side; F-16 landingbehind on left. "
"(AIC call sign) holdposition on right side; F-5 behindon left."
REFERENCE- FAAO 7110.65, UseofActive Runways, Para 3-1-3.
General •
Section 2. Terms of Reference › 1-2-1. WORD MEANINGS
Section 2. Terms of Reference
711O.65P
1-2-1. WORD MEANINGS
As used in this manual:
a. Shall, or an action verb in the imperative sense, means a procedure is mandatory.
EXAMPLE-
The transferring controller shall forward this data to the receiving controller.
Issue an alternative clearance.
Authorize the aircraft to taxi.
Do not clear an aircraft to land on or takeoff from a closed
runway.
b. Should means a procedure is recommended.
c. Mayor need not means a procedure is optional.
d. Will means futurity, not a requirement for the application of a procedure.
e. Singular words include the plural.
f. Plural words include the singular.
g. Aircraft means the airframe, crew members, or both.
h. Approved separation means separation in accordance with the applicable minima in this manual.
l, Altitude means indicated altitude mean sea level (MSL), flight level (FL), or both.
j. Miles means nautical miles unless otherwise specified, and means statute miles in conjunction with visibility.
k. Course, bearing, azimuth, heading, and wind direction information shall always be magnetic unless specifically stated otherwise.
I. Time when used for ATC operational activities, is the hour and the minute in Coordinated Universal Time (UTC). Change to thenext minute is made at the minute plus 30 seconds, except time checks aregiven to the nearest quarter minute.
m. Runway means the runway used by aircraft, and in discussions of separation standards is
Terms of Reference
applicable to helipads with accompanying takeoff! landing courses. (See Pilot/Controller Glossary term- Runway.)
n, Flightoperations inaccordancewith theoptions of due regard or operational obligates the authorized state aircraft commander to:
1. Separate his/her aircraft from all other air traffic; and
2. Assure that anappropriate monitoring agency assumes responsibility for search and rescue actions; and
3. Operate under at least one of the following conditions:
(a) In visual meteorological conditions (YMC); or
(b) Within radar surveillance and radio communications of a surface radar facility; or
(c) Be equipped with airborne radar that is sufficient to provide separation between his/her aircraft and any other aircraft he/she may be controlling and other aircraft; or
(d) Operate within Class G airspace.
(e) An understanding between the pilot and controller regarding the intent of the pilot and the slatus of the flight should be arrived at before the aircraft leaves ATC frequency.
NOTE-
1. A pilot's use ofthe phrase "Going Tactical" does not indicate "Due Regard. " An understanding between the pilot and controllerregardingtheintent ofthepilot and the
status ofthe flight should be arrived at before the aircraft leaves air traffic control (ATC)frequency.
2. The above conditions provide for a level of safety equivalent to that normally given by International Civil Aviation Organization (ICAO) ATC agencies and fulfills
U.S. Government obligations under Article 3 of the Chicago Convention of 1944 (Reference (d)), which stipulates there must be "due regard for the safety of navigation of civil aircraft" when flight is not being conducted under ICAO flight procedures.
o, CFR means Code of Federal Regulations.
711O.65P 2/19/04
FIG 1-2-1
Divergence • ~ ~
45° 135°k ~
Crossing
45° Thru 135°
0 +
S P Reference LessThan45° 136° Thru 180° p a 0 180° Course m s e LessThan45° J36° Thru 1800 i Ie
45° Thru 135°
~ ~ - 45° Crossing 135° ~ ~
1-2-2. COURSE DEFINITIONS
Section 2. Terms of Reference › 1-2-3. NOTES
The following definitions shall be used in the application of the separation criteria in this order.
NOTE- The term "protected airspace, I' as used in this paragraph, is the airspace equal to one halfthe required applicable lateral separation on either side of an aircraft along its projected flight path. If the protected airspace of two
aircraft does not overlap, applicable lateral separation is ensured.
a. SAME COURSES are courses whose protected airspaces are coincident, overlap, or intersect and whose angular difference is less than 45 degrees.
(See FIG 1-2-1.)
b. CROSSING COURSES are intersecting courses whose angular difference is 45 through 135 degrees inclusive. (See FIG 1-2-1.)
c. OPPOSITE/RECIPROCAL COURSES are courses whose protected airspaces are coincident, overlap, or intersect and whose angular difference is greater than 135 degrees through 180 degrees inclusive. (See FIG 1-2-1.)
1-2-3. NOTES
Statements of fact, or of a prefatory or explanatory nature relating to directive material, are set forth as notes.
Terms of Reference •
Section 2. Terms of Reference › 1-2-6. ABBREVIATIONS
1-2-4. REFERENCES
As used in this order, references direct attention to an additional or supporting source of information such as FAA, NWS, and other agencies' orders, directives, notices, CFRs, and Advisory Circulars (ACs).
1-2-5. ANNOTATIONS
Revised, reprinted, or new pages are marked as follows:
a. The change number and the effective date are printed on each revised or additional page.
b. A page that does not require a change is reprinted in its original form.
c. Bold vertical lines in the margin of changed pages indicate the locationofsubstantive revisions to the order. Bold vertical lines adjacent to the title of a chapter, section, or paragraph means that extensive changes have been made to that chapter, section, or paragraph.
d. Paragraphs/sections annotated with EN ROUTE or TERMINAL are only to be applied by the
designated type facility. When they are not so designated, the paragraphs/sections apply to both types of facilities (en route and terminal).
e. The annotation, USAF for the U.S. Air Force, USN for the U.S. Navy, and USA for the U.S. Army denotes that the procedure immediatelyfollowing the annotation applies only to the designated service.
REFERENCE· FAAO 7110.65, Military Procedures, Para 2-1-12.
f. WAKE TURBULENCE APPLICATION inserted within a paragraph means that the remaining information in the paragraph requires the application of wake turbulence procedures.
g. The annotation PHRASEOLOGY denotes the prescribed words and/or phrases to be used in
communications.
NOTE- Controllers may, after first using the prescribed phraseology for a specific procedure, rephrase the
message to ensure the content is understood. Good judgement shall be exercised when using nonstandard phraseology.
Terms of Reference
711O.65P
h. The annotationEXAMPLE provides a sample of the way the prescribed phraseology associated with the preceding paragraph(s) will be used. If the precedingparagraph(s) does (do) not include specific prescribed phraseology, the EXAMPLE merely denotes suggested words and/or phrases that may be used in communications.
NOTE- The use of the exact text contained in an example not preceded with specific prescribed phraseology is not mandatory. However, the words and/or phrases are expected, to the extentpractical, to approximate those used in the example.
1-2-6. ABBREVIATIONS
As used in this manual, the following abbreviations have the meanings indicated. (See TBL 1-2-1.)
TBL 1-2-1 FAAOrder 7110.65Abbreviations
Abbreviation Meaning
AAR … Airport acceptance rate
AAT-l … Director of Air Traffic
AC … Advisory Circular
ACC … Area Control Center
ACL … Aircraft list
ACLS … Automatic Carrier Landing System
ADC … Aerospace Defense Command
ADIZ … Air Defense Identification Zone (to be pronounced "AY DIZ")
ADS … Automatic Dependent Surveillance
ADS-A … Automatic Dependent Surveillance Addressable
ADS-B … Automatic Dependent Surveillance Broadcast
AlDC … ATS Interfacility Data Communications
AIM … Aeronautical Information Manual
AlRMET ... Airmen's meteorological information
ALERFA ... Alert phase code (Alerting Service)
ALNOT ... , Alert notice
ALS … Approach Light System
ALTRV … Altitude reservation
AMASS .... Airport Movement Area Safety System
AMB … Ambiguity-A disparity greater than 2 miles
exists between the position declared for a target by ADS and another facility's computer declared position during interfacility handoff
AMVER .... Automated Mutual Assistance Vessel Rescue System
711O.65P
Abbreviation Meaning
ANG … Air NationalGuard
APR … ATe preferred route
ARINC … Aeronautical RadioIncorporated
ARIP … Air refueling initial point
ARS … Air TrafficSystem Requirements Service
ARSR … Air routesurveillance radar
ARTCC … Air Route Traffic Control Center
ARTS … Automated Radar Terminal System
ASD … Aircraft Situation Display
ASDE … Airport surfacedetectionequipment
ASDE-X .. . Airport surface detection equipment - Xray
ASR … Airport surveillance radar
ATA .... - .. Air TrafficAirspaceManagement Program
ATC … Air trafficcontrol
ATCAA ... . ATC assigned airspace
ATCSCC .... Air Traffic Control System Command
Center
ATIS … Automatic Terminal Information Service
ATP … Air TrafficPlanningandProcedures
ATS … AirTraffic Service
ATTS … Automated Terminal Tracking Systems
BASE … Cloud base
CARCAH ... Chief, Aerial Reconnaissance Coordination. All Hurricanes
CARF … Central AltitudeReservation Function
CAT … Clearairturbulence
CDT … Controlled departure time
CENRAP ... Center Radar ARTSPresentation
CEP … Central EastPacific
CERAP … Combined Center/RAPCON
CFR … Code of Federal Regulations
CNS … Continuous
CPDLC … Controller Pilot DataLink Communications
CPME … Calibration Performance Monitor Equipment
CfA … Control Area
CTRD … Certified Tower Radar Display
CVFP … Charted Visual Flight Procedure
CWA … Center Weather Advisory
DARC … DirectAccess Radar Channel
DETRESFA. Distress Phase code (Alerting Service)
DF … Directionfinder
DH … Decision height
Abbreviation Meaning
DME … Distancemeasuring equipment compatible with TACAN
DOE … Department ofEnergy
DP … Instrument Departure Procedure
DR … Deadreckoning
DRT … Diversionrecoverytool
DSR … Display System Replacement
DVFR … Defense Visual Flight Rules
DVRSN . ... Diversion
ECM … Electronic countermeasure
EDARC .... Enhanced DirectAccess Radar Channel
EDCT … ExpectDeparture Clearance Time
EFC … Expectfurther clearance
ELP … Emergency Landing Pattern
ELT … Emergency locatortransmitter
EOS … EndService
EOVM … Emergency obstruction video map
ETA … Estimated time of arrival
FAA … Federal AviationAdministration
FAAO … FAA Order
FANS … Future Air Navigation System
FOIO … Flight Data Input/Output
FOP … " Flight data processing
FIR … FlightInformation Region
FL … '" Flight level Fill … FlightInformation Publication
FLY … Fly or flying
FMS … Flight Management System
FMSP … FlightManagement System Procedure
FSM … Flight Schedule Monitor
FSS … FlightService Station
GCA … Ground controlled approach
GNSS … Global NavigationSatelliteSystem
GPD … Graphics Plan Display
GPS … Global PositioningSystem
GS … Ground stop
HERT … Host Embedded Route Text
HF/RO … High Frequency/Radio Operator
HIRL … High intensityrunway lights
ICAO … International Civil AviationOrganization
!DENT … Aircraft identification
IFR … Instrument flight rules IFSS … International FlightService Station US … Instrument Landing System
Terms of Reference
•
•
I
•
e
I
Abbreviation Meaning
INCERFA ... Uncertainty Phasecode (AlertingService)
INREQ … Information request
INS … Inertial Navigation System
IR … IFRmilitary training route
IRU … Inertial Reference Unit
JATO … Jetassisted takeoff
LAHSO .. -, Land andHoldShort Operations
LOA Letter of Agreement
LLWAS … Low Level WindShearAlertSystem
UMF … Low/mediumfrequency
LORAN .... Long Range Navigation System
LID … Along Track Distance
Mach … Mach number
MALS … Medium Intensity Approach Light System
MALSR .... Medium Approach light System with runway alignment indicator lights
MAP … Missedapproach point
MARSA .... Military authority assumes responsibility forseparation of aircraft
MCA … Minimum crossingaltitude
MCI … MOOe C Intruder
MDA … Minimumdescent altitude
MDM … Maindisplay monitor
MEA … Minimumen route(IFR)altitude
MEARTS ... MicroEn RouteAutomated Radar Tracking System
MIA … MinimumIFR altitude
MIRL … Medium intensity runway lights
MLS … Microwave LandingSystem
MNPS … Minimum Navigation Performance Specification
MNT … MachNumber Technique
MOA … Military operations area
MOCA … Minimum obstruction clearance altitude
MRA … Minimum reception altitude
MSAW … Minimum Safe Altitude Warning
MSL … Meansea level
MTI … Moving target indicator
MTR … Military training route
MVA … Minimumvectoring altitude
NADIN … National Airspace DataInterchange Network
NAS … NationalAirspaceSystem
NAT .... - .. ICAO North Atlantic Region
NBCAP ... . National BeaconCodeAllocation Plan
Terms of Reference
Abbreviation Meaning
NOB … Nondirectional radiobeacon
NHOP … National Hurricane Operations Plan
NIDS … NationalInstitute for Discovery Sciences
NM … Nauticalmile NOAA . .. -. National OceanicandAtmospheric Administration
NOPAC … North Pacific
NORAD .... North American Aerospace Defense Command
NOS … National Ocean Service
NOTAM .... Noticeto Airmen
NRP … North American RouteProgram
NTZ … No transgression zone
NWS … National Weather Service
NWSOP .. . . National Winter Storm Operations Plan
ODALS .... Omnidirectional Approach Lighting System
OID … Operator Interface Device
ONER … OceanicNavigational Error Report
OS … Operations Supervisor
OTR … Oceanictransition route
PAR … Precision approach radar
PAR … Preferred arrival route
PBCT … Proposed boundary crossingtime
P/CG … Pilot/Controller Glossary
PDAR … Preferential departure arrival route
PDR … Preferential departure route
PIDP … Programmable indicator data processor
PPI … Plan positionindicator
PVD … Plan view display
RA … Radar Associate
RDP … Radar dataprocessing
RAIL … Runway alignment indicator lights
RAPCON ... Radar Approach Control Facility (USAF)
RATCF … Radar Air Traffic Controi Facility (USN)
RBS … Radar bombscoring
RCC … RescueCoordination Center
RCLS … Runway Centerline System
RCR … Runway condition reading
RE … Recent (usedto qualifyweather phenomena suchasrain, e.g. recent rain = RERA)
REIL … Runway end identifier lights
RNAV … Area navigation
RNP … Required Navigation Performance
I
Abbreviation Meaning RTQC … Real-Time Quality Cuntrol
RVR … Runway visual range
RVSM … Reduced Vertical Separation Minimum
RW … Runway visibilityvalue
SAR … Search andrescue
SATCOM '" SatelliteCommunication
SELCAL .... Selective Calling System
SFA … Single frequency approach
SFO … Simulated flameout
SID … Standard Instrument Departure
SIGMET .... Significantmeteorologicalinformation
STAR … Standard terminal arrival
STARS … Standard Terminal Automation Replacement System
STMC … Supervisory TrafficManagement Coordinator
STMCIC .... Supervisory Traffic Management Coordinator-in-charge
STOL … Short takeoff and landing
SURPIC .... SurfacePicture
SVFR … Special Visual Flight Rules TAA … Terminal arrival area
TACAN .... TACANUHF navigational aid (omnidirectional courseanddistance information)
TCAS … TrafficAlert andCollision Avoidance System
TCDD … Tower cab dlgltal display
TDW … Tower displayworkstation
TDZL … Touchdown Zone LightSystem
Abbreviation Meaning
TMC … TrafficManagement Coordinator
TMU … TrafficManagement Unit
TRACON ... Terminal Radar Approach Control
TRSA … Terminal radar servicearea
UFO … Unidentified flying object
UHF … Ultra high frequency
URET … Userrequest evaluation tool
USA … United States Army
USAF … UnitedStatesAir Force
USN … UnitedStatesNavy
UTe … Coordinated universal time
UTM … Unsuccessfultransmission message
UUA … Urgentpilot weather report
VFR … Visualflight rules
VHF … Very high frequency
VMC … Visualmeteorological conditions
VNAV … Vertical Navigation
VOR … VHFnavigational aid (omnidirectional courseinformation)
VOR/DME .. CollocatedVOR andDME navigational aids(VHFcourseandUHF distance information)
VORTAC ... Collocated VOR and TACAN navigation aids (VIIF and UHF course and UHF distance information)
VR … VFRmilitary training route
VSCS … VoiceSwitchingandControl System
WAAS … WideAreaAugmentation System
WATRS … WestAtlanticRouteSystem
WSO … Weather Service Office
WST … ConvectiveSIGMET
Terms of Reference
I
•
•
•
Section 1. General › 2-1-3. PROCEDURAL PREFERENCE
Chapter 2. General Control
Section 1. General
711O.65P
2-1-1. ATCSERVICE
The primary purpose of the ATCsystem is to prevent a collision between aircraft operating in the system and to organize and expedite the flow of traffic. In addition to its primary function, the ATCsystem has the capability to provide (with certain limitations) additional services. The ability to provide additional services is limited by many factors, such as the volume of traffic, frequency congestion, quality of radar, controllerworkload, higher priority duties, and the pure physical inability to scan and detect those situations that fall in this category. It is recognized that these services cannot be provided in cases in which the provision of services is precluded by the
above factors. Consistent with the aforementioned conditions, controllers shall provide additional service procedures to the extent permitted by higher priority duties and other circumstances. The provision of additional services is not optional on the part ofthe controller, but rather is required when the work situation permits. Provide air traffic control service in accordance with the procedures and minima in this order except when:
a. A deviation is necessary toconform with ICAO Documents, National Rules of the Air, or special agreements wherethe U.S. provides air traffic control service in airspace outside the U.S. and its possessions or:
NOTE- Pilots are required to abide by CFRs or other applicable
regulations regardless ofthe application ofany procedure or minima in this order.
b. Other procedures/minima are prescribed in a letter of agreement, FAA directive, or a military document, or:
NOTE- These procedures may include altitude reservations, air refueling, fighter interceptor operations, law enforcement, etc.
REFERENCE- FAAO 7110.65. Procedural Leuers ofAgreement, Para 1-1-8.
C. A deviation is necessary to assist an aircraft when an emergency has been declared.
General
REFERENCE· FAAO 7110.65, Safety Alert, Para 2-]-6. FAAO 7110.65, Emergencies, Chapter 10 FAAO 7110.65, Merging Target Procedures, Para 5-1-8.
2-1-2. DUTY PRIORITY
a. Give first priority to separating aircraft and issuing safety alerts as requited in this order. Good judgment shall be used in prioritizing all other
provisions of this order based on the requirements of the situation at hand.
REFERENCE· FAAO 7110.65, Safety Alert, Para 2-1-6.
NOTE- Because there are many variables involved, it is virtually
impossible to develop a standard list ofduty priorities that would apply uniformly to every conceivable situation. Each set of circumstances must be evaluated on its own merit, and when more than one action is required,
controllers shall exercise their best judgment basedon the facts and circumstancesknown to them. That action which
is most criticalfrom a safety standpoint is performed first.
b. Provide additional services to the extent possible, contingent only upon higher priority duties and other factors including limitations of radar, volume of traffic, frequency congestion, and workload.
2-1-3. PROCEDURAL PREFERENCE
a. Use automation procedures in preference to nonautomation procedures when workload, communications, and equipment capabilities permit.
b. Use radar separation in preference to nonradar separationwhen it will be to an operational advantage
and workload, communications, and equipment permit.
c. Use nonradar separation in preference to radar separation when the situation dictates that an operational advantage will be gained.
NOTE· One situation may be where vertical separation would preclude excessive vectoring.
Section 1. General › 2-1-4. OPERATIONAL PRIORITY
2-1-4. OPERATIONAL PRIORITY
Provide air trafficcontrol service to aircraft on a"first come, first served" basis as circumstances permit, except the following:
NOTE- It is solely the pilot's prerogative to cancel an IFR flight plan. However, apilot's retention ofan IFR flightplan does
not afford priority over VFR aircraft. For example, this does not preclude the requirement for the pilot of an arriving IFR aircraft to adjust hislher flight path, as necessary, to enter a traffic pattern in sequence with arriving VFR aircraft.
a. An aircraft in distress has the right of way over all other air traffic.
REFERENCE- 14 CFR Section 91.113(c).
b. Provide priority to civilian air ambulance flights "LIFEGUARD." Air carrier/taxi usage of the "LIFEGUARD" call sign, indicates that operational priority is requested. When verbally requested, provide priority to military air evacuation flights (AIR EVAC, MED EVAC) and scheduled air carrier/air taxi flights. Assist the pilots of air ambulance/evacuation aircraft to avoid areas of significant weather and tnrbulent conditions. When requested by apilot, provide notifications to expedite ground handling of patients, vital organs, or urgently needed medical materials.
NOTE· It is recognized that heavy traffic flow may affect the
controller's ability to provide priority handling. However, without compromising safety, good judgement shall be used in each situation to facilitate the most expeditious movement ofa lifeguard aircraft.
c. Provide maximum assistance to SAR aircraft performing a SAR mission.
REFERENCE- FAAO 7110.65, Providing Assistance; Para 10-1-3.
d. Expedite the movement of presidential aircraft and entourage and any rescue support aircraft as well as related control messages when traffic conditions and communications facilities permit.
NOTE· As used herein the terms presidential aircraft and
entourage include aircraftand entourage ofthe President, Wee President, or otherpublicfigures when designated by the White House.
REFERENCE· FAAO 7110.65, Aircraft Identification, Para 2-4-20. FAAO 7110.65, Departure Clearances, Para 4-3-2. FAAO 7210.3, Advance Coordination, Para 5-1-1.
e. Provide special handling, as required to expedite Flight Check aircraft.
NOTE· It is recognized that unexpected wind conditions, weather;
or heavy traffic flows may affect controller's ability to provide priority or special handling at the specific time
requested.
REFERENCE· FAAO 7110.65, F/ightCheckAircra[t. Para 9-1-3.
f. Expedite movement of NIGHT WATCH aircraft when NAOC (pronounced NA-YOCK) is indicated in the remarks section of the flight plan or in air/ground communications.
NOTE· Theterm "NAOC" willnolbe apartofthe callsign butmay be used when the aircraft is airborne to indicate a request for special handling.
REFERENCE· FAAO 7610A,Applications, Para 12-1-1.
g. Provide expeditious handling for any civil or military aircraft using the code name "FLYNET."
REFERENCE· FAAO 7110.65, FLYNET, Para 9-3-6. FAAO 7610.4, "FLYNET" Flights, Nuclear Emergency Teams, Para 12-4-1.
h. Provide expeditious handling of aircraft using the code name "Garden Plot" only when CARF notifies you that suchpriority is authorized. Refer any questions regarding flight procedures to cARF for resolution.
NOTE· Garden Plot flights require priority movement and.are coordinatedby the militarywith CARP. State authority will contact the RegionalAdministrator to arrange for priority ofNational Guard troop movements within a particular state.
l, Provide special handling for USAF aircraft engaged in aerial sampling missions using the code name "SAMP.~'
REFERENCE- FAAO 7110.65. SAMp, Para 9-3-15. FAAO 7210.3, Atmosphere Sampling For Nuclear Contamination, Para 5-3-4. FAAO 7610.4, Atmospheric Sampling For Nuclear Contamination; Para 12-4-3.
j. Provide maximum assistance to expedite the movement ofinterceptoraircraft on active airdefense missions until the unknown aircraft is identified.
General •
Section 1. General › 2-1-6. SAFETY ALERT
k, Expedite movement of Special Air Mission aircraft when SCOOT is indicated in the remarks section of the flight plan or in air/ground communications.
NOTE- The term"SCOOT" will notbepartofthe callsign but may be used when the aircraft is airborne to indicate a request for special handling.
REFERENCE· FAAO 7110.65, Law Enforcement Operations by Civil and Military
Organizations, Para 9-3-10. FAAO 7610.4, Applications, Para 12-7-1.
I. When requested, provide priority handling to TEAL and NOAA mission aircraft.
NOTE· Priority handling may be requested by the pilot, or via
telephone from CARCAHor the 53rd Weather Reconnaissance Squadron (53WRS) operations center personnel, or in the remarks section ofthe flight plan.
REFERENCE· FAAO 7110.65, Weather Reconnaissance Flights, Para 9-3-17.
m. IFR aircraft shall have priority over SVFR aircraft.
REFERENCE· FAAO 7110.65, Chapter 7, Section 5, Special VFR (SVFR).
n, Providing priority and special handling to expedite the movement of OPEN SKIES observation and demonstration flights.
NOTE- An OPEN SKIES aircraft has priority over all "regular" air traffic. "Regular" is defined as all aircraft traffic other than:
1. Emergencies. 2. Aircraftdirectly involvedinpresidentialmovement. 3. Forces or activities in actual combat. 4. Lifeguard, MED EVAC, AIR EVAC and active SAR missions.
REFERENCE· FAAO 7110.65 OPEN SKIES Treaty Aircraft, Para 9-3-20. FAAO 7210.3, OPEN SKIES Treaty Aircraft, Para 5-3-7.
Treaty on OPEN SKIES, Treaty Document, 102-37.
o. Aircraft operating under the North American Route Program (NRP) are not subj ect to route limiting restrictions (e.g., published preferred IFR routes, letter of agreement requirements, standard operating procedures).
REFERENCE· FAAO 7110.65, En Route Data Entries, Para 2-3-2. FAAO 7110.65, North American Route Program (NRP) Information, Para 2-2-15. FAAO 7110.65, RouteorA/titudeAmendments, Para 4-2-5. FAAO 7210.3, Chapter 17, Section 17, NorthAmerkanRouteProgram.
General
p. If able, provide priority handling to diverted flights. Priority handling may be requested via use of "DVRSN" in the remarks section of the flight plan or by the flight being placed on the Diversion Recovery Tool (DRT).
REFERENCE- FAAO 7210.3, Diversion Recovery, Para 17-4-6.
2-1-5. EXPEDITIOUSCOMPLIANCE
3. Use the word "immediately" only when expeditious compliance is required to avoid an imminent situation.
b. Use the word "expedite" only when prompt compliance is required to avoid the development of an imminent situation. If an "expedite" climb or descent clearance is issued by ATC,and subsequently the altitude to maintain is changed or restated without an expedite instruction, the expedite instruction is canceled.
c. In either case, iftime permits, include thereason for this action.
2-1-6. SAFETY ALERT
Issue a safety alert to an aircraft if you are aware the aircraft is in a position/altitude which, in your • judgment, places it in unsafe proximity to terrain,
obstructions, or other aircraft. Once the pilot informs you action is being taken to resolve the situation, you may discontinue the issuance of further alerts. Do not assume that because someone else has responsibility for the aircraft that the unsafe situation has been observed and the safety alert issued; inform the appropriate controller. If a TRACON has given control of an aircraft to one
of its remote towers, and the tower has aural and • visual MSAWalert capability, theTRACON does not have to inform the tower controller if an alert is observed for that aircraft.
NOTE-
1. The issuance of a safety alert is a first priority (see para 2-1-2, Duty Priority) once the controller observes
and recognizes a situation ofunsafe aircraft proximity to terrain, obstacles, or other aircraft. Conditions, such as workload, traffic volume, the quality/limitations of the radar system, and the available lead time to react are factors in determining whether it is reasonable for the
controller to observe and recognize such situations. While a controller cannot see immediately the development of every situation where a safety alert must be issued, the
controller must remain vigilant for such situations and issue a safety alert when the situation is recognized.
Section 1. General › 2-1-8. MINIMUM FUEL
2. Recognition ofsituations ofunsafeproximitymayresult fromMSAW/E-M&4WILAAS, automatic altitude readouts, Conflict/Mode C Intruder Alert, observations on a PAR scope, or pilot reports.
3. Once the alert is issued, it is solely the pilot's prerogative to determine what course ofaction, ifany, will
be taken.
a. Terrain/Obstruction Alert. Immediately issue/ initiate an alert to an aircraft if you are aware the aircraft is at an altitude which, in your judgment, places it in unsafe proximity to terrain/obstructions. Issue the alert as follows:
PHRASEOLOGY· (Identification) LOWALTITUDEALERT,
CHECK YOUR ALTITUDE IMMEDIATELY.
THE (as appropriate) MEAIMVA/MOCAIMIA IN YOUR AREA IS (altitude),
or if an aircraft is past the final approach fix (nonprecision approach),
or the outer marker,
or the fix used in lieu of the outer marker (precision approach),
and, if known, issue
THE '(as appropriate) MDA/DH IS (altitude).
b. Aircraft Conflict/Mode C Intruder Alert. Immediatelyissue/initiate an alert to an aircraft if you are aware of another aircraft at an altitude which you believe places them in unsafe proximity. If feasible, offer the pilot an alternate course of action.
c. When an alternate course ofaction is given, end the transmission with the word "immediately."
PHRASEOLOGY- TRAFFICALERT(call sign) (position ofaircraft)ADVISE YOU TURNLEFT/RIGHT (heading),
and/or
CLIMB/DESCEND (specific altitude if appropriate) IMMEDIATELY.
REFERENCE- FAAO 7110.65, ConflictAlert (CA) andMode C Intruder (Mel) Alert, Para 5-14-1. FAAO 7110.65,En RouteMinimum SafeAJJitude Warning (E-MSA""'I, Para 5-14-2. FAAO 7110.65, CAIMel, Para 5-15-6. FAAO 7110.65, Altitude Filters, Para 5-2-23.
2-1-7. INFLIGHT EQUIPMENT MALFUNCTIONS
8. When a pilot reports an inflight equipment malfunction, determine the nature and extent of any special handling desired.
NOTE· Inflight equipment malfunctions include partial or
complete failure of equipment which may affect either safety andlor the ability ofthe flight to proceed under IFR in the ATC system. Controllers may expect reports from pilots regarding VOR, TACAN, ADF, GPS, or low frequency navigation receivers, impairment ofair-ground
communications capability, or other equipment deemed appropriate by the pilot (e.g. airborne weather radar). Pilots should communicate the nature and extent of any assistance desired from ATe.
b. Provide the maximum assistance possible consistentwithequipment,workload, and any special handling requested.
c. Relay to other controllers or facilities who will subsequently handle the aircraft, all pertinent details concerning the aircraft and any special handling required or being provided.
2-1-8. MINIMUM FUEL
If an aircraft declares a state of "minimum fuel," inform any facility to whom control jurisdiction is transferred ofthe minimum fuel problem and be alert for any occurrence which might delay the aircraft en route.
NOTE-
Use ofthe term "minimum fuel" indicates recognition by a pilot that hislher fuel supply has reached a state where, upon reachingdestination, helshecannotacceptany undue delay. This is not an emergency situation but merely an advisory that indicates an emergency situation is possible should any undue delay occur. A minimum fuel advisory does not imply a need for traffic priority. Common sense and goodjudgment will determine the extent ofassistance to be given in minimum fuel situations. If, at any time, the remaining usable fuel supply suggests the need for traffic priority to ensure a safe landing, the pilot should declare
an emergency and report fuel remaining in minutes.
General
Section 1. General › 2-1-11. USE OF MARSA
•
2-1-9. REPORTING ESSENTIAL FLIGHT INFORMATION
Report as soon as possible to the appropriate FSS, airport manager's office, ARTCC, approach control facility, operations office, or military operations office any information concerning components ofthe NAS or any flight conditions which may have an adverse effect on air safety.
NOTE- FSSs are responsible for classifying and disseminating Notices to Airmen.
REFERENCE· FAAO 7110.65, Timely lrformation; Para 3-3-3. FAAO 7110.65, Service Limitations, Para 5-1-6. FAAO 7210.3, Periodic Maintenance, Para 3-1-2.
USN, See OPNA VINST 3721.30.
2-1-10. NAVAJO MALFUNCTIONS
a. When an aircraft reports a ground-based NAVAlD malfunction, take the following actions:
1. Request a report from a second aircraft.
2. If the second aircraft reports normal operations, continue use and inform the first aircraft. Record the incident on FAA Form 7230-4 or appropriate military form.
3. If the second aircraft confirms the malfunction or in the absence of a second aircraft report, activate the standby equipment orrequest the monitor facility to activate.
4. If normal operation is reported after the standby equipment is activated, continue use, record the incident on FAA Form 7230-4 or appropriate military form, and notify Airway Facilities (AF) personnel (the Systems Engineer of the ARTCC when an en route aid is involved).
5. If continued malfunction is reported after the standby equipment is activated or the standby equipment cannot be activated, inform AF personnel and request advice on whether or not the aid should be shut down. In the absence of a second aircraft report, advise the AF personnel of the time of the initial aircraft report and the estimated time a second aircraft report could be obtained.
b. When an aircraft reports a GPS anomaly, request the following information and/or take .the following actions:
1. Record the following minimum informalion:
General
(a) Aircraft call sign and type.
(b) Location.
(c) Altitude.
(d) Date/time of occurrence.
2. Record the incident on FAA Form 7230-4 or appropriate military form.
3. Broadcast the anomaly report to other aircraft as necessary.
PHRASEOLOGY· ATTENTION ALL AIRCRAFT, GPS REPORTED
UNRELIABLE IN VICINITY/AREA (position).
EXAMPLE·
"Attention all aircraft, GPSreported unreliable in the area 30 miles south ofWaco VOR." c. When an aircraft reports a Wide Area Augmentation System (WAAS) anomaly, request the following information and/or take the following actions:
1. Determine if the pilot has lost all WAAS service.
PHRASEOLOGY· ARE YOU RECENING ANYWAAS SERVICE?
2. If the pilot reports receipt of any WAAS service, acknowledge the report and continue normal operations.
3. If the pilot reports loss of all WAAS service, report as a GPS anomaly using procedures in subpara 2-1-lOb.
2-1-11. USEOFMARSA
a. MARSA may only be applied to military operations specified in a letter of agreement or other appropriate FAA or military document.
NOTE· Application ofMARSA is a military commandprerogative. It will not be invoked indiscriminately by individual units
or pilots. It will be used only for IFR operations requiring its use. Commands authorizing M4.RSA will ensure that its implementation and terms of use are documented and coordinated with the control agency having jurisdiction overthe area in which the operations are conducted. Terms ofuse will assign responsibility andprovide for separation among participating aircraft.
b. ATC facilities do not invoke or deny MARSA. Their sale responsibility concerning the use of MARSA is to provide separation between military aircraft engaged in MARSA operations and other nonparticipating IFR aircraft.
Section 1. General › 2-1-14. COORDINATE USE OF AIRSPACE
c. DOD shall ensure thatmilitary pilots requesting special-use airspace/ATCAAshave coordinatedwith the scheduling agency, have obtained approval for entry, and are familiar with the appropriate MARSA procedures. ATC is not responsible for determining which military aircraft are authorized to enter special-use airspace/ATCAAs.
REFERENCE· FAAO 7110.65, MilitaryAerialRefueling. Para 9-3-11.
2-1-12. MILITARY PROCEDURES
Military procedures in the form of additions, modifications, and exceptions to the basic FAA procedure are prescribed herein when a common procedure has not been attained or to fulfill a specific requirement. They shall be applied by:
a. ATCfacilities operated by that military service.
EXAMPLE·
1. AnAirForcefacility providing service for an AirForce base wouldapply USAFproceduresto all trafficregardless ofclass.
2. A Navyfacilityprovidingservicefor aNavalAirStation would apply USN procedures to all traffic regardless of class.
b. ATC facilities, regardless of their parent organization (FAA, USAF, USN, USA), supporting a designated military airport exclusively. This designation determines which military procedures are to be applied.
EXAMPLE· 1. An FAA facility supports a USAF base exclusively; USAFprocedures are applied to all traffic at that base.
2. An FAA facility provides approach controlservice for a Naval Air Station as well as supporting a civil airport;
basic FAAprocedures are applied at both locations by the FAA facility.
3. A USAF facility supports a USAF base and provides approach control service to a satellite civilian airport; USAF procedures are applied at both locations by the USAF facility.
REFERENCE· FAAO 7110.65, Annotations, Para 1-2-5.
c. Other ATCfacilities when specified in aletter of agreement.
EXAMPLE· A USAF unit is using a civil airport supported by an FAA facility- USAF procedures will be applied as specified in
a Ietier ofagreement between the unit and the FAA facility to the aircraft ofthe USAF unit. Basic FAAprocedures will be applied to all other aircraft.
2-1-13. FORMATION FLIGHTS
Control formation flights as a single aircraft. When individual control is requested, issue advisory information which will assist the pilots in attaining separation. When pilot reports indicate separation has been established, issue control instructions as required.
NOTE-
1. Separation responsibility between aircraft within the formation during transition to individual controlrests with the pilots concerned until standard separation has been attained.
2. Formation join-up and breakaway willbe conductedin VFR weather conditions unless prior authorization has been obtained from ATe or individual control has been approved.
REFERENCE- FAAO' 7110.65, Additional Separation for Formation Flights, Para 5-5-8. P/CG Tenn- Formation Flight.
2-1-14. COORDINATE USE OF AIRSPACE
a. Ensure that the necessary coordination hasbeen accomplishedbefore you allow an aircraft under your control to enter another controller's area of jurisdiction.
b. Before you issue control instructions directly or relay through another source to an aircraft which is within another controller's area of jurisdiction that will change that aircraft's heading, route, speed, or altitude, ensure that coordination has been accomplished with each of the controllers listed below whose area of jurisdiction is affected by those instructions unless otherwise specified by a letter of agreement or a facility directive:
1. The controller within whose area of jurisdiction the control instructions will be issued.
2. The controller receiving the transfer of control.
3. Any intervening controller(s) through whose area of jurisdiction the aircraft will pass.
General •
Section 1. General › 2-1-17. RADIO COMMUNICATIONS TRANSFER
c. If you issue control instructions to an aircraft through a source other than another controller (e.g., ARINC, FSS, anotherpilot) ensure that the necessary coordination has been accomplished with any controllers listed in subparas bl, 2, and 3, whose area ofjurisdictionis affectedby those instructions unless otherwise specified by a letter of agreement or a facility directive.
REFERENCE- FAAO 7110.65, Control Transfer; Para 2-1-15. FAAO 7110.65,AdjacentAirspace, Para 5-5-10. FAAO 7110.65, Transferring Controller Handoft. Para 5-4-5. FAAO 7110.65, Receiving Controller Handoff, Para 5-4-6.
2-1-15. CONTROL TRANSFER
a. Transfer control of an aircraft in accordance with the following conditions:
1. At a prescribed or coordinated location, time, fix, or altitude; or,
2. At the time a radar handoff and frequency change to the receiving controller have been completedand when authorizedby afacility directive or letter of agreement which specifies the type and extent of control that is transferred.
REFERENCE- FAAO 7110.65, Coordinate Use ofAirspace, Para 2-1-14. FAAO 7110.65, Transferring COn/roller Handoff, Para 5-4-5. FAAO 7110.65, Receiving Controller Randolf, Para 5-4-6.
b. Transfer control of an aircraft only after eliminating any potential conflict with other aircraft for which you have separation responsibility.
.. c. Assume control of an aircraft only after it is in your area of jurisdiction unless specifically coordinated or as specified by letter of agreement or a facility directive.
2-1-16. SURFACE AREAS
a. Coordinate with the appropriate nonapproach control tower on an individual aircraft basis before issuing a clearance which would require flight within
a surface area for which the tower has responsibility unless otherwise specified in a letter of agreement.
REFERENCE· FAAO 7210.3, Letters a/Agreement, Para 4-3-1.
14 CFR Section 91.127, Operating on or in the Vicinity ofan Airport in Class E Airspace. P/CG Term- SurfaceArea.
b. Coordinate with the appropriate control tower for transit authorizationwhenyou are providing radar
General
traffic advisory service to an aircraft that will enter another facility's airspace.
NOTE·
The pilot is not expected to obtain his/her own authorization through each area when in contact with a radar facility.
c. Transfer communications to the appropriate facility, if required,prior to operationwithin asurface area for which the tower has responsibility.
REFERENCE- FAAO 7110.65, Radio Communications Transfer, Para 2-1-17. FMO 7110.65, Surface Area Restrictions, Para 3-1-11. FAAO 7110.65, Application, Para 7-6-1.
14 CFR Section 91.129, Operations in Class DAirspace.
2-1-17. RADIO COMMUNICATIONS TRANSFER
a. Transfer radio communications before an aircraft enters the receiving controller's area of jurisdictionunless otherwisecoordinatedor specified by a letter of agreement or a facility directive.
b. Transfer radio communications by specifying the following:
NOTE- Radio communications transfer procedures may be specified by a letter ofagreement or contained in the route description ofan MIR as published in the DOD Planning AP/lB (AP/3).
1. The facility name or location name and terminal function to be contacted. TERMINAL: Omit the locationnamewhen transferring communications to another controller within your facility; except when instructing the aircraft to change frequency for final approach guidance include the name of the facility.
2. Frequencyto use exceptthefollowing may be omitted:
(a) FSS frequency.
(b) Departure frequency if previously given or published on a DP chart for the procedure issued.
(c) TERMINAL:
(1) Ground orlocal controlfrequency ifin 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.
Section 1. General › 2-1-18. OPERATIONAL REQUESTS
EXAMPLE-
"Contact Tower." "Contact Ground. n
IfCan/act Ground Point Seven. ,. "Contact Ground, One Tho Zero Point Eight. " "Contact Huntington Radio. " "Contact Departure. " "ContactLosAngeles Center, One Tho Three PointFour. "
3. Time, fix, altitude, or specifically when to contact a facility. You may omit this when compliance is expected upon receipt.
NOTE- AIM, para 5-3-1, ARTCCCommunications, informspilots that they are expected to maintain a listening watch on the transferring controller's frequency until the time, fix, or altitude specified.
PHRASEOLOGY- CONTACT (facility name or location name and terminal [unction), (frequency).
Ifrequired,
AT (time, fix, or altitude).
c. 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. J, "Monitor Ground, One Tho Zero Point Eight."
d. In situations where a sector has multiple frequencies or when sectors are combined using multiple frequencies and the aircraft will remain under your jurisdiction, transfer radio communication by specifying the following:
PHRASEOLOGY- (Identification) CHANGE TO MY FREQUENCY (state frequency).
EXAMPLE·
"United two twenty-two change to my frequency one two three point four. "
REFERENCE- AiM, Contact Procedures, Para 4-2-3.
e. Avoidissuing afrequency change to helicopters known to be single-piloted during air-taxiing, hovering, or low-level flight. Whenever possible,
relay necessary control instructions until the pilot is able to change frequency.
NOTE- Most light helicopters are flown by one pilot and require
the constantuse ofboth hands andfeet to maintain control. Although Flight Control Friction Devices assist the pilot,
changing frequency near the ground could result in inadvertentground contactandconsequentloss ofcontrol. Pilots are expected to advise ATC of their single-pilot
status ifunable to comply with a frequency change.
REFERENCE- AIM. Communications, Para 4-3-14.
r. In situations where the controller does not want the pilottochangefrequencybutthepilotis expecting or may want a frequency change, use the following phraseology.
PHRASEOLOGY· REMAIN THIS FREQUENCY.
REFERENCE- FAAo 7110.65, Clearancelnfonnation, Para 4-7-1. FAAO 7110.65,Communication Transfer, Para 5-12-9.
2-1-18. OPERATIONAL REQUESTS
Respond to a request from another controller, a pilot or vehicle operator by one of the following verbal means:
a. Restate the request in complete or abbreviated terms followed by the word "APPROVED." The phraseology "APPROVED AS REQUESTED" may be substituted in lieu of a lengthy readback.
PHRASEOLOGY-
(Requested operation) APPROVED.
or
APPROVEDAS REQUESTED.
b. State restrictions followed by the word "APPROVED."
PHRASEOLOGY- (Restriction and/or additional instructions, requested operation) APPROVED.
c. State the word "UNABLE" and, time permitting, a reason.
PHRASEOLOGY·
UNABLE (requested operation).
and when necessary,
(reason and/or additional instructions.)
General
Section 1. General › 2-1-21. TRAFFIC ADVISORIES
2/19104
d. State the words "STAND BY."
NOTE-
"STAND BY" is not an approval or denial. The controller acknowledges the request and will respond at a later time.
REFERENCE-
FAAO 7110.65. Traffic Advisories,Para2-1-21. FAAO 7110.65, Route or Altitude Amendments, Para 4-2-5. FAAO 7110.65, Methods, Para 7-9-3.
2-1-19. WAKE TURBULENCE
a. Apply wake turbulence procedures to aircraft operating behind heavy jets/B757s and, where indicated, to small aircraft behind large aircraft.
NOTE- Para 5-5-4, Minima, specifies increasedradar separation for small type aircraftlanding behindlarge, heavy, orB757
aircraft because ofthe possible effects ofwake turbulence.
b. The separation minima shall continue to touchdown for all IFR aircraft not making a visual
approach or maintaining visual separation.
REFERENCE- FAAO 7110.65, Approach Separation Responsibility, Para 5-9-5.
2-1-20. WAKE TURBULENCE CAUTIONARY ADVISORIES
a. Issue wake turbulence cautionary advisories and the position, altitude if known, and direction of flight of the heavy jet or B757 to:
REFERENCE- AC 90-23, Aircraft Wake Turbulence, Pilot Responsibility, Para 12.
1. TERMINAL. VFR aircraft not being radar vectored but are behind heavy jets or B757s.
2. IFR aircraft that accept a visual approach or visual separation.
REFERENCE- FAAO7110.65, visualApproach;Para 7-4-1.
3. TERMINAL. VFR arriving aircraft that have previously been radar vectored and the vectoring has been discontinued.
b. Issue cautionary informationto any aircraft ifin your opinion, wake turbulence may have an adverse effect on it. When traffic is known to be a heavy aircraft, include the word heavy in the description.
NOTE-
Wake turbulence may be encountered by aircraft in flight as well as when operating on the airport movement area. Because wake turbulence is unpredictable, the controller
is not responsible for anticipating its existence or effect. Although not mandatory during ground operations,
General
711O.65P
controllers may use the words jet blast, propwash, or rotorwash, in lieu of wake turbulence, when issuing a caution advisory.
REFERENCE· AC 90-23, Aircraft Wake Turbulence. PIcaTerm- Aircraft Classes. PIcaTerm- Wake Turbulence. PHRASEOLOGY- CAUTION WAKE TURBULENCE (traffic information).
REFERENCE-
FAAO 7110.65, VLSual Separation. Para 7-2-1.
2-1-21. TRAFFIC ADVISORIES
Unless anaircraft isoperating within ClassA airspace or omission is requested by the pilot, issue traffic advisories to all aircraft (IFR or VFR) on your frequency when, in your judgment, their proximity may diminish to less than the applicable separation minima. Where no separation minima applies, such as for VFR aircraft outside of Class BIClass C airspace, or a TRSA, issue traffic advisories to those aircraft on your frequency when in your judgment their proximity warrants it. Provide this service as follows:
a. To radar identified aircraft:
1. Azimuthfrom aircraft interms ofthe 12-hour clock, or
2. When rapidly maneuvering aircraft prevent accurate issuance of traffic as in 1 above, specify the direction from an aircraft's position in terms of the eight cardinal compass points (N, NE, E, SE, S, SW, W, and NW). This method shall be terminated at the pilot's request.
3. Distance from aircraft in miles.
4. Direction in which traffic is proceeding and/or relative movement of traffic.
NOTE- Relative movement includes closing, converging, parallel
same direction, opposite direction, diverging, overtaking, crossing left to right, crossing right to left.
5. If known, type of aircraft and altitude.
REFERENCE· FAAO 7110.65. Description ofAircraft Types, Para 2-4-21. PHRASEOLOGY- TRAFFIC, (number) O'CLOCK,
or when appropriate,
(direction) (number) MILES, (direction)-BOUND andlor (relative movement),
Section 1. General › 2-1-22. BIRD ACTIVITY INFORMATION
and ifknown,
(type ofaircraft and altitude).
or
When appropriate,
(type of aircraft and relative position), (number offeet) FEETABOVE/BELOWYOU.
Ifaltitude is unknown,
ALTITUDE UNKNOWN.
EXAMPLE-
"Traffic, eleven o'clock, one zero miles, southbound, converging, Boeing Seven Twenty Seven, one seven thousand. "
"Traffic, twelve o'clock, one five miles, opposite direction, altitude unknown. "
'(Traffic, ten o'clock, one two miles, southeast bound, one thousand feet below you. "
6. When requested by the pilot, issue radar vectors to assist in avoiding the traffic, provided the aircraft to be vectored is within your area of jurisdiction or coordination has been effected with the sector/facility in whose area the aircraft is operating.
7. Ifunable to provide vector service, inform the pilot.
REFERENCE· FAAO 7110.65, OperationalRequests, Para 2-1-18.
8. Inform the pilot of the following when traffic you have issued is not reported in sight:
(a) The traffic is no factor.
(b) The traffic is no longer depicted on radar.
PHRASEOLOGY- TRAFFIC NO FACTOR/NO LONGER OBSERVED,
or
(number) O'CLOCK TRAFFIC NO FACTOR/NO LONGER OBSERVED,
or
(direction) TRAFFIC NO FACTOR/NO LONGER OBSERVED.
b. To aircraft that are not radar identified:
1. Distance and direction from fix.
2. Direction in which traffic is proceeding.
3. If known, type of aircraft and altitude.
4. ETA over the fix the aircraft is approaching, if appropriate.
PHRASEOLOGY- TRAFFIC, (number) MILES/MINUTES (direction) OF (airport or fix), (direction)-BOUND,
and if known,
(type ofaircraft and altitude),
ESTIMATED (fix) (time),
or
TRAFFIC, NUMEROUS AIRCRAFT VICINITY (location).
Ifaltitude is unknown,
ALTITUDE UNKNOWN. EXAMPLE-
"Traffic, one zero miles east of Forsythe V-O-R, Southbound, M-D Eighty, descending to one six thousand. "
"Traffic, reported one zero miles west ofDowney V-O-R, northbound, Apache, altitude unknown, estimated Joliet V-O-R one three one five. "
"Traffic, eight minutes west ofChicago Heights V-O-R, westbound, Mooney, eight thousand, estimated Joliet
V-O-R two zero three five." '(Traffic, numerous aircraft, vicinity ofDelia airport. "
c. For aircraft displaying Mode C, not radar identified, issue indicated altitude. EXAMPLE-
"Traffic, one o'clock, six miles, eastbound, altitude indicates six thousand five hundred. " REFERENCE- FAAO 7110.65, Traffic Information, Para 3-1-6. FAAO 7110.65, Yisual Separation; Para 7-2-1. FAAO 7110.65, VFRDeparture Information, Para 7-6-10.
2-1-22. BIRD ACTIVITY INFORMATION
a. Issue advisory information on pilot-reported, tower-observed, or radar-observed and pilot-verified bird activity. Include position, species or size ofbirds, ifknown, course of flight, and altitude. Do this for at least 15 minutes after receipt of such information from pilots or from adjacent facilities unless visual observation or subsequent reports reveal the activity is no longer a factor.
General
•
•
•
Section 1. General › 2-1-27. TCAS RESOLUTION ADVISORIES
EXAMPLE-
"Flockofgeese,oneo'clock,sevenmiles,northbound, last reported at four thousand. "
"Flock ofsmall birds, southbound along Mohawk River, last reported at three thousand."
"Numerous flocks of ducks, vicinity Lake Winnebago, altitude unknown. "
b. Relay bird activity information to adjacent facilities and to FSSs whenever it appears it will become a factor in their areas.
2-1-23. TRANSFER OF POSITION RESPONSIBILITY
The transfer of position responsibility shall be accomplished in accordance with the "Standard Operating Practice (SOP)for theTransfer of Position Responsibility," and appropriate facility directives each time operational responsibility for a position is transferred from one specialist to another.
2-1-24. WHEELS DOWN CHECK
USA/USAF/USN
Remind aircraft to check wheels down on each approach unless the pilot has previously reported wheels down for that approach.
NOTE·
The intent is solely to remind thepilot to lower the wheels, not to place responsibility on the controller.
a. Tower shall issue the wheels down check at an appropriate place in the pattern.
PHRASEOLOGY- CHECK WHEELS DOWN.
b. Approach/arrival control, GCA shall issue the wheels down check as follows:
1. To aircraft conducting ASR, PAR, or radar monitored approaches, before the aircraft starts descent on final approach.
2. Toaircraftconductinginstrument approaches and remaining on the radar facility's frequency, before the aircraft passes the outer marker/final
approach fix.
PHRASEOLOGY· WHEELS SHOUW BE DOWN.
General
2-1-25. SUPERVISORY NOTIFICATION
Ensure supervisor/controller-in-charge (CrC) is aware of conditions which impact sector/position operations including, but not limited to, the following:
a. Weather.
b. Equipment status.
c. Potential sector overload.
d. Emergency situations.
e. Special flights/operations.
2-1-26. PILOT DEVIATION NOTIFICATION
When it appears that the actions of a pilot constitute
a pilot deviation, notify the pilot, workload permitting.
PHRASEOLOGY- (Identification) POSSIBLE PILOT DEVIATION ADVISE YOU CONTACT (facility)AT (telephone number).
REFERENCE· FAAO 8020.11, Aircraft Accident and Incident Notification, Investigation, and Reporting, Pilot Deviations, Para 84.
2-1-27. TCAS RESOLUTION ADVISORIES
a. When anaircraft underyourcontroljurisdiction informs you that it is responding to a TCAS Resolution Advisory (RA), do not issue control instructions that arecontrary tothe RA procedurethat
a crew member has advised you that they are executing. Provide safety alerts regarding terrain or obstructions and traffic advisories for the aircraft respondingtothe RA and allother aircraftunder your controljurisdiction, as appropriate.
b. Unless advised by other aircraft that they are also responding to a TCAS RA, do not assume that other aircraft in the proximity of the responding aircraft areinvolved in the RA maneuverorare aware of the responding aircraft's intended maneuvers. Continue to provide control instructions, safety alerts, and traffic advisories as appropriate to such aircraft.
c. Once the responding aircraft has begun a maneuver in response to an RA, the controller is not responsible for providing standard separation between the aircraft that is responding to an RA and any other aircraft, airspace, terrain or obstructions. Responsibility for standard separation resumeswhen one of the following conditions are met:
711O.65P
1. The responding aircraft has returned to its assigned altitude, or
2. A crew member informs you that the TeAS maneuver is completed and you observe that standard separation has been reestablished, or
3. The responding aircraft has executed an alternate clearance and you observe that standard separation has been reestablished.
NOTE- 1. AC 120-55A, Air Carrier Operational Approval and Use of TCAS II, suggests pilots use the following
phraseology to notify controllers during TCAS events.
When a TCAS RA may affect an ATC clearance, inform ATCwhenbeginningthemaneuver, or assoonas workload permits.
EXAMPLE· 1. "New YorkCenter, United 321, TCAS climb." NOTE- 2. When theRA has been resolved, the flight crew should adviseATC they arereturning to theirpreviously assigned clearance or subsequent amended clearance.
EXAMPLE· 2. "New York Center, United 321, clear of conflict, returning to assigned altitude. "
General
Section 2. Flight Plans and Control Information › 2-2-6. IFR FLIGHT PROGRESS DATA
Section 2. Flight Plans and Control Information
2-2-1. RECORDING INFORMATION
a. Record flight plan information required by the type of flight plan and existiug circumstances. Use authorized abbreviations when possible.
NOTE- Generally, all military overseas flights are required to clear through a specified military base operations office
(BASOPS). Pilotsnormallywill notfile flight plans directly with an FAA facility unless a BASOPS is not available. BASOPS will, in turn, forward the IFR flight notification message to the appropriate center.
b. ENROUTE. When flight plans arefiled directly with the center, record all items given by the pilot either on a flight progress strip/flight data entry or on a voice recorder. If the latter, enter in box 26 of the initial flight progress strip the sector or position number to identify where the information may be found in the event search and rescue (SAR) activities become necessary.
REFERENCE- FAAO 7110.65, En Route Data Entries. Para 2-3-2.
2-2-2. FORWARDING INFORMATION
a. Except during NAS Stage A operation, forward the flight plan information to the appropriate ATe facility,FSS,or BASOPS and record thetime offiling and delivery on the form.
b. EN ROUTE. During NAS Stage A operation, the above manual actions are required in cases where the data is not forwarded automatically by the computer.
NOTE- DuringNAS StageA operation, data is exchangedbetween
interfaced automated facilities and both the data and time a/transmission are recorded automatically.
c. EN ROUTE. Forward proposed tower en route flight plans and any related amendments to the appropriate departure terminal facility.
2-2-3. FORWARDING VFR DATA
TERMINAL
Forward aircraft departure times to FSSs or military operations offices when they have requested them. Forward other VFR flight plan data only if requested by the pilot.
Flight Plans and Control Information
2-2-4. MILITARY DVFR DEPARTURES
TERMINAL
Forward departure times on all military DVFR departures from joint-use airports to the military operations office.
NOTE- 1. Detailsfor handlingair carrier, nonscheduledcivil, and militaryDVFRflight data are contained in FAAO 7610.4, Special Military Operations.
2. Military pilots departing DVFRfrom ajoint-use airport will include the phrase "DVFR to (destination)" in their initial call-up to an FAA operated tower.
2-2-5. IFR TO VFR FLIGHT PLAN CHANGE
Request a pilot to contact the appropriate FSS if the pilot informs you of a desire to change from an lFR to a VFR flight plan.
2-2-6. IFR FLIGHT PROGRESS DATA
Forward control information from controller to controller within a facility, then to the receiving facility as the aircraft progresses along its route. Where appropriate, use computer equipment in lieu of manual coordination procedures. Do not use the remarks section of flight progress strips in lieu of voice coordination to pass control information. Ensure that flight plan and control information is correct and up-to-date. When covered by a letter of agreement/facility directive, thetime requirements of subpara a may be reduced, and the time requirements of subpara b1 and para 2-2-11, Forwarding Amendedand UTMData, subpara amay be increased up to 15 minutes when facilitated by automated systems or mandatory radar handoffs; or if operationally necessary because of manual data processing or nonradar operations, the time requirements of subpara a may be increased.
NOTE- I. The procedures for preparing flight plan and control information related to altitude reservations (ALTRVs) are contained in FAAO 7210.3, Facility Operation and Administration, para 8-1-2, ALTRV Flight Data
Processing. Development ofthe methods for assuring the
accuracy and completeness of ALTRV flight plan and control information is the responsibility of the military liaison and security officer.
2. The termfacility in thisparagraph refers to centers and terminal facilities when operating in an en route capacity.
Section 2. Flight Plans and Control Information › 2-2-9. COMPUTER MESSAGE VERIFICATION
a. Forward the following information at least 15 minntesbefore the aircraft is estimated toenterthe receiving facility's area:
1. Aircraft identification. I
2. Nnmber of aircraft if more than one, heavy aircraft indicator "HI" if appropriate, type of aircraft, and aircraft equipment suffix.
3. Assigned altitude andETAoverlast reporting point/fix in transferring facility's area or assumed departure time when the departure point is the last point/fix in the transferring facility's area.
4. Altitude at which aircraft will enter the receiving facility's area if other than the assigned altitude.
5. True airspeed.
6. Point of departure.
7. Route of flight remaining.
8. Destination airport and clearance limit if other than destination airport.
9. ETA at destination airport (not required for military or scheduled air carrier aircraft).
10. Altitude requested by the aircraft if assigned altitude differs from requested altitude (within a facility only).
NOTE- When an aircraft has crossed one facility's area and assignment at a differenr altitude is still desired, the pilot will reinitiate the request with the next facility.
REFERENCE- FAAO 7110.65, AnncipotedA/titude Changes, Para 4-5-8.
11. When flight plan data must be forwarded manually and an aircraft has been assigned a beacon code by the computer, include the code as part of the flight plan.
NOTE- When an IFR aircraft, or a VFR aircraft that has been assigned a beacon code by the host computer and whose flight plan will terminate in another facility's area cancels ATe service or does not activate the flight plan, send a
remove strips (RS) message on that aircraft via the host keyboard, the FDIO keyboard or call via service F.
12. Longitudinal separation being usedbetween aircraft atthesame altitude ifit results in these aircraft
having less than 10 minutes separation at the facilities' boundary.
13. Any additional nonroutine operational information pertinent to flight safety.
NOTE- ENROUTE. This includes alerting the receiving controller
that the flight is conducting celestial navigation training.
REFERENCE- FAAO 7110.65, Celestial Navigation Training, Para 9-3-2.
b. Forward position report over last reporting point in the transferring facility's area if any of the following conditions exist:
1. Time differs more than 3 minutes from estimate given.
2. Requested by receiving facility.
3. Agreed to between facilities.
2-2-7. MANUALINPUT OF COMPUTER-ASSIGNED BEACON CODES
When a flight plan is manually entered into the computer and a computer-assigned beacon code has been forwarded with the flight plan data, insert the beacon code in the appropriate field as part of the inpnt message.
2-2-8. ALTRV INFORMATION
ENROUTE
When an aircraft is a part of an approved ALTRV, forward only those items necessary to properly identify the flight, update flight data contained in the ALTRV APVL, or revise previously given informa-
tion.
2-2-9. COMPUTER MESSAGE VERIFICATION
ENROUTE
Unless yonr facility is equipped to automatically obtain acknowledgmentofreceipt oftransferred data, when you transfer control information by computer message, obtain, via Service F,acknowledgmentthat the receiving center has received the message and verification of the following:
a. Within the time limits specified by a letter of agreement or when not covered by a letter of agreement, at least 15 minutes before the aircraft is estimated to enter the receiving facility's area, or at
Flight Plans and Control Information
•
Section 2. Flight Plans and Control Information › 2-2-11. FORWARDING AMENDED AND UTM DATA
the time of a radar handoff, or coordination for transfer of control:
1. Aircraft identification.
2. Assigned altitude.
3. Departure or coordination fix time.
b. Any cancellation of IFR or HOST generated VFR flight plan.
REFERENCE· FAAO 71.IO.65./FRFJight Progress Data, Para 2-2-6.
2-2-10. TRANSMIT PROPOSED FLIGHT PLAN
ENROUTE
a. Transmit proposed flight plans which fall within an ARTCC's Proposed Boundary Crossing
Time (pBCf)parameter toadjacentARTCC's via the Computer B network during hours of inter-center computer operation. In addition, when the route of flight of any proposed flight plan exceeds 20 elements external to the originating ARTCC's area, NADIN shall be used to forward the data to all
affected centers.
b. During nonautomated operation, the proposed flight plans shall be sent via NADIN to the other centers involved when any of the following conditions are met:
1. The route of flight external to the originating center's area consists of 10 or more elemeuts and the flight will enter 3 or more other center areas.
NOTE· An element is defined as either afixor route as specified in
FAAO 7110.10, Flight Services, para 6-3-3, IFR Flight Plan Control Messages.
2. The route of flight beyond the first point of exit from the originating center's area consists of 10 or more elements, which are primarily fixes described in fix-radial-distance or latitude/longitude format, regardless of the number of other center areas entered.
3. The flight plan remarks are too lengthy for interphone transmission.
Flight Plans and Control Information
2-2-11. FORWARDING AMENDED AND UTM DATA
a. Forward any amending data concerning previously forwarded flight plans exceptthatrevisionsto ETA information in para 2- 2-6, IFR Flight Progress Data, need only be forwarded when the time differs by more than 3 minutes from the estimate given.
PHRASEOLOGY·
(Identification), REVISED (revised information).
EXAMPLE·
"American Two, revised flight level, three three zero. n
"United Eight Ten, revised estimate, FrontRoyal two zero zero five."
«Douglas Five Zero One Romeo, revised altitude, eight thousand. ,J
Continue reading ↓ 120 of 1487 passages shown