Controller Login
Go
Reset Password

• Homepage
• About ZOA
  • Crew Roster
  • Controller Stats
  • Staff List
  • Event Booking
  • News Archive
  • ZOA Video
• Events
  • Current Events
  • Past Events
  • VATUSA Events
  • Suggestions
  • Booking Form
  • Contact Info
• ATC Training
  • SOPs/LOAs
  • Syllabus
  • Mentors
  • Downloads
  • Test Standards
  • Reference
• Airports/Charts
  • Sector Maps
  • Airspace Maps
  • Military Airfields
  • VOR Listing
  • Other ARTCCs
• Pilot Info
  • Training Videos
  • NOTAMs
  • Virtual Airlines
  • Weather
  • SFO Scenery
  • Resources
  • Flight Training
  • SimRoutes
  • FlightAware IFR
• Feedback
• ZOA Forum

 

Virtual US Airforce

Date	Code	Version	Contact
2005-09-10	LOA-VUSF	1.00	Facility Advisory Board (FAB)

1. PURPOSE:

This Letter of Agreement (LOA) establishes operating procedures between Oakland ARTCC (Center) and vUSAF 9th Reconnaissance Wing (RW), Air Combat Command (ACC), Beale AFB for providing control services in the Beale Class C airspace and the surrounding Military Operating Areas (MOAs) along with the 60th Air Mobility Wing (AMW), Air Mobility Command, Travis AFB for providing control services in the Travis RAPCON and Class D airspace and military training routes.

2. SCOPE:

These procedures apply to all VFR/IFR aircraft entering or exiting the Beale AFB Class C Airspace, Travis Class D, local MOAs, air refueling routes and military training routes (MTRs).

3. ROLES AND RESPONSIBILITIES:

The Offices of Primary Responsibility (OPR) for this LOA are the ZOA Advisory Board (FAB) and the vUSAF 81st TW (ATC).

Northern California Terminal Radar Approach Control (TRACON) (Nor Cal Approach) provides Beale AFB with terminal IFR and Class C radar service. Beale Tower provides Class C service within a 5 NM radius, surface to 2,100 MSL. Beale Tower will coordinate with Nor Cal Approach to utilize airspace 2,100 to 2,600 MSL

 

The Travis Radar Approach controls Class E airspace from surface to 10,000’ MSL, in an approximately 2,000 square mile area, extending east to west from Napa County Airport to just west of Sacramento, and from north to south from Concord to just north of Watts-Woodland. Numerous civilian satellite airports and VFR training areas are within Travis Class E airspace. The Travis Tower controls Class D airspace, consisting of a 5 NM radius around the airport from the surface to 2,600’ MSL.

 

The Travis Aero Club lies within the northwest corner of the Class D airspace and medical mission helicopters operate within the northwest corner of the Class D airspace at David Grant Medical Center.

 

 

4. DISTRIBUTION:

This LOA is intended for use by ZOA and controllers of the vUSAF staffing Beale AFB and Travis AFB.

5. BACKGROUND:

This LOA has been developed and shall be maintained to establish flight management procedures for vUSAF operations, so that ZOA ARTCC ATC staff and vUSAF pilots can expect consistent ATC support within the ARTCC. The procedures set forth in this LOA shall be disseminated to vUSAF command staff, pilots and the ZOA ARTCC ATC Staff and controller roster.

6. POLICIES:

a. Facilities.

(1). Facilities will be of two types: "joint civil/military" and "military-only", as listed in section 7(a) and (b). ZOA controllers and vUSAF military controllers, who are certified as outlined in section 6(b) shall be authorized to man "joint" facilities. ZOA controllers shall not be authorized to man "military-only" facilities.

(2). vUSAF military controllers are not authorized to man any ATC positions other than those listed in section 7, unless they become certified visiting controllers as provided by CPS_006.

(3). vUSAF controllers shall use certified ZOA ARTCC sector files as available on the ZOA ARTCC web site, or may use other sector files, only if they have been reviewed and certified by the ZOA ARTCC Facility Engineer. Currently the following non-ZOA files have been reviewed and certified:

None.

