FSS

帅哥

Section 3. Alerting Service 7-3-1. GENERAL a. Alerting service shall be provided: 1. For all aircraft provided with air traffic control service. 2. Insofar as practical, to all other aircraft having filed a flight plan or otherwise known to an air traffic service. 3. To any aircraft known or believed to be the subject of unlawful interference. b. Additional information related to ICAO Search and Rescue procedures can be found in ICAO ANNEX 11, Chapter 5, Alerting Service. c. Apply domestic SAR procedures for the U.S. portion of the flight. 7-3-2. ALERTING PHASES a. Air traffic services units shall notify rescue coordination centers immediately when an aircraft is considered to be in a state of emergency in accordance with the following: 1. Uncertainty phase when: (a) No communication has been received from an aircraft within a period of 30 minutes after the time a communication should have been received, or from the time an unsuccessful attempt to establish communication with such aircraft was first made, whichever is the earlier. (b) An aircraft fails to arrive within 30_min- utes of the estimated time of arrival last notified to or estimated by air traffic services units, whichever is later, except when no doubt exists as to the safety of the aircraft and its occupants.

帅哥

2. Alert phase when: (a) Following the uncertainty phase, subse- quent attempts to establish communication with the aircraft or inquiries to other relevant sources have failed to reveal any news of the aircraft. (b) An aircraft has been cleared to land and fails to land within five minutes of the estimated time of landing and communication has not been reestablished with the aircraft. (c) Information has been received which indicates that the operating efficiency of the aircraft has been impaired, but not to the extent that a forced landing is likely. (d) An aircraft is known or believed to be the subject of unlawful interference. 3. Distress phase when: (a) Following the alert phase further unsuc- cessful attempts to establish communication with the aircraft and more widespread unsuccessful inquiries point to the probability that the aircraft is in distress. (b) The fuel on board is considered to be exhausted or thought to be insufficient to enable the aircraft to reach safety. (c) Information is received which indicates that the operating efficiency of the aircraft has been impaired to the extent that a forced landing is likely. (d) Information is received and it is reason- ably certain that the aircraft is about to make or has made a forced landing. b. In addition to the initial notification, the rescue coordination center shall, without delay, be furnished with: 1. Any useful additional information, especially on the development of the state of emergency through subsequent phases. 2. Information that the emergency situation no longer exists. 7-3-3. ALERTING MESSAGE CONTENTS a. The notification shall contain as much of the following information as is available in the order listed: NOTE- For supplemental flight plan information transmit an RQS Message. This information is used in the transmission of the INCERFA. EXAMPLE- AISR FF SVZMZRZX 231247 KMIAYFYX (RQS-N1234-SVMI-KMIA M1 JO 7110.10T 2/14/08 7-3-2 Alerting Service ORIGIN: PRECEDENCE:FF TIME: ACK:N ADDR:SVZMZRZX TEXTRQS-N1234-SVMI-KMIA 1. INCERFA, ALERFA, DETRESFA, as ap- propriate to the phase of the emergency. 2. Agency and person calling. 3. Nature of the emergency. 4. Significant information from the flight plan. 5. Unit which made last contact, time, and frequency used. 6. Last position report and how determined. 7. Color and distinctive marks of aircraft. 8. Any action taken by reporting office. 9. Other pertinent remark. EXAMPLE- AISR (INCERFA) SS MMMXYAYX DTG KSANYFYX (ALR-INCERFA/KSAN/OVERDUE -N1234S-VG -C172 -KRNO2000 -MMLP0130 -REQ ACK OR ARR ACFT OVERDUE YOUR STN) M1 (INCERFA) ORIGIN:SAN PRECEDENCE:SS TIME: ACK:N ADDR:MMMXYAYX TEXTALR-INCERFA/KSANYFYX/OVERDUE YOUR STATION -N1234S-VG -C172-SD/C -KSAN2000 -N0160A105-DCT TIJ DCT -MMLP2130 RMK/REQ ACK OR ARR) AISR (ALERFA) SS MMMXYAYX TEXTALR-ALERFA/KSAN/OVERDUE) (text remains same except for remarks information). M1 (ALERFA) ORIGIN: PRECEDENCE:SS TIME: ACK:Y ADDR:MMMXYAYX TEXTALR-ALERFA/KSANYFYX/OVERDUE (text remains same except for remarks information). AISR (DETRESFA) SS MMMXYAYX TEXTALR-DETRESFA/KSAN/OVERDUE (text remains same except for remarks information). M1 (DETRESFA) ORIGIN: PRECEDENCE:SS TIME: ACK:Y ADDR:MMMXYAYX TEXTALR-DETRESFA/KSANYFYX/OVERDUE (text remains same except for remarks information). NOTE- OASIS facilities shall transmit alerting messages using the Transmit General Facility Message dialog box. b. The cancellation of action initiated by the rescue coordination center is the responsibility of that center. EXAMPLE- AISR (CANCELLATION) SS MMMXYAYX 020618 KMIAYFYX (ALR-ALERFA/KMIAYFYX/CNL N1234 LOCATED) M1 (CANCELLATION) ORIGIN:_PRECEDENCE:SS_TIME: ACK:YADDR:MMMXYAYX TEXTALR-ALERFA/KMIAYFYX/CNL N1234 LOCATED NOTE- Transmit cancellation messages for INCERFA and DETRESFA using same format as above. JO 7110.10T 2/14/08 7-4-1 Canadian Movement and Control Messages (Transborder Flights Only) Section 4. Canadian Movement and Control Messages (Transborder Flights Only) 7-4-1. GENERAL Except as indicated in this section, handle transborder Canadian movem ent and control messages as described in Sections 1, 2, and 3. Do not pass ADCUS messages to NAV CANADA, as they no longer alert Canadian Customs to inbound flights. CANPASS authorizations are the obligation of the pilot, at the number in subpara 7-4-3a. 7-4-2. INBOUNDS FROM CANADA a. M1 will automatically acknowledge and suspense a VFR flight notification message if received in the proper format. Deliver VFR and IFR ADCUS to the U.S. Customs and Border Protection. File IFR messages after delivery. b. AISR facilities acknowledge receipt of flight notification messages as soon as practical by transmitting the letter R followed by the full aircraft identification; e.g., R N711VR. Suspense VFR flight notification messages until arrival or closure information is received. File IFR messages after delivery. 7-4-3. OUTBOUNDS TO CANADA a. When Customs notification service is requested advise the pilot to contact Canada's Private Aircraft Program for Customs (CANPASS) at 888-226-7277 and include CANPASS in the remarks section of the flight plan. If the pilot has contacted CANPASS, place CANPASS in the remarks section of the flight plan. Process outbound flight plans in accordance with Chapter 6 and subparas 7-4-3d and e. b. Accept Customs notification requests from inflight aircraft for relay via flight notification message only for airports of entry where Customs flight notification service is provided and when proposed ETA is during Customs service hours. NAV CANADA no longer passes ADCUS messages to Canadian Customs. c. Upon notification of departure of VFR flights, transmit a flight notification message directly to the destination Canadian relay facility. Include CANPASS in the remarks. NOTE1. M1 will format and address a flight notification message to a Canadian destination airport if the proposed flight plan was filed in accordance with subparas 7-4-3d and 7-4-3e. 2. AISR facilities address messages to the destination relay facility listed in FAAO JO 7350.8, Location Identifiers. AISR facilities transmit flight notification messages for VFR flights in accordance with para 6-4-4, Flight Notification Messages. Flight notification mes- sages included the type of flight plan as the first item of the notification message. CANPASS is required in the remarks, as appropriate. 3. OASIS facilities shall enter CANPASS in the Remarks text box of the Flight Plan dialog box. OASIS will automatically format and transmit a flight notification message to the tie-in destination facility. EXAMPLE- AISR FF CZYZZFZX DTG KBUFYFYX VFR N711VR C182 BUF YYZ 1735 CANPASS d. IFR Flight Plans 1. CANPASS Flight Plans. (a) M1FC. Insert an ampersand and the letter C (&C) as the first two entries in the OP field of the FP mask and use the four-letter Canadian location identifier for the destination airport in the AD: field. EXAMPLE- M1- AIRFILED FR:I AI:N1234 AT:C421/R TS:280 DDSM TM1800 AE:200 RTSM..CYYZ AD:CYYZ TE:0300 RMCANPASS FB:0400 AA: PD:JOE PILOT HBSM NB:2 CR:R/W TL: OP: CP: TA:2100 EXAMPLE- M1 - CANPASS FR:I AI:N1234 AT:C421/R TS:280 DDSM TM1800 AE:200 RTSM..CYYZ JO 7110.10T 2/14/08 7-4-2 Canadian Movement and Control Messages (Transborder Flights Only) AD:CYYZ TE:0300 RMCANPASS FB:0400 AA: PD:JOE PILOT HBSM NB:2 CR:R/W TL: OP:&C CP:CZYZZFZX TA:2100 (b) OASIS. Enter $CANPASS %ADCUS in the Remarks text box of a Canadian IFR flight plan. NOTE- The ADCUS remark is not transmitted but triggers the autoaddressing in OASIS. 2. Send a flight notification message on airfile IFR aircraft that has requested Customs notification. Place CANPASS (if prior notification) in the remarks section of the flight notification message. If the pilot files a flight plan, but gives no indication that CANPASS procedures have been implemented, or prefers to leave the notification off of the flight plan, leave the remarks section blank and allow the NAV CANADA specialists to handle the situation upon arrival. e. VFR Flight Plans. 1. M1FC. ADCUS (if airfiled) and CANPASS: Insert an ampersand and the letter C (&C) in the OP: field and use the four-letter Canadian location identifier for the destination airport in the AD: field. EXAMPLE- M1- AIRFILED FR:V AI:N1234 AT:C150 TS:90 DD:BUF TM1800 AE:045 RT:BUF..CYYZ AD:CYYZ TE:0030 RMCANPASS 2 FB:0330 AA: PD:JOE PILOT HBSM NB:2 CR:5/W TL: OP:&C CP:CZYZZFZX TA:1830 M1-CANPASS FR:V AI:N1234 AT:C150 TS:90 DD:BUF TM1800 AE:045 RT:BUF..CYYZ AD:CYYZ TE:0030 RMCANPASS FB:0330 AA: PD:JOE PILOT HBSM NB:2 CR:5/W TL: OP:&C CP:CZYZZFZX TA:1830 2. OASIS. Enter CANPASS in the Remarks text box. OASIS will automatically format and transmit a flight notification message to the tie-in destination facility. f. Refer to the Canada and North Atlantic IFR and VFR supplements to determine Customs hours of service, availability of Customs flight notification service (CANPASS), and the relay facility for infrequently used Airports of Entry not listed in FAAO JO 7350.8 Location Identifiers. g. Suspense VFR message until acknowledgment is received. REFERENCE- FAAO JO 7110.10, Para 8-5-2, Canadian Transborder. 1. If an acknowledgment is not received within 30 minutes after departure, M1 facilities retransmit the message. AISR facilities transmit the contraction REQ ACP (request acceptance) and the complete aircraft identification. EXAMPLE- AISR FF CZYZZFZX DTG KBUFYFYX REQ ACP N711VR 2. If acknowledgment is not received within 1_hour after departure, use interphone or telephone to deliver. In any event, assure delivery prior to ETA. 3. Refer to Section B of the Canada and North Atlantic IFR Supplements for Canadian FSS and ACC telephone numbers. h. When correcting or revising a message, retransmit the complete message preceded by the contraction CHG (change). EXAMPLE- AISR FF CZYZZFZX DTG KBUFYFYX CHG VFR N711VR C182 BUF YYZ 1845 CANPASS M1 ORIGIN: PRECEDENCE:FF TIME: ACK:Y ADDR:CZYZZFZX TEXT CHG VFR N711VR C182 BUF YYZ 1845 CANPASS AISR FF CZYZZFZX DTG KBUFYFYX CHG VFR N711VR C182 BUF YYZ 1845 CANPASS M1 JO 7110.10T 2/14/08 7-4-3 Canadian Movement and Control Messages (Transborder Flights Only) ORIGIN: PRECEDENCE:FF TIME: ACK:Y ADDR:CZYZZFZX TEXT: CHG VFR N711VR C182 BUF YYZ 1845 CANPASS NOTE- OASIS facilities use the Transmit General Facility Message dialog box when transmitting change messages. i. Do not transmit IFR flight notification messages except for military aircraft or Customs notification purposes. NOTE- Canada will not acknowledge receipt of these messages. j. When available, use interphone or telephone for flights of 30 minutes or less. 7-4-4. OUTBOUNDS TO CANADA DEPARTING FROM OUTSIDE FLIGHT PLAN AREA Accept flight plans regardless of departure point. We no longer forward ADCUS to CANADA; the current terminology is CANPASS (See para 7-4-1 and subpara 7-4-3a). a. Forward VFR flight plan information for aircraft proposing to depart from outside the facility's flight plan area to the tie-in AFSS/FSS for the departure point in the following format: 1. Aircraft identification. 2. Aircraft type. 3. Departure point. 4. Destination. 5. Proposed departure time/ETE. 6. Remarks. EXAMPLE- AISR FF KBUFYFYX DTG KCLEYFYX N711VR C182 BUF YYZ P1630/0030 CANPASS NOTE- OASIS facilities use the Flight Plan dialog box. OASIS will automatically format and transmit the proposal to the departure tie-in facility. b. Forward IFR flight plan information for aircraft proposing to depart from outside the facility's flight plan area in accordance with Para 6-3-1, Domestic IFR Flight Plans. If Customs flight notification service (ADCUS) is requested, advise the pilot to contact CANPASS at 888-226-7277; include CANPASS information as an intrafacility remark, and transmit the proposal message to both the ARTCC and the tie-in AFSS/FSS as follows: 1. M1 and OASIS facilities use procedures depicted in subpara 6-2-1a2(g) and Notes. 2. Enter the ARTCC computer address last. EXAMPLE- AISR FF KAOOYFYX KZOBZQZX DTG KDCAYFYX DCA2010001 FP N1234P P28R/A 150 PIT P0200 150 PIT..CIP..DKK..BUF..YYZ/0130 CANPASS c. Identify the tie-in AFSS/FSS, and advise the pilot to report departure time directly to that facility. NOTE- While the report may be relayed through another facility, it is the pilot's responsibility to notify the tie-in AFSS/FSS of the departure time. d. Upon receipt of the departure report, the tie-in AFSS/FSS is responsible for delivery of the flight notification message to Canada. 1. M1 facilities, enter the departure time in the TM: field of the proposed flight plan. Add &C to the OP: field. M1 will automatically transmit the flight notification message. 2. AISR facilities, transmit a flight notification message in accordance with para 6-4-4. NOTE- AISR facilities, if a departure report has not been received within 1 hour of the proposed departure time, cancel and file the proposed flight plan. 3. OASIS facilities, enter the departure time in the ETD text box of the Flight Plan dialog box. OASIS will automatically transmit the flight notification message. e. Acknowledgment from the departure point tie-in AFSS/FSS is required for both VFR and IFR proposals. 7-4-5. IFR FLIGHT PLANS DEPARTING CANADIAN AIRPORTS a. Accept IFR flight plans departing from Canadian airports and destined to the U.S. Transmit a proposal message in ARTCC HOST computer format to the associated Canadian ACC. Address messages to the ACC listed in FAAO JO 7350.8 Location Identifiers. JO 7110.10T 2/14/08 7-4-4 Canadian Movement and Control Messages (Transborder Flights Only) NOTE- FSSs and AFSSs in Alaska will still accept Canada to Canada IFR flight plans. b. Canada does not acknowledge for proposal messages. Do not expect or request acknowledgment. 7-4-6. SEARCH AND RESCUE MESSAGES Provide Search and Rescue, for flights inbound from Canada, in accordance with Chapter 8. JO 7110.10T 2/14/08 7-5-1 Mexican Movement and Control Messages (Transborder Flights Only) Section 5. Mexican Movement and Control Messages (Transborder Flights Only) 7-5-1. GENERAL Except as outlined in this section, handle transborder Mexican movem ent and control messages as described in Sections 1, 2, and 3. Transborder flight plans to Mexico with oceanic routing require the ICAO flight plan while the domestic flight plan may be used for flights with route over land. 7-5-2. INBOUNDS FROM MEXICO a. Flight notification messages. 1. M1FC/OASIS. When received in the proper form at, VFR flight notification messages are automatically acknowledged and suspended. Deliver VFR and IFR ADCUS messages to Customs and Border Protection. Store IFR ADCUS messages in the M1 DD file or OASIS History file, as appropriate. 2. AISR. Acknowledge receipt of a flight notification message as soon as practical by transmitting the letter R followed by the full ACID; e.g., R N7llVR. Deliver VFR and IFR ADCUS messages to Customs and Border Protection. Suspense VFR flight notification messages until arrival or closure information is received. File IFR messages. b. Search and Rescue. Provide search and rescue service in accordance with standard format/time increments listed in Section 3, Alerting Service, and Chapter 8, Search and Rescue (SAR) Procedures for VFR Aircraft. The departure station in Mexico is responsible for initiating SAR action until an acknowledgment of the flight notification message is received. 7-5-3. OUTBOUNDS TO MEXICO a. When customs notification service is requested for an airport-of-entry, include ADCUS, the number of persons on board, and the pilot's name in the remarks section of the flight plan. NOTE- Mexican customs regulations require that only interna- tional airports-of-entry may be used for first landing. REFERENCE- FAAO JO 7350.8, Location Identifiers. 1. If the pilot still intends to land at a destination other than an airport-of-entry, advise the pilot that the flight plan will not be used for Customs or search and rescue service in Mexico. 2. Transmit the flight notification message to the Regional Flight Dispatch Office, not the destination tie-in station. NOTE- If the correct addressee cannot be determined, transmit to the nearest border Regional Flight Dispatch Office. b. When a pilot files an IFR flight plan and Customs notification service is requested for an airport-of-entry, include ADCUS and the informa- tion listed in subpara 7-5-3a. Transmit to the appropriate ARTCC. NOTE- Mexico requires notification of an inbound aircraft before its arrival. The inclusion of ADCUS in the remarks section of an IFR flight plan or flight notification message satisfies this requirement. c. VFR Flight Plans. 1. Upon notification of departure of VFR flights, transmit a flight notification message. When Customs notification service is requested for an airport-of-entry include ADCUS and the informa- tion listed in subpara 7-5-3a. Address messages to the ICAO addressee for the appropriate destination location. 2. If a VFR flight plan is filed with a destination other than an airport-of-entry, transmit the flight notification message to the Regional Flight Dispatch Office, not the destination tie-in station. If the correct addressee cannot be determined, transmit to the nearest border Regional Flight Dispatch Office. NOTE- Facilities with interphone/telephone capability may relay flight notification messages by this method. REFERENCE- FAAO JO 7350.8, Location Identifiers. 3. M1FC. For automatic addressing and formatting, use V in the flight rules of the domestic flight plan mask. For automatic addressing, use &M in the OP: field. Use the four-letter (ICAO) location identifier for the destination airport. Manually JO 7110.10T 2/14/7-5-2 Mexican Movement and Control Messages (Transborder Flights Only) address the message to the designated Regional Flight Dispatch Office. EXAMPLE- M1FC FR:V AI:N1234S AT:C182/A TS:120 DD:SAT TM1200 AE:65 RT:SJT..DRT..MMCU AD:MMCU TE:0400 RMADCUS 4 ZUCHERMANN FB:0800 AA: PD: A. ZUCHERMANN HB:SAT NB:4 CR:R/B TL: OP:&M CP:MMCUXMXO TA:1600 M1FC will automatically address the CP: field if the 4-letter ICAO address is used in the AD: field, &M is used in the OP: field and the destination is an airport-of-entry. Only the tie-in facility will be addressed. 4. AIS R. Address messages to the ICAO addressee for the appropriate destination location. Transmit the following information: (a) Type of flight. (b) Aircraft identification. (c) Aircraft type. (d) Departure point. (e) Destination. (f) ETA. (g) Remarks. EXAMPLE- AISR FF MMCUXMXO DTG KSJTYFYX VFR N1234S C182 SJT MMCU 1400 $ADCUS 4ZUCHERMANN 5. OASIS . For automatic addressing and formatting, select VFR in the Flight Rules text box of the Flight Plan dialog box, and enter ADCUS in Remarks. d. If acknowledgment is not received within 30_minutes after departure, transmit a “request acceptance” message to the destination station tie-in addressee and to the Regional Flight Dispatch Office. Manually address the message to the designated Regional Flight Dispatch Office. REFERENCE- FAAO JO 7350.8, Location Identifiers. EXAMPLE- AISR FF MMCUXMXO MMMYXMXO REQ ACP N1234S M1FC ORIGIN:SJT PRECEDENCE:FF TIME:1130 ACK:Y ADDR:MMCUXMXO MMMYXMXO REQ ACP N1234S NOTE- OASIS facilities, use the Transmit General Facility Message dialog box to transmit “request acceptance” messages. e. The Regional Flight Dispatch Office involved will then normally send an acknowledgment to the departure station and assume responsibility for the flight notification message. f. If acknowledgment/acceptance is not received within 1 hour of the departure, use interphone/tele- phone or other available means to deliver the message to the appropriate Regional Flight Dispatch Office. g. Do not accept round-robin flight plans to Mexico. 7-5-4. MEXICAN REGIONAL FLIGHT DISPATCH OFFICE TELEPHONE NUMBERS (See Table 7-5-1.) TBL 7-5-1 Dispatch Office Phone Numbers Mexican Regional Flight Dispatch Office Telephone Numbers REGION IDENTIFIER TELEPHONE NUMBER CENTRO (CENTRAL) MMMX 01152 5 762-7062 01152 5 784-40-99 ext. 153 01152 5 762-58-77 ext. 153 NORESTE (NORTHEAST) MMMY 01152 83 454-020 ext. 141 NOROESTE (NORTHWEST) MMMZ 01152 67 23-114 01152 67 22-075 ext. 140 OCCIDENTE (WEST) MMGL 01152 36 890-121 ext. 32 and 167 SURESTE (SOUTHEAST) MMMD 01152 99 231-186 ext. 149 3/15/07 7110.65R CHG 2 JO 7110.10T CHG 1 7/31/08 JO 7110.10T 2/14/08 8-1-1 General Chapter 8. Search and Rescue (SAR) Procedures for VFR Aircraft Section 1. General 8-1-1. RESPONSIBILITY FOR SAR ACTION a. The departure station is responsible for SAR action until receipt of the destination station's acknowledgment for the flight notification message. This responsibility is then transferred to the destination station. b. The National SAR Plan assigns search and rescue responsibilities as follows: 1. To the military agencies for conducting physical search and rescue operations. 2. To the FAA for: (a) Providing emergency service to aircraft in distress. (b) Assuring that SAR procedures will be initiated if an aircraft becomes overdue or unreported. This is accomplished through the ATC system for IFR aircraft and the flight plan program and/or reports of overdue aircraft received at air traffic facilities for VFR aircraft. (c) Attempting to locate overdue or unre- ported aircraft by INREQ and ALNOT communica- tions search. (d) Cooperating in the physical search by making all possible facilities available for use of the searching agencies. c. Flight service stations serve as the central point for collecting and disseminating information on overdue or missing aircraft which are not on an IFR flight plan. d. ARTCCs serve as the central points for collecting information, coordinating with SAR, and conducting a communications search by distributing any necessary ALNOTs concerning: 1. Overdue or missing IFR aircraft. 2. Aircraft in an emergency situation occurring in their respective areas. 3. Aircraft on a combined VFR/IFR or an airfiled IFR flight plan, and 30 minutes have passed since the pilot requested IFR clearance, and neither communications nor radar contact can be established. 4. Overdue or missing aircraft which have been authorized to operate in accordance with a SVFR clearance. e. The ARTCC serves as the contact point for collecting information and coordinating with the RCC on all ELT signals. 8-1-2. OVERDUE AIRCRAFT ON FLIGHT PLAN Consider an aircraft on a VFR or DVFR flight plan overdue when it fails to arrive 30 minutes after its ETA and communications or location cannot be established. 8-1-3. OVERDUE AIRCRAFT NOT ON FLIGHT PLAN Consider an aircraft not on a flight plan as overdue at the actual time a reliable source reports it to be at least 1 hour late at destination. Based on this overdue time, apply the same procedures and action times as for aircraft on a flight plan. When such a report is received, verify (if possible) that the aircraft actually departed and that the request is for a missing aircraft rather than a person. Refer missing person reports to the appropriate authorities. REFERENCE- FAAO JO 7110.10, Para 8-2-1, Initial Action/QALQ; Para 8-3-1, INREQ; Para 8-4-1, ALNOT. JO 7110.10T 2/14/08 8-2-1 Overdue Aircraft Action Section 2. Overdue Aircraft Action 8-2-1. INITIAL ACTION/QALQ a. As soon as a VFR/DVFR aircraft (military or civil) becomes overdue, the destination station (including intermediate destination tie-in station for military aircraft) shall attempt to locate the aircraft by checking the destination airport and all adjacent airports that could accommodate the aircraft. Also, check appropriate ATCT facilities and ARTCC sectors through the area manager. If this communica- tions search does not locate the aircraft, transmit a QALQ to the departure location tie-in AFSS/FSS and when appropriate the DUAT vendor or AFSS/FSS where the flight plan information is on file. EXAMPLE- AISR FF KICTYFYX DTG KHONYFYX QALQ N12345 M1FC ORIGIN:ICT PRECEDENCE:FF TIME: ACK:N ADDR:MKL TEXTALQ Nl2345 NOTE1. OASIS facilities, use the Transmit Search and Rescue dialog box to transmit the QALQ. 2. If it is determined by the flight service specialist that the local field search cannot be completed before the INREQ transmission time, the QALQ shall be transmitted in time to receive the information for the INREQ message. The local field search shall continue without reference to time until completed. b. Use of long distance telephone in carrying out SAR responsibilities is authorized when appropriate. c. In the case of a U.S. registered aircraft, or any aircraft known to be piloted by or transporting U.S. citizens and en route within a foreign country or between two foreign countries, if the overdue report is received either from someone directly concerned or from aviation authorities of a foreign country, notify the Washington Communications Control Center immediately via Service B message addressed to RWA. d. Alaska. In addition to subparas 8-2-1a and c, address QALQ, INREQ, or ALNOT messages and replies to PANCYAYX and PAEDYCYX. NOTE- RCCs other than Elmendorf AFB (PAEDYCYX) are not on Service B and must be notified by telephone.

