Datacenter regulatory-trace changes as of August 21, 2026

As of 2026-08-21, 9 of the 57 tracked announced sites had a changed phantom score, or entered the baseline, in this published comparison.

Compared with the immediately preceding sealed source report dated 2026-08-20. The score reports how much trace was observed in bounded public air-permit and FAA airspace sources. A higher score is a diligence prompt, not a verdict about whether a datacenter will be built.

479permit applications in the source snapshot
26,306non-terminal FAA cases observed nationally
8.0 kmfixed airspace join radius

Sites that define this dated page

Announced sitePrior scoreCurrent scoreObserved trace
AWS Richmond County Campus (Energy Way Industrial Park)
Amazon · Hamlet, Richmond County, NC
5030FAA cases within 8.0km x1
Google Columbus Data Center
Google · Columbus, OH
5020FAA cases within 8.0km x3; active construction (0 crane cases)
Google Kansas City (East)
Google · Kansas City, MO
3020FAA cases within 8.0km x3; active construction (1 crane cases)
Google Mesa Data Center
Google · Mesa, AZ
2050No bounded trace observed
Google West Memphis Campus (Groot LLC)
Google · West Memphis, AR
3020FAA cases within 8.0km x1; active construction (1 crane cases)
QTS Richmond (White Oak) Campus
QTS · Sandston, Henrico County, VA
5020FAA cases within 8.0km x3; active construction (2 crane cases)
Stargate Abilene (Crusoe/Lancium campus)
OpenAI/Oracle/Crusoe · Abilene, TX
300air-permit match x2; technically-complete stage; stagnant application >203d still administrative; FAA cases within 8.0km x1; active construction (1 crane cases)
Stargate Milam County (SB Energy)
OpenAI/SB Energy (SoftBank) · Rockdale/Milam County, TX
3010air-permit match x2; technically-complete stage; stagnant application >203d still administrative; FAA cases within 8.0km x1
Stargate Project Jupiter (STACK/BorderPlex)
OpenAI/Oracle/STACK Infrastructure · Santa Teresa, Doña Ana County, NM
2030FAA cases within 8.0km x1

Rows not shown retained the same score and are intentionally omitted. That keeps this page about what changed instead of reproducing a 57-row table every day. Score bands are heuristic and depend on coverage: TCEQ pending applications cover Texas, while the FAA case layer is national. An issued permit, a local permit outside the collected sources, or construction that needs no sampled FAA filing can all be absent from this view.

Method, source, and content seal

The August 21, 2026 comparison is derived from public records published by TCEQ and the FAA Part 77 archive. The scorer joins those bounded records to publicly announced site locations. Name-token matches that are merely contextual do not count as direct permit evidence. Distance matches use the fixed radius shown above. The method does not infer power, capacity, financing, completion, or operator intent.

The August 21, 2026 source artifact reproduced its declared SHA-256 seal before this response was rendered. The seal excludes only the machine-local database path; dates, source counts, site rows, scores, and reasons remain bound.

SHA-256: 72a1965634dd478075198f9a01eff69a338b5558b1a6ee17bc13370ac338e939

Need the decision brief, not just the public evidence?

The archive is the proof layer. The Datacenter Materialization Watch turns the same two signals into a fixed monthly diligence deliverable for site-selection and infrastructure teams. Terms and coverage are on the archive hub.

See the watch offer