b. Certification and Enforcement - vUSAF military controllers

(1). vUSAF controllers shall be considered a unique class of visiting controller. They shall not be required to comply with the ZOA ARTCC visiting controller policy (CPS_006). They shall instead be subject to provisions contained solely in this LOA. This shall be referred to as "military controller privileges".

(2). vUSAF military controllers must meet published VSOA military certification requirements for the position manned. If no applicable VSOA military certification requirements are published, the following shall be applied:

·        Must hold a S-3 grade or higher to work an Approach Control position or lower position.

(3). 81st WG/XO will provide an e-mail list of the approved controllers to the Assistant Chief for posting on the ZOA Guest Controller roster.

(4). The ZOA shift supervisor (as defined in ZOA ARTCC SOP 002) shall use the Guest Controller roster as posted on the ZOA web site for verification of certification. vUSAF military Controllers not listed in this roster may be asked to leave the position.

(5). vUSAF military controllers must strictly adhere to all aspects of this LOA. The ZOA shift supervisor shall be authorized to remove any vUSAF military controller who fails to demonstrate detailed familiarity with the provisions of this LOA.

c. Certification and Enforcement - ZOA controllers

(1). ZOA controllers must meet standard ZOA ARTCC facility certification rules outlined in CPS_002 when operating joint civil/military positions.

(2). When ZOA ARTCC controllers are working at positions subordinate to a vUSAF controller (Ex: ZOA controller on BAB_GND, vUSAF controller on BAB_TWR), the vUSAF controller may request removal of the ZOA controller from the ZOA ARTCC shift supervisor if the ZOA ARTCC controller fails to demonstrate detailed familiarity with the provisions of this LOA.

d. Airspeeds in the Class C, D and MTRs

It is recognized that certain training operations and training aircraft require high speeds. Military training aircraft on MTRs may exceed 250 knots below 10,000' MSL if required. KC-10 and KC-135 aircraft may exceed 250 knots below 10,000' MSL within the Nor Cal airspace during formation departures to expedite formation join-up.

e. Flight Plans.

 

(1). All aircraft departing Beale or Travis AFB will file a flight plan in accordance with vUSAF policy.

 

(2). ATC will verify all “no flight plan” aircraft operations at Beale and Travis AFB via the aircraft commander prior to granting engine start approval or landing clearance, unless an emergency exists.

 

(3) KC-10 and KC-135 cell departure flight plans will contain the phrase, “MARSA w/ (wingman’s callsign)” as a remark after the flight plan route. KC-10 and KC-135 cell departures are discussed in paragraph 8.i. (Note, this is for automation purposes only. KC-10 and KC-135 aircrews shall file flight plans with Base Ops as dictated in FAAO 7610.4, Special Military Operations, paragraph 12-12-8.)

 

7. AUTHORIZED MILITARY FACILITIES:

The following facilities are designated as joint-use civil/military facilities, with the associated authorized positions. These positions may be manned by properly certified vUSAF military or ZOA controllers:

8. STANDARD OPERATING PROCEDURES:

a. General

(1). vUSAF military controllers shall comply with ZOA ARTCC SOP 001, sections:

·         5 (c) regarding ATIS messages

·         5 (e) regarding the ATC channel

·         5 (f) regarding Callsigns

·         5 (g) regarding client range

(2). vUSAF controllers shall comply with all provisions of ZOA ARTCC SOP 002.

(3). vUSAF controllers shall comply with all provisions of ZOA ARTCC SOP 004.

(4). vUSAF controllers shall comply with all provisions of ZOA ARTCC SOP 005.

(5). vUSAF controllers shall comply with all provisions of ZOA ARTCC SOP 020.

(6). vUSAF controllers shall comply with all provisions of ZOA ARTCC SOP 052.

b. Beale AFB (KBAB)

(1). Authorized text callsigns and frequencies are: 

BAB_GND...121.60 (CH-01) BAB_TWR...119.40 (CH-02)

(2). Initial climbs for IFR departures filed for altitudes at or above 11,000' shall be to 11,000'. If departure routing is to the south or east, aircraft will be given a heading of 060 until clear of SMF_APP traffic and then cleared direct to next point on flight plan.