帅哥

e. Upon receipt of a QALQ message from the destination station concerning a flight for which a proposed flight plan was transmitted, the station which transmitted the proposal shall immediately transmit a message to the destination station containing all information not previously sent. After a local airport check, no further search action is required of the station which transmitted the proposal and no further messages will be received by this facility unless the search area extends into its flight plan area. f. M1FC. Properly formatted QALQs, INREQs, ALNOTs, and INCERFAs are automatically placed on the Search and Rescue (SAR) list. Messages are manually deleted from the SAR list using the keyword DM. g. OASIS. Properly formatted QALQs, INREQs, ALNOTs, INCERFAs, ALERFAs and DETRESFAs are automatically placed on the Search and Rescue list and annotated as SAR. A SAR alarm is generated at designated workstations. Messages are deleted from the SAR List by selecting (highlighting) the message to be deleted, expanding the entry and clicking the Delete Entry button. 8-2-2. ACTION BY DEPARTURE STATION ON RECEIPT OF QALQ Upon receipt of the QALQ inquiry, the departure station shall check locally for any information about the aircraft, and take the following action: a. If the aircraft is located, notify the destination station. The destination station will close the file on the aircraft. EXAMPLE- AISR FF KCOUYFYX DTG KHHRYFYX QALQ N12345 C1255 JO 7110.10T 2/14/08 8-2-2 Overdue Aircraft Action M1FC ORIGIN:COU PRECEDENCE:FF TIME: ACK:N ADDR:MKL TEXTALQ Nl2345 C1255 b. If unable to obtain additional information transmit a message to the destination station containing all information not previously sent. Include any verbal or written remarks made by the pilot which may be pertinent to the search. The data transmitted may be obtained from the flight plan information or any other pertinent information located in the DD file. This information can be transmitted using the SV 1, TB, and RV 1 format. Before transmitting, the message will require the correct header to be added to ensure the QALQ reply message is placed on the SAR list. EXAMPLE- AISR FF KLOUYFYX DTG KJBRYFYX QALQ N12345 C150/X 110 PBF D1235 85 LIT PAH 0130/0400 CLARENCE NEWBERN 601 E 12TH MKC 555-123-4567 2 POB WHITE/RED M1FC ORIGIN:RDU PRECEDENCE:FF TIME: ACK:N ADDRIE TEXTALQ N12345 FR:V AT:C182/T TS:120 DD:EQY TM291445 AE:035 RT:EQY..CAE ..ALD..CRG..DAB..ORL..ISM AD:ISM TE: 0400 RMREFUEL CRG FB:0430 AA: PD: MIKE T. BROWN DQY 704-555-1212 NB:2 CR:W/R/B OP: CP:KPIEYFYX TA:291845 A/C ID TIME DEP DESTN INFLT BRFG: N12345 14:50 EQY ISM RMKS:AVFP A/C ID TIME DEP DESTN INFLT BRFG: N12345 14:00 EQY ISM RMKS:VNR NOTE- OASIS facilities, retrieve data from the history files using the SAR Search dialog box, format the message and transmit using the Transmit Search and Rescue dialog box. 8-2-3. CANCELLATION OF THE QALQ If the aircraft is located by the destination station after the QALQ is sent, transmit a cancellation message addressed to all recipients of the QALQ. EXAMPLE- AISR FF KSTLYFYX DTG KHONYFYX QALQ N12345 CNLD M1FC ORIGIN:JBR PRECEDENCE:FF TIME: ACK:N ADDR:FOD TEXTALQ Nl2345 CNLD NOTE- OASIS facilities, transmit the QALQ cancellation using the Transmit Search and Rescue dialog box. JO 7110.10T 2/14/08 8-3-1 Information Requests (INREQs) Section 3. Information Requests (INREQs) 8-3-1. INREQ If the reply to the QALQ is negative or the aircraft has not been located within 30 minutes after it becomes overdue: a. The destination station shall transmit a numbered INREQ message to the departure station, flight watch control stations with communication outlets along the route, and other AFSS/FSSs and ARTCCs along the route. In addition, address RCC and DUAT vendors using the collective address KSARYCYX. 1. If the departure airport, route of flight, destination airport or alternate airports are within 50_miles of the Great Lakes, include Cleveland AFSS as an addressee. They will relay to Cleveland RCC. 2. Hawaiian stations shall give preliminary notification to Honolulu SARCC as follows: (a) Hilo by long distance telephone. (b) Honolulu AFSS shall use local telephone. (c) Secondary means for Hilo shall be Service B to Honolulu AFSS and then by telephone between Honolulu AFSS and the SARCC. b. Include all information in the INREQ message that will assist in search activities. NOTE- The National Search and Rescue Plan is outlined in the AIM, para 6-2-7. EXAMPLE1. AISR DD (appropriate eight-character identifiers and KSARYCYX) DTG KJBRYFYX JBR001 (appropriate three-character identifiers) INREQ N12345 BE36/R 150 PAH D1235 85 PAH LIT FEXHA 1635 DALE CARNINE 601 E. 12TH ST. MKC 555-765-4321 2 POB BROWN/WHITE (any other information available) M1FC ORIGIN:RDU PRECEDENCED TIME:ACK:Y ADDRAppropriate three-character identifiers and KSARYCYX TEXT:INREQ N12345 FR:V AT:C152/T TS:100 DD:EQY TM291445 AE:035 RT:EQY..CAE.. ALD..CRG..DAB..ORL..ISM AD:ISM TE:0400 RMREFUEL CRG FB:0430 AA: PDAVE JOHNSON DQY 704-555-1212 NB:1 CR:W/R/B OP: CP:KPIEYFYX TA:291845 A/C ID TIME DEP DESTN INFLT BRFG: N12345 14:50 EQY ISM RMKS:AVFP A/C ID TIME DEP DESTN INFLT BRFG: N12345 14:00 EQY ISM RMKS:VNR 2. AISR DD (appropriate eight-character identifiers and KSARYCYX) DTG KJBRYFYX JBR001 (appropriate three-character identifiers) INREQ N12345 BE36/R 150 PAH LIT DALE CARNINE 601 E. 12TH ST MKC WIFE REPORTS ETA 1230 M1FC ORIGIN:OLU PRECEDENCED TIME:ACK:Y ADDRappropriate three-character identifiers and KSARYCYX) TEXT:INREQ N12345 BE36/R GRI LBF DALE CARNINE 601 E. 12TH ST MKC WIFE REPORTS ETA 1230 NOTE- OASIS facilities, retrieve data from the history files using the SAR Search dialog box, format the message and transmit using the Transmit Search and Rescue dialog box. c. RCC does not have transmit capability. Acknowledgement is not required for messages to RCC. 8-3-2. ACTION UPON RECEIPT OF INREQ Stations receiving an INREQ shall take the following action: a. Seek information about the aircraft by checking facility records and all flight plan area airports along the proposed route of flight that could accommodate the aircraft. Notify appropriate ATCT facilities. Reply to the INREQ with a numbered message within 1 hour. If unable to complete the search within 1 hour, forward a status report followed by a final report when the search is complete. If the reply contains JO 7110.10T 2/14/08 8-3-2 Information Requests (INREQs) pertinent information such as aircraft location or position report, transmit to the destination station. EXAMPLE- AISR DD KLANYFYX DTG KHONYFYX HON001 LAN INREQ N1234A NO SVCS PROVIDED. FPA SRCH INCOMP AISR DD KLANYFYX DTG KHONYFYX HON002 KLANYFYX INREQ N1234A NEG INFO M1FC ORIGINAN PRECEDENCED TIME: ACK:Y ADDR:HON TEXT:INREQ Nl234A NO SVCS PROVIDED. FPA SRCH INCOMP ORIGINAN PRECEDENCED TIME: ACK:Y ADDR:HON TEXT:INREQ N1234A NEG INFO NOTE- Upon receipt of INREQs and ALNOTs, ATCTs and ARTCCs are required to check facility records, report findings to AFSS/FSS that alerted them within 1 hour, and retain in an active status until canceled. REFERENCE- FAAO JO 7110.65, Para 10-3-4, ALNOT. b. The destination station shall retransmit the information, as necessary, to all original addressees. c. Cleveland AFSS. When addressed, shall notify Cleveland U.S. Coast Guard RCC. d. Hawaiian stations, notify Honolulu SARCC by telephone. e. Facilities served by the expanded 800 system that have any portion of their incoming calls and/or Service B diverted to another facility shall notify that facility of the INREQ. The facility receiving diverted calls or Service B traffic shall check their records and advise of any information or contact with the aircraft. 8-3-3. CANCELLATION OF INREQ The INREQ originator shall transmit a numbered cancellation message containing the location of the aircraft to all INREQ addressees when the aircraft is located. Notify associated ATCT facilities. EXAMPLE- AISR DD (appropriate eight-character identifiers including KSARYCYX) DTG KLOUYFYX LOU001 (appropriate three-character identifiers) INREQ N1234A CNLD LCTD BWG M1FC ORIGIN:FOD PRECEDENCED TIME: ACK:Y ADDRappropriate three-character identifiers and KSARYCYX)TEXT:INREQ Nl234A CNLD LCTD DSM NOTE- OASIS facilities, transmit the INREQ cancellation using the Transmit Search and Rescue dialog box. JO 7110.10T 2/14/08 8-4-1 Alert Notices (ALNOTs) Section 4. Alert Notices (ALNOTs) 8-4-1. ALNOT If the replies to the INREQ are negative, or if the aircraft is not located within 1 hour after transmission of the INREQ, whichever occurs first, the destination station shall transmit an ALNOT. a. Address ALNOT messages to your Regional Operations Center and those facilities within the search area. In addition, address the DUAT vendors and RCC using the collective address KSARYCYX. The search area is normally that area extending 50_miles on either side of the proposed route of flight from the last reported position to the destination. The search area may be expanded to the maximum range of the aircraft at the request of the RCC or by the destination station. If the departure airport, route of flight, destination airport, or alternate airports are within 50 miles of the Great Lakes, include Cleveland AFSS as an addressee. They will relay to the Cleveland RCC. b. Alaska. Address to PANCYGYX, PANCY- AYX, and KSARYCYX. (Only AFSSs/FSSs in the ALNOT search area are required to acknowledge.) c. Include all information in the ALNOT message that will assist in search activities (same as INREQ plus any additional information received). EXAMPLE- AISR SS (appropriate ARTCC circuit codes as identified in subpara 10-1-4c, other addresses as identified in subpara 8-4-1a and KSARYCYX) DTG KRDUYFYX ALNOT N12345 BE36/R 150 RDU D1840 75 RDU EWN FEXHA 2140 CLARENCE E. NEWBERN 601 E 12TH MKC 555-123-4567 2 POB BROWN/TAN (any other information available) M1FC ORIGIN:RDU PRECEDENCE:SS TIME: ACK:N ADDRappropriate ARTCC circuit code as identified in subpara 10-1-4c, other addresses as identified in subpara 8-4-1a and KSARYCYX TEXT:ALNOT N12345 FR:V AT:C172/T TS:100 DD:EQY TM291445 AE:035 RT:EQY..CAE.. ALD..CRG..DAB..ORL..ISM AD:ISM TE:0400 RMREFUEL CRG FB:0430 AA: PD:JOHN M. BROWN DQY 704-555-1212 NB:3 CR:W/R/B OP: CP:KPIEYFYX TA:291845 A/C ID TIME DEP DESTN INFLT BRFG: N12345 14:50 EQY ISM RMKS:AVFP A/C ID TIME DEP DESTN INFLT BRFG: N12345 14:00 EQY ISM RMKS:VNR NOTE- OASIS facilities, retrieve data from the history files using the SAR Search dialog box, format the message and transmit using the Transmit Search and Rescue dialog box. d. Ten minutes after issuance of the ALNOT, call Tyndall AFB to ensure delivery of the ALNOT and to answer any inquiries. (Alaska: Call Fort Richardson, 11th RCC at (907) 428-7230, 800-420-7230, or DSN 317-384-6726.) NOTE- RCC (Tyndall AFB) phone numbers are: 800-851-3051 or 850-283-5955. Defense Switching Network 523-5955. 8-4-2. ACTION UPON RECEIPT OF ALNOT Upon receipt of an ALNOT, each station whose flight plan area extends into the ALNOT search area shall: a. Immediately conduct a communications search of those flight plan area airports which fall within the ALNOT search area that could accommodate the aircraft and which were not checked during the INREQ search. Notify the appropriate ATCT facilities. Request the appropriate law enforcement agency to check airports which cannot be contacted otherwise. Stations that have any portion of their incoming calls and/or Service B diverted to another facility shall notify that facility of the ALNOT. The facility receiving diverted traffic shall check their records and advise of any information or contact with the aircraft. b. Within 1 hour after receipt of the ALNOT, notify the originator of the results or status of the communications search. If the reply contains pertinent information, such as aircraft location or position report, transmit to the destination station. The destination station shall retransmit the informa- tion, as necessary, to all original addresses. EXAMPLE- AISR JO 7110.10T 2/14/08 8-4-2 Alert Notices (ALNOTs) SS KFODYFYX DTG KANBYFYX ALNOT N12345 FLD CK INCOMP AISR SS KFODYFYX DTG KANBYFYX ALNOT N12345 ACFT LCTD OG DHN M1FC ORIGIN:GFK PRECEDENCE:SS TIME: ACK:N ADDR:COU TEXT:ALNOT N12345 FLD CK COMPL NEG INFO ORIGIN:GFK PRECEDENCE:SS TIME: ACK:N ADDR:COU TEXT:ALNOT N12345 ACFT LCTD OG DIK c. Stations within the ALNOT search area shall record the ALNOT. (See Para 2-2-2j, Phraseology.) d. Request search assistance from aircraft travers- ing the search area. 8-4-3. REPORTING ALNOT STATUS TO RCC If the extended communications search fails to locate the aircraft or if 1 hour has elapsed since ALNOT transmission, whichever occurs first, the destination station shall call the RCC and, if appropriate, the Cleveland AFSS, which notifies the Cleveland RCC. Provide all pertinent available information about the overdue aircraft not already provided in the ALNOT to include: a. Agency and the person calling. b. Details of the flight plan. If the aircraft was not on a flight plan, include all the facts about the source of the report. c. Time the last radio transmission was received, by whom, and the frequency used. d. Last position report. e. Whether an ELT signal was heard or reported along the route of flight. f. Action taken and the proposed action by the reporting station. g. Upon request, furnish positions of other aircraft known to be along or near the route of flight of the missing aircraft. 8-4-4. CANCELLATION OF ALNOT The ALNOT remains current until the aircraft is located or the search is suspended by the RCC. The ALNOT originator shall then transmit a cancellation message with the location of the aircraft, if appropriate, addressed to all recipients of the ALNOT. Each facility shall notify all previously alerted facilities and agencies of the cancellation. EXAMPLE- AISR SS (appropriate ARTCC circuit codes as identified in subpara 10-1-4c, other addresses as identified in subpara 8-4-1a and KSARYCYX) DTG KEWNYFYX ALNOT N12345 CNLD ACFT LCTD JAX AISR SS (appropriate ARTCC circuit codes as identified in para 10-1-4c, other addresses as identified in subpara 8-4-1a and KSARYCYX) DTG KEWNYFYX ALNOT N1513B CNLD SEARCH SUSPENDED M1FC ORIGIN:OLU PRECEDENCE:SS TIME:ACK:N ADDRappropriate ARTCC circuit codes as identified in subpara 10-1-4c, other addressees as identified in subpara 8-4-1a and KSARYCYX) TEXT:ALNOT Nl5l3B CNLD ACFT LCTD MCK NOTE- OASIS facilities, transmit the ALNOT cancellation using the Transmit Search and Rescue dialog box. JO 7110.10T 2/14/08 8-5-1 Other SAR Actions Section 5. Other SAR Actions 8-5-1. CONTACT WITH AIRCRAFT CROSSING HAZARDOUS AREA When Lake, Island, Mountain, or Swamp Reporting Service programs have been established and a pilot requests the service, establish radio contact every 10_minutes (or at designated position checkpoints) with the aircraft while it is crossing the hazardous area. If contact with the aircraft is lost for more than 15_minutes, alert Search and Rescue. NOTE- Hazardous Area Reporting Service and chart depictions are published in the AIM, para 4-1-20. 8-5-2. CANADIAN TRANSBORDER a. Assume responsibility for initiating SAR action on transborder aircraft upon acknowledgment for the inbound flight notification message. b. When SAR action is initiated, the destination and departure facilities are responsible for all communications search actions within their respec- tive countries and for alerting their respective RCC. c. Canadian communications search procedures and action times are similar to U.S. procedures. They will address all SAR messages to the U.S. departure AFSS/FSS, which is then responsible for initiating SAR action for the U.S. portion of the route of flight. d. For inbounds from Canada, apply standard U.S. SAR procedures contained in this chapter for the U.S. portion of the route. Include the Canadian departure facility as an addressee on all SAR messages since that facility is responsible for initiating SAR action for the Canadian portion of the route of flight. e. Upon receipt of a Canadian QALQ, the departure AFSS/FSS shall take the following actions: 1. Check locally for any information about the aircraft. 2. If unable to obtain additional information, or within 15 minutes after receipt of the QALQ, transmit a message to the destination facility containing all flight plan information not previously sent. f. Upon receipt of a Canadian INREQ, the departure AFSS/FSS shall transmit an INREQ for the U.S. portion of the route of flight and reply to Canada within 1 hour in accordance with standard INREQ procedures. g. Upon receipt of a Canadian ALNOT, the departure AFSS/FSS shall transmit an ALNOT for the U.S. portion of the route and reply to Canada within 1 hour in accordance with standard ALNOT procedures. JO 7110.10T 2/14/08 9-1-1 General Chapter 9. FAA Weather Services Section 1. General 9-1-1. PURPOSE Surface meteorological observations are filed at scheduled and unscheduled intervals with stations having sending capability to WMSC for dissemina- tion on the Service A domestic aviation weather system. These reports are aviation routine weather reports (METAR) and aviation selected special weather (SPECI). All reports will include a report type and the six-digit time of the observation. Computer sorting and validation requires exact adherence to format and procedure at all times. 9-1-2. SCHEDULED TRANSMISSION TIMES a. METAR REPORTS. Prepare and code METAR reports for transmission between H+55 and H+00. 1. M1FC entry, use TA mask and specify H in the time field. 2. AISR entry, use /T procedures between H+46 and H+54. Use /D procedure between H+55 and H+00. 3. OASIS entry, use the Transmit Weather Observation dialog box. If the Hold box is checked, OASIS will hold the METAR report(s) until the listed METAR Transmit Time parameter. b. SPECI AND DELAYED OR CORRECTED REPORTS. Transmit SPECI, delayed or corrected reports as soon as possible after H+00. 1. M1FC entry, use TA mask and leave the time field blank. 2. AISR entry, use /D procedure. 3. OASIS entry, use the Transmit Weather Observation dialog box, leaving the Hold box unchecked. 9-1-3. DISTRIBUTION Most meteorological and NOTAM data exchanged outside of the facility is dependent on the Weather Message Switching Center Replacement (WMSCR). It is important to adhere to strict form at and procedures during normal operations, as well as during system interruption periods. a. Circuit interruption. Notify your tie-in facility, the AISR Customer Service Center, WMSCR and, if appropriate, the GS-200 Host facility of all outages. The M1FC AFSS facility should notify their FSDPS, AWP, and the appropriate telco servicing company. The OASIS AFSS facility should notify WMSCR and/or NADIN and the appropriate telco servicing company. b. All outage reports should refer to the correct circuit and/or equipment identification numbers. Facilities should obtain and record ticket numbers provided by AISR or the telco authority. c. AISR and WMSCR telephone numbers are as follows: 1. AISR HELPDESK 866-466-1336. 2. WMSCR (KNKAWMSC): Atlanta 770-210-7931. Salt Lake City 801-320-2045. JO 7110.10T 2/14/08 9-2-1 Pilot Weather Report (UA/UUA) Section 2. Pilot Weather Report (UA/UUA) 9-2-1. GENERAL Pilot Weather Reports (PIR EPs) are filed at unscheduled times with stations having sending capability to WMSCR for dissemination on the Service A domestic aviation weather system. These reports shall be entered into the system as individual reports, not appended to a surface observation. Entry shall only be between H+00 and H+55. 9-2-2. PREPARATION FOR TRANSMISSION a. M1FC entry, use WY mask. (See para 4-2-4.) b. AISR entry, use /D procedures. c. OASIS entry, use the Transmit PIREP dialog box. 9-2-3. RESPONSIBILITY AFSS/FSS specialists shall actively solicit PIREPs in conjunction with preflight and inflight communi- cations with pilots and assure timely dissemination of the PIREP information. Each facility should make special efforts to obtain PIREPs on departure and arrival weather conditions at airports within their flight plan area. 9-2-4. PIREP DISPLAY Maintain a PIREP display to conform with the particular requirements of your facility. If it is posted for internal use only, symbology may be used at the facility's discretion. If it is displayed as a pilot self-briefing aid, the use of contractions, such as OVC, shall be applicable. 9-2-5. SOLICITING PIREPs a. Solicit PIREPs for the affected area(s) when one or more of the following weather conditions exist, are reported, or forecast to occur: 1. Ceilings at or below 5,000 feet. 2. Visibility reported on the surface or aloft is 5_miles or less. 3. Thunderstorms and related phenomenon. 4. Turbulence of moderate degree or greater. 5. Icing of light degree or greater. 6. Wind shear. 7. Volcanic ash clouds are reported or forecast. NOTE- Pilots may forward PIREPs regarding volcanic activity using the format described in the Volcanic Activity Reporting Form (VAR) as depicted in the Aeronautical Information Manual, Appendix 2. b. Also, solicit PIREPs regardless of weather conditions when: 1. An NWS or ATC facility indicates a need because of a specific weather or flight assistance situation. 2. Necessary to determine flying conditions pertinent to natural hazards (mountain passes, ridges, peaks) between the weather reporting stations. 3. The station is designated as responsible for PIREPs in an offshore coastal area. c. Flight watch specialists shall solicit sufficient PIREPs to remain aware of flight conditions. d. To solicit PIREPs within a specific area, broadcast a request on NAVAIDs, transcribed broadcast facilities, or a selected communications frequency. PHRASEOLOGY- PILOT WEATHER REPORTS ARE REQUESTED (location/area). CONTACT (name) RADIO/FLIGHT WATCH ON (frequency) TO REPORT THESE CONDITIONS. 9-2-6. RECORDING OF PIREP DATA Record PIREP data directly into M1FC or OASIS, or on FAA Form 7110-2, or on other material deemed appropriate; e.g., 5'' x 8'' plain paper. 9-2-7. DATA TO BE INCLUDED IN PIREPs Include the following reports of flight conditions, as appropriate: a. Height and coverage of cloud bases, tops, and layers. b. Flight visibility. JO 7110.10T 2/14/08 9-2-2 Pilot Weather Report (UA/UUA) c. Restrictions to visibility and weather occurring at altitude. d. Air temperature and changes to temperature with altitude or range. e. Direction and speed of wind aloft. f. Extent and intensity of turbulence. REFERENCE- FAAO JO 7110.10, Para 9-2-8. g. Extent, type, and intensity of icing. REFERENCE- FAAO JO 7110.10, Para 9-2-9. h. Weather conditions and cloud cover through mountain passes and over ridges and peaks. i. Location, extent, and movement of thunder- storms and/or tornadic activity. j. Excessive winds aloft, LLWS , and other phenomena bearing on safety and efficiency of flight. 9-2-8. REPORTING TURBULENCE IN PIREPs a. Turbulence reports should include location, altitude, or range of altitudes, and aircraft type, and should include whether in clouds or clear air. The degree of turbulence, intensity, and duration (occasional, intermittent, and continuous) is deter- mined by the pilot. It is essential that the report is obtained and dissem inated when possible in conformance with the U.S. Standard Turbulence Criteria Table as follows: 1. Light. Loose objects in aircraft remain at rest. 2. Moderate. Unsecured objects are dislodged. Occupants feel definite strains against seat belts and shoulder straps. 3. Severe. Occupants thrown violently against seat belts. Momentary loss of aircraft control. Unsecured objects tossed about. 4. Extreme. Aircraft is tossed violently about, impossible to control. May cause structural damage. b. Report CAT or CHOP if used by the pilot to describe the type of turbulence. 9-2-9. REPORTING ICING CONDITIONS IN PIREPs a. Icing reports shall include location, altitude or range of altitudes, type aircraft, air temperature, intensity, and type of icing. b. Icing types. 1. Rime. Rough, milky, opaque ice formed by the instantaneous freezing of small super-cooled water droplets. 2. Clear. A glossy, clear or translucent ice formed by the relatively slow freezing of large super-cooled water droplets. 3. Mixed. A combination of rime and clear. c. Icing intensity. 1. Trace. Ice becomes perceptible. Rate of accumulation slightly greater than sublimation. Deicing/anti-icing equipment is not utilized unless encountered for an extended period of time (over 1_hour). 2. Light. The rate of accumulation may create a problem if flight is prolonged in this environment (over 1 hour). Occasional use of deicing/anti-icing equipment removes/prevents accumulation. It does not present a problem if deicing/anti-icing is used. 3. Moderate. The rate of accumulation is such that even short encounters become potentially hazardous, and use of deicing/anti-icing equipment or diversion is necessary. 4. Severe. The rate of accumulation is such that deicing/anti-icing equipment fails to reduce or control the hazard. Immediate diversion is necessary. 9-2-10. MEANS USED TO SOLICIT PIREPs Inform pilots of a need for PIREPs. The following methods may be used to collect PIREPs: a. During preflight weather briefings. b. On post-flight contacts. c. During regular air-ground contacts. d. Broadcast a request on NAVAID frequencies. e. Append a request on HIWAS, TIBS, VOR- TWEB, or TWEB broadcasts. f. Request PIREPs from air carrier and military operations offices, military pilot-to-forecaster units, and local aircraft operators. JO 7110.10T 2/14/08 9-2-3 Pilot Weather Report (UA/UUA) g. Solicit from other air traffic facilities. 9-2-11. PIREP CLASSIFICATION Categorize PIREPs as follows: a. URGENT. The following weather phenomena shall be classified as an URGENT (UUA) PIREP: 1. Tornadoes, funnel clouds, or waterspouts. 2. Severe or extreme turbulence (including clear air turbulence). 3. Severe icing. 4. Hail. 5. Low level wind shear. Classify LLWS PIR EPs as UUA if the pilot reports air speed fluctuations of 10 knots or more. Classify reports of LLWS with air speed fluctuations less than 10 knots as routine. If air speed fluctuation is not reported, classify PIREP as UUA. NOTE- LLWS defined as windshear within 2,000 feet of the surface. 6. Volcanic ash clouds. 7. Any other weather phenomena reported which are considered by the specialist as being hazardous, or potentially hazardous, to flight operations. b. ROUTINE. Classify as ROUTINE (UA) all PIREPs received except those listed above. 9-2-12. PIREP HANDLING Upon receipt of a PIREP, accomplish the following: a. Urgent. 1. Deliver to the ARTCC Weather Coordinator as soon as possible. 2. Deliver to the associated WSO as soon as possible. 3. Enter on Service A at the first opportunity. 4. Use in weather briefings, as appropriate. b. Routine. 1. Transmit on Service A as soon as practical. 2. Broadcast in accordance with established procedures in Chapter 2. 3. Use in weather briefings, as appropriate. 9-2-13. OFFSHORE COASTAL ROUTES When your station has been given responsibility for collecting offshore coastal route PIREPs: a. Include the coastal water area when soliciting PIREPs. At least one PIREP is required hourly regardless of weather conditions. b. Pacific. Hawaiian Island station areas coincide with the Honolulu ARTCC sectors and the entire Hawaiian area is designated as offshore areas for PIREP purposes. NOTE- The Flight Services Operations Area Office assigns PIREP responsibility for an offshore coastal area, route, or route segment to a specific station. The area assigned will be within the same ARTCC area as the station, and the station shall have adequate air-ground communications coverage over its assigned offshore area. 9-2-14. PIREP PREPARATION To assure proper dissemination of PIREPs to all system users, the encoding procedures listed below shall be followed: a. Identify each element by a Text Element Indicator (TEI). b. Ensure each report includes TEIs for message type, location, time, altitude/flight level, type aircraft, and at least one other to describe the reported phenomena. c. Precede each TEI, except message type, with a space and a solidus (/). d. Follow each TEI, except altitude/flight level, with a space. e. Insert zeros in reported values when the number of digits in the report is less than the number required by the format. f. Use only authorized aircraft designators and contractions. g. In the location TEI, include any three-letter identifier to describe locations or routes. h. Omit entries of TEIs, except as listed in subpara_9-2-14b, for which no data was reported. JO 7110.10T 2/14/08 9-2-4 Pilot Weather Report (UA/UUA) 9-2-15. PIREP FORMAT Using TEIs as described below, prepare PIREPs for system entry in the following format: NOTE- OASIS. If using the “Folded” Transmit PIREP dialog box, each TEI must be specified and can be entered in any order. OASIS will automatically format the message before transmission. a. UUA or UA. Message type - Urgent or Routine PIREP. b. /OV. 1. Location in reference to a VHF NAVAID or an airport, using the three or four letter identifier. If appropriate, encode the identifier, then three digits to define a radial and three digits to define the distance in nautical miles. EXAMPLE/OV KJFK /OV KJFK107080 /OV KFMG233016/RM RNO 10SW

