Calvert County MD / June 17 vote / 2-2 tie / Ireland declined / second counter-signal in 4 days
Calvert County, Maryland's data center moratorium motion failed 2-2 on June 17 when Commissioner Hance was absent and Board President Ireland declined to vote — Commissioners Cox and Grasso voted yes on scheduling a July 7 work session to draft moratorium language, Commissioner Hart voted no, and the tie killed the motion despite a citizen petition with ~9,000 signatures and two pending data center projects (Amazon Web Services and Natelli Holdings, both in the Lusby area)
Plain-English version of the procedural detail. Calvert County is a five-member Board of County Commissioners. On any given vote, three yes votes are needed to pass. With one commissioner absent and one declining to vote, the math is brutal — even if the remaining three had all voted yes, the motion would have passed 3-1 with one abstention, but a 2-2 tie automatically kills the motion under Maryland local government procedure. The motion itself was procedural, not substantive. It called for scheduling a July 7 work session at which moratorium ordinance language would be drafted, followed by a July 28 public hearing once the legal notice requirements had been met. It was the planning-and-zoning step that has to happen before any actual moratorium vote. The Ireland 'decline to vote' is the most procedurally interesting part. In most county commission rules, declining to vote (rather than voting no) is a softer signal — the commissioner can say publicly they have not opposed the moratorium itself, but a decline-to-vote on a tied motion is mathematically identical to a no vote: the motion fails either way. In a public-facing record, however, it gives the commissioner cover to defend that they did not vote 'against the citizens.' This is a procedural pattern worth flagging because it is starting to recur across moratorium votes — the board president as the tiebreaker who declines to break the tie. Projects in play. Amazon Web Services and Natelli Holdings each have proposed data center developments in Lusby, in the southern half of the county. Both will now proceed through the existing standard development approval process, which includes site plan review, public input opportunities, and the regular planning-and-zoning permitting steps — but without the additional pause-and-restudy layer the moratorium would have inserted. The ~9,000 citizen petition. The petition was started by the 'Save Calvert' coalition. The county population is roughly 95,000 — so ~9,000 signatures is approximately 9-10% of the total population (and a higher percentage of the registered voter base). That is a structurally similar percentage to the hearing-attendance percentages flagged for earlier streak jurisdictions (Luther OK at ~23%, Imperial County CA, etc.), but it expressed itself as a petition rather than a hearing turnout and it still failed to produce a majority on the board.
Southern Maryland Newspapers Online (somdnews.com) ↗
Why it matters
Two corpus implications. (1) The streak narrative needs to be rewritten as 'streak with two narrow exceptions' rather than 'unbroken pause wave.' The strategic question for a developer is no longer 'is my jurisdiction in a pause cycle yes/no' — it is 'does my project remove the politically salient opposition issue, and is the local board procedurally positioned to act?' Those are two different sub-questions and the corpus should be answering both, per project. (2) The 'declined to vote' procedural move is worth tagging as a database field in its own right. If the same procedural pattern recurs across jurisdictions (board president declines to break a tie on a moratorium motion, which mathematically kills the motion but leaves the president politically defensible), that is a reliable late-stage off-ramp from the moratorium wave, and it should be tracked separately from a normal yes/no vote breakdown. The query 'show me every moratorium failure that ran through a procedural off-ramp rather than a substantive defeat' is the right cut for a developer trying to time site approval submissions to a board whose composition rules out a clean majority either way.