Order JO 7610.14A Non-Sensitive Procedures and Requirements for Special Operations
This order establishes non-sensitive procedures and requirements for air traffic control (ATC) planning and coordination; and operational execution of ATC-related services supporting special operations while mitigating collateral safety and efficiency effects on the National Airspace System (NAS). The procedures and requirements contained herein are applicable to the Department of Defense (DoD), including National Guard (NG); Department of Homeland Security (DHS); and other government agencies that conduct special operations for national defense, homeland security, intelligence, and emergency operations purposes.
Text read by OCR from a scanned file (32 of 244 pages). Check the original, as some words may be misread.
7610.14A Non-Sensitive Procedures and Requirements for Special…
Air Traffic Organization Policy
ORDER JO 7610.14A
Effective Date: August 7, 2025
SUBJ: Non-Sensitive Procedures and Requirements for Special Operations
This order establishes non-sensitive procedures and requirements for air traffic control (ATC) planning and coordination; and operational execution of ATC-related services supporting special operations while mitigating collateral safety and efficiency effects on the National Airspace System (NAS). The procedures and requirements contained herein are applicable to the Department of Defense (DoD), including National Guard (NG); Department of Homeland Security (DHS); and other government agencies that conduct special operations for national defense, homeland security, intelligence, and emergency operations purposes.
This order, which complements FAA Order JO 7610.4, Sensitive Procedures and Requirements for Special Operations, is focused on non-sensitive procedures and requirements that do not require a protection designation. FAA Order JO 7610.14 was created to provide easier access to uncontrolled and unclassified information relocated from JO 7610.4, which retains its protection designation. For Air Traffic Organization (ATO) purposes, this relocated, uncontrolled, and unclassified information is referred to as non-sensitive information. Relocated information identified as non-sensitive includes content in chapters such as procedures for altitude reservation (ALTRV) procedures, aerial refueling, military training routes (MTRs), and military radar units (MRUs). In consultation with the DoD, this non-sensitive information is relocated from JO 7610.4 to this publicly available order.
LaKisha A. Price Acting Vice President, System Operations Services Air Traffic Organization
Distribution: Electronic Initiated By: AJR-0
2/20/25 JO 7610.14
CHANGE
TO BASIC
SUPPLEMENTS
OPTIONAL
CHANGE
TO BASIC
SUPPLEMENTS
OPTIONAL
FAA Form 1320−5 (6−80) USE PREVIOUS EDITION
Appendix −1
Explanation of Changes
Direct questions through appropriate facility/service center office staff
to the Office of Primary Interest (OPI)
a. 6−1−6. FAA FORM 7110−4, MILITARY TRAINING ROUTE DATA
6−4−3. ALTITIDES 6−5−1. ESTABLISHING OR REVISING ROUTES 6−5−3. EFFECTIVE DATES 6−8−1. ESTABLISHING OR REVISING ROUTES
7610.14A Non-Sensitive Procedures and Requirements for Special… › Explanation of Changes
This change adds new paragraph 6–1–6, FAA Form 7110−4 Military Training Route Data, to provide guidance on FAA Form 7110−4. This change retitles FIG 6−5−2 to “FAA Form 7110−4 Military Training Route Data, and Instructions” and replaces the old instructions/sample FAA Form 7110−4 with a new revised sample FAA Form 7110−4 and instructions. Changes to paragraphs 6–4–3, 6–6–1, and 6–8–1 revise the references to FIG 6−5−2 for locating sample FAA Form 7110−4, and also adds a new reference to new paragraph 6–1–6. This change retitles paragraphs 6–5–1 and 6–8–1 for clarity. This change cancels and incorporates N JO 7610.118, which was effective April 11, 2025.
b. 7−5−1. HIJACK ESCORTS
This change deletes Section 5, Forwarding Information, and paragraph 7–5–1, Hijack Escorts, from Chapter 7, Miscellaneous Flight Activities and Requirements.
c. Editorial Changes
Editorial changes include correcting font size in chapter and section titles; a universal change replacing all prior references to the term Gulf of Mexico with the term Gulf of America in accordance with Executive Order 14172; and a universal change updating the term Notice to Air Missions (NOTAM) to Notice to Airmen (NOTAM).
d. Entire Publication
Additional editorial/format changes were made where necessary. Revision bars were not used because of the insignificant nature of these changes.
Table of Contents i
Change - 1 dated January 22, 2026
CHANGE
U.S. DEPARTMENT OF TRANSPORTATION
FEDERAL AVIATION ADMINISTRATION
JO 7610.14A
CHG 1
Air Traffic Organization Policy Effective Date: January 22, 2026
SUBJ: Non-Sensitive Procedures and Requirements for Special Operations
1. Purpose of This Change. This change transmits revised pages to Federal Aviation Administration Order JO 7610.14, Non-Sensitive Procedures and Requirements for Special Operations, and the Briefing Guide.
2. Audience. This change applies to all ATO personnel and anyone using ATO directives.
3. Where Can I Find This Change? Information for access to this order is available on the MyFAA employee website at https://employees.faa.gov/tools_resources/orders_notices/ and on the air traffic publications website at http://www.faa.gov/air_traffic/publications.
4. Explanation of Policy Change. See the Explanation of Changes attachment which has editorial corrections and changes submitted through normal procedures. The Briefing Guide lists only new or modified material, along with background statements.
5. Distribution. This change is distributed electronically to all who subscribed to receive email notifications through the FAA’s website. All organizations are responsible for viewing, downloading, and subscribing to receive email notifications when changes occur to this order. Subscriptions to air traffic directives can be made through the Air Traffic Plans and Publications website at https://www.faa.gov/air_traffic/publications/ or directly via the following link: https://public.govdelivery.com/accounts/USAFAA/subscriber/new?topic_id=USAFAA_39.
6. Disposition of Transmittal. Retain this transmittal until superseded by a new basic order.
7. Page Control Chart. See the page control chart attachment.
Digitally signed by LAKISHA A LAKISHA A PRICE Date: 2025.11.13 PRICE 18:33:23 -05'00'
LaKisha A. Price Acting Vice President, System Operations Services Air Traffic Organization
Distribution: Electronic Initiated By: AJR-0 Vice President, System Operations Services FOR OFFICIAL USE ONLY Public availability to be determined under 5 USC 552
Change - 1 dated January 22, 2026 › Explanation of Changes
Explanation of Changes
Direct questions through appropriate facility/service center office staff
to the Office of Primary Interest (OPI)
a. Editorial Changes
Editorial change includes a universal editorial change to terms from the National Aeronautical Charting office to FAA’s Aeronautical Information Services (AIS) to paragraph 7−1−4, Publication of Installation. Also, the removal of the National Flight Data Center (NFDC) for its replacement AIS, and the term AeroNav Products is removed for the term AIS.
b. Entire Publication
Additional editorial/format changes were made where necessary. Revision bars were not used because of the insignificant nature of these changes.
Table of Contents i
Change 2 - dtd July, 9, 2026
CHANGE
U.S. DEPARTMENT OF TRANSPORTATION
FEDERAL AVIATION ADMINISTRATION
JO 7610.14A
CHG 2
Air Traffic Organization Policy Effective Date:
July 9, 2026
SUBJ: Non-Sensitive Procedures and Requirements for Special Operations
1. Purpose of This Change. This change transmits revised pages to Federal Aviation Administration Order JO 7610.14A, Non-Sensitive Procedures and Requirements for Special Operations, and the Briefing Guide.
2. Audience. This change applies to all ATO personnel and anyone using ATO directives.
3. Where Can I Find This Change? Information for access to this order is available on the MyFAA employee website at https://employees.faa.gov/tools_resources/orders_notices/ and on the air traffic publications website at http://www.faa.gov/air_traffic/publications.
4. Explanation of Policy Change. See the Explanation of Changes attachment which has editorial corrections and changes submitted through normal procedures. The Briefing Guide lists only new or modified material, along with background statements.
5. Distribution. This change is distributed electronically to all who subscribed to receive email notifications through the FAA’s website. All organizations are responsible for viewing, downloading, and subscribing to receive email notifications when changes occur to this order. Subscriptions to air traffic directives can be made through the Air Traffic Plans and Publications website at https://www.faa.gov/air_traffic/publications/ or directly via the following link: https://public.govdelivery.com/accounts/USAFAA/subscriber/new?topic_id=USAFAA_39.
6. Disposition of Transmittal. Retain this transmittal until superseded by a new basic order.
7. Page Control Chart. See the page control chart attachment.
LAKISHA A
Digitally signed by LAKISHA A PRICE Date: 2026.05.15 PRICE 11:02:15 -04'00'
LaKisha A. Price Vice President, System Operations Services Air Traffic Organization
Distribution: Electronic Initiated By: AJR-0 Vice President, System Operations Services FOR OFFICIAL USE ONLY Public availability to be determined under 5 USC 552
Change 2 - dtd July, 9, 2026 › Explanation of Changes
7/9/26 JO 7610.14A CHG 2
Explanation of Changes
Direct questions through appropriate facility/service center office staff
to the Office of Primary Interest (OPI)
a. Editorial Changes
An editorial change replaces the term Center Radar Approach Control (CERAP) with Combined Control Facility (CCF) in multiple paragraphs.
b. Entire Publication
Additional editorial/format changes were made where necessary. Revision bars were not used because of the insignificant nature of these changes.
Table of Contents i
Table of Contents
7/9/26 JO 7610.14A CHG 2
Table of Contents
Chapter 1. General
Section 1. Introduction
Paragraph Page 1−1−1. PURPOSE OF THIS ORDER … 1−1−1 1−1−2. AUDIENCE … 1−1−1 1−1−3. WHERE TO FIND THIS ORDER … 1−1−1 1−1−4. WHAT THIS ORDER CANCELS … 1−1−1 1−1−5. EXPLANATION OF CHANGES … 1−1−1 1−1−6. EFFECTIVE DATES AND SUBMISSION FOR CHANGES … 1−1−1 1−1−7. RECOMMENDATIONS FOR PROCEDURAL CHANGES … 1−1−2 1−1−8. DISTRIBUTION … 1−1−2
Section 2. Application
1−2−1. FAA RESPONSIBILITIES … 1−2−1 1−2−2. MEMORANDA OF AGREEMENT, MEMORANDA OF UNDERSTANDING, EXECUTIVE ORDERS, AND OTHER NATIONAL−LEVEL REFERENCE DOCUMENTS … 1−2−1 1−2−3. WORD MEANINGS … 1−2−1 1−2−4. NOTES … 1−2−1 1−2−5. MILITARY PROCEDURES IDENTIFICATION … 1−2−1 1−2−6. REQUIREMENTS REVIEW WITH INTERAGENCY PARTNERS … 1−2−1
Chapter 2. Services and Responsibilities
Section 1. ATC Services by the Military
2−1−1. WHERE SERVICE MAY BE PROVIDED … 2−1−1 2−1−2. AIR TRAFFIC CONTROL AUTHORITY … 2−1−1 2−1−3. FREQUENCY REQUIREMENTS … 2−1−1 2−1−4. LETTERS OF AGREEMENT (LOAs)/LETTERS OF PROCEDURE (LOPs) … 2−1−1 2−1−5. TOWER EN ROUTE CONTROL SERVICE … 2−1−1 2−1−6. EVALUATIONS BY FAA … 2−1−1 2−1−7. SUSPENDING APPROACH CONTROL OR OTHER AIR TRAFFIC CONTROL AUTHORITY … 2−1−2 2−1−8. USE OF MILITARY AUTHORITY ASSUMES RESPONSIBILITY FOR SEPARATION OF AIRCRAFT (MARSA) … 2−1−2 2−1−9. RELEASE OF AIRCRAFT TO GROUND CONTROL APPROACH (GCA) UNITS 2−1−2 2−1−10. CONTROL OF FLIGHTS IN PATTERN … 2−1−3 2−1−11. EXCHANGE OF INFORMATION … 2−1−3
Section 2. Air Traffic Representative (ATREP)
2−2−1. ASSIGNMENTS … 2−2−1 2−2−2. ATREP FUNCTIONS … 2−2−1 2−2−3. FAMILIARIZATION FLIGHTS … 2−2−1 2−2−4. REQUIRED ABSENCE … 2−2−1 2−2−5. ALTERNATE AIR TRAFFIC REPRESENTATIVE … 2−2−1
Table of Contents i
JO 7610.14A CHG 2 7/9/26
Paragraph Page 2−2−6. FUNCTIONS OF ALTERNATE ATREP … 2−2−1 2−2−7. COORDINATION … 2−2−1 2−2−8. AVAILABILITY … 2−2−1
Section 3. Miscellaneous
2−3−1. ASSIGNMENT OF MILITARY TOWER LIAISONS … 2−3−1 2−3−2. SUPERVISOR OF FLYING (SOF) … 2−3−1 2−3−3. MILITARY AIRSPACE MANAGERS … 2−3−1 2−3−4. MILITARY REPRESENTATIVES (MILREPs) … 2−3−1 2−3−5. DOD REIMBURSABLE SUPPORT TO FAA … 2−3−1
Chapter 3. Military Exercise Planning
Section 1. General
3−1−1. PURPOSE … 3−1−1 3−1−2. POLICY … 3−1−1 3−1−3. PROCEDURES … 3−1−1 3−1−4. SPECIAL USE AIRSPACE (SUA) … 3−1−1 3−1−5. MILITARY AIRSPACE PLANNING … 3−1−1 3−1−6. FAA MILITARY LIAISON OFFICERS’ RESPONSIBILITIES … 3−1−3 3−1−7. CHANGES IN REQUIREMENTS … 3−1−3 3−1−8. PUBLIC NOTIFICATION … 3−1−3 3−1−9. PLANNING CONFERENCES … 3−1−3
Section 2. Criteria
3−2−1. PURPOSE … 3−2−1 3−2−2. POLICY … 3−2−1 3−2−3. AIRSPACE DESCRIPTION … 3−2−1 3−2−4. LIMITATIONS … 3−2−1 3−2−5. LETTERS OF AGREEMENT/PROCEDURE … 3−2−1
Section 3. ATCAA and MOA Procedures
3−3−1. REQUIREMENT … 3−3−1 3−3−2. USING AGENCY RESPONSIBILITIES … 3−3−1 3−3−3. CONTROLLING AGENCY RESPONSIBILITY … 3−3−1 3−3−4. ATC CONTROL WITHIN ATCAAs AND MOAs … 3−3−1 3−3−5. NONRADAR AND COMMUNICATIONS … 3−3−2
Section 4. ATCAA and MOA Procedures
3−4−1. EXERCISE/ORI … 3−4−1 3−4−2. NOTIFICATION OF EXERCISE/ORI … 3−4−1
Section 5. Air Mobility Command (AMC) Exercise/Operational
Readiness Inspection (ORI)
3−5−1. ORI … 3−5−1 3−5−2. NOTIFICATION OF ORI … 3−5−1
Table of Contents ii
7/9/26 JO 7610.14A CHG 2
Section 6. United States Strategic Command (USSTRATCOM)
Operational Readiness Inspection (ORI)
Paragraph Page 3−6−1. ORI BOOKLETS … 3−6−1 3−6−2. NOTIFICATION OF ORI … 3−6−1 3−6−3. NOTIFICATION FORMAT … 3−6−1 3−6−4. MISSION DELAYS … 3−6−1
Section 7. Navy Shipboard Exercises
3−7−1. FLEET AREA CONTROL AND SURVEILLANCE FACILITIES (FACSFACs) . . . 3−7−1 3−7−2. FACSFAC LOCATIONS … 3−7−1 3−7−3. FLEET READINESS EXERCISES … 3−7−1 3−7−4. PLANNING CONFERENCES … 3−7−1 3−7−5. AIRCRAFT CARRIER OPERATIONS … 3−7−2 3−7−6. FLYOFF PROCEDURES … 3−7−2 3−7−7. AIR CAPABLE SHIP OPERATIONS … 3−7−2 3−7−8. CENTRAL ALTITUDE RESERVATION FUNCTION (CARF) APPROVED ALTRVS 3−7−2 3−7−9. FAMILIARIZATION VISITS … 3−7−2
Chapter 4. Altitude Reservation (ALTRV) Procedures
Section 1. General
4−1−1. PURPOSE … 4−1−1 4−1−2. POLICY … 4−1−1 4−1−3. APPLICATION … 4−1−1 4−1−4. ALTERNATE TRACKS … 4−1−2 4−1−5. USER REQUIREMENTS … 4−1−2 4−1−6. ALTITUDE CRITERIA … 4−1−3
Section 2. Central Altitude Reservation Function (CARF)
4−2−1. INTERNATIONAL COORDINATION … 4−2−1 4−2−2. APPROVAL AUTHORITY … 4−2−1 4−2−3. ALTRV APPROVAL REQUEST (APREQ) … 4−2−1 4−2−4. ALTRV APPROVAL (APVL) … 4−2−2 4−2−5. NOTIFICATIONS … 4−2−2 4−2−6. AIRSPACE NOT UNDER CARF JURISDICTION … 4−2−2 4−2−7. RESOLUTION OF CONFLICTS BETWEEN MISSIONS … 4−2−2 4−2−8. ISSUE ALTITUDE RESERVATION NOTICE TO AIRMEN (NOTAM) … 4−2−2 4−2−9. ACKNOWLEDGMENT OF ALTRV APREQs … 4−2−3 4−2−10. MESSAGES CLASSIFIED AS ENCRYPT FOR TRANSMISSION ONLY (EFTO) 4−2−3 4−2−11. LETTERS OF AGREEMENT … 4−2−3
Section 3. ATC Facility Responsibilities
4−3−1. APREQ REVIEW AND COORDINATION … 4−3−1 4−3−2. ARTCC/CCF/HCF APPROVED ALTRVs … 4−3−1 4−3−3. MISSION SEPARATION … 4−3−1 4−3−4. FLIGHT PROGRESS STRIPS … 4−3−1 4−3−5. NOTIFICATION … 4−3−1
Table of Contents iii
JO 7610.14A CHG 2 7/9/26
Paragraph Page 4−3−6. ISSUE ALTITUDE RESERVATION NOTAM … 4−3−2 4−3−7. TRUSTED AGENTS … 4−3−2 4−3−8. ALTRV AUTHORIZATION AND CHANGES … 4−3−2
Section 4. Mission Planning
4−4−1. RESOLVING MISSION CONFLICTS … 4−4−1 4−4−2. ORDER OF PRECEDENCE … 4−4−1 4−4−3. SPECIFY VOID TIME … 4−4−2 4−4−4. RESCHEDULING … 4−4−2 4−4−5. DELAY NOTIFICATIONS … 4−4−2 4−4−6. EN ROUTE TIMING … 4−4−2
Section 5. Originator Responsibilities
4−5−1. TWO OR MORE COMMANDS … 4−5−1 4−5−2. TWO OR MORE SERVICES … 4−5−1 4−5−3. MISSIONS REQUIRING EXTENSIVE ATC SUPPORT … 4−5−1 4−5−4. PROJECT OFFICER … 4−5−1 4−5−5. ALTRVs ENTERING U.S. CTA/FIR … 4−5−2 4−5−6. NONOTICE AND/OR DO NOT PASS TO AIR DEFENSE RADAR (NOPAR) MISSION … 4−5−2
Section 6. Planning Approval of APREQs
4−6−1. PLANNING/APPROVAL OF APREQs … 4−6−1 4−6−2. MILITARY AUTHORITY ASSUMES RESPONSIBILITY FOR SEPARATION OF AIRCRAFT (MARSA) … 4−6−1 4−6−3. INFLIGHT SEPARATION … 4−6−1 4−6−4. POSITION REPORTS … 4−6−2 4−6−5. USE OF AIRSPACE THROUGH ALTRV … 4−6−2
Section 7. Special/Emergency ALTRVs
4−7−1. INTERNATIONAL PRESIDENTIAL FLIGHTS … 4−7−1 4−7−2. PROCESSING WAIVERS … 4−7−1 4−7−3. EMERGENCY ALTITUDE RESERVATIONS … 4−7−1
Section 8. Altitude Reservation NOTAMs
4−8−1. CRITERIA … 4−8−1 4−8−2. FORMULATION AND DISSEMINATION … 4−8−1
Section 9. Space Support Operations
4−9−1. PURPOSE … 4−9−1 4−9−2. POLICY … 4−9−1 4−9−3. CLASSIFIED SPACE LAUNCH/REENTRY NOTIFICATION … 4−9−1
Section 10. Altitude Reservation Approval Request (ALTRV APREQ),
Format, and Amendments
4−10−1. ALTRV APREQs … 4−10−1 4−10−2. FORMAT … 4−10−1 4−10−3. ALTRV APREQ AMENDMENTS … 4−10−4
Table of Contents iv
7/9/26 JO 7610.14A CHG 2
Section 11. Flight Path Format Components
Paragraph Page 4−11−1. INTRODUCTION … 4−11−1 4−11−2. DEFINITION … 4−11−1 4−11−3. FORMAT … 4−11−1 4−11−4. MOVING ALTRV COMPONENTS … 4−11−2 4−11−5. STATIONARY ALTRV COMPONENTS … 4−11−8 4−11−6. MOVING ALTRV APREQ EXAMPLES … 4−11−8 4−11−7. STATIONARY ALTRV APREQ EXAMPLES … 4−11−10
Chapter 5. Aerial Refueling
Section 1. General
5−1−1. POLICY … 5−1−1 5−1−2. OBJECTIVE … 5−1−1 5−1−3. RESPONSIBILITY … 5−1−1 5−1−4. SEPARATION … 5−1−1 5−1−5. DEVIATIONS … 5−1−1 5−1−6. CHRONOLOGY … 5−1−1
Section 2. Track Requirements
5−2−1. DESCRIPTION … 5−2−1 5−2−2. NAVIGATION ALONG AIR REFUELING TRACK … 5−2−1 5−2−3. ARIP ESTABLISHMENTS … 5−2−1 5−2−4. DEGREEDISTANCE TRACK DEFINITION … 5−2−1 5−2−5. TANKER ORBIT PATTERNS … 5−2−1
Section 3. Anchor Requirements
5−3−1. DESCRIPTION … 5−3−1 5−3−2. NAVIGATION WITHIN ANCHOR AREA … 5−3−1 5−3−3. ARIP ESTABLISHMENT … 5−3−1 5−3−4. DEGREEDISTANCE ANCHOR DEFINITION … 5−3−1
Section 4. Planning
5−4−1. TRACK/ANCHOR PROPOSALS … 5−4−1 5−4−2. COORDINATION … 5−4−1 5−4−3. CRITERIA FOR ESTABLISHMENT … 5−4−1 5−4−4. APPROVAL NOTIFICATION … 5−4−2 5−4−5. PUBLICATION IN FLIP … 5−4−2 5−4−6. MILITARY SERVICE AREA REPRESENTATIVE RESPONSIBILITIES … 5−4−3 5−4−7. NGA RESPONSIBILITIES … 5−4−3 5−4−8. EFFECTIVE DATE … 5−4−4 5−4−9. REVISIONS TO TRACKS/ANCHORS … 5−4−4
Section 5. Operations
5−5−1. PROVISIONS FOR CONDUCTING AERIAL REFUELING … 5−5−1 5−5−2. USER REQUIREMENTS … 5−5−1 5−5−3. MARSA APPLICABILITY FOR AERIAL REFUELING … 5−5−2
Table of Contents v
JO 7610.14A CHG 2 7/9/26
Paragraph Page 5−5−4. CRITERIA FOR SCHEDULING … 5−5−2 5−5−5. SCHEDULING RESPONSIBILITIES … 5−5−3 5−5−6. FLIGHT PLAN REQUIREMENTS … 5−5−4 5−5−7. TANKER AIRCRAFT/FORMATION COMMANDER RESPONSIBILITIES … 5−5−5 5−5−8. RECEIVER AIRCRAFT RESPONSIBILITIES … 5−5−6 5−5−9. ATC CLEARANCE … 5−5−6 5−5−10. RADAR VECTOR ASSISTANCE … 5−5−6 5−5−11. ATC FACILITY RESPONSIBILITIES … 5−5−6 5−5−12. COMMUNICATIONS FAILURE … 5−5−7
Section 6. Special Refueling Requirements
5−6−1. PROVISIONS FOR SPECIAL TRACKS/ANCHORS … 5−6−1 5−6−2. RESPONSIBILITY OF REQUESTING UNIT … 5−6−1 5−6−3. OPERATIONS WITHIN AN ALTRV … 5−6−1 5−6−4. OPERATIONS OUTSIDE AN ALTRV … 5−6−1 5−6−5. IN-FLIGHT REQUESTS … 5−6−2 5−6−6. SPECIAL EXERCISES … 5−6−2 5−6−7. ISSUE NOTAM … 5−6−2 5−6−8. VFR HELICOPTER/TILTROTOR REFUELING OPERATIONS … 5−6−2 5−6−9. VFR REFUELING TRACK ESTABLISHMENT … 5−6−2 5−6−10. REFUELING TRACK DEFINITION … 5−6−3 5−6−11. OPERATING PROCEDURES … 5−6−3 5−6−12. FLIGHT PLAN REQUIREMENTS … 5−6−3 5−6−13. WEATHER MINIMUMS … 5−6−4 5−6−14. ADHERENCE TO REFUELING TRACK … 5−6−4 5−6−15. FAA COORDINATION … 5−6−4 5−6−16. PUBLICATION/SCHEDULING … 5−6−4
Chapter 6. Military Training Routes (MTR)
Section 1. General
6−1−1. PURPOSE … 6−1−1 6−1−2. POLICY … 6−1−1 6−1−3. DEVIATIONS … 6−1−1 6−1−4. PUBLICATION … 6−1−1 6−1−5. RECORD OF MILITARY TRAINING ROUTE (MTR) OPERATIONS … 6−1−1 6−1−6. FAA FORM 7110−4, MILITARY TRAINING ROUTE DATA … 6−1−1
Section 2. MTR Route Designation Criteria
6−2−1. LIMITATIONS … 6−2−1 6−2−2. ROUTE IDENTIFICATION … 6−2−1
Section 3. Publicity
6−3−1. INFORMATION TO THE PUBLIC … 6−3−1
Table of Contents vi
7/9/26 JO 7610.14A CHG 2
Section 4. IR Route Definition
Paragraph Page 6−4−1. ROUTE WIDTH … 6−4−1 6−4−2. ROUTE ALIGNMENT … 6−4−1 6−4−3. ALTITUDES … 6−4−1 6−4−4. RE−ENTRY SEGMENTS … 6−4−2 6−4−5. ALTERNATE ENTRY, EXIT, AND END POINTS … 6−4−2 6−4−6. ROUTE REPORTING POINTS … 6−4−2 6−4−7. SPECIAL OPERATING PROCEDURES … 6−4−2 6−4−8. LOW ALTITUDE AIR−TO−AIR TRAINING (LOWAT) … 6−4−2
Section 5. IR Coordination
6−5−1. ESTABLISHING OR REVISING IR ROUTES … 6−5−1 6−5−2. PUBLICATION … 6−5−3 6−5−3. EFFECTIVE DATE … 6−5−3
Section 6. IR Route Use
6−6−1. SCHEDULING … 6−6−1 6−6−2. LETTERS OF AGREEMENT IR … 6−6−1 6−6−3. ADVISORY AND OPERATIONAL STATUS MESSAGES … 6−6−1 6−6−4. FLIGHT PLAN REQUIREMENTS … 6−6−1 6−6−5. IR USE DENIAL … 6−6−3 6−6−6. ROUTE ADHERENCE … 6−6−3 6−6−7. SPEED AUTHORIZATION … 6−6−4 6−6−8. ENTRY/EXIT PROCEDURES … 6−6−4 6−6−9. COMMUNICATION FAILURE … 6−6−4 6−6−10. LOST COMMUNICATIONS TRANSPONDER OPERATIONS … 6−6−4 6−6−11. SEPARATION OF PARTICIPATING AIRCRAFT … 6−6−4
Section 7. VR Route Definition
6−7−1. ROUTE WIDTH … 6−7−6 6−7−2. ROUTE ALIGNMENT … 6−7−6 6−7−3. ALTITUDES … 6−7−6 6−7−4. ROUTE ENTRY AND EXIT POINTS … 6−7−6 6−7−5. ALTERNATE ENTRY/EXIT/END POINTS … 6−7−6 6−7−6. SPECIAL OPERATING PROCEDURES … 6−7−7
Section 8. VR Coordination
6−8−1. ESTABLISHING OR REVISING VR ROUTES … 6−8−8 6−8−2. PUBLICATION … 6−8−9 6−8−3. EFFECTIVE DATE … 6−8−9
Section 9. VR Route Use
6−9−1. SCHEDULING … 6−9−1 6−9−2. COMPLIANCE … 6−9−1 6−9−3. FLIGHT PLAN REQUIREMENTS … 6−9−1 6−9−4. ROUTE ADHERENCE … 6−9−1 6−9−5. SPEED AUTHORIZATION … 6−9−1
Table of Contents vii
JO 7610.14A CHG 2 7/9/26
Paragraph Page 6−9−6. WEATHER MINIMUMS … 6−9−2 6−9−7. TRANSPONDER PROCEDURES … 6−9−2
Chapter 7. Miscellaneous Flight Activities and Requirements
Section 1. Aircraft Arresting System, Single Frequency Approach (SFA),
Simulated Flameout (SFO)/Emergency Landing Pattern (ELP)
Operations, Celestial Navigation (CELNAV) Training
7−1−1. OPERATION OF AIRCRAFT ARRESTING SYSTEMS … 7−1−1 7−1−2. ARRESTING SYSTEMS CONTROL PANELS … 7−1−1 7−1−3. ACTION REQUIRED BY FACILITY AIR TRAFFIC MANAGER … 7−1−1 7−1−4. PUBLICATION OF INSTALLATION … 7−1−2 7−1−5. SINGLE FREQUENCY APPROACH (SFA) … 7−1−2 7−1−6. SIMULATED FLAMEOUT (SFO)/EMERGENCY LANDING PATTERN (ELP) OPERATIONS … 7−1−2 7−1−7. CELESTIAL NAVIGATION (CELNAV) TRAINING … 7−1−3
Section 2. USAF Undergraduate Flying Training (UFT)/Pilot Instructor
Training (PIT)/Introduction to Fighter Fundamentals
7−2−1. DEFINITIONS … 7−2−1 7−2−2. KEY OPERATIONAL CONSTRAINTS … 7−2−1 7−2−3. RADAR SERVICE REQUIREMENTS … 7−2−1 7−2−4. MERGING TARGET VS APPROVED SEPARATION … 7−2−1 7−2−5. AIRSPACE REQUIREMENTS … 7−2−2 7−2−6. MTR REQUIREMENTS … 7−2−2 7−2−7. COMMUNICATION REQUIREMENTS … 7−2−2 7−2−8. SCHEDULING … 7−2−3 7−2−9. STEREOTYPE ROUTING/FLIGHT PLANS … 7−2−3 7−2−10. LETTERS OF AGREEMENT (LOAs) … 7−2−3 7−2−11. AUTHORIZATIONS … 7−2−3
Section 3. Military Formation Flight
7−3−1. PURPOSE … 7−3−1 7−3−2. POLICY … 7−3−1 7−3−3. FORMATIONS … 7−3−1 7−3−4. FORMATION DEPARTURE … 7−3−1 7−3−5. CELL FORMATION … 7−3−1 7−3−6. NONSTANDARD FORMATION TACTICS … 7−3−1 7−3−7. CELL SEPARATION STANDARDS … 7−3−2 7−3−8. NONSTANDARD FORMATION NOTIFICATION AND APPROVAL … 7−3−3 7−3−9. AERIAL REFUELING FORMATION … 7−3−3
Section 4. Special Interest Flights
7−4−1. GENERAL … 7−4−1 7−4−2. APPLICATION … 7−4−1
Chapter 8. Military Radar Unit Duties, Responsibilities, and
Procedures
Section 1. General
8−1−1. MILITARY RADAR UNIT (MRU)/AIRBORNE RADAR UNIT (ARU)/AIRBORNE WARNING AND CONTROL SYSTEM (AWACS) … 8−1−1
Table of Contents viii
7/9/26 JO 7610.14A CHG 2
Paragraph Page 8−1−2. MILITARY RADAR UNIT (MRU) … 8−1−1 8−1−3. AIRBORNE RADAR UNIT (ARU) … 8−1−1 8−1−4. AIRBORNE WARNING AND CONTROL SYSTEM (AWACS) … 8−1−1 8−1−5. ADDITIONAL AWACS RESPONSIBILITIES … 8−1−2 8−1−6. TACTICAL MONITOR (TM) … 8−1−2 8−1−7. TRANSFER OF FLIGHT INFORMATION … 8−1−2 8−1−8. FAA RESPONSIBILITY … 8−1−3 8−1−9. ATC FACILITIES RESPONSIBILITY … 8−1−3 8−1−10. RELEASE OF AIRSPACE … 8−1−3 8−1−11. MILITARY RESPONSIBILITY … 8−1−4 8−1−12. RADAR MALFUNCTION AT MRU/ARU … 8−1−5 8−1−13. RADAR MALFUNCTION AT ATC FACILITY … 8−1−5 8−1−14. COMMAND AND CONTROL … 8−1−5 8−1−15. SEPARATION BETWEEN PARTICIPATING AND NONPARTICIPATING AIRCRAFT … 8−1−6
Section 2. Intercept Training Activities
8−2−1. AREA OF OPERATION … 8−2−1 8−2−2. RADAR SURVEILLANCE … 8−2−1
Section 3. FAA/Military Joint Evaluations/Site Visits
8−3−1. PURPOSE … 8−3−1 8−3−2. SCOPE OF EVALUATION/SITE VISIT … 8−3−1 8−3−3. ADVANCE COORDINATION … 8−3−1 8−3−4. OBJECTIVES … 8−3−1 8−3−5. BASIC EVALUATION TEAM/SITE VISIT … 8−3−1 8−3−6. “TRUSTED AGENTS” … 8−3−1 8−3−7. OUTBRIEFING … 8−3−1 8−3−8. PREPARE JOINT REPORT … 8−3−2
Chapter 9. Air Traffic Control Assigned Airspace (ATCAA)
Procedures
Section 1. General
9−1−1. PURPOSE … 9−1−1 9−1−2. TERMS … 9−1−1 9−1−3. POLICY … 9−1−1
Section 2. Procedures
9−2−1. ATCAA PROPOSAL COORDINATION … 9−2−1 9−2−2. ATCAA PROPOSAL CONTENT … 9−2−1 9−2−3. ATCAA PROPOSAL SCHEDULING … 9−2−3
Section 3. Environmental Impact Analysis Procedures for ATCAAs
9−3−1. ENVIRONMENTAL REVIEW PROCESS FOR ATCAA PROPOSALS … 9−3−1
Table of Contents ix
JO 7610.14A CHG 2 7/9/26
Appendices
Paragraph Page Appendix 1. Abbreviations … Appendix 1−1
Appendix 2. Definitions … Appendix 2−1
Appendix 3. Documents Pertinent to System Operations Security … Appendix 3−1
Appendix 4. Documents Pertinent to Mission Support Services … Appendix 4−1
Table of Contents x
Chapter 1. General › Section 1. Introduction
Chapter 1. General
Section 1. Introduction
1−1−1. PURPOSE OF THIS ORDER
This order specifies non−sensitive procedures and requirements for air traffic control planning, coordination, and services supporting national defense, homeland security, and other special operations conducted by the Department of Defense (DoD), Department of Homeland Security (DHS), and other federal, state, local, territorial, or tribal governmental agencies in U.S. controlled airspace. Air Traffic Managers must ensure controllers are familiar with the provisions of this order that pertain to their operational responsibilities. In addition, controllers must exercise sound judgement if they encounter situations that are not covered.
1−1−2. AUDIENCE
This order applies to all ATO personnel and anyone using ATO directives.
1−1−3. WHERE TO FIND THIS ORDER
Information for access to this order is available on the MyFAA employee website at https://employees.faa.gov/tools_resources/orders_notices/ and on the FAA Air Traffic Plans and Publications website at https://www.faa.gov/air_traffic/publications.
1−1−4. WHAT THIS ORDER CANCELS
FAA Order JO 7610.14, Non−Sensitive Procedures and Requirements for Special Operations, dated October 5, 2023, and all changes to it are canceled.
1−1−5. EXPLANATION OF CHANGES
The significant changes to this order are normally identified in the Explanation of Changes page(s). It is advisable to retain the page(s) throughout the duration of the basic order.
1−1−6. EFFECTIVE DATES AND SUBMISSION FOR CHANGES
a. This order and its changes are scheduled to be published to coincide with Aeronautical Information Regulation and Control (AIRAC) dates. (See TBL 1−1−1.)
b. The “Cutoff Date for Completion” in the table below refers to the deadline for a proposed change to be fully coordinated and signed. Change initiators must submit their proposed changes well in advance of this cutoff date to meet the publication effective date. The process to review and coordinate changes often takes several months after the change is initially submitted.
Introduction 1−1−1
JO 7610.14A 8/7/25
TBL 1−1−1 Publication Schedule
Basic or
Change
Cutoff Date For
Completion
Effective Date Of Publication
JO 7610.14A 2/20/25 8/7/25 Change 1 8/7/25 1/22/26 Change 2 1/22/26 7/9/26 Change 3 7/9/26 12/24/26 JO 7610.14B 12/24/26 6/10/27 Change 1 6/10/27 11/25/27 Change 2 11/25/27 5/11/28 Change 3 5/11/28 10/26/28
1−1−7. RECOMMENDATIONS FOR PROCEDURAL CHANGES
a. The office of primary responsibility (OPR) for this order is ATO System Operations Security. However, other FAA organizations may be responsible for the non−sensitive procedures and requirements contained in this order. Inquiries regarding the responsible organization for a particular chapter, section, or paragraph may be addressed/emailed as follows:
FAA Headquarters Air Traffic Organization (ATO) Office of System Operations Security (AJR−2) 800 Independence Avenue, SW FOB 10A, Suite 300W Washington, DC 20597
Email: [email protected]
b. The responsibility associated with processing and coordinating revisions to this order is delegated to the Director, Policy, AJV−P. Recommended changes to this order must be submitted electronically to 9−AJV−P−HQ−[email protected]. The submission should include a description of the recommended change and the proposed language to be used in the order.
NOTE− For additional details on the submission process as well as further description of AJV−P processing responsibilities, see FAA Order JO 7000.5, Procedures for Submitting Changes to Air Traffic Control Publications.
c. ATO personnel should submit recommended changes in procedures to facility management.
d. Recommendations from other sources should be submitted through appropriate FAA, military, or industry/user channels.
e. Procedural changes will not be made to this order until coordination that supports implementation of the new or revised procedures has been completed through AJV−P.
1−1−8. DISTRIBUTION
This order is available online and will be distributed electronically to all offices that subscribe to receive email notification/access to it through the FAA website (https://www.faa.gov/air_traffic/publications/).
Introduction 1−1−2
Section 2. Application
1−2−1. FAA RESPONSIBILITIES
Chapter 1. General › Section 2. Application
FAA ATO must provide services for the special operations conducted by DoD, DHS, and other U.S. federal, state, local, territorial, or tribal government agencies in accordance with the policy, criteria, and procedures in this order.
1−2−2. MEMORANDA OF AGREEMENT, MEMORANDA OF UNDERSTANDING, EXECUTIVE ORDERS, AND OTHER NATIONAL−LEVEL REFERENCE DOCUMENTS
Where deemed appropriate and applicable, national−level reference documents, such as memoranda of agreement, memoranda of understanding, or Executive Orders, may be included in the appendices of this order.
1−2−3. WORD MEANINGS
As used in this order:
a. “Must” means a procedure is mandatory.
b. “Should” means a procedure is recommended.
c. “May” and “need not” mean a procedure is optional.
d. “Will” indicates futurity, not a requirement for application of a procedure.
e. “Must not” means a procedure is prohibited.
f. Words importing the singular include the plural.
g. Words importing the plural include the singular.
h. “Aircraft” means airframe, crew members, or both.
i. “Altitude” means altitude mean sea level, flight level, or both.
j. “Time,” when used in the context of a clock reading, is the hour in Coordinated Universal Time (UTC) or the local equivalent, as appropriate, and the minutes. Change to the next minute is made at the minute plus 30−second point, except for time checks, which are given to the nearest quarter minute.
k. “Miles” means nautical miles.
l. “Approved Separation” means separation in accordance with the applicable minima in FAA Order JO 7110.65, Air Traffic Control.
1−2−4. NOTES
Statements of fact of a prefatory or explanatory nature and relating to the use of procedural material have been identified and worded as “Notes.”
1−2−5. MILITARY PROCEDURES IDENTIFICATION
A service abbreviation – USAF for U.S. Air Force, USA for U.S. Army, USMC for U.S. Marine Corps, USN for U.S. Navy, and USCG for U.S. Coast Guard – denotes that the procedure immediately following the abbreviation only applies to the designated service.
1−2−6. REQUIREMENTS REVIEW WITH INTERAGENCY PARTNERS
Pursuant to 49 U.S.C. Section 40103(b), the FAA Administrator is responsible for developing plans and policy for the use of the navigable airspace and assigning by regulation or order the use of the airspace necessary to
Application 1−2−1
JO 7610.14A 8/7/25
ensure the safety of aircraft and the efficient use of airspace. The FAA may modify or revoke an airspace assignment when required in the public interest. It is the policy of the FAA to consult with DoD, DHS, and other interagency partners, as necessary, in developing policies, plans, and procedures enabling the safe and efficient movement of air traffic, and while delivering air navigation services needed by national defense, homeland security, law enforcement, and emergency operations efforts. To assist in this endeavor, FAA will convene meetings, as necessary, with the interagency partners to review plans, procedures, and requirements for the special operations described in this order.
1−2−2 Application
Chapter 2. Services and Responsibilities › Section 1. ATC Services by the Military
Chapter 2. Services and Responsibilities
Section 1. ATC Services by the Military
2−1−1. WHERE SERVICE MAY BE PROVIDED
The military may provide airport traffic control service at airports not served by an FAA or contract civil tower.
2−1−2. AIR TRAFFIC CONTROL AUTHORITY
a. Requests to delegate air traffic control authority at a location not served by an FAA facility to a military facility must come to the national level.
b. If there is agreement at the national level between FAA Air Traffic Organization (ATO) Air Traffic Services and the appropriate military service, then delegation may be authorized.
c. If authorized, the FAA Service Area office may delegate Terminal Radar Approach Control (TRACON)/approach control authority at a location not served by an FAA facility to a military ATC facility.
REFERENCE− FAA Order JO 7610.14, Appendix 4, Memorandum of Agreement between Department of Transportation, Federal Aviation Administration, and the U.S. Army – the U.S. Navy – the U.S. Air Force.
d. Regardless of the originator, requests for the situational deployment and operation of mobile DoD and/or National Guard (NG) ATC assets or other air navigation services in the NAS in response to a significant incident must be coordinated through System Operations Security (AJR−2) or, when activated, the Joint Air Traffic Operations Command (JATOC) Crisis Action Team (J−CAT). AJR−2 and/or the J−CAT will lead any needed coordination with DoD, NG, and other interagency stakeholders such as the Federal Emergency Management Agency (FEMA); conduct coordination within the ATO on letters of agreement and other implementation steps; and provide final ATO approval or disapproval to DoD and/or NG.
2−1−3. FREQUENCY REQUIREMENTS
Air traffic control authority must not be delegated to the military until the facility is equipped to transmit and receive on all frequencies necessary to control all categories of instrument flight rules (IFR) traffic (including civil) operating on a regular basis in the terminal area.
2−1−4. LETTERS OF AGREEMENT (LOAs)/LETTERS OF PROCEDURE (LOPs)
LOAs/LOPs relating to the control of air traffic must be completed between the military air traffic control facility and appropriate FAA facilities.
2−1−5. TOWER EN ROUTE CONTROL SERVICE
Tower en route control procedures, stated in an LOA, may be implemented between an FAA−operated terminal area traffic control facility and a military−operated approach control facility if an FAA Air Traffic Representative (ATREP) or ATC specialist designated by the FAA Service Area office has ensured that military personnel involved are qualified. This tower en route control service includes traffic to and from an airport that is served by a non−FAA facility if all en route control is exercised by a designated FAA approach control facility or a military facility that has been properly certified.
2−1−6. EVALUATIONS BY FAA
a. FAA evaluations of military air traffic control facilities and airport surveillance radar (ASR)/precision approach radar (PAR) units that exchange control of air traffic directly with FAA facilities must be accomplished
ATC Services by the Military 2−1−1
JO 7610.14A 8/7/25
in accordance with Article I, Paragraph E, of the Memorandum of Agreement between the Department of Transportation, Federal Aviation Administration, and the U.S. Army, U.S. Navy, and U.S. Air Force in Appendix 4 of this order.
b. The intent of the evaluation is to determine that:
1. Equipment performance and staffing are adequate for the service being provided.
2. Personnel qualifications, certifications/credentials, and performance meet acceptable standards.
3. Procedures utilized are consistent with LOAs between FAA air traffic control facilities and the appropriate local military authority and local memorandum of agreement between FAA and appropriate military authority.
c. FAA evaluations may only be conducted through participation in support of Service−scheduled Service−led evaluations.
d. Military Service−specific evaluation checklists must be utilized during evaluations of military ATC facilities.
e. All deficiencies that may affect flight safety must be reported to the cognizant military authority responsible for ATC oversight for timely corrective action.
f. Special interest items for evaluation must be coordinated with the Service evaluation team lead a minimum of 30 days prior to the evaluation.
g. FAA participation in Service−led evaluations must be coordinated with the appropriate Military Representative (MILREP) a minimum of 30 days in advance, except the U.S. Army, which requires a minimum of 45 days advance coordination.
2−1−7. SUSPENDING APPROACH CONTROL OR OTHER AIR TRAFFIC CONTROL AUTHORITY
FAA suspension or withdrawal of approach control or other air traffic control authority delegated to military air traffic control facilities must be accomplished in accordance with Article I, Paragraphs F and G, of the Memorandum of Agreement between the Department of Transportation, Federal Aviation Administration, and the U.S. Army, U.S. Navy, and U.S. Air Force in Appendix 4 of this order.
2−1−8. USE OF MILITARY AUTHORITY ASSUMES RESPONSIBILITY FOR SEPARATION OF AIRCRAFT (MARSA)
The application of MARSA is a military service prerogative and will not be invoked by individual units or pilots except as follows:
a. Military service commands authorizing MARSA must be responsible for its implementation and terms of use. When military operations warrant an LOA and MARSA will be applied, the authority to invoke MARSA must be contained in the LOA. It must be noted that an LOA will not be required in all cases involving MARSA.
b. ATC facilities do not invoke or deny MARSA. Their sole responsibility concerning the use of MARSA is to provide separation between military aircraft engaged in MARSA operations and other nonparticipating IFR aircraft.
c. DoD must ensure that military pilots requesting special activity airspace (SAA) have coordinated with the scheduling agency, obtained approval for entry, and are familiar with appropriate MARSA procedures. ATC is not responsible for determining which military aircraft are authorized to enter SAA/ATC−assigned airspace (ATCAA).
2−1−9. RELEASE OF AIRCRAFT TO GROUND CONTROL APPROACH (GCA) UNITS
When a GCA unit is located on an airport that is provided IFR service by an FAA facility, details concerning the release of arriving and/or departing aircraft to the unit must be contained in an LOA. Include the following items:
2−1−2 ATC Services by the Military
a. Details of the procedures, GCA patterns, release points, and areas to be used.
b. The maximum number of aircraft that may be released to GCA at any one time.
c. Specific instructions concerning a missed approach, loss of communications, and loss of radar.
d. A statement that the GCA unit must be responsible for maintaining radar separation in accordance with FAA JO Order 7110.65, Air Traffic Control.
e. Detailed instructions concerning the exchange of information between GCA and approach control.
2−1−10. CONTROL OF FLIGHTS IN PATTERN
At locations where the FAA facility normally vectors arrivals to base leg or final approach, permit the GCA unit to control sufficient flights throughout the pattern to maintain proficiency.
2−1−11. EXCHANGE OF INFORMATION
At airports served by an FAA tower and a military GCA unit, an LOA must be formulated containing the following items:
a. Before conducting actual or practice GCA approaches, GCA personnel must coordinate with the tower to obtain approval of the runway of intended landing.
b. If GCA personnel wish to subsequently change runways, they must coordinate with and obtain approval from the tower for this change.
c. GCA personnel must include the number of the runway of intended landing when the base leg report is relayed to the tower.
d. If a GCA approach is to be conducted straight−in, the number of the runway of intended landing must be relayed to the tower when the final controller assumes control of the aircraft, but in no case later than the time the aircraft is 6 miles from the end of the runway.
e. Procedures for opposite direction approaches that include the following:
1. Description of inter—and intra—facility coordination, and
2. Establishment of cutoff points, such as distances or fixes for authorizing the approach.
ATC Services by the Military 2−1−3
Chapter 2. Services and Responsibilities › Section 2. Air Traffic Representative (ATREP)
Section 2. Air Traffic Representative (ATREP)
2−2−1. ASSIGNMENTS
In cooperation with the appropriate military authority, Service Center Operation Support Groups assign ATREPs by geographic area to military air traffic control facilities.
2−2−2. ATREP FUNCTIONS
FAA ATREP functions are listed in Article IV of the Memorandum of Agreement between the Department of Transportation, Federal Aviation Administration, and the U.S. Army, U.S. Navy, and U.S. Air Force in Appendix 4 of this order.
2−2−3. FAMILIARIZATION FLIGHTS
ATREPs are encouraged to coordinate familiarization flights with units within their respective area of responsibility whenever possible. When unit resources are available and unit mission is not degraded, the ATREP should attempt to complete a flight every 6 months in each unit−equipped aircraft or simulator.
2−2−4. REQUIRED ABSENCE
When required to be absent from their assigned duties, the ATREP must:
a. Notify the appropriate military authority and FAA facilities, and furnish the name and contact information of the designated alternate.
b. Notify the designated alternate and apprise them of matters requiring ATREP services.
2−2−5. ALTERNATE AIR TRAFFIC REPRESENTATIVE
In order to ensure continuing FAA representation, an appropriately qualified alternate ATREP must be designated to substitute for the assigned specialist during periods of extended absence.
2−2−6. FUNCTIONS OF ALTERNATE ATREP
The alternate must perform the ATREP functions to the maximum extent possible.
2−2−7. COORDINATION
The ATREP and their designated alternate must coordinate to ensure familiarity with air traffic control facilities.
2−2−8. AVAILABILITY
FAA Service Areas must ensure that an ATREP and their designated alternate are not unavailable for the same period.
Air Traffic Representative (ATREP) 2−2−1
Chapter 2. Services and Responsibilities › Section 3. Miscellaneous
Section 3. Miscellaneous
2−3−1. ASSIGNMENT OF MILITARY TOWER LIAISONS
At the request of the USAF, a military tower liaison may be assigned to the cab of an FAA tower located on a joint−use airport or military base if space other than at the operating desk is available. Under these circumstances:
a. Telephone or intercom equipment that is necessary by virtue of the assignment of a military tower liaison to the tower must be independent of the tower system and must be reimbursable.
b. Install no radio equipment at this position. The release of a frequency and transmitting capability to the military tower liaison must be at the discretion of the area manager, and only in the case of an emergency. No air traffic control instructions must be formulated or transmitted by the military tower liaison, nor must the military tower liaison interfere in any manner with the performance of duties by FAA personnel.
c. The military tower liaison assigned must be on duty only during military flight activities. In many cases, this will only be during the hours from sunrise to sunset.
d. The number of personnel so assigned must be kept at a minimum. In most cases, one tower liaison should suffice to provide the necessary services.
2−3−2. SUPERVISOR OF FLYING (SOF)
Procedures governing the use of designated SOF inflight emergency frequencies must be contained in an LOA between the USAF and the appropriate FAA ATC facility.
a. The LOA must specify a radio frequency to be used by the SOF during the emergency.
b. Each LOA must contain explicit coordination procedures to be followed by the SOF prior to use of any ATC frequency including 121.5/243.0.
c. ATC must have the capability to override the SOF discrete frequency when required for ATC purposes.
2−3−3. MILITARY AIRSPACE MANAGERS
The military services have assigned airspace managers at various levels of command who are responsible to work with FAA and other agencies to identify, coordinate, procure, and manage airspace, and to develop and coordinate agreements/procedures to support military flight operations in meeting both peace and war−time requirements.
2−3−4. MILITARY REPRESENTATIVES (MILREPs)
DoD Military Representatives (MILREPs) are FAA’s principal points of contact for DoD aviation, airspace, and air traffic control matters, and are instrumental in providing effective liaison and agency interoperability. MILREP positions are embedded with various FAA offices at both FAA Headquarters and FAA Service Centers.
NOTE− For contact information on MILREPs, see Appendix 4 for the Memorandum of Agreement (MOA) between the Federal Aviation Administration (FAA) and the Department of Defense (DoD) for Military Representatives to the FAA.
2−3−5. DOD REIMBURSABLE SUPPORT TO FAA
FAA considers it essential to national security that military personnel present DoD’s perspective and provide expertise as members of the FAA staff and to ensure these military personnel are properly utilized in specific positions that will benefit both FAA and DoD. The DoD assigns military personnel as DoD Reimbursable Support to FAA for that purpose. FAA lines of business may request military reimbursable support on a
Miscellaneous 2−3−1
JO 7610.14A 8/7/25
case−by−case basis in accordance with DoD Instruction (DoDI) 1000.17, Detail of DoD Personnel to Duty Outside the Department of Defense, available on the DoD’s Directives Division Website at https://www.esd.whs.mil/DD/.
NOTE− See Appendix 3 for FAA and DoD memoranda that provide guidance for DoD Reimbursable Support to FAA.
Miscellaneous 2−3−2
Chapter 3. Military Exercise Planning › Section 1. General
Chapter 3. Military Exercise Planning
Section 1. General
3−1−1. PURPOSE
This chapter describes exercise requirements, policy, procedures, and criteria for planning military aviation exercises.
3−1−2. POLICY
Exercises will be planned, insofar as possible, to be conducted within U.S. controlled airspace. Exercise planners must coordinate with the affected ATC facilities all pertinent data relative to the mission. During initial planning with FAA, a decision will be made to determine the capability of FAA to provide ATC services for the entire exercise, or the extent to which services can be provided. Airspace requirements must be identified at this initial planning stage to ensure adequate processing time for airspace actions. Efforts will be made to minimize conflicts with other operations being conducted in the area.
3−1−3. PROCEDURES
ATC services to exercise aircraft must be predicated on the following:
a. Issuance of an appropriate ATC clearance. This includes filing a flight plan for each departure. The method of filing may be determined at the local level.
b. Pilot adherence to procedures, routes, and altitudes as agreed to between military users and air route traffic control centers (ARTCCs) through letters of agreement (LOAs), and/or Special Instructions (SPINS).
c. Aircraft participating in planned exercises must be afforded ATC clearances as agreed upon through LOAs.
d. Procedures for an altitude reservation (ALTRV) required in the conduct of an exercise are contained in Chapter 4 of this order.
3−1−4. SPECIAL USE AIRSPACE (SUA)
a. The establishment of special use airspace (SUA) as defined in FAA Order JO 7400.2, Procedures for Handling Airspace Matters, for planned exercises must be processed through the appropriate FAA Service Area. Other exercise−related airspace needs, such as ATCAA, aerial refueling tracks, etc., must be coordinated with the appropriate ARTCC.
b. Exercise airspace should be approved provided the airspace requirements will not impose an unreasonable burden upon the National Airspace System.
c. The appropriate military authority, when denied exercise airspace, may request the Service Area military representative to obtain further consideration from the appropriate FAA Air Traffic Service Area.
d. LOAs for exercise operations in ATCAA, stereo−type flight plans, and other exercise procedures must be coordinated with the ARTCCs concerned at least 45 days prior to the beginning of the proposed exercise.
3−1−5. MILITARY AIRSPACE PLANNING
To assist FAA and military personnel in planning and preparing for military exercises that require establishment of temporary Special Activity Airspace (SAA), the following listing of information items has been developed.
REFERENCE− FAA Order JO 7400.2, Procedures for Handling Airspace Matters.
General 3−1−1
JO 7610.14A 8/7/25
a. After all coordination has been completed and in sufficient time to process an airspace action, if needed, a formal proposal should be submitted to the appropriate FAA Service Area Office. The proposal should include:
1. Name of exercise.
2. Location and description of temporary SAA.
3. Time of designation.
4. Controlling and using agency.
5. Complete justification for the requested temporary SAA, including:
(a) Number of aircraft involved.
(b) Types of aircraft and missions they will perform.
(c) The exercise concept of operation (scenario).
6. A statement that describes the entire exercise area must include the following:
(a) Availability/non−availability for use by nonparticipating aircraft for the entire exercise period;
(b) Availability for real−time coordination with ATC and release of one or more portions of the area for use by nonparticipating aircraft for part of the exercise period; and
(c) Area/altitude/time of the exercise that may be available for release. Specify each portion, providing vertical and horizontal dimensions and for what period of time each portion may be available for release.
7. Requirements for refueling tracks, including location, visual flight rules (VFR) or instrument flight rules (IFR), in or below Class A airspace.
8. Military commands and, if applicable, other departments and agencies that will participate in the exercise.
9. Requirements for FAA liaison personnel at exercise facilities and military liaison personnel at affected FAA facilities.
10. Provisions to be made for nonparticipating aircraft desiring to operate in the exercise area.
(a) Local airport operations.
(b) Ingress and egress routes.
(c) Overflights.
(d) Capability of the using agency to accept direct radio requests from pilots.
b. Four months prior to the proposed exercise effective date, the proponent furnishes the following data:
1. Bases to be used as staging airfields and the estimated volume of activity at each.
2. Inactive bases to be activated and their locations.
3. Military control facilities or navigational aids to be established where none exists for use by participating aircraft outside of the exercise area. Information provided should include locations and frequencies.
4. Requirements for ingress and egress areas.
5. Requirements for routes from staging bases to include estimated volume of use.
6. Location of participating military air traffic facilities.
7. Requirements for military control of exercise traffic outside of the exercise area.
c. Three months prior to the beginning of the exercise:
1. Make provisions to ensure that participating pilots are provided the capability of closing VFR flight plans.
General 3−1−2
2. Provide information concerning other activities not mentioned which will require development of special operating procedures, such as an LOA or SPINS.
d. Forty−five (45) days prior to beginning of exercise:
1. Provide any additional information deemed necessary by FAA or the exercise proponent.
2. Provide copies of all established procedures and agreements for distribution to FAA and military personnel who require this information.
3−1−6. FAA MILITARY LIAISON OFFICERS’ RESPONSIBILITIES
FAA Military Liaison officers must encourage mission planning officers to include requested airspace requirements in the information disseminated with the request for exercise approval. In addition, they should recommend the use of planning conferences for the resolution of any issues that may impact air traffic.
3−1−7. CHANGES IN REQUIREMENTS
Changes to the exercise should not be made within 45 days of the exercise unless they are essential to the safe and successful conduct of the exercise or to reduce the amount of SAA to be designated.
3−1−8. PUBLIC NOTIFICATION
To minimize the effect of an exercise upon the public and to enhance flight safety, the military, with the assistance of FAA, must notify the public, to the maximum extent possible, with the location, configuration, and periods of use of the exercise areas.
3−1−9. PLANNING CONFERENCES
Initiate action to resolve problems attendant to military exercises that appear to impose an unreasonable burden upon the air traffic control system or other users of the airspace through the use of planning conferences, telephones, or other suitable media.
General 3−1−3
Chapter 3. Military Exercise Planning › Section 2. Criteria
Section 2. Criteria
3−2−1. PURPOSE
This section prescribes policy, criteria, administrative and operating procedures pertaining to airspace for military operations/training activities during planned exercises and daily training missions/research, development, test and evaluation (RDT&E).
3−2−2. POLICY
FAA recognizes that the military has a continuing requirement to conduct certain training and RDT&E activities within airspace as free from other aircraft as is practicable. Therefore, certain special military training and/or RDT&E operations must be conducted within ATC−assigned airspace (ATCAA), altitude reservation (ALTRV), military operations areas (MOA), restricted areas, warning areas, and IFR military training routes (IR) so that these activities are separated from other IFR traffic in controlled airspace. Flights to/from such areas must be under the control of either FAA or military ATC facilities to the maximum extent possible. The policies and procedures for designating special use airspace (SUA) are contained in FAA Order JO 7400.2, Procedures for Handling Airspace Matters.
3−2−3. AIRSPACE DESCRIPTION
Airspace utilized for military operations must be described in terms of lateral and vertical dimensions and specific times of use. In developing the dimensions and times of use for SUA and ATCAA descriptions, apply the criteria contained in Chapter 21, Section 2, of FAA Order JO 7400.2, Procedures for Handling Airspace Matters.
3−2−4. LIMITATIONS
a. The designation of SUA or ATCAA must be limited to the minimum number of areas necessary to support operational requirements.
b. To the extent possible, the area must be designed so as to accommodate the maximum number of different types of military activities in the same airspace area. The military must provide procedures for joint−use scheduling in an area.
c. To facilitate joint−use of SUA/ATCAA, activation must be limited to the minimum area, altitude, and time required for the activity/mission.
3−2−5. LETTERS OF AGREEMENT/PROCEDURE
a. Letters of agreement/procedure governing SUA must include as a minimum:
1. Scheduling procedures and positive updating, to include requirement and time parameters for providing these updates to the schedule.
2. Activation/deactivation procedures.
3. Activation/deactivation times.
b. The letters of agreement/procedure governing special conditions of use and procedures for each SUA and ATCAA areas must be authorized (signed) by the affected ATC facility manager and the military representative of the originating/scheduling activity.
c. Each SUA/ATCAA area will have a designated military office responsible for scheduling all military activities within that area. Areas must not be used for military activities unless scheduled by the responsible military office.
Criteria 3−2−1
JO 7610.14A 8/7/25
d. When the use of SUA/ATCAA has been requested in accordance with agreed upon procedures, the military scheduling unit is responsible for determining priority of use and for advising all users of the operational procedures restrictions or other conditions contained in the letters of agreement/procedure.
Criteria 3−2−2
Chapter 3. Military Exercise Planning › Section 3. ATCAA and MOA Procedures
Section 3. ATCAA and MOA Procedures
3−3−1. REQUIREMENT
a. Each ATC−assigned airspace (ATCAA)/military operations area (MOA) must have a designated military unit responsible for scheduling all military flights intending to use the airspace. If the designated military unit does not have a continuous point of contact—i.e., a unit subject to deployment or a unit not available during normal work days (Air National Guard unit working Wednesday through Sunday)—then an alternate scheduling agency will be designated. ATCAA/MOAs must not be used for military training/ research, development, test and evaluation (RDT&E) unless scheduled by the scheduling agency.
b. Procedures governing operations within ATCAAs and MOAs must be specified in letters of agreement authorized (signed) by the controlling facility Air Traffic manager and the military representative of the originating/scheduling agency (primary or alternate). The alternate scheduling agency will have the same responsibilities as the primary scheduling agency. Procedures must be developed to ensure continuity of scheduling functions so that the primary and alternate scheduling agencies do not schedule airspace simultaneously.
3−3−2. USING AGENCY RESPONSIBILITIES
When the use of an ATCAA/MOA has been requested, as specified in the letter of agreement, the using agency must:
a. Determine priority of use and advise all users of the pertinent procedures contained in the letter of agreement.
b. Establish a real−time activity schedule indicating airspace use times and forward the schedule and any subsequent changes to the controlling agency.
c. Develop procedures with the military using units to ensure that they inform the scheduling agency, as soon as possible, of any periods of nonuse (1 hour or longer) after the initial schedule has been established.
NOTE− Efficient management of ATCAAs/MOAs require that activity schedules reflect the real−time use of the airspace. After the initial activity schedule has been coordinated and established, maintenance problems, weather conditions, etc., can cause military using units to cancel previously scheduled missions. To provide FAA and the civil airspace users with actual (real−time) ATCAA/MOA activity schedules, it is essential that the military using units inform the scheduling agency of those unscheduled periods of nonuse so that the information can be disseminated to all interested parties.
3−3−3. CONTROLLING AGENCY RESPONSIBILITY
a. The controlling agency (normally an ARTCC) must originate a Notice to Airmen (NOTAM) for MOA activity scheduled for other than published times as follows:
1. The MOA contains a NOTAM provision in its times of use legal description.
2. The MOA can only be activated by NOTAM.
b. The NOTAM for MOA activity scheduled for other than published use times must be issued at least 2 hours prior to the beginning of the planned activity.
REFERENCE− FAA Order 7930.2 Notice to Airmen (NOTAM), Para 6−1−2, Special Activity Airspace (SAA).
3−3−4. ATC CONTROL WITHIN ATCAAs AND MOAs
ATCAAs and MOAs may be controlled by an ATC facility. Every effort should be made to provide instrument flight rules (IFR) service within these areas when requested by the military:
ATCAA and MOA Procedures 3−3−1
JO 7610.14A 8/7/25
a. When IFR service is provided by the ATC facility within the area, the separation within the area is the responsibility of the ATC facility unless MARSA is established in accordance with paragraph 2−1−8, Use of Military Authority Assumes Responsibility for Separation of Aircraft (MARSA).
b. The pilot, when cleared into the area, is responsible for remaining within the area, whether visual flight rules (VFR) or IFR; however, the ATC facility should assist the pilot when the aircraft is under its control.
3−3−5. NONRADAR AND COMMUNICATIONS
ATCAAs and MOAs may be established in airspace where radar and/or direct communication is not available. Procedures concerning these areas must be specified in a letter of agreement.
ATCAA and MOA Procedures 3−3−2
JO 7610.14A 8/7/25 7/9/26 JO 7610.14A CHG 2
Chapter 3. Military Exercise Planning › Section 4. ATCAA and MOA Procedures
Section 4. ATCAA and MOA Procedures
3−4−1. EXERCISE/ORI
a. To the extent practical, exercises and ORIs must be conducted using existing special use airspace (SUA), military training routes (MTR), air refueling tracks/anchors, and Airborne Warning and Control System (AWACS) orbits. The exercise/ORI project officer must advise the appropriate ARTCC/CCF/HCF(s) of the exercise/ORI objective, scenario, and execution date; and must ensure coordination is effected in sufficient time to establish arrival/departure procedures and ingress/egress of target/exercise area/air refueling tracks/anchors.
b. If alteration of existing SUA or the establishment of temporary SUA, MTRs, air refueling tracks/anchors, and/or AWACS orbits are required for an exercise or ORI, the exercise/ORI project officer must ensure coordination is effected with the appropriate ARTCC/CCF/HCF(s) in sufficient time to comply with the lead time required for development of letters of agreement and processing airspace proposals.
c. If an altitude reservation (ALTRV) is required for the exercise/ORI, the project officer must ensure the above coordination is coordinated with the appropriate ARTCC/CCF/HCF(s) prior to submitting the ALTRV request to the FAA Central Altitude Reservation Function (CARF).
d. ATC facilities may authorize communications out/reduced communications procedures in lieu of radio position reporting if required by military operations and prior coordination has been accomplished with affected ATC facilities.
3−4−2. NOTIFICATION OF EXERCISE/ORI
Exercise/ORI mission notification will be provided no later than 30 days prior to the departure date of the mission to the affected ARTCC/CCF/HCF(s).
ATCAA and MOA Procedures 3−4−1
Chapter 3. Military Exercise Planning › Section 5.
JO 7610.14A 8/7/25 7/9/26 JO 7610.14A CHG 2
Section 5. Air Mobility Command (AMC) Exercise/Operational Readiness Inspection (ORI)
3−5−1. ORI
The AMC project officer must coordinate with the air route traffic control center (ARTCC) affected by an ORI to establish arrival/departure procedures, ingress/egress of target areas, and air refueling tracks/anchor areas prior to submitting the altitude reservation (ALTRV) to the FAA Central Altitude Reservation Function (CARF).
3−5−2. NOTIFICATION OF ORI
Exercise/ORI mission notification will be provided no later than 30 days prior to the departure date of the mission to the affected ARTCC/CCF/HCF(s).
Air Mobility Command (AMC) Exercise/Operational Readiness Inspection (ORI) 3−5−1
Chapter 3. Military Exercise Planning › Section 6.
JO 7610.14A 8/7/25 7/9/26 JO 7610.14A CHG 2
Section 6. United States Strategic Command (USSTRATCOM) Operational Readiness Inspection (ORI)
3−6−1. ORI BOOKLETS
The USSTRATCOM will provide current ORI Altitude Reservation Flight Plan books to appropriate air route traffic control center (ARTCC)/ATC facilities and air defense regions/sectors. The Central Altitude Reservation Function (CARF) will be provided with a current base code listing to be used for identifying participating units.
3−6−2. NOTIFICATION OF ORI
ORI mission notification will be provided to CARF via telephone no later than (NLT) 30 calendar days prior to the date of the mission. The Inspector General Scheduling Division (IGXP) will forward the current information NLT 15 days prior to the mission. The telephonic coordination will include:
a. Mission names (from ORI books).
b. Call signs (if they differ from the ones listed in the ORI books).
c. Initiation hour (“I” hour)—the earliest time a unit may be told of the mission timing.
d. Execution reference time (“ERT”)—hour mission take−off time.
3−6−3. NOTIFICATION FORMAT
CARF must forward the ORI mission notification information to the required ARTCC/CCF/HCF(s) no later than 30 days prior to the departure date of the mission. The ARTCC/CCF/HCF(s) must be provided the current information, as provided by IGXP, NLT 15 days prior to the mission via the Aeronautical Fixed Telecommunications Network (AFTN) as follows:
a. Mission name.
b. Bomber call signs.
c. Tanker call signs.
d. “I” hour.
e. “ERT” hour.
3−6−4. MISSION DELAYS
ORI missions will delay in 24−hour increments.
United States Strategic Command (USSTRATCOM) Operational Readiness Inspection (ORI) 3−6−1
Chapter 3. Military Exercise Planning › Section 7. Navy Shipboard Exercises
JO 7610.14A 8/7/25 7/9/26 JO 7610.14A CHG 2
Section 7. Navy Shipboard Exercises
3−7−1. FLEET AREA CONTROL AND SURVEILLANCE FACILITIES (FACSFACs)
FACSFACs are Navy air traffic control facilities established to manage/schedule special use airspace (SUA), operating areas (OPAREAs), and off−shore airspace in support of air, surface and sub−surface operations. FACSFACs should be used as the point of contact for FAA activities with respect to Navy shipboard operations. Although each FACSFAC has location−specific responsibilities, they normally perform the following services:
a. Scheduling, coordinating, and monitoring of surface, sub−surface and airborne units operating within and transiting between offshore OPAREAs and the National Airspace System (NAS).
b. Scheduling and coordinating airborne units operating within assigned airspace of inland operating areas.
c. Scheduling of military training routes (MTRs).
d. Maintaining liaison with other controlling agencies, fleet commands, other military commands, FAA, Coast Guard, and selected state and federal agencies.
e. Providing SUA control services to participating military units, other government aircraft, government contract aircraft, and, on a not−to−interfere basis, civil aircraft as delineated in letters of agreement with applicable FAA and military activities.
f. Scheduling and coordinating associated commercial and military aircraft services support.
g. Assistance during search and rescue (SAR) and medical evacuation (MEDEVAC).
3−7−2. FACSFAC LOCATIONS
Each FACSFAC is structured to meet the operational needs of a specific geographic area in direct support of fleet requirements. Facility location and associated areas of responsibility are as follows:
a. FACSFAC San Diego, CA: responsible for NOCAL/SOCAL OPAREAs.
b. FACSFAC Pearl Harbor, HI: responsible for Hawaiian/MIDPAC OPAREAs.
c. FACSFAC Vacapes, VA: responsible for Narragansett, Atlantic City, Vacapes, and Cherry Point OPAREAs.
d. FACSFAC Jacksonville, FL: responsible for Charleston, Jacksonville, Gulf of America, Caribbean, and Puerto Rico OPAREAs.
3−7−3. FLEET READINESS EXERCISES
The Navy must coordinate with the ARTCC/CCF/HCF(s) involved in the handling of aircraft operating from shore bases participating in fleet readiness exercises at least 30 days prior to the exercise.
3−7−4. PLANNING CONFERENCES
Planning conferences between the regional FACSFAC supporting Navy shipboard operations, the regional Navy representative (NAVREP) and the appropriate FAA activity should be held to review operation planning and execution. Emphasis should be placed on procedures for aircraft transiting the NAS to/from inland OPAREAs and target complexes. The following topics should also be discussed:
a. Adherence to coordinated strike/launch sequence plans, published stereo routes and pre−coordinated flight plan routes.
b. Adherence to filed instrument flight rules (IFR) flight plan call signs while transiting the NAS.
Navy Shipboard Exercises 3−7−1
JO 7610.14A 8/7/25 3/15/07 7110.65R CHG 2 JO 7610.14A CHG 2 7/9/26
c. Assignment of Mode 3 Identification Friend or Foe (IFF) codes for flight operations within the air defense identification zone (ADIZ).
d. Coordination with other commercial, military, and civil agencies impacted by shipboard operations.
e. Issuance of Notices to Mariners (NOTMARs) for hazardous operations.
f. Notification procedures for completion of operations in altitude reservation (ALTRV)/SUA/range/target areas.
g. Flexibility/contingency plans for unforeseen changes to planned operations.
3−7−5. AIRCRAFT CARRIER OPERATIONS
Regional FACSFACs are the communications link between FAA activities and aircraft carriers. Shipboard air operations personnel establish ship−to−shore communications with the regional FACSFAC (unless beyond communication range or if shipboard electronic emissions are restricted) to facilitate the conduct of aircraft carrier operations. If circumstances dictate, airborne carrier air wing aircraft (such as E−2 airborne early warning aircraft) can be used as “middle−man” to coordinate with the aircraft carrier. Typical aircraft carrier operations consist of:
a. Cyclic operations consisting of numerous aircraft launching and recovering from the ship for extended periods of time.
b. Carrier qualification/refresher training consisting of continuous flight operations for pilot proficiency that may require several aircraft to divert/bingo to a shore installation for minimum/emergency fuel or other emergency situations.
c. ALPHA strike and amphibious assault exercises that require numerous aircraft to transit coastal routes to/from inland areas/target complexes.
d. Air wing flyoffs consisting of numerous aircraft (approximately 50–70 aircraft) departing the ship en route to their home bases at the completion of the at−sea period.
e. SAR and MEDEVAC missions.
3−7−6. FLYOFF PROCEDURES
Procedures for the coordination and handling of air wing flyoffs from aircraft carriers returning from deployments must be developed between appropriate FAA activities and the regional FACSFAC
3−7−7. AIR CAPABLE SHIP OPERATIONS
Air capable ships are naval vessels, such as destroyers, frigates, etc., that embark a helicopter detachment of one to three aircraft. Air capable ship operations consist of surveillance missions, logistical support flights, MEDEVAC missions, SAR support and passenger/cargo flights to/from shore installations in support of fleet operations. FACSFACs should be used as the point of contact for FAA activities with respect to air capable ship operations.
3−7−8. CENTRAL ALTITUDE RESERVATION FUNCTION (CARF) APPROVED ALTRVS
Exercises/operations requiring FAA CARF altitude reservations will normally be coordinated by FACSFAC in accordance with Chapter 4 of this order.
3−7−9. FAMILIARIZATION VISITS
Procedures must be developed to provide for liaison visits to the aircraft carrier by FAA personnel. Carrier air wing and shipboard air operations personnel must develop procedures to visit FAA activities.
3−7−2 Navy Shipboard Exercises
Chapter 4. Altitude Reservation (ALTRV) Procedures › Section 1. General
JO 7610.14A 8/7/25 7/9/26 JO 7610.14A CHG 2
Chapter 4. Altitude Reservation (ALTRV) Procedures
Section 1. General
4−1−1. PURPOSE
This chapter establishes policy, prescribes uniform procedures, and sets forth criteria to be applied to all phases of an ALTRV. The authority, responsibility, and general operating procedures under the ALTRV concept for Central Altitude Reservation Function (CARF) and other concerned ATC facilities are herein defined.
4−1−2. POLICY
An altitude reservation is authorization by the CARF or the appropriate ARTCC/CCF/HCF under certain circumstances, “for airspace utilization under prescribed conditions.” An altitude reservation must receive special handling from FAA facilities.
a. CARF or the appropriate ARTCC/CCF/HCF (if the approving authority) is responsible for separation of the ALTRV mission from other ALTRVs after the aircraft have reached the first cruising altitude to a point where descent is started into the destination airport or where the ALTRV ends.
b. ALTRVs must be classified as either moving or stationary.
1. A moving ALTRV encompasses en route activities and advances with the mission progress, i.e., the reservation moves with the aircraft or flight.
2. A stationary ALTRV encompasses activities within a fixed volume of airspace to be occupied for a specified time period.
3. The final approval authority is designated to the authority whose area of responsibility includes the departure airport. The final approval authority is responsible for the issuance of the final ALTRV approval.
NOTE− When the ALTRV is for aerial refueling, the departure airport is usually determined by the receiver aircraft.
4−1−3. APPLICATION
An ALTRV may be employed under conditions normally prescribed for the mass movement of aircraft or other special user requirements that cannot otherwise be accomplished.
a. In the application of ALTRV procedures, policies, and criteria, due consideration must be given to total user requirements throughout the navigable airspace in accordance with the procedures prescribed herein.
b. Unmanned aircraft system (UAS) operations within ALTRVs must operate in accordance with all applicable FAA regulations, including, if applicable, a written letter of authorization (LOA) and certificate of waiver or authorization (COA).
c. Stationary ALTRVs within oceanic and offshore airspace may encompass rocket, missile, and state activities. If multiple aircraft are expected to be in the ALTRV at the same time and military authority assumes responsibility for separation of aircraft (MARSA) will not be used, separation procedures must be covered in an LOA.
NOTE− State activities consist of DoD, DHS, law enforcement, and federal and state government agencies’ aircraft. NOTE− Commercial space operations are examples of activity permitted in ALTRVs within oceanic and offshore airspace.
d. Stationary ALTRVs in airspace other than oceanic and offshore may be approved for state aircraft; activities covered in Section 7, Special/Emergency ALTRVs; and other activities covered by an LOA.
General 4−1−1
JO 7610.14A 8/7/25 3/15/07 7110.65R CHG 2 JO 7610.14A CHG 2 7/9/26
e. An ALTRV must not be used in lieu of other airspace expressly defined and designated for a special activity. This airspace must be coordinated in accordance with (IAW) FAA Order JO 7110.65, paragraph 9−3−4, Transiting Active SUA/ATCAA.
NOTE− An ALTRV approval does not include approval to use special activity airspace. This airspace must be coordinated by the point of contact (POC) with the Using Agency IAW AP1A FLIP.
f. An ALTRV approval does not constitute authorization for chaff or electronic attack (EA) activities.
g. ALTRVs for single aircraft will not normally be approved, with the following exceptions:
1. The aircraft will join a tanker en route and conduct air refueling.
2. Operations above FL 600.
3. UAS with authorization.
h. Aircraft established on an approved ALTRV route and altitude must not be changed except in the interest of safety of flight. The ARTCC/CCF/HCF may cancel the entire ALTRV if the aircrew requests routing and/or altitude changes that are not in the approved ALTRV. Consideration will be given to the ALTRV when deviations are required.
i. An ALTRV APVL is valid in controlled airspace only.
j. Except within 180 NM of Bermuda, air refueling within New York Oceanic Airspace must be conducted on an approved ALTRV. Tankers joining receivers must be on an ALTRV to join/leave a receiver’s ALTRV. Altitudes will normally be approved at or below FL 280. Both receivers and supporting tanker ALTRVs must begin at least 60 NM prior to entering and must continue at least 60 NM after leaving New York Oceanic Airspace.
k. Within Anchorage Oceanic Airspace, west of a line between 5340N 16800E to 4830N 17230E (approximately 430 NM from the Tokyo/Anchorage boundary), tankers joining or leaving a receiver ALTRV must be on an ALTRV.
l. Due to handoff and communication transfer, ALTRVs that transit international airspace must not begin, end, climb, descend, expand, compress, orbit, join, or leave on the boundary.
m. Moving ALTRVs that transit domestic airspace must not begin, end, climb, descend, expand, compress, orbit, join or leave on ARTCC boundaries.
4−1−4. ALTERNATE TRACKS
Circumstances occasionally dictate the need for submitting alternate refueling/special tracks to meet mission objectives. Although they may be filed on the same request, only the primary track must initially be approved. If the alternate track is needed and coordinated in a timely manner to process the change, the alternate track must be approved and the primary track canceled.
NOTE− Depending on location and timing, coordination requirements may dictate up to 72−hour notice prior to departure time.
4−1−5. USER REQUIREMENTS
a. When approving an ALTRV, every effort should be made to ensure requested altitudes are approved and to provide adequate altitudes for the normal requirements of other airspace users. Total user requirements, traffic flow, available routes, military missions, and other operations that are using or that propose to use the ATC system must be afforded equitable consideration.
b. Special care must be exercised when processing ALTRV requests that entail operation on a broad frontal width. Indiscriminate approval of these requests could render a considerable portion of navigable airspace unavailable to other users for extended periods of time.
4−1−2 General
4−1−6. ALTITUDE CRITERIA
a. Altitude utilization criteria must be flexible and adjusted as required. Seasonal traffic trends and changes in revised civil and military jet aircraft inventories are factors that necessitate flexibility.
b. Due to pressure gradients, FL 180 will not normally be acceptable on an ALTRV except in oceanic airspace.
c. The normal altitude block assignments for nonstream aircraft are:
1. Two aircraft refueling, two altitudes.
2. More than two aircraft, 500 feet per aircraft.
NOTE− Flights of six or more aircraft should consider cell formations; 30 minutes between the cells.
General 4−1−3
Chapter 4. Altitude Reservation (ALTRV) Procedures › Section 2. Central Altitude Reservation Function (CARF)
JO 7610.14A 8/7/25 7/9/26 JO 7610.14A CHG 2
Section 2. Central Altitude Reservation Function
(CARF)
4−2−1. INTERNATIONAL COORDINATION
Coordinate international altitude reservation (ALTRV) request with the appropriate foreign altitude reservation facilities in accordance with CARF letters of agreement. This includes missions that depart from points within a control area/flight information region (CTA/FIR) in which the United States is responsible for the provision of air traffic services and enters a CTA or FIR in which a foreign country is responsible for the provision of air traffic services.
NOTE− Do not coordinate or approve classified missions that penetrate a CTA/FIR in which another country provides air traffic services, unless authorized in advance by the appropriate military authority. See subparagraph 4−10−1b.
4−2−2. APPROVAL AUTHORITY
a. CARF is authorized to approve an ALTRV in any CTA/FIR in which the United States is responsible for the provision of air traffic services, except in the territorial airspace of a foreign country, when authorized by the appropriate authorities of the foreign country:
1. FL 240 and above west of the 100th meridian.
2. FL 180 and above east of the 100th meridian.
b. CARF is the final approval authority for any ALTRV departing United States airspace which traverses or penetrates airspace outside a CTA/FIR in which the United States is responsible for the provision of air traffic services, regardless of the ALTRV location or start point.
4−2−3. ALTRV APPROVAL REQUEST (APREQ)
CARF must:
a. Transmit all ALTRV APREQs to the appropriate U.S. ARTCC/CCF/HCF and International Altitude Reservation Facilities as per letter of agreement and list those facilities in Item G of the ALTRV APREQ per section 10 of this chapter.
NOTE− This includes aircraft departing a point in the U.S. on a DD−175/1801 and beginning an ALTRV in Canadian airspace.
b. Normally, CARF will transmit the APREQ to impacted ARTCC/CCF/HCFs prior to issuing an approval.
c. When mission requirements or timeliness dictate, coordinate as needed by telephone, facsimile machine, or other electronic means.
NOTE− The APREQ coordination requirement may be waived in a national emergency.
d. Ensure Pacific Military Altitude Reservation Facility/European Central Altitude Reservation Facility (PACMARF/EUCARF) are addressed on the military ALTRV APREQ for any mission that departs U.S. airspace and traverses their countries’ FIRs or penetrates their traffic.
e. Advise all concerned ATC/international altitude reservation facilities and the project officer of any change to the original ALTRV APREQ prior to issuing a final ALTRV approval.
f. Process changes submitted by the project officer and ATC/international altitude reservation facilities.
g. Process all requests for ALTRVs in airspace above FL 600 in accordance with the provisions contained within this order for stationary and moving ALTRVs.
Central Altitude Reservation Function (CARF) 4−2−1
JO 7610.14A 8/7/25 3/15/07 7110.65R CHG 2 JO 7610.14A CHG 2 7/9/26
4−2−4. ALTRV APPROVAL (APVL)
CARF must be the final approval authority for any ALTRV departing a point within the United States CTA/FIR, regardless of the ALTRV start point, except as provided for in paragraph 4−3−2. CARF must:
a. Forward ALTRV APVLs to all concerned at least 24 hours prior to the proposed departure time, unless a shorter time is coordinated with all concerned U.S. ARTCC/CCF/HCF facilities. If special instructions are required concerning the delivery of the APVL to the project officer, they are to be included in the ALTRV APVL message. Forward ALTRV APVLs to the following:
1. Concerned U.S. ARTCC/CCF/HCF facilities.
2. International altitude reservation facilities, as appropriate.
3. Message originator.
4. Tanker support unit, when forwarding information is provided.
5. Other parties as requested in Item G of the ALTRV APREQ.
b. Provide the following information in Item G of the ALTRV APVL:
1. Location indicators of the recognized international altitude reservation facilities and U.S. air traffic control facilities concerned with the mission.
2. Whenever the requested altitudes include uncontrolled airspace, include the phrase “NOTE ALTRV APVL VALID IN CONTROLLED AIRSPACE ONLY.”
c. Precede a No−Notice ALTRV APVL message with “This is a (executing command) No−Notice Mission.”
d. Process proposed changes in an ALTRV APVL:
1. At least 24 hours prior to departure.
2. With less than the time specified above, subject to CARF discretion after approval from the affected ATC facilities.
e. Process the ALTRV in accordance with the above procedures and obtain APVL from facilities which abut the U.S. CTA/FIR whenever the ALTRV is penetrating traffic.
4−2−5. NOTIFICATIONS
Disseminate ALTRV cancellations to impacted U.S. air traffic facilities and recognized international altitude reservation facilities as soon as practicable.
4−2−6. AIRSPACE NOT UNDER CARF JURISDICTION
Coordinate with the appropriate international altitude reservation facilities in accordance with the applicable letters of agreement to obtain approval for ALTRV APREQs encompassing airspace under such facilities’ jurisdiction.
4−2−7. RESOLUTION OF CONFLICTS BETWEEN MISSIONS
Missions with higher precedence will be afforded priority over lower precedence missions when resolving a conflict. CARF will coordinate with the project officer for resolution of conflicts between missions. Information pertaining to a No−Notice mission conflict must not be divulged to anyone other than the designated trusted agents (see paragraph 4−3−7, Trusted Agents).
4−2−8. ISSUE ALTITUDE RESERVATION NOTICE TO AIRMEN (NOTAM)
CARF is responsible for the formulation and dissemination of Altitude Reservation NOTAMs for the portion of the ALTRV in the U.S. CTA/FIR that CARF is the approval authority (see paragraph 4−8−1, NOTAM Criteria).
4−2−2 Central Altitude Reservation Function (CARF)
4−2−9. ACKNOWLEDGMENT OF ALTRV APREQs
When requested, acknowledge receipt of ALTRV APREQs to the originator.
4−2−10. MESSAGES CLASSIFIED AS ENCRYPT FOR TRANSMISSION ONLY (EFTO)
Handle all ALTRV messages exchanged between CARF and ATC facilities, which are classified as EFTO via Defense Communication Systems, in accordance with FAA Order 1600.8, Communications Security (COMSEC). EFTO messages cannot be transmitted to foreign altitude reservation facilities.
4−2−11. LETTERS OF AGREEMENT
CARF is authorized to enter into letters of agreement as necessary to improve the coordination and processing of ALTRV requests provided that such agreements are not contrary to the provisions of this order.
Central Altitude Reservation Function (CARF) 4−2−3
Chapter 4. Altitude Reservation (ALTRV) Procedures › Section 3. ATC Facility Responsibilities
JO 7610.14A 8/7/25 7/9/26 JO 7610.14A CHG 2
Section 3. ATC Facility Responsibilities
4−3−1. APREQ REVIEW AND COORDINATION
a. Review all altitude reservation (ALTRV) approval requests (APREQs) to ensure completeness, and advise Central Altitude Reservation Function (CARF) of any requested change to the ALTRV APREQ as soon as possible.
b. Ensure that the required separation exists in accordance with (IAW) FAA Order JO 7110.65 between two or more missions departing within the ARTCC/CCF/HCF of origin up to the first cruising altitude requested. This coordination includes all ATC facilities to which airspace has been delegated.
c. Schedule ATC−Assigned Airspace (ATCAAs) to allow ALTRVs to transit or utilize the airspace. If unable to schedule an ATCAA, provide alternate routing.
4−3−2. ARTCC/CCF/HCF APPROVED ALTRVs
Where practical and advantageous, an ARTCC/CCF/HCF may be the final approval authority for an ALTRV when the entire route of flight and associated protected airspace will not involve more than two ARTCC/CCF/HCF areas of control jurisdiction. The ARTCC/CCF/HCF must:
a. Assume the ALTRV APREQ responsibilities outlined in paragraph 4−2−3.
b. Assume the ALTRV APVL responsibilities outlined in paragraph 4−2−4.
c. Forward ALTRV APREQ/APVL to CARF for ALTRVs which will be conducted in airspace outlined in paragraph 4−2−2.
d. Deliver all ALTRV APVLs and amendments to the designated project officer in accordance with delivery instructions contained in the ALTRV APREQ message. Comply with the security restrictions contained in the APREQ message regarding release time to military personnel, estimated time of departure (ETD), etc.
NOTE− ARTCC/CCF/HCFs are not authorized to approve ALTRVs whose routes of flight or protected airspace are not wholly contained within the U.S. CTA/FIR (see paragraph 4−2−1, Canadian and Overseas).
4−3−3. MISSION SEPARATION
Ensure that required separation exists, to the altitudes specified in paragraph 4−3−1, APREQ Review and Coordination, between two or more missions departing within the U.S. ARTCC/CCF/HCF of origin.
4−3−4. FLIGHT PROGRESS STRIPS
Departure ARTCC/CCF/HCF must ensure unclassified ALTRVs are entered into the NAS computer in accordance with FAA Order JO 7110.65, Air Traffic Control; and FAA Order JO 7210.3, Facility Operation and Administration, paragraph 8−1−2, ALTRV Flight Data Processing, to display the required information on mission aircraft utilizing an ALTRV.
4−3−5. NOTIFICATION
a. Forward departure times of ALTRV aircraft to the ALTRV approval authority and to all facilities concerned. Departure messages must include the departure time and identification of the following:
1. Cell formation.
2. First and last aircraft of a stream formation.
ATC Facility Responsibilities 4−3−1
JO 7610.14A 8/7/25 3/15/07 7110.65R CHG 2 JO 7610.14A CHG 2 7/9/26
3. Individual aircraft not listed in the above.
b. Forward cancellations of ALTRV aircraft and other ALTRV changes to CARF and appropriate approach control facilities. This applies to cancellations of individual aircraft within the ALTRV or the whole mission. CARF will forward the information to the appropriate ATC and international reservation facilities.
4−3−6. ISSUE ALTITUDE RESERVATION NOTAM
a. ARTCC/CCF/HCFs are responsible for the formulation and dissemination of an altitude reservation Notice to Airmen (NOTAM) for ALTRVs for which they are the final approval authority.
b. Coordination must be effected between adjacent ARTCC/CCF/HCFs for the issuance of a joint altitude reservation NOTAM if it will permit consolidation of the altitude reservation NOTAM information prescribed above.
4−3−7. TRUSTED AGENTS
Each ARTCC/CCF/HCF must provide CARF a current listing of trusted agents, responsible for safeguarding and controlling COMSEC material, updated at least once per year, no later than March 1. If the list changes during the year, forward updates as needed.
4−3−8. ALTRV AUTHORIZATION AND CHANGES
An ALTRV APVL authorizes the aircraft to climb or descend as specified. Controllers are not required to issue a climb or descent clearance for the various flight segments. They may, however, request that the pilot advise them prior to initiating an altitude change. Routing and altitude(s) of aircraft established on an approved ALTRV must not be changed except in the interest of safety of flight or as specified below:
a. Aircraft requested routing or altitude changes that are not in the approved ALTRV are handled in accordance with subparagraph 4−1−3i.
b. Short−term adjustments to altitude or course of single aircraft (or standard formation) on an ALTRV may be issued with the concurrence of the aircraft (flight) commander in order to expedite overall traffic flow as long as the controller ensures return of the aircraft to the ALTRV, within their sector or within sectors with which the adjustment and return are directly coordinated.
c. If ARTCC/CCF/HCF initiates changes to the ALTRV due to safety of flight or other extraordinary circumstances, military authority assumes responsibility for separation of aircraft (MARSA), if applicable, is suspended and the ARTCC/CCF/HCF assumes responsibility for separation. The ARTCC/CCF/HCF is also responsible to return the aircraft to the ALTRV as soon as practicable.
NOTE− Due to critical military operational requirements (timing, refueling, locations, etc.) that necessitated the ALTRV, changes must be kept to the absolute minimum required for safety of flight or other extraordinary circumstances.
d. Multiple cells in an ALTRV are responsible for their own separation (MARSA) from other cells within the same ALTRV from the initiation of the ALTRV until the termination or cancellation of the ALTRV.
1. Controller−assigned course or altitude changes without the concurrence of the formation flight leader will void MARSA between cells.
2. The ARTCC/CCF/HCF is responsible for returning the cell to the ALTRV as soon as practical and confirming re−establishment of MARSA between cells.
4−3−2 ATC Facility Responsibilities
Section 4. Mission Planning
4−4−1. RESOLVING MISSION CONFLICTS
During periods other than when the provisions of the Emergency Security Control of Air Traffic (ESCAT Plan 32 CFR part 245) are invoked, the order of precedence set forth in paragraph 4−4−2 below must be applied to all requests for altitude reservations (ALTRVs) for the purpose of resolving conflicts. Airspace assigned by ATC for the conduct of interceptor activity must be provided the same order of precedence class number as that applied to the ALTRV associated with the exercise or mission.
Chapter 4. Altitude Reservation (ALTRV) Procedures › Section 4. Mission Planning
NOTE− The ESCAT Air Traffic Priority List (EATPL) contained in the ESCAT Plan governs the movement of aircraft for airspace user requirements during time of tension and war.
4−4−2. ORDER OF PRECEDENCE
The order of precedence contained herein is designed to facilitate the handling of airspace user requirements.
a. The organization originating an ALTRV request must assign the appropriate order of precedence class number in accordance with the listing contained herein.
b. FAA may, under certain emergency conditions, determine an appropriate order of precedence classification.
c. The following class numbers establish the order of precedence designed to resolve mission conflicts in connection with ALTRVs:
1. Class One−Aircraft implementing peacetime national emergency plans as well as missile activities authorized by approved and pre−coordinated procedures or letters of agreement. ALTRV approval request (APREQ) should be filed as far ahead of departure/estimated time of launch as practicable.
2. Class Two−Aircraft engaged in search and rescue operations. ALTRV APREQ should be filed as far ahead of takeoff as practicable.
3. Class Three−Aircraft engaged in emergency air evacuation, hurricane operations, weather reconnaissance (WX RECON), or other operations involving safety of lives or property (i.e., use of airlift forces as directed by appropriate authority in support of domestic crises). ALTRV APREQ should be filed as far ahead of takeoff as practicable.
4. Class Four−Deployments at the direction of the Joint Chiefs of Staff (JCS) in support of an exercise or large−scale mission and fulfilling an unforeseen requirement. The deployment should be essential to the success of the exercise or mission when assigned Class Four precedence. ALTRV APREQ should be filed as far ahead of departure as practicable.
5. Class Five−Aircraft engaged in important peacetime service, joint or unified/specified command exercises or missions. Notification of application of this priority must be received from the appropriate military headquarters. ALTRV APREQ must be filed at least 15 days before proposed takeoff. It may be filed less than 15 days before proposed takeoff with Central Altitude Reservation Function (CARF) approval.
6. Class Six−Aircraft engaged in a large scale mission directed by a major command headquarters. ALTRV APREQ must be filed at least 10 days before proposed takeoff.
7. Class Seven−Aircraft engaged in evaluation−type operations or overseas deployment. ALTRV APREQ must be filed at least 4 days before proposed takeoff except for ALTRVs penetrating foreign airspace, which requires 6 days.
8. Class Eight−Aircraft engaged in missions directed by specified air forces or commands, aircraft engaged in other training exercises, and all other aircraft requesting ALTRVs. ALTRV APREQ must be filed at least 4 days before proposed takeoff except for ALTRVs penetrating foreign airspace, which requires 6 days.
Mission Planning 4−4−1
JO 7610.14A 8/7/25 3/15/07 7110.65R CHG 2 JO 7610.14A CHG 2 7/9/26
4−4−3. SPECIFY VOID TIME
Aircraft must depart within the assigned ALTRV APVL void for aircraft not airborne (AVANA) time for the purpose of providing separation between altitude reservations. Normal AVANA will be 1 hour.
4−4−4. RESCHEDULING
If a mission is to be delayed beyond the AVANA time, rescheduling:
a. Will normally be in 24−hour increments after the original schedule.
b. Can be in less than the time specified above, subject to CARF discretion and after approval from the affected ARTCC/CCF/HCF.
4−4−5. DELAY NOTIFICATIONS
As soon as the delay becomes apparent, notify the ALTRV approval authority and provide all available updated information.
4−4−6. EN ROUTE TIMING
In a nonradar environment, unless otherwise stated in the ALTRV APVL, the pilot must advise ATC if actual fix timing will be more than plus or minus 5 minutes from the planned ALTRV en route fix estimate.
4−4−2 Mission Planning
JO 7610.14A 8/7/25 7/9/26 JO 7610.14A CHG 2
Section 5. Originator Responsibilities
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.
a. 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.)
b. It must be the responsibility of the project officer to ensure receipt of the approvals specified in subparagraph a above.
c. The project officer must ensure that the ALTRV APVL and any subsequent amendments are coordinated with the aircrews.
d. 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.)
Originator Responsibilities 4−5−1
JO 7610.14A 8/7/25 3/15/07 7110.65R CHG 2 JO 7610.14A CHG 2 7/9/26
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.
e. 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.
f. 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.
g. The project officer must be responsible for informing the final approval authority of any mission delay request.
h. The project officer must ensure that aircraft commanders are briefed on the importance of maintaining planned ALTRV en route timing.
i. 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. NONOTICE 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.
a. Information concerning NOPAR missions must be withheld from specified air defense radar facilities and/or specified interceptor squadrons.
b. 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.”
4−5−2 Originator Responsibilities
Chapter 4. Altitude Reservation (ALTRV) Procedures › Section 6. Planning Approval of APREQs
Section 6. Planning Approval of APREQs
4−6−1. PLANNING/APPROVAL OF APREQs
The following separation minima must be applied in the planning and approval of ALTRVs:
a. Vertical − Standard minima specified for the area of operation.
b. Lateral − Standard minima specified for the area of operation. When a mission requires operation on a broad frontal width, separation must be provided in accordance with FAA Order JO 7110.65, Air Traffic Control, between the outer limits of such flight or formation and non-participating aircraft.
c. Longitudinal and Crossing.
1. Domestic − 30 minutes.
2. Oceanic − 60 minutes.
d. STATIONARY ALTRVs − Separate one stationary ALTRV from another stationary ALTRV by one of the following minima:
1. VERTICAL SEPARATION – Standard minima specified for the area of operation.
2. LATERAL SEPARATION − Between stationary ALTRVs, lateral separation will exist if there is no overlap of the boundary of the stationary ALTRV with the boundary of another stationary ALTRV.
3. Stationary ALTRVs are considered separated if the requested time periods do not coincide and are separated by one or more minutes.
4. You may approve ALTRVs that are separated from each other by less than the minima provided that each APREQ specifies MARSA with respect to the other conflicting ALTRV.
NOTE− The originator/agency of the ALTRV that specifies MARSA with another ALTRV is responsible for coordinating with the other originator/agency before submitting the initial request and any subsequent amendment requests.
4−6−2. MILITARY AUTHORITY ASSUMES RESPONSIBILITY FOR SEPARATION OF AIRCRAFT (MARSA)
When less than the separation in paragraph 4−6−1, Planning/Approval of APREQs, exists, MARSA must apply as follows:
a. The originator of an ALTRV APREQ must accept the responsibility for separation:
1. Between all aircraft in the ALTRV.
2. Between aircraft in the ALTRV and other aircraft or groups of aircraft utilizing the same “mission” name even though the flights originate from different air bases, division headquarters, and/or military commands.
b. When MARSA is applied between missions of different mission names, include a statement in the remarks section of the flight plan and ALTRV APREQ that includes the name(s) of the missions with which separation responsibility is accepted.
c. MARSA authorizes an ATC facility to clear a tanker to a common altitude with a receiver even though the altitude has not been processed as an ALTRV request. This information and the identification of the other aircraft must be included in the flight plan(s).
4−6−3. INFLIGHT SEPARATION
ATC facilities must provide separation in accordance with FAA Order JO 7110.65, Air Traffic Control, unless MARSA is applicable in accordance with paragraph 4−6−2, Military Authority Assumes Responsibility for Separation of Aircraft (MARSA).
Planning Approval of APREQs 4−6−1
JO 7610.14A 8/7/25
4−6−4. POSITION REPORTS
a. In a nonradar environment or when requested by the air traffic controller, the first and last aircraft in a stream formation must make position reports at each required reporting point and must indicate position in the formation.
NOTE− In Class A airspace, controllers may find it necessary to obtain information from pilots conducting certain military operations over and above that is normally required for IFR flight.
b. The cell leader must make position reports for the cell formation at each required reporting point.
NOTE− Caution should be exercised by the pilot and the controller during the departure and/or arrival phase of the ALTRV to avoid referring to the lead aircraft and succeeding aircraft as a cell unless the definition of a cell formation is met.
c. Aircraft in an ALTRV, other than in a stream or cell formation, must make position reports as individual aircraft or flight plan formation.
d. ATC facilities may authorize communications out/reduced communications procedures in lieu of radio position reporting if required by military operations and prior coordination has been accomplished with affected ATC facilities.
4−6−5. USE OF AIRSPACE THROUGH ALTRV
Approval of airspace for an ALTRV must not preclude ATC from using such airspace, provided that separation is applied in accordance with FAA Order JO 7110.65, Air Traffic Control, between nonparticipating aircraft and aircraft within the ALTRV.
Planning Approval of APREQs 4−6−2
JO 7610.14A 8/7/25 7/9/26 JO 7610.14A CHG 2
Chapter 4. Altitude Reservation (ALTRV) Procedures › Section 7. Special/Emergency ALTRVs
Section 7. Special/Emergency ALTRVs
4−7−1. INTERNATIONAL PRESIDENTIAL FLIGHTS
When requested, ALTRVs must be provided for aircraft transporting the President or the Vice President when conducting international flights. Headquarters USAF will authorize a Class One order of precedence for those flights.
a. The appropriate military authority will provide CARF with detailed flight plan information, both to the destination and return, as far in advance as possible.
b. CARF must arrange for ALTRVs for Presidential and Vice Presidential rescue support aircraft.
4−7−2. PROCESSING WAIVERS
a. ALTRV requests which do not qualify under the provisions of this section and cannot otherwise be accomplished will be handled on an individual basis.
b. Such ALTRV requests must be forwarded, with accompanying justification, to the David J. Hurley Air Traffic Control System Command Center, ATTN: Central Altitude Reservation Function, 3701 Macintosh Drive, Warrenton, Virginia 20187. A waiver will be issued by CARF if deemed appropriate.
c. All originating units must process such requests through channels to the appropriate Command Headquarters for transmittal to CARF.
4−7−3. EMERGENCY ALTITUDE RESERVATIONS
CARF or an ARTCC/CCF/HCF may approve a request for an emergency ALTRV if the safety of life or property is threatened. Operations such as search and rescue, hurricane evacuation, or mass air evacuation may be considered in this category. When an ARTCC/CCF/HCF approves an ALTRV under this paragraph, the following actions must be taken:
a. The facility must advise CARF and other concerned ARTCC/CCF/HCFs of the approved ALTRV in detail by the most expedient means.
b. Upon receipt of such notification, CARF must take immediate action to preclude possible conflict between ALTRVs previously approved by CARF and the emergency ALTRV.
Special/Emergency ALTRVs 4−7−1
Chapter 4. Altitude Reservation (ALTRV) Procedures › Section 8. Altitude Reservation NOTAMs
JO 7610.14A 8/7/25 7/9/26 JO 7610.14A CHG 2
Section 8. Altitude Reservation NOTAMs
4−8−1. CRITERIA
The issuance of an altitude reservation NOTAM, except as provided in subparagraph 4−8−2c, involving the U.S. control area/flight information region (CTA/FIR) must be governed by the following procedures:
a. Issue an altitude reservation NOTAM for:
1. All Stationary ALTRVs.
NOTE− CARF, ARTCC, CCF, or HCF (whoever is the final approval authority) must issue the NOTAM.
EXAMPLE− ZNY AIRSPACE DCC ANTARES NG−13 STNR ALT RESERVATION WI AN AREA DEFINED AS 3619N7240W TO 3537N7134W TO 3517N7214W TO 3536N7240W TO POINT OF ORIGIN AND WITHIN AN AREA DEFINED AS 2851N6257W TO 3056N6500W TO 2959N6635W TO 2740N6421W TO POINT OF ORIGIN SFC−UNL 2002142015−2002142215
2. Selected Moving ALTRVs, whenever a portion of the ALTRV includes air refueling and/or other unusual activity below FL 180, or when the activity covers a broad frontal width.
b. Describe the area which is in use and the duration of the ALTRV. Reference must not be made to the type of activity within the ALTRV unless the originator has agreed to the publication of this information.
EXAMPLE− ZNY AIRSPACE DCC ON CORONET EAST 037A LEG 3 MIL ACT ALONG THE ROUTE FM 4200N4000W TO 4200N4330W TO 4200N4500W TO 4200N5000W TO 4200N5300W TO 4200N5500W TO 4200N6000W TO 4125N6500W TO DOVEY TO ACK 15000FT−FL210 2002121354−2002122138
4−8−2. FORMULATION AND DISSEMINATION
a. The final approval authority, CARF or the appropriate ARTCC/CCF/HCF, is responsible for the formulation and dissemination of appropriate NOTAMs for those ALTRVs which they have approved in their area of jurisdiction.
b. Coordination must be effected between adjacent ARTCC/CCF/HCFs if it will permit consolidation of NOTAM information as prescribed above for the issuance of a joint altitude reservation NOTAM.
c. Altitude reservation NOTAMs must not be issued under the following conditions:
1. If the originator of an ALTRV request specifies “Secure Handling” by assigning one of the following classifications to the request:
(a) Confidential.
(b) Secret.
(c) Top Secret.
2. The mission is a No−Notice mission, except that appropriate altitude reservation NOTAMs may be issued after specific instructions have been received from the originator of the mission.
3. On portions of an ALTRV which are conducted in accordance with published activities; e.g., Military Training Routes, etc.
Altitude Reservation NOTAMs 4−8−1
Chapter 4. Altitude Reservation (ALTRV) Procedures › Section 9. Space Support Operations
Section 9. Space Support Operations
4−9−1. PURPOSE
This section prescribes policy, and administrative procedures pertaining to launch notification in support of future space missions.
4−9−2. POLICY
FAA NAS Operations, Space Operations (AJR−1800) will support all NASA, DoD and commercial space operations in accordance with written agreements (i.e., letters of agreement) and regulations.
REFERENCE− FAA Order JO 7400.2, Procedures for Handling Airspace Matters.
4−9−3. CLASSIFIED SPACE LAUNCH/REENTRY NOTIFICATION
a. FAA recognizes that the military has a continuing requirement for periodic space launches/reentry that are classified in nature due to payload and/or mission.
b. Classified notification procedures must be developed to ensure, to the extent possible, minimal impact on aircraft operations conducted in affected airspace.
Space Support Operations 4−9−1
Chapter 4. Altitude Reservation (ALTRV) Procedures › Section 10.
JO 7610.14A 8/7/25 7/9/26 JO 7610.14A CHG 2
Section 10. Altitude Reservation Approval Request
(ALTRV APREQ), Format, and Amendments
4−10−1. ALTRV APREQs
The originator must file an ALTRV APREQ with CARF in accordance with the instructions contained in this order unless specific guidance or instruction has been pre−coordinated with CARF/ARTCC/CCF/HCF.
a. Whenever possible, ALTRV APREQs should be sent unclassified.
b. If sent classified or encrypt for transmission only (EFTO), advise CARF of the earliest time the message may be declassified or EFTO may be dropped; i.e., 24 hours prior to departure, upon departure, etc.). Classified or EFTO missions cannot be coordinated with international facilities or agencies unless written permission is given by the unit or command that files the APREQ. Advise CARF of the earliest declassification time in item G of APREQ.
4−10−2. FORMAT
In order to accomplish timely data processing by the CARF automated system, ALTRV APREQs must be properly formatted prior to submission to CARF, or other approval authority, utilizing key phrases outlined in this paragraph and Section 10, Flight Path Format Components. Indicate the following items on all ALTRV APREQ messages:
NOTE− N/A may be used in a stationary ALTRV for items A thru C, E thru F, when applicable.
a. Heading: “ALTRV APREQ,” the mission name, and a slash “/” followed by the mission class. ALTRV APREQs filed in support of another ALTRV must file the same mission name and mission class, followed by the word “SUPPORT.”
EXAMPLE− ALTRV APREQ CORONET WEST 450A/7 ALTRV APREQ FULL UP 95−4/8 ALTRV APREQ FULL UP 95−4/8 SUPPORT
Continue reading ↓ 120 of 450 passages shown