Section 10. Altitude Reservation Approval Request (ALTRV APREQ), Format, and Amendments
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/CERAP/HCF.
- Whenever possible, ALTRV APREQs should be sent unclassified.
- 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.
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.
- 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
- Item A, Call Sign(s): “A” followed by the call sign(s) of all aircraft which will depart together from the location specified in item C. Call signs must not exceed seven alphanumeric characters in length; the tactical call sign is a pronounceable word of 3 to 6 alphabetical characters followed by a 4, 3, 2, or 1 digit number. When there are multiple flights with the same tactical call sign, combine the numbers portion by separating consecutive series with a dash and individual numbers with a comma.
NOTE-
Do not include the call signs of aircraft which file individual flight plans to join the ALTRV en route. These will be noted in the Item D or G.
EXAMPLE-
A. BONE11-13
(This indicates BONE11, BONE12 and BONE13).
A. HAPPY32,34
(This indicates HAPPY32 and HAPPY34).
A. PINE80,81 MOOSE31-33
(This indicates PINE80, PINE81, MOOSE31, MOOSE32, MOOSE33).
- Item B, Number and Type of Aircraft: “B” followed by the number of aircraft if more than one; heavy indicator “H,” if appropriate; type of aircraft; and equipment suffix code. The items should be specified in the same order that the call signs appear in Item A, and the number of aircraft should agree with the number of call signs.
EXAMPLE-
B. 3HB52/R
(3 is the number of aircraft, H indicates heavy, B52 is the type of aircraft, and R is the equipment suffix code).
- Item C, Point of Departure: “C” followed by the four-letter ICAO location identifier. When the point of departure is classified, indicate “ZZZZ.” Do not include the departure point of aircraft that file individual flight plans which join the ALTRV en route.
EXAMPLE-
C. KJAX
C. PANC
- Item D, Route of Flight, Elapsed Times, and Altitudes: “D” followed by the route of flight, elapsed times between segments on the routes, and the altitude to be flown for each segment (fix-time-event sequence).
- Route of Flight: The route of flight will include events or actions within the route and may be composed of any number of flight paths as defined in Section 11, Flight Path Format Components. Route of flight for operations above FL 180 should be defined in relation to established high altitude navigation aids only. The route of flight segment for a stationary ALTRV must adhere to the guidelines outlined in subparagraphs 4-11-4a-e.
NOTE-
When tanker aircraft do not depart with the ALTRV but join up at a later point, provide the following information, at the point at which they join the ALTRV: “JOIN”; the call sign; the number, type and equipment suffix, as in subparagraph c above; “IFPFP”; and the point of departure.
EXAMPLE-
[JOIN JOE53 KC10/R IFPFP PHIK]
- Elapsed times: Times should be specified in four digits which express hours and minutes. Indicate cumulative time elapsed in one of the following manners:
- When timing begins upon departure, from the point of departure.
EXAMPLE-
0012 (This indicates 12 minutes from the time of departure).
0509 (This indicates 5 hours and 9 minutes from the time of departure).
- When timing begins over the first fix of a partial route, indicate the beginning point as the first fix in Item D using the time elapsed from the departure point.
- Altitudes: Indicate the altitude in three digits expressed in hundreds of feet; “SURFACE” may be used to indicate altitudes which extend from the surface of controlled airspace. Precede the altitude with “FL” for altitudes of 18,000 feet or above. Insert “B” between the lower and upper limits of a block altitude.
NOTE-
Flight levels may be used in oceanic airspace below 18,000 feet if required to set altimeter to 29.92.
EXAMPLE-
090 (indicates 9,000 feet)
FL190 (indicates Flight Level 190)
FL240B260 (indicates block altitudes of FL240 through FL260).
- Item E. Destination: “E” followed by the four-letter ICAO location identifier.
- When all aircraft proceed to the same destination, no additional information is needed.
- When there are multiple destinations, specify the call sign and location identifier for the destination for all aircraft that remain in the ALTRV at the ALTRV end point as follows:
- Call sign.
- Location identifier for the destination.
- When the destination is classified, indicate “ZZZZ”; do not include an elapsed time.
EXAMPLE-
E. PHNL
E. CLAN80,81 PHNL ZESTY12 PHNG
E. ZZZZ
- Item F, Departure Information: “F” followed by “ETD” and:
- When timing begins upon departure, indicate the date time group of the estimated time of departure as follows:
- If a single cell is departing, indicate the day of the month and UTC time, expressed in six digits, and the month and year of departure.
- If more than one cell is departing, indicate the call sign for each cell, in the order of departure, followed by the date time group.
- For the first cell, specify the date time group as described in subparagraph (a) above.
- For successive cells, indicate only the day of the month and UTC time, expressed in six digits.
- Interval Between Aircraft (ADMIS): The ADMIS should be specified for any group of more than one aircraft. Indicate one of the following:
- “ADMIS” followed by two digits which indicate the number of minutes between departing aircraft in the group.
- “ADMIS” followed by two digits and “SEC” to indicate the number of seconds between departing aircraft in the group.
- “FRMN” to indicate that departing aircraft are considered as one and will depart in less than 30 second intervals.
- “MITO” to indicate the minimum takeoff interval between departing aircraft in the group.
- AVANA Time: “AVANA” followed by the date time group, expressed in six digits.
EXAMPLE-
F. ETD 020030 JAN 2005 ADMIS 01 AVANA
02013
F. ETD BONE11-16 020030 JAN 2005
ADMIS 30 SEC
BONE17,18 020100 FRMN
BONE19 020130 AVANA 020230
F. ETD SLIP31-36 151000 FEB 2005 ADMIS MITO AVANA 151100
- Item G, Remarks: “G” followed by:
- “TAS.” Include the airspeed in three digits and “KTS.” Indicate if cruise and air refueling speeds are different.
- “PROJECT OFFICER.” Include the name and telephone number of the project officer.
- “ALTERNATE PROJECT OFFICER.” Include the name and telephone number of the alternate project officer.
- “ADDITIONAL INFORMATION.” Include any remarks pertaining to the execution of the mission, for example:
NOTE-
A MARSA statement must be included if the aircraft will fly less than approved separation.
- NOPAR
- EA and chaff information, including authorization number, if applicable. (See subparagraph4-5-4a5 in this chapter.)
- IFPFP routings. All individual flight plan information from this point (IFPFP), including routing and altitude information, to the BEGIN ALTRV point and from the ALTRV termination point. Also, location, routing (IFPFP), and procedures for airborne spares to drop out/exit the ALTRV, etc.
- All special use airspace and ATC assigned airspace (ATCAA) for which approval has been obtained.
- Nonstandard Formation information in accordance with subparagraph 7-3-3b in this order; and FAA Order JO 7110.65, Air Traffic Control, paragraph 5-5-8, which addresses additional separation for formation flights.
- “ARTCC.” List the names of all ARTCC/CERAP/HCF/ATC facilities which will be concerned with the ALTRV.
- “REQUEST COPY OF ALTRV APVL BE SENT TO.” (Optional) List any additional parties that need a copy of the ALTRV APREQ. (See subparagraph 4-2-2a in this chapter.)
EXAMPLE-
G. TAS: 430KTS CRUISE/AIRFL
G. TAS: 440KTS CRUISE 410KTS AIRFL
PROJECT OFFICER: CAPT SMITH DSN 555-5555/COMM 111-555-1111
ALTERNATE PROJECT OFFICER: CAPT JONES DSN
555-5556/COMM 111-555-2222 ADDITIONAL INFORMATION:
MARSA ALL BUSY LEADER OSCAR AIRCRAFT. ARTCC CONCERNED:
ZNY ZDC AR-E EUCARF REQUEST COPY OF ALTRV APVL BE SENT TO
438MAW MCGUIRE AFB NJ//DO
When necessary to amend an ALTRV APREQ, indicate the following:
- Heading: “Amendment to,” followed by the heading information as specified in the original APREQ.
- Date Time Group: “ROMES” (Reference our message) followed by the date time group of the original APREQ message.
- Estimate Time of Departure: “ETD” followed by the date time group specified in Item F on the original APREQ.
- Amendment(s): “AMEND” followed by the item(s) to be amended and the amendment; indicate the specific item on the original APREQ; such as, Item A, Item B, etc.
- Ending: “ALL ELSE REMAINS THE SAME.”
EXAMPLE-
AMENDMENT TO ALTRV APREQ SHARP
SHOOTER 97-1/8
ROMES 111012 ETD 191500 FEB 1997
AMEND ITEM A AND B
ITEM A RAVEN01-07
ITEM B 7EF111/R
ALL ELSE REMAINS THE SAME