The Quanfinity Project
The Anomaly Files  ·  Installment I of III  ·  Signal & Noise Series
⚠   Investigative Content — All Claims Tiered by Evidence Standard — Read Editorial Note Before Proceeding   ⚠
The Anomaly Files — Part I

The Booms

What rattled the country from California's Central Coast
to South Carolina to Boston in a single week —
and why no one in charge has a complete answer
Published: May 2026  ·  Series: The Anomaly Files  ·  The Quanfinity Project
Evidence Standard: C1–C3 / LI / OA / ND  ·  Status: Initial Report — Ongoing
Editorial Standards Declaration. This report applies The Quanfinity Project's full six-tier evidence standard. C1 — Primary source (government record, official statement, court filing). C2 — Named credentialed journalism (AP, Reuters, CNN, CBS, NBC, major regional). C3 — Single-source or unverified; requires corroboration. LI — Logical inference from established facts; not independently confirmed. OA — Open architecture; speculative based on available pattern. ND — Officially denied by named agency or official. All claims are explicitly labeled. No claim in C3, LI, or OA tiers should be treated as established fact. This report does not allege wrongdoing by any individual or agency beyond what the public record supports.
C1 — Verified Primary source / official record
C2 — Credible Major named-source journalism
C3 — Unverified Single source; needs corroboration
LI — Inference Logical, not independently confirmed
OA — Speculative Open architecture; pattern-based
ND — Denied Officially denied by named source

Between May 26 and May 30, 2026, sonic booms rattled communities from California's Central Coast to South Carolina to Boston. Some had a known source. Others did not. None received the coordinated public response the scale of the events warranted. They were the latest entries in a statistically anomalous surge that began in January and has yet to peak.

Section I

Five Days. Three Regions. A Spectrum of Answers.

The week began on California's Central Coast.

On the morning of May 26, 2026 — the same day a tank imploded at a paper mill in Longview, Washington, killing eight workers — a SpaceX Falcon 9 rocket lifted off from Space Launch Complex 4 East at Vandenberg Space Force Base in Santa Barbara County. It was the 35th Vandenberg launch of 2026. Residents across Cambria, Morro Bay, San Luis Obispo, Santa Barbara, and Ventura counties reported hearing the characteristic double sonic boom as the booster returned to Earth. For many, it was not the first time. For some, it was still alarming.

C1 — Verified: SpaceX / Edhat / Spaceflight Now — May 26, 2026
SpaceX's Starlink 17-37 mission lifted off from Vandenberg at 7:50 AM PDT on May 26, 2026 — Vandenberg's 35th launch of the year. Officials acknowledged in advance that residents of Santa Barbara, San Luis Obispo, and Ventura counties might hear one or more sonic booms during the launch and booster return, depending on weather and atmospheric conditions. The booster — on its sixth flight — landed on the droneship "Of Course I Still Love You" in the Pacific Ocean. A follow-up launch from Vandenberg was scheduled for May 30. Reports of double booms across Cambria, Morro Bay, SLO, and surrounding communities are consistent with the characteristic double crack produced by Falcon 9 booster reentry.

The California booms had a name. They had a source. They had a company that warned residents they were coming — and a research program, ECOBOOM, actively studying their impact on communities and wildlife. What they did not have was a meaningful mechanism for residents who had not consented to have their homes shaken at increasing frequency to do anything about it. That is a separate accountability story, addressed in full in Section IV.

Two days later, a very different kind of boom arrived — this one with no name, no source, and no agency prepared to explain it.

On the afternoon of Thursday, May 28, 2026, residents across the South Carolina Midlands heard something they won't soon forget. The sound arrived without warning — a pressure wave that hit people in the chest before the boom registered in the ears. Windows shook. Cameras jolted. Pets fled. Within minutes, hundreds of reports flooded into the U.S. Geological Survey's self-reporting system, most describing what residents assumed was a significant earthquake.

It was not an earthquake.

