Section 5. IR Coordination

1. ESTABLISHING OR REVISING ROUTES

1. Military units having a requirement to establish or revise a route must have that requirement validated by the appropriate military major/type command. As a part of the validation process, a determination must be made that other alternatives have been explored (e.g., use of existing MOAs, restricted areas, or other routes). This determination must be documented in writing and become a part of the route proposal.
2. All route requests or route amendments developed by the originating unit must be submitted on FAA Form 7110-4 (see FIG 6-5-2 and FIG 6-5-3). A letter of transmittal must contain sufficient information to allow each reviewing authority to adequately understand and evaluate the proposal/revision. For route revisions, complete FAA Form 7110-4 with only the changed/new data, route designator, and originating unit. Check the “modified” block.
3. All route proposals must be illustrated on a current sectional chart (not required for revisions that do not effect route alignment) with routes depicted as follows:

1. Routes must be depicted by lines defining the route widths.
2. Altitudes must be depicted along each route segment and expressed in hundreds of feet AGL or MSL as appropriate. Altitude blocks or ranges must be indicated by separating the altitudes with a “B” for blocks or a dash “-” for ranges. (Refer to paragraph 6-4-3, Altitudes.)
3. Each point/fix, including turn points, must be identified in degrees, minutes, and seconds to the nearest tenth of a second, by sequential alphabetical lettering in accordance with the direction of flight.

1. The originating unit must coordinate the route proposal with other affected military organizations.
2. The ARTCC/CERAP/HCF in whose area the route originates must be the focal point and coordinate with other ATC facilities.
3. A listing of all personnel and organizations coordinated with must become a part of the route proposal.
4. Once the ARTCC/CERAP/HCF has concurred with an IR proposal, subsequent changes must be re-coordinated with the ARTCC/CERAP/HCF and documented regardless of the level at which the change was made.
5. Prior to submission for publication, the military must conduct an operational flight evaluation of the entire route to ensure compatibility with obstacle clearance, navigation, communication, and special restriction requirements. Coordination with the appropriate ATC facilities is required.
6. Once ARTCC/CERAP/HCF proponent agreement has been reached, proposals must be forwarded to the appropriate military major/type command headquarters for review and environmental certification.
7. If agreement between the proponent and the ATC facilities involved cannot be achieved after consideration of all feasible alternatives and compromises, the proponent must request assistance from the appropriate military headquarters and the FAA Service Area military representative. A resolution must then be sought at a meeting attended by the proponent, the ATC facilities involved, military major/type command headquarters representatives, the FAA Service Area, and the military representatives. Should a resolution not be achieved, the military headquarters representatives may authorize the proponent to proceed with processing of a VR proposal in lieu of the disagreed IR.
8. FAA Service Area Review action: IR proposals must be forwarded to the military representative at the FAA Service Area in which the routes originate. The IR proposal(s) must include copies of all environmental documentation supporting the proposal and the major/type command headquarters' environmental certification addressed in paragraph 6-5-1.i. above. The military representative must review the proposals for compliance with this criteria, coordinate with other military service representatives, and then submit them to the FAA Service Area office.
9. The FAA Service Area must:

1. Coordinate all proposals with other interested FAA Service Units.
2. Determine when proposals will increase the burden on civil users of the navigable airspace, and coordinate those proposals with the appropriate civil aviation user groups.
3. Approve or disapprove the proposal and notify the Service Area military representative, in writing, within 45 days of receipt of the original proposal.

1. The FAA Service Area office is the final approval authority for all IR proposals/revisions.
2. The block diagram below represents the normal coordination flow of a proposed IR.

1. PUBLICATION

1. The FAA Service Area office in whose area the route originates must submit the approved FAA Form 7110-4 containing the route descriptive data to FAA Aeronautical Information Services (AIS), Aeronautical Data website at https://www.faa.gov/air_traffic/flight_info/aeronav/aero_data/, at least 58 days prior to the requested/required airspace effective date. Send a copy to the appropriate Service Area military representative.

1. AIS must issue the official, complete route description via the National Flight Data Digest (NFDD). It must be published in the same format as FAA Form 7110-4.
2. The DoD FLIP Area Planning booklets, AP/1B or AP/3, as appropriate, must be the official source of MTR descriptions for military users. It must be published in the same format as FAA Form 7110-4.

1. ARTCC/CERAP/HCFs must review IR data published in the NFDD for accuracy and inform the appropriate FAA Service Area office whenever a disparity exists between that which was agreed to and that which was published.
2. The military is responsible for submitting IR data for publication in the DoD FLIP AP/1B booklet in accordance with DoD FLIP GP, Chapter 11. Military originating activities must review IR data published in the DoD FLIP AP/1B and AP/3 booklets and charts for accuracy and inform the appropriate Service Area military representative whenever a disparity exists between that which was submitted and that which was published.
3. Military originating activities and ARTCC/CERAP/HCFs must ensure that IR data published in the DoD FLIP AP/1B and AP/3 booklets correlate with provisions contained in the letters of agreement governing the use of the route.

1. EFFECTIVE DATE

1. New routes are effective upon the Aeronautical Information Regulation and Control (AIRAC) date published in the National Flight Data Digest (NFDD) and the DoD FLIP Area Planning booklets, AP/1B or AP/3, as appropriate.
2. Revisions to existing routes are effective upon the AIRAC date published in the NFDD and the DoD FLIP Area Planning booklets, AP/1B or AP/3, and issued as a Flight Data Center (FDC) NOTAM.