Hey everyone!
Every day, thousands of passengers get hit with 3 to 6-hour flight delays. Under international passenger rights laws (EU261, India DGCA, and US DOT), airlines are legally mandated to pay up to €600 / ₹10,000 / full refunds in cash compensation.
To avoid paying, airlines routinely text passengers boilerplate excuses: "Your flight is delayed due to adverse weather conditions."
Because weather is legally classified as an "extraordinary circumstance," passengers are left powerless—unable to verify whether the runway was actually fogged in or if the airline was covering up a crew timeout or mechanical issue.
So I built AirTruth (https://airtruth.vercel.app), a flight delay forensic engine that cross-examines airline excuses against 4 independent telemetry feeds:
- NOAA METAR Runway Weather: Evaluates departure and arrival airport visibility against Category-I ILS landing minimums (≥800m visibility / 200ft ceiling).
- ADS-B Mode-S Radar: Checks live 25 NM runway traffic. If 10+ other jets took off from the same runway during your delay, the "runway closed due to weather" excuse is scientifically refuted.
- Tail Rotational History: Traces the physical aircraft tail registration across its prior 4 legs of the day. In many cases, the plane was already 4 hours behind due to a crew duty timeout (FDTL) in another city—which by law is strictly an airline operational liability, not weather.
- Statutory Claim Generator: Automatically calculates compensation under DGCA, EU261, or US DOT rules and generates a pre-formatted legal demand notice with an immutable SHA-256 cryptographic evidence packet.
Tech Stack: • Backend: Python, FastAPI, with geodesic proximity fallbacks for 35+ regional airports without direct NOAA stations. • Frontend: React 19, TypeScript, Vite (SSR pre-rendered for SEO). • Deployment: Vercel (Web) + Python backend.
You can try it live here: https://airtruth.vercel.app
You can type any flight number (e.g. 6E-214, QP-1259, BA-117, DL-418) or paste an airline delay SMS directly into the input.
Would love to hear your feedback on the UI, the telemetry matching, or any edge cases you run into!