C1 — Verified: U.S. Geological Survey Official Statement
The USGS confirmed the event was not seismic. Recorded waves and eyewitness reports were consistent with a sonic boom. Because earthquake magnitude scales are calibrated for seismic waves traveling through the earth, standard magnitude methods do not apply; the event was manually assigned a magnitude of 0.0. The USGS estimated the boom originated approximately six kilometers north-northwest of St. Andrews, South Carolina.
C1 — Verified: Military Denials — Three Bases
Shaw Air Force Base, Fort Jackson, and McEntire Air National Guard each issued statements confirming the boom did not originate from any military operation. Shaw's chief of public affairs, Captain James Stewart, stated: all flying operations had concluded before the time of the occurrence.
C1 — Verified: NASA Statement
NASA confirmed the boom was not caused by a NASA launch or a meteor detected by NASA monitoring systems.

That sequence of denials is itself remarkable. In a span of hours on May 28, 2026, the federal government's relevant agencies publicly ruled out the three most common explanations for a large sonic boom — seismic event, military activity, and space agency activity — and offered no alternative explanation.

"It felt like someone shoved me right in my chest an instant before the boom began."
— Meteorologist Chris Jackson, reporting from South Carolina at the time of the event  ·  C2

Two days later, on Saturday, May 30, 2026, a second event — this one dramatically larger — rattled New England.

C1 — Verified: NASA / American Meteor Society — Boston Event, May 30
NASA confirmed a fireball over New England at approximately 2:06 PM EDT, traveling at roughly 75,000 miles per hour. The object — confirmed to be a natural meteor, not space debris or a satellite — fragmented at approximately 40 miles above extreme northeast Massachusetts and southeast New Hampshire. NASA calculated the energy released at the equivalent of approximately 300 tons of TNT. The American Meteor Society received reports spanning Delaware to Montreal. The object was approximately three feet wide — definitively identified as a bolide meteor.

The Boston event, unlike the South Carolina boom, has a confirmed, documented, scientifically verified explanation. A space rock entered the atmosphere, compressed air ahead of it at hypersonic speed, and detonated. Case closed — at least on mechanism.

The South Carolina event does not enjoy the same clarity.

Section II

The Surge: A Statistically Anomalous Year

To understand the May events in proper context, the reader must understand what has been happening since January. These booms did not begin in South Carolina. They are the most recent entries in what the American Meteor Society has formally identified as a statistically extraordinary surge in large fireball events — one that began in the first quarter of 2026 and has continued without scientific explanation.

C1 — Verified: American Meteor Society — Q1 2026 Formal Analysis
In a March 2026 formal report, the AMS documented 2,046 total fireball events in Q1 2026. Of those, 38 events had more than 50 reports each — against a historical average of 18 per quarter at that threshold. The 50+ witness threshold was running at double the historical average. At the most diagnostic measurement level, Q1 2026 sits 3.9 standard deviations above the 2018–2025 baseline — statistical odds of approximately 1-in-21,000 by chance alone. The AMS stated: "What this is, is a measurable change in the AMS fireball data that we do not yet fully understand."

Documented Events: January–May 2026

