Fixes.txt
Harry S edited this page Jul 24, 2023
·
4 revisions
Contained within these files are fixes pertaining to a particular airport and its procedures only. All other Fixes should be contained within one of the files described on this page.
These fixes take the format of a 5 character fix name, followed by a 10 digit coordinate format.
e.g. OLEVI N051.11.17.400 E000.06.11.300
What type of fixes would be contained within this file?
- Any that relate to an airport's RNP approach(es), and do not appear in ENR 4.4.
- Any that relate to an airport's RNAV SIDs, and again, do not appear in ENR 4.4.
- Any that relate to an airport's 'Air network' used for making and running sweatbox files (These will follow a different naming format).
e.g. Gatwick's file
For Sector File Users:
For Developers:
- First Time Contributor's Guide
- WIP: The AIRAC Process on GitHub
- Contributing Guide
- More specifically, on submitting pull requests...
- Coordinates
- How to Create SMR Displays
- Using GitHub Labels
- Using Milestones
- Using Projects
Repository Folders:
- Root
- _data
- Agreements
- Airports
- ATS Routes
- ARTCC
- Doc
- Misc
- Navaids (Fixes/NDBs/VORs)
- Ownership
- Sectors
File Contents: