Runway.txt

When to be included

We only include runway definitions for airports that meet one or more of the following criteria:

• Is situated inside controlled airspace
• Has a defined TWR/APP position (i.e. an ATC service - not an AFIS/AG!)
• Has SIDs/STARs (or uses STARs of a nearby airfield for inbound IFR aircraft)
• Has Instrument Approach Procedures
• Has a defined ATIS frequency

---

Definition

Each runway is defined on its own line in the Runway.txt file. A runway definition is comprised of the following eight space-separated fields:

1. Runway number with an optional L, R, or C for Left, Right or Center.
2. Runway number for the opposite end.
3. Magnetic runway heading.
4. Magnetic runway heading for the opposite end.
5. Latitude of the runway start point.
6. Longitude of the runway start point.
7. Latitude of the runway end point.
8. Longitude of the runway end point.

e.g. 17 35 164 344 N054.39.28.520 W006.13.43.040 N054.38.33.190 W006.13.11.960

---

Notes:

• Where a runway designator is only numeric (i.e. no L, R or C), an extra space should be added after it for alignment purposes.
• The magnetic heading is used as available from charts (e.g. Civil Aerodrome charts or Approach procedure charts). The magnetic heading value is not actually used by EuroScope for anything, so if no magnetic value can be found, the true value may be used instead as the closest 'best guess'.