View source for 7110.65:Chapter 9

<html>
<head>
<meta charset="UTF-8">
<title>Chapter 9. Special Flights</title>
<link href="/assets/711065/wiki.css" rel="stylesheet" type="text/css">
</head>

<body>
<main id="chapters">
<article>
<h1>Chapter 9. Special Flights</h1>
<section id="s1">
<h2><a href="#chapters">Section 1. General</a></h2>

<h3 id="9-1-1"><a href="#s1">9-1-1. GENERAL</a></h3>

<p>Provide aircraft engaged in the flight inspection of NAVAIDs with maximum assistance. Unless otherwise agreed to, maintain direct contact with the pilot and exchange information regarding known traffic in the area and his/her intentions.</p>
<ul class="note">
	<li>NOTE:</li>
	<li>1. Many flight inspections are accomplished using automatic recording equipment, and an uninterrupted flight is necessary for successful completion of the mission. The workload for the limited number of aircraft engaged in these activities requires strict adherence to a schedule.</li>
	<li>2. Flight inspection operations which require special participation of ground personnel, specific communications, or radar operation capabilities are considered to require special handling. These flights are coordinated with appropriate facilities before departure.</li>
</ul>
<ul class="reference">
	<li>REFERENCE</li>
	<li>FAA Order 8200.1, United States Standard Flight Inspection Manual.</li>
	<li>FAA Order 8240.41, Flight Inspection/Air Traffic On-Site Coordination Requirements.</li>
</ul>


<h3 id="9-1-2"><a href="#s1">9-1-2. SPECIAL HANDLING</a></h3>

<ol>
	<li>Clear the aircraft according to pilot request as soon as practicable. Do not ask the pilot to deviate from his/her planned action except to preclude an emergency situation.
		<ul class="reference">
			<li>REFERENCE</li>
			<li>FAA Order 8240.41, Flight Inspection/Air Traffic On-Site Coordination Requirements, Appendix 1, describes certain flight inspection maneuvers in detail.</li>
		</ul></li>
	<li>Issue radar advisories to the flight inspection aircraft where adequate coverage exists and to the extent permitted by workload.</li>
	<li>Suggest flight path adjustments, as required, for any aircraft which will enter or penetrate an area in which a flight inspection function is being performed.</li>
	<li>Provide special handling, as required, to FAA aircraft conducting flight inspections using the call sign “Flight Check.” The call sign “Flight Check (Nr) recorded” indicates automated flight inspections are in progress in terminal areas.</li>
</ol>
<ul class="note">
	<li>NOTE:</li>
	<li>1. FAA flight inspection aircraft will file flight plans using the call sign “FLIGHT CHECK” during flight inspections or when inbound to conduct flight inspections. Flight plan remarks may indicate type NAVAID inspection to be accomplished; e.g. “FC OKC P.”</li>
	<li>2. Authorized non-FAA Service Providers conducting Flight Validation activities use the call sign “FLIGHT VAL.” Although these activities are similar to Flight Inspection activities, no additional priority is granted with this call sign.</li>
</ul>

<h3 id="9-1-3"><a href="#s1">9-1-3. FLIGHT CHECK AIRCRAFT</a></h3>

<ol>
	<li>Provide special handling, as required, to expedite flight inspection of NAVAIDs and RADAR by flight check aircraft.
		<p class="note">NOTE: Certain flight inspection maneuvers require operations in close proximity to the surface. These maneuvers can only be performed during daylight visual meteorological conditions. Preplanned automatic flight places the following limitations on the capability of the pilot to adhere to normal ATC clearances:</p>
		<ol>
			<li>Route of flight - orbital from 6 nautical miles to a maximum of 40 nautical miles from the facility depending on the type of inspection. During commissioning flight checks all SIDs, STARs, airways, DME fixes, and approaches must be flown.</li>
			<li>Altitude assignment - from 1,000 feet above the antenna site up to the minimum en route altitude (MEA).</li>
		</ol>
		<ul class="reference">
			<li>REFERENCE</li>
			<li><a href="/wiki/7110.65:Chapter_2#2-1-4">FAA Order JO 7110.65, Para 2-1-4, Operational Priority.</a></li>
			<li>FAA Order 8240.41, Flight Inspection/Air Traffic On-Site Coordination Requirements, Appendix 1, describes certain flight inspection maneuvers in detail.</li>
		</ul></li>
	<li>Avoid changes in the route or altitude from that filed by the pilot in the initial flight plan.</li>
	<li>Do not impose air traffic control delays in the flight except to preclude emergency situations.</li>
	<li>Do not change the previously assigned discrete beacon code of special radar accuracy flight check aircraft.
	<ul class="reference">
		<li>REFERENCE</li>
		<li>FAA Order JO 7210.3, Para 7-1-2, Special Radar Accuracy Checks.</li>
		<li>FAA Order JO 7210.3, Para 10-5-4, ASR Performance Checks.</li>
	</ul></li>
</ol>

</section>

<section id="s2">
<h2><a href="#chapters">Section 2. Special Operations</a></h2>

<h3 id="9-2-1"><a href="#s2">9-2-1. AIRCRAFT CARRYING DANGEROUS MATERIALS</a></h3>

<ol>
	<li>Provide the following special handling to military aircraft or military contracted aircraft carrying dangerous materials when:
		<ol>
			<li>The words “dangerous cargo,” or “inert devices,” or both are contained in the remarks section of the filed flight plan, or
				<ul class="note">
					<li>NOTE:</li>
					<li>1. Certain types of military flights carrying dangerous materials require strict adherence to military regulations and flight planning along carefully selected routes. These flights must avoid heavily populated areas.</li>
					<li>2. “Inert devices” are devices containing no dangerous materials but closely resembling nuclear or explosive items that are classified as dangerous and could be easily mistaken for their dangerous counterparts.</li>
				</ul></li>
			<li>The pilot uses these words in radio communication.</li>
		</ol></li>
	<li>If it becomes necessary to issue a clearance to amend the route/altitude, advise the pilot:
		<ol>
			<li>Of the proposed change, and</li>
			<li>The amount of delay to expect if it is necessary to maintain the present route/altitude.</li>
		</ol></li>
	<li>When it becomes necessary for the pilot to refuse a clearance amending his/her route/altitude, he/she will advise if the traffic delay is acceptable or if an alternate route/altitude is desired. In such cases, offer all possible assistance.</li>
	<li>When the aircraft is provided an en route descent, do not vector the aircraft from the planned route unless the pilot concurs.</li>
	<li>Use special patterns and routings in areas where they have been developed for these flights. If special patterns and routings have not been developed, employ normal procedures.</li>
</ol>

<h3 id="9-2-2"><a href="#s2">9-2-2. CELESTIAL NAVIGATION TRAINING</a></h3>

<p><span class="typeheader">EN ROUTE</span></p>
<ol>
	<li>Approve flight plans specifying celestial navigation only when it is requested for USAF or USN aircraft.
		<p class="note">NOTE: An ATC clearance must be obtained by the pilot before discontinuing conventional navigation to begin celestial navigation training. The pilot will advise when discontinuing celestial navigation and resuming conventional navigation. Celestial navigation training will be conducted within 30 NM of the route centerline specified in the en route clearance unless otherwise authorized by ATC. During celestial navigation training, the pilot will advise ATC before initiating any heading changes which exceed 20 degrees.</p></li>
	<li>Within conterminous U.S. airspace, limit celestial navigation training to transponder-equipped aircraft within areas of ARTCC radar coverage.</li>
	<li>Prior to control transfer, ensure that the receiving controller is informed of the nature of the celestial navigation training leg.</li>
</ol>
<ul class="reference">
	<li>REFERENCE</li>
	<li><a href="/wiki/7110.65:Chapter_2#2-2-6">FAA Order JO 7110.65, Para 2-2-6, IFR Flight Progress Data.</a></li>
</ul>

<h3 id="9-2-3"><a href="#s2">9-2-3. DEPARTMENT OF ENERGY (DOE) SPECIAL FLIGHTS</a></h3>

<ol>
	<li>Provide notification of possible route or altitude changes as far in advance as possible for “RAC” flights. The pilot will indicate if the proposed change is acceptable or if alternate routing or altitude will be requested.
		<p class="note">NOTE: DOE contracts for civil pilots to operate public aircraft to transport radioactive or high explosive materials within the conterminous U.S. These flights operate on an IFR flight plan but principally during daylight hours and VFR conditions. These flights require flight along carefully selected routes and, in some instances, pilots will refuse clearances that require reroute or altitude changes that would derogate their objective.</p></li>
	<li><span class="typeheader">EN ROUTE</span>. Approve pilot requests to leave center frequency for operational purposes as traffic conditions permit.</li>
	<li>Notify a supervisor in the event any of the following occurs with “RAC” aircraft:
		<ol>
			<li>Loss of radio contact.</li>
			<li>Loss of radar contact.</li>
			<li>The flight is overdue at the destination.</li>
		</ol></li>
	<li>If you receive information that a “RAC” aircraft is involved in an accident, secure as much information as possible, particularly with respect to location, and immediately notify the ARTCC supervisory traffic management coordinator-in-charge.
		<p class="note">NOTE: There is a possibility of an explosive or radiation hazard of an “RAC” aircraft involved in an accident.</p></li>