帅哥

2. Route segment. Two or more fixes, as in subparas 9-2-15b1 and b2 examples, to describe a route. EXAMPLE/OV KSTL-KMKC /OV KSTL090030-KMKC045015 c. /TM. Time that the reported phenomenon occurred or was encountered. Report time in four digits UTC. EXAMPLE/TM 1315 d. /FL. Altitude/flight level. Enter the altitude in hundreds of feet (MSL) where the phenomenon was first encountered. If not known, enter UNKN. If the aircraft was climbing or descending, enter the appropriate contraction (DURC or DURD) in the remarks/RM TEI. If the condition was encountered within a layer, enter the altitude range within the appropriate TEI describing the condition. EXAMPLE/FL093 /FL310 /FLUNKN /RM DURC e. /TP. Type aircraft. Enter aircraft type. If not known, enter UNKN. Icing and turbulence reports shall always include the type aircraft. EXAMPLE/TP AEST /TP B74A /TP P28R /TP UNKN f. /SK. Sky condition. Report height of cloud bases, tops, and cloud coverage as follows: 1. Enter the height of the base of a layer of clouds in hundreds of feet (MSL). Enter the top of a layer in hundreds of feet (MSL) preceded by the word “-TOP.” If reported as clear above the highest cloud layer, enter a space and “SKC” following the reported level. EXAMPLE/SK OVC100-TOP110/ SKC /SK OVC015-TOP035/OVC230 /SK OVC-TOP085 2. Use authorized contractions for cloud cover. EXAMPLE- BKN FEW OVC SCT SKC 3. Cloud cover amount ranges will be entered with a hyphen and no spaces separating the amounts; i.e., BKN-OVC. EXAMPLE/SK SCT-BKN050-TOP100 /SK BKN-OVCUNKN-TOP060/BKN120-TOP150/ SKC 4. Unknown heights are indicated by the contraction UNKN. EXAMPLE/SK OVC065-TOPUNKN 5. If a pilot indicates he/she is in the clouds, enter IMC in the remarks. EXAMPLE/SK OVC065-TOPUNKN /RM IMC 6. When more than one layer is reported, separate layers by a solidus (/). g. /WX. Flight visibility and flight weather. Report weather conditions encountered by the pilot as follows: 1. Flight visibility, if reported, will be the first entry in the /WX field. Enter as FV followed by a two-digit visibility value rounded down, if neces- sary, to the nearest whole statute mile and append “S M” (FV03SM). If visibility is reported as unrestricted, enter FV99SM. JO 7110.10T 2/14/08 9-2-5 Pilot Weather Report (UA/UUA) 2. Enter flight weather types using one or more of the standard surface weather reporting symbols contained in TBL 9-2-1. TBL 9-2-1 Weather Type and Symbols Type METAR Code Drifting / Blowing Snow . . . . . . . . . DRSN/BLSN Drifting Dust . . . . . . . . . . . . . . . . . . DRDU Drifting Sand . . . . . . . . . . . . . . . . . . DRSA Drizzle/Freezing Drizzle . . . . . . . . . DZ/FZDZ Dust / Blowing Dust . . . . . . . . . . . . DU/BLDU Duststorm . . . . . . . . . . . . . . . . . . . . . DS Fog (vis < 5/8SM) . . . . . . . . . . . . . . FG Freezing Fog . . . . . . . . . . . . . . . . . . FZFG Freezing Rain . . . . . . . . . . . . . . . . . . FZRA Funnel Cloud . . . . . . . . . . . . . . . . . . FC Hail (aprx 1/4” dia or more) . . . . . . GR Hail Shower . . . . . . . . . . . . . . . . . . . SHGR Haze . . . . . . . . . . . . . . . . . . . . . . . . . HZ Ice Crystals . . . . . . . . . . . . . . . . . . . IC Ice Pellets/ Showers . . . . . . . . . . . . . PL/SHPL Mist (vis 5/8SM or more) . . . . . . . . BR Patchy Fog . . . . . . . . . . . . . . . . . . . . BCFG Patchy Fog on part of Arpt . . . . . . . PRFG Rain / Showers . . . . . . . . . . . . . . . . . RA/SHRA Sand / Blowing Sand . . . . . . . . . . . . SA/BLSA Sandstorms . . . . . . . . . . . . . . . . . . . . SS Shallow Fog . . . . . . . . . . . . . . . . . . . MIFG Sml Hail/Snow Pellet Showers . . . . SHGS Sml Hail/Snow Pellets . . . . . . . . . . . GS Smoke . . . . . . . . . . . . . . . . . . . . . . . FU Snow Grains . . . . . . . . . . . . . . . . . . . SG Snow / Showers . . . . . . . . . . . . . . . . SN/SHSN Spray . . . . . . . . . . . . . . . . . . . . . . . . PY Squalls . . . . . . . . . . . . . . . . . . . . . . . SQ Thunderstorm . . . . . . . . . . . . . . . . . . TS Tornado/Waterspout . . . . . . . . . . . . . +FC Unknown Precipitation . . . . . . . . . . UP Volcanic Ash . . . . . . . . . . . . . . . . . . VA Well developed Dust/Sand Whirls . . PO 3. Intensity of precipitation (- for light, no qualifier for moderate, and + for heavy) shall be indicated with precipitation types, except ice crystals and hail, including those associated with a thunderstorm and those of a showery nature. 4. Intensity of obscurations shall be ascribed as moderate or + heavy for dust and sand storms only. No intensity for blowing dust, blowing sand, or blowing snow. EXAMPLE/WX FV01SM +DS000-TOP083/ SKC /RM DURC 5. When more than one form of precipitation is combined in the report, the dominant type shall be reported first. EXAMPLE/WX FV00SM +TSRAGR /WX FV02SM BRHZ000-TOP083 6. When FC is entered in /WX, FUNNEL CLOUD is spelled out on /RM. When +FC is entered in /WX, TORNADO or WATERSPOUT is spelled out in the /RM TEI. EXAMPLE/WX FC /RM FUNNEL CLOUD /WX +FC /RM TORNADO or WATERSPOUT 7. When the size of hail is stated, enter in 1/4” increments in remarks /RM TEI. 8. The proximity qualifier VC (Vicinity) is only used with TS, FG, FC, +FC, SH, PO, BLDU, BLSA, and BLSN. EXAMPLE/WX FV02SM BLDU000-TOP083 VC W 9. When more than one type of weather is reported enter in the following order: 1) TORNADO, WATERSPOUT, OR FUNNEL CLOUD; 2) Thun- derstorm with or without associated precipitation; 3)_Weather phenomena in order of decreasing predominance. No more than three groups in a single PIREP. 10. Weather layers shall be entered with the base and/or top of the layer when reported. Use the same format as in the /SK TEI. EXAMPLE/WX FU002-TOP030 h. /TA. Air Temperature. Report outside air temperature using two digits in degrees Celsius. Prefix negative temperatures with an M; e.g., /TA 08 or /TA M08. i. /WV. Wind direction and speed. Encode using three digits to indicate wind direction (magnetic) and two or three digits to indicate reported wind speed. When the reported speed is less than 10 Kts use a leading zero. The wind group will always have “KT” appended. EXAMPLE/WV 28080KT /WV 28008KT /WV 280105KT JO 7110.10T 2/14/08 9-2-6 Pilot Weather Report (UA/UUA) j. /TB. Turbulence. Report intensity, type, and altitude as follows: 1. Intensity. Enter duration if reported by the pilot (intermittent, occasional continuous) and intensity using contractions LGT, MOD, SEV, or EXTRM. Separate a range or variation of intensity with a hyphen; e.g., MOD-SEV. If turbulence was forecasted, but not encountered, enter NEG. 2. Type. Enter CAT or CHOP if reported by the pilot. 3. Altitude. Report altitude only if it differs from value reported in /FL. When a layer of turbulence is reported, separate height values with a hyphen. If lower or upper limits are not defined, use BLO or ABV. EXAMPLE/TB LGT 040 /TB MOD-SEV BLO 080 /TB MOD-SEV CAT 350 /TB NEG 120-180 /TB MOD CHOP 220/NEG 230-280 /TB MOD CAT ABV 290

