How to read an event record
Every PNTMAP™ event is published in one fixed format. This page explains what each field means, what it does not mean, and where the limits of the evidence lie.
PNTMAP is an intelligence and situational-awareness service. It is not an authorised navigation source and must not be used as the sole basis for flight planning, navigation or aviation safety decisions.
Worked example
A fully populated record, clearly marked as invented, is published as the synthetic demonstration record. It uses the same component as live records, so the format shown there is exactly the format a real record uses.
Event reference
A permanent identifier of the form PNT-EVT-000123. It never changes and never gets reused, so it can be cited in a safety case, a claim file or a regulatory submission.
Evidence class
Where the record sits on the published evidence ladder, from an unexplained ADS-B integrity anomaly through to confirmed spoofing. The class describes the evidence held, not a conclusion about intent or source.
Confidence and severity
Two separate judgements. Confidence expresses how well supported the classification is; severity expresses how disruptive the observed degradation was. A high-severity record can carry low confidence, and vice versa.
Affected measurement, sample and baseline
The measurement is the share of distinct aircraft in the cell reporting a degraded navigation integrity category. The sample gives that share as n/N so a small-sample figure cannot be mistaken for a network-wide statistic. The baseline is that cell's own recent history, not a national average.
Persistence
How long the degradation held. A single window above baseline is an observation; a record requires the degradation to persist.
Supporting nodes and capabilities
Which nodes contributed and which of their capabilities were live at the time. Capabilities marked planned did not contribute anything to the record.
Data latency and coverage limitations
How quickly the contributing telemetry reached the platform, and the plain statement that only airspace inside the listed nodes' reception range is described. Absence of a record elsewhere carries no information.
Methodology version and revisions
The methodology version (v1.0) under which the record was produced, plus a revision history so a later correction is visible rather than silent.
Cryptographic proof status
Until ML-DSA signing is live on a node, records from that node show proof status "pending". No record should be treated as cryptographically verifiable before then; see Verify Evidence.