Aviation Conflict-Event Tempo, July 2026: The Reversion Reverted

Iran's aviation conflict-event tempo did not stay reverted. In AeroVigil's pipeline, Iran's share of all aviation-tagged conflict events fell to roughly 5% by early July — and then climbed straight back up, reaching 11.2% in the week of 6 July and 14.4% in the week of 13 July. That second peak is higher than the 13.5% June spike it was supposed to have replaced. Last month the story was a spike that reverted; this month it is a reversion that reverted.

Data window: 1 June – 19 July 2026 (seven complete Monday-start weeks). Sources: AeroVigil's intelligence pipeline (normalized intelligence items and their threat-signal classifications) and GDELT aviation-tagged conflict events ingested into the same pipeline. Because the pipeline's total ingest volume grew across the window, every cross-week comparison below uses a share or ratio metric, never a raw count presented as a world trend. See the methodology footer.

How did last month's forecasts hold up?

This is the third issue of AeroVigil's monthly trend-and-forecast series, so it opens by grading the July issue's three forecasts against the data that has since arrived. The scorecard is humbling, and that is the point: published forecasts are only worth anything if they are graded honestly.

Forecast 1 — "The tempo–footprint decoupling persists" (likely). Status: hit, holding. The July issue predicted the contested-airspace classification share would stay at or above 2.5% of weekly classified items through the week of 2 August. It has not come close to that floor. Contested-airspace classifications ran at 68% of classified items in the week of 29 June, then 55% and 34% in the two July weeks — an order of magnitude above the disconfirmation line. The forecast is a clear hit.

Forecast 2 — "Ukraine holds the top single-theatre tempo share" (even chance). Status: tracking to miss. The forecast expected Ukraine to outrank Iran on event tempo in a majority of July's complete weeks. It has done the opposite. In both complete July weeks so far, Iran led decisively: 11.2% versus 5.5% in the week of 6 July, and 14.4% versus 4.8% in the week of 13 July. The forecast is disconfirmed if Iran outranks Ukraine in three or more complete July weeks; it is at two of two and trending the wrong way.

Forecast 3 — "Iran does not re-test its June peak in July" (highly likely). Status: missed. This was the confident call, and it was wrong. The forecast said Iran's weekly event-tempo share would not return to its 13.5% June peak in any complete July week, and would be disconfirmed by any week at or above 13.5%. The week of 13 July printed 14.4%. The forecast is falsified. The lesson is written into this issue's analysis: a single mean-reversion is not evidence that a driver has gone away.

What did Iran's conflict-event tempo actually do?

It formed a double peak. Iran's share of weekly aviation-tagged conflict events sat at 6.8% in the week of 1 June, spiked to 13.5% in the week of 8 June, reverted through 5.9%, 5.0% and 5.1% over the following three weeks, then re-escalated to 11.2% and 14.4%. The July peak exceeds the June one.

Share is the honest metric here. AeroVigil's total ingest volume grew across the window, so a raw event count would mostly measure the pipeline, not the world. Iran's share of all aviation conflict events is robust to that growth: if the whole pipeline doubles and Iran doubles with it, the share is flat. It did not stay flat. The re-escalation is a real change in Iran's proportional weight in the aviation-conflict signal, not an artefact of a bigger pipeline.

Did the theatre rotation reverse?

Yes. The July issue documented Ukraine edging past Iran on event tempo in the week of 29 June — Ukraine 5.4% to Iran 5.1%. That crossover did not hold. As Iran re-escalated, its share pulled far ahead of every other theatre, while Ukraine stayed in its steady 5% band and Israel kept fading, from 5.4% in the week of 8 June to about 1.6% by mid-July.

The rotation reading from last month was not wrong about Ukraine — Ukraine remains the steady background theatre whose share never spikes and never collapses. It was wrong to treat one week's crossover as a durable handover. Iran re-took the top single-theatre tempo share within two weeks. A one-week ranking is a data point, not a trend.

Why did the footprint not follow the tempo up?

Because operational classification lags reporting — and this month the lag ran the other way. In June, the event tempo spiked first and the contested-airspace footprint compounded behind it. In July, the tempo re-escalated but the operational footprint did not re-spike with it. Indexed to the week of 29 June, Iran's event-tempo share rose to 218 and then 279, while the contested-airspace classification share fell to 81 and then 51.

This is the mirror image of last month's chart, and it carries the same warning. In June the lesson was that a falling tempo does not mean the operational risk has eased. In July the lesson is the converse: a rising event tempo does not automatically mean the operational footprint has widened. Correlation is not causation, and the two signals are not interchangeable. Reporting intensity and operational avoidance move on different clocks, and reading one off the other — in either direction — is the mistake.