帅哥

k. IC. Icing. Report intensity, type and altitude of icing as follows: 1. Intensity. Enter intensity first using contrac- tions TRACE, LGT, MOD, or SEV. Separate reports of a range or variation of intensity with a hyphen. If icing was forecast but not encountered, enter NEG. 2. Type. Enter the reported icing type as RIME, CLR, or MX. 3. Altitude. Enter the reported icing/altitude only if different from the value reported in the /FL TEI. Use a hyphen to separate reported layers of icing. Use ABV or BLO when a layer is not defined. EXAMPLE/IC LGT-MOD MX 085 /IC LGT RIME /IC MOD RIME BLO 095 /IC SEV CLR 035-062

帅哥

4. When icing is reported always report temperature in the /TA TEI. l. /RM. Rem arks. Use this TEI to report a phenomenon which is considered important but does not fit in any of the other TEIs. This includes, but is not limited to, low level wind shear (LLWS) reports, thunderstorm lines, coverage and movement, size of hail (1/4'' increments), lightning, clouds observed but not encountered, geographical or local descrip- tion of where the phenom enon occurred, and contrails. Report hazardous weather first. Describe LLWS to the extent possible. 1. Wind Shear. +/- 10 Kts or more fluctuations in wind speed, within 2,000 Ft of the surface, require an Urgent (UUA) pilot report. When Low Level Wind Shear is entered in a pilot report enter LLWS as the first remark in the /RM TEI. LLWS may be reported as -, +, or +/- depending on how it effects the aircraft. If the location is different than the /OV or /FL fields, include the location in the remarks. EXAMPLE/RM LLWS +/-15 KT SFC-008 DURC RY22 JFK

