Policy and procedure updates have been uploaded to the site.
First, a few changes to CPS-001 have been made. ATIS, D-ATIS and PDC information was moved to CPS-004.
There has also been a change to the monthly activity requirements. All controllers will now need to spend at least 50% of the minimum monthly time on their highest rated position. If your highest rated position is NCT_APP, and you are a home controller, you need to log at least 1:30 on NCT_APP, the other 1:30 can be on any position you want for a total of 3 hours. The same applies to visitors, except it is only 1:00, for a total of 2:00. This will be in effect for September, meaning the first removals/ warnings will not be sent until Oct 1. If you have questions please email management[at]oakartcc.org or DM me on Discord.
CPS-004 has been updated with ATIS, D-ATIS, and PDC information as noted above.
The Reno ATCT SOP has had a small updated to LUAW procedures.
The new Monterey ATCT SOP is now up. Not too much going on in that SOP, but please review it prior to working a MRY ATCT position.
We’re working on getting LOA’s for FAT-NCT and FAT-ZOA up next, and from there we will likely begin working on military fields.
Both the Oakland ATCT and San Jose ATCT SOP’s have been updated on the website. They include a new format, new procedures, diagrams, and all you will need to control these airports. Please check them out in the SOP’s/LOA’s page.
We will be working on Sacramento and Reno next and hope to have that to you soon. Please direct any comments/questions/concerns to management[at]oakartcc.org
Updates to the ZOA En Route SOP, NORCAL Tracon SOP, and San Francisco ATCT have been published, as well as an update to the ZOA-NCT LOA.
The ZOA SOP has been changed to reflect the feedback you provided in the recent procedures survey, as well as a format change to reflect the new ZOA. If you have any questions please send them via Discord or email.
The NCT SOP has been consolidated back into a single document and the format was updated for consistency. We’re continuing to look at options for further updates to this SOP based on the feedback we recently received.
The SFO ATCT SOP has been reformatted and the NCT LOA has been consolidated into a single document.
The ZOA-NCT LOA updated a formatting and readability issue, as well as adding the new PIRAT STAR.
There is a new ZOA Class D Airport SOP available. This is a completely rewritten SOP with hundreds of changes. Before controlling any Class D airport, please read the new procedures.
This SOP can be found here.
After months of hard work I’m happy to announce that we’ve made some needed changes to the NorCal TRACON. In addition we have rebuilt the sector file to offer more features and more organization. The NCT SOP was rewritten from the ground up and formatted so that it is easier to read and find information within it. The Reno Complex SOP has been split, putting the Nugget and Silver information into the NCT SOP and the ATCT into it’s own SOP.
In depth details regarding the sector changes can be found on the forums. In a nut shell, not much has changed with the west flow sectors except for the addition of OAK_DEP. SFO_DEP has been renamed from Richmond to Sutro to reflect the real world name, and OAK_DEP is now called Richmond. The OAK_DEP sector was added in order to give OAK_APP or Area C controllers the ability to full control Oakland rather than confusing them when OAK_APP is online but not providing departure or local services to them. A few other minor changes have taken place that help with some of the operational conflicts that were introduced with the new RNAV arrivals.
The east flow sectors are where most of the changes have occurred. The previous sectorization was very bulky, had confusing operations, and wasn’t very efficient. We have redrawn almost all of the east flow sectors and believe that it will make east flow a little less intimidating and confusing. More details regarding sectorization can be found in the forums.
The sector file was rebuilt with organization and ease of use in mind. Everything has been organized in a way that makes sense and is easy to find. We really hope that you enjoy the sector file and if you have any suggestions we want to hear them! The sector file is available for download in the downloads section – it includes major sectors changes so everybody needs to update their sector file!
We’ve updated the LOA with ZSE and there are a few things to know.
First, we’ve changed the altitude restriction for aircraft going to Reno from PDX or SEA. They’ll now cross into our airspace at or below FL330. There are some preferred route changes as well that allows us to use the new RNAV arrivals into PDX and SEA. Please take some time to review the other changes.
CPS-006 Visiting Controller Policy has been updated with rewording to be in compliance of VATSIM GRP v2.2013.1, this policy only effects current and future visiting controller in vZOA.
CPS-009 Transfer Policy has been updated with rewording to be in compliance of VATSIM GRP v2.2013.1, this policy only effects transferring controllers into vZOA.
Gents, the LOA with ZLA has been updated to reflect a few minor changes.
The changes made in the LOA are to Fresno operations as well as some preferred routings for flights going to Burbank and Van Nuys from the bay, as well as FAT/BFL routing. You can now expect Fresno aircraft to be handed off at their cruise altitude or 11000, whichever is lowest. Please review this LOA before controlling to make sure you’re up to speed on the new requirements.
We are expecting an LOA update from Seattle soon, so keep an eye out for that.
Gents, the LOA with ZLC has been updated.
The change removes an altitude restriction at Reno, updates preferred routings for KSFO, KOAK, KSJC, KSMF, and KRNO for both RNAV and non RNAV aircraft, and more. Please go review this LOA before controlling.
We have changes with ZLA and ZSE pending, so keep an eye out for those in the future.