FSS

帅哥

3. Separate stopover legs by inserting a slant (/) at the end of each leg except the last. Begin each leg on a new line. EXAMPLE- AISR FF KANDYFYX KGNVYFYX KMIAYFYX DTG KDCAYFYX IFR VV12345 P3 ADW CHS 1300/ NIP 01+30 A5 BALL DP10 AP5 S/ MIA 02+30 NO DE-ICING EQUIPMENT M1FC FR:MI AI:BAT21 AT:F16/R TS:450 DDBQ TM1700 AE:280 RTBQ..TNU..OFF/FOE 0+15/MLC 0+45 AD:OFF TE:0030 RM:*REMARKS FB:0230 AA: PD:ON FILE BASOPS NB:1 CR:OD OP:ZCG CP:KOFFYXYX KFOEYXYX KMLCYFYX TA:1730 NOTE1. M1FC will autoaddress the CP: field, automatically extract the required items from the flight plan mask, and transmit a flight notification message to the destination BASOPS. MV is used in the FR field when sending a military VFR flight notification. JO 7110.10T 2/14/08 6-4-4 Flight Plan Handling 2. OASIS will autoaddress, automatically extract the required items from the flight plan dialog box, and transmit a flight notification message to all required facilities.

帅哥

4. For composite flights, specify type flight plan as the first item of each leg. 5. When en route delays are involved, include delay time in ETE. h. Apply military flight plan procedures to all civil aircraft landing at military bases. NOTE- It is the civil pilot's responsibility to obtain permission (from military authorities) to land at a military base. i. Apply civil flight plan procedure to civil aircraft departing military bases and en route to civil airports. j. When a pilot reports a departure time that is more than 2 hours prior to the current clock time, request an updated ETE based on the aircraft's present position. M1FC facilities amend the ETE in the existing flight plan, and activate the flight plan using the current time as the time of departure (M1FC will automatically calculate the updated ETA) and inform the pilot of any changes. 6-4-5. SUSPENDING FLIGHT NOTIFICATION MESSAGES a. Suspense the flight notification message or proposal message until acknowledgment is received from the addressee, then file in the completed file. b. If an acknowledgment is not received within the following time period, use the telephone or interphone to assure delivery. 1. Thirty minutes after departure if ETE is between 30 minutes and 2 hours. 2. One hour before ETA if ETE is 2 hours or more. 3. Thirty minutes after departure if RONVIP information is contained in remarks of a military flight notification.

帅哥

c. When an acknowledgment for a message is required and has not been received in accordance with the procedure described above, M1FC and OASIS facilities retransmit the complete message to the addressee. AISR facilities transmit the signal QSLQ and the complete aircraft identification to the addressee. d. M1FC. Messages awaiting acknowledgment are suspended on the Suspense List (S). It contains a list of all numbered Service B messages (except those numbered messages sent internally to other facilities in the same FSDPS family) and those messages transmitted from the flight plan mask not acknowl- edged by all the addressees. 1. The message identification is the aircraft identification for flight notifications and/or the message number for all other message types. 2. Acknowledgments received via NADIN shall be automatically processed if they are in the proper format. 3. Improperly formatted acknowledgments will be directed to the Service B edit queue (B flag). 4. The S list will display the aircraft identifica- tion and message numbers in chronological order of transmission times (first transmitted being at the top) and the addressees for each message with an asterisk appearing next to those that have not acknowledged. 5. If a transmission has not been acknowledged by all addressees within 30 minutes, an asterisk will automatically appear immediately preceding the message identification in the S list and an S flag is automatically displayed on the terminals enabled for Edit and Review Service B Communications (ERS) function.

帅哥

6. When an S flag is displayed, use the ERS keyword to display the S list in the edit mode. Use the RT keyword to retransmit the message to addressees who have not acknowledged the message. EXAMPLE- M1FC RT N12345 (ACID as it appears on the S list) RT 003 (MSG Number as it appears on the S list) 7. When an acknowledgm ent message is received from any other source, such as interphone/ telephone or facility guarding for the addressee, the specialist shall display the Edit and Review Suspense List (ERS) and use the AK keyword to acknowledge the message. EXAMPLE- M1FC AK DECAL01,KRCAYXYX e. OASIS. Messages awaiting acknowledgment are suspended on the Suspense List. It contains a list of all numbered Service B messages and those messages transmitted from the flight plan dialog box not acknowledged by all the addressees. JO 7110.10T 2/14/08 6-4-5 Flight Plan Handling 1. The message identification is the aircraft identification for flight notifications and/or the message number for all other message types. 2. Acknowledgments received via NADIN shall be automatically processed if they are in the proper format. 3. Improperly formatted acknowledgments will be directed to the Facility Message List for editing and will generate an alarm at designated worksta- tions. 4. The Suspense List will display the aircraft identification and message numbers in chronological order of transmission times (first transmitted being at the top) and the addressees for each message with an hourglass symbol appearing next to those that have not acknowledged.

帅哥

5. If a transmission has not been acknowledged by all addressees within 30 minutes, the message is considered overdue (red icon) and will generate a Suspense alarm at designated workstations. 6. Upon receipt of a Suspense alarm, retransmit the message to addressees who have not acknowl- edged the message by selecting (highlighting) the addressee(s) and clicking the ReTransmit button. 7. When an acknowledgm ent message is received from any other source, such as interphone/ telephone or facility guarding for the addressee, the specialist shall manually acknowledge the message by selecting (highlighting) the addressee and clicking the Ack button. 6-4-6. ACKNOWLEDGING FLIGHT NOTIFICATION MESSAGES Acknowledge a flight notification message or proposal as soon as practical after receipt. Prefix the acknowledgment with the letter R followed by a space and then the full aircraft identification. EXAMPLE- AISR FF KRCAYXYX DTG KRIUYFYX R DECAL01 NOTE- M1FC and OASIS will automatically acknowledge flight notification messages which are received in or have been edited into the correct format.

帅哥

6-4-7. ACTION BY ADDRESSEES In addition to acknowledging receipt of the flight notification message, addressees shall take the following actions: a. Military IFR flights. 1. Notify BASOPS, if applicable, of the inbound flight. 2. Upon request, deliver flight plan amend- ments to the ARTCC. 3. File the flight notification message in the DD file or with the daily traffic. 4. Forward the actual departure time to the destination BASOPS or the tie-in AFSS/FSS for the next destination. b. Military VFR flights. 1. Notify BASOPS, if applicable, of the inbound flight. 2. Suspense the message, awaiting closure/can- cellation/departure and assume destination station responsibility. 3. Forward the departure time to the destination BASOPS or the tie-in AFSS/FSS, and assume departure station responsibility. 4. M1FC. All flight notification messages are suspended on the Inbound List (I list). An entry on the I list will remain there until the flight plan is closed. Thirty minutes after the ETA (default value), if the flight plan has not been closed, it will automatically be placed in the Inbound Overdue Queue (I flag). NOTE- To display a flight plan on the I list, enter the keyword FP (ACID). To place a flight plan on the I list, use the keyword STI, use STIM to amend a flight plan.

帅哥

5. OASIS. All flight notification messages are suspended on the Inbound List. An entry on the list will remain there until the flight plan is closed. Thirty minutes after the ETA (default value), if the flight plan has not been closed, it is considered overdue (red icon) and will generate an Inbound alarm at designated workstations. NOTE- To display a flight plan on the Inbound List, select (highlight) the flight plan and click the Retrieve Flight Plan button. To place a flight plan on the Inbound List, click the Add Flight Plan button and enter information in the appropriate text boxes. JO 7110.10T 2/14/08 6-4-6 Flight Plan Handling c. If no information is received (e.g., departure time, revised ETA) indicating that the flight is still active prior to the void time, note this on the flight notification message and file.

帅哥

