Decision driving
Transport
AOT airport flight status.
Arrivals and departures for AOT airports with airline, flight number, status, and passenger-facing board context. Some airport/app surfaces also mention gate, check-in counter, or baggage information, but these pages should be treated as brittle public surfaces rather than a guaranteed API.
Public
Public airport flight-status pages and Sawasdee by AOT flight-board surfaces
Free public web/app surfaces; no general documented public API was verified
Operational / near real time
2026-05-11
Public web, file, catalog, or documented endpoint access with no paid gate implied in the source profile.
source health, observation ingest, signal compute, decision compute
airport code, airport flight-status page URL, arrivals/departures board flags, public search-mode support, latest-update label flag, passenger-facing field claims, turnstile-gated board-query flag, bundle URL, source URL, confidence, last verified
Medium-high for discovery and context; operational reliability depends on endpoint stability.
Runtime truth
Decision driving
Yes
route, station, airport, pier, destination, terminal
official_airport_board_surface_score
where_to_go_today, where_to_stay, route_check
Feeds active observations and signals that currently influence traveler-facing decisions.
How this helps travel recommendations
Turns public airport board surfaces into route and stay confidence: whether a traveler can self-check an official arrivals/departures board, whether the airport exposes passenger-facing fields like gate or baggage context, and how much self-serve visibility exists before paying for a flight-based plan.
Endpoint and API notes
Arrivals and departures for AOT airports with airline, flight number, status, and passenger-facing board context. Some airport/app surfaces also mention gate, check-in counter, or baggage information, but these pages should be treated as brittle public surfaces rather than a guaranteed API.
Open the source endpoint or documentation. Return to the Thailand data atlas.
Developer reference
Use the public AOT /flight pages as the passenger-facing board-surface layer. Treat the visible page, metadata, and self-serve board surface as the stable signal; do not treat the Sawasdee by AOT GraphQL board query as a clean public server API because it requires a browser turnstile token.
Refresh every 15-60 minutes, with caching and backoff when the upstream fails.
Turns public airport board surfaces into route and stay confidence: whether a traveler can self-check an official arrivals/departures board, whether the airport exposes passenger-facing fields like gate or baggage context, and how much self-serve visibility exists before paying for a flight-based plan.
CAAT, AOT, Department of Airports, AEROTHAI, TMD Aeromet, NOAA, OAG, Cirium, FlightAware, Flightradar24, OpenSky, ADS-B Exchange, Amadeus, Skyscanner, Duffel, Sabre, IATA ONE Record, THAI Cargo, and OurAirports.
Example request
# Verify the documented flight endpoint before production use.
curl -L "https://suvarnabhumi.airportthai.co.th/flight" -H "Accept: application/json"Failure modes
- The public AOT flight-status pages are real passenger surfaces, but the live board query is protected by a browser turnstile token.
- HTML, Next.js bundle paths, metadata fields, and visible board-surface markers can change without notice.
- The public page can prove self-serve board visibility without proving server-safe machine access to live flight rows.
- Passenger-facing field claims such as gate, check-in, or baggage context do not guarantee complete realtime accuracy for every flight.
Last checked and source confidence
Last checked: 2026-05-11.
Source confidence: Treat this profile as strongest for the exact role named above. It is weaker when the source is stretched into live availability, legal proof, or traveler-fit decisions it does not directly prove.