Pricing Search Start free trial
// EVENT · VOLCANIC ASH CLOSED · 1 Sep FIR disruption entry closed — Central American FIR traffic ran 1.10× its own same-hours norm · La Aurora (GUA) inside none of the last 390 observed ash areas · Fuego still emitting, still tracked Data as of 1 Sep 2026, 12:55 UTC

Fuego Ash — 1 September Disruption Entry Closed, Ash SFC/FL140 Still Drifting West, Guatemala City Inside None of 390 Ash Areas, September 2026

← All airspace events

The volcano-category airspace-disruption entry our automated multi-signal analysis opened for the Central American FIR on 1 September is closed in our signals. Its traffic component stopped flagging after 10:15 UTC, and measured hour-for-hour the FIR ran 1.10 times its own same-hours average for 18–31 August across the 00:00–12:45 UTC stretch that triggered it — above the norm, not below. Fuego has not stopped: VAAC Washington issued three advisories on 1 September, the latest at 11:00 UTC reporting observed ash SFC/FL140 45 NM west of the summit, and Tegucigalpa's meteorological watch office has volcanic-ash SIGMET A2 running in the Central American FIR (MHCC) until 17:00 UTC (VAAC Washington and MHTG, public bulletins). La Aurora International (GUA), 40 km east-north-east of the vent, falls inside none of the 390 observed ash areas drawn over the last 90 days — the airport that does fall inside them is Retalhuleu (RER), 88 km west, on 21 of those 390, most recently on 1 September itself.
// Flying to Guatemala City or Central America this week? The short version
  • The 1 September disruption entry is closed: the Central American FIR's en-route traffic ran 1.10× its own same-hours average through the morning that triggered it, and the last closure-flagged reading was at 10:15 UTC. Guatemala City (GUA) observed traffic ended the window about 2% above its own August baseline.
  • Guatemala City (GUA) is 40 km from the vent and inside none of the 390 observed ash areas of the last 90 days. Flights are operating — check your airline on the day, because wind moves ash.
  • Closing this entry does not close the volcano. Fuego has produced at least one advisory on every day our record covers, 11 May through 1 September, at four to five a day, and it was still emitting at the 11:00 UTC bulletin. The August brief closed that month's episode the same way.
  • Ash is reported SFC/FL140 and drifting west. Guatemala City is east-north-east of the vent, which is why the exposure that does show up in the data belongs to Retalhuleu (RER), 88 km to the west — inside the observed ash areas on 21 advisories across 13 days, including the 11:00 UTC advisory on 1 September.

Advisory timeline — how active is this episode

Fuego is a persistent emitter, and the month boundary means nothing to it: VAAC Washington has issued 390 ash advisories over the last 90 days, and at least one on every single day our record covers — 11 May through 1 September. That is 114 consecutive days, and it is a floor rather than a start: 11 May is when our advisory collection begins, not when Fuego began emitting. The monthly volume has crept up rather than spiked — 125 advisories in June, 134 in July, 138 in August, four to five on almost every day — and September opened with three advisories by 11:00 UTC on the 1st (04:53, its 04:57 correction, and 11:00). The latest bulletin reports observed ash SFC/FL140 (surface to about 14,000 ft) 45 NM west of the summit, forecast to keep moving west to west-south-west. Daily advisory count, 15 August – 1 September:

4
15 Aug
5
16 Aug
5
17 Aug
5
18 Aug
5
19 Aug
4
20 Aug
4
21 Aug
5
22 Aug
4
23 Aug
4
24 Aug
4
25 Aug
4
26 Aug
5
27 Aug
4
28 Aug
5
29 Aug
4
30 Aug
4
31 Aug
3*
1 Sep

Fig. 1 — Fuego daily VAAC ash advisory count, VAAC Washington (public) · * partial day · Data as of 1 Sep 2026, 12:55 UTC · Source: VAAC Washington ash advisories (public).

Airports in the exposure zone

AirportSizeDistance from ventFIR
La Aurora International (GUA) large 40 km · outside all 390 observed ash areas (90 d) MHTG
Retalhuleu (RER) small 88 km · inside observed ash on 21 of 390; most recent 1 Sep MHTG
Tapachula International (TAP) medium 164 km · inside observed ash on 1 of 390 (11 Aug) MMFR
Ilopango International (ILS) small 209 km · outside all 390 observed ash areas (90 d) MHTG
El Salvador International (Monseñor Óscar Arnulfo Romero) (SAL) large 228 km · outside all 390 observed ash areas (90 d) MHTG

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: La Aurora closed the phase slightly above its own baseline

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. La Aurora International (Guatemala City)'s last 30 days:

