Methodology — how LayoverDB decides

Data rule: UNKNOWN > WRONG

Every factual field in the dataset is optional. If it cannot be verified against an official source it stays null and renders as Unknown. Facility pages are only generated when at least one verified location exists. The checker returns insufficient data rather than inventing a transfer time.

How the layover checker computes a verdict

  1. Total layover. Departure time minus arrival time, in airport local time. A departure earlier in the day than arrival is treated as an overnight connection crossing midnight (+24 h).
  2. Transfer time. The officially published range for the terminal pair. Same terminal: 0. No verified data: the engine refuses to estimate.
  3. Buffers. +30 minutes to re-clear security when your route leaves the secured area (landside transfer or international→domestic); +60 minutes for immigration and customs when entering the country. These are heuristics and are always shown, never hidden.
  4. Usable time = total − transfer (upper bound) − buffers.
  5. Verdict: ≥60 min usable → likely comfortable; 30–59 → tight; <30 → very tight; missing inputs → insufficient data.

Facility reachability states

  • Reachable — airside-compatible path exists (same terminal, or a verified airside transfer).
  • Possibly reachable — landside facility or landside transfer: you can get there, but immigration and security re-entry may apply depending on your itinerary and nationality.
  • Not reachable — airside facility in a terminal you cannot return to after a landside onward transfer.
  • Unknown — the official source does not document the zone or the path.

What this is not

The checker's output is an informational estimate, not a guarantee. Flight delays, queue lengths, gate changes and airline minimum connection times all live outside our data. Visa and entry questions are answered only by links to government sources — we never summarize them into advice.