AFI 13-212 Luke Sup 1.pdf
Air Force Instruction PDF 12 MB Posted
- Attached to
- Air Combat Training System (ACTS)
- Solicitation number
- FA3002-10-R-0009
About this file
Air Force Instruction 13-212 Luke AFB Sup 1 (31 Aug 2009) Range Planning and Operations as a part of Q A (Round 2 Question 14)
View the file
Other versions and copies of AFI 13-212
| File | Revision | Posted | Attached to |
|---|---|---|---|
| AFI13-212_ACCSUP_MOUNTAINHOMEAFB_ADD_A.pdf | Revision not stated | Primary Training Ranges (PTR) OM&S |
Who attaches AFI 13-212
Other files
Show all 48
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
BY ORDER OF THE COMMANDER
56TH FIGHTER WING (AETC)
AIR FORCE INSTRUCTION 13-212
LUKE AIR FORCE BASE
Supplement 1
31 AUGUST 2009
Space, Missile, Command and Control
RANGE PLANNING AND OPERATIONS
COMPLIANCE WITH PUBLICATION IS MANDATORY
ACCESSIBILITY: This publication is available digitally on the 56 RMO Knowledge Now website at https://afkm.wpafb.af.mil/ARO. If you lack access, contact your Publications Management Office and the office of primary responsibility.
RELEASABLITY: This publication is limited to official business only.
OPR: 56 RMO/DO Certified by: 56 RMO/CC (YC-03 James R. Uken) Supersedes AFI 13-212 Volume 1 Pages: 170 LAFB Sup 1, 3 December 2007
Air Force Instruction (AFI) 13-212, 16 November 2007, Range Planning and Operations, is supplemented as follows. Ensure that all records created as a result of processes prescribed in this publication are maintained in accordance with Air Force Manual (AFMAN) 33-363, Management of Records, and disposed of in accordance with Air Force Records Information Management System (AFRIMS) Records Disposition Schedule (RDS) located at https://www.my.af.mil/gcss-af61a/afrims/afrims/. Submit an AF Form 847, Recommendation for Change of Publication to the OPR to recommend changes to this publication.
SUMMARY OF REVISIONS
This document is substantially revised and must be completely reviewed. This supplement applies to all personnel utilizing the USAF managed portion of the Barry M. Goldwater Range.
AFI 13-212_LAFBSUP_1 31 AUGUST 2009 2
Chapter 1--RESPONSIBILITIES AND SCHEDULING 8
1.1 General Description
Figure 1.1. Barry M. Goldwater Range
Figure 1.2. BMGR East, BMGR West and Surrounding Areas
1.2. Responsibilities
1.3. User Classification
1.4. Scheduling
1.5. Daily Operations Oversight
1.6. Maintenance
1.7. Range Clearance and EOD (Explosive Ordnance Disposal) Operations
1.8. Environmental Resources
1.9. Safety
1.10. Annual Range Board
1.11. Arizona AOR Special Instructions (SPINs)
1.12. Fire Fighting
1.13. Reports
Chapter 2—BMGR EAST DESCRIPTION / CAPABILITIES AND INFORMATION 20
2.1. General
Figure 2.1. BMGR East Area and Sub Ranges
2.2. Restricted Airspace
Figure 2.2. BMGR East Special Interest Areas and Reference Points
2.3. SELLS Military Operating Area (MOA) / Air Traffic Control Assigned Airspace
(ATCAA)
Figure 2.3. SELLS MOA/ATCAA; Subdivision Coordinates
2.4. AR-647 and AR-647A
2.5. Tactical Drop and Assault Landing Zones
Figure 2.4. Aux-6 Traffic Patterns
2.6. Command, Control, and Communication
2.7. Air Combat Training Systems (ACTS)
2.8. Threat Simulation
Figure 2.5. UMTE and RSS Locations
2.9. Countermeasures Employment
Table 2.1. Chaff Authorizations
3 AFI 13-212_LAFBSUP_1 31 AUGUST 2009
Table 2.2. Fire Danger Forecast / Flare Restrictions
Table 2.3. LUU-Series Flare and Illuminating Rocket Authorizations
2.10. Large Scale Target Sensor System (LSTSS)
2.11. Tactical Data Link (TDL)
2.12. Weapons Employment
Figure 2.6. Non-Military Lands Underlying BMGR East Complex Airspace
2.13. Laser Operations
2.14. Tactical Air Control Parties (TACP)
2.15. Bird Watch Procedures
2.16. Contingencies within BMGR East
2.17. Southwest Data Link Range Operations and Scheduling
Chapter 3—MANNED RANGES 43
3.1. General
Figure 3.1. Manned Range Locations within BMGR East
3.2. Airspace Defined
Figure 3.2. Typical Manned Range Pattern Layouts
3.3. Classes of Ranges
3.4. Communications
3.5. Manned Ranges Entry/Exit/Holding Procedures
Figure 3.3. Manned Range Entry/Exit/Holding Procedures
3.6. Weather Requirements
3.7. Target Specifics
Figure 3.4. Typical Manned Range Layout
3.8. Authorized Ordnance
3.9. Ordnance Procedures
3.10. Manned Range Pattern Considerations
3.11. Manned Range Delivery Considerations
3.12. Night Weapons Delivery
Figure 3.5. Manned Range Night Lighting Schemes
3.13. LANTIRN (Low Altitude Navigation and Targeting, Infrared for Night) Procedures
3.14. Manned Range Laser Procedures
3.15. Air Commander’s Pointer (ACP) Procedures
AFI 13-212_LAFBSUP_1 31 AUGUST 2009 4
3.16. Range 1
3.17. Range 2
3.18. Range 3
3.19. Range 4
Figure 3.6. Range 1
Figure 3.7. Range 2
Figure 3.8. Range 3
Figure 3.9. Range 4
Chapter 4--UNMANNED TACTICAL RANGES 61
4.1. General
Figure 4.1. BMGR East Restricted Area Layout
4.2. Airspace Defined
4.3. Classes of Ranges
4.4. Communication
4.5. Target Specifics
4.6. Authorized Ordnance
4.7. Delivery Considerations
4.8. Night Tactical Range Procedures
4.9. Laser Procedures
4.10. TACP/JTAC Considerations
4.11. Air-To-Air Range
4.12. NTAC Range
Figure 4.2. NTAC Area
4.13. STAC Range
Figure 4.3. STAC Area
4.14. ETAC Range
Figure 4.4. ETAC Area
Chapter 5--RANGE CONTROL OFFICER (RCO) PROCEDURES 76
5.1. General
5.2. Tour of Duty
5.3. RCO Training, Checkout, and Certification
5.4. Air-to-Air Range Control Officer Program
5.5. Instructions, Regulations, and Manuals
5 AFI 13-212_LAFBSUP_1 31 AUGUST 2009
5.6. Other Range Publications/Documents
5.7. Range Opening Procedures
5.8. Operations
Table 5.1. Manned Range Ground Access Restrictions
5.9. Fouls/Dangerous Passes
5.10. Weapons Delivery Scoring
5.11. Curtailed Range Operations
5.12. Normal Range Closing
5.13. Reports and Logs
Chapter 6--SURFACE ACCESS ON THE GOLDWATER RANGE 85
6.1. General
6.2. Overview
6.3. Standard Control Areas
6.4. Critical Control Areas
Figure 6.1. BMGR East Containment Areas
6.5. Tours and Visit Requests
Chapter 7—RANGE OPERATIONS COORDINATION CENTER (ROCC) 90
7.1. General
7.2. Scheduling Responsibilities
7.3. Data Gathering Responsibilities
7.4. Range and Airspace Supervision
Chapter 8—GILA BEND AIR FORCE AUXILLIARY FIELD PROCEDURES 94
8.1. General Description
Figure 8.1. GBAFAF Layout
8.2. Aircraft Priorities
8.3. Operating Hours
8.4. Runway Utilization
8.5. Arresting System
8.6. Barrier Status
8.7. Airfield Lighting
Table 8.1. GBAFAF Lighting
8.8. Control of Ground Traffic and Vehicle Operations
8.9. Traffic Patterns
AFI 13-212_LAFBSUP_1 31 AUGUST 2009 6
Figure 8.2. GBAFAF Typical Overhead Pattern
8.10. Overhead/Rectangular Pattern Entry Procedures
8.11. Simulated Flameout (SFO) Procedures
8.12. GBAFAF Departures
Figure 8.3. GBAFAF VFR West Departure
Figure 8.4. GBAFAF VFR East Departure
8.13. Helicopter Operations
8.14. Reduced Runway Separation
Table 8.2. RRS for Similar Type Airframe (F-16 to F-16, A-10 to A-10)
8.15. Drop Zone (DZ) Operations
8.16. Night Vision Goggle (NVG) Operations
Figure 8.5. GBAFAF Night VFR Straight-in Pattern (NVG Pattern)
8.17. GBAFAF Emergency Procedures
8.18. Runway Change Procedures
8.19. Air Evacuation Aircraft Procedures
8.20. Tower and Airfield Management Operations Coordination
8.21. Civil Aircraft Use of GBAFAF Facilities
8.22. Hijack/Theft Response
Chapter 9—PRESCRIBED AND ADOPTED FORMS 112
9.1. Forms Prescribed
9.2. Forms Adopted
Attachment 1—GLOSSARY OF REFERENCES AND SUPPORTING
INFORMATION
Attachment 2—BMGR EAST CASUAL USER RANGE / AIRSPACE REQUEST
FORM
Attachment 3—BMGR EAST INCIDENT REPORT
Attachment 4—BMGR EAST WAYPOINT COORDINATES
Attachment 5—BMGR EAST MODE 2 STANDARD SQUAWKS
Attachment 6—BMGR EAST FREQUENCY MATRIX
Attachment 7—TACTICAL TARGET-WEAPONS ALLOWANCE TABLE
Attachment 8—LASER SYSTEMS CERTIFIED FOR USE ON BMGR EAST
Attachment 9—MANNED RANGE TARGET AND REFERENCE POINT
COORDINATES
7 AFI 13-212_LAFBSUP_1 31 AUGUST 2009
Attachment 10—TACTICAL RANGE TARGET GROUP LAYOUTS AND TARGET
CENTROID COORDINATE DATA
Attachment 11—RCO CERTIFICATE FORMAT FOR BMGR EAST
Attachment 12—RCO QUALIFICATIONS AND REQUIREMENTS
Attachment 13—GROUND PARTY HOLD HARMLESS AGREEMENT
Attachment 14—RANGE OPERATIONS COORDINATION CENTER TRAINING
SCHEDULE
AFI 13-212_LAFBSUP_1 31 AUGUST 2009 8
Chapter 1
RESPONSIBILITIES AND SCHEDULING
1.1. General Description. This supplement provides information and procedures for all units operating in the USAF managed portion of the Barry M. Goldwater Range (BMGR). This area is referred to as BMGR East, which is comprised of the eastern segment of the BMGR, SELLS Military Operating Area (MOA)/Air Traffic Control Assigned Airspace (ATCAA), Restricted Areas 2301E, 2304 and 2305, and Gila Bend Air Force Auxiliary Airfield (GBAFAF). (Figure 1.1)
Figure 1.1. Barry M. Goldwater Range.
1.1.1. BMGR Defined. Congress divided the BMGR into eastern and western segments in 1999 and assigned management authority to the Secretaries of the Air Force and Navy, respectively (Public Law 106-65; referred to hereinafter as the MLWA of 1999). The BMGR segments are:
the Gila Bend (BMGR East) segment, which is approximately 1,050,000 acres; and the Yuma (BMGR West) segment, which is approximately 691,760 acres. The Air Force controls the land and airspace of the Gila Bend segment (administered through the 56 Fighter Wing Range Management Office (56 RMO) at Luke Air Force Base AFB), and the Marine Corps controls the Yuma segment (administered by the Range Management Division, Marine Corps Air Station
9 AFI 13-212_LAFBSUP_1 31 AUGUST 2009
(MCAS) Yuma). A five-mile wide air and ground buffer zone along the R2301E and R2301W boundary separates the two segments.
1.1.1.1. Gila Bend Segment (BMGR East). The eastern portion of the BMGR underlies a portion of R-2301E, R-2304, and R-2305, on either side of Arizona State Route (SR) 85, as shown in Figure 1.2.
Figure 1.2. BMGR East, BMGR West and Surrounding Areas
1.1.1.2. Yuma Segment (BMGR West). The western segment of the BMGR (Figure 1.2.)
underlies a portion of R-2301W (west of a line from N32-05.500 W113-30.000 to N32-44.250 W113-41.000). Scheduling control of the BMGR West and R-2301W is delegated to Yuma Range Scheduling; correspondence may be sent to:
Commanding Officer Attn: Range Scheduling H & HS ATC Box 99160 MCAS Yuma, AZ 85369-9160 COMM Phone: 520-269-2214/15 DSN Phone 269-2214/15 FAX 2964.
1.1.2. For purposes of this document, all land and special use airspace identified in para 1.1. are hereto referred to as BMGR East. Withdrawn land under USAF jurisdiction is hereto referred to as BMGR East.
AFI 13-212_LAFBSUP_1 31 AUGUST 2009 10
1.2. Responsibilities.
1.2.1. Commanders. Commanders of all units and agencies which operate aircraft or perform ground operations within the boundaries of BMGR East will ensure compliance with the provisions of this supplement by all personnel within their jurisdiction.
1.2.2. Units. Units requesting flight operations on BMGR East will have thoroughly reviewed this supplement for mission planning, and will make contact with the appropriate point of contact (POC) if intending to perform operations not specifically described in this supplement. All aircrew will review the daily Range Notice to Airmen (NOTAMs) at https://afkm.wpafb.af.mil/BMGR-E prior to operating in BMGR East. All requests outside the scope of this supplement should be in writing (e-mail can suffice) to the appropriate POC.
1.2.3. Range Operations. For primary users of BMGR East, tactical aviation operations are not allowed without Gila Bend Air Force Auxiliary Field (GBAFAF) being open and operational for emergency services and the Range Operations Coordination Center (ROCC), call sign Snakeye, being open for range and airspace control and advisory service to users (see paragraph 2.6).
Other flight operations within BMGR East without GBAFAF open will be considered on a case-by-case basis. Waiver authority lies with the 56 RMO Director (56 RMO/CC). Contact 56 RMO/ASMS for further information (see paragraph 1.2.4.3.5. below).
1.2.4. Office of Primary Responsibility (OPR). The 56 FW RMO has primary responsibility for all BMGR East issues and concerns. The 56 RMO Director of Operations (56 RMO/DO) is the primary POC for all operations relating to BMGR East.
1.2.4.1. Daily Management. The BMGR East is supported by contract operations under the direction of the 56 RMO and Quality Assurance Evaluators (QAE). Authority for daily management of BMGR East, range maintenance, scoring, security, operations support and management of GBAFAF is delegated to the GBAFAF lead QAE who also shares range operating officer duties with the 56 RMO/DO.
1.2.4.2. Quality Assurance. Daily oversight and evaluation of the contractor’s performance is assigned to the QAEs, who operate at GBAFAF and Luke AFB, under the supervision and control of the 56 RMO/DO. To coordinate any surface activity or any use of the GBAFAF, see Chapter 7 and contact the appropriate QAE office at:
Operations and Maintenance:
56 RMO/QAE
HCO1 Box 20 3096 1st St.
Gila Bend AFAF, AZ 85337 Phone: (DSN) 896-5261 (Comm) 928-683-6261 FAX: (DSN) 896-5239 (Comm) 928-683-6239
Communications and Instrumentation:
56 RMO/QAE
7046 N Fighter Country Ave.
Luke AFB, AZ 85309-1934
11 AFI 13-212_LAFBSUP_1 31 AUGUST 2009
1.2.4.3. 56 RMO OPRs.
1.2.4.3.1. 56 RMO Director. The 56 RMO Director is the overall Range Operating Authority (ROA) for issues related to BMGR East. Correspondence should be sent to:
56 RMO/CC
7224 N. 139th Drive Luke AFB AZ 85309-1934 Phone: (DSN) 896-8520 (Comm) 623-856-8520 FAX: (DSN) 896-7096 (Comm) 623-856-7096 Range Management Homepage https://afkm.wpafb.af.mil/aro
1.2.4.3.2. 56 RMO/DO. The 56 RMO/DO is responsible for all operations on the BMGR East and/or within the airspace managed by the 56 RMO for the 56 FW. The 56 RMO/DO shares Range Operations Officer (ROO) duties as defined by AFI 13-212, Range Planning and Operations, with the GBAFAF QA. Additionally, 56 RMO/DO is the POC for the BMGR East Annual Range Board, the contractors at GBAFAF, Range Incidents, and all other agencies responsible for managing various aspects of the airspace and range complex. Correspondence should be sent to:
56 RMO/DO
7224 N. 139th Drive Luke AFB, AZ 85309-1934 Phone: (DSN) 896-8790 (Comm) 623-856-8790 FAX: (DSN) 896-7096 (Comm) 623-856-7096
1.2.4.3.3. 56 RMO/ARO. The 56 RMO/ARO (Air Range Operations) is the single POC for operational employment within BMGR East. Additionally, the 56 RMO/ARO office is designated the Range Liason Officer (RLO) as defined by AFI 13-212, Range Planning and Operations. As RLO, the 56 RMO/ARO is responsible for the Range Control Officer (RCO) Qualification and Training program.
56 RMO/ARO
7224 N. 139th Drive Luke AFB, AZ 85309-1934 Phone: (DSN) 896-8813 (Comm) 623-856-8813 FAX: (DSN) 896-7096 (Comm) 623-856-7096
1.2.4.3.4. 56 RMO/ASM. The 56 RMO/ASM (Airspace Management Office) is responsible for coordinating all airspace issues, including Letters of Agreement (LOAs) with the Federal Aviation Administration (FAA) and other users. 56 RMO/ASM also coordinates counter measures and Electronic Counter Measures (ECM) clearances and authorizations, as well as all activities on the Military Training Routes (MTRs) assigned to the 56th Fighter Wing. Send correspondence to:
56 RMO/ASM
7224 N. 139th Drive Luke AFB, AZ 85309-1934
AFI 13-212_LAFBSUP_1 31 AUGUST 2009 12
Phone: (DSN) 896-5855 (Comm) 623-856-5855 FAX: (DSN) 896-7096 (Comm) 623-856-7096
1.2.4.3.5. 56 RMO/ASMS. The 56 RMO/ASMS (Range Scheduling) is responsible for managing scheduling issues and procedures, and is responsible for overall allocation and scheduling of 56 FW ranges, airspace and MTRs. ASMS interfaces with the Joint Terminal Attack Controller (JTAC) parties, ASM, ARO, ACMI and QAE officers. Request airspace or range time through 56 RMO Range Scheduling (56 RMO/ASMS) at:
56 RMO/ASMS
7224 N. 139th Drive Luke AFB, AZ 85309-1934 Phone: (DSN) 896-7654/3330 (Comm) 623-856-7654/3330 FAX: (DSN) 896-7655 (Comm) 623-856-7655 Range Scheduling Homepage: https://afkm.wpafb.af.mil/BMGR-E
1.3. User Classification. Priority is given to the 23 flying squadrons deemed “Regular Users” who claim the BMGR-E as their primary training range.
1.3.1. Regular Users. Units of the 56 FW at Luke AFB, 355 FW, 305 RQS (AFRES), and 563 RQG at Davis-Monthan AFB, 162 FW (ANG) at Tucson International Airport to include the ANG AFRC Test Center and ANG SNOWBIRD operations, Western Army National Guard Aviation Training Site, Peace Vanguard, 1-285 AHBE (ARNG), at Silverbell Army Heliport (Marana, AZ), and the 189th CSB, at Papago Army Airfield in Phoenix are considered regular users. All other units are classified as Casual Users or Hosted Units. Regular units can use their rotating priority weeks for any unit they host and these units will be supported appropriately, however, they are not guaranteed 100 percent airspace and range utilization requested.
1.3.2. Priority. The three primary regular user Wings (56 FW, 355 FW and 162 FW) rotate as the 'Priority Wing' for a given week. The wing afforded top priority one week, moves to the 2nd position the following week, the 3rd position the week after that and back to the 1st position again. Typically, range scheduling can accommodate all regular users within 1 hour of their requested times. Priority does not guaranty 100 percent of range/airspace requested based on all user requests. Regular user range/airspace requirements are assigned with the following priorities:
1.3.2.1. Higher headquarters missions (e.g. ORI), as tasked.
1.3.2.2. WTI, ORE, and LFE.
1.3.2.3. Tanker associated requirements (not the track).
1.3.2.4. Missions supported by deployed DACT assets.
1.3.2.5. Wing weapons competitions.
1.3.3. Casual User. Casual Users include all units not specifically designated as regular users to include out-of-state Air National Guard; other U.S. Military Services and foreign military units.
13 AFI 13-212_LAFBSUP_1 31 AUGUST 2009
Casual users are scheduled based upon availability of range time after the regular users have finalized their requirements.
1.3.4. Hosted Unit. A Hosted Unit refers to a unit deployed to a ‘regular user’ base and hosted by a regular user flying unit. Hosted units may request and receive range times for missions not flown in conjunction with their hosting unit; the scheduling priority, however, is below regular users. The host unit is responsible for ensuring their visitors are familiar with local area procedures and complying with this range instruction.
1.3.5. 162d Fighter Wing Operation Snowbird (162 FW/OSB). Snowbird is aligned with 162 FW rotating priority.
1.3.5.1. ANG units being supported by the 162 OSB specifically for AEF pre-deployment training will receive priority 1 status per 1.3.2.1., above as a regular user for use of BMGR-E Complex provided 56 RMO/ASMS is given a minimum of 45 days prior notice. Note: When less than 45 days notice is given, 56 RMO will make every effort to accommodate however, status cannot be guaranteed.
1.3.5.2. 162 FW/OSB hosted US units, other than AEF pre-deployment, i.e. other ANG, other U.S. military services will be afforded regular status IAW 1.3.5.1., above.
1.3.5.3. 162 OSB hosted international or friendly foreign nation units will be afforded regular status but will not necessarily have priority over primary regular users (USAF/NG). Given situation, foreign military units will be supported to the maximum extent possible.
1.3.5.3. 162 OSB hosted international or friendly foreign nation units will be charged range usage fees per the United States Code, Title 22, Chapter 39 Arms Export Control Act.
Coordination and arrangements to include funds transfer must be finalized prior to foreign operations within the BMGR-E Complex.
1.3.5.4. Due to the BMGR-E user demand/request dynamics it is incumbent on 162 OSB to coordinate and communicate hosting schedules as far in advance as possible. In particular, in-coming units with special requirements, i.e. special weapons need to coordinated with 56 RMO/ARO during deployment planning; BMGR-E Joint Terminal Air Control (JTAC) ground parties scheduling occurs in many cases a year in advance—162 OSB should reference the 56 RMO/ASMS JTAC schedule when determining level of support capability. Based on previously scheduled special request range operations, 56 FW/RMO may not be able to fully support 162 OSB requests.
1.4. Scheduling. BMGR East use must be coordinated with 56 RMO/ASMS. Any ground operations must also be coordinated with range scheduling. Any operation involving GBAFAF must be coordinated with 56 RMO/ASMS and the 56 RMO/QAE offices at GBAFAF (see paragraph 1.2.4.2.). Scheduling activity the “Day of” will be coordinated through Snakeye (Chapter 7).
1.4.1. Range scheduling will maintain the Range Scheduling website located at https://afkm.wpafb.af.mil/BMGR-E.
AFI 13-212_LAFBSUP_1 31 AUGUST 2009 14
1.4.2. Range scheduling will annotate number and type aircraft, LIVE ordnance, LASER and NVG on the schedule when each unit calls to confirm the Next-Day schedule.
1.4.3. Range scheduling will publish and distribute the Range NOTAMs. The range schedule is available to all units at https://afkm.wpafb.af.mil/BMGR-E . Units may request the schedule via email by submitting a valid email address to Range.Scheduling@luke.af.mil.
1.4.4. Range Availability. From 1 October through 31 March, BMGR East normal operating hours are (except Federal Holidays) from 0730-2330L Mountain Standard Time (MST), Monday through Friday, and 0800-1700L MST on two ANG/AFRES flying weekend days per month.
From 01 April through 30 September, BMGR East normal operating hours are (except Federal Holidays) from 0700-2300L MST, Monday through Friday, and 0800-1700L MST on two ANG/AFRES flying weekend days per month. Arizona maintains MST all year round (no Daylight Savings Time [DST]), therefore, local time for the BMGR is always ZULU minus 7 hours. The weekend fly dates are published at the Range Scheduling website.
1.4.5. Confirming Range Times. Confirm range times with 56 RMO Range Scheduling between 48 hours prior to and 1000 hours (MST) local of the day prior to the scheduled range time. If not confirmed within this window, range times are taken back to fill other demands.
1.4.6. Obtaining Range Time Outside of Normal Hours. BMGR East time may be requested outside of the normal operating hours by coordinating with Range Scheduling. See Attachment 2 for the request format. Requests must be received at least 30 days in advance. Units will be charged for support (referred to as contract “call-outs”) outside normal operating hours. Funds must be transferred before confirming range times the day prior.
1.4.7. Casual User/Hosted Unit User Scheduling Procedures. Casual users/hosted units users should submit a written range request IAW Attachment 2 or online through the Range Scheduling website. All blanks must be properly filled in or the request will be delayed pending completion.
1.4.8. Casual User/Hosted Unit User Confirmation. Casual user/hosted units are not usually added to the schedule until approximately 10 days before the beginning of the week. Range times may be taken back under extraordinary circumstances. Range times not confirmed between 48 hours prior to and 1000L of the day prior, are taken back.
1.4.9. Unscheduled Users ("bootlegging"). Unscheduled users request entry onto a cold range by contacting Snakeye prior to takeoff, or Snakeye once airborne (see Appendix 6 for radio frequency information). Snakeye will coordinate with the appropriate RCO if an unscheduled manned range is requested. The RCO will notify base operations.
1.4.10. Manned Range Restrictions and Constraints.
1.4.10.1. 01 April through 30 September. Four manned ranges are available from sunrise plus 30 minutes, but no earlier than 0700 until sunset/1800, whichever occurs first, Monday through Friday. Night manned ranges are available from sunset/1800 (whichever occurs first) until 2230.
15 AFI 13-212_LAFBSUP_1 31 AUGUST 2009
1.4.10.2. 01 October through 31 March. Four manned ranges are available from sunrise plus 30 minutes, but no earlier than 0730 until sunset/1830, whichever occurs first, Monday through Friday. Night manned ranges are available from sunset/1830 (whichever occurs first) until 2300.
1.4.10.3. Add-ons. “Add-ons” are defined as requests made after 1600 of the workday prior.
Short-notice requests to add-on range times outside or beyond pre-scheduled range hours can be denied due to minimum notification time requirements to alert support crews.
1.4.10.4. Night Operations. All ranges are night capable. Ranges 1, 2 and 4 are the preferred night ranges. Range 3 is not normally used for night missions since the East Tactical range must also be scheduled to accommodate F-16 users and conflicts with the night Visual Flight Rules (VFR)/Night Vision Goggle (NVG) pattern at GBAFAF.
1.4.11. Events Requiring Coordination/Approval. JTAC employment, Drop Zone use, Assault Zone operations, ground employment, special type operations at GBAFAF and unique test requirements downrange are among the events requiring prior coordination and advanced approval. This list is not all inclusive. Contact the 56 RMO/ARO and 56 RMO/ASMS for coordination as required.
1.4.11.1. Specific Ordnance/LASER Requirements. Coordinate Live Drops/Live Fire/inert GBU-24/31/32/38 deliveries and combat laser use a minimum 48 hours prior to the day of the mission when the sortie(s) occurs on a weekday (M-F) and 7 days in advance to the mission date when the sortie(s) will occur on a weekend (S/S) or holiday. Employment of high explosive (HE) ordnance, inert GBU-24/31/32/38, or combat LASER is not authorized unless annotated as such on the range schedule. Some ordnance requires scheduling multiple areas to comply with WDZ Tool/SAFE-RANGE footprint restrictions.
1.4.11.2. Users that wish to employ munitions not listed in this supplement as ‘authorized ordnance’ will consult 56 RMO/ARO in advance to ensure that the munitions are approved for use on the targets selected for employment and that Explosive Ordnance Disposal (EOD) clearance teams are advised of the presence of these munitions and trained on any peculiar hazards they may present. Written approval of 56 RMO/CC is required for dropping live ordnance not included in the authorized ordnance in Attachment 2.
1.4.11.3. Dissimilar Aircraft/Large Force Employment (LFE) Missions. Missions with three or more different type aircraft, and/or missions with more than eight aircraft are considered large force employment missions. Casual user/hosted unit LFE mission commanders must receive briefing from the RMO/DO or a designated representative prior to execution. Contact RMO/ASMS a minimum of 1-week prior for coordination.
1.4.12. Ground Access Request. Refer to Chapter 6.
1.5. Daily Operations Oversight. Daily operations are under the supervision of the ROCC located at Luke AFB, AZ. ROCC specifics are defined in paragraph 2.6.
1.6. Maintenance. The 56 RMO is responsible for maintenance of BMGR East. Scheduled dates for range maintenance are coordinated by the contractor to be published annually NLT
AFI 13-212_LAFBSUP_1 31 AUGUST 2009 16
1 Aug of each year. The latest forecast range maintenance schedule may be found linked from the Range Scheduling Homepage at https://afkm.wpafb.af.mil/BMGR-E.
1.6.1. 75 Use-day Closure. Manned ranges are normally scheduled for a 75 use-day ordnance disposal on a Thursday and Friday, every 15 weeks.
1.6.2. Annual Closure. Manned and tactical ranges are scheduled for an annual ordnance disposal each year. Ordinarily, annual clearances require 7 weeks (tactical ranges) or 3 weeks (manned ranges). Typically, about 2 weeks are free between one ordnance disposal and the next.
The standard cycle is: Oct-Dec: STAC; Jan-Mar: NTAC; Mar-May: ETAC; June: Range 1;
July: Range 2; August: Range 3; September: Range 4.
1.7. Range Clearance and EOD (Explosive Ordnance Disposal) Operations. Under the 56th Civil Engineering Squadron (56 CES), the Chief, EOD Flight (56 CES/CED), is responsible for providing range clearance and EOD support for BMGR. 56 CES/CED is responsible for providing qualified personnel to conduct EOD Safety Briefings, upon unit commander's request, according to this publication. 56 CES/CED is responsible for determining if weather and fire hazard conditions preclude safe EOD operations. Detailed plans for each range clearance operation will be established by the EOD Team Chief. Changes to range maintenance schedules will be coordinated with 56 CES/CED to permit proper EOD planning/scheduling.
1.7.1. Detonation Scheduling Procedures. 56 CES/CED will notify 56 RMO/ASMS no later than a day prior to detonations (typically accomplished on Thursdays), so that an appropriate Range NOTAM can be published at https://afkm.wpafb.af.mil/BMGR-E.
1.8. Environmental Resources. The 56 RMO/ESM will assess any new operation/construction to determine if an environmental impact assessment is required, manage the land and natural resources to promote environmental protection consistent with meeting the current and future military missions, serve as focal point for non-military organizations having an interest in the natural and cultural resources of the BMGR, and conduct meetings as required to review resource concerns of the BMGR.
1.8.1. Endangered Species. Two federally listed endangered species occur on BMGR East, along with six Arizona wildlife concerns and two highly safeguarded plant species. Of these, the Sonoran pronghorn is of greatest concern. It is a federally listed endangered species;
approximately 95 percent of its existing distribution in the US is in the Cabeza Prieta National Wildlife Refuge (CPNWR) and on the BMGR East and West. An ongoing monitoring program is in place to minimize the risk of injury or mortality to pronghorn in accordance with the Endangered Species Act (ESA). Management actions for the other federal- and state-listed species do not have operational impacts; these actions are specified in the Integrated Natural Resources Management Plan (INRMP) and are implemented by 56 RMO/ESM staff.
1.8.2. Pilots and ground personnel will abide by all Sonoran pronghorn rules (closed targets, speed limits) IAW 56 RMO OI 1-1. A captive breeding area is located in Childs Valley within the Cabeza Prieta at N 32° 22.648' W 113° 01.187' MGRS 12S UA 0999 8407. The captive breeding plot is approximately 1 square statute mile and pilots should avoid overflight unless on a MTR.
17 AFI 13-212_LAFBSUP_1 31 AUGUST 2009
1.8.3. Sonoran Pronghorn (SPH) Antelope Clearances. 56 RMO contract personnel will monitor for SPH IAW the SPH Biological Opinion and Operating Instruction. The monitoring will take place during daylight only, as the first event of the day on the scheduled range. If a SPH is sighted within 5 km of either NTAC/STAC HE Hill/live maverick target, no high explosive ordnance deliveries will be authorized on the affected target and no deliveries of any kind will be made within 3 km of the sighting for the remainder of the day.
1.9. Safety. The 56 RMO is responsible for all safety aspects of range and SUA operations.
The Chief of Safety (56 FW/SE) conducts periodic safety reviews of GBAFAF. 56 FW/SE will, as needed, monitor, investigate, and coordinate with concerned/involved units, all reports of violations, incidents, or accidents in BMGR East, which affect safety of air or ground operations.
1.9.1. Range Incidents. Range incidents (airspace violations, ground intrusions, unintentional release, etc.) will be reported by anyone on the range (ground) or in the airspace (pilot). All incidents should be reported to Snakeye /RCO to document. Snakeye or RCO (GBAFAF base operations) will document on the BMGR East Incident Report (Attachment 3) and forward to the appropriate agencies within 3 hours. When incidents occur, a phone call will be made within 1 hour of the incident to 56 RMO/DO/ARO.
1.9.2. 56 RMO will provide both initial response and follow-on support for all range incidents within BMGR East IAW 56 RMO applicable OIs.
1.9.3. Emergency response.
1.9.3.1. BMGR East is a very remote operating area. Medical attention is limited to first response stabilization. Most if not all injuries will require transport to the Phoenix metropolitan area for treatment. GBAFAF fire department will coordinate transportation either by ambulance or medical evacuation helicopter. Typically, Arizona Department of Public Safety will respond with helicopter support. Other possible responders are civilian contract medivac and if necessary, military search and rescue assets from Davis Monthan AFB or MCAS Yuma.
1.9.3.2. Ground party injury. If any person on the ground is injured downrange, notify Snakeye or GBAFAF security for assistance. GBAFAF fire and/or EMT support will respond as needed.
At a minimum, GBAFAF security will respond.
1.9.3.3. Aircraft accident. Aircraft accidents may be reported by ground party (i.e., JTAC, RCO) or pilot. Reporting should be to the Snakeye, for initial support assessment. Snakeye will advise respective command posts of an aircraft accident. Other avenues of reporting/communication are GBAFAF tower, security, and respective Supervisor of Flying (SOF). The GBAFAF emergency management team will convene upon notification of an aircraft accident within BMGR East. GBAFAF fire, medical and security will respond to aircraft accidents.
1.10. Annual Range Board. The BMGR East Annual Range Board will be convened in accordance with AFI 13-212 AETC Sup 1. 56 RMO/DO is the OPR for the Annual Range Board.
AFI 13-212_LAFBSUP_1 31 AUGUST 2009 18
1.10.1. Members. Except when otherwise designated by the board chairman, the following are the members of the BMGR Board:
1.10.2. Chairman: 56 RMO/Director; Vice: 56 RMO/DO.
1.10.3. Members: 56 RMO/ARO, 56 RMO/ESM, 56 RMO/ASM, 56 RMO/ASMS, 56 RMO/QAE, 56 OG/OGV, 56 OSS/DO, 56 OSS/OSK, 355 FW/OG, 355 OSS/OSK, 563
RQG/DO, 162 FW/OG (ANG), 162 FW/LNG (ANG Operation Snowbird), 305 RQS (AFRES), 55 RQS, 79 SOS, MATWS-1 (MCAS Yuma), WAATS (ARNG), 1/285 AHB (ARNG).
1.10.4. Advisors: 56 TRS, 56 FW/SEW, 56 CONS/LGCV, 56 MSG/CC, 56 CES/CED, 56 CS/CC, 56 RMO contract support.
1.11. Arizona Area of Responsibility (AOR) Special Instructions (SPINS). Arizona AOR SPINS review will be held in conjunction with the annual range board as outlined in paragraph
1.10. 355 FW/OG maintains ownership of the SPINS, and therefore will take the lead for the review process during the annual range board meeting.
1.11.1. SPINS Content. The Arizona AOR SPINS provide standard procedures to be used by units executing or controlling interdiction, close air support, or combat search and rescue training missions in BMGR East. The SPINS represent procedures used in a cross-section of AORs.
Units will comply with the SPINS when working with other BMGR East users unless coordinated with the participating unit(s). If any doubt exists, use clear communications to immediately resolve any potential conflicts.
1.11.2. SPINS Location. The Arizona AOR SPINS can be obtained by contacting the 355 OSS/OSK at DSN 228-4960 or COMM 580-228-4960. It can also be obtained from the 355 OG Stan/Eval Knowledge Now website located at:
https://afkm.wpafb.af.mil/ASPs/CoP/ClosedCoP.asp?Filter=AC-OP-00-52.
1.12. Fire Fighting. The 56 RMO is responsible for fire response at GBAFAF and on BMGR East. GBAFAF fire fighting procedures will be IAW AFI 32-2001, Fire Emergency Services Program, 9 Sep 2008 and Fire Protection Management Plan 32. For wildland fires, NFPA 1500, Standard on Fire Department Occupational Safety and Health Program, 2007, the 56 RMO Wildland Fire Management Plan, and the 56 RMO—BLM memorandum of understanding (MOU) regarding fire support applies.
1.13. Reports.
1.13.1. Utilization/Reporting Information Requirements.
1.13.1.1. Airspace utilization. Snakeye will log airspace entry and exit times for all users within BMGR East and forward information to 56 RMO/ASM for compilation on a daily basis.
1.13.1.2. Weapons expenditures. All users of the BMGR East will report all weapons expenditures on tactical ranges to Snakeye upon check-out from the airspace. RCOs on manned ranges will log weapons expenditures for all users and forward information to 56 RMO/ASM for compilation on a daily basis.
19 AFI 13-212_LAFBSUP_1 31 AUGUST 2009
1.13.1.3. Aircrew will advise Snakeye of any unusual airspace or range restriction (i.e., ground party, pronghorn sighting, etc…) that adversely affected the mission. Snakeye will annotate amplifying information in their daily reporting to 56 RMO/ASM.
1.13.1.4. Supersonic tracking. 56 FW pilots will log all supersonic activity in Graduate Training Integration Management Systems (GTIMS). Any off-base user will report any unauthorized supersonic activity to 56 RMO/ASM (623-856-5855, DSN 896).
1.13.2. Utilization/Reporting Requirements.
1.13.2.1. 56 RMO/ASMS will compile a monthly range activity report IAW AFI 13-212 AETC Sup 1. A copy will be forwarded to 56 FW/HO.
1.13.2.2. 56 RMO/ASM will compile a quarterly/annual airspace utilization report IAW AFI 13-201, Airspace Management. A copy will be forwarded to 56 FW/HO.
1.13.2.3. Range Clearance Activity Report. 56 CES/CED will prepare the annual Range Clearance Activity Report required by Public Law 106-65 and submit it to 56 RMO for coordination NLT 01 November of each calendar year.
1.13.3. Toxic Release Inventory Report. 56 RMO/ESM will submit Toxic Release Inventory Reports for range munitions as required by the Emergency Planning and Community Right-to- Know Act (EPCRA).
AFI 13-212_LAFBSUP_1 31 AUGUST 2009 20
Chapter 2
BMGR EAST DESCRIPTION / CAPABILITIES AND INFORMATION
2.1. General. All casual/hosted units must receive a range orientation briefing prior to range utilization. Aircrews must have the most current edition of this supplement in their possession for mission planning and will review 56 RMO range NOTAMs. Strict adherence to ordnance, target, and LASER restrictions is essential. Additionally, the restricted areas are subdivided for multiple simultaneous uses. Proper area entry/exit procedures and maintaining flight within scheduled airspace are crucial to flight and ground safety.
2.1.1. Internal subdivisions to BMGR East include an Air Combat/Aerial Gunnery range “Air-to-Air (AA)”, three air-to-ground tactical employment ranges “NORTH, SOUTH, EAST TACTICAL” (NTAC, STAC, ETAC), four manned bombing ranges, “Ranges 1, 2, 3, 4” and SELLS MOA/ATCAA A/B/C/D illustrated at Figure 2.1. Refer to Chapters 3 and 4 for specific range information. Although not included in special use airspace, BMGR East includes drop/assault zones (DZ/LZ) and GBAFAF. Refer to paragraph 2.5 for DZ/LZ information and Chapter 8 for GBAFAF information.
Figure 2.1. BMGR East Area and Sub Ranges
2.1.2. Altitudes. Unless stated otherwise, all altitudes given in this supplement are in feet above Mean Sea Level (MSL). Use the GBAFAF altimeter when operating within BMGR East.
21 AFI 13-212_LAFBSUP_1 31 AUGUST 2009
2.1.3. Coordinate Conversions. Airspace boundaries and target locations are defined by WGS– 84 NAD 83 coordinates in degrees, minutes, decimal minutes.
2.1.4. Avoid maneuvering within 500’ of any vertical boundary. This provides 1,000’ vertical separation between aircraft. Avoid maneuvering within 2 NM of restricted area borders.
Exception: avoid maneuvering within 2.5 NM of the R-2301E/W border. Live Aerial Gunnery missions should also avoid internal borders by at least 2 NM.
2.1.5. Weather Requirements. The minimum weather requirements for range operations will be IAW AFI 11-214, Air Operations Rules and Procedures, and specific Mission Design Series (MDS) guidance. Administrative Maneuvering: Aircrew are allowed to transit IMC in scheduled restricted airspace without an ATC clearance (an ATC clearance is required to transit MOAs/ATCAAs IMC). Tactical Maneuvering: Due to the complex nature of airspace subdivisions all tactical maneuvering will operate under VFR in the BMGR East. Exceptions will be considered and must be approved by 56 RMO/CC to accommodate IMC intercept training and or IMC weapons delivery (restricted areas only).
2.2. Restricted Airspace.
2.2.1. R-2301E. R-2301E is airspace defined by Arizona SR 85 on the east and the Mohawk Mountains to the west between I-8 and the US-Mexican border. The western boundary of R- 2301E is adjacent to R-2301W. R-2301E extends from the surface to 80,000’, except over the CPNWR, where a 1,500’ AGL restriction exists when not on a scheduled MTR. R-2301E is authorized for unrestricted supersonic operations above 5,000’ MSL, except over the manned ranges, where supersonic is restricted to above 10,000’ AGL. The entire R-2301E area is activated for any use of AA, NTAC, STAC, manned Ranges 1, 2, or 4. R-2301E boundaries are:
N 32 50.000 W 112 49.000 to N 32 12.000 W 112 57.000 to N 32 12.000 W 113 06.000 to N 31 58.000 W 113 06.000 along the US/Mexico border to N 32 06.000 W 113 31.000 to N 32 44.000 W 113 41.000 to N 32 46.000 W 113 35.000 to the beginning.
2.2.2. R-2305. R-2305 consists of the airspace over and out to 7 NM east of Arizona SR 85 between the town of Ajo and GBAFAF. R-2305 extends from the surface to 24,000’. R-2305 is authorized for subsonic operations only. R-2305 is activated for any use of manned ranges 1, 2, or 3. R-2305 boundaries are:
N 32 50.000 W 112 49.000 to N 32 51.000 W 112 43.000 to N 32 49.000 W 112 39.000 to N 32 29.000 W 112 43.000 to N 32 29.000 W 112 54.000 to the beginning.
2.2.3. R-2304. R-2304 consists of the airspace east of R-2305, southwest of Gila Bend, AZ. R- 2304 underlies the SELLS ATCAA and overlies both military managed land as well as Native
AFI 13-212_LAFBSUP_1 31 AUGUST 2009 22
American land. R-2304 extends from the surface to 24,000’. R-2304 is authorized for subsonic operations only. R-2304 is activated for any use of ETAC and/or Range 3 (see paragraph 4.14 for specific ETAC information). R-2304 boundaries are:
N 32 39.000 W 112 18.000 to N 32 27.000 W 112 18.000 to N 32 27.000 W 112 44.000 to N 32 49.000 W 112 39.000 to the beginning.
2.2.4. Restricted area entry/exit. IFR entry is via ARSON, NOLLS, or BUGGS. IFR exit is via ARSON, BUGGS or COOLY, Figure 2.2 (also see Attachment 4 for waypoint coordinates).
VFR entry/exit is via military training route (entry only) or VFR altitudes. Specific range entry/exit procedures are located in Chapter 3/4.
2.2.5. General Aviation/Air Evacuation Corridor. This corridor transects R-2301E and R-2305 extending from GBAFAF to the Ajo Airport along Arizona SR 85 to afford civilian traffic restricted airspace transit. Crossing altitudes are 500' AGL (day) and 1,000’ AGL (night). VFR rules govern civilian flights through the BMGR East. Civilian air evacuation flights (“Lifeguard”) will be given priority over all other air traffic except in-flight emergencies. The “Air Evac” call sign (USAF) will be used only when the aircraft is on an actual air evacuation mission. Arizona Department of Public Safety "Ranger" call signs must indicate they are on an air evacuation mission to receive priority. Military aircraft on manned ranges will be instructed to remain clear of Arizona SR 85 or to transit the highway 1000' above the air evacuation/general aviation aircraft.
2.2.5.1. Corridor Activation. Snakeye will advise RCOs on the manned ranges and GBAFAF tower prior to activating the General Aviation/Air Evacuation Corridor. RCOs will in turn advise/restrict manned range operations until the traffic has passed.
23 AFI 13-212_LAFBSUP_1 31 AUGUST 2009
Figure 2.2. BMGR East Special Interest Areas and Reference Points
2.3. SELLS MOA/ATCAA (Figure 2.3). The SELLS MOA/ATCAA can be used individually or in conjunction with flight operations within the BMGR restricted areas, or as a transit route to and from the Tucson area. The MOA/ATCAA overlies R-2304 and R-2305, and is subdivided into five parts, A, B, C, D and E and the Ajo transition and also includes AR 647/647A. Sectors A and B are usually assigned together, and constitute the northern half of SELLS. Sectors C, D and E are usually assigned together, and constitute the southern half of SELLS. The airspace is further subdivided vertically as SELLS Low and SELLS MOA/ATCAA (Figure 2.3). SELLS MOA/ATCAA boundaries are:
N 32 50.000 W 112 45.000 to N 32 51.000 W 112 43.000 to N 32 15.167 W 111 36.000 to N 31 58.000 W 111 36.500 to N 31 49.000 W 111 32.000 to N 31 43.500 W 111 38.500 to N 31 31.000 W 111 38.500 to N 31 58.000 W 113 05.500 to
AFI 13-212_LAFBSUP_1 31 AUGUST 2009 24
N 32 11.500 W 113 05.500 to N 32 11.500 W 112 56.750 to the beginning
2.3.1. Special Considerations. SELLS MOA overlies two noise sensitive areas, the Tohono O’odham Nation and the Organ Pipe Cactus National Monument. Strict adherence to directives is essential to respecting the concerns of and maintaining a good working relationship with the residents and managers of these areas. Supersonic flight in SELLS A-E is authorized above 10,000’ MSL and will be directed away from villages. Supersonic flight is not authorized within 5 miles of Ajo, Hickiwan, Vaya Chin, Sells, and the Kitt Peak Observatory. Avoid overflight of Kitt Peak. Avoid Baboquivari Peak by 3 NM.
Figure 2.3. SELLS MOA/ATCAA; Subdivision Coordinates
2.3.2. SELLS MOA/ATCAA Altitudes. The MOA extends from 3000’ AGL to 18,000’ MSL.
The SELLS Low MOA is a subset of the overall MOA under A/B/C/D/E from 3,000’ AGL to 9,500’ MSL. The SELLS ATCAA extends from 18,000’ to 51,000’. (Note: depending on scheduled use of SELLS subsection airspace, the 500’ buffer is not applicable.)
25 AFI 13-212_LAFBSUP_1 31 AUGUST 2009
2.3.2.1. SELLS A/B. SELLS A/B begins at 10,000’ MSL unless low airspace is specifically scheduled. A/B Low can be scheduled under special circumstances. SELLS A is restricted over R-2304 and R-2305 to 25,000’ and above.
2.3.2.2. SELLS C/D/E. SELLS C/D/E begins at 10,000’.
2.3.2.3. Typically SELLS A/B, SELLS C/D/E are grouped respectively for simultaneous but different use. Subdivisions may be scheduled separately or in different configurations depending on mission requirements. SELLS A/B is commonly scheduled with R-2304 (ETAC) and/or the SELLS MOA/ATCAA is scheduled in conjunction with R-2301E. SELLS E may be scheduled with SELLS C/D or R-2301E.
2.3.2.4. SELLS A/B Low. The SELLS A/B Low sectors begin at 3,000’ AGL and extend up to and including 9,500’ MSL. It is used primarily as a transit area for traffic to and from the Tucson area as well as low altitude tactical navigation (any aircraft 250 kts and below). SELLS A/B Low will not normally be scheduled for individual flight use, however when required (i.e., LFE), will be scheduled and published via range NOTAM.
2.3.2.5. SELLS C/D/E Low. The SELLS C/D/E Low sectors begin at 3,000’ AGL and extend up to and including 9,500’ MSL. It is normally scheduled in conjunction with SELLS C/D/E high airspace.
2.3.3. SELLS MOA/ATCAA Activation.
2.3.3.1. The SELLS MOA/ATCAA is activated 1 hour prior to the first scheduled SELLS mission, and is deactivated 1 hour after the last scheduled SELLS mission.
2.3.3.2. SELLS Low MOA’s. The entire SELLS Low MOA is activated 1 hour prior to the first Tucson/ Davis-Monthan AFB mission scheduled into the BMGR, and is not closed until 1 hour after the last mission on the BMGR. Additionally, the Low MOA is activated one hour prior to the first scheduled mission in SELLS C/D/E Low, until 1 hour after the last mission in SELLS C/D/E Low. The 500’ buffer between LOW and HIGH MOAs exists unless a unit has scheduled both simultaneously.
2.3.4. SELLS, AAHI, STAC and Range 1 Deconfliction. Extreme caution must be used by flights operating in SELLS, AAHI, and STAC when AR-647 is active. Air refueling missions above 17,999’ use the standard altimeter setting of 29.92, while flights in SELLS, AAHI and STAC use the GBAFAF local altimeter setting.
2.3.5. Ajo Transition. The Ajo transition (Figure 2.2) is a VFR means to traverse from north to SELLS C/D/E or the eastern portion of R 2301-E and vice versa. Routing southbound is NOLLS-Black Gap-town of Ajo at odd VFR hemispheric altitudes (Note: BMGR East IFR entry from the north will be via NOLLS at 8,000’ MSL). Routing northbound is Ajo-Black Gap- COOLY at even VFR hemispheric altitudes. Transition altitudes are from 10.5K MSL to 14.5K MSL. Coordinate deconfliction with SELLS A/B and avoid manned ranges by 5 NM. If below 10,000’ MSL pilots must coordinate with manned ranges 1, 2, and 3 for deconfliction.
2.3.6. SELLS MOA/ATCAA Entry/Exit.
AFI 13-212_LAFBSUP_1 31 AUGUST 2009 26
2.3.6.1. North entry. Normal entry is through BUGGS at 9000’ MSL or as assigned. Use caution for departing traffic at 7,000’-8,000’ (BUGGS) and crossing east-west traffic at even/odd VFR hemispheric attitudes below 10,000’ MSL.
2.3.6.2. East entry. Normal entry is through either KITT at 8500’ MSL or WHISKEY between 7500’ and 9500’ MSL or as assigned.
2.3.6.3. Flights desiring to enter SELLS above 10,000’ must confirm SELLS A/B is cold or deconflict with using flight prior to request. Luke RAPCON/ABQ ARTCC IAW LOA must approve block altitudes for entry.
2.3.6.4. SELLS C/D/E entry. Normal entry from the north is through BUGGS at 9,000’ MSL.
Flight(s) will remain at 9,500’ MSL until the lateral limits of SELLS C/D/E unless coordinated and deconflicted with SELLS A/B traffic.
2.3.6.4.1. Normal entry from the east is through KITT at 8500’ MSL or SIERRA at 7500’ or 9500’ MSL. (Note: A-10s may enter VFR from the Low Altitude Tactical Navigation (LATN) area.)
2.3.6.4.2. Flights may also enter via the Ajo transition IAW paragraph 2.3.5. Normal IFR point of entry is NOLLS at 8,000’ MSL.
2.3.6.4.3. Flights exiting SELLS to the north (BUGGS) will be between 7,000’- 8,000’ within 10 NM of BUGGS to deconflict with entering traffic. Use caution for entering traffic at 9000’ MSL (BUGGS) and crossing east-west traffic at even/odd VFR hemispheric attitudes below
10,000’ MSL.
2.3.6.4.4. Flights exiting SELLS to the east (KITT/WHISKEY/SIERRA) will depart between 7500’ and 9500’ MSL.
2.3.6.4.5. SELLS C/D/E exits via the Ajo transition will depart at 8,500’ unless coordinated with SELLS A/B traffic. Comply with paragraph 2.3.5.
2.4. AR-647/AR-647A (Figure 2.3).
2.4.1. AR-647. The AR-647 refueling track overlies SELLS and the southeast portion of AAHI and STAC. When activated, AR-647 restricts the use of SELLS, AAHI and STAC and will be posted in the Range NOTAMs.
2.4.1.1. AR-647 Deconfliction. SELLS, AAHI and STAC missions must remain at least 1,000’ above or below the AR-647 block. AR-647 Low-block extends from 10,000’ to 17,000’; AR- 647 Mid-block FL180 to FL230; AR-647 High-block FL 240 to FL290. The High and Low blocks will not be scheduled simultaneously. On rare occasions the Low and Mid or Mid and High blocks may be scheduled simultaneously. When AR-647 is active all flights scheduled to work in SELLS, AAHI and STAC airspace will confirm BMGR range NOTAMs with Snakeye.
All…
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .