Search the site

Type at least two letters.

EN
Talk to AIR NEXUS
MenuClose
Talk to AIR NEXUS

Technology

Cooperative & External Aviation Data

Keep cooperative data distinct, and useful.

Discuss Aviation Data Integration

What it observes

It brings in data that aircraft and operators choose to send: position reports, identification messages and, for drones, broadcast identity. Each arrives as a message, not as an observation made by the system.

The principle

A public-safe diagram of the mechanism, drawn without real values.

The diagram shows a data flow from external feeds to a shared record, with each message keeping the name of the feed that carried it. The cooperative source is drawn as its own family, never merged into the sensed ones.

Unified state: Data table
ItemValue
Unified stateSource A, Source B
Unified state RD05Data status: IllustrativeEvidence level: E0 · ConceptQuestion answered: What does a unified state rest on?One small state glyph sits above the sources that support it, each listed by name. The glyph is never shown without its support underneath.Limitation: The glyph is a drawn symbol. It is not a detection.

Where it sits in the chain

It joins the first band as a distinct source family. After time alignment it is correlated with what the sensing sources saw, and a disagreement between the two is kept, not smoothed away.

See the architecture

What it does to the data

A message becomes a record that says who reported it, when, and in what form. Where it matches a sensed observation the link is stated; where it does not, both stay on the record.

How it shows up in the data

Data flow: Data table
StageValue
1Sources
2Model
3Policy
4Interface
5Consumer
6Audit
Data flow CH13Data status: IllustrativeEvidence level: E0 · ConceptQuestion answered: How does data flow through the architecture?A pipeline of six stages, from sources to audit, shows how data moves through the model, the policy and the interface to the consumer, with a record kept at the end.Limitation: A conceptual flow. It does not describe a deployed system.

Strengths / Constraints

Strengths

  • It carries identity and intent that sensing cannot, where a sender chooses to provide them.
  • It covers aircraft that are expected and cooperating, so what is not accounted for stands out.
  • Its provenance is explicit: every message names its feed.

Constraints

  • It reports only what a sender chooses to say, and a sender can be wrong or silent.
  • The absence of a message is not the absence of an object.
  • Feeds differ in age, completeness and reliability, and are outside the system's control.

Environmental dependencies

Coverage, feed delay, local rules on who must broadcast and the state of each external feed change what arrives. The page states these as conditions and gives no completeness figure.

Limitations

  • Source availability: external feeds can stop, lag or change format without notice.
  • Environment and rules: who must broadcast, and where, differs between places and over time.
  • Confidence variability: a message is as reliable as its sender and its feed, and the two are not the same.
  • Integration dependency and validation scope: its value rests on joining the sensed picture, and it is a design at the evidence level of its projects; no completeness or delay is stated.

Evidence and validation

This page claims nothing above the level of the projects it rests on.

Projects behind this