Date Location Event Official Status Tier
Mar. 8 Germany / France Daytime bolide — 3,229 witnesses across two countries Confirmed: meteor C1
Mar. 17 Ohio / Pennsylvania 7-ton, 2-meter asteroid; 250-ton TNT airburst; 222 reports across 16 states Confirmed: meteor C1
Mar. 21 Houston, TX 1-ton meteoroid airburst; 26-ton TNT; fragment through roof of residence Confirmed: meteorite impact C1
Mar. 23 California (×2) Two separate fireballs same day; 306 + 122 reports Confirmed: meteor C1
Mar. 24 Michigan / Georgia Two additional fireballs; 111+ reports Confirmed: meteor C1
May 26 Cambria, Morro Bay, SLO County, Santa Barbara, Ventura — CA Central Coast Double sonic boom from SpaceX Falcon 9 Starlink 17-37 launch and booster return; Vandenberg's 35th launch of 2026; reports across multiple Central Coast communities Confirmed: SpaceX Vandenberg launch C1
May 28 Columbia, SC Large sonic boom; 5:24 PM; hundreds of reports across multiple counties UNRESOLVED — all agencies denied C1 / ND
May 30 Boston, MA Bolide explosion; 300-ton TNT; reports Delaware to Montreal Confirmed: bolide meteor C1
C2 — Credible: AMS Analysis — Space.com, AccuWeather, EarthSky (March 2026)
AMS fireball monitor Mike Hankey noted that roughly 30 large fireball events producing audible booms occurred in a single quarter — approximately one every three days. The rate is elevated in both absolute count and rate simultaneously. Multiple analysts noted the daytime fireballs over Germany and Ohio originated from different parts of the sky on unrelated orbits, ruling out a single parent object or debris stream as the source of the entire cluster.
◉   Signal — What Is Confirmed
◈   Noise — What Remains Unknown
  • Double sonic booms rattled Cambria, Morro Bay, SLO County, Santa Barbara, and Ventura counties on May 26 — confirmed as SpaceX Falcon 9 Starlink 17-37, Vandenberg's 35th launch of 2026
  • A statistically anomalous surge in large fireball events began in Q1 2026 and has continued
  • The Boston May 30 event is a confirmed bolide meteor — 300 tons TNT equivalent
  • The Texas March 21 event is a confirmed meteorite impact — fragment recovered from a home
  • The South Carolina May 28 event produced a confirmed sonic boom, verified by USGS instrumentation
  • All three military bases near Columbia, SC denied involvement in the May 28 event
  • NASA denied the May 28 event was related to any NASA activity or a detected meteor
  • The AMS received a video showing a contrail near the May 28 event — no fireball visible
  • California Central Coast residents have no meaningful regulatory recourse despite documented, escalating boom frequency — SpaceX is actively suing the agency that reviews coastal impacts
  • The cause of the South Carolina May 28 boom has not been officially identified as of publication
  • The SC contrail may indicate a supersonic aircraft — but aircraft are prohibited from breaking the sound barrier over most domestic airspace, and all bases denied activity
  • The underlying cause of the Q1 2026 fireball surge is scientifically unresolved — the AMS stated it does not yet fully understand it
  • Whether the SC boom was meteor, classified aircraft, or another source entirely remains an open question — all agencies point away from their own involvement
Section III

The Response Gap: What Agencies Said, and What They Didn't

In a well-resourced, well-funded public safety infrastructure, a sonic boom of the magnitude recorded on May 28, 2026 — large enough to rattle homes across multiple South Carolina counties, register on USGS seismographic instruments, and be felt as a pressure wave in people's chests — would produce a rapid, coordinated, and transparent agency response. What the public received instead was a cascade of denials from agencies pointing away from their own jurisdictions, with no agency pointing toward an answer.

What Was Said
  • USGS: "Not an earthquake. Consistent with sonic boom."
  • Shaw AFB: No activity from this base contributed.
  • Fort Jackson: No activity from this base contributed.
  • McEntire ANG: No activity from this base contributed.
  • NASA: Not a launch. Not a detected meteor.
  • AMS: Received a contrail video; no fireball visible.
What Was Not Said
  • No agency identified what actually caused the event.
  • No agency coordinated a joint public response.
  • No follow-up investigation timeline was announced.
  • No federal emergency coordination was triggered.
  • No agency confirmed or denied the involvement of classified aircraft.
  • The public was not told what to expect if it happens again.
LI — Logical Inference
When every agency with a plausible explanation denies responsibility, one of three conditions exists: (1) the event was caused by something genuinely unknown — an undetected natural object entering the atmosphere under conditions that defeated monitoring systems; (2) the event was caused by a classified program that responding agencies are not authorized to confirm or deny; or (3) the event is still being investigated and agencies are awaiting confirmation before public disclosure. The public record, as of publication, does not permit distinguishing between these three possibilities. Each is consistent with the available evidence.

The Funding and Infrastructure Context

The response gap described above does not exist in a vacuum. It exists within a policy environment that has systematically reduced the capacity of the agencies responsible for detecting, analyzing, and communicating about precisely these kinds of events.

