Privacy & Signing · verification standard

Zero blind trust.

How AIRTRUTH collects public aviation telemetry, signs ADS-B coordinates, and keeps statutory claim verification tamper-evident.

  • SHA-256 coordsEvery Mode-S ADS-B coordinate fix and rotation leg is cryptographically sealed into the claim packet.
  • Zero carrier lock-inOperates purely on public transponder feeds, NOAA/IMD METAR reports, and airport slot logs — even without carrier API cooperation.
  • Stateless verificationDemo and claim verification logs expire automatically and keep no passenger PII beyond ticket route & claim ID.
  • Deterministic chartersCompensation payouts (€250–€600 EU261, $400–$650 US DOT, ₹5k–₹10k DGCA) follow statutory statute text without LLM hallucination.
01
Public telemetry ingestion

ADS-B, METAR & runway logs

AirTruth cross-references aircraft hex ICAO24 broadcasts against airport meteorological reports (METAR/TAF) and runway movement logs. Because airframe position and runway departures are public safety broadcasts, airlines cannot retroactively scrub prior delays.

02
Tamper-evident claim packets

Signed ADS-B flight coordinates

Each generated statutory claim packet includes raw Mode-S coordinates (lat, lon, altitude, UTC timestamp), ICAO24 transponder hex, 4-leg rotation delays, and deterministic SHA-256 coordinate seals verified by AirTruth.

03
Regulated passenger data

Minimization by default

Optional PNR / booking references entered during escalation never train external models and can be cleared immediately after exporting your signed JSON / claim filing packet.