</ol>

<h3 id="9-2-4"><a href="#s2">9-2-4. EXPERIMENTAL AIRCRAFT OPERATIONS</a></h3>

<ol>
	<li>When notified that an experimental aircraft requires special handling:
		<p class="note">NOTE: 14 CFR Section 91.319(d)(3) requires that each person operating an aircraft with an experimental certificate must notify the control tower of the experimental nature of the aircraft when operating into or out of airports with operating control towers.</p></li>
		<ol>
			<li>Clear the aircraft according to pilot requests as traffic permits and if not contrary to ATC procedures.</li>
			<li>Once approved, do not ask the pilot to deviate from a planned action except to preclude an emergency situation.</li>
		</ol>
	<li>At locations where volume or complexity of experimental aircraft operations warrant, a letter of agreement may be consummated between the facility and operator.</li>
</ol>

<h3 id="9-2-5"><a href="#s2">9-2-5. FAA RESEARCH AND DEVELOPMENT FLIGHTS</a></h3>

<p>When coordinated in advance and traffic permits, approve requests for special flight procedures from aircraft participating in FAA research and development test activities. These special procedures must be applied to participating aircraft/vehicles.</p>
<p class="note">NOTE: Special flight procedures for FAA research and development test activities must be approved by the facility air traffic manager prior to their use.</p>
<ul class="reference">
	<li>REFERENCE</li>
	<li>FAA Order JO 7210.3, Para 5-2-4, Research and Development Flights.</li>
</ul>

<h3 id="9-2-6"><a href="#s2">9-2-6. FLYNET</a></h3>

<p>Provide expeditious handling for U.S. Government, civil or military aircraft using the code name “FLYNET.” Relay the code name as an element in the remarks position of the flight plan.</p>
<p class="note">NOTE: The code name “FLYNET” indicates that an aircraft is transporting a nuclear emergency team or a disaster control team to the location of a potential or actual nuclear accident or an accident involving chemical agents or hazardous materials. It is in the public interest that they reach their destination as rapidly as possible.</p>
<ul class="reference">
	<li>REFERENCE</li>
	<li><a href="/wiki/7110.65:Chapter_2#2-1-4">FAA Order JO 7110.65, Para 2-1-4, Operational Priority.</a></li>
	<li>FAA Order JO 7610.4, Para 12-4-1, “FLYNET” Flights, Nuclear Emergency Teams.</li>
</ul>

<h3 id="9-2-7"><a href="#s2">9-2-7. IFR MILITARY TRAINING ROUTES</a></h3>

<ol>
	<li>Except for aircraft operating in the same altitude reservation, clear aircraft into an MTR provided separation will be applied between successive aircraft unless otherwise covered in a letter of agreement between the military scheduling activity and the concerned ATC facility.
		<ul class="phraseology">
			<li>PHRASEOLOGY</li>
			<li>CLEARED INTO IR (designator). MAINTAIN (altitude),</li>
			<li>or</li>
			<li>MAINTAIN IR (designator) ALTITUDE(S),</li>
			<li>or</li>
			<li>MAINTAIN AT OR BELOW (altitude),</li>
			<li>or</li>
			<li>CRUISE (altitude),</li>
			<li>and if required,</li>
			<li>CROSS (fix) AT OR LATER THAN (time).</li>
		</ul></li>
	<li>Unless otherwise covered in a letter of agreement between the military scheduling activity and the concerned FAA facility, clear aircraft to exit an MTR.
		<ul class="phraseology">
			<li>PHRASEOLOGY</li>
			<li>CLEARED TO (destination/clearance limit) FROM IR (designator/exit fix) VIA (route).</li>
			<li>MAINTAIN (altitude).</li>
		</ul></li>
	<li>If the provisions of subpara a above cannot be accomplished, MTRs may be designated for MARSA operations. To preclude an inadvertent compromise of MARSA standards by ATC, appropriate MARSA application for such routes must be covered in a letter of agreement with the military scheduling activity. Establish separation between aircraft as soon as practicable after operation on the designated MARSA route is ended.
		<p class="note">NOTE: For designated MARSA routes, the military assumes responsibility for separation for MTR aircraft that have passed the primary/alternate entry fix until separation is established by ATC after operations on the MARSA route are completed.</p></li>
	<li>The lateral airspace to be protected along an MTR is the designated width of the route.</li>
	<li>Prior to an aircraft entering an MTR, request the pilot’s estimate for the route’s exit/alternate exit fix, the pilot’s requested altitude after exiting and, if applicable, the number of reentries on a Strategic Training Range (STR).
		<ul class="phraseology">
			<li>PHRASEOLOGY</li>
			<li>(Call sign) VERIFY YOUR EXIT FIX ESTIMATE AND REQUESTED ALTITUDE AFTER EXIT,</li>
			<li>and if applicable,</li>
			<li>THE NUMBER OF REENTRIES.</li>
		</ul></li>
	<li>Forward estimates for exit/alternate exit fixes, requested altitude after exit, and, if applicable, the number of reentries on the STR.</li>
	<li>Apply the procedures of para 6-1-2, Nonreceipt of Position Report, based upon the pilot’s estimate for the route exit fix.</li>
	<li>Clearance may be issued to amend or restrict operations on a route for ATC considerations. Where a route has been designated MARSA in accordance with subpara c, ATC must not amend or restrict operations in such a manner as to compromise MARSA provisions.
		<p class="note">NOTE: When MARSA is provided through route scheduling and circumstances prevent the pilot from entering the route within established time limits, it must be the responsibility of the pilot to inform the ATC facility and advise his/her intentions.</p></li>
	<li>If an aircraft on an IR experiences a two-way radio communications failure and you are unable to determine if the aircraft is proceeding VFR in accordance with <a href="https://www.law.cornell.edu/cfr/text/14/91.185" target="_blank">14 CFR Section 91.185(b)</a> or the aircraft has not been positively radar identified:
<ol>
			<li>Provide separation to the destination airport based on the aircraft complying with the following:
				<ol>
					<li>(a) Maintain to the exit/alternate exit fix the higher of the following altitudes:
						<ol>
							<li>(1) The minimum IFR altitude for each of the remaining route segment(s) remaining on the route.</li>
							<li>(2) The highest altitude assigned in the last ATC clearance.</li>
						</ol></li>
					<li>(b) Depart the exit/alternate exit fix at the appropriate altitude specified in subpara (a) above, then climb/descend to the altitude filed in the flight plan for the remainder of the flight, or
						<p class="note">NOTE: In the event of a two-way communications failure, ATC will be based on the following anticipated pilot action at the exit fix. Unless otherwise covered in a letter of agreement, and if the pilot is unable to comply with the VFR provisions of 14 CFR Section 91.185/FLIP IFR Supplement, the pilot will exercise his/her emergency authority, squawk transponder Code 7700, depart the exit/alternate exit fix and climb/descend (continuing to squawk 7700) to the altitude filed in the flight plan. Subsequent transponder operations will be in accordance with para 10-4-4, Communications Failure. Air traffic controller action from the exit fix is as prescribed in para 10-1-1, Emergency Determinations.</p></li>
					<li>(c) Proceed in accordance with the lost communication procedure contained in letters of agreement.</li>
				</ol></li>
			<li>Continue to monitor the last ATC assigned discrete code.
				<p class="note">NOTE: Pilots who experience a two-way radio failure will adjust their transponder to Code 7700 during climb/descent to altitude filed for the next leg of the flight plan; then change to Code 7600 for a period of 15 minutes. At the end of each 15-minute period, he/she will squawk 7700 for a period of 1 minute; all other times he/she will squawk 7600.</p></li>
		</ol></li>
	<li>Impose delays, if needed, to eliminate conflict with nonparticipating IFR aircraft when necessary to preclude denial of IR usage. Advise the pilot of the expected length and reason for delay.</li>
</ol>

<h3 id="9-2-8"><a href="#s2">9-2-8. INTERCEPTOR OPERATIONS</a></h3>

<p>Provide maximum assistance to expedite the movement of interceptor aircraft on active air defense (scrambles) missions until the unknown aircraft is identified in accordance with the policies and procedures published in FAAO JO 7610.4, Special Operations.</p>
<p class="note">NOTE: The FAA and the military have mutually agreed to the implementation of policies and procedures for control of air defense interceptor operations. Effective coordination and cooperation between FAA and the military at all levels are essential if policy objectives are to be met.</p>
<ol>
	<li>The ADCF initiating the SCRAMBLE must identify the mission as an active air defense mission.</li>
	<li>ATC services must be used for active air defense missions insofar as the circumstances and situation permits.</li>
	<li>Upon request, the ATC facility must expedite transfer of the control jurisdiction of the interceptors to the requesting ADCF.</li>
</ol>

<h3 id="9-2-9"><a href="#s2">9-2-9. SPECIAL INTEREST SITES</a></h3>

