Popocatépetl Ash — Ash to FL200 and Mexico City 66 km Away, August 2026
- Mexico City (MEX) is 66 km from the vent and outside the ash areas in current advisories — observed traffic held near normal through the episode; check your airline on the day, as wind can shift ash.
- Popocatépetl is a persistent emitter: 141 advisories on 43 days in 90 days, in pulses — the latest ran 6–8 August, then six quiet days, one new advisory 15 August.
- Ash is reported to FL200 (~20,000 ft) — higher than many persistent emitters, and relevant to climb-out and descent at high-elevation Mexican airports, which is what dispatchers re-plan around.
Advisory timeline — how active is this episode
Popocatépetl is a persistent emitter, not an eruption-headline event: VAAC Washington has issued 141 ash advisories on 43 separate days over the last 90 days, in irregular pulses rather than a steady stream. Ash in the current advisories is reported to FL200 (about 20,000 ft). The August pulse ran 2–8 August (2–5 advisories/day), then went quiet for six days (9–14 August) — the gap that closed this episode in our signals — before three fresh advisories on 15 August reopened the emitter's next pulse. Daily advisory count through the August window (zero = no advisory issued that day):
Fig. 1 — Popocatépetl daily VAAC advisory count, VAAC Washington (public) · Data as of 15 Aug 2026, 18:45 UTC · Source: VAAC Washington advisories (public).
Airports in the exposure zone
| Airport | Size | Distance from vent | FIR |
|---|---|---|---|
| Hermanos Serdán (Puebla) (PBC) | medium | 30 km · outside reported ash areas | MMFR |
| Mexico City Benito Juárez (MEX) | large | 66 km · outside reported ash areas | MMFR |
| Felipe Ángeles Intl (NLU) | large | 90 km · outside reported ash areas | MMFR |
| Adolfo López Mateos (Toluca) (TLC) | medium | 105 km · outside reported ash areas | MMFR |
Distance alone does not determine impact — wind direction and the flight levels the ash reaches decide which airports and routes are affected on a given day. FIR = Flight Information Region.
What our monitoring shows: Mexico City kept running through the episode
FlySafe tracks observed departures and arrivals at 493 airports from crowdsourced ADS-B receiver data. Observed counts are a floor, not a total — receiver coverage varies — but an airport measured against its own baseline is a reliable shape. Mexico City Benito Juárez's last 30 days:
Fig. 2 — Observed daily movements at MEX, 15 Jul – 13 Aug (latest complete UTC day). Data as of 15 Aug 2026, 18:45 UTC · Source: FlySafe monitoring (ADS-B receiver network).
- 30-day baseline at Mexico City (MEX): ~896 observed movements/day.
- Through the 6–8 August advisory pulse, daily traffic stayed inside the normal band (833–915) — no collapse, no cancellation wave.
- Last complete day (13 Aug): 860 movements, about −4% versus baseline — within ordinary day-to-day variation; the 7-day average is ~881 (about −2%).
- Honesty note: these are observed movements from a crowdsourced ADS-B network — a floor, not the airport's official total — and we report them as such. The first day of the window and 12 Aug (262) are flagged by our receiver network as partial-coverage days — treated as data gaps, not real dips, and excluded from the average.
The shape is the tell: a persistent emitter 66 km from one of the region's busiest hubs, with ash areas that have not reached the metro, produces no operational signature at the airport — the opposite of a typhoon's collapse-and-snap-back. Live view: MEX airport brief.
What it means for flights
A persistent emitter is a planning problem, not a crisis. Eruption-spike volcanoes disrupt in bursts; persistent emitters like Popocatépetl redraw the ash map a little, in pulses, for months — 141 advisories on 43 days over the last 90. The operational response is routine: dispatchers file around the advisory polygons on flight plans touching the Mexico FIR (MMEX). The risk profile changes only if the cadence or the reported flight levels change — which is exactly what this page tracks.
Why FL200 is worth more attention than a lower ceiling. Ash reported to FL200 (~20,000 ft) sits above typical persistent-emitter ceilings. It stays below high-altitude overflight cruise, so aircraft crossing central Mexico high are largely unaffected — but Mexico City's field sits at ~7,300 ft, so departures and arrivals climb and descend through the FL200 band in the terminal area. That is why the reported flight level, not just the distance, is the number regional operators watch.
66 km matters — and it is not a verdict. Benito Juárez sits west of the vent; the ash areas drawn in current VAAC advisories have not extended to it, and observed traffic held near baseline through the pulse. That is a measured fact about today's advisories and today's movements, not a safety guarantee: wind shifts move ash, and go/no-go decisions belong to operators and authorities. What the distance buys the metro is time and options.
What we watch for escalation. Three signals would change this story: an advisory-cadence inflection (the 2–5/day pulses becoming a sustained 10+/day), reported ash tops climbing well above FL200, or ash polygons reaching the MEX/PBC terminal areas. Our detection layer checks all three every three hours; this page and the MEX brief update from the same cycle.
What the data showed — episode closed 15 Aug. This episode is now closed in our signals: after the 2–8 August advisory pulse, VAAC Washington issued nothing for six days (9–14 August), and automated multi-signal monitoring registered no airspace-disruption event in the Mexico FIR (MMEX) across the window. The operational number is the story: Mexico City (MEX) held a 7-day average of about 881 observed movements/day against its ~896 baseline (roughly −2%), and no complete day fell outside its normal band once partial-coverage days are excluded — no cancellation wave, and nothing to recover from. A persistent emitter 66 km away, with ash areas that never reached the metro, left no operational signature at the airport. Three fresh advisories on 15 August opened the emitter's next pulse; Popocatépetl stays under continuous monitoring, and this page will reopen if the cadence, reported flight levels, or ash reach cross the thresholds above.
Passenger questions, answered from the data
As of 15 August 2026, the ash areas in current VAAC advisories do not reach Mexico City's Benito Juárez (MEX), 66 km west of the vent, and observed traffic held near its ~896-movement daily baseline through the August pulse — no ash-related closure was in effect. Conditions can shift with wind; check your airline's status on the day of travel.
It is a persistent emitter: recurring low-to-moderate ash emission rather than one discrete eruption. VAAC Washington issues fresh advisories whenever an ash plume is detected — 141 advisories on 43 separate days over the last 90, in pulses, with quiet gaps in between (for example 9–14 August).
Aircraft do not fly through reported ash — dispatchers file around the advisory areas, and regulators close airspace if ash reaches it. We publish the measured picture (advisory cadence, reported flight levels to FL200, distances, and observed traffic that held near baseline); routing and go/no-go decisions belong to operators and authorities.
For media — the full kit
Everything on this page — charts, CSV, quotes — is published under CC BY 4.0: free to reuse with attribution to FlySafe.zone. Charts come in dark (social/web) and light (print/light layouts) versions; attribution and license are embedded in every file.
“Popocatépetl has generated 141 volcanic-ash advisories on 43 separate days over 90 days with ash reported to FL200, while the ash areas in current advisories do not reach Mexico City's Benito Juárez airport 66 km away, where observed traffic held near its normal daily baseline through the episode, according to flight-monitoring service FlySafe.zone.”
Boilerplate — about the source (for your article footer)
FlySafe.zone monitors airspace risk and observed airport activity worldwide: 334 flight-information regions scored daily, GPS-interference signals, volcanic-ash exposure and daily observed movements at 493 airports from the crowdsourced ADS-B receiver network. Methodology: flysafe.zone/methodology.
Need a different cut of the data, a comment, or numbers for another airport? Leave an email — we answer fast during active events.

