Flights, airports, fares, tracking, weather, and slots
Thailand flight intelligence only works when regulation, airport boards, flight tracking, fares, weather, NOTAM, slots, and cargo stay separate. Use CAAT for AIP Thailand, aircraft registers, AOC holders, official air-transport statistics, and slot-coordination rules; AOT and Department of Airports for airport flight boards and airport traffic statistics; AEROTHAI for NOTAM and AIS layers; TMD Aeromet and NOAA for aviation weather; OAG, Cirium, FlightAware, Flightradar24, OpenSky, and ADS-B Exchange for schedules, status, and tracking; Amadeus, Skyscanner, Duffel, and Sabre for fares, availability, and booking; and THAI Cargo plus IATA ONE Record for cargo-service and schema context.
Current trip check
The page below is still useful without JavaScript. When current checks are available, this panel points you to the Today, comparison, and route pages that matter before committing.
Showing static flight planning links until the latest check is available.
Use this order when official aviation documents, airport boards, ADS-B tracking, weather, and booking APIs disagree.
| Rank | Source layer |
|---|---|
| 1 | CAAT, AEROTHAI, AOT, Department of Airports, and TMD Aeromet for official airport, airspace, weather, statistics, operator-legality, and slot truth. |
| 2 | OAG, Cirium, FlightAware, Flightradar24, OpenSky, and ADS-B Exchange for live schedule, status, tracking, and aircraft-position layers, with each source carrying its own operational blind spots. |
| 3 | Amadeus, Skyscanner, Duffel, Sabre, and direct-airline retail layers for fares, availability, ancillaries, and booking flow where authorization exists. |
| 4 | OurAirports and other open master-data backups for airport, runway, and code-reference sanity checks when official Thai pages are thin or hard to automate. |
| 5 | THAI Cargo, IATA ONE Record, and shipment-specific cargo systems for cargo schedule and workflow context without pretending air-cargo operational data is a public bulk feed. |
These rules keep regulatory truth, airport boards, commercial status feeds, fare engines, and restricted passenger or cargo data from collapsing into one misleading record.
| Rule | Meaning |
|---|---|
| 1 | ADS-B position feeds are not the same thing as passenger-facing flight status, airport boards, gate data, or cancellations. |
| 2 | A published schedule is not the same thing as seat availability, a live fare, or a bookable itinerary. |
| 3 | Airport flight-board pages are useful public surfaces, but they are not the same thing as a documented public API contract. |
| 4 | CAAT AIP and slot rules are official static and seasonal truth layers; they should not be merged blindly with live airport operations or commercial fare feeds. |
| 5 | Gate, baggage-belt, and check-in-counter data are airport-local fields and can be missing or delayed in global schedule APIs. |
| 6 | Passenger APPS, PNR, check-in, boarding, and payment data are restricted security or booking-context layers, not public aviation data. |
| 7 | Cargo schemas, cargo schedules, and AWB or e-booking workflows should stay separate from passenger flight boards and fare-shopping layers. |
Each aviation layer answers a different question. A CAAT register is not a live departure board, an airport board is not a fare engine, an ADS-B track is not a baggage-belt feed, and a public weather page is not the same thing as a clean API contract.
CAAT provides the official Thai aviation spine: AIP, eAIP, AOC holders, aircraft register, air-transport statistics, and slot-coordination rules.
AIP licensing limits matter arrivals and departuresAOT and the Department of Airports provide the public airport-board layer and airport-level traffic statistics that travelers actually look at before departure and arrival.
public boards are brittle live statusCommercial status and tracking APIs plus ADS-B networks provide aircraft position, delay, and movement context, but they do not all answer the same question.
ADS-B is not full status fare searchShopping and booking APIs answer whether a flight is for sale, how much it costs, what baggage or ancillaries exist, and when a quote expires.
prices expire quickly airport weatherTMD Aeromet, NOAA, and AEROTHAI provide the disruption context that changes whether a route or airport is just delayed or operationally constrained.
warning cadence differs by product market contextSlot coordination, airport capacity, passenger volumes, and traffic trends help explain why a route is crowded, constrained, or strategically important.
seasonal slot notices change cargo schemaCargo standards and shipment workflows are useful, but passenger APPS/PNR and detailed cargo events are restricted or partner-only and must not be treated as public feeds.
shipment data is account-specificThese pages turn the source model into airport, route, fare, weather, and delay-risk guidance travelers can actually use.
Bangkok aviation planning across Suvarnabhumi and Don Mueang needs separate airport-board, fare, weather, delay, and airport-ground-friction logic.
Bangkok airport choice / arrival planning airport guideSuvarnabhumi flight intelligence should combine public airport boards, official airport statistics, fare and tracking APIs, weather, and airport-specific disruption context.
international departures / long-haul arrivals airport guideDon Mueang flight intelligence needs low-cost carrier schedule context, airport boards, domestic-route friction, weather, and delay-risk modeling kept separate.
domestic flights / low-cost carriers airport guidePhuket flight planning should combine airport boards, island weather exposure, seasonal traffic, fares, and tracking rather than relying on a single departures page.
island arrivals / weather-sensitive flights airport guideChiang Mai flight intelligence should separate airport-board truth, northern seasonality, smoke-related travel planning, and commercial fare-shopping layers.
northern trips / smoke-season planning airport guideSamui flight planning needs airport constraint, slot and capacity context, fares, weather, and route availability kept visible because the airport behaves differently from Thai mainland gateways.
island access / premium route planning route guideBangkok to Chiang Mai flight decisions need route schedules, live fares, airport choice, smoke-season timing, and disruption context separated.
route comparison / fare checks route guideBangkok to Phuket flight planning needs flight status, route depth, fare competition, weather, and airport-transfer logic kept separate.
island access / fare comparison route guideBangkok to Krabi routes need airport-board, fare, weather, and schedule-confidence logic kept separate so island-side plans stay realistic.
Andaman trips / weather-aware booking route guideBangkok to Koh Samui flights need fare-shopping, airport constraint, weather, and schedule-capacity context handled together because the route is sensitive and often expensive.
premium domestic flights / island route timing delay-risk guideDelay-risk pages should combine airport boards, status/tracking feeds, weather, NOTAM, seasonal traffic, and airport-specific friction instead of relying on one source.
irregular operations / schedule resilience aviation weather guideAirport-weather pages should combine TMD Aeromet, NOAA, and airport-specific flight impacts so travelers know whether the issue is rain, visibility, storms, or broader operational disruption.
airport weather checks / storm-day planningUse CAAT for AIP Thailand, aircraft registers, AOC holders, official air-transport statistics, and slot-coordination rules; AOT and Department of Airports for airport flight boards and airport traffic statistics; AEROTHAI for NOTAM and AIS layers; TMD Aeromet and NOAA for aviation weather; OAG, Cirium, FlightAware, Flightradar24, OpenSky, and ADS-B Exchange for schedules, status, and tracking; Amadeus, Skyscanner, Duffel, and Sabre for fares, availability, and booking; and THAI Cargo plus IATA ONE Record for cargo-service and schema context.