<ol>
	<li>Immediately relay any reports or information regarding unusual aircraft activities in the vicinity of special interest sites such as nuclear power plants, power plants, dams, refineries, etc., to supervisory/CIC personnel.
		<p class="note">NOTE: Air traffic controllers have no responsibilities to monitor or observe aircraft in the vicinity of special interest sites unless directed by supervisory/CIC personnel.</p>
</li>
</ol>

<h3 id="9-2-10"><a href="#s2">9−2−10. SPECIAL AIR TRAFFIC RULES (SATR) AND SPECIAL FLIGHT RULES AREA (SFRA)</a></h3>
<p>The Code of Federal Regulations prescribes special air traffic rules for aircraft operating within the boundaries of certain designated airspace. These areas are listed in 14 CFR Part 93 and can be found throughout the NAS. Procedures, nature of opera- tions, configuration, size, and density of traffic vary among the identified areas.</p>

<ol>
	<li>Special Flight Rules Areas are areas of airspace wherein the flight of aircraft is subject to special air traffic rules set forth in 14 CFR Part 93, unless otherwise authorized by air traffic control. Not all areas listed in 14 CFR Part 93 are Special Flight Rules Areas, but special air traffic rules apply to all areas designated as SFRA.
		<ul class="reference">
			<li>REFERENCE</li>
			<li><a href="https://www.law.cornell.edu/cfr/text/14/part-93" target="_blank">14 CFR Part 93, Special Air Traffic Rules.</a></li>
			<li><a href="/wiki/7110.65:PCG#special_air_traffic_rules_satr">P/CG - SPECIAL AIR TRAFFIC RULES (SATR)</a></li>
			<li><a href="/wiki/7110.65:PCG#special_flight_rules_area_sfra">P/CG - SPECIAL FLIGHT RULES AREA (SFRA)</a></li>
		</ul></li>
	<li>Each person operating an aircraft to, from, or within airspace designated as a SATR area or SFRA must adhere to the special air traffic rules set forth in 14 CFR Part 93, as applicable, unless otherwise authorized or required by ATC.</li>
</ol>

<h3 id="9-2-11"><a href="#s2">9-2-11. ATC SECURITY SERVICES FOR THE WASHINGTON, DC, SPECIAL FLIGHT RULES AREA (DC SFRA)</a></h3>
<a href="Interpretation_22" title="Interpretation" target="_blank"><span class="interp">interpretation 22</span></a>
<p>Provide ATC security services at locations where procedures are required for tracking aircraft in security services airspace. ATC security services are designed to support the national security mission of the FAA and other agencies. Two-way radio communications, flight planning, and an operational transponder on an assigned code are required for operations in the designated area.</p>
<ol>
	<li>When the assigned code is observed, advise the aircraft to proceed on course/as requested but to remain outside of Class B, C, and/or D airspace as appropriate.
		<ul class="phraseology">
			<li>PHRASEOLOGY</li>
			<li>(ACID) TRANSPONDER OBSERVED PROCEED ON COURSE/AS REQUESTED; REMAIN OUTSIDE (class) AIRSPACE.</li>
		</ul>
		<ol>
			<li>Maintain continuous security tracking of VFR aircraft operating in the designated area to assist security forces in situational awareness. Immediately report all instances of loss of radio communication or the inability to conduct security tracking of an aircraft to the operations supervisor (OS)/CIC and wait for instructions.</li>
			<li>Basic separation services to aircraft, for example, IFR, SVFR, Class B, Class C, TRSA, do not apply to ATC security tracking.</li>
			<li>Aircraft with operating transponders, but without operating Mode C (altitude), require specific authorization from ATC to operate in the SFRA. ATC must coordinate with the Domestic Events Network (DEN) before approval.</li>
			<li>Aircraft flying too low for radar coverage must be instructed to report landing or exiting the SFRA. Keep flight progress strips on these aircraft until pilot reports landing or exiting the SFRA. If a flight progress strip does not exist for the aircraft, record the call sign, transponder code, entry point (for example, north, northeast, east), and time of entry into the SFRA.
				<ul class="phraseology">
					<li>PHRASEOLOGY</li>
					<li>(Call sign), REPORT LANDING OR LEAVING THE SFRA.</li>
				</ul></li>
			<li>United States military, law enforcement, and aeromedical flights are exempt from filing flight plans.</li>
		</ol></li>
	<li>Establishing two-way Communications.
		<ol>
			<li>Pilots must establish two-way radio communications with ATC prior to entering the security service area. Responding to a radio call with, “(a/c call sign) standby,” establishes radio communications and the pilot may enter the area, provided all other security requirements have been satisfied.</li>
			<li>Aircraft requesting security services should not normally be held. However, if holding is necessary or workload/traffic conditions prevent immediate provision of ATC security services, inform the pilot to remain outside the designated area until conditions permit the provision of ATC security services. Inform the pilot of the expected length of delay.
				<ul class="phraseology">
					<li>PHRASEOLOGY</li>
					<li>(A/C call sign) REMAIN OUTSIDE OF THE (location) AND STANDBY. EXPECT (time) MINUTES DELAY.</li>
				</ul></li>
		</ol></li>
	<li>Termination of Service.
		<ol>
			<li>If the aircraft is not landing within the designated area, provide security services until the aircraft exits the area and then advise the aircraft to squawk VFR and that frequency change is approved.
				<ul class="phraseology">
					<li>PHRASEOLOGY</li>
					<li>SQUAWK VFR, FREQUENCY CHANGE APPROVED.</li>
					<li>or</li>
					<li>CONTACT (facility identification).</li>
				</ul></li>
			<li>When an aircraft is landing at an airport inside the area, instruct the pilot to remain on the assigned transponder code until after landing.
				<ul class="phraseology">
					<li>PHRASEOLOGY</li>
					<li>(ACID) REMAIN ON YOUR ASSIGNED TRANSPONDER CODE UNTIL YOU LAND, FREQUENCY CHANGE APPROVED.</li>
				</ul></li>
			<li>Using approved handoff functionality, transfer the data blocks of all security tracked aircraft that will enter another sector/position for coordination of aircraft information/location. Upon acceptance of the transferred information, instruct the pilot to contact the next sector/positions’ frequency.</li>
		</ol></li>
</ol>

<h3 id="9-2-12"><a href="#s2">9-2-12. SECURITY NOTICE (SECNOT)</a></h3>

<p>Upon receiving notification of a SECNOT, the controller must forward all information on the subject aircraft to the OS/CIC. If information is not known, broadcast call sign on all frequencies and advise the OS/CIC of the response.</p>
<ul class="reference">
	<li>REFERENCE</li>
	<li><a href="/wiki/7110.65:PCG#security_notice">P/CG Term - Security Notice.</a></li>
	<li>FAA Order JO 7210.3, Chapter 19, Section 9, Security Notice (SECNOT).</li>
</ul>

<h3 id="9-2-13"><a href="#s2">9-2-13. LAW ENFORCEMENT OPERATIONS BY CIVIL AND MILITARY ORGANIZATIONS</a></h3>

<ol>
	<li>Law enforcement alerts.
		<ol>
			<li>Aircraft lookouts must not be distributed outside the FAA.
				<ul class="reference">
					<li>REFERENCE</li>
					<li>FAA Order 1600.29, Law Enforcement Alert Message System.</li>
					<li>FAA Order JO 7210.3, Para 2-7-7, Cooperation With Law Enforcement Agencies.</li>
				</ul></li>
			<li>Stolen aircraft alerts, including stolen aircraft summaries, may be distributed outside the FAA to: airport offices, air carriers, fixed base operators, and law enforcement agencies.</li>
			<li>Upon receipt of knowledge concerning an aircraft for which a current law enforcement alert message is held, do the following:
				<ol>
					<li>(a) Forward any information on the aircraft to El Paso Intelligence Center (EPIC) and the requester when specified in the message.</li>
					<li>(b) Immediately notify the cognizant Transportation Security Administration office by the most rapid means.</li>
					<li>(c) DO NOT TAKE ANY OTHER ACTION AFFECTING THE AIRCRAFT, CARGO, CREW, OR PASSENGERS NOT NORMALLY RELATED TO JOB RESPONSIBILITIES.</li>
				</ol></li>
		</ol></li>
	<li>Special law enforcement operations.
		<ol>
			<li>Special law enforcement operations include inflight identification, surveillance, interdiction and pursuit activities performed in accordance with official civil and/or military mission responsibilities.</li>
			<li>To facilitate accomplishment of these special missions, exemptions from specified parts of Title 14 of the Code of Federal Regulations have been granted to designated departments and agencies. However, it is each organization’s responsibility to apprise ATC of their intent to operate under an authorized exemption before initiating actual operations.
				<ul class="reference">
					<li>REFERENCE</li>
					<li>FAA Order JO 7210.3, Para 18-3-1, Authorizations and Exemptions from Title 14, Code of Federal Regulations (14 CFR).</li>
				</ul></li>
			<li>Additionally, some departments and agencies that perform special missions have been assigned coded identifiers to permit them to apprise ATC of ongoing mission activities and solicit special air traffic assistance.
				<ul class="reference">
					<li>REFERENCE</li>
					<li>FAA Order 7110.67, Special Aircraft Operations by Law Enforcement/Military Organizations.</li>
				</ul>
				<p class="note">NOTE: As specified in para 2-1-4, Operational Priority, priority of handling for aircraft operating with coded identifiers will be the same as that afforded to SAR aircraft performing a SAR mission.</p></li>
		</ol></li>
	<li>Assistance to law enforcement aircraft operations.
		<ol>
			<li>Provide the maximum assistance possible to law enforcement aircraft, when requested, in helping them locate suspect aircraft.</li>
			<li>Communicate with law enforcement aircraft, when possible and if requested, on a frequency not paired with your normal communications frequencies.</li>
			<li>Do not allow assistance to law enforcement aircraft to violate any required separation minima.</li>
			<li>Do not assist VFR law enforcement aircraft in any way that will create a situation which, in your judgment, places the aircraft in unsafe proximity to terrain or other aircraft.</li>
		</ol></li>