帅哥

2. FUNNEL_CLOUD,_TORNADO,_and WATERSPOUT are entered with the direction of movement if reported. EXAMPLE/RM TORNADO E MOV E 3. Thunderstorm. Enter coverage (ISOL, FEW, SCT, NMRS) and description (LN,BKN LN,SLD LN) if reported. Follow with “TS,” the location and movement, and the type of lightning if reported. EXAMPLE/RM NMRS TS S MOV E GR1/2 4. Lightning. Enter frequency (OCNL, FRQ, CONS), followed by type (LTGIC , LTGCC, LTGCG, LTGCA, or combinations), if reported. EXAMPLE/RM OCNL LTGICCG 5. Electric_DischargeEnter_DISCHARGE fol- lowed by the altitude. EXAMPLE/RM DISCHARGE 120 6. Clouds. Use remarks when clouds can be seen but were not encountered and reported in /SK. EXAMPLE/RM CB E MOV N /RM OVC BLO

帅哥

7. Plain Language. If specific phraseology is not adequate, use plain language to describe the phenomena or local geographic locations. Include remarks that do not fit in other TEIs like DURC, DURD, RCA, TOP, TOC, or CONTRAILS. EXAMPLE/RM BUMPY VERY ROUGH RIDE /RM CONTRAILS /UA/OV BIS270030/TM 1445/FL060/TP CVLT/TB LGT /RM Donner Summit Pass JO 7110.10T 2/14/08 9-2-7 Pilot Weather Report (UA/UUA) 8. Volcanic Eruption. Volcanic Ash alone is an Urgent PIREP. A report of volcanic activity shall include as much information as possible. Include name of the mountain, ash cloud and movement, height of the top and bottom of the ash, etc. If received from other than a pilot, enter Aircraft “UNKN,” Flight Level “UNKN,” and /RM UNOFFICIAL. EXAMPLE- UUA/OV ANC240075/TM 2110/FL370/TP DC10/WX VA/RM VOLCANIC ERUPTION 2008Z MT AUGUSTINE ASH 40S MOV SSE

