Monterrey (MTY) Traffic Drop — a −97% Anomaly the Evidence Says Is Lost Receiver Coverage, Not a Shutdown, August 2026
- Closed. Between 15 and 21 August, flight-tracking data (ours included) showed almost no traffic at Monterrey — our cross-checks indicate the crowdsourced ADS-B receiver coverage in the area failed, not the airport. Coverage came back on 22 August and has held for sixteen days, so we are closing the anomaly as a measurement failure.
- No disruption signal corroborates a shutdown: MTY's weather station reports hourly as normal (clear sky, no adverse weather), no closure NOTAM appears in our feed, and a second Monterrey-area airport (Del Norte) lost its observed traffic in lockstep — the fingerprint of receiver-coverage loss around Monterrey, not of an airport shutting down. The country's busiest airports (Mexico City, Cancún) stayed visible throughout, so this looks localised to the Monterrey area, not national. Coverage around Monterrey returned from 22 August, and observed counts are back near their ~400/day baseline.
- For 15–21 August we cannot measure MTY's real traffic — that window is a hole in our data, not a record of what flew, and closing this page does not fill it. Low-altitude coverage came back on 22 August and observed counts have run near baseline since (346/day over the seven most recent fully-landed days vs ~400/day before); the freshest one or two days still land short and fill in later. For the status of a specific flight, check your airline; observed counts here are a floor, not a total.
Advisory timeline — how active is this episode
This first chart is deliberately not a traffic chart — it is a receiver-reach chart, and it is the heart of this page. It counts every ADS-B position report our crowdsourced receiver network heard below 3,000 m (~10,000 ft) inside the Monterrey area — the altitude band where arrivals, departures and pattern traffic live. Through 14 August the network heard 280–340 low-altitude reports a day. On 15 August that fell to 217; on 16 August it fell to zero, and 17–21 August produced just 4, 9, 7, 2 and 6 — while aircraft crossing the same box at cruise altitude remained visible throughout. Then across 22 August–6 September the low-altitude count recovered to 161, 237, 216, 265, 285, 297, 386, 310, 271, 275, 291, 362, 312, 288, 241 and 250 — sixteen straight days with coverage, no day below 161, and the last seven of them (31 Aug–6 Sep) average 288 a day against a 319/day pre-outage mean (8–14 Aug), or 90% of it. That is what closes this page: the receiver coverage came back and has held. Low-altitude signals are the first thing lost when local receivers go offline, because only nearby antennas can hear them — and the first to reappear when they come back:
Fig. 1 — ADS-B position reports below 3,000 m received within the Monterrey area (25.0–26.5° N, 99–101° W), per UTC day · Data as of 7 Sep 2026, 15:46 UTC · Source: FlySafe monitoring (crowdsourced ADS-B receiver network).
Airports in the exposure zone
| Airport | Size | Observed signal | FIR |
|---|---|---|---|
| Monterrey International (MTY) | large | — · observed count 443 → 12, 14–16 Aug | MMFR |
| Veracruz (Gen. Heriberto Jara Intl) (VER) | medium | — · parallel decline 59 → 7, 14–16 Aug | 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: the observed count collapsed — which is not the same as traffic collapsing
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. Monterrey International's last 30 days:
Fig. 2 — Observed daily movements at MTY, 20 Jul – 5 Sept (latest complete UTC day). Data as of 7 Sep 2026, 15:46 UTC · Source: FlySafe monitoring (ADS-B receiver network).
- Baseline: ~400 observed movements/day (mean, 20 Jul–14 Aug), peaking at 443 on 14 August.
- 15 Aug: 285 (−29% vs baseline) — the decline begins mid-feed, not at a clean day boundary.
- 16 Aug: 12 observed movements (−97% vs the preceding 7-day average of 399) — and the composition is the tell: all 12 were arrivals; zero departures, scattered across the day. A real schedule collapse does not look like this; a distant receiver catching a few descending aircraft does.
- 17 Aug: 15 · 18 Aug: 7 · 19 Aug: 23 · 20 Aug: 9 · 21 Aug: 18 — arrival-dominated throughout, the fingerprint of edge-of-coverage detection.
- 22 Aug: 235 observed movements (130 departures, 105 arrivals) — a balanced, roughly half-baseline day, and the first since 15 Aug with departures showing at all: the coverage is returning. 23 Aug: 338 (195 dep, 143 arr), 24 Aug: 367 (205 dep, 162 arr), 25 Aug: 374 (217 dep, 157 arr), 26 Aug: 306 (156 dep, 150 arr), 27 Aug: 381 (218 dep, 163 arr), 28 Aug: 419 (242 dep, 177 arr), 29 Aug: 364 (207 dep, 157 arr), 30 Aug: 354 (203 dep, 151 arr), 31 Aug: 368 (213 dep, 155 arr), 1 Sep: 370 (218 dep, 152 arr), 2 Sep: 368 (210 dep, 158 arr), 3 Sep: 287 (167 dep, 120 arr) and 5 Sep: 314 (184 dep, 130 arr) — balanced throughout, and the seven most recent days that have fully landed (29 Aug–5 Sep, excluding 4 Sep) average 346 movements a day, 87% of the ~400 baseline. 3 and 5 September are the softest of them, and on the evidence they are genuinely quieter days rather than ingest holes: the second ADS-B aggregate we cross-check recorded 278 and 297 movements at MTY on those days — within one and within 17 of our own counts — and our global rollup landed a normal ~247k and ~228k movements. One day inside the stretch is an ingest artefact rather than signal: 4 Sep reads 182 (96 dep, 86 arr) on a day when our whole movement rollup landed ~121k movements against a ~245k median for the surrounding fortnight (Mexico City 401 vs its usual ~820, Cancún 269 vs ~355) — a shortfall on our side, not Monterrey's, and that same second aggregate recorded 362 movements at MTY. The chart plots 4 September at its measured 182 but that bar is under-landed rather than a Monterrey signal, and the series ends on 5 September, the latest complete UTC day (6 September is still ingesting: 56 movements, all departures, against an ~18k global rollup, far below the norm).
- Known revisions: late-arriving receiver data keeps revising recent days, in both directions — 15 Aug was ingested at 220 and now stands at 285; 16 Aug was ingested at 12, was revised down to 3 on 19 August, and stands at 12 again after further late data; 21 Aug climbed from 1 to 18, 22 Aug from 228 to 235, 23 Aug from 53 to 338, and 25 Aug from 58 to 374 (315 of that day's movements arrived in a single later ingest). Since the last update, 2 Sep — the day this page flagged as under-landed at 226, and had been restated down to get there — has filled back in to 368 (210 dep, 158 arr), with the global rollup for that day recovering from ~156k to ~250k movements and Mexico City from 572 to 849; 3 Sep also firmed slightly, 279 → 287. That is the fourth flagged gap day running, after 29 and 30 August and 1 September, to heal on its own — every day this page has marked as under-landed has subsequently filled in, and none has turned out to be a Monterrey signal. The shortfall has again moved one day later, to 4 September, which we mark rather than delete on exactly that record. The pattern held across six updates — the freshest one or two days land short and fill in later. The chart shows the current measured counts; the anomaly first fired at −96% on the as-ingested figure of 12.
Observed counts are a floor, not a total, and they are only meaningful while receiver coverage holds. This page exists precisely because on 15–16 August that assumption broke for the Monterrey area — the cross-checks below are how we know. Live view: MTY airport brief.
What it means for flights
What fired, and why we publish it anyway. Our detection layer flagged MTY when the 16 August observed count came in at 12 movements against a rolling 7-day average of 335 — a −96% traffic anomaly at Mexico's third-busiest airport. (Reprocessing of late receiver data on 19 August briefly revised that day's count down to 3; further late data has since restored it to 12 — the figure the chart now shows, a −97% anomaly against the preceding 7-day average.) Automated multi-signal analysis then did what it always does: checked the anomaly against every other layer we track — closure NOTAMs, SIGMETs, volcanic-ash exposure, GNSS interference. Nothing corroborated. A −96% collapse with zero corroborating signals has two possible explanations — an undetected real disruption, or broken measurement — and the honest move is to publish the evidence for both rather than silently suppress the anomaly or, worse, headline a phantom shutdown.
The signature of coverage loss, not a closure. Three measured facts separate these explanations. First, altitude: position reports below 3,000 m in the Monterrey area went 341 → 217 → 0 across 14–16 August, while 181 distinct aircraft were still seen crossing the same airspace at cruise levels on 16 August (vs 246 on 14 Aug), and the cruise-level count has held at 181–268 aircraft a day ever since — never near zero. Receivers near the city stopped hearing; distant ones still catch high traffic. A closed airport does not delete a region's ability to receive low-altitude radio signals. Second, lockstep: Monterrey Del Norte (MMAN), a separate airport across the city, fell 155 → 100 → 72 → 1 over the same days. Two airports in one metro do not shut down simultaneously without a single published notice. Third, composition: MTY's 12 observed movements on 16 August were all arrivals, zero departures — the fingerprint of edge-of-coverage detection, not of a functioning schedule.
The independent checks we ran. MTY's weather station kept reporting on its normal hourly cadence throughout — 726 observations over the last 30 days at a steady 24 a day, the latest at 14:40 UTC on 7 September: broken cloud at 2,000 ft, 6 SM visibility in haze, a light north-easterly wind, 26 °C — marginal VFR, with zero IFR/LIFR observations in the entire 30-day window. No closure NOTAM for the Monterrey FIR (MMTY) appears in our feed — though we flag honestly that our NOTAM source's coverage of Mexican domestic notices is thin, so this absence is weak evidence on its own. There is no volcanic-ash exposure and the GNSS-interference ratio for the area is at its floor (0.001). Traffic at Mexico City (800 / 893 / 859 / 847 / 809 movements on 16–20 Aug against a steady ~880/day) and Cancún (421 / 374 / 363 / 340 / 354 against ~430/day) stayed visible throughout — never anywhere near Monterrey's near-zero. This is also where the caution about fresh days keeps proving necessary — and it kept resolving the same way. 2 September was flagged here in the last update as the under-landed day, reading 572 at Mexico City and 266 at Cancún against a ~156k global rollup; it has since filled back in to 849 at Mexico City — normal — as that day's global rollup recovered to ~250k movements, while Cancún recovered only to 313, still under its ~355 norm. That is the fourth flagged gap day running, after 29 and 30 August and 1 September, to heal after being labeled rather than deleted. The shortfall has moved one day later, to 4 September, whose rollup landed ~121k movements globally against a ~245k median for the surrounding fortnight: it reads 401 at Mexico City and 269 at Cancún, both under their usual ~820 and ~355. Mexico City is back at 781 on 5 September; Cancún reads 42 that day, its own fresh-day hole rather than a Monterrey signal. Net: unlike Monterrey, the country's busiest airports have not lost coverage in a sustained way, so the failure looks localised to the Monterrey area rather than national. A second crowdsourced ADS-B aggregate we cross-check against also lost Monterrey on 16 August — no row at all for that day, then 4, 4, 2, 9 and 3 movements on 17–21 August — while seeing Mexico City normally, corroborating that reception died in the area; we label this check honestly, since crowdsourced networks share volunteer receiver hosts and it is therefore not fully independent evidence about operations. That same aggregate now puts MTY at 278–392 movements a day since 23 August, including 362 on 4 September — and our own position feed was healthy that day too (288 low-altitude reports near Monterrey, and 947,851 positions worldwide against a ~900k daily norm). Two of our three views of 4 September are normal, which is what identifies the third — our movement rollup, at 182 — as under-landed rather than anything happening at the airport. The same three-way check runs the other way for 5 September: the second aggregate reads 297, our rollup 314, and our position feed logged 241 low-altitude reports — three views agreeing on a genuinely quieter day at Monterrey, not a hole in the data. That check cleared 29 and 30 August, 1 September and 2 September in previous updates, and all four have since filled in on their own — which is why we label these days rather than delete them.
The footprint is regional, around Monterrey. Observed movements at Veracruz (VER), ~700 km south in the Mexico FIR (MMEX), fell 59 → 48 → 7 over the same 14–16 August window (−89% against its ~66/day average), and small border airports like Nuevo Laredo faded to zero — the anomaly clusters in northeastern Mexico, tightest around Monterrey. Veracruz has since recovered along with Monterrey (37 / 43 / 47 / 53 / 61 / 73 / 60 / 65 / 44 / 56 movements on 22–31 Aug, then 54, 71, 58 on 1–3 Sep and 58 on 5 Sep — its seven most recent fully-landed days average 58, a little under its ~66/day pre-outage rate; 4 Sep reads 38 and is the same under-landed fresh day flagged throughout this page, not a Veracruz signal). Monterrey Del Norte (MMAN) recovered on the same clock: 55–132 movements a day since 28 August, averaging 78 over the seven most recent fully-landed days against a ~102/day pre-outage mean — restored, and still running somewhat below where it was. We initially saw the busiest national airports dip on the freshest days too, but late receiver data revised every one of those newest days upward as it arrived — with the settled figures now sitting at their normal levels (Mexico City 847, Cancún 340 on 19 Aug), far above Monterrey's near-zero — so we are walking back the earlier 'national' framing: the sustained, days-long coverage loss is a Monterrey-area phenomenon, not a country-wide one. A gradual, multi-airport, multi-day decline that starts mid-feed is what volunteer receivers going offline one by one looks like; operational disruptions are announced, bounded and airport-specific. This is a coverage-level observation about our own measurement, labeled as such — not a claim about operations at any of these airports.
What we cannot say, and what changed this page. Being honest about the likely cause cuts both ways: through 21 August, with low-altitude coverage down, we could not measure Monterrey's actual traffic, and nothing published since fills that window. From 22 August coverage returned and stayed — which is the middle of the three branches this page listed while it was open: a closure NOTAM or other official signal appearing (it never did); coverage returning with counts near the ~400 baseline (what happened); or coverage returning with counts genuinely depressed (it did not). We still do not declare the airport 'operating normally' — that judgement belongs to the airport, the airlines and the relevant authorities, and our freshest one or two days still land short before filling in. What we can say is narrower and is the thing we owed readers: the measurement failure we flagged has ended. Automated multi-signal analysis keeps re-checking every layer for Monterrey; if the count breaks again, a new page opens. Publishing our own blind spots is the price of publishing observed counts at all — a floor is only trustworthy if you say so when the floor itself gives way.
What the data showed — final numbers. Closed 7 September 2026 as a confirmed loss of receiver coverage, not a disruption. The recovery number: low-altitude ADS-B position reports near Monterrey have run for sixteen consecutive days (22 August–6 September) with no day below 161, and average 288 a day over the last seven (31 Aug–6 Sep) against a 319/day pre-outage mean — 90% of it. Observed movements at MTY track the same recovery: the seven most recent fully-landed days (29 August–5 September, excluding the still-ingesting 4 September) average 346 movements a day, 87% of the ~400/day baseline, balanced between departures and arrivals rather than arrival-only as during the outage. The independently-sourced ADS-B aggregate we cross-check puts MTY at 278–392 a day over the same stretch. Monterrey Del Norte came back too (78/day over its last seven landed days vs ~102 before), Veracruz likewise (58 vs ~66). Through it all, no corroborating disruption signal ever appeared: no closure NOTAM for the Monterrey FIR, no ash exposure, GNSS interference at its floor (7-day ratio 0.002), and MTY's weather station reporting continuously — 726 observations in 30 days, zero IFR or LIFR among them. Two things this close-out does not claim. First, 15–21 August stays unmeasurable: that week is a hole in our data, and the counts published for it are a floor produced by broken coverage, not a record of what flew. Second, the residual gap between the recovered counts and the pre-outage baseline (−13% on movements, −10% on low-altitude reports) is not evidence of reduced operations — the recovery is still healing at the fresh end, seasonality is unaccounted for, and observed counts are a floor. Every day we marked as under-landed during this event — 29 and 30 August, 1 and 2 September — subsequently filled in; 4 September is the last one still open, and we label it rather than delete it. Source: observed movement counts and position aggregates from the crowdsourced ADS-B receiver network, weather continuity from published METARs.
Passenger questions, answered from the data
Nothing in the signals we track indicates a closure: MTY's weather station reports hourly as normal in clear conditions, no closure NOTAM for the Monterrey FIR appears in our feed, and the collapse in observed traffic matches the signature of receiver-coverage loss, not a shutdown. Coverage returned on 22 August and has held for sixteen days; observed counts have averaged 346 a day against a ~400/day baseline, which fits the coverage-loss reading — but we measure signals, not operations, so for the status of a specific flight, check your airline or the airport's own channels.
Flight-tracking services build their picture from crowdsourced ADS-B receivers hosted by volunteers. When receivers in an area go offline, low-altitude traffic — arrivals and departures — disappears from the picture first, because only nearby antennas can hear it. Our data shows exactly that signature for Monterrey from 15–16 August 2026: position reports below 3,000 m fell to zero while high-altitude overflights stayed visible. The flights are not necessarily gone; the ability to see them is. Those low-altitude reports came back on 22 August and have run 241–386 a day since 26 August, averaging 288 over the last seven days against a 319/day pre-outage mean — which is why this page is now closed.
The observed count on 16 August stands at 12 movements against a ~400-movement daily baseline (−97%); late-data reprocessing has moved that day between 12 and 3 as receiver data trickles in. Observed counts are a floor, not a total: they count what the receiver network hears, and every cross-check we ran (altitude profile of lost signals, a second Monterrey airport collapsing in lockstep, continuous normal weather reporting, no closure signal in any layer) points to the network losing the area, not to flights stopping. We publish the anomaly with that attribution rather than headline a phantom shutdown.
We publish measured signals, not safety verdicts — go/no-go decisions belong to airlines, airports and aviation authorities, who operate from their own complete data, not from crowdsourced tracking. Nothing in the layers we track — weather reporting, closure notices, ash, GNSS interference — indicates a hazard at Monterrey; what failed, on the evidence, is public visibility of the traffic.
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.
“Observed traffic at Monterrey International fell from 443 movements on 14 August to 12 on 16 August, but ADS-B position reports below 3,000 metres in the area fell to zero while high-altitude overflights remained visible and the airport's weather station kept reporting normally — the signature of receiver-coverage loss rather than an airport shutdown, 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.

