Below lists a general guide to help someone taking over the FE position to temporarily maintain ARTCC resources until FE is able to return to duty.

Table of Contents

Change Log Maintenance

Every change to any beta “ZLC Facility Files WIP” facility file that will have an affect on any operational practice or documentation requires a description of the change in the DropBox Change Log for Beta Files.txt file.
Note- This file can be found here: %userprofile%\Dropbox\6. Internal Facility Files\Please Review

Mission

To have all AIRAC, NAVDATA, Diagrams, In-Scope Reference Materials, Facility Directives, Quick References, etc… updated and release to ZLC members via the Resource Center the night prior to the AIRAC change.

Every AIRAC requires an update of

  • FAA publication changes/additions/deletions (if any)
  • NAVDATA (fixes, NAVAIDs, airports, Airways, etc…)
  • Newest AIRAC designation in the alias file. CTRL+H; Find: /1601/ ; Replace: /1602/ (this updates all FAA chart recall commands)

Schedule

CYCLEEFFECTIVE DATE
20118-Oct-2020
20125-Nov-2020
20133-Dec-2020
201431-Dec-2020
210128-Jan-2021
210225-Feb-2021
210325-Mar-2021
210422-Apr-2021
210520-May-2021
210617-Jun-2021
210715-Jul-2021
210812-Aug-2021
21099-Sep-2021
21107-Oct-2021
21114-Nov-2021
21122-Dec-2021
211330-Dec-2021
220127-Jan-2022
220224-Feb-2022
220324-Mar-2022
220421-Apr-2022
220519-May-2022
220616-Jun-2022
220714-Jul-2022
220811-Aug-2022
22098-Sep-2022
22106-Oct-2022
22113-Nov-2022
22121-Dec-2022
221329-Dec-2022

The following is a general timeline complete with deadlines and expectations for the ZLC FE.

NOTES:

  • The schedule will be relevant to each AIRAC release, minus a specified number of days. AIRAC data is released from the FAA on a 28 day cycle.
  • At minimum, a new sector file with the newest AIRAC data will be released within 2hrs of an AIRAC release. Example: AIRAC release 9NOV 0000z. The new file(s) will be released to ZLC for download/use between 2200z and 2359z on 8NOV.
  • Each release of a sector file will have the AIRAC designation in the Sector Info section. If multiple releases are required within the same AIRAC cycle, the designation will have a version designation. Example: The third sector file release within AIRAC 1803 will be designated as 1803v3

Note- Deviations from this timeframe must be approved by ZLC ATM or DATM. If the MyFSim site has not uploaded the next AIRAC data by AIRAC-2 days, new sector file NavData is likely to be approved to be released up to 24hrs after AIRAC release due to the more extensive methods of collecting the newest NavData.

  • There is an issue with the order in which the FAA compiles VOR and NDB data. This will make the VOR ISN be published as missing. Until this is resolved, the ISN VOR will need to be manually inserted into the Sector file VOR section.ISN 116.300 N048.14.09.484 W103.48.25.502 ;WILLISTON VOR/DME



General Ops Schedule/Deadlines

AIRAC-28 Days

  • Gather AIRAC data (Airports, Fixes, NDB, Airways, VORs).
  • This site is helpful but may not always have the next cycle data up in time. If using this site, use “JAC” as the basepoint and 800nm radius.


AIRAC-19 Days

  • Gather AIRAC procedural changes .
  • Notify ATM and DATM of all changes that would have an operational affect on Facility Directives and Quick References. Also if any changes would affect any other department, email the appropriate party and CC the ATM and DATM.


AIRAC-18-1 Days

  • Add/Delete/Create affected ZLC resource data.
  • Utilize this guide to complete this.
  • Utilize the Change Log txt file on the ZLC Dropbox folder to record changes as they are made. Dropbox\5. Public Facility Files\Please Review\Change Log for Beta Files.txt


AIRAC-2 Days

  • If MyFSim data has not been updated to the upcoming AIRAC data:
    • Notify the ATM and DATM of expected delayed time of AIRAC data release due to MyFSim data not being updated.
    • Utilize any tools necessary to get the newest data within 800nm of JAC.
  • If able, schedule a Windows Task to update the beta files to official release 1min prior to AIRAC release. Contact DATM for instructions on how to do this.


AIRAC-2hrs

  • If Windows Task has not been scheduled to do so, load all new ZLC Resource Files to the ZLC Dropbox
  • Update Resource Center data accordingly (by default, the DATM will be doing this but may required FE to complete the task)
  • Post change log announcement (by default, the DATM will be doing this but may required FE to complete the task)

