Aviation intelligence¶
Aviation intelligence merges qualified aircraft observations from 1090ES, 978 UAT, TIS-B, and ADS-R into a protocol-agnostic current view while retaining the source and timestamp of every field.
The implementation boundary is AviationIntelligenceService; its live reducer
and historical worker/index path are deliberately separate. The Aviation
workspace and map consume this one service and the shared aircraft selection
target; neither owns a parallel aircraft store or opens another receiver.
Aircraft are not amateur stations: ICAO addresses, registrations and transmitted
flight IDs must not manufacture an FCC association.
Identity and state¶
The address qualifier determines the identity namespace. Confirmed ICAO
observations use icao:<address> across 1090ES and UAT. UAT non-ICAO addresses
stay in their qualified namespaces; TIS-B track-file and ADS-R-other keys also
retain the site identifier where supplied. A six-digit hex value alone does
not establish an ICAO airframe. Callsign, registration, operator and temporal
flight/track instance remain distinct facts, not convenient merge keys.
Protocol is observation provenance, not aircraft identity. New adapters extend
the shared aviation contracts rather than creating protocol-specific aircraft
stores. Current ingestion accepts validated adsb1090 and uat978 events;
names reserved in the protocol type do not prove ACARS, VDL2 or HFDL support.
Observation identity combines receiver/path, capture epoch, rational source sample position, protocol and raw-frame signature. Decoder job, tab, arrival time and replay time are excluded. Replaying the same captured frame therefore must not inflate counts or make old evidence the newest state.
flowchart TB
A[CRC-valid ADS-B frame] --> O[Normalized observation]
U[RS-valid UAT frame] --> O
T[TIS-B / ADS-R report] --> O
O --> RAW[(Capture-time observations)]
O --> CUR[Per-aircraft current reducer]
FAA[Local FAA metadata] --> CUR
CUR --> DELTA[Changed ICAO set]
DELTA --> LIST[Aviation table]
DELTA --> MAP[Markers, labels, trails]
RAW --> RANGE[Indexed history worker]
RANGE --> REPLAY[As-of aircraft state]
Current fields select fresh, trustworthy observations independently: position, altitude, track, velocity, vertical rate, squawk/status, identity, and category need not all come from the same last frame. Details show provenance and age.
FAA enrichment and category¶
The optional local FAA dataset adds registration, manufacturer, model, type and released registrant/owner evidence. Owner is not proof of the operator of the current flight, and a registry address is not an aircraft position or operating base. Withheld and missing fields stay missing. Broad presentation category uses the strongest available metadata:
- commercial/airline;
- civilian/private/general aviation;
- government/military; or
- unknown.
Government/military classification requires strong owner/operator or known type evidence; a dramatic callsign is supporting evidence, not a commissioning certificate. Unknown remains a valid result.
The appliance's rfsentry-aviation-update stages a source-hashed generation of
the FAA Releasable Aircraft Database, validates it and atomically switches its
current symlink. The last valid generation survives refresh failures and is
served read-only at /aviation/faa/. This bounded metadata job does not acquire
IQ; decoding, fusion, history queries and map rendering remain browser work.
The browser reads the manifest and fetches ICAO-prefix shards on demand. Resolved records persist in IndexedDB with source/generation provenance; RAM maps and shared in-flight promises avoid repeated lookups and duplicate shard fetches. A per-service resolved-address set also remembers no-match results. This is not a complete in-memory registry import or a durable negative-result database. Metadata failure must not stop RF learning. See dataset ownership.
Live state versus history¶
Live ingestion maintains compact current snapshots and per-aircraft authoritative position trails. A coalesced publication carries only changed aircraft. It never reconstructs current state by replaying all observations.
AviationStore owns the dedicated rfsentry-aviation-intelligence IndexedDB:
raw observations, FAA metadata, UAT broadcasts, compact aircraft heads,
checkpoints and projection progress. Aircraft history is not the FCC SQLite
corpus or an OPFS payload archive.
The production history worker restores compact heads at startup, not every raw observation. If the projection needs rebuilding, it uses bounded capture-order cursor batches, saves resumable progress and yields between batches. Heads and checkpoints are rebuildable acceleration structures; raw observations remain the evidence. The non-worker fallback used by deterministic tests still hydrates its in-memory history index; production browsers use the worker path.
Routine browsing defaults to a rolling 24-hour horizon, but details are paged; 24 hours is not a command to put every observation into RAM. Per-aircraft pages use the aircraft/capture-order index. Historical snapshots start from an as-of checkpoint and fold the required later observations up to the cursor. Older evidence remains available for explicit investigation, rather than being deleted at the browsing boundary.
The history worker's requested-page/snapshot cache is byte-budgeted and expires on inactivity; maintenance continues even with the decoder stopped. Its byte accounting is an estimate, not a browser resident-memory measurement. Eviction releases derived query results, not persisted evidence. The service separately ages recent CPR/reference observations out of RAM. See history/storage architecture and operator storage guidance.
Trails and movement¶
Trails contain decoded positions only. Interpolated marker positions smooth display but are not evidence and are never persisted. Segment color reflects the altitude at its observed endpoints. All-trail and military-path visibility allocate/update per-aircraft retained GPU blocks without rebuilding global relationship lists.
When ground track is fresh, the marker points in the direction of travel over the ground. For example, an aircraft flying an easterly track in a crosswind may point its nose into the wind to stay on course. Heading is recorded separately when the aircraft reports it.
Replay guarantees¶
An as-of result includes only observations at or before the selected reference
time, using the lane's shared MapReferenceTime. Scoped asynchronous snapshot
and trail requests are latest-request-wins; cancellation/supersession prevents
late historical responses replacing the selected view. Returning to Live
invalidates pending historical work, takes a compact current snapshot and
resumes deltas. Live updates do not reconstruct historical snapshots.
FAA limitation: the metadata schema records source/generation, not validity intervals. Historical reconstruction can attach cached FAA metadata without an effective-date filter; it does not prove who owned or operated an airframe at the replay time. The roadmap's stronger requirement to exclude later metadata from historical state remains unresolved. Capture-filtered RF positions and flight IDs must not be described as qualification of that separate metadata requirement.
Ledger and qualification¶
docs/roadmap/aviation-satcom.md Phase 10 records an accepted first 1090ES/shared-service,
selection, workspace, map and FAA foundation, not completion of the aviation
roadmap. Current source also implements UAT ingestion and indexed history
paging; the original foundation paragraph predates those changes. Their code
presence does not close the ledger's remaining protocol, replay, analytics or
operator-acceptance gates.
aviationService.test.ts covers qualified cross-protocol identity and broadcast
separation; aviationHistoryIndex.test.ts covers capture ordering, replay,
paging and observed trails; aviationPersistence.test.ts covers durable paging,
heads/checkpoints and cache eviction. aviationScale.test.ts is a local scale
regression, not proof of continuous live reception on the current appliance.
Broader corrupted-input, identity-reassignment, metadata-temporal and
simultaneous receiver/DSP/DVR/live protocol matrices retain their separate
qualification requirements. See the
aviation ledger map.
Received traffic and weather are experimental, not safety-certified flight guidance. Data stays browser-local by default; publishing to an outside tracking or messaging service requires explicit operator approval.