C1 — Verified: Federal Agency Cuts — 2025–2026
The National Oceanic and Atmospheric Administration (NOAA) has faced workforce reductions and budget constraints under the current administration's broader federal agency restructuring efforts. The U.S. Geological Survey — the agency that detected and reported the South Carolina sonic boom — operates monitoring infrastructure that its own scientists have noted is not calibrated to characterize sonic boom events. The EPA's enforcement capacity has been reduced through staffing and budget adjustments in fiscal years 2025 and 2026.
C2 — Credible: USGS Statement on Monitoring Limits
In its official notice regarding the South Carolina event, the USGS explicitly acknowledged: "its equipment is not calibrated to measure the magnitude of such an event." The agency assigned a magnitude of 0.0 — not because the event was small, but because the agency's own standards do not apply to sonic boom events. This is an infrastructure gap, not a measurement of the event's actual force.
LI — Logical Inference
An agency whose instruments are acknowledged by that agency to be uncalibrated for the event it is detecting cannot produce a complete public accounting of that event. The gap between what happened on May 28, 2026 and what the public was told is partly a function of what agencies were equipped to detect and characterize — and that equipment gap is at least partially a function of resource and priority decisions made before May 28.
Section IV

California: Named Source, Unresolved Accountability

In Cambria — the small coastal community in northern San Luis Obispo County, population roughly 6,000, known for its Monterey pines and Pacific views — residents heard the double boom on the morning of May 26, 2026. In Morro Bay, in the city of San Luis Obispo, in communities across Santa Barbara and Ventura counties, the same double crack rattled windows, startled animals, and sent residents reaching for their phones. Some knew immediately what it was. Others did not. Many who knew were still unsettled.

This is the 35th time it has happened this year from this base alone.

C1 — Verified: Vandenberg Launch Record / SpaceX / Edhat, May 26, 2026
The Starlink 17-37 mission on May 26 was Vandenberg Space Force Base's 35th launch of 2026. A follow-up launch was confirmed for May 30, with additional missions scheduled for June 3 and June 10. Vandenberg ended 2025 with a record 52+ launches — up from 51 in 2024. SpaceX has stated plans for more than 90 Vandenberg launches in 2026. The ECOBOOM program — a joint research initiative between Vandenberg, Brigham Young University, and California State University Bakersfield — has tracked sonic booms from launches using eight monitoring stations across Santa Barbara and Ventura counties, collecting 477 acoustic recordings across 23 launches by January 2026 alone.

The Double Boom: What Communities Are Experiencing

The characteristic "double boom" residents across the Central Coast hear results from the Falcon 9 first-stage booster returning to Earth after stage separation. As the booster decelerates from hypersonic speeds, it generates two distinct shock waves — one from the nose, one from the base — that reach the ground in rapid succession. When the booster returns to Landing Zone 4 at Vandenberg, residents nearby hear both. When it lands on a droneship at sea, as with the May 26 mission, the booms still propagate inland depending on atmospheric conditions.

