The Airport Board is designed to avoid a common travel-site failure: presenting simulated, stale or inferred information as if it were live operational data. These are the rules the site follows.
The Airport Board does not fabricate scheduled flight rows. Each airport page keeps the airport or airline official board as the primary operational source. Gate, terminal, delay and last-minute operational decisions should be verified with that official source or the airline.
METAR and TAF data are fetched server-side from the U.S. NOAA Aviation Weather Center. Results are cached to reduce upstream requests. If the feed fails, The Airport Board may show a previously fetched real observation marked stale; it does not synthesize weather.
Nearby aircraft positions come from ADSB.lol and are displayed under its Open Database License attribution. Positions are informational only and never intended for navigation or safety-critical use. The site caches this feed and limits refresh frequency.
Airport location maps use OpenStreetMap and show the airport area. Indoor gate detail varies, so The Airport Board also links to each airport's official terminal map when available.
Fares, terminal-transfer instructions, rail connections and similar operational facts are checked against airport authorities, transport operators or tourism authorities. Each airport hub lists its sources and a verification date.
Guides are original The Airport Board summaries created around traveler questions and practical travel decisions. They include an update date and source links when they contain airport-specific operational facts. They are not substitutes for airline, immigration or airport instructions.
Translated guides are mapped to a source-backed English origin rather than generated as empty language variants. The translated page keeps the same official source trail, adds language-specific navigation and is published only when the body content is substantive. Automation and AI assistance may support drafting or formatting, but they are not represented as firsthand airport experience.
Live feeds refresh through server-side caches. Editorial facts should be rechecked on a schedule and whenever an airport changes terminals, transport systems, pricing or connection procedures. Each airport record stores its own verification date.
The Airport Board can contain affiliate or partner links in clearly relevant travel-service contexts. Partner links are kept visually distinct from operational sources. A commercial relationship does not change which official airport, transport or aviation source is shown for time-sensitive travel information.