6-4-8. MAJOR FLIGHT PLAN CHANGES FROM EN ROUTE AIRCRAFT a. Change of Destination. 1. When a civil aircraft on a VFR flight plan or a military aircraft on any flight plan changes destination, obtain, as a minimum, the following information: (a) Type of flight plan. (b) Aircraft identification. (c) Aircraft type. (d) Departure point. (e) Old destination. (f) Present position. (g) Altitude and route. (h) New destination. (i) Estimated time en route. NOTE1. M1FC. If the flight plan mask is used to transmit the flight notification in lieu of the TB mask, the flight notification goes on the suspense list, acknowledgments are processed automatically, and flight plan and acknowledgments are placed in the DD file. 2. OASIS. If the Flight Plan dialog box is used to transmit the flight notification in lieu of the General Facility Message, the flight notification goes on the Suspense List, acknowledgments are processed automatically, and flight plan and acknowledgments are placed in the history file. 2. Transmit a revised flight notification mes- sage to the departure station, original, and new destination tie-in stations containing the type of flight, aircraft identification, aircraft type, departure point, new destination, new ETA, and in Remarks, aircraft position and time, the words ORIG DESTN followed by the identifier of the original destination. EXAMPLE- VFR Change of Destination: AISR FF KBOIYFYX KSEAYFYX DTG KCDCYFYX VFR N98789 C182/U PVU GEG 2230 $0VR SLC 1900 ORIG DESTN BOI M1FC FR:V AI:N9878 AT:C182/U TS:130 DDVU TM1900 AE:105 RT:SLC..TWF..MLD..LWS..GEG AD:GEG TE:0330 RMOVR SLC 1900 ORIG DESTN BOI FB: AA: PD: NB: CR: OP: CP:KBOIYFYX KSEAYFYX TA:2230 IFR Change of Destination: AISR FF KRCAYXYX KTIKYXYX KRIUYFYX DTG KCDCYFYX IFR DECAL01 T43/R SMF TIK 0230 $AP3NP3S OVR SLC 2330 ORIG DESTN RCA M1FC FR:MI AIECAL1 AT:T43/R TS:400 DD:SMF TM2330 AE:310 RT:SMF..SLC..GJT..AMA..OKC AD:TIK TE:0300 RMNP3 S OVR SLC 2330 ORIG DESTN RCA FB: AA: PD: NB: CR: OP: CP:KRCAYXYX KTIKYXYX KRIUYFYX TA:0230 NOTE1. M1FC. On VFR flight plans, M1FC will transmit and file the flight plan with the TS: and AE: fields blank. On IFR flight plans, these fields must be completed. If the TS: and AE: are unknown, 2 or 3 zeros may be used instead. 2. OASIS. If the Flight Plan dialog box is used to transmit VFR flight plans, OASIS will transmit and file the flight plan with the airspeed and en route altitude text boxes blank. For military IFR change of destination, use the General Facility Message to transmit changes to the closure points.

帅哥

