How AeroDue Radar monitors upcoming disruptions

What must be true before an event is published

1. The notice comes from a publication-eligible source in the registry below, and its link is an HTTPS URL on that source's own domain. News reports can help discovery but never publish an event on their own: publication requires official primary evidence.
2. The notice has a parseable start date, an end date that is not earlier than the start, at least one country and a current verification in the latest collection.
3. Notices without a complete, confirmed date window are published as advisories and are never given invented dates.
4. Only English event pages that also pass stricter rules are offered for search indexing: official primary evidence, a named schedule, airport or airline, a descriptive title, aviation relevance and a forward or recent time window. Every other event page stays available with noindex.

Evidence boundaries published with every dataset

• Calendar events require an explicit future or active date window. Notices without a complete confirmed window are published separately as advisories, never assigned invented dates.
• Confirmed means listed by the named source; it does not guarantee that a planned strike will happen.
• A calendar date marker is not a claim that disruption lasts all day. Refer to schedule_text and the official source for exact local hours.
• Zero events means no qualifying notice in the monitored sources, not proof that travel will be disruption-free.
• A failed source is shown as unavailable; last-known events may be retained for at most 48 hours with their original verification timestamp.
• Advisories retain the original report and verification dates during source failures. Older or no-longer-reconfirmed notices remain accessible in the advisory archive, not as confirmed current disruptions.
• The rolling 30-day view is a calendar filter, not an expiry rule for active events. Undated advisories remain visible independently of that filter; RSS includes events and additional notices, CSV/iCalendar contain dated events, and JSON also contains the advisory archive.
• No flight counts, passenger counts, operational impact ratings or passenger-specific legal outcomes are inferred.

What the statuses mean

Confirmed / Announced

As listed by the named source. Confirmed does not guarantee that a planned strike will happen.

Active

The published date window has started and has not ended.

Archived reference

The published window has ended. This does not prove that operations recovered.

Needs review

Not reconfirmed in the latest collection. The last-known record can remain for at most 48 hours with its original verification time and is never shown as newly confirmed.

Planned action cancelled · Planned action suspended · Scheduled notice withdrawn · Planned action reinstated · Sources disagree

A later official notice reported this change. The original notice and the change are both kept and both linked.

Monitored collectors

Each collector reads one official page or feed. Empty means the page was read and no qualifying notice was extracted; that is not proof that nothing is happening. Snapshot shown: 23 Oct 2026, 05:09 UTC.

Coverage and known gaps by market

100 * (healthy configured categories + categories with >=2 independent healthy organizations) / (2 * 8). Empty parser results are not proof of absence. This is configured capability coverage, not national event recall.

Publication lead time

Published events whose canonical page was first verified at least 24 hours: 43 · 3 days: 40 · 7 days: 34 · 14 days: 21 · 30 days: 15 before the event start. Measured from first successful HTTP verification of the canonical page; search indexation remains unverified.

Collectors failing in the latest run

transpennine-express, american-airlines-alerts

No compensation decisions, guaranteed indexing, measured search volumes or full national coverage. Resolved indicates an elapsed published schedule, not proof of operational recovery. Failed jobs are observed by the GitHub watchdog, not inferred from successful collection history. Automatic discovery/miss rates require an external benchmark.

Benchmark and misses

Independent trackers and reports are kept as a small benchmark. They are never publication sources; they only test whether the Radar noticed an event that others surfaced. Recall is reported only when at least one case is inside its evaluation window.

Measured recall: not measurable at this snapshot (no case inside its evaluation window) · eligible 0 · detected 0 · missed 0 · evaluated against the build snapshot of 23 Oct 2026, 05:09 UTC.

Publication-eligible source identities

Official operator: 15 · Official airport: 13 · Official union notice: 12 · Official authority: 9 · Official air-traffic control: 4 · Reputable news (never sufficient alone): 1.

Change history and corrections

• Every event keeps an append-only history: first detection, first publication and every material or status change. Earlier states are not deleted or rewritten.
• Each event has a stable AeroDue ID. The same id is the id in the JSON feeds, the prefix of the RSS item guid (<id>:<revision>) and the iCalendar UID (<id>@aerodue.com). It is shown on every event page next to the first-detection time.
• Each event's publisher briefing page lists the full change history, the evidence class, the source ids and the original source links.
• To report a factual error, email contact@aerodue.com with the AeroDue ID and the official source that shows the correct information. Any change to a published record, including a correction, is added as a new entry in its change history.

Citing and reusing the data

Attribution format: AeroDue Disruption Intelligence — [event title]. [canonical event URL]. Always link to the canonical event page.

AeroDue quotes the source headline and schedule text and links to the original notice; official notices remain subject to their publishers' terms. No open licence for bulk redistribution of the AeroDue compilation has been published yet — for reuse beyond citation and the published embeds, contact contact@aerodue.com.

Machine-readable feeds

• All markets: JSON · RSS · CSV · iCalendar
• Australia: JSON · RSS · CSV · iCalendar
• Germany: JSON · RSS · CSV · iCalendar
• Spain: JSON · RSS · CSV · iCalendar
• France: JSON · RSS · CSV · iCalendar
• United Kingdom: JSON · RSS · CSV · iCalendar
• Italy: JSON · RSS · CSV · iCalendar
• Netherlands: JSON · RSS · CSV · iCalendar
• United States: JSON · RSS · CSV · iCalendar
• Publisher briefings with history fields: briefings.json · Collector health: radar-health.json · Media and data room