</ol>

<h3 id="9-2-14"><a href="#s2">9-2-14. MILITARY AERIAL REFUELING</a></h3>

<p>Authorize aircraft to conduct aerial refueling along published or special tracks at their flight plan altitude, unless otherwise requested.</p>
<ul class="phraseology">
	<li>PHRASEOLOGY</li>
	<li>CLEARED TO CONDUCT REFUELING ALONG (number) TRACK,</li>
	<li>or</li>
	<li>FROM (fix) TO (fix),</li>
	<li>and</li>
	<li>MAINTAIN REFUELING LEVEL (altitude),</li>
	<li>or</li>
	<li>MAINTAIN (altitude),</li>
	<li>or</li>
	<li>COMMENCING AT (altitude), DESCENDING TO (altitude).</li>
</ul>
<ul class="note">
	<li>NOTE:</li>
	<li>1. During aerial refueling, tanker aircraft are responsible for receiver aircraft communication with ATC and for their navigation along the track.</li>
	<li>2. Aerial refueling airspace is not sterilized airspace and other aircraft may transit this airspace provided vertical or lateral separation is provided from refueling aircraft.</li>
	<li>3. MARSA begins between the tanker and receiver when the tanker and receiver(s) have entered the air refueling airspace and the tanker advises ATC that he/she is accepting MARSA.</li>
	<li>4. MARSA ends between the tanker and receiver when the tanker advises ATC that the tanker and receiver aircraft are vertically positioned within the air refueling airspace and ATC advises MARSA is terminated.</li>
</ul>
<ul class="reference">
	<li>REFERENCE</li>
	<li><a href="/wiki/7110.65:Chapter_2#2-1-11">FAA Order JO 7110.65, Para 2-1-11, Use of MARSA.</a></li>
	<li><a href="/wiki/7110.65:Chapter_5#5-5-8">FAA Order JO 7110.65, Para 5-5-8, Additional Separation for Formation Flights.</a></li>
	<li>FAA Order JO 7610.4, Chapter 10, Aerial Refueling.</li>
</ul>
<ol>
	<li>Provide radar assistance to the rendezvous for participating aircraft:
		<ol>
			<li>When requested, and</li>
			<li>By providing vertical separation prior to MARSA declaration.</li>
		</ol></li>
	<li>Do not request receiver aircraft that have been cleared to conduct air refueling and have departed the ARIP to:
		<ol>
			<li>Make code changes when less than 5 miles from the tanker.</li>
			<li>Squawk standby when less than 1 mile or more than 3 miles from the tanker.</li>
		</ol>
		<p class="note">NOTE: Requests for receiver aircraft to make code changes during air refueling diverts the receiver pilot’s attention during a critical phase of flight.</p></li>
	<li>When issuing an initial air refueling clearance, you may request a receiver to squawk standby when the receiver reaches a point 3 miles from the tanker.
		<ol class="note">
			<li>NOTE:</li>
			<li>1. Receiver aircraft will squawk normal when separation from the tanker is greater than 3 miles.</li>
			<li>2. Once rendezvous is completed, heading and altitude assignments may be made with the tanker concurrence with MARSA remaining in effect.</li>
			<li>3. Upon rendezvous completion, the tanker must keep receiver aircraft within 3 miles of the tanker until MARSA is terminated.</li>
		</ol></li>
	<li>After MARSA has been declared, you should avoid issuing course or altitude changes prior to rendezvous.
		<p class="note">NOTE: Altitude or course changes issued will automatically void MARSA.</p></li>
	<li>Do not use the altitude vacated during the refueling operation until the refueling aircraft has reported reaching the next IFR altitude.
		<ul class="reference">
			<li>REFERENCE</li>
			<li><a href="/wiki/7110.65:Chapter_6#6-6-2">FAA Order JO 7110.65, Para 6-6-2, Exceptions.</a></li>
		</ul></li>
	<li>Approve requests by the tanker pilot for vectors or alternative routes or altitudes as follows:
		<ol>
			<li>Furnish vectors or alternative altitudes at any time.</li>
			<li>Furnish nonradar routes only after the refueling aircraft have passed the ARCP.</li>
		</ol>
		<ul class="note">
			<li>NOTE:</li>
			<li>1. To meet a training requirement that aerial refueling be accomplished in a nonradar environment, the military has requested that vectors be furnished only upon request.</li>
			<li>2. The tanker commander is responsible for coordinating all inflight requests with other aircraft in the refueling mission before submission of such requests to the center.</li>
			<li>3. Normally, aircraft conducting aerial refueling operations will utilize at least three consecutive altitudes.</li>
		</ul></li>
	<li>Unless a vector or alternative route has been furnished, clear the aircraft to depart the refueling track at a navigational reference point or egress fix.</li>
	<li>Request an aircraft to report the ARIP, ARCP, or egress fix as necessary.
		<ul class="phraseology">
			<li>PHRASEOLOGY</li>
			<li>REPORT: A-R-I-P,</li>
			<li>or A-R-C-P,</li>
			<li>or</li>
			<li>EGRESS FIX.</li>
		</ul></li>
	<li>Expect the following procedures in addition to those required by the appropriate parts of Title 14 of the Code of Federal Regulations in the event of two-way communications failure:
		<ol>
			<li>The tanker will depart the track from the highest altitude in the block.</li>
			<li>The receiver will depart the track from the lowest altitude in the block.</li>
			<li>Aircraft will squawk 7600 for at least 2 minutes prior to departing the track.</li>
		</ol>
		<ul class="reference">
			<li>REFERENCE</li>
			<li><a href="#9-2-15">FAA Order JO 7110.65, Para 9-2-15, Military Operations Above FL 600.</a></li>
		</ul>
	</li>
</ol>
<h3 id="9-2-15"><a href="#s2">9-2-15. MILITARY OPERATIONS ABOVE FL600</a></h3>

<p>Control aircraft operating above FL 600 using the following procedures:</p>
<ol>
	<li>Flight plans involving supersonic flight are required 16 hours in advance of proposed departure times for processing and approval by the ARTCCs concerned. The originating ARTCC, where the flight plan is first filed, may waive the 16-hour advance filing requirement.</li>
	<li>The route of flight must be defined by at least one high altitude fix within each ARTCC area without regard to the distance between fixes. Additionally, the entry and exit points of turns of 90 degrees or more will be designated.</li>
	<li>Elapsed times from takeoff to the first fix in each ARTCC area must be included in the route of flight.</li>
	<li>The ARTCC which originates the flight plan must forward departure times to all ARTCCs responsible for processing the flight plan.</li>
	<li>Approval of the flight plan indicates approval of both route and flight levels (if stated) including operations below FL 600 (aerial refueling).
		<ul class="phraseology">
			<li>PHRASEOLOGY</li>
			<li>CLEARED AS FILED VIA ROUTE AND FLIGHT LEVELS.</li>
		</ul>
		<ul class="reference">
			<li>REFERENCE</li>
			<li><a href="#9-2-14">FAA Order JO 7110.65, Para 9-2-14, Military Aerial Refueling.</a></li>
		</ul></li>
	<li>Separation. Use the following as minima in lieu of the corresponding type of separation prescribed in:
		<p class="note">NOTE: The primary method described to provide separation between two supersonic aircraft is to descend the aircraft at the lower FL and provide vertical separation since the aircraft at the higher FL may not be able to climb rapidly enough to establish the required separation. Another aspect which should be considered is that supersonic aircraft during turns, either programmed or as the result of vectors, will lose a few thousand feet. Vectoring supersonic aircraft seriously affects the range and mission objectives. Radar separation is the preferred method of separating a subsonic aircraft both from another subsonic aircraft or from a supersonic aircraft.</p>
		<ol>
			<li>Para 4-5-1, Vertical Separation Minima: 5,000 feet.
				<ul class="note">
					<li>NOTE:</li>
					<li>1. The security requirements of the military services preclude the transmission of actual altitude information on the air/ground or landline circuits. A classified document detailing the plan for ascertaining altitude codes for the day should be readily available to the controllers at their positions of operation.</li>
					<li>2. Pilots will report their altitude, using the coded plan, and intended flight profile on initial contact with each ARTCC.</li>
				</ul></li>
			<li>Para 6-5-4, Minima Along Other Than Established Airways or Routes: Protect the airspace 25 miles either side of the route centerline. For turns by supersonic aircraft, protect the airspace 75 miles on the overflown side and 25 miles on the other side. For turns by subsonic aircraft, protect the airspace 34 miles on the overflown side and 25 miles on the other side.
				<ul class="reference">
					<li>REFERENCE</li>
					<li><a href="/wiki/7110.65:Chapter_4#4-3-3">FAA Order JO 7110.65, Para 4-3-3, Abbreviated Departure Clearance.</a></li>
				</ul></li>
		</ol></li>
