How we cover airports

Every crowd prediction and airport data point on this site is derived from a named primary source, in priority order:

• Primary: FlightAware AeroAPI (real, dated flight schedules and aircraft data)
• Secondary: FAA Air Traffic Control System Command Center (delay reports)
• Tertiary: Individual airport-published terminal, TSA wait, and parking data
• Never: AI-generated statistics, unattributed round numbers, or Wikipedia-scraped filler

If an editorial guide contains an opinion or a personal observation, it is labeled as such. Data is data; opinion is opinion.

Every article carries a real, named byline that links to a full author page with a photo, credentials, and public contact info. We do not publish under pseudonyms and we do not publish AI-generated articles without human editorial review and byline responsibility.

Before an article is published:

• Every airport claim is cross-checked against the airport's own website
• Every numeric statistic is either sourced to a public dataset or generated from our own AeroAPI-backed data
• Every product mention (credit cards, lounges, services) is verified against the official issuer or operator page in the week of publication
• Every embedded link is manually clicked before publish

Airport policies, prices, and TSA rules change. We handle it three ways:

• Evergreen guides (how-to, methodology, FAQs) — reviewed quarterly, timestamped when updated
• Specific-product guides (credit cards, lounges) — reviewed at least twice a year and re-dated on republish
• Data pages (live crowd, insights) — regenerated automatically from AeroAPI multiple times per hour

When we make a material update, we add an "Updated:" line to the article and log substantive changes in the corrections log.

We do not:

• Accept paid placements, sponsored posts, or "review swaps"
• Let affiliate relationships influence which products or airports we cover
• Publish content we have not personally reviewed, whether AI-assisted or not
• Republish or lightly rewrite content from Wikipedia, airline blogs, or competitor sites
• Use scraped or purchased email lists for our newsletter
• Serve interstitial or pop-under ads on any page

We take reader corrections seriously. If you spot an error:

1. Email jamursch@gmail.com with "Correction" in the subject, including the article URL and the specific claim
2. We reply within 3 business days
3. Confirmed corrections are updated in-line, timestamped, and logged publicly on the corrections page
4. We never quietly delete errors — the log stays public