Fuse selected aircraft data and validate routes

[kewonit]

Summary

• Preserve response time, observation time, position age, and provider identity.
• Fetch one fresh adsb.lol hex result when an aircraft is selected.
• Fuse the current map record, the fresh result, and local registry data.
• Keep timing and provider identity with the selected coherent position group.
• Prefer FAA metadata for US registrations and Mictronics metadata elsewhere.
• Record all contributing sources. Cancel stale requests and cache selected-aircraft results for 30 seconds.
• Send bounded aircraft context to route lookup and label results as Reported route.
• Hide routes that conflict with corridor, endpoint, altitude, or ground-state checks.
• Cache positive route results for five minutes and negative results for one minute.
• Keep the existing OpenSky fallback unchanged. Do not add adsb.fi fan-out for selected aircraft.
• Do not store ADSBDB route snapshots.

Stack

• Stack position: 2 of 3
• PR base: data/open-aviation-data
• Base commit: d6d80ff9aaa1877e152fbaa025ef9dff14c486c8
• Previous PR: Add reproducible open aviation data #40
• Next PR: Simplify the aircraft details sidebar #42
• Changelog impact: PR Simplify the aircraft details sidebar #42 contains the single consolidated 0.8.9 entry to prevent stack conflicts.

Verification

• pnpm test:data with 11 passing tests on the full stack
• pnpm data:check with 496,914 aircraft and 72,490 airports
• pnpm test with 351 passing tests on the full stack
• pnpm lint with no errors and four existing warnings
• pnpm build
• Coherent timing and provider regression coverage
• DAL1598-style incorrect SFO route regression coverage

Production safety

• main is production.
• Keep this PR as a draft and unmerged for review.
• Do not enable auto-merge or deploy from this PR.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
aeris-flight	Ready	Preview	Aug 23, 2026 6:27pm