Enter CID

VATGlasses was originally developed by Lenny Colton as a Windows application and released in 2020, at the height of the COVID-19 pandemic. The original tool has been deprecated and is no longer compatible with the VATSIM Status API.

---

Lenny first published the VATGlasses website in early 2022, with coverage for the UK only. The site has now expanded with many countries taking part and is moving towards global coverage. Thank you to everyone who uses and supports the site!

---

All of the servers which host the VATGlasses website and associated services are managed internally. We rely on the community to help fund this - we can't do it on our own! Please consider subscribing to our Patreon if you like the site!

---

Aircraft icons are provided by SimAware and are licensed under CC BY-NC-SA 4.0. The remainder of the VATGlasses project is proprietary and should not be reused without permission.

Data is maintained either by local staff or the VATGlasses team. We are not accepting any new VATGlasses-managed areas, but local staff are always welcome to add their sectors to our GitHub. Data should not be reused without permission.

---

We have a parallel site for testing new data updates before publication. The site and its repository are both private. Please create an issue on the GitHub for access. N.B. Only staff members who actively maintain a data set will be granted access.

---

Data for unsupported areas is taken from VAT-Spy. If your FIR is displayed incorrectly, please consider adding your airspace to our repository. It's possible to add full sectorisation for both en-route and airports, or to only add airports and leave en-route sectorisation dynamic.

• Airborne sectors are displayed on the map, based on altitude.
• Use the slider in the top-right to select an altitude.
• Some sectors may cover only high or low altitudes.
• Click on a sector to see its name and owner.
• All sectors covered by one controller are the same colour.
• Only online sectors are shown. To see offline sectors, too, click here.

---

• Airport Labels as follows:
• A - Approach/Departure
• Low airspace close to the airport. May be a nearby major Tower at satellites.
• Covers Tower if offline.
• T - Tower
• Runways and some very low airspace.
• Covers Ground if offline.
• G - Ground, Ramp, or Apron
• Taxiways, ramps, and/or aprons.
• Covers Delivery if offline.
• D - Clearance Delivery
• ATC route clearance for departures.
• I - ATIS
• Automated broadcast with weather, runways, and procedures.
• Airports with empty labels are either covered by an En-Route controller or have aircraft on the ground.
• En-route controllers provide all services (from Delivery to Approach/Departure) at all airports they control.
• Click on an airport marker to see who to call before departure.

This is the beta version of VATGlasses, which is used by maintainers to test their changes.

This site should be used by maintainers only. Lots of the data is old and/or inaccurate.

For the latest, accurate ATC sectors, visit the main VATGlasses site.

You can create a custom ownership file or select from one of the pre-made options. Ownership changes can take up to 60 seconds to reflect on the map.

To get started with your own ownership file, either download the current ownership using the button on this page or download one of the pre-made options from the GitHub repository.

---

Sector ownership can be created by combining ownership orders. Each order contains one or more ATC positions. A full list of ownership orders available for your facility can be found in your positions.json file on our GitHub repository.

For example, if ZOA's NorCal Toga sector is assigned the following ownership order: ["N1T", "40", "ZOA_COMBINED"], it will first by owned by NorCal Toga and then combine into NorCal Area A according to the NorCal SOP. If no NorCal A positions are online, it will be owned by ZOA Sector 40 and then combine according to the ZOA SOP. If no other valid sectors are online, it will revert to the ZOA Combined controller.

---

Airport ownership can be defined in a few different ways. If multiple types of ownership are defined, they will be prioritised in descending order according to this list.

• Default - Any airport will automatically be owned by its _DEP controller or by _APP in their absence. This can be disabled by adding "default": false to the airport entry.
• Top-Down - Top-down ownership can be defined in the same way as for ATC sectors above, like this: "topdown": [YOUR_OWNERSHIP_HERE]
• Sector - The airport can be assigned to an ATC sector (the airspace, not the position), like this: "sector": "N1T". Whoever owns that sector will also own the airport.
• Major - The airport can be assigned as a satellite of another airport, like this: "major": "KSFO". The highest priority APP/DEP/CTR position for the designated major airport will also own the satellite airport.

If an airport is not included in the ownership file, DEL/GND/TWR and default APP/DEP ownership will apply automatically.

---

If your ownership file is commonly used, speak to your local VATGlasses engineer about adding it to the list on this page for quicker access.