For flight operations, that gap is the whole argument for tracking the two signals separately. The tempo tells you where the reporting is; the classification footprint tells you where the operational posture actually sits. On any given week they can point in opposite directions.

What does this mean for the threat picture and the technology to track it?

The threat vector is conflict-zone overflight risk: airspace where military activity, air-defence posture, or GNSS jamming and spoofing can degrade the safety of an overflight even when no single incident dominates the news. The June–July arc shows why event-driven monitoring alone is insufficient. Event tempo told you Iran was the story on 8 June, told you it was over by 22 June, and told you it was back — bigger — by 13 July. A go/no-go process wired to that signal alone would have whipsawed three times in six weeks.

The mitigation is continuous, FIR-level classification rather than incident alerting. AeroVigil's pipeline attaches a disposition to each intelligence item and tracks the contested-airspace footprint independently of the reporting cycle, which is what let this analysis see the tempo re-escalate while the footprint eased. That durable disposition is the input a pre-flight risk assessment workflow turns into a decision, converting a volatile event-tempo series into a trackable airspace posture instead of a string of one-day alerts. The mechanics of that posture — prohibited versus restricted airspace, the role of NOTAMs, and why a single open-source report is not an alert — are covered in our guide to conflict-zone and overflight risk and in the glossary.

Crucially, the current status of any specific airspace is volatile and is not frozen in this article. For the live disposition — whether overflight is advisable today, and at what flight levels — consult the continuously updated flight-risk feeds rather than any figure here.

Forecasts

These assessments use a fixed probability yardstick, defined once in the methodology footer. Each is falsifiable, with the disconfirming observation and a deadline stated.

Forecast 1 — The Iran tempo re-escalation does not immediately re-revert (likely). Iran's weekly aviation event-tempo share will stay at or above 8% in a majority of the complete weeks of the window 20 July – 16 August 2026, rather than snapping straight back to its ~5% late-June floor. Disconfirmed if Iran's share prints below 8% in a majority of those complete weeks.

Forecast 2 — The tempo–footprint gap narrows (even chance). The contested-airspace classification footprint will begin catching up to the re-escalated tempo: the contested-airspace share of weekly classified items will rise above its 34% week-of-13-July reading in at least two complete weeks before 16 August 2026. Disconfirmed if the contested-airspace share stays at or below 34% in every complete week through 16 August.

Forecast 3 — Iran holds the top single-theatre tempo share (highly likely). Iran will remain the highest-share single theatre for aviation conflict events, ahead of Ukraine and Israel, in a majority of the complete weeks through 16 August 2026. Disconfirmed if any other single theatre outranks Iran in a majority of those weeks. Live ground-truth status remains at the flight-risk feeds.

Frequently asked questions

Does a second, higher tempo peak mean the airspace is more dangerous than in June?

Not necessarily. Event tempo is a reporting-intensity signal, not an airspace ruling. In July, Iran's tempo re-escalated while the operational avoidance footprint eased. The safety question depends on NOTAMs, flight-level restrictions and current avoidance practice — consult the live flight-risk feeds.

Why does AeroVigil publish a scorecard of its own past forecasts?

Because an ungraded forecast is marketing, not analysis. This issue's July call that Iran would not re-test its June peak was wrong, and saying so plainly is what makes the next forecast worth reading. Calibration only improves when misses are counted.

What is the difference between event tempo and the contested-airspace footprint?

Event tempo is the rate of conflict-related reporting tied to an airspace. The contested-airspace footprint is the slower-moving operational response — restrictions, reroutes, and the analyst classifications that track them. In June the footprint outran the tempo; in July the tempo outran the footprint. They move on different clocks.

Is this an event-driven brief about a specific incident?

No. This is a trend analysis of how conflict-event tempo and airspace classifications moved across a defined window, with falsifiable forecasts. AeroVigil publishes same-week event briefs separately.

Methodology

This article draws only on AeroVigil's own intelligence pipeline and the open-data GDELT aviation event stream ingested into it. No third-party proprietary feeds are republished.

Window and pipeline-growth control. The data window is 1 June – 19 July 2026 (seven complete Monday-start weeks). Because the pipeline's total ingest volume rose across the window, every cross-week comparison uses a share or ratio metric, or is indexed to a fixed base week — never a raw count presented as a world trend. Event-tempo series are pinned to a single fixed source (GDELT aviation-tagged events) ingested across the whole window; classification-footprint series are expressed as a share of weekly classified items.

Probability yardstick. Highly likely ≥ 80%; likely 60–80%; even chance ~50%; unlikely 20–40%; highly unlikely ≤ 20%.

Source grading. AeroVigil grades sources on a five-tier reliability model; a single open-source report is treated as a lead, not a confirmed alert. See our methodology for the full approach to source reliability, analyst-in-the-loop verification, and classification.

_Last reviewed: 20 July 2026._