Fig. 2 — Observed daily movements at GUA, 1 Aug – 30 Aug (latest complete UTC day). Data as of 1 Sep 2026, 12:55 UTC · Source: FlySafe monitoring (ADS-B receiver network).

  • Observed baseline at La Aurora (GUA), 1–30 August: ~381 movements/day across the 29 complete UTC days of that window — 29 August is excluded as a partial-collection day (see below).
  • Last six complete days (24–30 August, 29 August excluded): 388/day — about 2% above that baseline. The month high was 472 on Friday 28 August (+24%); Fridays are GUA's busiest day, with an August median of 482.
  • Latest complete day, Sunday 30 August: 331 movements. Against GUA's own Sunday median of 364 that is −9%, and our airport verdict reads it as an ordinary day. Against the all-days ~381 baseline the same number looks like −13% — the same-weekday comparison is the honest one for an airport whose Friday median (482) runs more than 40% above its Saturday median (341).
  • Three days are deliberately not in those averages. 29 August is a partial-collection day we had previously treated as complete: network-wide volume on our feed sits at 0.59× its recent median that day, against 0.89–1.05× on every other day of the fortnight, and GUA's own figure has been revised down at every pass — 306 → 283 → 278 → 259. 31 August is a near-total gap: 49 movements at GUA, network-wide volume 0.09× median. 1 September has not been aggregated into daily movements yet, so this phase's own traffic day does not exist at the time of writing. Both gap days remain on the chart as measured — they are undercount floors, not traffic collapses.
  • Honesty note: these are observed movements from a crowdsourced ADS-B receiver network — a floor, not the airport's official total, and recent days revise as data backfills.

The comparison that matters is regional, and it is the reason this close-out carries no recovery curve. Between 2–15 August and 24–30 August, on the same receiver feed and with the same partial days excluded, observed movements at GUA moved +2% (380 → 388) — while San José (SJO) moved −10%, Mexico City −11% and Cancún −16% over the same fortnight. The airport 40 km from an erupting volcano is the only one of that set that went up. Live view: GUA airport brief.

What it means for flights

Direction decides this one, not distance. Forty kilometres sounds close, and on its own it tells you almost nothing. What the advisories actually settle is where the ash goes. Across the 390 observed ash areas of the last 90 days, the reported drift was west on 251 of them, north-west on 69 and south-west on 58 — plus nine due-north readings in June and July, two due-south in June, and one advisory that carried no drift reading at all. Guatemala City sits at roughly 072° from the vent, east-north-east; not one of those advisories carried the cloud onto that bearing. Testing the published polygons directly gives the same answer from the other side: La Aurora falls inside none of the 390, while Retalhuleu — 88 km west, downwind — falls inside 21 of them across 13 separate days, the latest being the 11:00 UTC advisory on 1 September, and Tapachula once, on 11 August. The prevailing low-level flow here is easterly, so the ash goes west; that is a measured pattern in our record, not a guarantee about tomorrow, and a wind shift changes it.

FL140 is a low ceiling — that shapes who cares. Ash reported SFC/FL140 (surface to about 14,000 ft) sits well below the cruise levels of traffic crossing Central America, so overflights are largely unaffected. It matters in the terminal area and on regional routes: La Aurora's field elevation is 4,952 ft, so departures and arrivals work through part of that band on every rotation, and turboprop routes west of the capital sit inside it. That is the whole reason a volcano can generate 390 advisories in 90 days without a single cancelled long-haul — and why dispatchers read the reported flight level and the drift vector in each advisory, not the distance from the summit.

Two bulletins, two different jobs — and the SIGMET is the operational one. The VAAC advisory is the volcanological product: it says where ash is and where it is forecast to go. The SIGMET is the air-traffic product: the Tegucigalpa meteorological watch office (MHTG) issues volcanic-ash SIGMETs into the Central American FIR (MHCC), and that is what an en-route crew is told about. Both are running: 134 Fuego ash SIGMETs since 1 August — on every one of those 32 days, without exception — and the current one (A2) is valid 11:00–17:00 UTC on 1 September for ash SFC/FL140 moving west at 20 kt. Our SIGMET record begins 1 July, so the 258 Fuego ash SIGMETs it holds are a floor on the real count, not a total. Two independent bulletin streams describing the same low westward plume is exactly the corroboration our detection layer looks for before treating a hazard as an operational fact.

