Order JO 7110.10Z Flight Services
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 judgment if they encounter situations not covered by it.
This document is cancelled. Cancelled by JO 7110.10AA. Check the official source before relying on it.
Text read by OCR from a scanned file (7 of 411 pages). Check the original, as some words may be misread.
FAA Order JO 7110.10Z, Flight Services, effective October 12, 2017
Distribution: Electronic Initiated By: AJR-0 Vice President, System Operations Services
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 judgment if they encounter situations not covered by it.
Original Signed By: Michael C. Artist
Michael C. Artist Vice President, System Operations Services Air Traffic Organization
Date: September 1, 2017
Effective Date:
10/12/2017
Air Traffic Organization Policy
SUBJ: Flight Services
ORDER JO 7110.10Z
DIRECTIVE NO. RECORD OF CHANGES JO 7110.10Z
CHANGE
TO BASIC
SUPPLEMENTS
OPTIONAL
CHANGE
TO BASIC
SUPPLEMENTS
OPTIONAL
FAA Form 1320−5 (6−80) USE PREVIOUS EDITION
FAA Order JO 7110.10Z, Flight Services, effective October 12, 2017 › Explanation of Changes - Basic
Explanation of Changes E of C−1
Flight Services Explanation of Changes
Basic
Direct questions through appropriate facility/service center office staff
to the Office of Primary Interest (OPI)
i. 3−2−1. CONDUCT OF STANDARD BRIEFING This change adds a note regarding special awareness information for flights in and around Special Flight Rules Areas and areas that require Special Air Traffic Rules (SATR).
j. Entire Publication
Additional editorial/format changes were made where necessary. Revision bars were not used because of the insignificant nature of these changes.
Change 1, effective March 29, 2018
Distribution: Electronic Initiated By: AJR-0 Vice President, System Operations Services
CHANGE
U.S. DEPARTMENT OF TRANSPORTATION
FEDERAL AVIATION ADMINISTRATION
JO 7110.10Z
CHG 1
Air Traffic Organization Policy Effective Date: March 29, 2018
SUBJ: Flight Services
1. Purpose of This Change. This change transmits revised pages to Federal Aviation Administration Order JO 7110.10Z, Flight Services, and the Briefing Guide.
2. Audience. This change applies to select offices in Washington headquarters, service area offices, the William J. Hughes Technical Center, the Mike Monroney Aeronautical Center, and to all air traffic field facilities, international aviation field offices, and the interested aviation public.
3. Where Can I Find This Change? This change is available on the FAA Web site at http://faa.gov/air_traffic/publications and http://employees.faa.gov/tools_resources/orders_ notices/.
4. Explanation of Policy Change. See the Explanation of Changes attachment which has editorial corrections and changes submitted through normal procedures. The Briefing Guide lists only new or modified material, along with background.
5. Distribution. This change is distributed to select offices in Washington headquarters, service area offices, the William J. Hughes Technical Center, the Mike Monroney Aeronautical Center, and to all air traffic field facilities, international aviation field offices, and the interested aviation public.
6. Disposition of Transmittal. Retain this transmittal until superseded by a new basic order.
7. Page Control Chart. See the page control chart attachment.
Original Signed By: Michael C. Artist
Michael C. Artist Vice President, System Operations Services Air Traffic Organization
Date: March 5, 2018
Change 1, effective March 29, 2018 › Explanation of Changes - Chg. 1
JO 7110.10Z CHG 1 3/29/18
Explanation of Changes E of C−1
Flight Services Explanation of Changes
Change 1
Direct questions through appropriate facility/service center office staff
to the Office of Primary Interest (OPI)
f. 2−3−2. AREA/ROUTE BRIEFING PROCEDURES
3−2−1. CONDUCT OF STANDARD BRIEFING
9−5−1. GENERAL 9−5−2. AREA FORECAST (FA) SCHEDULE
9−5−3. DISTRIBUTION
This change retires the textual Area Forecast for the CONUS only and adds information about the new Static Graphical Forecast Images (Aviation Surface Forecast and Aviation Cloud Forecast).
g. 10−1−9. SIMULTANEOUS APPROACH AND RUNWAY EDGE LIGHT OPERATION Runway and approach lighting must be operated in accordance with the criteria contained in Paragraphs 10−1−4, Approach Lights, and 10−1−7, Runway Edge Lights. Runway edge lights are not required on a runway to which an approach is being made when the landing will be made on another runway. Therefore, this paragraph is being deleted.
h. Entire Publication Additional editorial/format changes were made where necessary. Revision bars were not used because of the insignificant nature of these changes.
Distribution: Electronic Initiated By: AJR-0 Vice President, System Operations Services
CHANGE
U.S. DEPARTMENT OF TRANSPORTATION
Change 2, effective September 13, 2018
FEDERAL AVIATION ADMINISTRATION
JO 7110.10Z
CHG 2 Air Traffic Organization Policy Effective Date: September 13, 2018
SUBJ: Flight Services
1. Purpose of This Change. This change transmits revised pages to Federal Aviation Administration Order JO 7110.10Z, Flight Services, and the Briefing Guide.
2. Audience. This change applies to select offices in Washington headquarters, service area offices, the William J. Hughes Technical Center, the Mike Monroney Aeronautical Center, and to all air traffic field facilities, international aviation field offices, and the interested aviation public.
3. Where Can I Find This Change? This change is available on the FAA Web site at http://faa.gov/air_traffic/publications and http://employees.faa.gov/tools_resources/orders_ notices/.
4. Explanation of Policy Change. See the Explanation of Changes attachment which has editorial corrections and changes submitted through normal procedures. The Briefing Guide lists only new or modified material, along with background.
5. Distribution. This change is distributed to select offices in Washington headquarters, service area offices, the William J. Hughes Technical Center, the Mike Monroney Aeronautical Center, and to all air traffic field facilities, international aviation field offices, and the interested aviation public.
6. Disposition of Transmittal. Retain this transmittal until superseded by a new basic order.
7. Page Control Chart. See the page control chart attachment.
Original Signed By: Michael C. Artist
Michael C. Artist Vice President, System Operations Services Air Traffic Organization
Date: August 8, 2018
Change 2, effective September 13, 2018 › Explanation of Changes - Chg. 2
JO 7110.10Z CHG 2 9/13/18
Explanation of Changes E of C−1
Flight Services Explanation of Changes
Change 2
Direct questions through appropriate facility/service center office staff
to the Office of Primary Interest (OPI)
a. 1−1−6. SUBMISSION CUTOFF AND EFFECTIVE DATES
1−1−8. RECOMMENDATIONS FOR PROCEDURAL CHANGES
This change adds language to clarify the submission guidelines for changes to this Order. It changes “Cutoff date for Submission” to “Cutoff date for Completion” to clarify that even after changes are submitted to the correspondence mailbox, several months of coordination are often still required before they are completed and submitted internally for publication. It also adds a Note referencing FAA Order JO 7000.5, Procedures for Submitting Changes to Air Traffic Control Publications.
b. 3−1−4. WEATHER DISPLAY PRODUCTS
4−1−1. INFLIGHT SERVICES
This change includes weather display information that should have been relocated when En Route Advisory Service was terminated in FAA Order JO 7110.10Y, Change 1. This change cancels and incorporates N JO 7110.751.
c. 3−1−8. LOGGING PILOT BRIEFINGS
4−2−3. IFR/VFR/DVFR FLIGHT PLAN RECORDING
6−1−6. IFR/VFR/DVFR FLIGHT PLAN RECORDING
This change supports the standardized use of FAA Form 7233−4, International Flight Plan.
d. 9−2−14. PIREP FORMAT
12−1−8. WEATHER PHRASEOLOGY
This change adds clarity to the meteorological phenomena that is reported by the weather observer distinguishing between small hail and snow pellets.
e. Entire Publication
Additional editorial/format changes were made where necessary. Revision bars were not used because of the insignificant nature of these changes.
Change 3. effective February 28, 2019
Distribution: Electronic Initiated By: AJR-0 Vice President, System Operations Services
CHANGE
U.S. DEPARTMENT OF TRANSPORTATION
FEDERAL AVIATION ADMINISTRATION
JO 7110.10Z
CHG 3 Air Traffic Organization Policy Effective Date: February 28, 2019
SUBJ: Flight Services
1. Purpose of This Change. This change transmits revised pages to Federal Aviation Administration Order JO 7110.10Z, Flight Services, and the Briefing Guide.
2. Audience. This change applies to select offices in Washington headquarters, service area offices, the William J. Hughes Technical Center, the Mike Monroney Aeronautical Center, and to all air traffic field facilities, international aviation field offices, and the interested aviation public.
3. Where Can I Find This Change? This change is available on the FAA Web site at http://faa.gov/air_traffic/publications and http://employees.faa.gov/tools_resources/orders_ notices/.
4. Explanation of Policy Change. See the Explanation of Changes attachment which has editorial corrections and changes submitted through normal procedures. The Briefing Guide lists only new or modified material, along with background.
5. Distribution. This change is distributed to select offices in Washington headquarters, service area offices, the William J. Hughes Technical Center, the Mike Monroney Aeronautical Center, and to all air traffic field facilities, international aviation field offices, and the interested aviation public.
6. Disposition of Transmittal. Retain this transmittal until superseded by a new basic order.
7. Page Control Chart. See the page control chart attachment.
Original Signed By: Michael C. Artist
Michael C. Artist Vice President, System Operations Services Air Traffic Organization
Date: February 6, 2019
Change 3. effective February 28, 2019 › Explanation of Changes - Chg. 3
JO 7110.10Z CHG 3 2/28/19
Explanation of Changes E of C−1
Flight Services Explanation of Changes
Change 3
Direct questions through appropriate facility/service center office staff
to the Office of Primary Interest (OPI)
a. 2−1−1. TYPES OF BROADCASTS
2−1−3. REDUCING RECORDED WEATHER INFORMATION SERVICES
2−3−1. GENERAL
This change documents that Telephone Information Briefing Services (TIBS) will only be provided by Alaska Flight Service Stations. This change cancels and incorporates N JO 7110.760, effective September 13, 2018.
b. 3−2−1. CONDUCT OF STANDARD BRIEFING
This change advises NAS users of updates to FAA publications, reflecting a more accurate means of obtaining IFR route and procedures FDC NOTAM information.
c. 4−3−7. ATC CLEARANCES, ADVISORIES, OR REQUESTS
This change provides instruction to the Flight Data Communications Specialists at the ARTCCs on how to properly obtain and relay clearance requests.
d. 7−1−1. GENERAL
7−2−1. FLIGHT PLAN/CUSTOMS REQUIREMENTS
7−2−2. INBOUND AIRCRAFT: CUSTOMS REQUIREMENTS
7−2−3. INBOUND AIRCRAFT: ADIZ REQUIREMENTS
7−4−1. GENERAL 7−4−2. INBOUNDS FROM CANADA 7−4−3. OUTBOUNDS TO CANADA 7−4−4. OUTBOUNDS TO CANADA DEPARTING FROM OUTSIDE FLIGHT PLAN AREA
7−5−1. GENERAL 7−5−2. INBOUNDS FROM MEXICO 7−5−3. OUTBOUNDS TO MEXICO
As a result of the changes cited above in the U.S. customs notifications procedures, Chapter 7 was modified to remove all references to ADCUS in remarks, provide guidance and a link to the CBP website on the APIS requirements for pilots to coordinate directly with CBP, and to update the sections on Canadian and Mexican trans−border flights.
e. 8−2−1. COMMUNICATIONS SEARCH
8−2−2. QALQ 8−3−1. INREQ 8−4−1. ALNOT
This change removes all references to Direct Users Access Terminal System (DUATS) II contract, including references to vendors CSRA and Lockheed Martin. This system has been terminated and is no longer available to the flying community.
f. 9−2−3. RESPONSIBILITY
9−2−5. SOLICITING PIREPS 9−2−14. PIREP FORMATTING
This change incorporates the ATO’s Top 5 PIREP CAP recommendations, and FAA Order JO 7110.10 contains consistent guidance regarding the solicitation and dissemination of PIREPs. Specifically, it includes requirements for the solicitation of more detailed information regarding cloud ceilings and braking action reports.
g. 9−5−2. AVIATION SURFACE FORECAST/ AVIATION CLOUD FORECAST/ AREA FORECAST (FA) SCHEDULE
9−5−3. AVIATION SURFACE FORECAST AND AVIATION CLOUD FORECAST ISSUANCE TIMES
This change removes incorrect headers from Section 9−5−2 and TBL 9−5−2 and also removes the incorrect distribution information in Section 9−5−3. This change cancels and incorporates N JO 7110.759, effective September 5, 2018.
JO 7110.10Z CHG 3 2/28/19
E of C−2 Explanation of Changes
h. APPENDIX A. INSTRUCTIONS FOR THE COMPLETION OF THE FLIGHT PLAN FORM
This change removes the “Reserved for RCP” description for the P−Code and includes the P−Code equipment definitions. Additionally, this change adds guidance for the filing of Required Surveillance Performance (RSP) information in Item 18 of the flight plan. This is in conjunction with changes to the United States (U.S.), Aeronautical Information Man-
ual Table 5−1−4 and the U.S. Aeronautical Information Publication ENR 1.10 12.5.
i. EDITORIALS
Editorial changes include an update to DEN information in paragraph 5−2−13 as well as a reference correction in paragraph 4−1−1.
j. Entire Publication
Additional editorial/format changes were made where necessary. Revision bars were not used because of the insignificant nature of these changes.
Table of Contents
JO 7110.10Z CHG 3 2/28/19
i Table of Contents
Table of Contents
Chapter 1. General
Section 1. Introduction
Paragraph Page 1−1−1. PURPOSE OF THIS ORDER 1−1−1 … 1−1−2. AUDIENCE 1−1−1 … 1−1−3. WHERE TO FIND THIS ORDER 1−1−1 … 1−1−4. WHAT THIS ORDER CANCELS 1−1−1 … 1−1−5. EXPLANATION OF CHANGES 1−1−1 … 1−1−6. EFFECTIVE DATES AND SUBMISSIONS FOR CHANGES 1−1−1 … 1−1−7. DELIVERY DATES 1−1−1 … 1−1−8. RECOMMENDATIONS FOR PROCEDURAL CHANGES 1−1−1 … 1−1−9. SUBSCRIPTION INFORMATION 1−1−2 … 1−1−10. DISTRIBUTION 1−1−2 …
Section 2. Terms of Reference
1−2−1. WORD MEANINGS 1−2−1 … 1−2−2. NOTES 1−2−1 … 1−2−3. EXAMPLES 1−2−1 … 1−2−4. PHRASEOLOGY 1−2−1 … 1−2−5. ABBREVIATIONS 1−2−1 … 1−2−6. JO 7110.10 CHANGES 1−2−1 … 1−2−7. SYSTEM INSTRUCTIONS 1−2−2 …
Section 3. Responsibility
1−3−1. PROCEDURAL APPLICATIONS 1−3−1 … 1−3−2. DUTY PRIORITY 1−3−1 … 1−3−3. DUTY FAMILIARIZATION AND TRANSFER OF POSITION RESPONSIBILITY 1−3−1
Chapter 2. Broadcast Procedures
Section 1. General
2−1−1. TYPES OF BROADCASTS 2−1−1 … 2−1−2. SPEECH RATE AND PHRASEOLOGY 2−1−1 … 2−1−3. REDUCING RECORDED WEATHER INFORMATION SERVICES 2−1−1 … 2−1−4. CURRENT DATA 2−1−1 … 2−1−5. AUTOMATED BROADCAST 2−1−1 …
Section 2. Transcribed Weather Broadcasts (TWEB) (Alaska Only)
2−2−1. GENERAL 2−2−1 … 2−2−2. CONTENT 2−2−1 … 2−2−3. TESTING TWEB EQUIPMENT 2−2−2 … 2−2−4. SERVICE MAY BE SUSPENDED 2−2−2 … 2−2−5. MONITORING 2−2−2 …
Section 3. Telephone Information Briefing Service (TIBS)
2−3−1. GENERAL 2−3−1 …
JO 7110.10Z CHG 3 2/28/19
ii Table of Contents
Paragraph Page 2−3−2. AREA/ROUTE BRIEFING PROCEDURES 2−3−1 … 2−3−3. MONITORING 2−3−2 …
Section 4. Hazardous Inflight Weather Advisory Service (HIWAS)
2−4−1. GENERAL 2−4−1 … 2−4−2. PRIORITY 2−4−1 … 2−4−3. CONTENT 2−4−1 … 2−4−4. BROADCAST PROCEDURES 2−4−1 … 2−4−5. SUSPENSION 2−4−2 …
Section 5. Automatic Flight Information Service (AFIS) (Alaska Only)
2−5−1. AUTOMATIC FLIGHT INFORMATION SERVICE (AFIS) 2−5−1 …
Chapter 3. Pilot Briefing
Section 1. General
3−1−1. DEFINITION 3−1−1 … 3−1−2. PRE-DUTY REQUIREMENTS 3−1−1 … 3−1−3. PREFLIGHT BRIEFING DISPLAY 3−1−1 … 3−1−4. WEATHER DISPLAY PRODUCTS 3−1−1 … 3−1−5. FORECASTS, WARNINGS, AND ADVISORIES 3−1−2 … 3−1−6. UNAVAILABILITY OF DATA 3−1−3 … 3−1−7. TYPE OF BRIEFING TO BE CONDUCTED 3−1−3 … 3−1−8. LOGGING PILOT BRIEFINGS 3−1−3 …
Section 2. Preflight Pilot Briefing
3−2−1. CONDUCT OF STANDARD BRIEFING 3−2−1 … 3−2−2. CONDUCT OF ABBREVIATED BRIEFING 3−2−2 … 3−2−3. CONDUCT OF OUTLOOK BRIEFING 3−2−3 …
Chapter 4. Inflight Services
Section 1. General
4−1−1. INFLIGHT SERVICES 4−1−1 … 4−1−2. OPERATIONAL PRIORITY 4−1−1 … 4−1−3. INFLIGHT WEATHER BRIEFING 4−1−1 … 4−1−4. INFLIGHT EQUIPMENT MALFUNCTIONS 4−1−1 … 4−1−5. AIRCRAFT REPORTED MALFUNCTIONS 4−1−1 … 4−1−6. NAVAID FLIGHT CHECK 4−1−2 …
Section 2. Data Recording
4−2−1. TYPES OF DATA RECORDED 4−2−1 … 4−2−2. METHODS OF RECORDING DATA 4−2−1 … 4−2−3. IFR/VFR/DVFR FLIGHT PLAN RECORDING 4−2−2 … 4−2−4. FLIGHT PROGRESS STRIPS (FAA FORMS 7230-21 AND 7233-5) 4−2−2 … 4−2−5. FLIGHT PROGRESS STRIPS AND ENTRY DATA 4−2−2 … 4−2−6. AIRCRAFT CONTACTS 4−2−6 …
JO 7110.10Z CHG 3 2/28/19
iii Table of Contents
Section 3. Radio Communications
Paragraph Page 4−3−1. FREQUENCY USE 4−3−1 … 4−3−2. AUTHORIZED TRANSMISSIONS 4−3−1 … 4−3−3. RADIO MESSAGE FORMAT 4−3−1 … 4−3−4. ABBREVIATED TRANSMISSION 4−3−2 … 4−3−5. ROUTINE RADIO CONTACTS 4−3−2 … 4−3−6. RADIO COMMUNICATIONS TRANSFER 4−3−4 … 4−3−7. ATC CLEARANCES, ADVISORIES, OR REQUESTS 4−3−4 … 4−3−8. DEPARTURE REPORTS 4−3−4 … 4−3−9. IFR FLIGHT PROGRESS REPORTS 4−3−5 … 4−3−10. ARRIVAL/MISSED APPROACH REPORTS 4−3−5 … 4−3−11. NONDELIVERY OF MESSAGES 4−3−5 … 4−3−12. BROADCAST (BLIND TRANSMISSION) OF MESSAGES 4−3−5 … 4−3−13. PENETRATION OF CLASS A AIRSPACE OR PROHIBITED/RESTRICTED AREA 4−3−5 …
Section 4. Airport Advisory Services (Alaska Only)
4−4−1. TYPES OF AIRPORT ADVISORY SERVICES 4−4−1 … 4−4−2. GENERAL 4−4−1 … 4−4−3. AIRPORT ADVISORY/RAIS ELEMENTS AND PHRASEOLOGY 4−4−2 … 4−4−4. CHARTS 4−4−4 … 4−4−5. AUTHORIZED FREQUENCIES 4−4−4 … 4−4−6. TRAFFIC CONTROL 4−4−5 … 4−4−7. AIRCRAFT EQUIPMENT CHECKS 4−4−5 …
Section 5. Special VFR Operation
4−5−1. AUTHORIZATION 4−5−1 … 4−5−2. REQUESTS FOR SPECIAL VFR CLEARANCE 4−5−1 … 4−5−3. VISIBILITY BELOW 1 MILE 4−5−2 … 4−5−4. PREDESIGNED SPECIAL VFR CLEARANCES 4−5−3 …
Chapter 5. Emergency Services
Section 1. General
5−1−1. EMERGENCY DETERMINATION 5−1−1 … 5−1−2. RESPONSIBILITY 5−1−1 … 5−1−3. OBTAINING INFORMATION 5−1−1 … 5−1−4. COORDINATION 5−1−1 … 5−1−5. PROVIDING ASSISTANCE 5−1−1 … 5−1−6. RECORDING INFORMATION 5−1−2 … 5−1−7. SAFE ALTITUDES FOR ORIENTATIONS 5−1−2 …
Section 2. Operations
5−2−1. INFORMATION REQUIREMENTS 5−2−1 … 5−2−2. FREQUENCY CHANGES 5−2−1 … 5−2−3. AIRCRAFT ORIENTATION 5−2−1 … 5−2−4. ALTITUDE CHANGE FOR IMPROVED RECEPTION 5−2−1 … 5−2−5. ALERTING CONTROL FACILITY 5−2−1 …
JO 7110.10Z CHG 3 2/28/19
iv Table of Contents
Paragraph Page 5−2−6. VFR AIRCRAFT IN WEATHER DIFFICULTY 5−2−1 … 5−2−7. AIRCRAFT POSITION PLOTS 5−2−2 … 5−2−8. EMERGENCY LOCATOR TRANSMITTER (ELT) SIGNALS 5−2−2 … 5−2−9. EXPLOSIVE CARGO 5−2−2 … 5−2−10. EXPLOSIVE DETECTION DOG HANDLER TEAMS 5−2−2 … 5−2−11. INFLIGHT EQUIPMENT MALFUNCTIONS 5−2−3 … 5−2−12. MINIMUM FUEL 5−2−3 … 5−2−13. AIRCRAFT BOMB THREATS 5−2−3 … 5−2−14. EMERGENCY SECURITY CONTROL OF AIR TRAFFIC (ESCAT) 5−2−4 …
Section 3. ADF/VOR Orientation
5−3−1. ACTIONS REQUIRED 5−3−1 … 5−3−2. GENERAL 5−3−1 … 5−3−3. VOR ORIENTATION/VOR CROSS-FIX 5−3−2 … 5−3−4. GUIDANCE TO AIRPORT 5−3−4 …
Section 4. Global Positioning System (GPS)
5−4−1. ACTIONS REQUIRED 5−4−1 … 5−4−2. GPS ORIENTATION 5−4−1 … 5−4−3. GUIDANCE TO AIRPORT 5−4−1 …
Chapter 6. Flight Data
Section 1. General
6−1−1. COMMUNICATIONS SERVICE 6−1−1 … 6−1−2. FLIGHT PLANS 6−1−1 … 6−1−3. FLIGHT PLAN DATA 6−1−2 … 6−1−4. TYPES OF DATA RECORDED 6−1−2 … 6−1−5. METHODS OF RECORDING DATA 6−1−2 … 6−1−6. IFR/VFR/DVFR FLIGHT PLAN RECORDING 6−1−3 … 6−1−7. PART-TIME FSS CLOSURE ACTION 6−1−3 … 6−1−8. TELEPHONE REQUESTS FOR ATC CLEARANCES 6−1−3 …
Section 2. Flight Plan Proposals
6−2−1. FLIGHT PLAN RECORDING 6−2−1 … 6−2−2. OUTBOUNDS DEPARTING FROM OUTSIDE FLIGHT PLAN AREA 6−2−3 … 6−2−3. FLIGHT PLANS WITH AREA NAVIGATION (RNAV) ROUTES IN DOMESTIC U.S. AIRSPACE 6−2−4 …
Section 3. IFR Flight Plan Handling
6−3−1. IFR FLIGHT PLANS 6−3−1 … 6−3−2. NOTIFYING ARTCC 6−3−1 … 6−3−3. IFR FLIGHT PLAN CONTROL MESSAGES 6−3−1 … 6−3−4. IFR FLIGHT PLAN CONTROL MESSAGE FORMAT 6−3−2 … 6−3−5. ADDITIONAL MESSAGES 6−3−6 … 6−3−6. COORDINATE RNAV ROUTES 6−3−8 …
Section 4. Flight Plan Handling
6−4−1. FLIGHT PLAN ACTIVATION 6−4−1 …
JO 7110.10Z CHG 3 2/28/19
v Table of Contents
Paragraph Page 6−4−2. DEPARTURE REPORT MESSAGE 6−4−1 … 6−4−3. ACKNOWLEDGING NUMBERED MESSAGES 6−4−1 … 6−4−4. FLIGHT NOTIFICATION MESSAGE 6−4−1 … 6−4−5. SUSPENDING FLIGHT NOTIFICATION MESSAGES 6−4−2 … 6−4−6. ACKNOWLEDGING FLIGHT NOTIFICATION MESSAGES 6−4−3 … 6−4−7. ACTION BY ADDRESSEES 6−4−3 … 6−4−8. MAJOR FLIGHT PLAN CHANGES FROM EN ROUTE AIRCRAFT 6−4−3 … 6−4−9. CHANGE IN ETA 6−4−4 … 6−4−10. FLIGHT PLAN CLOSURE 6−4−4 … 6−4−11. MILITARY FLIGHTS TO/FROM U.S. 6−4−5 …
Section 5. Military Operations
6−5−1. SPECIAL MILITARY FLIGHTS 6−5−1 … 6−5−2. MILITARY FOREIGN FLIGHTS 6−5−1 … 6−5−3. USAF/USN UNDERGRADUATE PILOTS 6−5−1 … 6−5−4. MESSAGE HANDLING 6−5−1 …
Section 6. IFR/DVFR ADIZ Flight Plans
6−6−1. AIRCRAFT MOVEMENT INFORMATION SERVICES (AMIS) WITHIN AN ADIZ-IFR 6−6−1 … 6−6−2. AMIS WITHIN AN ADIZ-DVFR 6−6−1 … 6−6−3. FORWARDING DVFR INFORMATION 6−6−1 … 6−6−4. STOPOVER DVFR FLIGHT PLANS 6−6−1 …
Section 7. Law Enforcement Messages
6−7−1. LAW ENFORCEMENT ALERT MESSAGES (LEAM) 6−7−1 … 6−7−2. INITIATING LEAMS 6−7−1 …
Section 8. Non−Emergency Parachute Jumping
6−8−1. COORDINATION 6−8−1 … 6−8−2. PRE-JUMP RADIO COMMUNICATIONS 6−8−1 …
Section 9. SECURITY NOTICE (SECNOT)
6−9−1. SECURITY NOTICE (SECNOT) 6−9−1 … 6−9−2. ACTION UPON RECEIVING A SECNOT 6−9−1 … 6−9−3. CANCELING A SECNOT 6−9−1 …
Chapter 7. International Operations
Section 1. Messages and Formats
7−1−1. GENERAL 7−1−1 … 7−1−2. AIR TRAFFIC SERVICE (ATS) MESSAGES 7−1−2 … 7−1−3. CATEGORIES OF MESSAGES 7−1−2 … 7−1−4. SERVICE MESSAGES 7−1−2 … 7−1−5. TRANSMISSION VIA NADIN 7−1−2 … 7−1−6. TRANSMISSION OF ATS MESSAGES 7−1−3 … 7−1−7. ORIGINATING MESSAGES 7−1−4 …
JO 7110.10Z CHG 3 2/28/19
vi Table of Contents
Paragraph Page 7−1−8. ADDRESSING MESSAGES 7−1−4 … 7−1−9. FLIGHT PLAN FORMS AND INSTRUCTIONS 7−1−5 … 7−1−10. ICAO ATS MESSAGE FORMAT 7−1−5 … 7−1−11. FLIGHT PLAN CHANGES AND CANCELLATIONS 7−1−5 … 7−1−12. AIR MOBILE SERVICE (AMS) 7−1−5 … 7−1−13. AIREPS (POSITION REPORTS) 7−1−6 … 7−1−14. AIREP SPECIALS (ARS) 7−1−9 … 7−1−15. ARTCC RELAY OF VFR MESSAGES 7−1−9 …
Section 2. Customs Notification and ADIZ Requirements
7−2−1. FLIGHT PLAN/CUSTOMS REQUIREMENTS 7−2−1 … 7−2−2. CUSTOMS REQUIREMENTS FOR INBOUND AND OUTBOUND AIRCRAFT 7−2−1 . . 7−2−3. ADIZ REQUIREMENTS FOR INBOUND AND OUTBOUND AIRCRAFT 7−2−1 …
Section 3. Alerting Service
7−3−1. GENERAL 7−3−1 … 7−3−2. ALERTING PHASES 7−3−1 … 7−3−3. ALERTING MESSAGE CONTENTS 7−3−1 …
Section 4. Canadian Movement and Control Messages
(Transborder Flights Only)
7−4−1. GENERAL 7−4−1 … 7−4−2. INBOUNDS FROM CANADA 7−4−1 … 7−4−3. OUTBOUNDS TO CANADA 7−4−1 … 7−4−4. OUTBOUNDS TO CANADA DEPARTING FROM OUTSIDE FLIGHT PLAN AREA 7−4−3 … 7−4−5. IFR FLIGHT PLANS DEPARTING CANADIAN AIRPORTS 7−4−3 … 7−4−6. SEARCH AND RESCUE MESSAGES 7−4−3 …
Section 5. Mexican Movement and Control Messages
(Transborder Flights Only)
7−5−1. GENERAL 7−5−1 … 7−5−2. INBOUNDS FROM MEXICO 7−5−1 … 7−5−3. OUTBOUNDS TO MEXICO 7−5−1 …
Chapter 8. Search and Rescue (SAR) Procedures
Section 1. General
8−1−1. RESPONSIBILITY FOR SAR ACTION 8−1−1 … 8−1−2. OVERDUE AIRCRAFT ON FLIGHT PLAN 8−1−1 … 8−1−3. OVERDUE AIRCRAFT NOT ON FLIGHT PLAN 8−1−1 …
Section 2. Overdue Aircraft Action
8−2−1. COMMUNICATIONS SEARCH 8−2−1 … 8−2−2. QALQ 8−2−1 … 8−2−3. ACTION BY DEPARTURE STATION ON RECEIPT OF QALQ 8−2−1 … 8−2−4. CANCELLATION OF THE QALQ 8−2−2 …
Section 3. Information Requests (INREQs)
8−3−1. INREQ 8−3−1 …
JO 7110.10Z CHG 3 2/28/19
vii Table of Contents
Paragraph Page 8−3−2. ACTION UPON RECEIPT OF INREQ 8−3−1 … 8−3−3. CANCELLATION OF INREQ 8−3−1 …
Section 4. Alert Notices (ALNOTs)
8−4−1. ALNOT 8−4−1 … 8−4−2. ACTION UPON RECEIPT OF ALNOT 8−4−1 … 8−4−3. REPORTING ALNOT STATUS TO RCC 8−4−1 … 8−4−4. CANCELLATION OF ALNOT 8−4−2 …
Section 5. Other SAR Actions
8−5−1. CANADIAN TRANSBORDER 8−5−1 …
Chapter 9. FAA Weather Services
Section 1. General
9−1−1. INTRODUCTION 9−1−1 … 9−1−2. SCHEDULED TRANSMISSION TIMES 9−1−1 … 9−1−3. DISTRIBUTION 9−1−1 …
Section 2. Pilot Weather Report (UA/UUA)
9−2−1. GENERAL 9−2−1 … 9−2−2. PREPARATION FOR TRANSMISSION 9−2−1 … 9−2−3. RESPONSIBILITY 9−2−1 … 9−2−4. PIREP DISPLAY 9−2−1 … 9−2−5. SOLICITING PIREPS 9−2−1 … 9−2−6. DATA TO BE INCLUDED IN PIREPS 9−2−2 … 9−2−7. REPORTING TURBULENCE IN PIREPS 9−2−2 … 9−2−8. REPORTING ICING CONDITIONS IN PIREPS 9−2−2 … 9−2−9. MEANS USED TO SOLICIT PIREPS 9−2−2 … 9−2−10. PIREP CLASSIFICATION 9−2−3 … 9−2−11. PIREP HANDLING 9−2−3 … 9−2−12. OFFSHORE COASTAL ROUTES 9−2−3 … 9−2−13. PIREP PREPARATION 9−2−3 … 9−2−14. PIREP FORMAT 9−2−4 … 9−2−15. PIREP ENCODING 9−2−8 …
Section 3. Wind and Temperature Aloft Forecast (FB)
9−3−1. GENERAL 9−3−1 … 9−3−2. LEVELS FORECAST 9−3−1 … 9−3−3. DISTRIBUTION 9−3−1 …
Section 4. Terminal Aerodrome Forecast (TAF)
9−4−1. GENERAL 9−4−1 … 9−4−2. TERMINAL AERODROME FORECAST SCHEDULES 9−4−1 …
Section 5. Aviation Surface Forecast/Aviation Cloud Forecast/Area
Forecast (FA)
9−5−1. GENERAL 9−5−1 …
JO 7110.10Z CHG 3 2/28/19
viii Table of Contents
Paragraph Page 9−5−2. AREA FORECAST (FA) SCHEDULE 9−5−1 … 9−5−3. AVIATION SURFACE FORECAST AND AVIATION CLOUD FORECAST ISSUANCE TIMES 9−5−2 …
Section 6. Severe Weather Forecasts
9−6−1. GENERAL 9−6−1 … 9−6−2. DISTRIBUTION 9−6−1 … 9−6−3. CONVECTIVE OUTLOOK NARRATIVE (AC) 9−6−1 …
Section 7. Flight Advisories (SIGMET/WS−Airmet/WA−Convective SIGMET/WST)
9−7−1. GENERAL 9−7−1 … 9−7−2. DISTRIBUTION 9−7−1 …
Section 8. Center Weather Advisory (CWA)
9−8−1. GENERAL 9−8−1 … 9−8−2. CRITERIA 9−8−1 … 9−8−3. DISTRIBUTION 9−8−1 …
Chapter 10. Airport Lighting and Visibility Aids
(Alaska Only)
Section 1. General
10−1−1. AIRPORT LIGHTING 10−1−1 … 10−1−2. OBSTRUCTION LIGHTS 10−1−1 … 10−1−3. ROTATING BEACON 10−1−1 … 10−1−4. APPROACH LIGHTS 10−1−1 … 10−1−5. APPROACH LIGHTING SYSTEM NTENSITY SETTINGS (ALS) 10−1−1 … 10−1−6. SEQUENCED FLASHING LIGHTS (SFL) 10−1−1 … 10−1−7. RUNWAY EDGE LIGHTS 10−1−2 … 10−1−8. CHANGING LIGHTED RUNWAYS 10−1−2 … 10−1−9. MEDIUM INTENSITY APPROACH LIGHTING SYSTEM WITH RUNWAY ALIGNMENT INDICATOR LIGHTS (MALSR)/OMNIDIRECTIONAL APPROACH LIGHTING SYSTEM (ODALS) 10−1−2 … 10−1−10. HIGH INTENSITY RUNWAY LIGHTS (HIRL) ASSOCIATED WITH MALSR 10−1−2 . 10−1−11. MEDIUM INTENSITY RUNWAY LIGHTS (MIRL) 10−1−3 … 10−1−12. HIGH INTENSITY RUNWAY, RUNWAY CENTERLINE (RCLS), AND TOUCHDOWN ZONE LIGHTS (TDZL) 10−1−3 … 10−1−13. HIRL CHANGES AFFECTING RVR 10−1−3 … 10−1−14. HIGH SPEED TURNOFF LIGHTS 10−1−3 … 10−1−15. RUNWAY END IDENTIFIER LIGHTS (REIL) 10−1−3 … 10−1−16. TAXIWAY LIGHTS 10−1−3 … 10−1−17. VISUAL APPROACH SLOPE INDICATORS (VASIS) 10−1−4 … 10−1−18. VISIBILITY AIDS - GENERAL 10−1−4 … 10−1−19. RVR/RVV 10−1−4 … 10−1−20. OPERATION OF LANDING DIRECTION INDICATOR 10−1−5 …
Chapter 11. Interphone Communications
Section 1. General
11−1−1. PURPOSE 11−1−1 …
JO 7110.10Z CHG 3 2/28/19
ix Table of Contents
Paragraph Page 11−1−2. INTERPHONE TRANSMISSION PRIORITIES 11−1−1 … 11−1−3. PRIORITY INTERRUPTION 11−1−1 … 11−1−4. MESSAGE INITIATION 11−1−1 … 11−1−5. MESSAGE TERMINATION 11−1−1 …
Chapter 12. Phraseology
Section 1. General
12−1−1. PURPOSE 12−1−1 … 12−1−2. PHRASEOLOGY 12−1−1 … 12−1−3. WORDS AND PHRASES 12−1−1 … 12−1−4. ANNOUNCING MISSING ITEMS 12−1−1 … 12−1−5. ICAO PHONETICS 12−1−1 … 12−1−6. RELAY OF ATC COMMUNICATIONS 12−1−2 … 12−1−7. EXPEDITIOUS COMPLIANCE 12−1−2 … 12−1−8. WEATHER PHRASEOLOGY 12−1−2 … 12−1−9. WEATHER REMARKS 12−1−6 … 12−1−10. WEATHER ADVISORIES 12−1−8 … 12−1−11. RADAR 12−1−9 … 12−1−12. WINDS AND TEMPERATURES ALOFT FORECAST (FB) 12−1−9 … 12−1−13. NUMBER USAGE 12−1−9 … 12−1−14. FACILITY IDENTIFICATION 12−1−11 … 12−1−15. AIRCRAFT IDENTIFICATION 12−1−12 … 12−1−16. DESCRIPTION OF AIRCRAFT TYPES 12−1−15 … 12−1−17. AIRCRAFT EQUIPMENT CODES 12−1−15 … 12−1−18. AIRWAYS AND ROUTES 12−1−15 … 12−1−19. NAVAID TERMS 12−1−16 … 12−1−20. NAVAID FIXES 12−1−16 … 12−1−21. RUNWAY CONDITIONS 12−1−16 …
Chapter 13. Data Communication Systems
Section 1. General
13−1−1. TYPES OF DATA ACCEPTABLE ON FAA DATA COMMUNICATIONS SYSTEMS 13−1−1 … 13−1−2. PRIORITY MESSAGES 13−1−1 … 13−1−3. GROUP CODES 13−1−1 … 13−1−4. MESSAGE FORMATS 13−1−2 … 13−1−5. WMSCR NEGATIVE RESPONSE MESSAGES 13−1−3 … 13−1−6. Q SIGNALS 13−1−3 …
Appendices
APPENDIX A. ICAO FLIGHT PLANS Appendix A−1 … APPENDIX B. FSS FORM Appendix B−1 … INDEX I−1 … PILOT/CONTROLLER GLOSSARY PCG −1 …
1−1−1 Introduction
Chapter 1. General
Section 1. Introduction
1−1−1. PURPOSE OF THIS ORDER
This order prescribes procedures and phraseology for use by air traffic personnel providing flight services. Flight service specialists 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 that are not covered.
Chapter 1. General › Section 1. Introduction
1−1−2. AUDIENCE
This order applies to all ATO personnel and anyone using ATO directives.
1−1−3. WHERE TO FIND THIS ORDER
This order is available on the FAA Web site at
http://faa.gov/air_traffic/publications &
http://employees.faa.gov/tools_resources/orders_notices/
1−1−4. WHAT THIS ORDER CANCELS
FAA Order JO 7110.10Y, Flight Services, dated December 10, 2015, and all changes to it are canceled.
1−1−5. EXPLANATION OF CHANGES
The significant changes to this order are identified in the Explanation of Changes page(s). It is advisable to retain the page(s) throughout the duration of the basic order. If further information is desired, direct questions through the appropriate facility/service area office staff to Flight Services Safety and Operations Policy Group.
1−1−6. EFFECTIVE DATES AND SUBMISSIONS FOR CHANGES
a. This order and its changes are scheduled to be published to coincide with AIRAC dates, according to the table below.
b. The “Cutoff Date for Completion” in the table below refers to the deadline for a proposed change to be fully coordinated and signed. Change initiators
must submit their proposed changes well in advance of this cutoff date to meet the publication effective date. The process to review and coordinate changes often takes several months after the change is initially submitted.
Publication Schedule
Basic
or Change
Cutoff Date for Coomple-
tion
Effective Date of Publication
JO 7110.10Z 4/27/17 10/12/17
Change 1 10/12/17 3/29/18
Change 2 3/29/18 9/13/18
Change 3 9/13/18 2/28/19
JO 7110.10AA 2/28/19 8/15/19
1−1−7. DELIVERY DATES
This order will be available on the FAA’s website 30 days prior to its effective date.
All organizations are responsible for viewing, downloading, and subscribing to receive electronic mail notifications when changes occur to this order. Subscriptions can be made at: https://www.faa.gov/air_traffic/publications/.
1−1−8. RECOMMENDATIONS FOR PROCEDURAL CHANGES
The responsibility associated with processing and coordinating revisions to this order is delegated to the Director, Air Traffic Procedures, AJV-8.
a. Personnel should submit recommended changes in procedures to facility management.
b. Recommendations from other sources should be submitted through appropriate FAA, military, or industry/user channels.
c. Proposed changes must be submitted electronically to the Air Traffic Procedures Correspondence Mailbox at 9−AJV−8−HQ−[email protected]. The submission should include a description of the
9/13/18 JO 7110.10Z CHG 2
1−1−2 Introduction
recommended change and the proposed language to be used in the order.
NOTE− For details on the submission process as well as additional AJV−8 processing responsibilities, please see FAA Order JO 7000.5, Procedures for Submitting Changes to Air Traffic Control Publications.
d. Procedural changes will not be made to this order until the operational system software has been adapted to accomplish the revised procedures.
1−1−9. SUBSCRIPTION INFORMATION
This publication may be purchased from the U.S. Government Printing Office. Address subscription inquiries to:
Superintendent of Documents U.S. Government Publishing Office P.O. Box 979050 St. Louis, MO 63197−9000 Online: http://bookstore.gpo.gov
FAA air traffic publications are also available on the FAA’s web site at: http://www.faa.gov/air_traffic/publications/
1−1−10. DISTRIBUTION
This order is available online and will be distributed electronically to all offices that subscribe to receive email notification/access to it through the FAA’s website: http://www.faa.gov/air_traffic/publications/
3/15/07 7110.65R CHG 2 JO 7110.10Z CHG 2 9/13/18
Chapter 1. General › Section 2. Terms of Reference
1−2−1 Terms of Reference
Section 2. Terms of Reference
1−2−1. WORD MEANINGS
As used in this order:
a. “Must” means a procedure is mandatory.
b. “Should” means a procedure is recommended.
c. “May” or “need not” means a procedure is optional.
d. “Will” means futurity, not a requirement for application of a procedure.
e. “Must not” means a procedure is prohibited.
f. Singular words include the plural.
g. Plural words include the singular.
h. “Aircraft” means the airframe, crew members, or both.
i. “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. “Time,” when used for ATC operational activities, is the hour and the minute/s in Coordinated Universal Time (UTC). Change to the next minute is made at the minute plus 30 seconds, except time checks are given to the nearest quarter minute. The word “local” or the time zone equivalent must be stated when local time is given during radio and telephone communications. The term “ZULU” may be used to denote UTC.
l. “Sector,” when used in conjunction with flight service station (FSS) functions, means a specifically described geographic area that is assigned a National Airspace Data Interchange Network (NADIN) address.
m. “Tie−in facility,” as indicated in FAA Order JO 7350.9, Location Identifiers, for the purposes of this order, designates the responsible facility/sector for sending/receiving flight plans, flight notification messages, and performing search and rescue duties for the listed location.
n. “Shared database” is a database within an FSS operational system that is accessible by specialists in other geographical locations.
o. “Transmit” means to send data via NADIN or Weather Message Switching Center Replacement (WMSCR) to an outside recipient or to process data internally within an operational system that shares a global database.
p. “Form” means a paper record or an automated equivalent. Both must be retained in accordance with FAA directives.
q. “History files” means one or more digital or paper repositories of data that must be retained in accordance with FAA directives.
r. “Pertinent” means relating directly and significantly to the matter at hand.
1−2−2. NOTES
Statements of fact or of an explanatory nature and relating to the use of directive material have been identified and worded as “Notes.”
1−2−3. EXAMPLES
Any illustration used which serves to explain subject material is identified as an “Example.”
1−2−4. PHRASEOLOGY
Phraseology depicted in this order is mandatory.
NOTE− Exceptions to this paragraph are referenced in Paragraph 5−1−1, Emergency Determination
1−2−5. ABBREVIATIONS
Abbreviations authorized for use in the application of the procedures in this order are those contained in FAA Order JO 7340.2, Contractions.
1−2−6. JO 7110.10 CHANGES
a. Each reprinted, revised, or additional page will show the change number and the effective date of the change.
b. Bold lines in the margin of the text will mark the location of all changes except editorial corrections.
1−2−2 Terms of Reference
1−2−7. SYSTEM INSTRUCTIONS
Different operational systems are used to provide flight services within the United States. Each individual operational system must have instructions in the form of a user’s manual or guide, either
electronically or in paper form, that provide the necessary steps to accomplish the requirements set forth in this order.
Where databases are shared, local procedures may be used to facilitate the handling of flight data across the flight plan area boundaries.
Chapter 1. General › Section 3. Responsibility
1−3−1 Responsibility
Section 3. Responsibility
1−3−1. PROCEDURAL APPLICATIONS
Apply the procedures in this order, except when other procedures are contained in a letter of agreement (LOA) or other appropriate FAA documents, provided they only supplement this order and any standards they specify are not less than those in this order.
NOTE− 1. Pilots are required to abide by applicable provisions of 14 Code of Federal Regulations (14 CFR) or any other pertinent regulations regardless of the application of any procedure in this order.
2. FAA Order JO 7210.3, Facility Operation and Administration, contains administrative instructions pertaining to these letters and documents.
1−3−2. DUTY PRIORITY
Because there are many variables involved, it is impossible to provide a standard list of duty priorities that apply to every situation. Each set of circumstances must be evaluated on its own merit, and when more than one action is required, personnel must exercise their best judgment based on the facts and circumstances known to them. Action which appears most critical from a safety standpoint should be performed first.
a. The following order of duty priorities is offered as a guideline.
1. Emergency Situations. Emergency situations are those where life or property is in immediate danger.
2. Inflight Services. Inflight services are those provided to or affecting aircraft in flight or otherwise operating on the airport surface. This includes services to airborne aircraft, airport advisories, delivery of air traffic control (ATC) clearances, advisories or requests, issuance of military flight advisory messages, notices to airmen (NOTAM), search and rescue (SAR) communications searches, flight plan handling, transcribed or live broadcasts, weather observations, pilot weather reports (PIREP), and pilot briefings.
3. Preflight Services. Preflight services are those which directly affect aircraft operations but
which are provided prior to actual departure and usually by telephone. These include pilot briefings, recorded data, flight plan filing/processing, and aircraft operational reservations.
1−3−3. DUTY FAMILIARIZATION AND TRANSFER OF POSITION RESPONSIBILITY
The transfer of position responsibility must be accomplished in accordance with appropriate facility directives each time the operational responsibility for a position is transferred from one specialist to another. The relieving specialist and the specialist being relieved must share equal responsibility for the completeness and accuracy of the position relief briefing.
a. Purpose. This paragraph prescribes the method and the step-by-step process for conducting a position relief briefing and transferring position responsibility from one specialist to another.
b. Discussion.
1. In all operational facilities, the increase in traffic density and the need for the expeditious movement of air traffic without compromising safety have emphasized the importance of the position relief process. Major problems occur whenever there is a heavy reliance upon memory unsupported by routines or systematic reminders. This procedure addresses the complete task of transferring position responsibility and the associated relief briefing.
2. Position relief unavoidably provides added workload for specialists at the time of relief. The intent of this procedure is to make the transfer of position responsibility take place smoothly and to ensure a complete transfer of information with a minimum amount of workload. The method takes advantage of a self-briefing concept in which the relieving specialist obtains needed status information by reading from the Status Information Areas to begin the relief process. Up-to-the-minute information relating to the provision of flight services to pilots and aircraft in flight requires verbal exchanges between specialists during the relief process. The method also specifies the point when the transfer of position responsibility occurs.
1−3−2 Responsibility
3. In the final part of the relief process, the specialist being relieved monitors and reviews the position to ensure that nothing has been overlooked or incorrectly displayed and that the transfer of position responsibility occurred with a complete briefing.
c. Terms. The following terms are important for a complete understanding of this procedure:
1. Status Information Areas. Manual or automated displays of the current status of position−related equipment and operational conditions or procedures.
2. Written Notes. Manually recorded items of information kept at designated locations on the positions of operation are elements of Status Information Areas.
3. Checklist. An ordered listing of items to be covered in a position relief briefing.
d. Precautions.
1. Specialists involved in the position relief process should not rush or be influenced to rush.
2. During position operation, each item of status information which is or may be an operational factor for the relieving specialist should be recorded as soon as it is operationally feasible so that it will not be forgotten or incorrectly recorded.
3. Extra care should be taken when more than one specialist relieves or is being relieved from a position at the same time; for example, combining or decombining positions.
e. Responsibilities. The specialist being relieved must be responsible for ensuring that any pertinent status information of which he/she is aware is relayed to the relieving specialist and is either:
1. Accurately displayed in the Status Information Areas for which he/she has responsibility, or
2. Relayed to the position having responsibility for accurately displaying the status information. Prior to accepting responsibility for a position, the relieving specialist must be responsible for ensuring that any unresolved questions pertaining to the operation of the position are resolved. The specialists engaged in a position relief must conduct the relief process at the position being relieved, unless other
procedures have been established and authorized by the facility air traffic manager.
f. Step−By−Step Process of Position Relief.
1. Preview of the Position
RELIEVING SPECIALIST
(a) Follow the checklist and review the Status Information Areas.
NOTE− This substep may be replaced by an authorized preduty briefing provided an equivalent review of checklist items is accomplished.
(b) Observe position equipment, operational situation, and the work environment.
(c) Listen to voice communications and observe other operational actions.
(d) Observe current and pending aircraft and vehicular traffic and correlate with flight and other movement information.
(e) Indicate to the specialist being relieved that the position has been previewed and that the verbal briefing may begin.
NOTE− Substeps (b), (c), and (d) may be conducted concurrently or in order.
2. Verbal Briefing
SPECIALIST BEING RELIEVED
(a) Review with the relieving specialist the checklist, Status Information Areas, written notes, and other prescribed sources of information, and advise of known omissions, updates, and inaccuracies. Also, brief the relieving specialist on the abnormal status of items not listed on the Status Information Areas, as well as on any items of special operational interest calling for verbal explanation or additional discussion.
(b) Brief on traffic, if applicable.
(c) Completely answer any questions asked.
(d) Observe overall position operation. If assistance is needed, provide or summon it as appropriate.
(e) Sign off the position in accordance with existing directives or otherwise indicate that the relief process is complete.
1−3−3 Responsibility
REFERENCE− FAA Order JO 7210.3, Para 2-2-4, Duty Familiarization and the Transfer of Position Responsibility FAA Order JO 7210.3, Para 2-2-6, Sign In/Out and On/Off Procedures
RELIEVING SPECIALIST
(f) Ask questions necessary to ensure a complete understanding of the operations situation.
(g) Make a statement or otherwise indicate to the specialist being relieved that position responsibility has been assumed.
(h) Sign on the position unless a facility directive authorizes substep (g) above.
(i) Check, verify, and update the information obtained in steps 1 and 2.
g. Check position equipment in accordance with existing directives.
Chapter 2. Broadcast Procedures › Section 1. General
2−1−1 General
Chapter 2. Broadcast Procedures
Section 1. General
2−1−1. TYPES OF BROADCASTS
Weather and flight information must be broadcast/ recorded by one or more of the following categories:
a. Transcribed Weather Broadcast (TWEB). (Alaska only.)
b. Telephone Information Briefing Service (TIBS). (Alaska only.)
c. Hazardous Inflight Weather Advisory Service (HIWAS).
d. Automatic Flight Information Service (AFIS). (Alaska only.)
2−1−2. SPEECH RATE AND PHRASEOLOGY
a. Data must be spoken such that:
1. The speech rate is not excessive,
2. The enunciation is of the highest quality, and;
3. Each part of the message is easily understood.
b. Standardized procedures and phraseology to be used by FSS personnel and automated equipment are to be conducted in accordance with Chapter 12 Phraseology.
2−1−3. REDUCING RECORDED WEATHER INFORMATION SERVICES
Recorded weather information services in Alaska (TWEB and TIBS) may be reduced during the hours of 1800−0600 local time only. Adjust full broadcast
service times to coincide with daylight hours. When a broadcast period is reduced, record the time the broadcast will be resumed, and advise users to contact flight service for weather briefings and other services.
PHRASEOLOGY− THE TIBS RECORDING IS SUSPENDED. REGULAR RECORDED WEATHER SERVICE WILL BE RESUMED AT (time) ZULU/ (time) LOCAL. FOR PILOT WEATHER BRIEFINGS AND OTHER SERVICES, CONTACT FLIGHT SERVICE (phone number or additional telephone instructions, as appropriate). THE TWEB RECORDING IS SUSPENDED. REGULAR RECORDED WEATHER SERVICE WILL BE RESUMED AT (time) ZULU/ (time) LOCAL. FOR PILOT WEATHER BRIEFING AND OTHER SERVICES CONTACT FLIGHT SERVICE (frequency or phone number, as appropriate)
2−1−4. CURRENT DATA
An aviation surface report is considered current for 1 hour beyond the standard time of observation (H+00) unless superseded by a special or local observation or by the next hourly report. Do not broadcast obsolete data.
2−1−5. AUTOMATED BROADCAST
Most broadcasts are automated products that are available 24 hours a day. The products must adhere to the requirements of this chapter. Specialists are responsible for monitoring the product for accuracy, speech rate, and proper enunciation before it is transmitted.
2/28/19 JO 7110.10Z CHG 3
Chapter 2. Broadcast Procedures › Section 2. Transcribed Weather Broadcasts (TWEB) (Alaska Only)
2−2−1 Transcribed Weather Broadcasts (TWEB) (Alaska Only)
Section 2. Transcribed Weather Broadcasts (TWEB)
(Alaska Only)
2−2−1. GENERAL
a. Transcribed weather broadcast service provides continuous aeronautical and meteorological information on low or medium frequency (L/MF) and very high frequency omnidirectional range (VOR) facilities.
b. At TWEB equipment locations controlling two or more VORs, the one used least for ground−to−air communications, preferably the nearest VOR, may be used as a TWEB outlet simultaneously with the nondirectional radio beacon (NDB) facility. Where this is accomplished, capability to manually override the broadcast must be provided for emergency communications.
2−2−2. CONTENT
The sequence, source, and content of transcribed broadcast material must be:
a. Introduction. State the location and preparation time.
PHRASEOLOGY− (location) TRANSCRIBED AVIATION WEATHER BROADCAST PREPARED AT (time) ZULU.
b. Adverse Conditions. Extracted from convective significant meteorological information (SIG- MET) (WST), SIGMET (WS), Airmen’s Meteorological Information (AIRMET), AIRMET (WA), Center Weather Advisory (CWA), and Alert Weather Watch (AWW).
PHRASEOLOGY− WEATHER ADVISORIES ARE IN EFFECT FOR (adverse conditions) OVER (geographical area) (list weather advisories only, no text).
c. Synopsis. A brief statement describing the type, location, and movement of weather systems and/or masses which might affect the route or the area.
d. Terminal Forecasts. Include the valid time of forecast.
PHRASEOLOGY− TERMINAL FORECAST FOR (location) VALID UNTIL (time) ZULU.
e. Winds Aloft Forecast. Broadcast winds aloft forecast for the location nearest to the TWEB. The broadcast should include the levels from 3,000 to 12,000 feet but must always include at least two forecast levels above the surface.
PHRASEOLOGY− WINDS ALOFT FORECAST VALID UNTIL (time) ZULU. (Location) (Altitude) (direction) AT (speed).
f. Surface Weather Reports. Record surface reports as described in paragraph 12-1-8, Weather Phraseology.
1. Broadcast local reports first, then broadcast the remainder of the reports beginning with the first station east of true north and continuing clockwise around the TWEB location.
2. Announce the location name of a surface report once.
(a) Surface weather broadcast introduction:
PHRASEOLOGY− (Location name) AVIATION WEATHER, (4 digits of time), ZULU OBSERVATIONS.
(b) Special weather reports:
PHRASEOLOGY− (Location name) SPECIAL REPORT (last 2 digits of time) OBSERVATION, (weather report).
g. Density Altitude. Include temperature and the statement “Check Density Altitude” as part of the surface weather broadcast for any station with a field elevation of 2,000 feet MSL or above that meets the following criteria: (See TBL 2−2−1.)
TBL 2−2−1 Density Altitude
Field Elevation Temperature (C) 2,000−2,999 29 degrees or higher 3,000−3,999 27 degrees or higher 4,000−4,999 24 degrees or higher 5,000−5,999 21 degrees or higher 6,000−6,999 18 degrees or higher 7,000−higher 16 degrees or higher
h. PILOT WEATHER REPORTS
Summarize PIREPs and, if the weather conditions meet solicitation requirements, append a request for PIREPs.
2−2−2 Transcribed Weather Broadcasts (TWEB) (Alaska Only)
PHRASEOLOGY− PILOT REPORT OF WEATHER CONDITIONS AT (text).
i. Alert Notice (ALNOT) Alert Announcement, if applicable.
PHRASEOLOGY− OVERDUE AIRCRAFT ALERT, (time) ZULU (aircraft identification), (color), (type), DEPARTED (airport) VIA (route), (destination). LAST KNOWN POSITION (state last known position). THIS AIRCRAFT IS OVERDUE. ALL AIRCRAFT ARE REQUESTED TO MONITOR ONE TWO ONE POINT FIVE FOR E−L−T SIGNAL. INFORM THE NEAREST F−A−A FACILITY OF ANY INFORMATION REGARDING THIS AIRCRAFT.
j. Closing statement.
PHRASEOLOGY− PILOT WEATHER REPORTS ARE REQUESTED. FOR NOTAM, MILITARY TRAINING ACTIVITY, OR OTHER SERVICES, CONTACT A FLIGHT SERVICE STATION.
2−2−3. TESTING TWEB EQUIPMENT
When TWEB equipment is to be tested, broadcast an advisory to this effect. Ensure no obsolete information is broadcast during a testing period.
2−2−4. SERVICE MAY BE SUSPENDED
TWEB service may be suspended:
a. For routine maintenance only during periods when weather conditions within 100 miles of the broadcast outlet are equal to or better than a ceiling of 3,000 feet and visibility of 5 miles.
b. When the equipment fails. If a malfunction occurs in the recording or control unit but the tape transport unit remains operative, continue broadcasting current data. Remove data as it becomes obsolete.
2−2−5. MONITORING
a. At TWEB equipment locations, listen to at least one complete TWEB cycle each hour. Check for completeness, accuracy, speech rate, and proper enunciation. Correct any noted irregularities.
b. If practical:
1. The control facility must monitor the transmissions through local outlet.
2. The FSS associated with a remote outlet must monitor the transmissions for a sufficient period each hour to assure voice quality and clarity.
c. Promptly correct or inform the TWEB facility of any irregularities.
Chapter 2. Broadcast Procedures › Section 3. Telephone Information Briefing Service (TIBS)
2−3−1 Telephone Information Briefing Service (TIBS)
Section 3. Telephone Information Briefing Service
(TIBS)
2−3−1. GENERAL
a. TIBS provides a continuous telephone recording of meteorological and/or aeronautical information.
1. TIBS must contain:
(a) Area and/or route briefings.
(b) Airspace procedures, if applicable.
(c) Special announcements, if applicable.
2. TIBS should also contain, but not be limited to:
(a) Surface observations (METAR).
(b) Terminal forecasts (TAF).
(c) Winds/temperatures aloft forecasts.
NOTE− User needs should dictate the content of these recordings.
b. Each FSS sector/flight plan area must provide at least four route and/or area weather briefings. As a minimum, area briefings should encompass a 50 NM radius. Each briefing should require the pilot to access no more than two channels which must be route and/or area specific.
c. Separate channels must be designated for each route area, local meteorological/aeronautical information, special event, airspace procedures, etc.
EXAMPLE− 11 Special Announcements 12 Route FAI to GAL 13 Route FAI to AKP 14 Route FAI to FYU 17 Current Weather – FAI−ANC 18 Current Weather −Interior AK.
2−3−2. AREA/ROUTE BRIEFING PROCEDURES
Service is provided 24 hours a day, but may be reduced in accordance with Paragraph 2−1−3. Recorded information must be updated as conditions change.
a. Introduction. State the preparation time and the route and/or the area of coverage. The service area
may be configured to meet the individual facility’s needs; for example, 50 NM radius, route oriented.
NOTE− For the purpose of TIBS broadcasts, an area briefing may be a geographic location not defined by a nautical mile radius, for example, NORTHWEST NEBRASKA.
PHRASEOLOGY− THIS RECORDING PREPARED AT (time) LOCAL or (time) ZULU. BRIEFING SUMMARY FOR: A (number of miles) NAUTICAL MILE RADIUS OF (location),
or (location not defined by nautical mile radius),
or THE ROUTE FROM (location) TO (location).
b. Weather Advisories. Include WST, WS, WA, CWA, AWW, urgent PIREP (UUA), and any other available meteorological information that may adversely affect flight in the route/area.
PHRASEOLOGY− WEATHER ADVISORIES ARE IN EFFECT FOR (adverse conditions) OVER (geographic area) (text).
c. VFR Not Recommended (VNR) Statement. Include this recommendation when current or forecast conditions, surface or aloft, would make flight under visual flight rules doubtful.
PHRASEOLOGY− V−F−R FLIGHT NOT RECOMMENDED (location) DUE TO (conditions).
d. Synopsis. A brief statement describing the type, location, and movement of weather systems and/or masses which might affect the route or the area. This element may be combined with adverse conditions and/or the VNR element, in any order, when it will help to more clearly describe conditions.
e. Current Conditions. Include current weather conditions over the route/area and PIREPs on conditions reported aloft.
NOTE− When communicating weather information on the TIBS broadcast or telephone, specialists may announce cloud heights in either group form or in hundreds or thousands of feet, such as, “seventeen-thousand” or “one-seven-thousand.”
f. Density Altitude. Include the statement “Check Density Altitude” as part of the surface weather
2/28/19 JO 7110.10Z CHG 3
2−3−2 Telephone Information Briefing Service (TIBS)
broadcast for any weather reporting point with a field elevation of 2,000 feet MSL or above that reaches the criteria found in TBL 2−2−1.
g. En Route Forecast. Include forecast information from appropriate data; for example, area forecast (FA) synopsis for Hawaii and Alaska only, terminal aerodrome forecast (TAFs), and weather advisories.
h. Winds Aloft. Include winds aloft as forecast for the route/area as interpolated from forecast data for the local and/or the adjacent reporting locations for levels through 12,000 feet. The broadcast should include the levels from 3,000 to 12,000 feet, but must always include at least two forecast levels above the surface.
i. Request for PIREPs. When weather conditions within the area or along the route meet requirements for soliciting PIREPs (Paragraph 9−2−5), include a request in the recording.
PHRASEOLOGY− PILOT WEATHER REPORTS ARE REQUESTED. CONTACT FLIGHT SERVICE.
j. Closing Announcement. The closing announcement must provide instructions for contacting a pilot briefer for NOTAMs, military training activity, or other information.
2−3−3. MONITORING
a. Manually prepared recordings must be monitored immediately after recording to insure accuracy of data and availability by calling 1−800−WX−BRIEF.
b. Automated TIBS products and non-meteorological recordings must be monitored once each shift to ensure clarity and accuracy.
3/15/07 7110.65R CHG 2 JO 7110.10Z CHG 1 3/29/18
Chapter 2. Broadcast Procedures › Section 4. Hazardous Inflight Weather Advisory Service (HIWAS)
2−4−1 Hazardous Inflight Weather Advisory Service (HIWAS)
Section 4. Hazardous Inflight Weather Advisory Service
(HIWAS)
2−4−1. GENERAL
a. Hazardous Inflight Weather Advisory Service (HIWAS), available in the 48 contiguous states and the District of Columbia, is a continuous broadcast of inflight weather advisories including AWWs, WSs, WSTs, CWAs, WAs, and UUAs.
b. HIWAS broadcast areas are defined as the area within 150 NM of a HIWAS outlet.
2−4−2. PRIORITY
HIWAS broadcasts must not be interrupted/delayed except for emergency situations, when an aircraft requires immediate attention, or for reasonable use of the voice override capability on specific HIWAS outlets in order to use the limited Remote Communication Outlet (RCO) to maintain en route communications. The service must be provided 24 hours a day.
a. Make the following announcement if there are no hazardous weather advisories in the HIWAS broadcast area. Update the announcement at least every 2 hours.
PHRASEOLOGY− THIS RECORDING PREPARED AT (time) ZULU. THERE ARE NO HAZARDOUS WEATHER ADVISORIES WITHIN A ONE-FIVE-ZERO NAUTICAL MILE RADIUS OF THIS HIWAS OUTLET.
b. Complete the update recording as soon as practical, but not more than 15 minutes from time of receipt of new hazardous weather information.
2−4−3. CONTENT
Record hazardous weather information occurring within the HIWAS broadcast area. The broadcast must include the following elements:
a. Statement of introduction including the appropriate area(s) and a recording time.
PHRASEOLOGY− HIWAS WITHIN A ONE−FIVE−ZERO NAUTICAL MILE RADIUS OF (geographic area) RECORDED AT (time) ZULU (text).
NOTE− Border facilities must append “in domestic U.S. airspace” to the geographical area text in the introduction statement.
b. Statement of hazardous weather, including WSTs, WSs, WAs, UUAs, AWWs, and CWAs.
c. Request for PIREPs, if applicable. (See Paragraph 9−2−5, Soliciting PIREPs.)
PHRASEOLOGY− PILOT WEATHER REPORTS ARE REQUESTED.
d. Recommendation to contact Flight Service for additional details concerning hazardous weather.
PHRASEOLOGY− CONTACT FLIGHT SERVICE FOR ADDITIONAL DETAILS.
2−4−4. BROADCAST PROCEDURES
a. Upon receipt of new hazardous weather information:
1. Update the HIWAS broadcast.
2. Make a HIWAS update announcement once on all communications/navigational aid (NAVAID) frequencies except on emergency and navigational frequencies already dedicated to continuous broadcast services.
PHRASEOLOGY− ATTENTION ALL AIRCRAFT, HAZARDOUS WEATHER ADVISORY UPDATE FOR (geographical area) IS AVAILABLE ON HIWAS, OR CONTACT FLIGHT SERVICE, as appropriate.
b. In the event that a HIWAS broadcast area is out of service, make the following announcement on all communications/NAVAID frequencies except on emergency and navigational frequencies already dedicated to continuous broadcast services:
PHRASEOLOGY− ATTENTION ALL AIRCRAFT, HAZARDOUS WEATHER ADVISORY UPDATE IS AVAILABLE FROM FLIGHT SERVICE. NOTE− Simultaneous announcements may cause heterodyne problems on multiple outlets having the same frequency and interference over close outlets with known problems. Announcements may have to be rebroadcast to insure compliance.
2−4−2 Hazardous Inflight Weather Advisory Service (HIWAS)
2−4−5. SUSPENSION
HIWAS broadcasts must not be suspended for routine maintenance during periods when weather advisories have been issued for the HIWAS outlet area.
Chapter 2. Broadcast Procedures › Section 5. Automatic Flight Information Service (AFIS) (Alaska Only)
2−5−1 Automatic Flight Information Service (AFIS)
Section 5. Automatic Flight Information Service (AFIS)
(Alaska Only)
2−5−1. AUTOMATIC FLIGHT INFORMATION SERVICE (AFIS)
Use the AFIS to provide advance non-control airport, meteorological, and pertinent NOTAM information to aircraft. Specialists must provide local airport advisory (LAA) information when the AFIS is not available.
NOTE− Use of the AFIS by pilots is not mandatory, but pilots who use two-way radio communication with the FSS are urged to use the service.
a. Begin each new AFIS message with the airport/facility name and a phonetic alphabet letter. The phonetic alphabet letter must also be spoken at the end of the message and be used sequentially, beginning with “Alpha,” ending with “Zulu.” Full-time facilities must repeat the letter without regard to the beginning of a new day. Part−time facilities must identify the first resumed broadcast message with “Alpha.”
b. The AFIS recording must be reviewed for completeness, accuracy, speech rate, and proper enunciation before being transmitted.
c. Maintain an AFIS message that reflects the most current local airport information.
1. Make a new AFIS recording when any of the following occur:
(a) Upon receipt of any new official weather, regardless of any change in values.
(b) When runway braking action reports are received that indicate runway braking is worse than that which was included in the current AFIS broadcast.
(c) When there is a change in any other pertinent data for the airport or surrounding area, such as change in favored runway, new or canceled NOTAMs, WAs, WSs, CWAs, PIREPs, or other information that facilitates the repetitive transmission of essential but routine information.
2. Omit rapidly changing data. When this occurs, the AFIS must contain a statement advising pilots whom to contact for the omitted data.
EXAMPLE− “For latest ceiling/visibility/altimeter/wind/(other conditions) contact (facility and frequency).”
3. Broadcast, on the LAA frequency, the new airport AFIS phonetic alphabet identifier after each new recording.
4. After establishing twoway radio communication, if the pilot does not state that he/she has the current AFIS code, the specialist must either:
(a) Use LAA procedures to issue pertinent AFIS information, or
(b) Advise the pilot to return to the AFIS frequency.
5. AFIS broadcasts may be suspended within specified time periods. During these periods, the AFIS must contain a brief statement that the AFIS is suspended for the specified time and pilots should contact the FSS for LAA.
PHRASEOLOGY− (Airport name) FLIGHT INFORMATION BROADCASTS ARE SUSPENDED UNTIL (time). CONTACT (facility name) RADIO ON (frequency) FOR AIRPORT INFORMATION.
6. Part-time and seasonal facilities must record a message with the appropriate frequency and facility contact information as well as known information regarding resumption of LAA.
PHRASEOLOGY− (Name of FSS) HOURS OF OPERATION ARE (time) LOCAL TIME TO (time) LOCAL TIME. THE COMMON TRAFFIC ADVISORY FREQUENCY IS (frequency). PILOT CONTROLLED LIGHTING IS AVAILABLE ON (frequency). FOR ADDITIONAL INFORMATION CONTACT (name of FSS) ON (frequency).
(Name of FSS) IS CLOSED FOR THE WINTER SEASON. THE COMMON TRAFFIC ADVISORY FREQUENCY IS (frequency). PILOT CONTROLLED LIGHTING IS AVAILABLE ON (frequency). FOR ADDITIONAL INFORMATION CONTACT (name of FSS) ON (frequency).
2−5−2 Automatic Flight Information Service (AFIS)
7. Use the following format and include the following in AFIS broadcast as appropriate:
(a) (Airport/facility name) airport information.
(b) Phonetic alphabet designator.
(c) Special routing procedures in effect (when appropriate for the Ketchikan (KTN) area).
(d) Time of the AFIS preparation (UTC) followed by the word, “ZULU.”
(e) Include the current weather observation and other pertinent remarks. The ceiling/sky conditions, visibility, and obstruction to vision maybe omitted if the ceiling is above 5,000 and the visibility is more than 5 miles.
EXAMPLE− “The weather is better than five thousand and five.”
(f) Favored runway and additional local information, as required.
(g) NOTAMs concerning local NAVAIDs and field conditions pertinent to flight.
EXAMPLE− “Notice to Airmen, Iliamna NDB out of service.” “Transcribed weather broadcast out of service.”
(h) Runway braking action or runway condition codes (RwyCC) when provided. Include the time of the report.
PHRASEOLOGY− RUNWAY (number) condition code (first value, second value, third value) AT (time).
EXAMPLE− Runway Three−Six condition code two, two, one at one zero one eight Zulu.”
REFERENCE− FAA Order JO 7110.10, Para 4−4−3, Airport Advisory/RAIS Elements and Phraseology.
(i) Low-level wind shear (LLWS) advisory, including those contained in the terminal aerodrome forecast (TAF)and in PIREPs. (Include PIREP information at least 20 minutes following the report).
EXAMPLE− “Low level wind shear is forecast.”
(j) Unauthorized Laser Illumination Events. When a laser event is reported, include reported unauthorized laser illumination events on the AFIS broadcast for one hour following the last report.
Include the time, location, altitude, color, and direction of the laser as reported by the pilot.
PHRASEOLOGY− UNAUTHORIZED LASER ILLUMINATION EVENT, (UTC time), (location), (altitude), (color), (direction).
EXAMPLE− “Unauthorized laser illumination event at zero one zero zero Zulu, eight-mile final runway one eight at three thousand feet, green laser from the southwest.”
(k) Man-Portable Air Defense Systems (MANPADS) alert and advisory. Specify the nature and location of threat or incident, whether reported or observed and by whom, time (if known), and notification to pilots to advise ATC if they need to divert.
PHRASEOLOGY− MANPADS ALERT. EXERCISE EXTREME CAUTION. MANPADS THREAT/ATTACK/POST-EVENT ACTIVITY OBSERVED/REPORTED BY (reporting agency) (location) AT (time, if known). (When transmitting to an individual aircraft) ADVISE ON INITIAL CONTACT IF YOU WANT TO DIVERT.
EXAMPLE− “MANPADS alert. Exercise extreme caution. MANPADS threat reported by TSA, Anchorage area. Advise on initial contact if you want to divert.”
“MANPADS alert. Exercise extreme caution. MANPADS attack observed by flight service station one-half mile northwest of airfield at one-two-five-zero Zulu. Advise on initial contact if you want to divert.”
NOTE− 1. Upon receiving or observing an unauthorized MANPADS alert/advisory, contact the Alaska Flight Service Information Area Group(AFSIAG) through the Alaskan Region Regional Operations Center (ROC).
2. Continue broadcasting the MANPADS alert/advisory until advised by national headquarters the threat is no longer present. Coordination may be through the AFSIAG or the Alaskan ROC.
REFERENCE− FAA Order JO 7210.3, Para 2-1-10, Handling MANPADS Incidents.
(l) Any other advisories applicable to the area covered by the LAA.
(m) Local frequency advisory.
PHRASEOLOGY− CONTACT (facility name) RADIO ON (frequency) FOR TRAFFIC ADVISORIES.
(n) Instructions for the pilot to acknowledge receipt of the AFIS message on initial contact.
3/15/07 7110.65R CHG 2 JO 7110.10Z CHG 3 2/28/19
2−5−3 Automatic Flight Information Service (AFIS)
EXAMPLE− “Dillingham airport information ALPHA. One six five five Zulu. Wind one three zero at eight; visibility one five; ceiling four thousand overcast; temperature four, dew point three; altimeter two niner niner zero. Favored runway one niner. Notice to Airmen, Dillingham V-O-R out of service. Contact Dillingham Radio on one two three point six for traffic advisories. Advise on initial contact you have ALPHA.” “Kotzebue information ALPHA. One six five five Zulu. Wind, two one zero at five; visibility two, fog; ceiling one
hundred overcast; temperature minus one two, dew point minus one four; altimeter three one zero five. Altimeter in excess of three one zero zero, high pressure altimeter setting procedures are in effect. Favored runway two six. Weather in Kotzebue surface area is below V-F-R minima - an ATC clearance is required. Notice to Airmen, Hotham NDB out of service. Contact Kotzebue Radio on one two three point six for traffic advisories and advise intentions. Transcribed Weather Broadcast out of service. Advise on initial contact you have ALPHA.”
Chapter 3. Pilot Briefing › Section 1. General
3−1−1 General
Chapter 3. Pilot Briefing
Section 1. General
3−1−1. DEFINITION
Pilot briefings are the translation of weather observations and forecasts, including surface, upper air, radar, satellite, and PIREPs into a form directly usable by the pilot or flight supervisory personnel to formulate plans and make decisions for the safe and efficient operation of aircraft. These briefings must also include information on NOTAM, flow control, and other items as requested.
3−1−2. PRE-DUTY REQUIREMENTS
Before assuming pilot briefing duties, familiarize yourself sufficiently with aeronautical and meteorological conditions to effectively provide briefing service. This includes:
a. General locations of weather-causing systems and general weather conditions.
b. Detailed information of current and forecast weather conditions for the geographical area(s) of responsibility.
c. Aeronautical information; for example, NOT- AM, special use airspace (SUA), temporary flight restrictions (TFR), ATC delays, etc.
REFERENCE− Pertinent facility directives
3−1−3. PREFLIGHT BRIEFING DISPLAY
Provide a preflight briefing display for specialist/pilot use. The contents and method of display must be based on individual facility requirements; for example, available equipment and space. Additional displays, as required, must be provided to ensure availability of information at all positions. At the discretion of facility management, provide a separate display for pilot use. All material in such displays must be current.
3−1−4. WEATHER DISPLAY PRODUCTS
a. The weather graphic display should include, but not necessarily be limited to, the following analysis, prognosis, and data products:
1. Weather Depiction.
2. Surface Analysis.
3. Forecast Winds Aloft.
4. Freezing Level Graphic.
5. G-AIRMET Graphic.
6. 12- and 24-hour Low Level Significant Weather Prognosis.
7. 12-, 24-, 36-, and 48-hour Surface Prognosis.
8. High Level Significant Weather Prognosis.
9. Current Icing Product (CIP).
10. Forecast Icing Product (FIP).
11. Graphical Turbulence Guidance (GTG).
12. National Weather Radar Summary. (CONUS Only).
13. National/Regional Radar Mosaics.
14. Radar Echo Tops.
15. Radar VAD Wind Profiles.
16. Visible/IR Satellite Imagery.
17. Constant Pressure Charts.
18. 500 MB Heights and Vorticity Analysis.
19. 500 MB Heights and Vorticity Prognosis.
20. 6−, 12−, 24−, 36−, and 48−hour 500 MB Heights and Vorticity Prognosis.
21. Convective Outlook.
22. Maximum Temperature 24− and 36−Hour Forecast (CONUS Only).
23. Minimum Temperature 24− and 36−Hour Forecast (CONUS Only).
b. Map features. (See FIG 3−1−1.)
c. Precipitation and obstruction to vision. (See FIG 3−1−2.)
9/13/18 JO 7110.10Z CHG 2
3−1−2 General
FIG 3−1−1 Map Features Chart
FIG 3−1−2 Precipitation and Obstruction To Vision Chart
d. Interpret and summarize weather radar displays as appropriate.
1. Use all available radar data and PIREPs to determine intensity, tops, area of coverage, movement, etc.
REFERENCE− Pilot Controller Glossary (P/CG) Term, Precipitation Radar Weather Descriptions
2. Identify data obtained from sources other than radar display by source and time of observation.
3. Define area of coverage in relation to VORs, airways for the route structure being flown, airports or geographic points to assist the pilot in relating coverage to route of flight or destination. EXAMPLE− ”A broken line of light to heavy echoes covers an area along and three zero miles east of a line from the Crazy Woman V−O−R to the Riverton V−O−R. Average tops between two-six thousand and three−four thousand. This line is increasing in intensity. Movement has been from northwest to southeast at three zero knots. The line includes an extreme echo one five miles in diameter on Victor Two Ninety-eight forty−eight miles southeast of the Worland V−O−R, tops four three thousand. There are no known echoes within three-zero nautical miles of Victor Eight−five or Victor Two Ninety−eight south at this time.”
3−1−5. FORECASTS, WARNINGS, AND ADVISORIES
a. Use only weather forecasts, warnings, and advisories issued by a National Weather Service
3/15/07 7110.65R CHG 2 JO 7110.10Z CHG 2 9/13/18
3−1−3 General
(NWS) office, including Center Weather Service Units (CWSUs), the U.S. military, foreign governments, or graphics systems owned/leased by the FAA or provided through a FAA−contracted service provider.
b. Use the OUTLOOK section of WSTs to provide information on where convective activity is expected. Use the Convective Outlooks (ACUS01 KWNS) to extract pertinent forecast information regarding the convective activity.
c. When an NWS forecast requires an amendment or correction, request assistance from the appropriate NWS office.
3−1−6. UNAVAILABILITY OF DATA
Use all available means to obtain the data required to brief pilots. If a complete briefing cannot be provided due to circuit problems or missing data, inform the pilot of this fact. Brief to the extent possible. Advise the pilot of the time you expect the data to be available.
3−1−7. TYPE OF BRIEFING TO BE CONDUCTED
Provide the pilot with the type of briefing requested (standard, abbreviated, or outlook). When it is not clear initially which type briefing is desired, provide the first one or two items requested, and then ascertain if the pilot would like a standard briefing. If a standard briefing is requested, conduct the briefing in accordance with Paragraph 3−2−1. If the pilot does not desire a standard briefing, provide either an abbreviated briefing in accordance with Paragraph 3−2−2 or an outlook briefing in accordance with Paragraph 3−2−3.
3−1−8. LOGGING PILOT BRIEFINGS
a. Pilot briefings must be logged and retained in accordance with FAA Order 1350.14, Records Management. Briefings must be logged in operation-
al systems when possible but may be logged manually if needed for operational efficiency.
b. Operational systems must, as a minimum, automatically record the facility/sector, date, position, time, and specialist identification for each logged briefing. In addition, enter the following information:
1. Departure and destination.
2. Aircraft identification. (The pilot’s name may be substituted for the aircraft identification, if unknown.)
3. Remarks, as applicable, to indicate OTLK (outlook briefing), AB (abbreviated briefing), and/or VNR.
c. To manually log pilot briefings, use one of the following FAA forms:
1. FAA Form 7233−2, Pilot Briefing Log. Use a separate form each day. Two or more forms may be used simultaneously at different operating positions. Complete boxes 1 through 3 on each form. Enter appropriate data in columns 4, 5, 6, 7, 8 (if pertinent), and 9. If the pilot’s name is known, it may be substituted for the aircraft identification. As applicable, enter OTLK (outlook briefing), AB (abbreviated briefing), and/or VNR in column 8.
2. FAA Forms 7233−5, Inflight Contact Record, or 7230-21, Flight Progress Strip. Enter PB in block 14 if a briefing is provided. As applicable, also enter AB, OTLK, and/or VNR in the same block.
NOTE− See Appendix B for FAA forms.
d. Where audio recorders are used, facility management may limit entries on pilot briefing records to those required for facility use.
e. Where fast-file recorders are used and the pilot states the source of a briefing on the recorder, it must be entered in the remarks field of the flight plan.
EXAMPLE− PB/DCA PB/DUATS
9/13/18 JO 7110.10Z CHG 2
3−2−1 Preflight Pilot Briefing
Section 2. Preflight Pilot Briefing
3−2−1. CONDUCT OF STANDARD BRIEFING
Chapter 3. Pilot Briefing › Section 2. Preflight Pilot Briefing
a. Brief by translating, interpreting, and summarizing available data for the intended flight. Do not read individual weather reports or forecasts unless, in your judgment, it is necessary to emphasize an important point or unless specifically requested to do so by the pilot. Obtain the following information if it is pertinent and not evident or already known:
1. Type of flight planned.
2. Aircraft identification or pilot’s name.
3. Aircraft type.
4. Departure point.
5. Route of flight.
6. Destination.
7. Flight altitude(s).
8. Estimated time of departure (ETD) and estimated time en route (ETE).
b. The specialist must issue the following cautionary advisory to a pilot planning a flight outside of United States controlled airspace, unless the pilot advises they have the international cautionary advisory.
PHRASEOLOGY− CHECK DATA AS SOON AS PRACTICAL AFTER ENTERING FOREIGN AIRSPACE, AS OUR INTERNATIONAL DATA MAY BE INACCURATE OR INCOMPLETE.
c. Using all sources of weather and aeronautical information, provide the following data when it is applicable to the proposed flight. Provide the information in subparagraphs c1 through c8 in the sequence listed except as noted.
1. Adverse Conditions. Include this element when meteorological or aeronautical conditions are reported or forecast that might influence the pilot to alter the proposed flight. Emphasize conditions that are particularly significant, such as low level wind shear, thunderstorms, reported icing, frontal zones along the route of flight, NOTAMs; for example, airport/runway closures, air traffic delays, TFRs etc. Weather advisories (WS, WA, WST, CWA, and
AWW) must be given by stating the type of advisory followed by the pertinent information.
EXAMPLE− “An AIRMET is in effect until 1400Z for moderate turbulence below 10,000 feet over the mountainous area of southern California.” “Palmer airport closed” NOTE− NOTAMs in this category may be provided with NOTAMs listed in subparagraph c8.
2. VFR Flight Not Recommended (VNR). Include this statement when VFR flight is proposed and sky conditions or visibilities are present or forecast, surface or aloft, that in your judgment would make flight under visual flight rules doubtful. Describe the conditions, affected locations, and times.
PHRASEOLOGY− VFR FLIGHT NOT RECOMMENDED
EXAMPLE− ‘‘There are broken clouds along the entire route between niner and one one thousand feet. With the approach of a cold front, these clouds are forecast to become overcast and to lower to below seven thousand with mountains and passes becoming obscured. V-F-R flight not recommended between Salt Lake City and Grand Junction after two two zero zero ZULU.” ‘‘V-F-R flight not recommended in the Seattle area until early afternoon. The current weather at Seattle is indefinite ceiling three hundred, visibility one, mist, and little improvement is expected before one eight zero zero ZULU.”
NOTE− This recommendation is advisory in nature. The decision as to whether the flight can be conducted safely rests solely with the pilot.
3. Synopsis. Provide a brief statement describing the type, location, and movement of weather systems and/or air masses which might affect the proposed flight. This element may be combined with adverse conditions and/or the VNR element, in any order, when it will help to more clearly describe conditions.
4. Current Conditions. Summarize from all available sources reported weather conditions applicable to the flight. This element may be omitted if the proposed time of departure is beyond 2 hours, unless the information is requested by the pilot. If
3−2−2 Preflight Pilot Briefing
AUTO appears after the date/time element and is presented as a singular report, follow the location with the word “AUTOMATED.”
5. En Route Forecast. Summarize forecast information that will affect the proposed flight; for example, area forecasts for the Gulf of Mexico, Caribbean, Alaska, and Hawaii; Static Graphical Forecast Images for the CONUS, TAFs, prognosis charts, weather advisories, etc. Provide the information in a logical order; for example, climb out, en route, and descent.
6. Destination Forecast. Provide the destination forecast including significant changes expected within 1 hour before and after the estimated time of arrival (ETA).
7. Winds Aloft. Provide forecast winds aloft for the flight using degrees of the compass. Interpolate wind directions and speeds between levels and stations as necessary. Provide temperature information on request.
8. Notices to Airmen (NOTAM). Provide NOTAM information affecting the flight:
(a) NOTAM (D). All NOTAMs (D), including SUA NOTAMs for restricted areas, aerial refueling, and night vision goggles (NVG).
NOTE− Other SUA NOTAMs (D) such as military operations area (MOA), military training route (MTR) and warning area NOTAMs, are considered “upon request” briefing items as indicated in paragraph 3-2-1c13(a).
(b) Combine this element with adverse conditions when it would be logical and advantageous to do so.
9. Prohibited Areas P-40, P-56, and the Special Flight Rules Area (SFRA) for Washington, DC. Include this element when pertinent to the route of flight. Advise the pilot that VFR flight within 60 miles of the DCA VOR/DME requires Special Awareness Training.
NOTE− Refer to 14 CFR Part 93 for additional information such as special awareness for flights in and around SFRAs and/or areas that require special air traffic rules.
10. ATC Delays. Inform the pilot of ATC delays and/or flow control advisories that might affect the proposed flight.
11. Request for PIREPs. Include this element when in your judgment, a report of actual inflight conditions is beneficial or when conditions meet criteria for solicitation of PIREPs (paragraph 9−2−5). Advise the pilot to contact Flight Service to report en route conditions.
12. Upon Request. Provide any information requested by the pilot, including, but not limited to:
(a) Special use airspace, except those listed in paragraph 3-2-1c8(a), SUA-related airspace (air traffic control assigned airspace (ATCAA)), and MTR activity. For all SUA and MTR data requests, advise the pilot that information may be updated periodically and to contact the appropriate ATC facility for additional information while in flight.
NOTE− For the purpose of this paragraph, SUA and related airspace includes the following types of airspace: alert area, MOA, warning area and ATCAA. MTR data includes the following types of airspace: instrument flight rule (IFR) training routes (IR), VFR training routes (VR), and slow training routes (SR).
(b) Approximate density altitude data.
(c) Information regarding such items as air traffic service and rules, customs/immigration procedures, air defense identification zone (ADIZ) rules, SAR, etc.
(d) Military NOTAMs.
REFERENCE− FAA Order JO 7930.2, Paragraph 8-3-1, Military NOTAM Availability.
(e) Special FDC instrument approach procedure changes.
(f) FDC NOTAMs containing amendments to airways, airport, and facility IFR procedures and General Information.
NOTE− General FDC NOTAMs include Chart amendments, Special Security Instructions, and Special Advisory Notices.
(g) Information contained in the Notices to Airmen Publication to include Part 95 Revisions, International NOTAMs and Graphic Notices.
3−2−2. CONDUCT OF ABBREVIATED BRIEFING
a. Provide an abbreviated briefing when a pilot requests information to supplement mass-disseminated data; update a previous briefing; or when the
3/15/07 7110.65R CHG 2 JO 7110.10Z CHG 3 2/28/19
3−2−3 Preflight Pilot Briefing
pilot requests that the briefing be limited to specific information. If applicable, include the statement “VFR flight not recommended” in accordance with subparagraph 3-2-1c2. The specialist must issue the following cautionary advisory to a pilot planning a flight outside of United States controlled airspace, unless the pilot advises they have the international cautionary advisory.
PHRASEOLOGY− CHECK DATA AS SOON AS PRACTICAL AFTER ENTERING FOREIGN AIRSPACE, AS OUR INTERNATIONAL DATA MAY BE INACCURATE OR INCOMPLETE.
b. Conduct abbreviated briefings as follows:
1. When a pilot desires specific information only, provide the requested information. If adverse conditions are reported or forecast, advise the pilot. Provide details on these conditions, in accordance with subparagraph 3-2-1c1, at the pilot’s request.
2. When a pilot requests an update to a previous briefing, obtain from the pilot the time the briefing was received and necessary background information. To the extent possible, limit the briefing to appreciable changes in meteorological and aeronautical conditions since the previous briefing.
3. When a pilot requests information to supplement data obtained through FSS mass-dissem-
ination media, obtain pertinent background information, the specific items required by the pilot, and provide the information in the sequence listed in subparagraph 3-2-1c.
4. When a pilot requests to file a flight plan only, ask if he/she requires the latest information on adverse conditions along the route of flight. If so, provide the information pertinent to the route of flight in accordance with subparagraph 3-2-1c1.
5. Solicit PIREPs in accordance with subparagraph 3-2-1c11.
3−2−3. CONDUCT OF OUTLOOK BRIEFING
a. Provide an outlook briefing when the proposed departure is 6 hours or more from the time of the briefing. Conduct the briefing in accordance with subparagraph 3-2-1c. Omit items in subparagraphs c2, c4, and c7 through c11, unless specifically requested by the pilot or deemed pertinent by the specialist.
b. When the proposed flight is scheduled to be conducted beyond the valid time of the available forecast material, provide a general outlook and then advise the pilot when complete forecast data will be available for the proposed flight.
2/28/19 JO 7110.10Z CHG 3
Chapter 4. Inflight Services › Section 1. General
4−1−1 General
Chapter 4. Inflight Services
Section 1. General
4−1−1. INFLIGHT SERVICES
a. Inflight services are those provided to or affecting aircraft inflight or otherwise operating on the airport surface. This includes services to airborne aircraft, such as delivery of ATC clearances, advisories or requests, issuance of military flight advisory messages, NOTAM, SAR communications searches, flight plan handling, transcribed or live broadcast, weather observations, PIREPs, and pilot briefings.
b. Upon request, provide en route aircraft with timely and pertinent weather data tailored to a specific altitude and route using the most current available sources of aviation meteorological information. Tailor en route flight advisories to the phase of flight that begins after climb out and ends with descent to land. Current weather and terminal forecast at the airport of first intended landing and/or the alternate airport must be provided on request. When conditions dictate, provide information on weather for alternate routes and/or altitudes to assist the pilot in the avoidance of hazardous flight conditions.
NOTE− Provide inflight services in accordance with the procedures in this chapter to aircraft on a “first come, first served” basis, as circumstances permit.
c. Prior to assuming inflight duties, the specialist must review, as a minimum, the graphic information listed in subparagraph 3−1−4a, Weather Display Products (if available). After assuming duties, the specialist must continue to review graphic and written data as needed during the watch to update and maintain a thorough knowledge of weather synoptic and forecast information affecting aviation operations.
4−1−2. OPERATIONAL PRIORITY
a. Emergency situations are those where life or property are in immediate danger. Aircraft in distress have priority over all other aircraft.
b. Provide priority to civilian air ambulance flights (call sign “MEDEVAC”). Use of the MEDEVAC call sign indicates that operational priority is requested. When verbally requested, provide priority to AIR EVAC, HOSP, and scheduled air carrier/air taxi flights. Assist the pilots of MEDEVAC, AIR EVAC, and HOSP aircraft to avoid areas of significant weather and turbulent conditions. When requested by a pilot, provide notifications to expedite ground handling of patients, vital organs, or urgently needed medical materials.
c. Provide maximum assistance to search and rescue (SAR) aircraft performing a SAR mission.
d. Provide special handling as required to expedite Flight Check and automated flight inspection “Flight Check (number) Recorded” aircraft.
4−1−3. INFLIGHT WEATHER BRIEFING
Upon request, provide inflight weather briefings, in accordance with the procedure outlined in Chapter 3, Section 2.
4−1−4. INFLIGHT EQUIPMENT MALFUNCTIONS
a. Inflight equipment malfunctions include partial or complete failure of equipment which may affect either safety and/or the ability of the flight to proceed.
b. When a pilot reports a flight equipment malfunction, determine the nature and extent of any assistance desired.
c. Provide maximum assistance possible consistent with equipment and any special handling requested.
d. Relay to other specialists or facilities who will handle the aircraft all information concerning the equipment malfunction on the aircraft and any special handling requested or being provided.
4−1−5. AIRCRAFT REPORTED MALFUNCTIONS
a. Aircraft-reported NAVAID malfunctions are subject to varying circumstances. When an aircraft
2/28/19 JO 7110.10Z CHG 3
4−1−2 General
reports a ground-based NAVAID malfunction, take the following action:
1. Request a report from a second aircraft.
2. If the second aircraft reports normal operations, if able, inform the first aircraft. Record the incident on FAA Form 7230-4, Daily Record of Facility Operation.
3. If the second aircraft confirms the malfunction:
(a) Notify the appropriate IFR control facility or sector.
(b) Notify Technical Operations personnel.
(c) Take NOTAM action when requested by Technical Operations personnel.
(d) Record the incident on FAA Form 7230-4.
4. In the absence of a second aircraft report:
(a) Notify Technical Operations and advise what time the initial aircraft reported the failure and when a second aircraft report might be obtained.
(b) Record the incident on FAA Form 7230-4.
b. When an aircraft reports a global positioning system (GPS)/global navigation satellite system (GNSS) anomaly:
1. Request the following information:
(a) Aircraft call sign and type of aircraft.
(b) Date and time of the occurrence.
(c) Location of anomaly.
(d) Altitude.
2. Record the incident on FAA Form 7230-4.
3. Forward this information to the traffic management unit (TMU) and Technical Operations personnel.
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.
EXAMPLE− “Are you receiving any WAAS 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 Paragraph 4−1−5b.
d. When a pilot reports an ADS-B services malfunction (i.e., ADS-B, TIS-B, FIS-B, or ADS-R):
1. Request the following information:
(a) Aircraft call sign and type of aircraft.
(b) Date and time of observation.
(c) Location and altitude of anomaly.
(d) Condition observed (or anomaly).
(e) Type and software version of avionics system.
2. Forward this information to an Operations Control Center (OCC) or Service Operations Center (SOC) as appropriate.
3. Record the incident on FAA Form 7230-4.
4−1−6. NAVAID FLIGHT CHECK
Provide maximum assistance to aircraft engaged in flight inspection of NAVAIDs. Unless otherwise agreed to, maintain direct contact with the pilot and provide information regarding known traffic in the area and request the pilot’s intentions.
NOTE− 1. Many flight inspections are accomplished using automatic recording equipment. An uninterrupted flight is necessary for successful completion of the mission. The workload for the limited number of aircraft engaged in these activities requires strict adherence to a schedule.
2. Flight inspection operations which require special participation of ground personnel, specific communications, or radar operation capabilities are considered to require special handling. These flights are coordinated with appropriate facilities before departure.
3/15/07 7110.65R CHG 2 JO 7110.10Z CHG 3 2/28/19
Chapter 4. Inflight Services › Section 2. Data Recording
4−2−1 Data Recording
Section 2. Data Recording
4−2−1. TYPES OF DATA RECORDED
a. Operational system entries for:
1. Flight plans and related messages.
2. Logging pilot briefings and aircraft contacts.
3. Weather/Flight data messages.
b. Manual strip marking.
4−2−2. METHODS OF RECORDING DATA
a. Except as provided in 4−2−2b, all entries must be made directly into the operational system.
b. Locally-approved procedures may be used to manually record data during heavy traffic periods or system outages. Aircraft contact information should be logged in the operational system as soon as practical.
c. Use control/clearance symbols, abbreviations, location identifiers, and contractions for recording position reports, traffic clearances, and other data. When recording data either electronically or manually, you may use:
1. Plain language to supplement data when it will aid in understanding the recorded information.
2. Locally-approved contractions and identifiers for frequently used terms and local fixes not listed in either FAA Order JO 7340.2, Contractions, or FAA Order JO 7350.9, Location Identifiers. Use only within your facility, not on data or interphone circuits. All locally-approved contractions and identifiers must be placed in facility files for record and reference purposes.
d. When recording data manually, use the standard hand-printed characters shown in FIG 4−2−1 to prevent misinterpretation.
FIG 4−2−1 Hand-Printed Characters Chart
4−2−2 Data Recording
NOTE− A slant line crossing through the numeral zero and an underline of the letter “S” on handwritten portions of flight progress strips are required only when there is reason to believe the lack of these markings could lead to a misunderstanding. A slant line through the numeral zero is required on all weather data.
1. To correct or update data, draw a horizontal line through it and write the correct information adjacent to it.
2. Do not erase any item.
4−2−3. IFR/VFR/DVFR FLIGHT PLAN RECORDING
a. Use the operational system to record and file flight plans, flight plan modifications, cancellations, activations, and closures for appropriate distribution and processing. Detailed instructions are contained in the operational system manuals.
NOTE− FSS operational systems contain an electronic equivalent of authorized FAA Flight Plan Forms.
b. When closing an active VFR flight plan, obtain departure point and destination, if not already known.
NOTE− A cancelled VFR flight plan is one that is removed from a proposed list and has not been activated. A closed VFR flight plan is one that has been activated and is then removed from an inbound list.
c. Flight plan information may initially be recorded on FAA Form 7233-1 or other paper prior to entry into the operational system.
4−2−4. FLIGHT PROGRESS STRIPS (FAA FORMS 7230-21 AND 7233-5)
a. When officially used to record inflight data, use flight progress strips to record:
1. Aircraft contacts.
2. ATC clearances.
3. Pilot briefings on airborne aircraft.
4. Other operationally significant items.
b. Use a flight progress strip for each aircraft and record all contacts with that aircraft on the same strip. If supplemental strips are needed for additional writing space, keep the original and supplemental strips together.
NOTE− Multiple flights by the same aircraft may be recorded on a single strip when situational awareness and strip bay efficiency are improved.
4−2−5. FLIGHT PROGRESS STRIPS AND ENTRY DATA
a. Flight progress strip. (See FIG 4−2−2.)
b. Flight progress strip entry. (See FIG 4−2−3 and FIG 4−2−4.)
FIG 4−2−2 Flight Progress Strip
3/15/07 7110.65R CHG 2 JO 7110.10Z CHG 2 9/13/18
4−2−3 Data Recording
FIG 4−2−3 Strip Entry 1
FIG 4−2−4 Strip Entry 2
4−2−4 Data Recording
c. Flight progress strip Item and Information. (See TBL 4−2−1.)
TBL 4−2−1 Item and Information
Item Information
1
Aircraft Identification (ACID) (To identify IFR aircraft piloted by solo USAF under-graduate pilot, the letter Z will be added to aircraft ID on the flight progress strip. Do not use the suffix in ground-to-air communications.) 2 Type of aircraft/special equipment. 3 True airspeed (TAS) and altitude (IFR). Altitude (VFR/DVFR, if known). 4 Departure point. 5 Route of flight. 6 Destination. 7 Actual departure time, or time VFR flight plan activated. 8 ETA at destination. 9 Estimated time of fuel exhaustion. 10 Type of flight. 11 Action time; for example, overdue time, fuel exhaustion time, LR contact time. 12 Time of contact with pilot. 13 Information received from pilot/another facility. 14 Data issued to the aircraft.
d. Flight progress strip abbreviation. (See TBL 4−2−2 )
TBL 4−2−2 Abbreviation
Abbreviation Meaning Õ Over Flight ↓ Inbound Flight ↑ Outbound Flight A AIRMET (WA) AA Airport Advisory CWT Caution Wake Turbulence D DVFR DA Decided Against Flight DD Decided to Delay Flight DW Downwind FP Filed Flight Plan I IFR IC Incomplete Briefing PB Pilot Brief RY Runway S SVFR V VFR VNR VFR Flight not recommended (Pilot Brief) WS SIGMET WST Convective SIGMET e. Record ATC instructions and clearances completely and exactly.
f. Summarize other data using approved symbols and contractions. (See FIG 4−2−5 and FIG 4−2−6.)
4−2−5 Data Recording
FIG 4−2−5 Control Information Symbols Chart 1
4−2−6 Data Recording
FIG 4−2−6 Control Information Symbols Chart 2
g. Do not record issuance of altimeter setting unless that is the only information provided during the contact.
4−2−6. AIRCRAFT CONTACTS
a. Inflight contacts may be logged in the operational system, on flight progress strips, or on facility approved alternate forms.
b. When using flight progress strips, if the station has the aircraft’s flight plan, enter “FP” in item 14 on the strip to show the flight plan is on file at the facility.
c. If there is no flight plan on file for the aircraft, the following must be obtained:
1. ACID.
2. Type of flight.
3. Time of contact.
4−2−7 Data Recording
4. Other items which are operationally significant.
d. If the inflight position is recorded, you may limit entries in the aircraft contact portion of the strip to those necessary for your use.
e. Log aircraft contacts using the operational system. The following should be logged using the symbols in TBL 4−2−3 and TBL 4−2−4:
1. Type of Briefing
(a) Standard
(b) Abbreviated
(c) Outlook
2. Type of Flight
(a) IFR
(b) VFR
(c) Defense VFR (DVFR)
3. Category of Flight
(a) Air Carrier
(b) Air Taxi
(c) Military
(d) General Aviation
4. Aircraft ID
5. Type of Service
(a) Airport advisory
(b) Clearance(s); for example, IFR, special VFR (SVFR)
6. Remarks. Operating Position (if not automatically logged by operational system)
TBL 4−2−3 Clearance Abbreviation
Abbreviation Meaning
A Cleared to airport (point of intended landing). B Center clearance delivered
C
ATC clears (when clearance relayed through non-ATC facility). CAF Cleared as filed.
D Cleared to depart from the fix. F Cleared to the fix.
H Cleared to hold and instructions issued. L Cleared to land. N Clearance not delivered. O Cleared to the outer marker.
PD Cleared to climb/descend at pilot’s discretion.
Q
Cleared to fly specified sectors of a NAVAID defined in terms of courses, bearings, radials, or quadrants within a designated radius.
T
Cleared through (for landing and takeoff through intermediate point). V Cleared over the fix.
X Cleared to cross (airway, route, radial) at (point). Z Tower jurisdiction.
TBL 4−2−4 Miscellaneous Abbreviation
Abbreviation Meaning BC Back course approach. CT Contact approach. FA Final approach. GPS GPS approach. I Initial approach. ILS ILS approach. MA Missed approach. MLS MLS approach. NDB Nondirectional radio beacon approach. OTP VFR conditions-on-top. PA Precision approach. PT Procedure turn. RH Runway heading. RP Report immediately upon passing (fix/altitude). RX Report crossing. SA Surveillance approach. SI Straight-in approach. TA TACAN approach. TL Turn left. TR Turn right. VA Visual approach. VR VOR approach.
Chapter 4. Inflight Services › Section 3. Radio Communications
4−3−1 Radio Communications
Section 3. Radio Communications
4−3−1. FREQUENCY USE
a. Use radio frequencies for the specific purposes for which they are intended. A frequency may be used for more than one function when required. Use the minimum number of frequencies to conduct communications. Request pilots file flight plans on discrete frequencies when possible.
b. Monitor assigned radio frequencies continuously. Keep speaker volumes at a level sufficient to hear all transmissions.
4−3−2. AUTHORIZED TRANSMISSIONS
a. Transmit only those messages necessary for safe and efficient use of the National Airspace System (NAS).
1. Relay operational information to an aircraft or its company, as requested, when abnormal conditions necessitate such requests. Do not agree to handle such messages on a regular basis.
2. Relay official FAA messages as required.
b. Inform an aircraft of the source of any message you relay from an appropriate authority.
c. Use the words or phrases in radio communications as contained in the PCG.
4−3−3. RADIO MESSAGE FORMAT
a. Use the following format for radio communications with an aircraft:
1. Identification of aircraft.
2. Identification of the calling unit.
3. The type of message to follow when this will assist the pilot.
4. The word “over,” if required.
b. Specialist initiated call. State the prefix , for example “November” when establishing initial communications with U.S.−registered aircraft followed by the International Civil Aviation Organization (ICAO) phonetic pronunciation of the numbers/letters of the aircraft registration. The specialist may state the aircraft type, the model, the manufacturer’s name, followed by the ICAO
phonetic pronunciation of the numbers/letters of the aircraft registration if used by the pilot on the initial or subsequent call.
EXAMPLE− Specialist initiated call:
“November One Two Three Four Golf, Juneau Radio, over.” “Piper Three Four Seven Seven Papa, Fort Worth Radio, A-T-C clearance, over.”
c. Replying to call up from aircraft. Identification of the aircraft initiating the call up. Use the full identification in reply to aircraft with similar sounding identifications. For other aircraft, use the same identification the pilot used in initial call up; then use the correct identification after communication has been established. The specialist may state the aircraft type, model, or manufacturer’s name followed by the ICAO phonetic pronunciation of the numbers/letters of the aircraft registration if used by the pilot.
EXAMPLE− Responding to pilot’s initial or subsequent call:
“Jet Commander One Two Three Four Papa.”
“Bonanza One Two Three Four Tango.”
“November Six Three Eight Mike Foxtrot.”
d. The word “heavy” must be used as part of the identification in communications with or about heavy jet aircraft.
PHRASEOLOGY− UNITED FIFTY-EIGHT HEAVY.
NOTE− 1. Most airlines use the word “heavy” following the company prefix and trip number when establishing communications or when changing frequencies.
2. When in radio-telephone communications with “Air Force One,” do not add the “heavy” designator to the call sign. State only the call sign “Air Force One” regardless of the type of aircraft.
e. Preface a clearance or instruction intended for a specific aircraft with the identification of that aircraft.
f. Emphasize appropriate digits, letters, or similar sounding words to aid in distinguishing between similar sounding aircraft identifications.
4−3−2 Radio Communications
Additionally, notify each pilot concerned when communicating with aircraft having similar sounding identifications.
EXAMPLE− “American Five Twenty-one and American Twenty-one, transmissions being made to each of you on this frequency.”
“Advisory to Cessna One Three Two Four, transmissions to Cessna One Two Three Four also being made on this frequency.”
4−3−4. ABBREVIATED TRANSMISSION
Transmissions may be abbreviated as follows:
a. Use the identification prefix and the last three digits or letters of the aircraft identification after communications have been established. Do not abbreviate similar sounding aircraft identifications or the identification of an air carrier or other civil aircraft having an FAA-authorized call sign.
b. Omit the facility identification after communication has been established.
c. Transmit the message immediately after the call up (without waiting for the aircraft’s reply) when the message is short and receipt is generally assured.
d. Omit the word “over” if the message obviously requires a reply.
4−3−5. ROUTINE RADIO CONTACTS
Record information received from or given to the pilot. Prior to terminating the contact, provide the following information if it is pertinent and the pilot indicates that it has not been received previously.
a. Weather Advisory. When a weather advisory such as a WA, WS, WST, CWA, or AWW which affects an aircraft’s position, route, or destination.
b. NOTAM. Inform the pilot of any pertinent NOTAMs affecting the flight.
c. Altimeter Setting.
1. If the aircraft is operating below 18,000 feet MSL, issue current altimeter setting obtained from direct reading instruments or received from weather reporting stations. Use the setting for the location nearest the position of the aircraft.
2. If the aircraft is arriving or departing a local airport served by an operating control tower, issue altimeter setting on request only.
3. When a pilot acknowledges that he/she has received the AFIS broadcast, specialists may omit those items contained in the broadcasts if they are current.
4. Aircraft arriving or departing from a non-towered airport which has a commissioned automated weather reporting with ground-to-air capability must be advised to monitor the automated weather frequency for the altimeter setting.
PHRASEOLOGY− MONITOR (location) AUTOMATED WEATHER FOR CURRENT ALTIMETER.
NOTE− This requirement is deleted if the pilot states that he/she has the automated weather.
5. When the barometric pressure is greater than 31.00 inches Hg., Flight Standards will implement high barometric pressure procedures by NOTAM, defining the geographic area affected. When this occurs, use the following procedures:
(a) IFR aircraft. Issue the altimeter setting and advise the pilot that high pressure altimeter setting procedures are in effect. Control facilities will issue specific instructions when relaying IFR clearances and control instructions through FSS facilities when the altimeter is above 31.00 inches Hg.
(b) VFR aircraft. Issue the altimeter setting. Advise the pilot that high pressure altimeter setting procedures are in effect and to use an altimeter setting of 31.00 inches Hg en route.
PHRASEOLOGY− ALTIMETER IN EXCESS OF THREE ONE ZERO ZERO. HIGH PRESSURE ALTIMETER SETTING PROCEDURES ARE IN EFFECT. RECOMMEND YOU SET ALTIMETER THREE ONE ZERO ZERO EN ROUTE.
NOTE− Airports unable to accurately measure barometric pressures above 31.00 inches Hg will report the barometric pressure as missing or in excess of 31.00 inches Hg. Flight operations to or from those airports are restricted to VFR weather conditions.
REFERENCE− AIM, Chapter 7, Section 2, Altimeter Setting Procedures FAA Order JO 7110.65 Para 2-7-2.g, Altimeter Setting Issuance Below Lowest Usable FL
4−3−3 Radio Communications
d. Incorrect Cruising Altitude. If the aircraft is operating VFR at an altitude between 3,000 feet AGL to, but not including FL180, and reports at an incorrect cruising altitude for the direction of flight, issue a VFR cruising altitude advisory.
PHRASEOLOGY− V-F-R CRUISING LEVELS FOR YOUR DIRECTION OF FLIGHT ARE: (Odd/Even) ALTITUDES PLUS FIVE HUNDRED FEET.
NOTE−
Facilities located in those areas where VFR altitude separation is below 3,000 feet AGL or above FL 180 must provide appropriate phraseology examples for local use.
e. Altimeter Setting in Millibars (MBs). If a request for the altimeter setting in MBs is received, use the setting for the location nearest the position of the aircraft and convert to the MBs equivalent value using a MBs conversion chart. If the Mbs setting is not a whole number, always round down. (See TBL 4−3−1.)
TBL 4−3−1 Millibar Conversion Chart
MILLIBAR CONVERSION CHART inches millibars inches millibars inches millibars inches millibars inches millibars inches millibars inches millibars inches millibars 27.50 931.3 28.00 948.2 28.50 965.1 29.00 982.1 29.50 999.0 30.00 1015.9 30.50 1032.8 31.00 1049.8 27.51 931.6 28.01 948.5 28.51 965.5 29.01 982.4 29.51 999.3 30.01 1016.3 30.51 1033.2 31.01 1050.1 27.52 931.9 28.02 948.9 28.52 965.8 29.02 982.7 29.52 999.7 30.02 1016.6 30.52 1033.5 31.02 1050.5 27.53 932.3 28.03 949.2 28.53 966.1 29.03 983.1 29.53 1000.0 30.03 1016.9 30.53 1033.9 31.03 1050.8 27.54 932.6 28.04 949.5 28.54 966.5 29.04 983.4 29.54 1000.3 30.04 1017.3 30.54 1034.2 31.04 1051.1 27.55 933.0 28.05 949.9 28.55 966.8 29.05 983.7 29.55 1000.7 30.05 1017.6 30.55 1034.5 31.05 1051.5 27.56 933.3 28.06 950.2 28.56 967.2 29.06 984.1 29.56 1001.0 30.06 1017.9 30.56 1034.9 31.06 1051.8 27.57 933.6 28.07 950.6 28.57 967.5 29.07 984.4 29.57 1001.4 30.07 1018.3 30.57 1035.2 31.07 1052.2 27.58 934.0 28.08 950.9 28.58 967.8 29.08 984.8 29.58 1001.7 30.08 1018.6 30.58 1035.6 31.08 1052.5 27.59 934.3 28.09 951.2 28.59 968.2
Continue reading ↓ 120 of 958 passages shown