b. Change from IFR to VFR. When a civil aircraft changes from an IFR to a VFR flight plan, obtain all flight plan information and then transmit a flight notification message to the destination tie-in station. Include the type of flight plan, aircraft identification and type, departure point, destination, ETA, and pertinent remarks. EXAMPLE- AISR FF KABQYFYX DTG KOAKYFYX VFR N87690 C182/U SFO ELP 2100 $CNLD IFR OVER BFL JO 7110.10T 2/14/08 6-4-7 Flight Plan Handling M1FC FR:V AI:N8769 AT:C182/U TS:130 DDVU TM1940 AE:105 RT:SLC..TWF..MLD..LWS..GEG AD:GEG TE:0330 RMCNLD IFR OVR TWF FB: AA: PD: NB: CR: OP: CP:KSEAYFYX TA:2310 NOTE- Obtaining the name of the original flight plan source may provide additional information if the aircraft becomes overdue. c. Military Change from IFR to VFR or VFR to IFR. When a military aircraft changes from IFR to VFR, or VFR to IFR, or requests that other significant information be forwarded, transmit this information to the destination station. EXAMPLE- AISR FF KTIKYXYX DTG KDENYFYX DECAL01 CHGD TO VFR RON M1FC ORIGINEN PRECEDENCE:FF TIME: ACK:N ADDR:KTIKYXYX TEXTECAL01 CHGD TO VFR RON 6-4-9. CHANGE IN ETA When an aircraft wants to change its estimated time en route (ETE), facilities shall secure a new estimated time of arrival (ETA) and forward the information to the destination tie-in station as a numbered message. The destination tie-in station shall acknowledge and, thereafter, use the new ETA as the standard for any necessary follow-up action; e.g., QALQ message. EXAMPLE- AISR FF KSEAYFYX DTG KBOIYFYX BOI001 SEA N34567 E2140 M1FC ORIGIN:BOI PRECEDENCE:FF TIME: ACK:Y ADDR:SEA TEXT:N34567 E2140 NOTE1. M1FC. M1FC will automatically acknowledge the message, change the ETA on the flight plan and inbound list, and store the message in the DD file without specialist intervention. 2. OASIS. OASIS will automatically acknowledge the message, update the ETA on the Inbound List, store the message in the history file, and notify the specialist that a Changed ETA message was received which matched an active flight plan. 6-4-10. FLIGHT PLAN CLOSURE Do not transmit arrival reports except under unusual circumstances or in the following cases: a. Transmit to any facility requested by the pilot, arrival or any other information involving FAA or Canadian MOT aircraft. EXAMPLE- AISR FF KDCAYFYX DTG KHHRYFYX HHR002 DCA N2 A0839 (Remarks, as appropriate) M1FC ORIGIN:HHR PRECEDENCE:FF TIME: ACK:Y ADDRCA TEXT:N2 A0839 (Remarks as appropriate) b. For U.S. military aircraft, transmit arrival reports to the departure station only when: 1. Requested by BASOPS. 2. Special military flights arrive. c. When a pilot closes a flight plan with a station that has not received a flight notification message, obtain as a minimum, the departure point, the flight planned destination point, and the station with which the flight plan was filed. 1. If the station receiving the closure is the tie-in station for the planned destination, transmit an arrival message to the departure station with the remark FPNO and the departure point and destination identifiers. The departure station shall relay the arrival information to the station holding the flight notification message in the active file. EXAMPLE- AISR FF KDCAYFYX DTG KMIVYFYX MIV001 DCA N8567 A1745 FPNO PHF NMK M1FC JO 7110.10T 2/14/08 6-4-8 Flight Plan Handling ORIGIN:MIV PRECEDENCE:FF TIME: ACK:Y ADDRCA TEXT:N8576 A1745 FPNO PHF NMK 2. If the station receiving the closure message is not the destination tie-in station, transmit a closure message to the destination tie-in station, including the aircraft identification, the closure time, the departure point, and destination. Remarks are optional. EXAMPLE- AISR FF KHUFYFYX DTG KDAYYFYX DAY003 N11ND C1217 LOU IND LNDD CMH M1FC ORIGINAY PRECEDENCE:FF TIME: ACK:Y ADDR:HUF TEXT:N11ND C1217 LOU IND LNDD CMH NOTE1. M1FC. Closure and arrival messages do not process automatically; manual intervention is required. 2. OASIS. OASIS automatically processes correctly formatted closure and arrival messages. OASIS will automatically remove the flight plan from the Inbound List, store the message in the history file, and notify the specialist that a Closed flight plan message was received which matched an active flight plan. 6-4-11. MILITARY FLIGHTS TO/FROM U.S. a. To U.S. If REQ ARR is in remarks, suspend the flight plan until arrival information is received from BASOPS and forward to the departure location. b. From U.S. If requested by BASOPS, include REQ ARR in remarks section of ICAO flight plan. Terminate suspense action only after receipt of an arrival message and delivery to BASOPS. JO 7110.10T 2/14/08 6-5-1 Military Operations Section 5. Military Operations 6-5-1. MILITARY TRAINING ACTIVITY a. Military Training Routes (MTR). 1. Unless otherwise covered in a letter of agreement, the tie-in AFSS/FSS/ARTCC/BASOPS for an MTR-scheduling activity shall transmit an unnumbered NADIN message. Use the assigned group code KAWP YFYX and for Alaska, use KFSSYFAK KAWPYFYX. Transmit as a single message whenever possible. EXAMPLE- AISR FF ADDRESSES DTG KDCAYFYX IR104 1400-1440 60 AND BELOW IR104 021530-021625 60 AND BELOW M1FC ORIGIN:FOD PRECEDENCE:FF TIME: ACK:N ADDR: ADDRESSES TEXT: IR505 1400-1600 60 AND BELOW 2. Multiple activities should be combined chronologically by use time(s) and transmitted (not more than 24 hours in advance) as a single message using only the format shown in the example below. EXAMPLE- AISR FF ADDRESSES DTG KDCAYFYX VR066 1330-1440 100 AND BELOW IR104 1400-1440 60 AND BELOW IR104 1545-1630 50 AND BELOW VR066 1600-1655 30 AND BELOW M1FC ORIGN:FOD PRECEDENCE:FF TIME: ACK:N ADDR: ADDRESSES TEXT: IR505 1440-1640 60 AND BELOW IR507 1700-1800 60 AND BELOW NOTE- Slow-speed, low-altitude training routes are not to be transmitted, briefed on, or posted. The contraction VLAR is not an approved contraction. b. Military Operations Area (MOA). 1. Transmit MOA messages only when the use times are other than what has already been published or otherwise covered in a letter of agreement. The controlling agency (usually an ARTCC) shall transmit an unnumbered NADIN message. Use the assigned group code KAWPYFYX and for Alaska, use KFSSYFAK KAWPYFYX. Use only approved MOA names as depicted in FAAO 7400.8 (DO NOT USE ABBREVIATIONS). EXAMPLE- AISR FF ADDRESSES DTG KZKCZRZX BISON MOA 1345-1550 ALT 025B180 2. Activity schedules should be combined and listed chronologically by use time(s) and transmitted (not more than 24 hours in advance) as a single NADIN message using only the format shown in the following example: EXAMPLE- AISR FF ADDRESSES DTG KZKCZRZX BISON MOA 1345-1550 ALT 025B180 BISON MOA 1600-1645 ALT 060B180 HILLTOP MOA 1600-1715 ALT 100B180 HOWARD MOA 1600-0200 ALT 090B180 REDHILLS MOA 1700-1800 ALT 080B100 c. A VR operation may be filed as a composite flight, IFR-VFR-IFR. Unless the BASOPS has the capability to do so, the tie-in AFSS/FSS shall transmit the IFR proposals in separate messages to the appropriate ARTCCs in accordance with paras 6-3-1, 6-3-2, 6-3-3, and 6-3-4. d. Information received from either the AFSS/ FSS/ARTCC/military scheduling activity or control- ling agency that modifies an MTR and MOA schedule shall be transmitted by an unnumbered message via Service B as defined in subparas 6-5-1a and b. e. Special Use Airspace (SUA). 1. M1FC. Properly formatted IRs, VRs, and MOAs are automatically placed on the list and the 0_queue. Messages are deleted from the list by automatic cancellation. The list is displayed by use of the following keywords: VM MO (ALL MOAs), or VM (MOA NAME) MO, IR, VM (STATE IDENT; i.e., VA) MO or VM IR, VM VR (ALL IRs or VRs), or VM 1756 VR (route specific). The route must be JO 7110.10T 2/14/08 6-5-2 Military Operations a four-digit character. Three-digit routes must be preceded by a zero. 2. OASIS. Properly formatted IRs, VRs and MOAs are automatically stored and are displayed using the Briefing functions. Messages are deleted by automatic cancellation. NOTE- The above procedures do not preclude a specialist from exercising his/her own judgment in providing further assistance when there is the slightest doubt about the adequacy of data being furnished to alert a pilot to the existence of an MTR or MOA. 6-5-2. AERIAL REFUELING TRACKS Upon notification from the ARTCC or a scheduling facility that a published refueling track will be activated and all or part of the activity will take place outside of restricted/warning areas or Class A airspace, the tie-in AFSS/FSS shall issue a NOTAM for the aerial refueling track. 6-5-3. SPECIAL MILITARY FLIGHTS a. Advise the ARTCC of flight notification messages, progress reports, changes en route, and related messages concerning Presidential or Vice Presidential flights. b. Alaska. In addition to the above, give advance notice to all RCCs along the route of flight. Telephone SARCC (907) 752-0227 or (907) 752-0128. Initiate communications search proce- dures if arrival is not received within 15 minutes after ETA and immediately notify ANRCC (Alaskan NORAD Region Control Center). 6-5-4. MILITARY FOREIGN FLIGHTS Generally, all military foreign flights are required to clear through specified military bases. Pilots normally will not file flight plans directly with an AFSS/FSS unless BASOPS is not available. BASOPS with no Service B access will forward an ICAO-type flight plan message via their tie-in AFSS/FSS for relay through the AFTN. BASOPS should specify all addressees, both ATC and operational, in accordance with ICAO standards and military regulations. 6-5-5. USAF/USN UNDERGRADUATE PILOTS To identify aircraft piloted by solo USAF/USN undergraduate student pilots (who may occasionally request revised clearances because they normally are restricted to flight in VFR conditions), the aircraft identification in the flight plan shall include the letter Z as a suffix. Do not use this suffix in ground-to-air communication. NOTE- USAF solo students who have passed an instrument certification check may penetrate cloud layers in climb or descent only. Requests for revised clearances to avoid clouds in level flight can still be expected. This does not change the requirement to use the letter Z as a suffix to the aircraft identification. 6-5-6. MESSAGE HANDLING Accept and forward messages from any military authority that concern aircraft movement, national defense, safety of flight, or emergencies. This includes, but is not limited to, the following: a. Flight Advisory Messages. 1. The tie-in AFSS/FSS originating the adviso- ry or receiving it from the originating BASOPS shall determine the AFSS/FSS nearest the aircraft's estimated position for VFR flights, or the appropriate ARTCC for IFR flights. Transmit a numbered message only to the facility identified. Include in the text, FLT ADVY, aircraft identification and type, and route of flight in that order. The last item shall be the identifier of the originating BASOPS or AFSS/FSS. EXAMPLE- AISR FF KZIDZRZX DTG KCOUYFYX COU005 ZID FLT ADVY A12345 T38 GVW J80 DAY DAY WX BLO LNDG MIN. SUG PROCD CVG. ADZ INTENTIONS DLVR 1625 GVW BASOPS M1FC ORIGIN:COU PRECEDENCE:FF TIME: ACK:Y ADDR: KZIDZRZX TEXT: A12345 FLT ADVY T38 GVW J80 DAY DAY WX BLO LNDG MIN. SUG PROCD CVG. ADZ INTENTIONS DLVR 1625 GVW BASOPS 2. Inform the originator if unable to deliver the flight advisory within 15 minutes. File the message. JO 7110.10T 2/14/08 6-5-3 Military Operations b. Electronic Counter Measure (ECM) Alerts. Transmit a numbered message via Service B to tie-in stations serving the addressees. If acknowledgements are not received within 1 hour, deliver via telephone. c. REACH and SAM Flight Messages. Forward to the airlift command post specified by the pilot if message contains request PASS TO AMC ACP. d. UNIDENTIFIED FLYING OBJECT (UFO)/ UNEXPLAINED PHENOMENA REPORTS. 1. Persons observing UFOs/Unexplained Phe- nomena should contact an UFO/Unexplained Phenomena Reporting Data Collection Center, such as the National Institute for Discovery Science (NIDS), the National UFO Reporting Center, etc. 2. If concern is expressed that life or property might be endangered, also refer the individual to the local police department. JO 7110.10T 2/14/08 6-6-1 IFR/DVFR ADIZ Flight Plans Section 6. IFR/DVFR ADIZ Flight Plans 6-6-1. AIRCRAFT MOVEMENT INFORMATION SERVICES (AMIS) WITHIN AN ADIZ-IFR In addition to the normal handling of aircraft operating in accordance with IFR, ADIZ penetration information or position reports on IFR operations outside of controlled airspace shall be forwarded immediately to the appropriate ARTCC. 6-6-2. AMIS WITHIN AN ADIZ-DVFR For security control of air traffic, specific information contained in flight plans filed by a pilot operating or proposing to operate in accordance with DVFR within an ADIZ shall be forwarded to NORAD. NOTE- Other offices, military and civil, as well as pilots, may file DVFR flight plans with an AFSS/FSS for forwarding to NORAD. 6-6-3. FORWARDING DVFR INFORMATION Except for Alaska, forward DVFR flight plan information to NORAD via the Service B NORAD address or by telephone as follows: NOTE1. The following NORAD addresses are group addresses that include all appropriate NORAD sectors and law enforcement: KZAMZQZX - the contiguous 48 states and San Juan. PHIRAOCZ - Hawaii. 2. NORAD will not send an acknowledgement and must be manually acknowledged from the suspense list by the specialist. (NORAD Headquarters assumes responsibility for receipt.) a. VFR. 1. M1FC - DVFR flight plans shall be entered into the M1FC Flight Plan mask with “V” in the FR: field for processing purposes. The applicable NORAD address must be manually entered into the CP: field. If “NORIV,” delete AFSS closure point address. 2. OASIS - DVFR flight plans shall be entered into the OASIS Flight Plan dialog box with “VFR” selected in the Flight Rules (FR) drop-down list box for processing purposes. The applicable NORAD address must be manually entered into the Closure Points text box. If “NORIV,” delete AFSS closure point address. b. Aircraft call sign. c. Number and type of aircraft. d. Altitude (within ADIZ). e. True airspeed. f. Time of departure. 1. When the flight plan information is provided before the aircraft's departure, enter as a proposal. Depart the flight plan immediately upon receipt of the actual departure time. 2. If arrangements cannot be made to obtain the actual departure time, forward the estimated time of departure (ETD). g. Point of departure. h. ETA. i. Destination. j. Remarks. 1. DVFR discrete transponder code. 2. True airspeed. 3. Estimated point of penetration of the ADIZ (latitude/longitude or fix-radial-distance). 4. Estimated time of penetration of the ADIZ. 5. If no arrival report (NORIV) will be filed with an appropriate aeronautical facility, include the abbreviation NORIV. Do not pass “NORIV” to NORAD. For Service B transmissions, precede “NORIV” remark with the percent (%) symbol. EXAMPLE1210 135 3442/9345 1446 NOTE- On a proposed flight plan, a single “X” may replace the DVFR discrete transponder code, true airspeed, estimated point of penetration of ADIZ, or the estimated time of penetration. EXAMPLE- Missing true airspeed: 1210 X 3442/9345 1446 Missing estimated point of ADIZ penetration and time JO 7110.10T 2/14/08 6-6-2 IFR/DVFR ADIZ Flight Plans with NORIV: 1210 135 XX %NORIV 6-6-4. STOPOVER DVFR FLIGHT PLANS Accept stopover DVFR flight plans filed on those aircraft planning one or more landings (within an ADIZ) en route to the destination, provided the information in para 6-6-3 is furnished for each segment of flight. Remind the pilot that 14 CFR Part_99 requires departure times to be made good and that a written record should be retained of these times at each departure point. 6-6-5. ADDRESSING DVFR FLIGHT PLAN MESSAGES Forward DVFR flight plan information (Reference para 6-6-3) as follows: a. Contiguous U.S. ADIZ. Forward DVFR flight plan information to NORAD. b. Alaskan ADIZ. Alaska ADIZ procedures are contained in a Letter of Agreement with the affected facility. c. Hawaiian ADIZ. Forward all DVFR flight plan information to NORAD. 1. M1FC - Enter “V” in the FR: field of the Flight Plan mask. 2. OASIS - Select “VFR” in the Flight Rules drop-down list of the Flight Plan dialog box. d. Canada. Routing DVFR flight plan messages to Canada. Compose DVFR messages pertaining to aircraft operating on a DVFR flight into Canada using the same procedure as for DVFR messages in the contiguous 48 states, except add “DVFR” in remarks. In addition, address and route to the appropriate transborder tie-in station. JO 7110.10T 2/14/08 6-7-1 Law Enforcement Messages Section 7. Law Enforcement Messages 6-7-1. LAW ENFORCEMENT ALERT MESSAGES (LEAM) The El Paso Intelligence Center (EPIC ) is an organization composed of 14 Federal agencies, including the FAA. The principal mission of EPIC is to facilitate the exchange of information and tactical intelligence on illicit narcotic trafficking and to support, through the intelligence process, Federal investigations concerning violation of Federal statutes as they apply to narcotics, aliens, currency, and weapons. EPIC issues two types of Law Enforcement Alert Messages (LEAM) that pertain to aircraft: Aircraft Lookout Alerts and Stolen Aircraft Alerts. Upon receipt of a LEAM from EPIC, take the following actions: a. Aircraft Lookout Alerts. 1. Keep active for 7 days, unless otherwise specified, or until cancellation is received. 2. Do not disseminate Suspect Aircraft Look- outs outside of official government facilities. As this data is inherently sensitive, unauthorized disclosure of information could compromise an investigation, endanger lives, and could result in crim inal prosecution or administrative action against the offender. REFERENCE- FAAO 1600.29, Para 7c(7), Stolen Aircraft Alert Procedure. NOTE- Paragraph 6-7-1a applies only to FSS and AFSS facilities in Alaska. AFSS facilities operating under contract of a Service Provider are not considered official government facilities and therefore will not receive Aircraft Lookout Alerts. b. Stolen Aircraft Alerts. Stolen Aircraft Alerts request recipients to watch for and report on the location and movement of an aircraft which has been reported stolen. 1. M1FC. (a) Keep active until included in a stolen aircraft summary or until cancelled. (b) Upon receipt, check local records for any aircraft contact, beginning with the date the aircraft was reported stolen. AFSSs shall notify their Flight Service Data Processing System (FSDPS) personnel to run the ENFORCE program as soon as practicable. (c) Relay any information available to the office listed on the alert. 2. OASIS. When OASIS receives a correctly formatted stolen aircraft alert, it processes it as follows: Checks the database for the past 15 days for a match. If no match is found, the LEAM is added to the Law Enforcement (LE) List with a green icon and no alarm. If a match is found, a Law Enforcement alarm is generated at designated workstations and the LEAM is placed on the LE List with a red icon. c. Stolen Aircraft Summaries. 1. Stolen Aircraft Summaries should be used to displace and consolidate all the individual stolen aircraft alerts received in the interim. 2. Monthly summaries are sent as soon as possible after the end of the month. They include aircraft registration numbers, aircraft type, and the date/time stolen and/or recovered. 3. Biannual summaries are sent in January and July. They list only those aircraft stolen in the past 2_years. d. All LEAM. 1. Distribute the Stolen Aircraft Alerts and Summaries, at the discretion of the Air Traffic Manager, to all parties, fixed base operators, airport managers, etc. REFERENCE- FAAO 1600.29, Para 7c(6), Stolen Aircraft Alert Procedure. 2. Check local records for the previous 24 hours. 3. Notify EPIC via Service B message (KDEAYYYX) or by telephone (1-888-873-3742 [USE EPIC], 1-915-760-2227 for the Air Watch Desk or 1-915-760-2200 for the General Watch Desk) of any contact within the past 24 hours. Also, notify your Regional duty officer for relay to the cognizant Transportation Security Administration Aviation Command Center. 4. Subsequent aircraft transactions shall be monitored and require the same notification as defined in subpara 6-7-1d3. JO 7110.10T 2/14/08 6-7-2 Law Enforcement Messages 5. Take no action regarding the aircraft, crew, or passengers other than normal air traffic job related functions. 6. Cease all actions upon receipt of a cancellation or a summary if the latter does not include this aircraft's registration number. 6-7-2. INITIATING LEAMs Any inquiries from airport managers, aircraft owners, or law enforcement entities to initiate an alert message shall be directed to EPIC. EPIC is interfaced with the National Crime Information Center, which gives them access to any stolen aircraft report entered by law enforcement agencies. FAA facilities shall not volunteer to relay this inform ation to EPIC . Assistance shall be limited to providing EPIC phone number(s) as specified in subpara 6-7-1d3 or advising the inquiring party to go through normal law enforcement channels. 6-7-3. FSDPS RESPONSIBILITIES The FSDPS shall: a. As a minimum, execute the ENFORCE program every 8 hours. In addition, run the ENFORCE program when requested. b. Not accept requests to search for individual aircraft from other than an FAA facility or office. c. Immediately notify the requesting facility or office when the program recognizes any aircraft registration number in the history file that matches one in the LEAM. Negative replies are required. JO 7110.10T 2/14/08 6-8-1 Nonemergency Parachute Jumping Section 8. Nonemergency Parachute Jumping 6-8-1. COORDINATION All pertinent information received from pilots prior to and during parachute jumping activity shall be forwarded to other affected ATC facilities. 6-8-2. PREJUMP RADIO COMMUNICATIONS a. When a prejump radio call required by 14 CFR Section 105.14 is received, contact the ARTCC sector or terminal facility in whose airspace the jump begins. If the controller has pertinent traffic, advise the jump aircraft to contact the control facility on the appropriate frequency for traffic information. b. If the aircraft is unable to contact the control facility direct, obtain traffic information and relay it to the aircraft. EXAMPLE“Cessna Four Zero Yankee, A-T-C advises traffic is a Cessna Four Twenty-One passing the Sputs intersection eastbound on Victor One Fifty-Seven at seven thousand.” JO 7110.10T 2/14/08 7-1-1 Messages and Formats Chapter 7. International Operations Section 1. Messages and Formats 7-1-1. GENERAL a. Title 14 of the U.S. Code of Federal Regulations (14 CFR) and the International Civil Aviation Organization (ICAO) require flight plans for all civil aircraft operation between the United States and foreign locations. Bureau of Customs and Border Protection requirements, international flight plan information, and Air Defense Identification Zone (ADIZ) penetration requirements are listed in other publications; e.g., the FAA International Flight Information Manual (IFIM), the Bureau of Customs and Border Protection Guide for Private Flyers, the Aeronautical Information Manual (AIM), 14 CFR Part 91, and 14 CFR Part 99. Designated airports of first landing are listed in the IFIM and the Airport/Facility Directory (A/FD). b. This chapter provides guidance to AIFSS, AFSS, FSS, and ARTCC facilities that transmit international flight movement messages. It incorpo- rates relevant information from ICAO and 14 CFR docum ents. All personnel required to handle international messages shall be familiar with ICAO documents containing instructions for preparing and transmitting communications for the AFTN circuits. These documents should be retained at FAA facilities which handle international messages. FAA personnel shall not act as agents for any aircraft operating or dispatching company. NOTE- International telecommunications instructions are found in International Standards and Recommended Practices, ICAO Annex 10 - Aeronautical Telecommunications, Volume II, and Document 7946, Manual of Teletypewriter Operating Practices. DOC 4444-RAC 501, Rule of the Air and Air Traffic Services, lists various ATS movement messages. Location indicators are contained in ICAO Document 7910, and Designators for Aircraft Operating Agencies Aeronautical Authorities and Services are contained in ICAO DOC 8585. FAA policies concerning acceptance of messages for international transmission are contained in 14 CFR Part 189. c. AFSSs and FSSs that transmit only occasional international messages or are unable to determine the correct addressing for all air traffic units concerned may refer the pilot to the proper gateway facility or address the message to the proper gateway facility for handling. The gateway stations and their areas of responsibilities are as follows: 1. New York AIFSS (ISP): Bermuda, Canada, North Atlantic, Europe, and Africa. 2. Miami AIFSS (MIA): Caribbean, South America, and Central America. 3. Kenai AIFSS (ENA): Alaska. 4. Oakland AIFSS (OAK): Pacific. d. To ensure that the gateway facility understands your request, include T (transmit) instructions in the first line of text. EXAMPLE- AISR FF KMIAYFYX DTG KICTYFYX MIA T ALL INTL ADDRESSEES (Text) M1 ORIGIN: PRECEDENCE.FF TIME: ACK:N ADDR:KMIAYFYX TEXT:MIA T ALL INTL ADDRESSEES (TEXT) 7-1-2. AIR TRAFFIC SERVICE (ATS) MESSAGES ATS as used in this section, as opposed to the meaning of the term within the FAA, is a generic term meaning and including: flight information, alerting, air traffic advisory, and air traffic control (ATC) services. 7-1-3. CATEGORIES OF MESSAGES The following ATS messages, with their normal priority indicators, are authorized for transmission by any means; i.e. , AFTN, NADIN, interphone, computer-to-computer, or via the aeronautical mobile service, as applicable. a. Emergency Messages. 1. Distress messages and distress traffic, including alerting (ALR) messages relating to distress (DETRESFA) phase-SS. JO 7110.10T 2/14/08 7-1-2 Messages and Formats 2. Urgency messages, including alerting mes- sages relating to an alert (ALERFA) phase or to an uncertainty (INCERFA) phase-SS. 3. Other messages concerning known or suspected emergencies which do not fall under subparas 7-1-3a1 and 2 and radio communications failure (RCF) messages-FF or higher as required. b. Movement and Control Messages. 1. Flight plan (FPL)-FF. 2. Amendment and coordination messages. (a) Departure (DEP)-FF. (b) Delay (DLA)-GG. (c) Arrival (ARR)-GG. (d) Boundary estimate (EST)-FF.* (e) Modification (CHG)-FF.* (f) Coordination (CDN)-FF.* (g) Acceptance (ACP)-FF.* 3. Cancellation (CNL)-GG.* 4. Clearances, flow control (SPL, CHG, CDN)-FF or DD.* 5. Transfer of control (TCX)-FF.* 6. Requests (RQS)-FF.* 7. Position reports (AIREP)-FF.* c. Flight Information Messages. 1. Traffic information-FF.* 2. Meteorological information (MET)-FF or GG. 3. Operation of aeronautical facilities and essential airport information (NOTAM)-GG. * Normally exchanged between ATC units via voice circuits. d. Technical Messages. Four categories of these messages are specified for use on computer-to-com- puter circuits only. They will not be sent on AFTN or NADIN circuits. 7-1-4. SERVICE MESSAGES a. NADIN will immediately generate a service message to an originator when incorrect code or routing indicators are detected. EXAMPLE- FF KZKCZQZX 031840 KSLCYTYX SVC. ZKC121 QTA RPT FF KZKCZQZX 031840 KSLCYTYX SVC. ZKC122 QTA MSR b. Assign the appropriate priority indicator to international service messages. When service messages refer to messages previously transmitted, assign the same priority prefix. Identify a service message by inserting SVC as the first item of the text. EXAMPLE- FF TJSJYFYX DTG KSEAYFYX SVC. RUMES 231015 (Text) 7-1-5. TRANSMISSION VIA NADIN International messages are generally introduced on NADIN for relay to AFTN circuits. a. M1FC facilities use the ICAO flight plan mask or TB mask. Addressee(s): Not to exceed 69 characters or seven addressees, each addressee separated by a space. b. AISR facilities handle international messages on NADIN for relay to AFTN as follows: 1. Start of message. New Line Key. 2. Preamble (priority, space, addressee(s). (a) Priority. Two-character precedence field. (b) Addressee(s). Not to exceed 69 characters or seven addressees, each addressee separated by a space. (c) End of Line (EOL) new line key. (d) End of Text (EOT) (enter function). c. OASIS facilities use the ICAO Flight Plan dialog box or General Facility Message. A maximum of 16_addressees can be entered. 7-1-6. TRANSMISSION OF ATS MESSAGES a. Air traffic service messages are interchanged in the international air traffic control system in the following modes: JO 7110.10T 2/14/08 7-1-3 Messages and Formats 1. The preferred step-by-step mode wherein each ACC/ARTCC sends forward the full current (updated) flight plan information as the flight progresses. 2. The simultaneous mode wherein information extracted from the filed flight plan (FPL) is sent simultaneously to all ATS units along the route of flight. In this mode, only amendments to the FPL, plus necessary control information, are forwarded from center to center as the flight progresses. b. Prepare and transmit ATS messages as set forth in this Order. Address these messages as follows: 1. Include an eight-character addressee indica- tor for each addressee. For M1FC and AIS R facilities, there can be no more than one line (69_characters including separating spaces) of addressees. When more than the allowable number of addressees are required, two or more transmissions of the message (each with no more than the allowable number of addresses) must be made. For OASIS facilities, a maximum of 16 addressees can be entered. The eight-letter combination addressee indicators are composed as follows: (a) The four-letter ICAO location indicator; e.g., MPTO. Use only those listed in ICAO DOC 7910 (Location Indicators). Some ICAO eight-char- acter addressees for Mexico and Canada are listed in FAAO JO 7350.8, Location Identifiers. (b) A four-letter designator for the facility type/office, or if no designator has been assigned, affix YXYX for military, ZZZX for aircraft in flight, or YYYX for all other cases; e.g., MTPPYYYX. (See Note.) REFERENCE- ICAO DOC 8585, Designators for Aircraft Operating Agencies, Aeronautical Authorities and Services. NOTE- The most frequently used and authorized designators are: YAYX Government Civil Aviation Authority (FAA Regional Office or Headquarters). YCYX Rescue Coordination Center (RCC). YDYX Authority Supervising the Aerodrome. YFYX Aeronautical Fixed Station (AFSS/FSS/IFSS/ IATSC). YMYX Meteorological Office (NWS). YNYX International NOTAM Office (NOF). YTYX Telecommunications Authority. YWYX Military Flight Operational Control Center (ACP) YXYX Military Organization (BASOPS). YYYX Organization not allocated a two-letter designator. ZOZX Oceanic Air Traffic Control Center. ZPZX Air Traffic Service Reporting Office. ZQZX Computer Facility at ACC/ARTCC. ZRZX ACC/ARTCC. (Center in charge of a FIR/UIR when the message is relevant to a VFR flight (AMIS)). ZTZX Aerodrome Control Tower. ZZZX Aircraft in flight. (c) A one-letter designator will appear following an air carrier designator to indicate the department or division of the organization addressed. 2. Filing time. A six-digit date/time group indicating the time the message is filed with the AIFSS/AFSS/FSS for transmission. c. Originator Indicator. Consists of an eight-letter sequence similar to an address indicator, identifying the place of origin and the organization originating the message. d. Supplementary Address and Origin Informa- tion. When the four-letter designators YXYX, ZZZX, or YYYX are used, identify the aircraft operator or organization at the beginning of the text preceding the start-of-ATS data symbol ( - - ), in the same order as in the addressee(s) and/or originator indicator(s). Where there is more than one such insertion, the last should be followed by the word “stop.” Where there are one or more insertions in respect to addressee indicators plus an insertion in respect to the originator indicator, the word FROM is to appear before that relating to the originator. e. When addressing flight plan messages or related amendments and flight plan cancellation messages to centers, use one of the four-letter designators as follows: 1. If message is relevant to IFR and: (a) The ARTCC is computer-equipped (U.S. ARTCCs), use ZQZX. (b) The center is not computer-equipped, use ZRZX. (c) R elevant to oceanic operations, use ZOZX. NOTE- Some centers may request specific addressing different from above. ZTZX and ZPZX are used internationally, but are not used in internal U.S. application. 2. If message is VFR (AMIS), use ZRZX. 3. If SVC or administrative, use ZRZX. JO 7110.10T 2/14/08 7-1-4 Messages and Formats 7-1-7. ORIGINATING MESSAGES a. Messages for ATS purposes may be originated with ATS units by aircraft in flight, or, through local arrangem ents, a pilot, the operator, or their designated representative. b. Accept air-filed flight plans or changes in destination information from aircraft inbound from foreign locations and, if requested by the pilot, enter Customs notification service. c. Do not accept round-robin flight plans to international locations, other than Canada. NOTE1. Only accept VFR round-robin flight plans to Canada if the filer of the flight plan is in possession of a valid numbered letter of authorization and adheres to the provisions contained therein. 2. Individual requests for the temporary authorization letter should be directed to the appropriate service area office. 3. The temporary authorization letter mandates the pilot, or responsible party, to provide the AFSS/FSS with a name, telephone number and authorization number for inclusion in the remarks section of the flight plan. 4. AFSS/FSS shall log a double (2) count for the round-robin flight plan. d. Do not accept assumed departure flight plans when the destination is in a foreign country other than Canada. e. Aircraft movement, control, and flight informa- tion messages for purposes other than ATS, such as operational control, shall be originated by the pilot, the operator, or their designated representative. 7-1-8. ADDRESSING MESSAGES a. Addressing the flight plan is determined by the point of departure, the destination, and the FIR boundaries to be penetrated during the course of the flight. b. Address IFR FPL messages to the ARTCC serving the airport of departure and to all ATS units (including oceanic) providing air traffic control service or concerned with flight along part or the whole of the route to be flown except FAA ATCTs and other conterminous U.S. ARTCCs. NOTE- Within the North Atlantic (NAT) Region, FPLs on turbojet aircraft transiting the control areas of Gander Oceanic, New York Oceanic, Reykjavik, Santa Maria Oceanic, Shanwick Oceanic and Sondrestrom (south of 70 degrees) within 90 nautical miles of the control area boundary, shall be addressed to the adjacent ACC to provide lateral separation. For all other aircraft, a 120 nautical mile proximity limit shall apply. c. Transmit all IFR FPLs to ARTCCs not less than 1 hour prior to the proposed departure time. Do not hold FPLs until after departure time and transmit as a combined FPL and DEP. Separate FPL and DEP messages must be transmitted. NOTE- ICAO flight plans do not require an acknowledgment to the transmitting facility. d. Address aircraft movement messages only to those ATS units responsible for the provision of relevant service, except when requested by the operator concerned, these messages, when transmitted via the AFTN, may also be routed, as specified by the operator or a representative to: 1. One addressee at the point of intended landing or point of departure. 2. Not more than two operational control units concerned. e. The ARTCC serving the departure airport shall transmit the DEP message on IFR aircraft to all known recipients of the FPL message. Flights between conterminous U.S. and Canada (excluding Gander Oceanic), Alaska, Hawaii and Puerto Rico do not require DEP messages. Discontinuance of DEP messages affecting the route of flight can only be accomplished by ICAO Regional Air Navigation Agreement. 7-1-9. FLIGHT PLAN FORMS AND INSTRUCTIONS a. Use the International Flight Plan, FAA Form 7233-4 (see Appendix A), ICAO Model Flight Plan Form displayed in DOC 4444, M1FC ICAO Flight Plan Mask, or OASIS ICAO Flight Plan dialog box and apply the procedures set forth in this section for flight: NOTE- Exceptions apply for flights to Canada and Mexico, see Section 4 and Section 5, for procedures. 1. Originating within conterminous U.S. and Canada and destined nonstop to points beyond those areas. JO 7110.10T 2/14/08 7-1-5 Messages and Formats 2. Originating within or transiting Pacific Flight Information Regions (FIR) and destined to or from FIRs beyond the Pacific Region including the North American (NAM) Region. NOTE1. The NAM Region encompasses the conterminous U.S., Alaska, and Canada to the North Pole. 2. FAA Form 7233-1, or Military Form DD-175, and domestic procedures are used for flights in the conterminous U.S., Canada, and the Honolulu, Alaskan, and San Juan domestic control areas. 3. AISR facilities record on the flight plan form the time that a flight plan is filed. This time will constitute evidence of the pilot's intention to comply with Customs, Immigration, and Public Health requirements and will be made available upon request from these authorities. 7-1-10. ICAO ATS MESSAGE FORMAT The following are examples of ICAO message types most likely to appear on AFTN/NADIN circuits. The number above the data corresponds to the field type numbers on the flight plan form (FAA Form 7233-4) and on the chart of Standard ATS Messages and Their Composition, Appendix A. a. Departure Message (DEP). ARTCCs are the designated ATS unit responsible for originating and transmitting DEP messages on all IFR aircraft departing airports within their center boundaries. IFR flight plans must be transmitted to ARTCCs at least 1 hour before departure. This allows ARTCCs to determine recipients of DEP message when domestic portions are transmitted to ARTCCs in M1 format. Do not hold FPLs and combine with DEP into a single message. b. Delay Message (DLA). Transmitted when departure of an aircraft, for which an FPL message has been transmitted, is postponed or delayed more than 30 minutes after the estimated time of departure contained in the FPL. c. Alerting Message (ALR). Relating to an overdue situation on an aircraft. d. Supplementary Flight Plan (SPL) information shall be sent to ATS units requesting the information (RQS).

