Did anyone else notice the FAA flight restrictions that popped up over that Nevada site last month?

So I've been down this rabbit hole for the past week and honestly the timing is suspicious as anything. The restrictions went up with basically zero public explanation and then quietly disappeared again - if that doesn't scream ". Something happened out there" I don't know what does.

I pulled the FAA NOTAM data and cross-referenced it with some of the ADS-B Exchange logs from around the same period. There's a gap in commercial flight paths that you just don't see unless someone's actively pushing traffic away from an area. Not a weather thing, not a scheduled exercise as far as I can tell.

What gets me is the shape of the restricted zone. It wasn't a standard circular TFR like you'd get for a VIP movement or a wildfire. The boundaries were weirdly irregular, almost like they were containing a specific ground area rather than just protecting airspace.

A few things I want to know:

Has anyone with better OSINT tools than me (genuinely just working with free resources here) managed to pull satellite imagery from that window?, Did anyone notice any unusual military transport activity at Nellis or Creech around the same dates?, Are there any local Nevada residents on here who noticed anything on the ground?

I know some of you will say this is just routine and I'm pattern-matching into nothing. Maybe. But we've seen this exact playbook before - restricted airspace, no explanation, memory-holes itself after a few days. Feels very familiar to some of the pre-announcement activity people documented before the 2019 UAP disclosures.

What have you lot actually managed to dig up on this?

@CuriousOwl nothing says ". Nothing to see here". Quite like literally making it illegal to see here.

Worth noting that FAA TFRs over Nevada aren't automatically sinister - they do get issued routinely for military exercises, VIP movements, even wildfire suppression. The key thing to check is the NOTAM classification. A [4/5] security TFR reads very differently to a standard [0/1] airspace management one.

What I'd actually want to know:

Exact coordinates (did it overlap with Groom Lake or was it adjacent?), Duration - hours vs. days changes the interpretation massively, Whether any ATIS frequencies showed unusual activity during that window

@CuriousOwl which tracking service flagged it? FlightAware sometimes strips context that you'd catch on ADS-B Exchange. The absence of traffic data can occasionally tell you more than the restriction itself.

Suspicious timing is worth investigating properly rather than assuming. What specific dates are we talking?

@SnappySeeker makes a fair point about routine TFRs, but the detail worth digging into here is the classification code attached to the restriction. Standard military exercise TFRs typically sit under 14 CFR 91.137 or 91.141 - they're identifiable, predictable, and usually pre-announced via NOTAM with reasonable lead time.

What @CuriousOwl is describing sounds more like a snap restriction with minimal NOTAM window. That's the tell. I'd suggest pulling the archived NOTAM data from the FAA's public system - it's all still retrievable - and checking the issuing facility code alongside the effective/expiry timestamps.

If it originated from a non-standard facility designator rather than the regional ARTCC, that's your anomaly worth documenting properly. Screenshot everything before it rolls off the archive window. Those records don't stay publicly accessible indefinitely.