Runway Almanac uses the nightly CSV exports published by OurAirports. OurAirports releases the data to the Public Domain and provides no guarantee of accuracy or fitness for use.
Selection policy
The default build publishes medium and large fixed-wing airports with valid coordinates and at least one reported open, non-water runway with a positive published length. A configurable quality gate controls which profiles are indexable and submitted in the sitemap.
Calculations
- Feet are converted to metres with
feet × 0.3048and rounded to the nearest metre. - Nearby-airport distance uses the WGS 84 coordinates and the haversine formula.
- Runway orientation uses the source fields ending in
_heading_degT; these are true headings, not magnetic headings. - Country percentiles compare the longest reported open runway among profiles included in the same build.
Runway-end records
Low-numbered and high-numbered runway-end fields are presented independently according to the OurAirports data dictionary. End coordinates are source-published runway-end centre points; they are never replaced with the airport position. Blank headings, elevations, coordinates, and displaced-threshold lengths remain missing, while an explicitly published zero remains zero. Displaced-threshold values are not used to infer declared distances such as TORA or LDA.
Simulator Runway Finder
The finder excludes reported closed, water, zero-length, and helipad-labelled rows. Length, surface, and reported-lighting filters must match the same runway record; elevation and runway-count filters apply to the airport. Filter state is kept in the URL fragment so one canonical tool page serves every combination.
Live report feeds and language aid
METAR and TAF data is requested from the AviationWeather.gov Data API through a cached same-origin endpoint. Simulator ATIS text comes only from the public VATSIM Data API and is labelled accordingly. English and Turkish explanations are deterministic conversions of structured fields and a limited abbreviation glossary; they are not official translations or weather briefings. Raw reports remain visible.
Snapshot
Data as of:
Airport dataset SHA-256: 4bc8232ba1f40e0d6b6c721e24b3a057160a1302f2b9ff7953560a5368e134ff
Corrections
Source-record corrections should be submitted to OurAirports so the wider open-data community benefits. Site implementation issues can be reported in the project's GitHub repository.