PNTMAP™

Validation status & roadmap

Published 2026-08-14 (methodology v1.0). A precise, verifiable statement of what PNTMAP™ has and has not been validated against, and the ordered roadmap to closing the gap. The roadmap is published as a commitment: each item is marked complete only when the corresponding evidence is published on this page.

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.

Current status

PNTMAP™ has not yet undergone controlled jamming/spoofing evaluation. Probability of detection, false-alarm rates, localisation error and time-to-detection are not yet characterised. The platform currently observes GNSS accuracy degradation statistics (NIC/NACp) from live ADS-B traffic; it does not claim calibrated detection performance. The roadmap below is published as a commitment.

This is consistent with the methodology page, which records controlled-test validation as pending and classifies all current observations as observational rather than validated. See Data Methodology v1.0 for the parameter-level description of what the platform measures and which parts are not yet implemented.

Validation roadmap

Ordered by cost and feasibility, lowest first. Items 1 and 2 require no transmission testing and are the immediate next steps; item 4 is an external dependency stated honestly.

  1. 1

    Labelled event baseline

    Cross-reference flagged windows against known ground truth: NOTAMs, published MoD jamming trials (e.g. Sennybridge/West Wales areas), and EUROCONTROL EVAIR reports. Provides a first probability-of-detection and false-alarm estimate without any transmission testing.

  2. 2

    Natural-degradation characterisation

    Quantify baseline NIC/NACp variation by altitude, traffic density and aircraft/avionics type from the platform's own accumulating dataset. Pure analysis of data already collected; addresses sensitivity to traffic density, altitude, avionics type and natural GNSS degradation.

  3. 3

    Confidence calibration and time-to-detection

    Definable once the labelled baseline (item 1) exists.

  4. 4

    Controlled testing

    Real jamming/spoofing emission requires Ofcom-licensed trials or partnership with an MoD/DSTL exercise. Stated honestly as an external dependency, not a self-serve step.

  5. 5

    Benchmark against academic literature

    Compare openly against published ADS-B GNSS-interference research (large labelled event sets, OpenSky-based studies) and cite the comparison.

Closing statement

We publish limitations and this roadmap for the same reason we publish cryptographic provenance: claims about this platform should be verifiable. Each roadmap item will be marked complete only when the corresponding evidence is published on this page.
Traffic
LOADING LIVE TRAFFIC…