C2 — Credible: LA Times / Air Force Disclosure to California Coastal Commission
The Air Force formally acknowledged to the California Coastal Commission that sonic booms from Vandenberg launches regularly rattle a large swath of Southern California — a fact Space Force officials had previously downplayed. Recent changes in flight trajectories due to Starlink orbital mechanics have shifted boom patterns closer to the coast, expanding the affected area from northern Santa Barbara County southward into Ventura and northern Los Angeles counties. The commission's staff report documented a launch on April 2, 2023, after which dead harbor seal pups were found — potentially trampled by other seals fleeing the boom. SpaceX subsequently sued the Coastal Commission after it denied plans to increase launches to 50 per year. Those launches have continued anyway — at a rate now approaching 90 per year.
"One time, I thought a car hit my house. It's felt by everyone. We hear the boom. My dog freaks out."
— Camarillo resident Mikayla Shocks, speaking to the Los Angeles Times  ·  C2
LI — Logical Inference
The California Central Coast boom story and the South Carolina and Boston stories share a structural feature that is worth naming explicitly: in all cases, the public is experiencing the acoustic and physical consequences of large-scale activity — commercial space launches in California, unidentified atmospheric events on the East Coast — for which existing public communication, regulatory, and detection infrastructure is demonstrably inadequate. In California, residents know what is causing the shaking but have limited recourse. In South Carolina, residents don't know what caused the shaking and have received no follow-up. In Boston, residents know — but had no warning. The common thread is not the source of the boom. It is the gap between what happened and what the public was told, prepared for, or offered by way of accountability.
C1 — Verified: SpaceX Litigation Against California Coastal Commission
SpaceX filed suit against the California Coastal Commission after the commission denied the company's application to increase annual launches from Vandenberg. Despite the litigation, launch frequency has continued to increase. The commission has no authority to halt federal space launches; it can only condition the permitting of coastal development associated with them. The practical effect is that Central Coast communities bear the acoustic impact of launch frequency growth while the regulatory mechanism designed to protect their coastline is simultaneously under legal attack by the company generating that impact.
Section V

What the Record Permits Us to Say

This report does not claim to know what caused the South Carolina boom on May 28, 2026. Neither do the agencies responsible for knowing. That is the point.

What the record permits us to say — with evidence-tier confidence — is the following:

C1 — Verified: Confirmed Factual Findings
1. Double sonic booms from SpaceX's 35th Vandenberg launch of 2026 rattled Cambria, Morro Bay, SLO County, Santa Barbara, and Ventura counties on May 26, 2026. The source was identified. The community impact was real and ongoing. The regulatory mechanism designed to address it is under active litigation by the company causing it.

2. A large sonic boom struck South Carolina on May 28, 2026. It was real, widespread, and instrumentally recorded. It remains officially unexplained.

3. A confirmed bolide meteor exploded off the Massachusetts coast on May 30, 2026, equivalent to 300 tons of TNT. It was the second such event in six weeks to produce widely heard sonic booms across multiple states.

4. The American Meteor Society has formally documented a statistically anomalous surge in large fireball events in 2026 — 3.9 standard deviations above the historical baseline, with odds of occurring by chance of approximately 1-in-21,000.

5. The USGS's own instruments are acknowledged to be uncalibrated for sonic boom characterization. No federal agency has announced plans to improve this capacity.
LI — Logical Inference: The Pattern
The convergence of a statistically anomalous increase in atmospheric events, the absence of coordinated federal response infrastructure, and a policy environment that has reduced agency capacity rather than expanded it creates a foreseeable public safety gap. Whether the South Carolina boom was natural, classified, or something else entirely — the gap between what happened and what the public was told is a documented, verifiable failure of public information infrastructure. That failure is not speculation. It is the record.
OA — Open Architecture: Questions the Record Does Not Yet Answer
— What caused the South Carolina boom? No agency has answered this question.

— Does the 2026 fireball surge represent a temporary anomaly in Earth's near-space environment, or a trend line? The AMS has stated it does not yet fully understand the cause.

— Are classified aircraft or programs responsible for any of the domestic sonic boom events for which no public explanation has been offered? The record is silent.

— At what point does the frequency and intensity of unexplained atmospheric events constitute a public safety communication obligation? No threshold has been established by any federal agency.
◈   Open Dockets — Active Questions as of Publication
Docket 01
The cause of the May 28, 2026 South Carolina sonic boom remains officially unidentified. No agency has announced an investigation timeline or follow-up disclosure. Status: Open.
Docket 02
The American Meteor Society's documented Q1 2026 fireball surge — 3.9 standard deviations above baseline — has received no coordinated federal scientific response. No interagency working group, no congressional hearing, no public briefing has been announced. Status: Open.
Docket 03
The USGS's acknowledged limitation — instruments uncalibrated for sonic boom characterization — has not been addressed by any announced budget, program, or policy change. Status: Open.
Docket 04
SpaceX's litigation against the California Coastal Commission — filed after the Commission denied the company's plan to increase Vandenberg launches to 50 per year — is ongoing. Vandenberg is now projected to host 90+ launches in 2026. Central Coast communities including Cambria, Morro Bay, and SLO County continue to bear the impact with no effective regulatory remedy. Status: Litigation pending; launches continuing.
Docket 05
The broader 2026 fireball surge continues. As of publication, additional fireball events have been reported in New England and potentially elsewhere. The AMS has not issued an updated analysis post-May 30. Status: Ongoing / Developing.
Closing Note

