D5 Flight Ops · P1 ingest

Ingest connectors

5 of 5 on disk
Substrate targetP03 · P04

Postgres data spine + NATS JetStream

Cadence rangelive · 5–60 min · post-flight

Five families, each with its own SLA

AuthorityP05 append before publish

No bus message without an audit row first

Active feeds

Five live ingest sources

ConnectorOwnerSourceCadenceBus topicStateAction
Weather (METAR/TAF)D5Aviationweather.gov / OGIMET5–60 minaxiom.dispatch.weather.metar.v1On disk
NOTAM (ICAO)D5FAA NOTAM / EAD15 minaxiom.dispatch.notam.bulletin.v1On disk
ATC slots (Eurocontrol/CDM)D5Eurocontrol NM B2Bliveaxiom.dispatch.slots.allocation.v1On disk
ACARS downlinkD5ARINC / SITAliveaxiom.dispatch.acars.downlink.v1On disk
FDM (Flight Data Monitoring)D5 → D8Aircraft FDR / CSMpost-flightaxiom.safety.fdm.exceedance.v1On disk

Contracts

Connector contracts (per-feed)

Weather (METAR/TAF)Boundcontracts/connectors/weather.v1.yaml
NOTAM (ICAO)Boundcontracts/connectors/notam.v1.yaml
ATC slots (Eurocontrol/CDM)Boundcontracts/connectors/atc_slots.v1.yaml
ACARS downlinkBoundcontracts/connectors/acars.v1.yaml
FDM (Flight Data Monitoring)Boundcontracts/connectors/fdm.v1.yaml

Why connectors live above the bus, not in the bus

Each connector pulls from its native source, normalises through a versioned schema, and appends to P05 before publishing on P04. The bus carries authority-scoped events, not raw vendor payloads. If the upstream changes shape, the connector quarantines the message and a contract bump follows.

Ingest connectors | AXIOM