(3). Departure releases {as defined in ZOA SOP 003 section 5 (k) (ii) } must be obtained from SMF_APP for operations from runway 15 at all times, and for runway 33 at the request of SMF_APP. This shall protect FLUNK3 and TUDOR1 arrivals to KSMF.

(4). U-2 High Flight Departures, shall be routed via the PYNUN-THREE Departure and given an unrestricted climb to filed or requested flight level.

(5). Local climbout for touch-and-goes and missed approaches when radar facilities are manned shall be:

(a) Rwy 15: Turn right to heading of 300 and climb to 3,000' MSL and then will be transferred to the radar facility.

(b) Rwy 33: Turn left to heading of 180 and climb to 3,000’ MSL and then be transferred to the radar facility.

When no radar facility is online, missed approaches shall be handled in accordance with ZOA SOP_003.

(6). When SMF_APP or OAK_C_CTR is manned, the Beale Class C is active. VFR departures shall require Class C clearance.

(7). When the BAB_FC_APP is manned, all VFR departures will be instructed to "after departure, fly runway heading".

(8). When BAB_FC_APP is manned, SMF_APP shall handle all BAB departures on a fixed point-out with BAB_FC_APP, thru the Beale Class C.

(9). Departures to the Maxwell MOA shall be routed via MXW then HUPTU.

(10). Departures to the China/Whitmore MOAs shall be routed via the BAB335075 (EWOKS).

(11). Runway 15 shall be used for departures and arrivals when winds are less than 6 knots.

(12). Runway 15/33 Operations:  

·    Rwy 15- Right or left hand traffic pattern, 1,100' Traffic Pattern Altitude, 2,100’ Overhead Altitude. Note: Fighter Type Aircraft- right hand traffic only.

·    Rwy 33- Right or left hand traffic pattern, 1,100' Traffic Pattern Altitude, 2,100’ Overhead Altitude

(13). IFR arrivals and practice instrument approaches to Beale AFB for Rwy 15 shall be vectored to intercept BAB325/13.5 (BAB21) for the ILS 15 approach.

(14). IFR arrivals and practice instrument approaches to Beale AFB for Rwy 33 shall be vectored to intercept the BAB146/09 (BAB59) for the ILS 33 approach. 

(15). Practice instrument approaches to Beale AFB by other than 9 RW assigned aircraft shall be coordinated with BAB_TWR and are only authorized when pattern traffic permits.

c. Beale Radar Final Control

(1). Authorized text callsigns and frequencies are BAB_FC_APP...124.55 (Ch-10).

(2). Authorized voice callsign is "Beale Final Control".

(3). Responsibility is to provide PAR / ASR approach services to aircraft on approach to Beale AFB.

(4). When manned, BAB_FC_APP shall be delegated the Beale Class C airspace.

(5). SMF_APP shall handle all BAB departures on a fixed point-out with BAB_FC_APP, thru the Beale Class C. VFR traffic shall exit the Class C on runway heading, unless coordination is obtained from BAB_FC_APP.

(6). BAB_FC_APP shall instruct missed approaches to "fly runway heading and c/m 3,000" and initiate handoff to SMF_APP for re-sequencing.

d. Beale High Instrument Approaches

(1). Beale has two high instrument approaches within the OAK_CTR low structure.  

(2). When the HI-ILS or the HI-TACAN approach to 15 is being utilized; OAK_CTR shall clear the aircraft for the approach.

(3). When the HI-ILS is to be flown, aircraft will be given one turn in holding at BAB326/36 (GIMMY) at 16,000’ MSL then cleared the approach.

(4). When the HI-TACAN is to be flown, aircraft will be given one turn in holding at BAB333/42 (HOLLI) at FL190 then cleared the approach.

(5). Prior to passing 11,000’ MSL, the aircraft will be handed off to SMF_APP.

e. Beale Stereo Flight Plans

(1). The following routes may be issued to military and civil aircraft. VSOA member aircraft (vUSN, vUSAF, vUSCG, vUSA, vUSMC) may file the appropriate "stereo route" ID in the flight plan.