</ol>

<h3 id="9-2-16"><a href="#s2">9-2-16. MILITARY SPECIAL USE FREQUENCIES</a></h3>

<ol>
	<li>Assign special use frequency to:
		<p class="note">NOTE: Special use frequencies are assigned to ARTCCs in such a manner that adjacent ARTCCs will not have the same frequency. They are to be used within the ARTCC area jurisdiction from the established FL base of the high altitude sectors and above. Each high altitude sector should have the capability to use the special use frequency on a shared basis.</p>
		<ol>
			<li>USAF, U.S. Navy, and Air National Guard (ANG) single-pilot jet aircraft formations operating at night or in instrument weather conditions. Formations of five or more USAF aircraft deploying either to a continental U.S. staging base or nonstop to an overseas location are authorized to use special use frequencies at any time. Normally these deployments will be conducted within an altitude reservation.</li>
			<li>U-2 and B-57 (pressure suit flights) aircraft at all altitudes/FLs except where terminal operations require the assignment of other frequencies.
				<p class="note">NOTE: Aerial refueling operations may require that aircraft leave the special use frequency for communications with the tanker. This will occur when the receiver is approximately 200 miles from the ARCP. The tanker aircraft will remain on the ARTCC assigned frequency and will relay clearances to the receiver as required. An alternate means of communications between the tanker and receiver is HF radio.</p></li>
			<li>All aircraft during supersonic flight.
				<p class="note">NOTE: Pilots are expected to request assignment of the special use frequency in the remarks section of the flight plan or before entering supersonic flight. B-57 aircraft engaged in pressure suit operations will use the static call sign KITE and flights will normally be conducted from Dover, Eielson, Ellington, Hickman, Howard, Kirtland, and McClellan Air Force Bases.</p></li>
			<li>E-3A AWACS mission crews when operations are being conducted as an MRU in accordance with appropriate letters of agreement.</li>
		</ol></li>
	<li>The special use frequency may be assigned as “backup” for the high-altitude sector when direct communications are essential because of a potential emergency control situation.</li>
	<li>Do not assign the special use frequency to the aircraft in subpara a1 above, when they will operate in airspace assigned for special military operations.</li>
</ol>

<h3 id="9-2-17"><a href="#s2">9-2-17. AVOIDANCE OF AREAS OF NUCLEAR RADIATION</a></h3>

<ol>
	<li>Advise pilots whenever their proposed flight path will traverse a reported or forecasted area of hazardous radiation and reroute the aircraft when requested by the pilot.
		<ul class="reference">
			<li>REFERENCE</li>
			<li>FAA Order JO 7610.4, Para 4-4-4, Avoidance of Hazardous Radiation Areas.</li>
		</ul></li>
	<li>Inform pilots when an airfield of intended landing lies within a reported or forecasted area of hazardous radiation and request the pilot to advise his/her intentions.</li>
</ol>

<h3 id="9-2-18"><a href="#s2">9-2-18. SAMP</a></h3>

<p>Provide special handling to U.S. Government and military aircraft engaged in aerial sampling missions (atmosphere sampling for nuclear, chemical, or hazardous material contamination). Honor inflight clearance requests for altitude and route changes to the maximum extent possible. Other IFR aircraft may be recleared so that requests by SAMPLER aircraft are honored. Separation standards as outlined in this order must be applied in all cases.</p>
<ul class="reference">
	<li>REFERENCE</li>
	<li><a href="/wiki/7110.65:Chapter_2#2-1-4">FAA Order JO 7110.65, Para 2-1-4, Operational Priority.</a></li>
	<li><a href="/wiki/7110.65:Chapter_2#2-4-20">FAA Order JO 7110.65, Para 2-4-20, Aircraft Identification.</a></li>
	<li>FAA Order JO 7610.4, Para 4-4-4, Avoidance of Hazardous Radiation Areas.</li>
</ul>

<h3 id="9-2-19"><a href="#s2">9-2-19. AWACS/NORAD SPECIAL FLIGHTS</a></h3>

<p>Do not delay E-3 AWACS aircraft identified as “AWACS/NORAD Special” flights. The following control actions are acceptable while expediting these aircraft to the destination orbit.</p>
<ol>
	<li>En route altitude changes +/– 2,000 feet from the requested flight level.</li>
	<li>Radar vectors or minor route changes that do not impede progress towards the destination orbit.</li>
</ol>
<p class="note">NOTE: NORAD has a requirement to position E-3 AWACS aircraft at selected locations on a time-critical basis. To the extent possible these flights will utilize routes to the destination orbit that have been precoordinated with the impacted ATC facilities. To identify these flights, the words “AWACS/NORAD SPECIAL” will be included as the first item in the remarks section of the flight plan.</p>

<h3 id="9-2-20"><a href="#s2">9-2-20. WEATHER RECONNAISSANCE FLIGHTS</a></h3>

<p>TEAL and NOAA mission aircraft fly reconnaissance flights to gather meteorological data on winter storms, (NWSOP missions), hurricanes and tropical cyclones (NHOP missions). The routes and timing of these flights are determined by movement of the storm areas and not by traffic flows.</p>
<ol>
	<li>When a dropsonde release time is received from a TEAL or NOAA mission aircraft, workload and priorities permitting, controllers must advise the mission aircraft of any traffic estimated to pass through the area of the drop at altitudes below that of the mission aircraft. This traffic advisory must include:
		<ol>
			<li>Altitude.</li>
			<li>Direction of flight.</li>
			<li>ETA at the point closest to drop area (or at the fix/intersection where drop will occur).</li>
		</ol>
		<p class="note">NOTE: A dropsonde is a 14-inch long cardboard cylinder about 2.75 inches in diameter, that weighs approximately 14 ounces (400 grams), and has a parachute attached. When released from the aircraft it will fall at a rate of approximately 2,500 feet per minute. Controllers should recognize that a dropsonde released at FL 310 will be a factor for traffic at FL 210 four minutes later. It is the aircraft commanders responsibility to delay release of dropsondes if traffic is a factor. Aircraft commanders will delay release of dropsondes based solely upon traffic as issued by ATC.</p></li>
	<li>When advised that an airborne TEAL or NOAA aircraft is requesting a clearance via CARCAH, issue the clearance in accordance with Chapter 4, IFR, Section 2, Clearances.
		<ul class="reference">
			<li>REFERENCE</li>
			<li><a href="/wiki/7110.65:Chapter_4#4-2-1">FAA Order JO 7110.65, Para 4-2-1, Clearance Items.</a></li>
			<li><a href="/wiki/7110.65:Chapter_4#4-2-2">FAA Order JO 7110.65, Para 4-2-2, Clearance Prefix.</a></li>
			<li><a href="/wiki/7110.65:Chapter_4#4-2-3">FAA Order JO 7110.65, Para 4-2-3, Delivery Instructions.</a></li>
		</ul></li>
	<li>If a TEAL or NOAA mission aircraft must be contacted but is out of VHF, UHF, and HF radio range, advise the supervisory traffic management coordinator-in-charge.
		<ul class="reference">
			<li>REFERENCE</li>
			<li>FAA Order JO 7210.3, Para 5-3-6, Weather Reconnaissance Flights.</li>
			<li><a href="/wiki/7110.65:Chapter_2#2-1-4">FAA Order JO 7110.65, Para 2-1-4, Operational Priority.</a></li>
		</ul></li>
	
	<li>Aircraft operations associated with a Weather Reconnaissance Area (WRA) must be conducted in accordance with the Memorandum of Agreement between the National Oceanic and Atmospheric Administration Aircraft Operations Center, U.S. Air Force Reserve Command 53rd Weather Reconnaissance Squadron, and the Federal Aviation Administration Air Traffic Organization in Support of the National Hurricane Operations Plan (FAA Order JO 7610.4, Appendix 3), and the associated letters of agreement.</li>
</ol>

<h3 id="9-2-21"><a href="#s2">9-2-21. EVASIVE ACTION MANEUVER</a></h3>

<p>Approve a pilot request to conduct an evasive action maneuver only on the basis of a permissible traffic situation. Specify the following items, as necessary, when issuing approval:</p>
<ul class="note">
	<li>NOTE: The “evasive action” maneuver is performed by a bomber/fighter bomber aircraft at or above FL 250 along a 60 NM long segment of the flight plan route overlying a RBS or other site and includes:</li>
	<li>1. Flying a zigzag pattern on both the left and right side of the flight plan route centerline. Altitude deviations are made in conjunction with the lateral maneuvering.</li>
	<li>2. Lateral deviations from the route centerline will not normally exceed 12 miles. Altitude variations must not exceed plus or minus 1,000 feet of the assigned flight level; i.e., confined within a 2,000 foot block.</li>
</ul>
<ol>
	<li>Specific route segment on which the maneuver will take place.</li>
	<li>Distance of maximum route deviation from the centerline in miles.</li>
	<li>Altitude.</li>
</ol>
<ul class="phraseology">
	<li>PHRASEOLOGY</li>
	<li>CLEARED TO CONDUCT EVASIVE ACTION MANEUVER FROM (fix) TO (fix),</li>
	<li>and</li>
	<li>(number of miles) EITHER SIDE OF CENTERLINE,</li>
	<li>and</li>
	<li>MAINTAIN (altitude) THROUGH (altitude),</li>
	<li>and</li>
	<li>COMPLETE MANEUVER AT (fix) AT (altitude).</li>
</ul>

<h3 id="9-2-22"><a href="#s2">9-2-22. NONSTANDARD FORMATION/CELL OPERATIONS</a></h3>

<p>Occasionally the military is required to operate in a nonstandard cell formation and controllers should be knowledgeable of the various tactics employed and the procedures used.</p>
<ul class="reference">
	<li>REFERENCE</li>
	<li>FAA Order JO 7610.4, Chapter 12, Section 11, Formation Flight.</li>
</ul>
<ol>
	<li>Formation leaders are responsible for obtaining ATC approval to conduct nonstandard formation/cell operations.</li>
	<li>When nonstandard formation/cell operations have been approved, controllers must assign sufficient altitudes to allow intra-cell vertical spacing of 500 feet between each aircraft in the formation.</li>
	<li>Control nonstandard formation/cell operations on the basis that MARSA is applicable between the participating aircraft until they establish approved separation which is acknowledged by ATC.</li>
	<li>Apply approved separation criteria between the approved nonstandard formation/cell envelope and nonparticipating aircraft.</li>
	<li>Clear aircraft operating in a nonstandard formation/cell to the breakup fix as the clearance limit. Forward data pertaining to route or altitude beyond the breakup point to the center concerned as a part of the routine flight plan information.</li>
	<li><span>EN ROUTE</span>. If the breakup occurs in your area, issue appropriate clearances to authorize transition from formation to individual routes or altitudes. If a breakup cannot be approved, issue an appropriate clearance for the flight to continue as a formation.</li>
</ol>

<h3 id="9-2-23"><a href="#s2">9-2-23. OPEN SKIES TREATY AIRCRAFT</a></h3>

<ol>
	<li>Open Skies aircraft will be identified by the call sign “OSY” (Open Skies) followed by the flight number and a one−letter mission suffix.
		<ul class="example">
			<li>EXAMPLE</li>
			<li>OSY123D</li>
			<li>Mission suffixes:</li>
			<li>*F = Observation Flights (Priority).</li>
			<li>*D = Demonstration Flights (Priority).</li>
			<li>*T = Transit Flights (Nonpriority).</li>
		</ul>
		<ul class="note">
			<li>NOTE:</li>
			<li>1. Observation/Demonstration flights are conducted under rigid guidelines outlined in the Treaty of Open Skies that govern sensor usage, maximum flight distances, altitudes and priorities.</li>
			<li>2. Transit flights are for the sole purpose of moving an Open Skies aircraft from airport to airport in preparation for an actual Open Skies “F” or “D” mission.</li>
		</ul></li>
	<li>Provide priority and special handling to expedite the movement of an Open Skies observation or demonstration flight.
		<ul class="reference">
			<li>REFERENCE</li>
			<li><a href="/wiki/7110.65:Chapter_2#2-1-4">FAA Order JO 7110.65, Para 2-1-4, Operational Priority, subpara n.</a></li>
			<li>FAA Order JO 7210.3, Para 5-3-7, Open Skies Treaty Aircraft.</li>
			<li>Treaty on Open Skies, Treaty Document, 102-37.</li>
		</ul></li>
	<li>Open Skies (F and D) Treaty aircraft, while maintaining compliance with ATC procedures, must have priority over activities in special use airspace (SUA)/Air Traffic Control Assigned Airspace (ATCAA). Open Skies (F and D) Treaty aircraft are nonparticipating aircraft and must be allowed to transit SUA/ATCAA as filed after appropriate and timely coordination has been accomplished between the using agency and controlling agency.
		<p class="note">NOTE: A letter of agreement is not required for nonparticipating aircraft to transit deactivated/released airspace.</p>
		<ul class="reference">
			<li>REFERENCE</li>
			<li><a href="#9-3-4">FAA Order JO 7110.65, Para 9-3-4, Transiting Active SUA/ATCAA.</a></li>
		</ul>
		<ol>
			<li>Open Skies (F and D)Treaty flights transiting SUA/ATCAA will be handled in the following manner:
				<ol>
					<li>(a) The ATC facility controlling the Open Skies (F and D) Treaty flight must advise the using agency, or appropriate ATC facility, upon initial notification and when the aircraft is 30 minutes from the SUA/ATCAA boundary; and
						<ol>
							<li>(1) For active SUA/ATCAA with an ATC facility, coordinate and execute the transit of Open Skies (F and D) Treaty aircraft.
								<ul class="reference">
									<li>REFERENCE</li>
									<li><a href="#9-3-4">FAA Order JO 7110.65, Para 9−3−4, Transiting Active SUA/ATCAA.</a></li>
								</ul></li>
							<li>(2) For active SUA/ATCAA without an ATC facility, the using agency must deactivate/re- lease the SUA/ATCAA to permit the Open Skies (F and D) Treaty aircraft to transit as filed in proximity to the active SUA/ATCAA. When deactivating/releasing the SUA/ATCAA for this purpose, the using agency is only required to deactivate/release the portion of the SUA/ATCAA to the controlling agency that is necessary to provide approved separation.</li>
						</ol></li>
					<li>(b) The using agency must deactivate/release the SUA/ATCAA, or portion thereof, no later than 15 minutes prior to the Open Skies (F and D) Treaty aircraft reaching the SUA/ATCAA boundary.</li>
					<li>(c) If the controlling agency is unable to confirm with the using agency that all conflicting activities in the SUA/ATCAA have ceased, the Open Skies aircraft must not be permitted access to the SUA/ATCAA.
						<ul class="reference">
							<li>REFERENCE</li>
							<li><a href="#9-3-2">FAA Order JO 7110.65, Para 9−3−2, Separation Minima.</a></li>
						</ul></li>
				</ol></li>
			<li>Return SUA/ATCAA to the using agency, if requested, within (15) minutes after the Open Skies (F and D) Treaty aircraft clears the SUA/ATCAA.</li>
		</ol></li>
	<li>Clear the aircraft according to the filed flight plan.
		<ol>
			<li>Do not ask the pilot to deviate from the planned action or route of flight except to preclude an emergency situation or other higher priority aircraft.</li>
			<li>Do not impose air traffic control delays except to preclude emergency situations or other higher priority aircraft.</li>
		</ol>
		<p class="note">NOTE: If for reasons of flight safety the route or altitude must be changed, return the aircraft to the filed flight plan route as soon as practical.</p></li>
</ol>

</section>

<section id="s3">
<h2><a href="#chapters">Section 3. Special Use, ATC-Assigned Airspace, and Stationary ALTRVs</a></h2>

<h3 id="9-3-1"><a href="#s3">9-3-1. APPLICATION</a></h3>

<p>Apply the procedures in this section to aircraft operating in proximity to special use, ATC-assigned airspace (ATCAA), and stationary ALTRVs unless the airspace is designated an alert area/controlled firing area or one of the following conditions exist:</p>
<p class="note">NOTE: These procedures are not applicable to Alert Areas or Controlled Firing Areas.</p>
<ul class="reference">
	<li>REFERENCE</li>
	<li><a href="/wiki/7110.65:PCG#special_use_airspace">P/CG Term - Special Use Airspace.</a></li>
</ul>
<ol>
	<li>The pilot informs you that permission has been obtained from the using agency to operate in the airspace.</li>
	<li>The using agency informs you they have given permission for the aircraft to operate in the airspace.
		<p class="note">NOTE: Using agency permission may be relayed to the pilot.</p></li>
	<li>The restricted/warning area, MOA, ATCAA, or stationary ALTRV has been released to the controlling agency.</li>
	<li>The aircraft is on an approved ALTRV, unless the airspace area in question is an ATCAA.
		<p class="note">NOTE: Mission project officers are responsible for obtaining approval for ALTRV operations within prohibited/ restricted/warning areas, MOAs, and stationary ALTRVs.</p>
		<ul class="reference">
			<li>REFERENCE</li>
			<li><a href="#9-3-4">FAA Order JO 7110.65, Para 9-3-4, Transiting Active SUA/ATCAA.</a></li>
		</ul></li>
	<li>Operations in special use airspace and stationary ALTRVs located in offshore/oceanic airspace will be conducted in accordance with the procedures in Chapter 8, Offshore/Oceanic Procedures.</li>
</ol>


<h3 id="9-3-2"><a href="#s3">9-3-2. SEPARATION MINIMA</a></h3>

