Orlando Sanford (SFB) Observed Traffic −73%: Training Flights Stood Down Under Rain and Low Cloud — November 2026
- Our count at Sanford fell to 129 movements on 18 November (provisional), −72% against recent Wednesdays — the shortfall is mostly local training and private flying; airline flights kept operating through the day.
- Sanford reported low cloud and heavy rain for most of the daytime, and small airports across central Florida dropped together, while Orlando International, Tampa and Jacksonville were close to normal.
- Sanford was still reporting IFR in rain early on 19 November. This page will update as the counts settle; for a specific flight, check your airline and the airport.
Advisory timeline — how active is this episode
This chart isolates the part of Sanford's traffic that moved. Over the eight days to 16 November, one callsign family accounted for 2,812 of the airport's 4,331 observed movements — 65%: a fleet of 65 airframes flying sorties of about an hour, most of which land back at Sanford — the signature of flight training (that word is our interpretation of the pattern, not a measurement). On the previous four Wednesdays it logged 306, 160, 379 and 369 movements. On Wednesday 18 November it logged 78, with 27 airframes flying against 46–64 on those Wednesdays — the second-lowest day in the 30-day window. The lowest, 80 on Monday 2 November, came on a day of IFR and marginal-VFR reports at Sanford, and the fleet was back at 321 the next day. The 16 and 17 November bars are recounts from raw records (see the gap-day note below); the 18 November bar is provisional until 22 November and may rise.
Fig. 1 — Observed daily movements at Orlando Sanford International (SFB) by the airport's largest callsign family — a fleet flying short sorties that mostly end back at Sanford — 20 Oct – 18 Nov 2026; 16 and 17 Nov recounted from raw records, 18 Nov provisional until 22 Nov · * partial day · Data as of 19 Nov 2026, 03:55 UTC · SFB series settled through 15 Nov; 16 and 17 Nov plotted as recounts; 18 Nov provisional (one overnight collection pass, settles 22 Nov); NOTAM set for the Jacksonville FIR last refreshed 15 Aug · Source: FlySafe monitoring (crowdsourced ADS-B receiver network).
Airports in the exposure zone
| Airport | Size | Observed signal | FIR |
|---|---|---|---|
| Orlando Sanford International Airport (SFB) | medium | — · Wed 18 Nov: 129 observed, provisional (63 dep / 66 arr) vs ~455 Wednesday mean (−72%) · training fleet 78 vs ~304 (27 of 65 airframes) · airline 19 vs 27–37 · IFR or lower in 9 of 11 daytime weather reports | KZJX |
| Orlando International Airport (MCO) | large | 39 km · Same metro, same feed: 909 observed on 18 Nov (provisional) against 956 on Wed 11 Nov (−5%); 7 IFR or lower and 15 marginal-VFR among 42 weather reports that day | KZJX |
| Tampa International Airport (TPA) | large | 155 km · 518 observed on 18 Nov (provisional) against 561 on Wed 11 Nov (−8%) — in line with the worldwide shortfall in our record that day | KZJX |
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: local training and private flying fell away under rain and low cloud; airline flights kept operating
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. Orlando Sanford International's last 30 days:
Fig. 2 — Observed daily movements at SFB, 20 Oct – 18 Nov (latest complete UTC day). Data as of 19 Nov 2026, 03:55 UTC · SFB series settled through 15 Nov; 16 and 17 Nov plotted as recounts; 18 Nov provisional (one overnight collection pass, settles 22 Nov); NOTAM set for the Jacksonville FIR last refreshed 15 Aug · Source: FlySafe monitoring (ADS-B receiver network).
- Wednesday 18 Nov: 129 observed movements, provisional (63 departures, 66 arrivals) — −72% against the ~455 mean of the four previous Wednesdays (466, 267, 526, 561). The detection layer fired at −73% against the 481 seven-day all-days average. Between 12:00 and 22:00 UTC — the local daytime — we counted 101 movements against 460 in the same hours on 11 November.
- Where the drop sat: the training-fleet callsign family (chart above) logged 78 movements against a ~304 Wednesday mean — −74% — with 27 of its 65 airframes flying. Privately registered aircraft flying under their registration number logged 21 against ~94 (−78%). Between them, those two groups account for most of the shortfall.
- Scheduled airline movements kept operating. Sanford's based low-cost carrier (callsign family AAY) logged 19 movements between 13:32 and 22:58 UTC, against 37, 31, 27, 30 on the four previous Wednesdays. That is lower, on a provisional day when our worldwide record is itself short (below), and its schedule varies by day; we do not read the difference as cancellations, and we make no claim about any individual flight.
- Collection on 18 November: our worldwide departure record for the day stands at 118,747 — 82% of the previous Wednesday's 145,308 — after a single overnight collection pass. That is short but above our 60% gap-day rule, and it cannot explain Sanford reading 23% of its previous Wednesday while Orlando International, 39 km away, read 95%.
- Tuesday 17 Nov: 413, recounted (202 / 211) — −10% against ~461 on the four previous Tuesdays (472, 326, 450, 594); fleet 296. The stored rollup reads 699 because the day was collected twice, on the nights of 18 and 19 November, and most flights were stored as near-duplicates (the same pattern appears at Atlanta, Orlando International and Tampa that day); we plot a recount that drops repeated records.
- Monday 16 Nov: 431, recounted (211 / 220) — the stored rollup reads a clipped 398 from a trailing refresh; the raw records give 431. Fleet 253. Sanford reported 2 IFR and 2 marginal-VFR observations that day.
- Second, independent feed: a separate ADS-B source has no value for 18 November yet. On 17 November it read SFB at 72, below its 104–199 range on 1–16 November; that feed hears roughly a quarter to a third of the movements ours does at Sanford, so we report it and do not pick between them.
- Gap days, labeled: no collection-gap day in the 20 Oct – 18 Nov window as plotted. 16 and 17 November are recounts (clipped and double-collected rollups, respectively); 18 November is provisional, settles on 22 November and may still rise as later collection passes add flights.
Observed counts are a floor, not a total — our receiver network does not hear every movement, especially low-level local flying. Live view: SFB airport brief.
What it means for flights
What fired, and why we publish it. Our detection layer flagged SFB when the 18 November observed count came in at 129 movements against a seven-day average of 481 — a −73% traffic anomaly at a Florida airport with scheduled passenger service. Automated multi-signal analysis then cross-checked it against the other layers we track: same-weekday history, callsign composition, hourly shape, weather reporting, closure events, temporary flight restrictions, GNSS integrity, volcanic-ash exposure, tropical-cyclone advisories, neighbouring airports, worldwide collection completeness and a second independent ADS-B feed. The cross-checks say clearly which flying dropped. We publish it because a raw −73% at an airline airport invites the wrong reading, and the composition is what tells a traveller whether it matters to them.
Sanford's observed traffic is mostly training, and training is weather-sensitive. Over the eight days to 16 November, 65% of Sanford's observed movements came from one callsign family of 65 airframes flying sorties of about an hour, most of them returning to Sanford. Another ~17% are privately registered aircraft; the based low-cost carrier is about 9%. Instruction and private flying are largely visual — when cloud sits a few hundred feet above the ground and rain reduces visibility, visual flying largely stops while instrument-rated airline operations continue. That is the mechanism we believe explains this event; it is interpretation built on measurements, and we label it as such. What is measured: the training family fell 74% against its Wednesday mean, private registrations fell 78%, and airline movements continued from morning to late evening.
The weather on 18 November. Sanford's weather station reported IFR or lower in 9 of its 11 observations between 12:00 and 22:00 UTC, with broken-to-overcast cloud between 300 and 1,100 ft from 14:00 UTC, rain in most reports and a low-IFR special at 19:26 UTC (visibility 3/4 mile in heavy rain, cloud at 300 ft); winds gusted to 27 knots. Over the whole UTC day, 9 of 25 observations were IFR or lower and 7 marginal VFR. For contrast, all 21 Sanford observations on 11 November were VFR, and our 30-day record for the station puts IFR at 3% of 718 observations. Nearby stations agree: Orlando International filed 7 IFR-or-lower and 15 marginal-VFR reports among 42, Orlando Executive 7 IFR and 8 marginal among 26, and Daytona Beach IFR in 26 of 47 with gusts to 44 knots. Sanford was still reporting IFR in heavy rain at 03:15 UTC on 19 November, so the next day's count may also be low.
The geography test: small fields fell together, airline hubs did not. Each airport against the previous Wednesday, 11 November (single-day comparisons, provisional for 18 November): general-aviation and training fields across central Florida all dropped — Daytona Beach −90% (80 vs 827), Melbourne −83% (57 vs 329), New Smyrna Beach −99% (2 vs 164), Leesburg −84% (12 vs 77), Orlando Executive −65% (102 vs 289), Kissimmee −59% (76 vs 184). The airline hubs did not: Orlando International −5% (909 vs 956), Tampa −8% (518 vs 561), Jacksonville −10% (251 vs 280); Miami (−20%) and Fort Lauderdale (−19%) read lower, closer to the 18% worldwide shortfall in our record that day. A receiver-coverage loss would not sort airports by the kind of flying they host; weather that stops visual flying would. This is why the drop is not Sanford's alone and why we tag the Jacksonville FIR (KZJX), which covers central Florida, as the affected area.
It has happened before — at this airport, twice in two months. On Monday 2 November Sanford read 182 movements with the training family at 80 (31 airframes), as the airport filed 6 IFR and 12 marginal-VFR reports among 34; by Tuesday 3 November it was back at 450, fleet 321. In October, a two-day spell of IFR cloud took Sanford to 132 observed movements and the fleet to 49, with airline movements unaffected; the counts recovered within two days of the sky clearing — see our October brief. The November drop has the same shape: the training fleet goes quiet, the airline layer keeps flying, and neighbouring hubs stay close to normal.
The independent checks we ran. No airspace-closure event stands for the Jacksonville FIR (KZJX) in our detection layers: six have ever been recorded there, all in a late-May to 1-June cluster, and every one has since been invalidated by our own integrity checks. No FIR-level traffic anomaly has been logged for KZJX on 16–18 November (the most recent were overnight and early-morning dips on 13–15 November). The temporary flight restrictions we hold for Florida on 17–18 November (feed refreshed 00:00 UTC on 19 November) are security areas at Santa Rosa Island and Mayport, a space-operations area at Cape Canaveral on 17 November and the standing Disney World security area; none covered Sanford. GNSS interference for the FIR read 0.0002–0.0005 on every day from 8 to 17 November, at its floor; there is no ash exposure; and the US National Hurricane Center has no active Atlantic tropical cyclone in our record (the last November system, Pena, was in the central Pacific and ended on 12 November). Our NOTAM set for the Jacksonville FIR was last refreshed on 15 August, so we make no claim either way about closure notices for the aerodrome.
What we cannot say, and what changes this page. Observed counts are a floor, not a total — our receiver network does not hear every movement, and low-level local flying is the hardest kind to hear. We make no claim about Sanford's schedule-level totals, about individual cancellations, or about any flight's status; that belongs to the airport, the airlines and the FAA, who work from their own complete data. Three things will move this page: the settled 18 November count (from 22 November); the counts for 19 and 20 November, as the rain clears or does not; and any closure, restriction or traffic signal in the Jacksonville FIR. We will close it when the training family is back inside its normal range under ordinary weather, and say so with the number.
Passenger questions, answered from the data
We publish observed movement counts, not flight status. In our count, scheduled airline movements at Sanford kept operating through 18 November — the based low-cost carrier logged 19 movements between mid-morning and late evening local time. The 72% drop sits mostly in local training sorties and private flying, under low cloud and heavy rain. For a specific flight, check your airline or the airport's own channels.
On 18 November our receivers observed 129 movements at SFB, 73% below its 481 seven-day average and 72% below the ~455 mean of its four previous Wednesdays. About two-thirds of Sanford's normal observed traffic is one fleet flying short sorties that mostly return to Sanford — a flight-training pattern. That fleet logged 78 movements against a ~304 Wednesday mean (−74%) on a day when the airport reported IFR or lower in 9 of 11 daytime weather observations. The count is provisional until 22 November. Observed counts are a floor, not a total.
Not in our data. Orlando International logged 909 observed movements on 18 November against 956 on the previous Wednesday (−5%), despite 7 IFR-or-lower and 15 marginal-VFR weather reports that day. Tampa (518 vs 561) and Jacksonville (251 vs 280) were close to normal too. The drop is at airports dominated by training and private flying.
We publish measured signals, not safety verdicts — operating decisions belong to airlines, airports and the FAA, who work from their own complete data. What our layers show: no closure event for the Jacksonville FIR, no restriction over Sanford, no GNSS-interference signature, no ash exposure, no active Atlantic tropical cyclone, airline movements continuing through the day, and a sharp drop in training and private flying during low cloud and heavy rain.
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 Orlando Sanford International fell to 129 movements on Wednesday 18 November — 72% below recent Wednesdays — with the shortfall concentrated in local training sorties, down 74% as the airport reported IFR cloud and heavy rain in 9 of 11 daytime weather observations, while Orlando International, Tampa and Jacksonville traffic stayed close to normal, 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.