What is affected

  • IAP
    • FAA Charts Recall alias commands
    • Facility Directives/Quick Reference (possible)
    • Scope De-Clutter/Diagram Setup commands
      • Sector Diagram
  • DP
    • Facility Directives/Quick Reference
    • FAA Charts Recall alias commands
    • DP & STAR In-Scope Reference commands
    • Scope De-Clutter/Diagram Setup commands
      • Sector Diagram
    • ATC To Pilot Text>DEL/GND/TWR
  • STAR
    • Facility Directives/Quick Reference
    • FAA Charts Recall alias commands
    • DP & STAR In-Scope Reference commands
    • Scope De-Clutter/Diagram Setup commands
      • Sector Diagram
  • APD
    • Runway name change:
      • Facility Directives/Quick Reference
    • Sector Diagram
  • Airways
    • Scope De-Clutter/Diagram Setup commands
    • Sector File Airway Data
  • VORs
    • Scope De-Clutter/Diagram Setup commands
    • Sector File VOR Data

List of publication changes

Note-This process takes 5-30min to complete depending on amount of changes posted per state.

  • Use the FAA Terminal Publication Advanced Search page: https://www.faa.gov/air_traffic/flight_info/aeronav/digital_products/dtpp/search/advanced/
  • Effective date: select the next cycle for upcoming updates. NOTE- If it is not displayed, you have to try again later. It is suppose to be released 28 days prior to the next AIRAC but it can sometimes be late. New notice says it will be released 19 days prior to effective date.
  • Check by STATE, not VOLUME. This reduces the amount of filtered airports to go through.
    • OR
    • ID
    • MT
    • ND
    • SD
    • WY
    • UT
    • NV
  • Search by the first state “OR”
  • Leave “All airports” displayed
  • Select all three of the “Filter results by” options
    • A = Added publication (new)
    • D = Deleted publication (old/removed)
    • C = Changed publication (there has been a change in this publication since last AIRAC)
  • Hit “Search”
  • Click the “Ident (ICAO)” column title to sort by airport codes in alphabetical order.
  • Review each returned publication and check to see if that field is served by ZLC facilities. If it is not, keep scrolling to the next procedure.
  • If the airport is served by a ZLC facility/position, take the appropriate action (below).
    • Make a list of changes that affect ZLC controllers in some way (Facility Directives, Alias Commands, Sector File Diagrams, Training Department, etc…)
  • Once complete with the first state, go back to search by the next state using the same criteria listed above.

With a changed FAA publication

  • Use the FAA site “Compare” link next to the chart
  • Take notes about the changes if they affect controller required knowledge
  • If the change affects phraseology/SOP, notify the DATM and TA of the change.
  • Once phraseology and changes to facility directives are made, update the in-scope reference commands to reflect these changes.
  • Include change notes in “Change Log” when new files/resources are released to ZLC members.

With a deletion of a FAA publication

  • Notify DATM and TA.
  • Delete the in-scope reference materials in the alias command for it
  • Delete sector file diagrams (if any) for it.
  • Include change notes in “Change Log” when new files/resources are released to ZLC members.

With an added/new FAA publication

  • Notify DATM and TA
  • Once phraseology and changes to facility directives are made, update the in-scope reference commands to reflect these changes. (make new in-scope reference material for all appropriate positions)
  • Create appropriate diagrams for new publications
  • Include change notes in “Change Log” when new files/resources are released to ZLC members.

Finding Airports with instrument or FAA publications in your ARTCC

https://www.faa.gov/air_traffic/flight_info/aeronav/procedures/application/?event=procedure.advanced
  • Sort by state
  • Select at the bottom APD, DP, IAP or STAR but only do one at a time (one option per search)
  • Export that search list to CSV
  • Open the CSV file in a spreadsheet program and sort it by “comma”
  • Copy ICAO Code column into another sheet.
  • Now run a search on the same state for the next variable (APD, DP, IAP or STAR).
  • Once all ICAOs have been listed for that state for each variable, move to the next state and continue.
  • Once all states and vaiables are done, place all ICAO Codes in a single column and have the sheet sort by alphebetical order
  • Now have the sheet remove duplicates
  • Now start running through each code in airnav to see if it is owned by the ARTCC you are searching for. Delete the rows that are owned by other ARTCCs. (If you are smart with CTRL+H functions of word processing documents, you can actually automatically create airnav links next to your airports faily quickly and paste them next to your airports so all you have to do is click on that link as you go)
  • Remove spaces and you now have all the airports that have FAA publications of APD, DP, IAP or STARs.
  • Now the hard work comes when you start listing each of these procedures one by one to make diagrams and everything else.

Tools

FE WIKI