帅哥

9. The “SKYSPOTTER” program is a result of a recommendation from the Safer Skies FAA/ INDUSTRY Joint Safety Analysis and Implementa- tion Teams. The term “SKYSPOTTER” indicates that a pilot has received specialized training in observing and reporting inflight weather phenome- non, pilot weather reports, or PIREPs. (a) When the FSS Air Traffic Control Specialist receives a PIREP from a pilot identifying themselves as a “SKYSPOTTER” aircraft, the additional comment “/AWC” shall be added at the end of the remarks section of the PIREP. EXAMPLE- PIREP TEXT/RM REMARKS/AWC 9-2-16. PIREP ENCODING PIREPs shall be coded to ensure the PIREP is stored and subsequently distributed with the surface observation location nearest the condition being reported. If more than one SA location is appropriate, select the location that provides the greatest distribution and/or prominence, such as a major hub airport.

帅哥

9-2-17. PIREP ORDER Prepare PIREPs by routes from the reported location to an adjacent location, if possible. Start a multiple PIREP transmission with the most northerly route and progress clockwise. Place each PIREP on a separate line. EXAMPLE- UA/OV MRB045030/TM 1645/FL060 /TP UNKN /SK OVC055 UA/OV MRB-DCA/TM 1630/FL090/TP AEST /RM BTWN LYRS 090 UA/OV MRB-EKN/TM 1640/FL060/TP P28R /SK BKN-OVC020-TOP040/RM RDGS OBSCD JO 7110.10T 2/14/08 9-3-1 Radar Weather Report (SD/ROB)