<p>Unless clearance of nonparticipating aircraft in/ through/adjacent to a prohibited/restricted/warning area/MOA/ATCAA/stationary ALTRV is provided for in a letter of agreement (LOA) or letter of procedure (LOP), separate nonparticipating aircraft from active special use airspace, ATCAAs, and stationary ALTRVs by the following minima:</p>
<ol>
	<li>Assign an altitude consistent with para 4-5-2, Flight Direction, and 4-5-3, Exceptions, which is at least 500 feet (above FL 290-1000 feet) above/below the upper/lower limit of the prohibited/ restricted/ warning area/MOA/ ATCAA/stationary ALTRV.
		<ul class="reference">
			<li>REFERENCE</li>
			<li>FAA Order JO 7210.3, Para 2-1-17, Prohibited/Restricted Areas and Stationary ALTRVs.</li>
		</ul></li>
	<li>Provide radar separation of 3 miles (FL600 and above - 6 miles) from the special use airspace, ATCAA, or stationary ALTRV peripheral boundary.</li>
	<li>Clear aircraft on airways or routes whose widths or protected airspace do not overlap the peripheral boundary.</li>
	<li>Exception. Some prohibited/restricted/warning areas are established for security reasons or to contain hazardous activities not involving aircraft operations. Where facility management has identified these areas as outlined in FAA Order JO 7210.3, Facility Operation and Administration, vector aircraft to remain clear of the peripheral boundary.
		<p class="note">NOTE: Nonparticipating aircraft refers to those aircraft for which you have separation responsibility and which have not been authorized by the using agency to operate in/through the special use airspace, ATCAA, or stationary ALTRV in question. VFR traffic is not prohibited from transiting stationary ALTRVs.</p></li>
</ol>

<h3 id="9-3-3"><a href="#s3">9-3-3. VFR-ON-TOP</a></h3>

<p>If the aircraft’s route, track, or altitude may cause it to enter an active Prohibited/Restricted/Warning Area, MOA, or ATCAA:</p>
<ol>
	<li>Inform the pilot to conduct flight “VFR-on-top” at least 500 feet above the upper limit or below the lower limit of the airspace (subject to para 7-3-1, VFR-on-top); or
		<ul class="phraseology">
			<li>PHRASEOLOGY</li>
			<li>MAINTAIN VFR-ON-TOP AT LEAST 500 FEET ABOVE/BELOW (upper/lower limit of airspace) ACROSS (name or number of airspace) BETWEEN (fix) AND (fix);</li>
			<li>and if the airspace is an ATCAA,</li>
			<li>(name of ATCAA) IS ATC ASSIGNED AIRSPACE.</li>
		</ul>
		<ul class="reference">
			<li>REFERENCE</li>
			<li><a href="/wiki/7110.65:Chapter_7#7-1-1">FAA Order JO 7110.65, Para 7-1-1, Class A Airspace Restrictions.</a></li>
		</ul></li>
	<li>Clear the aircraft via a routing which provides approved separation from the airspace.</li>
	<li>Exception: Some Prohibited/Restricted Areas are established for security reasons or to contain hazardous activities not involving aircraft operations. The addition of 500 (or 1,000) feet to the upper/lower limit of these Prohibited/Restricted Areas is not required if the areas have been identified by facility management.</li>
</ol>
<ul class="reference">
	<li>REFERENCE</li>
	<li>FAA Order JO 7210.3, Para 2-1-17, Prohibited/Restricted Areas.</li>
</ul>

<h3 id="9-3-4"><a href="#s3">9-3-4. TRANSITING ACTIVE SUA/ATCAA</a></h3>

<p>If a LOA/LOP has been coordinated with the Using Agency and permission has been granted to transit the area:</p>
<ol>
	<li>Comply with the instruction/clearances issued by the Using Agency and provide the applicable separation minima between aircraft when two or more aircraft are transiting the area; or
		<p class="note">NOTE: Some Using Agencies are also air traffic control facilities.</p></li>
	<li>If unable to comply with instructions/clearances, clear the aircraft in accordance with para 9-3-2, Separation Minima.
		<p class="note">NOTE: The FAA has no jurisdictional authority over the use of non-joint use prohibited/restricted/warning area airspace; therefore, clearance cannot be issued for flight therein without the appropriate approval.</p></li>
</ol>

</section>

<section id="s4">
<h2><a href="#chapters">Section 4. Fuel Dumping</a></h2>

<h3 id="9-4-1"><a href="#s4">9-4-1. INFORMATION REQUIREMENTS</a></h3>
<p>When information is received that an aircraft plans to dump fuel, determine the route and altitude it will fly and the weather conditions in which the operation will be conducted.</p>

<h3 id="9-4-2"><a href="#s4">9-4-2. ROUTING</a></h3>
<p>Except when it is dumping fuel for emergency reasons, an aircraft in either VFR or IFR conditions may be requested to fly a different route.</p>

<h3 id="9-4-3"><a href="#s4">9-4-3. ALTITUDE ASSIGNMENT</a></h3>
<p>If an aircraft is dumping fuel in IFR conditions, assign an altitude at least 2,000 feet above the highest obstacle within 5 miles of the route or pattern being flown.</p>

<h3 id="9-4-4"><a href="#s4">9-4-4. SEPARATION MINIMA</a></h3>

<p>Separate known aircraft from the aircraft dumping fuel as follows:</p>
<ol>
	<li>IFR aircraft by one of the following:
		<ol>
			<li>1,000 feet above it; or in accordance with para 4-5-1, Vertical Separation Minima, whichever is greater.</li>
			<li>2,000 feet below it. 3. 5 miles radar.</li>
			<li>5 miles laterally.</li>
		</ol></li>
	<li>VFR radar-identified aircraft by 5 miles and in accordance with para 5-6-1, Application.</li>
</ol>

<h3 id="9-4-5"><a href="#s4">9-4-5. INFORMATION DISSEMINATION</a></h3>

<ol>
	<li>If you are in contact with an aircraft when it starts dumping fuel, inform other controllers and facilities which might be concerned. Facilities concerned must broadcast an advisory on appropriate radio frequencies at 3-minute intervals until the dumping stops.
		<ul class="phraseology">
			<li>PHRASEOLOGY</li>
			<li>ATTENTION ALL AIRCRAFT.</li>
			<li>FUEL DUMPING IN PROGRESS OVER (location) AT (altitude) BY (type aircraft) (flight direction).</li>
		</ul></li>
	<li>Broadcast a terminating advisory when the fuel dumping operation is completed.
		<ul class="phraseology">
			<li>PHRASEOLOGY</li>
			<li>ATTENTION ALL AIRCRAFT.</li>
			<li>FUEL DUMPING OVER (location) TERMINATED.</li>
		</ul></li>
</ol>

</section>

<section id="s5">
<h2><a href="#chapters">Section 5. Jettisoning of External Stores</a></h2>

<h3 id="9-5-1"><a href="#s5">9-5-1. JETTISONING OF EXTERNAL STORES</a></h3>

<p>At locations where a drop area has been established for radar assistance in jettisoning of external stores, provide vectoring service upon request to:</p>
<ul class="note">
	<li>NOTE:</li>
	<li>1. Where required, a mutually satisfactory drop area for the jettisoning of external stores will be determined by radar-equipped towers and centers in cooperation with the local USAF units, Air Division, or civil operators and civil aircraft companies concerned.</li>
	<li>2. FAA and Headquarters, USAF, have agreed to allow FAA facilities to vector USAF, Air Force Reserve, and Air National Guard aircraft for jettisoning of all external stores; i.e., tip tanks, JATO racks, special weapons, etc. Any similar vectoring service given to civil operators and civil aircraft companies operating Air Force type aircraft requires written agreement between the FAA and the user to relieve the FAA of possible liability. The regional counsel’s office acts for FAA in executing this agreement.</li>
</ul>
<ol>
	<li>USAF, ANG, and Air Force Reserve aircraft at any time.</li>
	<li>Civil operators and civil aircraft when a written agreement is in effect for your location.</li>
</ol>

</section>

<section id="s6">
<h2><a href="#chapters">Section 6. Unmanned Free Balloons</a></h2>

<h3 id="9-6-1"><a href="#s6">9-6-1. APPLICATION</a></h3>

<figure id="fig961">
	<figcaption>FIG 9-6-1 Shapes of 11 Million Cubic Feet Balloon at Various Altitudes</figcaption>
    <img src="/assets/711065/images/fig9-6-1.png" alt="FIG 9-6-1 Shapes of 11 Million Cubic Feet Balloon at Various Altitudes"/>
</figure>