Rights Without Limit Includes the Right to Know

The Quanfinity Project does not traffic in fear. We do not claim to know what caused the South Carolina boom. We do not assert that the fireball surge is evidence of anything beyond what the American Meteor Society's own data shows — which is itself extraordinary enough to warrant serious public attention.

What we assert — based solely on the public record — is this: in the same week that residents of Cambria, Morro Bay, and San Luis Obispo County were rattled for the 35th time this year by booms from a commercial space company actively litigating against the only regulatory body that reviews its coastal impact, residents of South Carolina were struck by a boom that no agency has explained, and residents of Boston were struck by a space rock equivalent to 300 tons of TNT that no one warned them about.

Three different events. Three different sources — one known, one unknown, one confirmed. One common thread: in each case, the gap between what happened and what the public was told, prepared for, or offered by way of accountability was wider than it should be.

In a functioning public information infrastructure, that gap closes. The question this report leaves open — and that The Anomaly Files will continue to examine — is whether the infrastructure capable of closing it still exists.

"What this is, is a measurable change in the AMS fireball data that we do not yet fully understand."
— American Meteor Society, Q1 2026 Formal Analysis  ·  C1
Sources & Bibliography
01
U.S. Geological Survey. Official Sonic Boom Event Notice — South Carolina Midlands. May 28, 2026. Primary record. C1
02
WLTX News 19 / WBTV / WMBF / WIS. Multiple reports on SC boom — agency responses, expert interviews, resident accounts. May 28–29, 2026. C2
03
CBS Boston / NBC Boston / Boston Globe / CNN. Massachusetts meteor coverage. May 30, 2026. C1/C2
04
American Meteor Society. Q1 2026 Fireball Surge Analysis. Published March 25–26, 2026. amsmeteors.org. C1
05
NASA Jet Propulsion Laboratory / NASA official statements — Houston meteor (March 21), Massachusetts meteor (May 30). C1
06
AccuWeather / Space.com / EarthSky. Fireball surge analysis — expert commentary. March–May 2026. C2
07
Ars Technica. "Falcon 9 sonic booms can feel more like seismic waves." May 2025. ECOBOOM program research documentation. C2
08
Los Angeles Times. Vandenberg sonic boom residential impact reporting. 2024–2026. California Coastal Commission staff reports. C2
09
College of Charleston, Dr. Erin Beutel — atmospheric pressure instrumentation analysis, SC boom. Quoted by WLTX News19, May 29, 2026. C2
10
Shaw Air Force Base — Captain James Stewart, Chief of Public Affairs. Official denial statement. May 28–29, 2026. C1
11
Edhat Santa Barbara. SpaceX Vandenberg 35th mission of 2026 — Starlink 17-37. May 26, 2026. edhat.com. C1/C2
12
Spaceflight Now. Starlink 17-37 mission launch record, May 26, 2026. spaceflightnow.com. C1
13
NBC Palm Springs. SpaceX Vandenberg launch advisory — Santa Barbara, SLO, Ventura county sonic boom notice. May 25–26, 2026. C2
The Anomaly Files — Series Navigation
Part I — Published The Booms
Part II — Published The Fires
Part III — Published The Vanishing
Part IV — Published The Credibility Gap
The Anomaly Files — Part I: The Booms  ·  The Quanfinity Project  ·  Page 1 of 4  ·  May 2026
The Quanfinity Project Rights Without Limit  ·  Bringing Light to Darkness, Ignorance to Wisdom
thequanfinityproject.org  ·  Signal & Noise Series
All claims evidence-tiered. All inferences labeled. All speculation marked.
This document may be shared freely with attribution.