The overnight signal we did not call a closure — and how it resolved. Our automated multi-signal analysis opened a volcano-category airspace-disruption entry for the Central American FIR on 1 September. We published what it rested on rather than the label: its traffic component was a run of closure-flagged readings between 04:15 and 10:15 UTC — 22:15 to 04:15 local time — compared against an all-hours average. Over the previous fortnight this FIR averaged 0.5 to 3.4 aircraft per snapshot across the 04:00–09:00 UTC hours, against 17 to 18 in the 14:00–17:00 UTC peak, so a nightly reading always looks like a large drop against a 24-hour mean. The day resolved the way that reading predicted: the last closure-flagged reading came at 10:15 UTC (07:45 UTC for the adjacent MHTG airspace) and none followed, and by 12:45 UTC the Central American FIR was carrying 13 aircraft against a trailing average of 8.5 — 1.53× — with the neighbouring MHTG airspace at 1.69×. Compared hour-for-hour instead of against a 24-hour mean, the 00:00–12:45 UTC stretch on 1 September ran at 3.80 aircraft per snapshot against 3.46 for the same hours across 18–31 August — 1.10×. On the whole-day measurement, FIR-level en-route counts ran between 0.81 and 1.20 times their own trailing average on every complete day from 18 to 31 August. No avoidance signature appeared at any point. That is a FIR-level statement about whole-airspace counts, not about any individual flight, and it is not a statement that nothing was happening — it is a statement that our traffic data did not show it.

The comparison that keeps the traffic number honest. An airport 40 km from an erupting volcano moving a few per cent either way invites a causal story. The control group kills it. Comparing 2–15 August with 24–30 August on the same receiver feed, with the same partial-collection days excluded from both, GUA moved +2% (380 → 388 movements/day) while San José (SJO) moved −10%, Mexico City −11% and Cancún −16% over the same fortnight — the end of the northern summer travel season, visible across the whole region. Guatemala City, the one airport in that set with a volcano next door, is the only one that rose. We do not publish an observed-movement count for El Salvador (SAL) at all: our receiver coverage there is too thin to stand behind, so that cell stays blank rather than being filled with a number we would not cite ourselves.

What we watch for escalation. Three signals would reopen this page: an advisory-cadence inflection — the standing four to five a day becoming a sustained ten-plus; reported ash tops climbing well above the FL140–FL150 band the last week has held (the 90-day range is FL130–FL180, with FL180 last seen on 14 August); or an observed ash polygon reaching the La Aurora terminal area alongside a drop in our observed movements. Our detection layer checks all three every three hours, together with the SIGMET stream, the FIR-level en-route counts and the airport pulse, and this page, the GUA brief and the live ash map all update from the same cycle. Until one of those thresholds moves, the operating decision on any given day stays where it belongs — with the airport, the airline and the Guatemalan and Central American authorities.

What the data showed — 1 September entry closed. We close this entry on the signal that opened it: whether Central American airspace was actually carrying less traffic. It was not. The last closure-flagged reading was at 10:15 UTC; hour-for-hour the FIR ran 1.10× its own 18–31 August norm (3.80 aircraft per snapshot against 3.46) and stood at 1.53× its trailing average by 12:45 UTC, with both the Central American FIR and the adjacent MHTG airspace scored low for the day. At the airport, GUA never drew down: 388 observed movements/day across the six complete days of 24–30 August against a ~381/day August baseline (+2%), while San José, Mexico City and Cancún fell 10–16% on the same feed — which is why this close-out carries no recovery curve. On exposure, the headline held to the last advisory: La Aurora fell inside none of the 390 observed ash areas; Retalhuleu, 88 km west, fell inside 21 of them across 13 days, the most recent at 11:00 UTC on 1 September. Three honesty notes. Fuego is still emitting — three advisories on 1 September and SIGMET A2 valid to 17:00 UTC — so this closes the 1 September disruption entry and the near-field exposure question, not the eruption. Our movement counts are a floor from a crowdsourced receiver network, not official totals, and 29 and 31 August are partial-collection days excluded from every average above rather than read as traffic drops. And our advisory record starts 11 May, our SIGMET record 1 July, so every count here is a floor on the real total. Automated multi-signal analysis keeps Fuego under continuous watch, and this page reopens the moment the cadence, the reported flight levels, or the reach of the ash areas cross the thresholds above; the operating decision on any given day stays with the airport, the airline and the relevant authorities.

Passenger questions, answered from the data

Is Guatemala City airport affected by the Fuego volcano right now?

As of 1 September 2026, La Aurora International (GUA), 40 km east-north-east of the vent, falls inside none of the 390 observed ash areas VAAC Washington has drawn over the last 90 days, and no ash-related closure is in effect at the airport in our signals. Observed traffic closed the window slightly above its own baseline — 388 movements a day across the six complete days of 24–30 August against ~381. The latest advisory reports ash SFC/FL140 45 NM west of the summit, away from the city. Conditions can shift with wind — check your airline's status on the day of travel and the live ash map.