帅哥

e. Arrival Message (ARR). Sent only on Canadian MOT, U.S. DOT, or FAA aircraft or upon request. f. Current Flight Plan (CPL) Message. Originated by and transmitted in a step-by-step mode between successive ACCs and between the last ACC to the control at the airport of intended landing. CPLs contain only information relevant to that portion of the route of flight which extends from the point of entry into the next control area or FIR to the airport of intended landing. g. Acceptance (ACP) Message. Transmitted when the data contained in a CPL message are found to be acceptable to the receiving ACC. h. Flight Plan Cancellation (CNL) Message. Transmitted when a current (CPL) or filed flight plan (FPL) message was transmitted and the flight is canceled. 7-1-11. FLIGHT PLAN CHANGES AND CANCELLATIONS a. Assume departure station duties when a flight plan change is received from an aircraft en route to a foreign location. REFERENCE- FAAO JO 7110.10, Para 6-4-8, Major Flight Plan Changes from En Route Aircraft, and FAAO JO 7110.10, Para 6-4-9, Change in ETA. b. An AFSS/FSS receiving a VFR flight plan cancellation report from aircraft en route to a foreign location shall transmit a cancellation message to the appropriate foreign tie-in facility. REFERENCE- FAAO JO 7110.10, Para 6-4-10, Flight Plan Closure. 7-1-12. AIR MOBILE SERVICE (AMS) a. Air Mobile Service (AMS) is an international air/ground communications network. It provides service to en route aircraft primarily in support of ATC and company operations, and collects meteoro- logical data for dissemination. Although in the U.S. this service is provided via contract (ARINC), FAA flight service facilities may be required to relay information on a case-by-case basis. b. The AMS network is composed of individual units geographically limited to areas where effective coordination and cooperation between ground stations are possible. c. For any individual route segment, the AMS communication requirements will normally be met by two or more network stations serving the flights on that route segment. In general, these primary stations JO 7110.10T 2/14/08 7-1-6 Messages and Formats serve the ACC serving the FIRs and the points of takeoff and landing. In some cases, additional suitably located stations are required to complete the communications coverage. d. Each of these stations may be required at some stage of the flight to exchange communications with the aircraft, and when not so engaged, to intercept, as required, communications exchanged between the aircraft and any one of the other stations. e. Stations providing regular network service to aircraft operation along route segments in an ACC's FIR are termed regular stations. Other network stations will only be required to assist communica- tions for that FIR in the event of communications failure. f. When communications permit, aircraft should transmit their messages to the primary station of the network from which they can most readily be delivered to their ultimate destination. In particular, aircraft reports required by ATC should be transmitted to the network station serving the ATC center in whose area the aircraft is flying. Conversely, messages to aircraft in flight should be transmitted direct to the aircraft by the network station serving the location of the originator. g. Messages passed from aircraft to a network station should be intercepted and acknowledged by other stations which serve locations where the information is also required. Such intercepts provide instantaneous delivery of information and eliminates the transmission of messages over the AFTN. Networks may not be used for transmission of aircraft reports except under the intercept principle. Acknowledgm ents of intercept shall be made immediately after the acknowledgment of receipt by the station to which the message was passed. In the absence of acknowledgment of intercept within 1_minute, the station accepting the message from the aircraft shall forward the message via the AFTN to the ultimate destination. h. In areas or on routes where radio operations, lengths of flights, or distance between stations require additional measures to ensure continuity of communications throughout the route segment, the stations shall share the responsibility of primary guard whereby each station will provide the primary guard for that portion of the flight during which the messages from the aircraft can be handled most effectively by that station. i. During its tenure of primary guard, each station will: 1. Be responsible for designating primary and secondary frequencies for communications with aircraft. 2. Receive all position reports and handle other messages from and to the aircraft essential to the safe conduct of the flight. 3. Be responsible for the action required in case of failure of communication. j. Transfer of primary guard from one primary station to the next will normally take place at the time of traversing FIR or control area boundaries. When communications conditions so demand, a station may be required to retain primary guard beyond geographical boundaries or release its guard before the aircraft reaches a boundary. 7-1-13. AIREPs (POSITION REPORTS) a. AIREPs are messages from an aircraft to a ground station. AIREPs are normally comprised of the aircraft's position, time, flight level, ETA over its next reporting point, destination ETA, fuel remain- ing, and meteorological information. When record- ing an AIREP on data terminals or written copy, the following procedures shall be used. 1. Each line shall begin at the left margin. 2. A new line shall be used for each transmission. 3. If communications allow, each report shall contain the following items in the order shown: (a) Message type ARP. (b) Call sign of the calling station (aircraft). (c) Text of the message. (d) Call sign of the station called or receiving station followed by the appropriate abbreviation to indicate received, readback, or no reply heard. (e) Call sign of station(s) acknowledging intercept followed by appropriate abbreviation to indicate received. (f) Designation of frequency used. EXAMPLE*2866QM 8903VO 13300YH JO 7110.10T 2/14/08 7-1-7 Messages and Formats 2932QI *5631TY 11384XM 2998QL 6532UA 13294YF 5628TO 10048WH 17904ZC *For Alaskan domestic use only. (g) Time in UTC of the communication. 4. Missing parts of the message text shall be indicated by the letter M. EXAMPLE- ARP CPC583 KBRO 2100 F330 MMTM 2128 ETA XMMMX 2248 FUEL 0324 KNEW RB MMMX R TO2103 b. AIREPs may be filed from any aircraft inflight within World Meteorological Organization (WMO) areas of responsibility in conformity with ICAO requirem ents for position, operational, or meteorological reporting in AIREP format. AIREP information shall be disseminated to ATC, company, and meteorological offices as required. AIREPs consist of three sections comprised of 12 items. AIREPs may be filed in one, two, or three sections as follows: 1. Section 1, Routine report. A position report (PSNRP) comprising the Message Type Designator -ARP and the following items: (a) Item 1, Aircraft identification. (b) Item 2, Position. Record position in latitude (degrees as two numerics, or degrees and minutes as four numerics, followed without a space by N or S) and longitude (degrees as three numerics, or degrees and minutes as five numerics, followed without a space by E or W) or as a significant point identified by a coded designator (two-to-five characters) or as a significant point followed by a magnetic bearing (three numerics) and a distance in nautical miles (three numerics) from the point, such as 4620N07805W, 4620N078W, 46N078W, LN, MAY or DUB180040. Precede significant point by ABM (abeam), if applicable. (c) Item 3, Time. Record time in hours and minutes UTC (four numerics). The time recorded must be the actual time of the aircraft at the position and not the time of origination or transmission of the report. (d) Item 4, Flight level or altitude. Record flight level as F followed by three numerics when on standard pressure altimeter setting, such as F370. Record altitude in meters followed by M, or in feet followed by FT, when on QNH. Record ASC (level) when climbing, or DES (level) when descending to a new level after passing the significant point. (e) Item 5, Next position and time over. Record the next reporting point and the estimated time over such reporting point, or record the estimated position that will be reached 1 hour later, according to the position reporting procedures in effect. Use the data conventions specified in subpara 7-1-13b1(b) Item 2, Position, for position. Record time in minutes past the hour (two numerics) or in hours and minutes UTC (four numerics) when necessary. EXAMPLE- PSNRP portion of AIREP prepared by De Ridder and addressed to Canadian Pacific Airlines (CPC) in Toronto and Mexico City: AISR FF CYYZCPCX MMMXXMZT 122105 KDRIYFYX ARP CPC583 KBRO 2100 F370 MMTM28 KNEW RB MMMM R TO2103] M1 ORIGIN:KDRIYFYX PRECEDENCE:FF TIME: ACK:N ADDR:CYYZCPCX MMMXXMZT TEXT:ARP CPC583 KBRO 2100 F370 MMTM28 KNEW RB MMMM R TO2103 NOTE- OASIS facilities shall transmit AIREPs using the Transmit General Facility Message dialog box. 2. Section 2. When reported by the pilot: (a) Item 6, Estimated Time of Arrival (ETA). Record ETA by the four-letter location indicator of the airport of first intended landing, or if no location indicator exists, the name of the airport followed by the estimated time of arrival at this aerodrome in hours and minutes UTC (four numerics). JO 7110.10T 2/14/08 7-1-8 Messages and Formats (b) Item 7, Endurance. Record fuel in hours and minutes (four numerics). 3. Section 3. A full AIR EP comprising a PSNRP, company inform ation, and en route meteorological information. (a) Item 8, Air temperature. Record PS (plus) or MS (minus), no space, followed by the temperature in degrees centigrade corrected for instrument error and airspeed, such as MS05. (b) Item 9, Spot wind or mean wind and position. Spot wind is used whenever practical and normally refers to the position given in subpara 7-1-13b1(b) Item 2, Position. When a spot wind is given for any other location, record its position. Whenever it is not practical to record spot wind, record the mean wind between two fixes, followed by the word “mean,” and the position of the midpoint between the two fixes. Record wind direction in degrees true (three numerics) and wind speed in knots (two or three numerics), separated by an oblique stroke, such as 345/55. Record the direction of variable winds of a given strength as VRB, such as VRB/10. Record light and variable winds or calm as LV. If wind position is required, record latitude and longitude to the nearest whole degree, using the data convention specified in Item 2, such as 22N180W. EXAMPLE- AIREP comprised of PSNRP and aircraft operator information. AISR FF CYYZCPCX MMMXXMZT 122105 KDRIYFYX ARP CPC583 KBRO 2100 F370 MMTM28 MMMX 2248 FUEL 0324 KNEW RB MMMX R TO2103 M1 ORIGIN:KDRIYFYX PRECEDENCE:FF TIME: ACK:N ADDR:CYYZCPCX MMMXXMZT TEXT:ARP CPC583 KBRO 2100 F370 MMTM28 MMMX 2248 FUEL 0324 KNEW RB MMMX R TO2103 (c) Item 10, Turbulence (TURB). Record severe turbulence as TURB SEV and moderate turbulence as TURB MOD. If turbulence is experienced in cloud, add INC (in cloud). If in subsonic flight, report severe turbulence as soon as possible after occurrence. This requires AIREP SPECIAL. Record and report moderate turbulence only if encountered within last 10 minutes prior to reaching position in subpara 7-1-13b1(b) Item 2, Position. If in transonic or supersonic flight, report severe or moderate turbulence as soon as possible after occurrence. This requires AIREP SPECIAL. (d) Item 11, Icing. Record severe icing as ICE SEV, moderate icing as ICE MOD. Report severe icing as soon as possible after occurrence. This requires AIREP SPECIAL. Record and report moderate icing only if encountered within last 10 minutes prior to reaching position in subpara 7-1-13b1(b) Item 2, Position. (e) Item 12, Supplementary Information. Record data which in the opinion of the pilot-incommand are of aeronautical interest. (1) Present Weather. Rain (RA), Snow (SN), Freezing rain (FZRA), Funnel cloud (FA) (waterspout or tornado), Thunderstorm (TS) on or near flight path, Front (FRONT). (2) Clouds. If heights of cloud bases and/or tops can be accurately ascertained, amount of clouds scattered (SCT) if clear intervals predominate, broken (BKN) if cloud masses predominate, or continuous (CNS) type of clouds only if cumulonim- bus (CB), and an indication of the bases (BASE) and/or the tops (TOP) together with the respective height indication F (number) or (number) or (number) M/ or (number) FT. (3) Turbulence and Icing. Moderate turbu- lence (TURB MOD) if in subsonic flight, or moderate aircraft icing (ICE MOD) observed prior to the last 10_minutes. (4) D-Value. Reading or radio altimeter minus reading of pressure altimeter set to 1013.2 mb and corrected for calibration and position error; record differences as PS (plus) or MS (minus), no space, followed by the number of meters or feet. EXAMPLE- Full AIREP: AISR FF CYYZCPCX MMMXXMZT KMIAYMYX 162215 TJSJYFYX ARP CPC583 2709N05415W 2212 F330 JO 7110.10T 2/14/08 7-1-9 Messages and Formats 23N056W 59 0035 FUEL 0324 M534 310/60 MEAN 2543N05532W TURB MOD ICE MOD SCT CB TOP F280 TJSJ RB TO2214 M1 ORIGIN:TJSJYFYX PRECEDENCE:FF TIME: ACK:N ADDR:CYYZCPCX MMMXXMZT KMIAYMYX TEXT:ARP CPC583 2709N05415W 2212 F330 23N056W 59 0035 FUEL 0324 M534 310/60 MEAN 2543N05532W TURB MOD ICE MOD SCT CB TOP F280 TJSJ RB TO2214 NOTE- Transmit to the WMO office serving the FIR where the report is made. (5) Operationally Significant Weather Ra- dar Echoes (echo or echo line). True bearing of center of echo or line and distance from aircraft in nautical miles; if appropriate, indicate weather intensifying or weakening and whether no gaps, some gaps, or frequent gaps are observed. (6) Significant differences between condi- tions encountered and those forecast for the flight, such as forecast thunderstorms not observed or freezing rain not forecast. (7) If the position of the phenomenon re- ported is not the same as the position given under subpara 7-1-13b1(b) Item 2, Position, report it after the phenomenon. 7-1-14. AIREP SPECIALS (ARS) a. Turbulence. TURB SEV encountered while in subsonic flight is reported as soon as possible after occurrence and requires AIREP SPECIAL. TURB MOD is reported only if encountered within 10_minutes prior to reaching reporting position. If in transonic or supersonic flight, TURB MOD and SEV is reported as soon as possible and requires AIREP SPECIAL. b. Icing. ICE SEV is reported as soon as possible after occurrence and requires AIREP SPECIAL. ICE MOD is reported only if encountered within last 10_minutes prior to reaching reporting position. EXAMPLE- AISR FF KMIAYMYX 211538 TJSJYFYX ARS PAA101 5045N02015W 1536 F310 ASC F350 51N030W 21 FUEL 0900 ICE SEV M1 ORIGIN:TJSJYFYX PRECEDENCE:FF TIME: ACK:N ADDR:KMIAYMYX TEXT: ARS PAA101 5045N02015W 1536 F310 ASC F350 51N030W 21 FUEL 0900 ICE SEV 7-1-15. ARTCC RELAY OF VFR MESSAGES ARTCC AISR operators shall relay all international VFR flight movement messages to the adjacent AIFSS/AFSS/FSS unless that facility is also an addressee. NOTE- If an overseas unit erroneously routes a VFR movement message to an ARTCC, the automatic NADIN switch will not divert it to an AIFSS, AFSS or FSS. JO 7110.10T 2/14/08 7-2-1 Customs Notification and ADIZ Requirements Section 2. Customs Notification and ADIZ Requirements 7-2-1. FLIGHT PLAN/CUSTOMS REQUIREMENTS Specific flight plan, Customs, and other requirements of individual countries are listed in the FAA International Flight Information Manual, IFIM. 7-2-2. INBOUND PRIVATE AIRCRAFT: CUSTOMS REQUIREMENTS a. All private aircraft entering U.S. airspace from a foreign port must provide at least 1 hour advance notice to the U.S. Customs and Border Protection at the point of first intended landing. Private aircraft arriving from the following location shall furnish a notice of intended arrival to Customs at the nearest designated airport to point of crossing for the first landing in the U.S. 1. Via the U.S./Mexican border or the Pacific Coast from a foreign place in the Western Hemisphere south of 33 degrees north latitude. 2. From the Gulf of Mexico and Atlantic Coasts from a place in the Western Hemisphere south of 30_degrees north latitude from any place in Mexico. 3. From the U.S. Virgin Islands. 4. From Puerto Rico, which if from Puerto Rico, are conducting VFR flight. b. This notice must be given at least 1 hour before crossing the U.S. coastline or border. The advance notice of arrival shall include the following: 1. Aircraft registration number. 2. Name of aircraft commander. 3. Number of U.S. citizen passengers. 4. Number of alien passengers. 5. Place of last departure. 6. Estimated time and location of crossing U.S. border/coastline. 7. Estimated time of arrival. 8. Nam e of intended U.S. airport of first landing. c. This notice may be furnished directly to the U.S. Customs and Border Protection by telephone, radio, or other means, or may be furnished through the FAA to the Customs and Border Protection. REFERENCE- U.S. Customs and Border Protection Guide for Private Flyers. d. When Customs flight notification service is requested, as indicated by inclusion of ADCUS in remarks, deliver the complete message to the associated Customs and Border Protection office as soon as practical. Relay additional or amended information to the Customs and Border Protection in order to properly comply with requirements; e.g., when actual arrival time varies from ETA by more than 15 minutes. 1. Provide the service only for those airports where availability is advertised in the AFD on flight notification messages. Pilots are responsible for making their own Customs arrangements for other airports. 2. Notify only the Customs and Border Protection office which, in turn, is responsible for notifying other inspection agencies concerned. e. Prefiled Customs notification requests for flights returning to the U.S. shall be delivered to the Customs and Border Protection office not earlier than 23 hours in advance. f. When an airborne aircraft identifies an airport of first intended landing that is not one of the designated airports, advise the pilot that this airport is not a designated airport of first landing. PHRASEOLOGY- BE ADVISED THAT YOUR DESTINATION IS NOT A CUSTOMS AND BORDER PROTECTION DESIGNATED FIRST LANDING AIRPORT. WHAT ARE YOUR INTENTIONS? NOTE- If a pilot insists on landing at a nondesignated airport, pass this information to nearest Customs and Border Protection office. g. When a flight notification message containing ADCUS in remarks identifies a nondesignated airport of first intended landing, notify the message JO 7110.10T 2/14/08 7-2-2 Customs Notification and ADIZ Requirements originator to advise the pilot that the filed destination is not a designated airport. PHRASEOLOGY- ADVISE (aircraft identification) THAT THE FILED DESTINATION IS NOT A CUSTOMS AND BORDER PROTECTION DESIGNATED FIRST LANDING AIRPORT. NOTE- The FAA role in this program is advisory only. Any appearance of action of enforcing compliance shall be avoided. Any questions should be directed to the U.S._Customs and Border Protection. h. AISR Facilities. Record the time of receipt of Customs requests. This time will constitute evidence of the pilot's intention to comply with Customs and Border Protection, Immigration, and Public Health requirements and will be made available upon request from these authorities. 7-2-3. INBOUND PRIVATE AIRCRAFT: ADIZ REQUIREMENTS a. Unless otherwise authorized by ATC, no person may operate an aircraft into, within, or across an ADIZ unless that person has filed a flight plan with an appropriate aeronautical facility. b. Unless otherwise authorized by ATC, no person may operate an aircraft into, within, or across an ADIZ unless that aircraft is equipped with a coded radar beacon transponder and automatic pressure altitude reporting equipment having altitude report- ing capability that automatically replies to interroga- tions by transmitting pressure altitude information in 100-foot increments. NOTE- This paragraph does not apply to the operation of an aircraft which was not originally certificated with an engine-driven electrical system and which has not subsequently been certified with such a system installed; e.g., a balloon or glider. c. Pilots of aircraft entering the United States through an ADIZ are required to comply with the provisions of 14 CFR Sections 99.17 and 99.19. d. Forward information on DVFR aircraft in- bound to the U.S. to NORAD via Service B or by telephone. Forward the following information: 1. Aircraft call sign. 2. Number and type of aircraft. 3. Altitude (within ADIZ). 4. True airspeed. 5. Time of departure. 6. Point of departure. 7. Destination. 8. ETA. 9. Remarks: DVFR discrete transponder code; estimated point of penetration of ADIZ (latitude/lon- gitude or fix-radial-distance); estimated time of penetration of ADIZ. NOTE1. See para 6-6-3 for M1FC and OASIS transmission information. 2. Further information on ADIZ requirements is contained in 14_CFR_Part_99. JO 7110.10T 2/14/08 7-3-1 Alerting Service