Ahmedabad (AMD) Traffic ‘Drop’ of −72% on Sunday 1 November 2026 — the Airport Went Silent in Our Feed at 08:00 UTC, and We Cannot Measure It
- The −72% on 1 November is a gap in our own feed, not evidence of fewer flights. Ahmedabad’s records stop at 08:00 UTC, while flights bound for Ahmedabad kept departing Delhi, Bengaluru, Mumbai and other cities at their usual rate.
- Weather reports showed routine haze and mist with light winds, and no closure signal registered in the Mumbai FIR (VABF). We found nothing in any layer that points to an operational stoppage.
- Records came back at 13:23 UTC on 3 November, and 4 November ran a full day in our feed (228 movements, inside the usual range) — but they stopped again at 05:36 UTC on 5 November and came back at 07:16 UTC on 9 November, with 11 November back inside the usual range (269), before thinning again on 13–14 November; 15 November settled at 275, inside the usual range, and the record thinned again from 08:00 UTC on 16 November. For 1–3, 5–9 and 13–14 November we cannot say how many flights operated. Observed counts are a floor, not a total — for a specific flight, check your airline or the airport.
Advisory timeline — how active is this episode
This chart splits Ahmedabad’s 1 November count into two-hour UTC blocks (Ahmedabad is UTC+5:30, so 08:00 UTC is 13:30 local). From midnight to 08:00 UTC our feed recorded 71 movements — thinner than the ~105 of the same hours on 25–30 October, but a working airport by any reading. From 08:00 UTC to midnight it recorded none, in eight blocks that normally carry 8 to 27 movements each. A traffic fall caused by weather or a disruption thins blocks unevenly and leaves a trickle; a record that drops to zero mid-afternoon across both departures and arrivals is the signature of a signal that stopped:
Fig. 1 — Observed departures + arrivals at Ahmedabad (AMD) in each two-hour UTC block of Sunday 1 November 2026; the 25–30 October average for the same blocks is 26 / 28 / 24 / 27 / 14 / 19 / 26 / 27 / 26 / 23 / 8 / 10 · Data as of 19 Nov 2026, 00:55 UTC · Source: Observed movement records for VAAH from a crowdsourced ADS-B receiver network, as collected by FlySafe monitoring.
Airports in the exposure zone
| Airport | Size | Observed signal | FIR |
|---|---|---|---|
| Sardar Vallabh Patel International Airport (AMD) | large | — · 1 Nov: 71 observed movements (46 dep / 25 arr), all before 08:00 UTC, −72% vs ~258; 26 of 30 AMD-bound flights with no recorded landing; 2 Nov: 7 records, all 04–06 UTC; 3 Nov: 104 from 13:23 UTC on (99–115 in the same hours 25–30 Oct); 4 Nov: 228 settled (117 / 111), 26 of 29 AMD-bound flights recorded landing; 5 Nov: settled 71 (50 / 21), all before 05:36 UTC; 6–8 Nov: no record after all three ingest nights; 9 Nov: 110 from 07:16 UTC (54 / 56, final), below the same hours of 25–30 Oct; 10–12 Nov: 306 / 269 / 294 (167 / 139, 145 / 124, 166 / 128) after the 17 Nov catch-up night filled feed-wide shortfalls — whole days, 11 Nov inside 208–280; 13 Nov: 31 (19 / 12) and 14 Nov: 41 (26 / 15) with the rest of the feed complete — not readable; 15 Nov: 275 (146 / 129) settled, inside 208–280; 16 Nov: 97 after two nights, 83 of them before 08:00 UTC; 17 Nov: no record after one night | VABF |
| Vadodara International Airport (BDQ) | medium | 102 km · Second network: no record on 1–2 Nov, after 8–23 a day on 25–31 Oct — the coverage loss reaches beyond Ahmedabad; back on 3 Nov (14), 18–19 on 4–5 Nov, 14 on 7 Nov, 8 on 8 Nov, 15 on 9 Nov, 13 on 10 Nov, 20 on 11 Nov, 4 on 12 Nov, 23 on 13 Nov, 4 on 14 Nov, 21 on 15 Nov, 16 on 16 Nov, 4 on 17 Nov (6 Nov missing across that whole feed) | VABF |
| Chhatrapati Shivaji Maharaj International Airport (BOM) | large | 444 km · Separate partial coverage gap since 25 Oct (own brief); evening records back on 1 Nov | VABF |
| Indira Gandhi International Airport (DEL) | large | — · Control: 936 departures on 1 Nov, inside the 921–960 of 25–31 Oct; Ahmedabad-bound flights still departing | VIDF |
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: a stable month, then a record that thins and stops
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. Sardar Vallabh Patel International Airport's last 30 days:
Fig. 2 — Observed daily movements at AMD, 4 Oct – 15 Nov (latest complete UTC day). Data as of 19 Nov 2026, 00:55 UTC · Source: FlySafe monitoring (ADS-B receiver network).
- Baseline = 25–30 October, the first six days of the winter timetable: 280, 266, 259, 250, 228 and 262 observed movements, ~258 a day. Across 4–30 October the airport read between 208 and 280 on every day but one (178 on 23 October, a day on which departure records also thinned). Sunday 1 November came in at 71 — −72% against that baseline (46 departures, 25 arrivals). Detection fired at −66% against a seven-day rolling average of ~210 that already included a partly recorded 31 October.
- The 31 October and 1 November bars are coverage-gap days, not traffic readings. 31 October is plotted at its settled count, 157 (65 departures, 92 arrivals): arrivals ran close to normal, departures at about 40% of the 133–159 of 25–30 October. 1 November is plotted from a recount of the raw flight records — 71 movements, all before 08:00 UTC (the stored rollup of 20 was clipped by a routine refresh); a third ingest night added nothing. Neither is a whole day at the airport, and neither should be read as one.
- 2 and 3 November are left blank as gap days. After three nightly ingests our feed holds seven records at Ahmedabad for 2 November (three departures, four arrivals), all between 04:00 and 06:00 UTC, while the same nights carried tens of thousands of records elsewhere. For 3 November, after two ingest nights, it holds 104 movements (42 departures, 62 arrivals), every one from 13:23 UTC onward — inside the 99–115 of the same hours on 25–30 October, but only the second half of a day.
- 4 November, the first full day back, settled at 228 (117 departures, 111 arrivals) after all three nightly ingests, with records in every two-hour block from 00:15 to 23:59 UTC. That is −12% against ~258 and level with 29 October’s 228 — inside the 208–280 that 4–30 October read on every day but one. Arrivals (111) sit inside the 95–121 of 25–30 October; departures (117) stay short of their 133–159, the one part of the count still below range. Network-wide, takeoff records for 4 November ran 5–11% below 26–30 October at the same ingest stage, so part of that shortfall sits in the feed as a whole.
- 5–8 November are not plotted: the record stopped again. After all three nightly ingests 5 November settled at 71 movements (50 departures, 21 arrivals), every one between 00:09 and 05:36 UTC — at the two-night stage, 69 before 05:36 against 65–79 in the same hours of 25–30 October — and nothing after. 6 November, after all three ingest nights, holds no record at Ahmedabad at all, while network-wide that day settled at 145,560 takeoff records, level with 5 November, and Delhi departures read 974. 7 and 8 November, after all three ingest nights, hold none either (network-wide 131,196 and 131,849 takeoff records, Delhi 916 and 821). These are gap days, not traffic readings.
- Records resumed at 07:16 UTC on 9 November; 10–12 and 15 November are plotted, 9, 13–14 and 16–17 November are not. 9 November finished at 110 movements (54 departures, 56 arrivals), every one from 07:16 UTC onward — below the 124–181 that the same hours carried on 25–30 October once settled, with arrivals at 56 against 65–94. Its third ingest night added nothing; network-wide that night carried 15 takeoff records for the day, against 4,700–5,400 on most earlier days. It is the second part of a day, not a whole day. 10–12 November then ran into five nightly ingests, on 12–16 November, that each carried a small fraction of their usual records across the whole feed — about 3,200–3,600 takeoff records network-wide per day at the second-night stage, against 100,000–125,000 for each of 1–9 November — so for a week those days held only 39–53 movements at Ahmedabad and could not be read. The 17 November ingest night caught up: it carried 841,757 records, 106,000–128,000 takeoff records for each of 10–16 November, and network-wide 10–12 November now hold 145,308–146,699 takeoff records each, at the top of the 131,196–145,865 of 2–9 November, with Delhi departures at 947–960. At Ahmedabad 10, 11 and 12 November now read 306, 269 and 294 movements (167 / 139, 145 / 124 and 166 / 128 departures / arrivals), each recorded from the first ten minutes after midnight to 23:48 UTC or later. 11 November sits inside the 208–280 of 4–30 October; 10 and 12 November read above it, as do their departures (against 133–159 on 25–30 October) and arrivals (against 95–121). We read none of the three as a change in traffic — only as the airport back in our feed across whole days — and a late record could still be added. They are plotted. 13 and 14 November are not plotted: our record thinned again. With the rest of the feed now holding both days in full (141,851 and 124,929 takeoff records network-wide, Delhi departures 988 and 937), Ahmedabad holds 31 movements for 13 November (19 departures, 12 arrivals) and 41 for 14 November (26 / 15), scattered across both days, against 208–280. 15 November settled at 275 (146 departures, 129 arrivals), with records in every two-hour block from 00:01 to 23:56 UTC; its third ingest night added nothing, and network-wide that night carried no takeoff records for the day at all. It sits inside the 208–280 of 4–30 October, so the 13–14 November break meets the same test the first two did, and it is the last bar. 16 November, after two ingest nights, still holds 97 (56 / 41): 83 before 08:00 UTC and 14 after, against 8–27 a block in those hours on 25–30 October. Its second night carried 1,062 takeoff records network-wide for the day; the day now holds 121,560, near the 124,929–126,408 of 14–15 November, but Delhi departures read 610, against 891–988 on 13–15 November, so the day may not be complete in our feed yet. 17 November, after one ingest night, holds no record at Ahmedabad, while that night carried 81,931 takeoff records network-wide for the day and 372 Delhi departures. Neither day is plotted; whether this is a fourth break is read once their ingest nights are in.
- Not a feed-wide collection gap. Network-wide, 1 November holds 119,049 takeoff records, above our 60% gap rule but softer than recent days, and Delhi departures read 936, inside the 921–960 of 25–31 October. Ahmedabad’s fall is out of all proportion to that softness.
Observed counts are a floor, not a total — they measure what our receivers heard, and they are meaningful only while coverage holds. Here it did not. Live view: AMD airport brief.
What it means for flights
What fired, and why we do not read it as a traffic drop. Our detection layer flagged AMD when Sunday 1 November came in at 71 observed movements against a rolling seven-day average of ~210 — a −66% traffic anomaly; against the ~258 a day of 25–30 October it is −72%. A drop that size can be an operational event or a failure of the instrument, so automated multi-signal analysis checks it against every other layer we track before anything is claimed. Here the layers line up on the instrument, as at Mumbai in October: the count does not thin, it stops — all 71 records fall before 08:00 UTC, and the eight two-hour blocks after that, which normally carry 8 to 27 movements each, are empty for departures and arrivals alike.
The flights kept flying — they dropped out of view near Ahmedabad. The test that separates a real drop from lost coverage is continuity. We took the 50 callsigns that landed at Ahmedabad from nine major origins (Delhi, Bengaluru, Mumbai, Kolkata, Chennai, Hyderabad, Kochi, Dubai, Abu Dhabi) on at least two days of 25–30 October, and counted their departures from those origins after 06:00 UTC each day. On 1 November they departed 30 times, against 28–35 a day on 25–31 October — the origin airports saw them go. On the earlier days 24–34 of them were recorded landing at Ahmedabad; on 1 November 0 were, and 26 ended with no recorded destination at all, against 0–1 on most days (6 on 29 October). On 2 November, after three ingest nights, it is 31 departures, none recorded landing, 26 with no destination; on 3 November, the day records resumed, 20 of 28 were recorded landing at Ahmedabad, and on 4 November, the first full day back, 26 of 29, with 1 ending with no recorded destination — the pre-gap pattern. The outbound side reads the same way: callsigns that usually depart Ahmedabad were seen in the air with no recorded origin 56 times on 1 November and 77 on 2 November, against 8–15 a day on 25–30 October; on 4 November it was 14. On 5 November, when our Ahmedabad record stopped again at 05:36 UTC, both checks returned to the gap pattern: 31 departures from those origins, none recorded landing at Ahmedabad and 26 with no recorded destination, and 45 no-origin sightings on the outbound side. 6 November, after all three ingest nights, reads the same way — 29 departures, none recorded landing, 23 with no recorded destination, and 67 no-origin sightings — as do 7 and 8 November after all three nights (29 and 30 departures, none recorded landing, 24 and 25 with no destination, 66 and 70 no-origin sightings). On 9 November, the day records resumed at 07:16 UTC, the pattern turned part-way back: 14 of 32 departures were recorded landing at Ahmedabad and 17 ended with no recorded destination, and outbound callsigns were recorded departing Ahmedabad 43 times against 54 no-origin sightings. The origin airports’ records for 10–16 November arrived in bulk only with the 17 November catch-up ingest night, and this check has not yet been re-run on those days. A callsign is a flight number, not a specific aircraft, and this is a continuity indicator, not a flight log — but it is what lost reception looks like, and not what cancellations look like.
It began a day earlier, on the departure side. 31 October was already incomplete. Arrivals ran close to normal (92, just under the 95–121 of 25–30 October), but departures were recorded 65 times against 133–159, and callsigns that usually depart Ahmedabad turned up with no recorded origin 62 times, against 8–15. A receiver that hears aircraft on approach but loses them on the ground and in the first minutes of climb would produce exactly that. On 1 November the loss became total from 08:00 UTC. We cannot see the receivers themselves, so this is an inference from the pattern of records, not a confirmed equipment fault.
The second network lost the area too. We cross-check against a second crowdsourced ADS-B aggregate built on volunteer receivers. It does not report movements for Ahmedabad at all, so it cannot confirm or contradict the count directly, but its count of aircraft seen per one-degree cell is telling: the cell covering the Ahmedabad–Vadodara area fell from 141–152 aircraft a day on 29–31 October to 3 on 1 November, and the cells to its south roughly halved. Its movement count for Vadodara, 102 km away, went from 8–23 a day to no record on 1–2 November. Two networks losing the same area on the same day points at shared receivers going offline, not at the sky emptying — some volunteer receivers feed more than one network. On 3 November the second network saw the area again: the Ahmedabad–Vadodara cell read 173 aircraft, the cells to its south were back in their usual range, and Vadodara reappeared with 14 movements. Our own feed caught up after a second ingest night: Ahmedabad records resume at 13:23 UTC on 3 November, and the 104 movements from then to midnight sit inside the 99–115 of the same hours on 25–30 October. The two networks again move together, but our 3 November holds only the second half of the day, so it is not plotted as a traffic reading. The second network has held the area since: the Ahmedabad–Vadodara cell read 169 aircraft on 4 November and 187 on 5 November, with Vadodara at 18 and 19 movements. This time the two networks part: 5 November, the day our own Ahmedabad record stopped again at 05:36 UTC, is the second network’s highest cell count since 29 October, which points at reception specific to our own feed rather than a shared receiver outage. Its 6 November figures are missing across its whole feed, not just this area. On 7 November the Ahmedabad–Vadodara cell read 87 aircraft, about half of 4–5 November, and the cells to its south 49–67 against 121–200 on 3–5 November, while the network’s count across India fell about 8% and Vadodara read 14 movements — the second network has thinned over the area too, but still sees it, unlike the 3 aircraft of 1 November. On 8 November the cell read 112 and Vadodara 8 movements, while the cells to its south ran 1–71 (one with no record) and the cells over Mumbai also fell, with the network’s count across India about 13% below 5 November — a thinning across western India in that feed, not one specific to Ahmedabad. On 9 November, the day our own records resumed, the cell read 182, back to its 4–5 November level, with the cells to its south at 59–105 and Vadodara at 15 movements. On 10 November the cell read 161, the cells to its south 108–185, near the 121–200 of 3–5 November, and Vadodara 13 movements, with the network’s count across India about 2% below 5 November. On 11 November the cell read 154, the cells to its south 118–184, and Vadodara 20 movements. On 12 November the cell fell to 67, less than half its 9–11 November level, and Vadodara read 4 movements, while the cells to its south held at 110–191 and the network’s count across India was about 1% below 5 November — a thinning in that feed over the Ahmedabad–Vadodara cell alone, on a day our own first-night record at Ahmedabad ran close to its usual size; we do not attribute it. On 13 November the cell was back at 146, the cells to its south at 121–172 and Vadodara at 23 movements, with the network’s count across India level with 5 November — the two networks part again: the same day, after one ingest night of usual size, our own feed holds a single record at Ahmedabad. On 14 November the cell fell to 79, about half its 13 November level, and Vadodara read 4 movements, while the cells to its south held at 113–184 and the network’s count across India stayed level with 5 November — again a thinning over the Ahmedabad–Vadodara cell alone, which we do not attribute; that network still sees the area, unlike the 3 aircraft of 1 November, while our own feed holds no record at Ahmedabad that day. On 15 November the cell was back at 149, the cells to its south at 130–185 and Vadodara at 21 movements, with the network’s count across India about 1% below 5 November — the same day our own Ahmedabad records resumed at 02:38 UTC. On 16 November the cell read 136, the cells to its south 119–181 and Vadodara 16 movements, with the network’s count across India about 3% below 5 November. On 17 November the cell fell to 58 and Vadodara read 4 movements, while the cells to its south held at 103–162 and the network’s count across India was about 6% below 5 November — again a thinning over the Ahmedabad–Vadodara cell, which we do not attribute. Its latest day is 17 November. Mumbai, 444 km south, is in a separate partial coverage gap of its own since 25 October, with evening records back on 1 November.
No weather, no closure, no interference. Ahmedabad’s routine weather reports on 31 October – 3 November show haze, mist and smoke with visibility of 2,000–6,000 m, no cloud ceiling and winds of 0–12 kt; none of the 178 reports carried thunderstorm, fog or heavy rain. Around 05:30 UTC on 5 November, when our records stopped again, the reports read smoke haze with 4,000 m visibility, no cloud ceiling and 6–7 kt winds; across 5–18 November they show haze, smoke and mist at 1,000–6,000 m (the lowest, 1,000 m in mist and haze between 01:30 and 02:00 UTC on 17 November; 1,200 m early on 9 November; 1,500 m in haze at 01:30 UTC on 18 November), no cloud ceiling and winds of 0–10 kt, with no thunderstorm, fog or heavy rain. No closure signal registered in the Mumbai FIR (VABF) for 31 October – 7 November — a FIR-level statement about airspace signals, not a claim about operations at Ahmedabad, which belong to the airport, the airlines and Indian aviation authorities. Two older low-confidence (0.18) VABF flags of unknown cause, spanning 15–22 and 25–28 October, are tied to the Mumbai gap, not to Ahmedabad. A third flag of the same kind, for 8 November, registered at 21:00 UTC that day; it rests on an FIR-level traffic-anomaly reading from our own feed and on three notices already in our set — a test-flight airspace reservation, a flying-club training area and a local-flying area, none at Ahmedabad — so it adds no independent signal about the airport; no flag has registered for 9–17 November. Our NOTAM set, last refreshed on 19 November at 00:31 UTC, holds 26 VABF notices; the two that name Ahmedabad concern a departure route into the Mumbai terminal area and an advisory, in force since 22 October, asking crews not to request direct routings in the Ahmedabad terminal area to reduce radio congestion — and none closes the airport. The airport’s seven-day GNSS-interference ratio is near zero.
What would change this page. Two things decide it. The records coming back: the reception half of that test is now met — Ahmedabad reappeared in our feed at 13:23 UTC on 3 November at its pre-gap hourly rate, and on 4 November its records ran through the whole day, with AMD-bound flights recorded landing again and the second network seeing the area as before. The count half is now settled too: after its third ingest night 4 November finished at 228, inside the 208–280 that 4–30 October read on every day but one, so the 1–3 November break reads as a coverage gap — the test this page set is met. But from 05:36 UTC on 5 November our Ahmedabad record stopped again, 6–8 November hold no record at all after their third ingest night, and AMD-bound flights once more ended with no recorded destination, while the second network kept seeing the area. Records resumed at 07:16 UTC on 9 November, and once a catch-up ingest night on 17 November filled the shortfalls of 12–16 November across the whole feed, 11 November read 269, inside 208–280 — the second break meets the same test (10 and 12 November read above the range, at 306 and 294). Then our record thinned again: 13 and 14 November hold 31 and 41 movements with the rest of the feed complete, so traffic on those days is not measurable either. 15 November settled at 275 after three ingest nights, inside 208–280, so that third break meets the test too. From 08:00 UTC on 16 November our record thinned again, and 17 November holds no record after one ingest night; both days are read once their ingest nights are in. An official signal: a closure, a NOTAM or an operational notice for AMD appearing in any layer would change the framing. Until then we publish measured signals and their limits, not a traffic figure we do not have.
Passenger questions, answered from the data
Nothing in the layers we track points to a closure. No closure signal registered in the Mumbai FIR (VABF), no notice in our NOTAM set closes the airport, and flights bound for Ahmedabad kept departing Delhi, Bengaluru, Mumbai and other origins at their usual rate. The −72% reading comes from our own receivers losing Ahmedabad from 08:00 UTC. For official status, check the airport or your airline.
The observed count did — 71 movements on 1 November against ~258 a day on 25–30 October — but all 71 fall before 08:00 UTC, and after that our feed recorded nothing at the airport. Observed counts are a floor, not a total, and on this day the floor is not informative: flights that normally land at Ahmedabad kept departing their origins, but their landings were not recorded, and a second receiver network lost the area too. We do not know how many flights operated, and we do not claim a fall.
Crowdsourced flight tracking depends on volunteer ground receivers near each airport. The pattern we see — departure records thinning on 31 October, then every record stopping at 08:00 UTC on 1 November, with a second network losing the same area the same day — is consistent with receivers in the Ahmedabad area going offline. We cannot see the receivers themselves, so the cause of the outage is not known to us.
We publish measured signals, not safety verdicts — operating decisions belong to airlines, the airport and Indian aviation authorities, who work from complete operational data rather than crowdsourced tracking. What we can say: the gap is in our measurement, weather at the airport was routine haze and mist, and no closure signal registered in the Mumbai FIR. For any specific flight, check your airline on the day of travel.
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 Ahmedabad’s Sardar Vallabh Patel International Airport read 72% below normal on 1 November, but the figure reflects a gap in crowdsourced tracking rather than fewer flights: every recorded movement fell before 08:00 UTC, flights bound for Ahmedabad kept departing Delhi, Bengaluru and Mumbai at their usual rate with their landings unrecorded, and a second receiver network lost the same area the same day, 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.