What was the 1 September airspace-disruption entry for the Central American FIR, and why is it closed?

Our automated multi-signal analysis opened a volcano-category entry for the Central American FIR (MHCC) on 1 September. Its traffic component compared overnight readings — 04:15 to 10:15 UTC, or 22:15 to 04:15 local — against an all-hours average, which always looks like a large drop in an airspace that carries 0.5–3.4 aircraft per snapshot at night against 17–18 at its afternoon peak. Measured hour-for-hour instead, the FIR ran 3.80 aircraft per snapshot over 00:00–12:45 UTC against 3.46 for the same hours across 18–31 August — 1.10 times its own norm. The last closure-flagged reading came at 10:15 UTC, nothing followed, and by 12:45 UTC the FIR was at 1.53 times its trailing average. The entry is closed on that evidence.

Did Fuego stop erupting when this brief closed?

No. This close-out ends the 1 September disruption entry and the near-field exposure question, not the eruption. Fuego has produced at least one VAAC ash advisory on every day our record covers — 11 May through 1 September — at four to five a day, with 125 advisories in June, 134 in July and 138 in August, and three on 1 September itself: 04:53, its 04:57 correction, and 11:00 UTC. The August brief carries that month's full record.

Does ash reported to FL140 affect flights over Guatemala?

FL140 is about 14,000 ft — below the cruise levels of traffic crossing Central America, so high overflights are largely unaffected. It matters in the terminal area and on regional routes: La Aurora's field sits at 4,952 ft, so departures and arrivals work through part of that band, and turboprop routes west of the capital sit inside it. Dispatchers file around the advisory areas and the SIGMET zones; regulators close airspace if ash reaches it.

Why does Fuego produce so many ash advisories?

It is a persistent emitter: near-continuous low-intensity ash emission rather than discrete eruptions. VAAC Washington re-issues advisories roughly every six hours while emission continues — 390 over the last 90 days, with at least one on every day of that window — and Tegucigalpa's watch office issues the matching SIGMETs into the Central American FIR, 134 of them since 1 August.

Is it safe to fly to Guatemala with the volcano active?

Aircraft do not fly through reported ash — dispatchers file around the advisory and SIGMET areas, and regulators close airspace if ash reaches it. We publish the measured picture: advisory cadence, reported flight levels, drift directions, which airports fall inside the published ash polygons, observed airport movements and FIR-level en-route counts. Routing and go/no-go decisions belong to operators and the relevant authorities, not to us.

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.

// Copy-paste quote

“The volcano-category airspace-disruption entry opened for the Central American FIR on 1 September 2026 is closed: measured hour-for-hour the airspace carried 3.80 aircraft per snapshot over 00:00–12:45 UTC against 3.46 for the same hours across 18–31 August — 1.10 times its own norm — and La Aurora International in Guatemala City, 40 km east-north-east of Fuego, fell inside none of the 390 observed ash areas of the last 90 days while averaging 388 observed movements a day over the six complete days of 24–30 August against a ~381-a-day August baseline; Fuego itself is still emitting, with three advisories issued on 1 September, according to flight-monitoring service FlySafe.zone.”

Chart: observed traffic at GUA
PNG · 1600px · attribution baked in
Observed daily movements at GUA — light version preview
Chart: advisory cadence
PNG · 1600px · attribution baked in
Fuego daily VAAC ash advisory count, VAAC Washington (public) — light version preview
↓ Data behind the charts — CSV CC BY 4.0 · dates + daily values, ready for your own chart
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.

No newsletters — we only reply to this request. Press page
// Cite this
"FlySafe.zone — Fuego Ash — 1 September Disruption Entry Closed, Ash SFC/FL140 Still Drifting West, Guatemala City Inside None of 390 Ash Areas, September 2026", https://flysafe.zone/events/fuego-ash-2026-09/, data as of 1 Sep 2026, 12:55 UTC — free to cite with a link. Observed-traffic figures are FlySafe’s own ADS-B-derived counts (floor, not total). Advisory cadence, reported flight levels, drift directions and observed ash-area geometry attributed to VAAC Washington (public advisories); volcanic-ash SIGMETs to the Tegucigalpa meteorological watch office (MHTG) for the Central American FIR (MHCC). Per-airport exposure counts are derived by FlySafe from the published advisory polygons; airport movement counts and FIR-level en-route ratios come from a crowdsourced ADS-B receiver network and are reported as a floor, not an official total. Method: /methodology/ · Press: /press/.

Related coverage