Chapter 4. Altitude Reservation (ALTRV) Procedures

Section 5. Originator Responsibilities

4-5-1. TWO OR MORE COMMANDS

When two or more commands within the same service are involved in an exercise, the responsibility for planning ­and processing an ALTRV APREQ must be accepted by each command unless notice is given to CARF that one ­command has accepted the responsibility for the other commands.

4-5-2. TWO OR MORE SERVICES

When two or more services (USAF, USA, USN, USMC) are involved in an exercise, the responsibility for ­planning and processing an ALTRV APREQ must be accepted by each service unless notice is given to CARF ­that one service has accepted the responsibility for the other service(s).

4-5-3. MISSIONS REQUIRING EXTENSIVE ATC SUPPORT

Missions which originate on a Joint Chiefs of Staff or Service Headquarters level (USA, USN, USMC, USAF) ­and require extensive ATC support, must be initially coordinated with FAA Headquarters, ATO System ­Operations Security, 800 Independence Avenue, S.W., Washington, DC 20591.

4-5-4. PROJECT OFFICER

The originator of the ALTRV request must assign a project officer and an alternate project officer for each ­proposed ALTRV APREQ. These project officers must be thoroughly familiar with the requirements set forth ­in this chapter and available for coordination until the ALTRV completion or cancellation. Telephone numbers ­must be specified in Item G of the ALTRV APREQ in accordance with subparagraph 4–10–2h (2) and (3) of this ­chapter.

  1. The project officer must coordinate the ALTRV APREQ with the following:
    1. The ARTCC/CCF/HCF in whose area the flight originates to obtain acceptable departure procedures up ­to the first cruising altitude. Additional data must be provided in accordance with section 10 of this chapter.
    2. The using agency for approval to transit special use airspace; e.g., prohibited, restricted, warning, or ­military operations areas, etc.
    3. The designated scheduling unit for approval to use or transit published refueling tracks/anchors and ­military training routes.
    4. The appropriate FAA Liaison Officer, Service Area ATREP and/or military representative.
    5. 5.Air Traffic Control Spectrum Engineering Services for EA and chaff authorization, if applicable. (See ­subparagraph 4-1-3e of this chapter.)
  2. It must be the responsibility of the project officer to ensure receipt of the approvals specified in ­subparagraph a above.
  3. The project officer must ensure that the ALTRV APVL and any subsequent amendments are coordinated ­with the aircrews.
  4. The project officer must ensure the results of coordination efforts listed in subparagraphs 4-5-4a2, 3, and ­5 above, are included in the remarks section, item G. of the APREQ under Additional Information. Refer to ­section 10 of this chapter for more details.
    1. ARTCC/CCF/HCFs in which ALTRV is flight planned.
    2. EA and chaff information, including EA and/or chaff authorization number, if applicable. (See ­subparagraph 4-1-3f.)
    3. All individual flight plan from this point (IFPFP) routing and altitude information to the BEGIN ALTRV ­point and from the ALTRV termination point. Location, routing (IFPFP), and procedures for airborne spares to ­drop out/exit the ALTRV.
    4. All special use airspace and ATC-assigned airspace (ATCAA) for which approval has been obtained.
  5. It must be the responsibility of the originator and the project officer to ensure that ALTRV APREQs are ­submitted so as to reach CARF not later than the time criteria specified in paragraph 4-4-2, Order of ­Precedence. Proposed departure times of No-Notice missions must be included. If the ALTRV APREQ is to be ­submitted in accordance with Section 10 and Section 11 of this chapter, all mission aircraft, and other aircraft ­as deemed necessary by coordination between CARF and the project officer, must be included in the ALTRV ­APREQs.
  6. The final approval authority will be determined in accordance with paragraphs 4-2-4, ALTRV Approval ­(APVL), and 4-3-2, ARTCC/CCF/HCF Approval ALTRVs. CARF/EUCARF/PACMARF and all U.S. ­ARTCC/CCF/HCF must be addressed when missions will enter their areas of responsibility. Missions which ­do not depart from within the U.S. CTA/FIR should be addressed to the appropriate altitude reservation facility ­with whom CARF has a LOA.
  7. The project officer must be responsible for informing the final approval authority of any mission delay ­request.
  8. The project officer must ensure that aircraft commanders are briefed on the importance of maintaining ­planned ALTRV en route timing.
  9. The project officer must ensure that all air traffic facilities are provided aircraft call signs in the original ­submission of the ALTRV APREQ in accordance with existing directives.

4-5-5. ALTRVs ENTERING U.S. CTA/FIR

Military command headquarters located outside U.S. CTA/FIR proposing to conduct an exercise that will ­encompass activities within the U.S. CTA/FIR must coordinate with CARF.

4-5-6. NO*NOTICE AND/OR DO NOT PASS TO AIR DEFENSE RADAR (NOPAR) MISSION

Every precaution must be taken to safeguard the execution time and date of a No-Notice mission.

  1. Information concerning NOPAR missions must be withheld from specified air defense radar facilities ­and/or specified interceptor squadrons.
  2. The following procedures apply:
    1. If required, the project officer or the FAA Liaison Officer must furnish the concerned FAA facilities, in ­separate correspondence, a list of “trusted agents” or “eyes only officers” with whom the time and dates of the ­No-Notice mission may be discussed.
    2. The project officer must specify “NOPAR” in the remarks sections of an ALTRV APREQ when mission ­information is to be withheld from all air defense radar facilities and fighter interceptor squadrons. When mission ­information is to be withheld only from specific Air Defense Radar Facilities and/or fighter interceptor ­squadrons, the facilities and/or squadrons must be added to the ALTRV APREQ immediately after “NOPAR.”