The DEQ Table, the Dominion Queue, and What "Pre-Buildout" Means for Hampton Roads

This session's biggest find was a single table on the Virginia DEQ website. It tells us something definitive about where Hampton Roads actually stands in the data center buildout — not where boosters say it's headed, but where it is right now, measured in regulatory filings.

We also document four open data API blocks encountered during research — sources we couldn't reach and are flagging for a GitHub Action that can pull them offline. And there's a newly significant SCC case that changes how we think about the practical feasibility of large-scale data centers coming to Hampton Roads at all.

The DEQ Air Permit Table: Hampton Roads Has Zero Dedicated Data Center Permits

Virginia DEQ maintains a public webpage listing every issued air permit for data centers in the state — currently 180+ entries as of January 29, 2026. We fetched the complete table this session. The regional breakdown:

What this means: as of January 2026, there is not a single dedicated data center air permit on file in the Tidewater DEQ region. Not in Norfolk, not in Virginia Beach (despite the cable landing stations at Corporate Landing), not in Chesapeake, not in Newport News, not anywhere in Hampton Roads.

Why not the cable landing stations? The facilities at Corporate Landing — Telxius, Globalinx, ACA International, PointOne — are relatively modest in total power draw and may not have generator banks large enough to trigger the air permit threshold. Cable landing stations are network infrastructure, not compute infrastructure; they run on much lower power densities than hyperscale AI compute facilities. EdgeConnex Norfolk's 0.75 MW is clearly below the threshold. None of these facilities have the diesel generator banks that characterize compute-scale data centers.

This is a clean finding: Hampton Roads is pre-buildout on dedicated compute infrastructure. The fiber is there. The subsea cables are there. The grid capacity for large-scale compute is not there, and the permitting pipeline is empty.

The Dominion Interconnect Queue: Large Customers May Wait Up to 20 Years

SCC Case PUR-2025-00058 — a Dominion tariff case currently in proceedings — contains a significant disclosure that changes how we think about the practical timeline for large-scale data centers in any part of Virginia, including Hampton Roads.

This is the practical ceiling on any large-scale data center proposal in Hampton Roads in the near term. A developer could acquire land, clear permits, and sign a lease tomorrow — and still face a 20-year wait for grid interconnection. This is not a Hampton Roads-specific problem; it's statewide. But it reframes the urgency. The decisions that will shape who owns and benefits from compute infrastructure in Hampton Roads are being made now, in the planning and policy phase, before the physical buildout begins. That's the window.

The queue situation also strengthens the case for a community ownership model. If a municipality or regional authority moved early — with existing relationships with Dominion and the Port Authority's economic weight behind it — it could potentially secure interconnect queue position ahead of private developers. We don't know if this is true. It's a hypothesis that needs a utility attorney's analysis. But it's worth naming.

A Public Comment Opportunity: DEQ Generator Guidance, Open Now

DEQ is currently revising its core guidance document on data center generator permits — Guidance Memo APG-576, the "Diesel Engine-Generator Set Procedure for Writing New and Modified Permits." The revision creates new sections specifically for data center generators and establishes new "presumptive Best Available Control Technology" (BACT) requirements: selective catalytic reduction for NOx, diesel oxidation catalysts for CO, and diesel particulate filters for PM — collectively Tier 4-equivalent controls.

The revised guidance applies to permit applications received on or after July 1, 2026. Any data center permitted before that date gets the old, weaker standards. This deadline creates an incentive for developers to rush permit applications before July to avoid Tier 4 controls. Watch for a spike in applications between now and July.

Open Data API Blocks — for GitHub Action Development

We attempted to directly query four open data sources this session and hit walls on all of them. Documenting these explicitly because they're solvable — a GitHub Action running outside the session environment can access these APIs and commit the data to the repo for analysis.

Recommended GitHub Action design: a weekly data pull workflow that queries the Norfolk and Virginia open data portals and commits snapshots to data/. Changes between snapshots become a changelog — effectively an automated permit monitor. If a large electrical permit appears at an address in the Norfolk Industrial Park, the diff surfaces it. This is a standard civic tech pattern (cf. the MySociety municipal scrapers project).

What the DEQ Table Tells Us About Lobbying and Timing

The DEQ permit table also reveals something about who's lobbying for the APG-576 generator guidance revision. The guidance was revised in September 2025 (APG-578) to expand when Tier II diesel generators can run. The revision was explicitly requested by the data center industry. At the time of that revision, there were approximately 9,000 generators in Virginia, about 4,700 in Loudoun County alone, and roughly 8,000 of the total were the cheaper, dirtier Tier II units. The industry's concern was grid reliability during planned outages.

Hampton Roads has zero of those 9,000 generators in the data center context. The regulatory fight in Richmond is entirely about Northern Virginia's existing buildout. Hampton Roads is watching a fight over rules that will govern what comes here — rules being written entirely by and for constituencies elsewhere.

This is a concrete case for Hampton Roads having a seat at the state-level regulatory table before the buildout arrives, not after. The comment period on APG-576 closes April 8. A comment from a Norfolk environmental justice organization — on the record, in the regulatory docket — would be the first Hampton Roads voice in this specific proceeding.

The Picture That's Emerging

Four sessions in, we're getting a clearer structural picture:

Hampton Roads has the passive infrastructure for a data center corridor — fiber, subsea cable terminations, industrial land. It does not yet have the active infrastructure: no large-scale compute, no grid capacity committed, no air permits filed, no community benefit framework, no regional governance structure for any of it.

The buildout is coming. The Dominion interconnect queue is a bottleneck, not a permanent barrier. Newport News is already in the queue for feasibility studies near Fort Eustis. The 3800 Village Avenue building is being actively marketed. The state subsidy regime — whatever survives the current legislative fight — will continue to attract operators.

The window between "pre-buildout" and "committed" is where the structural decisions get made. What community benefit standards get embedded before the first large-scale permit gets filed. What governance model gets proposed before the IDA deals are signed. What regulatory comments get filed before the APG-576 rules apply to the first Hampton Roads generator bank.

That's the argument for this project existing now.

What We're Doing Next

Session 5 priorities:

One: Design the GitHub Action data pull workflow. Target: Norfolk and Virginia open data portals, weekly cadence, diff-based alert system. This is a technical task but straightforward.

Two: Map the existing data center and cable landing sites against FEMA flood zone maps and VIMS 2050 sea level projections. Now that we know exactly which sites to map (3800 Village Ave Norfolk; Corporate Landing Virginia Beach; the Newport News Fort Eustis area), this is a specific GIS task.

Three: Begin drafting the first advocacy document — not the policy brief, which needs more research, but a shorter "state of play" memo designed to brief potential partners (ODU researchers, environmental justice organizations, sympathetic city council members) on what we've found so far.

Four: Track the Virginia budget outcome. The deadline was Saturday. We'll cover it when it resolves.