Skip to content

Methodology

Manzlytics collects the integrity values in the ADS-B position messages that aircraft broadcast themselves, evaluates them with a calculation method we developed, and presents the result on the map as an indicator. This page describes the method in outline; the detailed calculation rules, thresholds and parameters belong to Manzlytics and are not disclosed.

Methodology version 1.6.0 · Last updated: 17 October 2026

In short

  • Source: ADS-B position messages from the adsb.lol community network; only what the aircraft broadcast itself (ODbL).
  • Method: integrity values are gathered in regional cells and run through a series of calculations and statistical comparisons; the result is an indicator and a suggestion.
  • Observation sufficiency: every result is labelled separately by how much data it rests on; an uncoloured hatched area means “no data”, not “clean”.
  • No binding effect: everything presented is for information only, with no binding effect and no warranty; all rights reserved.

Open the sections for details.

Data source

Position messages come from the adsb.lol community network (ODbL licence). Receivers set up by volunteers collect the ADS-B messages aircraft broadcast on 1090 MHz.

Only ADS-B positions broadcast by the aircraft itself are used. Positions computed by ground stations and aircraft on the ground are excluded.

Calculation approach

The position integrity (NIC) values aircraft report are gathered in hexagonal cells over the airspace. For each cell the number and share of affected aircraft is calculated and compared with the usual level seen in clean areas; the result is shown as a low, medium or high level.

The details of the calculation (thresholds, parameters, filters and statistical test rules) are trade secrets and are not published. The method may change over time; the version number is stated on this page.

Observation sufficiency and coverage

The level answers “how affected is it”; observation sufficiency answers “how far can we trust this number”. The two are shown separately. Seeing no affected aircraft in a cell with few aircraft does not mean “clean”; there is simply not enough data.

Uncoloured, hatched areas have no observations at all. This does not mean there is no interference there; it only shows that no receiver collects data from that region. Coverage is currently very weak over central and eastern Anatolia, the eastern Black Sea, Iraq and Iran.

Limitations

A NIC drop is not always deliberate interference: a receiver fault, a software bug or satellite geometry can give a similar result. A drop on a single aircraft is not evidence by itself.

Many aircraft reporting the same drop in one area is not independent evidence either: shared causes (aircraft avionics, the receiver network, traffic mix) can produce the same result. The data rests on a single receiver network; if its distribution changes, the patterns can change too.

Position anomalies appear as a separate layer on the map and in the event catalogue. It is rule-based, experimental and not independently validated; it shows unusual position behaviour and does not prove physical spoofing.

This view rests only on the integrity value the aircraft reports, so some situations do not show up on the map. Counts from different products are not directly comparable.

Manzlytics reports observed data, does not state a cause and is not an operational navigation source.

No binding effect and rights

The maps, events, reports and suggestions presented are for information only; they have no binding effect and no warranty and cannot be used as a basis for decisions. All rights are reserved, including the calculation method, software, text and design.