<p>Apply the following procedures, as appropriate, when unmanned free balloons are within airspace for which you have control jurisdiction:</p>
<p class="note">NOTE: These procedures apply to unmanned free balloons that carry payloads as described in 14 CFR Section 101.1(a)(4). Payloads may weigh several hundred pounds and the physical shape of the balloons change at various altitudes/flight levels. (See FIG 9-6-1.) Balloon and payload ascend at an average rate of 400 feet a minute. Over the descent area, the payload is normally released from the balloon and descends by parachute at a minimum rate of 1,000 feet a minute. The balloon is normally deflated automatically when the payload is released. The operator is required to advise ATC 1 hour in advance of descent in accordance with 14 CFR Section 101.39.</p>
<ol>
	<li>Post the balloon flight on flight progress strips along the planned trajectory and revise routing as tracking/position reports require.
		<p class="note">NOTE: The prelaunch notice information should be posted on flight progress strips for planning and operational purposes.</p></li>
	<li>Radar flight follow balloons to the extent that equipment capabilities permit. If radar flight following is not possible, tracking should be attempted by communication with the “chase plane,” telephone contact with the operator, pilot, or ground observation reports.
		<p class="note">NOTE: Some operators have equipped their balloons with transponder beacons in addition to a radar reflection device or material required by 14 CFR Section 101.35, but at cruise altitude, the balloon’s communications equipment and transponder, if so equipped, are operated intermittently to conserve battery energy.</p></li>
	<li>With pilot concurrence, provide separation between aircraft and balloons when you are satisfied that the balloon information is sufficiently reliable to provide the service. Do not attempt to separate aircraft from the balloon by using vertical separation unless you have accurate balloon altitude information.</li>
	<li>Provide traffic advisories to all affected aircraft during initial contact specifying the balloon’s known or estimated position, direction of movement, and altitude as “unknown” or “reported,” as appropriate.
		<p class="note">NOTE: Unless ATC requires otherwise, operators of unmanned free balloons are required to monitor the course of the balloon and record its position at least every two hours. As required in 14 CFR Section 101.39a, balloon position reports are not forwarded by the operator unless requested by ATC.</p>
		<ul class="phraseology">
			<li>PHRASEOLOGY</li>
			<li>UNMANNED FREE BALLOON OVER (name of location),</li>
			<li>or</li>
			<li>ESTIMATED OVER (name of location), MOVING (direction of movement).</li>
			<li>LAST REPORTED ALTITUDE AT (altitude as reported by the operator or determined from pilot report),</li>
			<li>or</li>
			<li>ALTITUDE UNKNOWN.</li>
		</ul></li>
	<li>To transfer flight following responsibility of balloons between facilities or between controllers, forward the following information when available:
		<ul class="reference">
			<li>REFERENCE</li>
			<li><a href="https://www.law.cornell.edu/cfr/text/14/101.37" target="_blank">14 CFR Section 101.37, Notice Requirements.</a></li>
			<li><a href="https://www.law.cornell.edu/cfr/text/14/101.39" target="_blank">14 CFR Section 101.39, Balloon Position Reports.</a></li>
		</ul>
		<ol>
			<li>Identification and type; e.g., Flight 804 Balloon.</li>
			<li>Last known position and altitude.</li>
			<li>General direction of movement and speed.</li>
			<li>ETA over facility boundary, sector boundary, or other point if believed to be reasonably accurate.</li>
			<li>Other pertinent information.</li>
			<li>If in radar contact, physically point out the target to the receiving controller.</li>
			<li>The name and the telephone number of the location where tracking is being accomplished.</li>
		</ol>
		<ul class="reference">
			<li>REFERENCE</li>
			<li><a href="#9-6-2">FAA Order JO 7110.65, Para 9-6-2, Derelict Balloons.</a></li>
		</ul></li>
</ol>


<h3 id="9-6-2"><a href="#s6">9-6-2. DERELICT BALLOONS</a></h3>

<p>Balloons become derelict when a moored balloon slips its mooring and becomes a hazard to air navigation or when an unmanned free balloon flight cannot be terminated as planned. When this occurs:</p>
<ol>
	<li>In the case of a moored balloon which has slipped its moorings, issue traffic advisories.</li>
	<li>In the case of an unmanned free balloon, flight follow the balloon and, to the extent possible, provide aircraft under your control separation from the balloon.</li>
	<li>Forward balloon position information received from pilot reports or derived from radar returns to your supervisor for further dissemination.</li>
	<li>If radar contact with the balloon is lost, broadcast an advisory to all aircraft operating in the airspace affected by the derelict balloon at 10-minute intervals continuing until the derelict balloon is no longer a factor.
		<ul class="phraseology">
			<li>PHRASEOLOGY</li>
			<li>ADVISORY TO ALL AIRCRAFT.</li>
			<li>DERELICT BALLOON REPORTED IN THE VICINITY OF (location),</li>
			<li>or</li>
			<li>ESTIMATED IN VICINITY OF (location),</li>
			<li>or</li>
			<li>REPORTED OVER (location),</li>
			<li>or</li>
			<li>RADAR REPORTED OVER (location).</li>
			<li>LAST REPORTED ALTITUDE/FLIGHT LEVEL AT (altitude/flight level as reported by operator or pilot report),</li>
			<li>or</li>
			<li>ALTITUDE/FLIGHT LEVEL UNKNOWN.</li>
		</ul></li>
	<li>Transfer flight following responsibility as outlined in para 9-6-1, Application, subpara e.
		<ul class="reference">
			<li>REFERENCE</li>
			<li>FAA Order JO 7210.3, Para 18-5-2, Derelict Balloons/Objects.</li>
		</ul></li>
</ol>

</section>

<section id="s7">
<h2><a href="#chapters">Section 7. Parachute Operations</a></h2>

<h3 id="9-7-1"><a href="#s7">9-7-1. COORDINATION</a></h3>

<p>Coordinate any pertinent information prior to and at the end of each parachute jump or series of jumps which begins or ends in your area of jurisdiction with other affected ATC facilities/sectors.</p>
<p>NOTE: 14 CFR Section 105.15 prescribes the information required from each person requesting authorization or submitting notification for nonemergency parachute jumping activity.</p>
<ul class="reference">
	<li>REFERENCE</li>
	<li>FAA Order JO 7210.3, Para 18-4-1, Nonemergency Parachute Jump Operations.</li>
	<li><a href="https://www.law.cornell.edu/cfr/text/14/part-105" target="_blank">14 CFR Part 105, Parachute Operations.</a></li>
</ul>
	
<h3 id="9-7-2"><a href="#s7">9-7-2. CLASS A, CLASS B, AND CLASS C AIRSPACE</a></h3>

<ol>
	<li>Authorize parachute operations only within airspace designated for the jumping activity.</li>
	<li>Separate aircraft, other than those participating in the jump operation, from the airspace authorized for the jumping activity.</li>
	<li>Impose, as necessary, any conditions and restrictions which in your judgment would promote the safety of the operation.</li>
</ol>
<ul class="reference">
	<li>REFERENCE</li>
	<li><a href="https://www.law.cornell.edu/cfr/text/14/105.25" target="_blank">14 CFR Section 105.25, Parachute Operations in Designated Airspace.</a></li>
</ul>

<h3 id="9-7-3"><a href="#s7">9-7-3. CLASS D AIRSPACE</a></h3>

<p><span class="typeheader">TERMINAL</span></p>
<p>Handle requests to conduct jump operations in or into Class D airspace in which there is a functioning control tower as follows:</p>
<ol>
	<li>Authorize parachute jumping with respect to known or observed traffic.</li>
	<li>Issue advisory information to the jump aircraft and to nonparticipating aircraft as necessary for the safe conduct of the jump operation.</li>
</ol>

<h3 id="9-7-4"><a href="#s7">9-7-4. OTHER CONTROL AIRSPACE</a></h3>
<p>Handle notifications to conduct jump operations in other Class E airspace as follows:</p>
<ol>
	<li>Issue a traffic advisory to the jump aircraft before the jump. Include aircraft type, altitude, and direction of flight of all known traffic which will transit the airspace within which the jump will be conducted.
		<p class="note">NOTE: 14 CFR Section 105.13, Radio Equipment and Use Requirements, prescribes that, except when otherwise authorized by ATC, parachute jumping is not allowed in or into Class E airspace unless radio communications have been established between the aircraft and the FAA ATC facility having jurisdiction over the affected airspace of the first intended exit altitude at least 5 minutes before the jumping activity is to begin for the purpose of receiving information in the aircraft about known air traffic in the vicinity of the jump aircraft.</p></li>
	<li>Issue advisories to all known aircraft which will transit the airspace within which the jump operations will be conducted. Advisories must consist of the location, time, duration, and altitude from which the jump will be made.</li>
	<li>When time or numbers of aircraft make individual transmissions impractical, advisories to nonparticipating aircraft may be broadcast on appropriate control frequencies, or when available, the ATIS broadcast.</li>
	<li>When requested by the pilot and to the extent possible, assist nonparticipating aircraft to avoid the airspace within which the jump will be conducted.</li>
</ol>

</section>

<section id="s8">
<h2><a href="#chapters">Section 8. Unidentified Flying Object (UFO) Reports</a></h2>

<h3 id="9-8-1"><a href="#s8">9-8-1. GENERAL</a></h3>

<ol>
	<li>Persons wanting to report UFO/unexplained phenomena activity should contact a UFO/ unexplained phenomena reporting data collection center, such as the National UFO Reporting Center, etc.</li>
	<li>If concern is expressed that life or property might be endangered, report the activity to the local law enforcement department.</li>
</ol>

</section>

</article>
</main>
</body>
</html>