When AARO published its Fiscal Year 2025 Consolidated Annual Report on UAP in July, most coverage ran the same headline for a day and moved on: "100 UFOs swarm off Virginia coast." That framing isn't wrong, exactly, but it buries the more interesting fact sitting inside AARO's own numbers — one that none of the day's coverage stopped to dwell on.
Of the 319 UAP reports AARO received in fiscal year 2025, only one was maritime. It's this one. And unlike most of the report's air-domain sightings — which AARO resolved as balloons, birds, drones, or a passing rocket launch — this single maritime case remains open, undated, and, per AARO's own account, short on the sensor data that would let anyone resolve it either way.
What AARO's Report Actually Says
Per AARO's report, as detailed in DefenseScoop's reporting on it, U.S. Navy assets documented "approximately 100 airborne UAP and two, likely uncrewed, surface systems" operating off Virginia's coast. AARO's own statement on the case is brief: "AARO is actively investigating this event in coordination with the reporting unit." No date for the incident is given anywhere in the public reporting. No further description of the objects — size, altitude, behavior, duration — has been released.
The report's broader domain breakdown makes the Virginia case's isolation clear: of 319 total reports, 274 were air domain, 44 were space domain, and exactly 1 was maritime. AARO resolved 114 of the air-domain cases as ordinary objects — "balloons, birds, satellites, aircraft, UAS, and a single instance each of a rocket launch and a manned jet pack," in the report's own words. The Virginia case is not on that resolved list.
-
Total UAP case holdings across all of AARO's records as of May 30, 2025 — not just this fiscal year's 319 new reports.
-
Separate, unrelated cases in the same report where UAP proximity caused documented "electronic or avionic interference" on operational aircraft — a genuinely operational concern, distinct from the Virginia case.
-
AARO's explicit conclusion: no resolved case in the report indicates "advanced foreign adversarial capabilities or breakthrough technologies."
Why Standing Alone Matters
A single maritime case out of 319 isn't itself proof of anything unusual happening off Virginia — AARO simply receives far fewer reports from ships and sailors than from pilots and radar operators, so a low maritime count is expected on its own. What's harder to wave off is the shape of the one maritime report AARO did get: not a lone light on the water, but a reported coordinated event — roughly a hundred airborne objects and two surface vessels, operating together, in the same account. That's a materially different claim than "we saw something in the sky," and it's the only report of that shape anywhere in AARO's 319-case year.
"Likely uncrewed" is doing real work in that sentence, and not the work headlines gave it credit for. AARO's own phrasing hedges on whether the two surface systems were even confirmed to be uncrewed, let alone what built them. Uncrewed surface vessels (USVs) are an increasingly common category of ordinary hardware — used by navies, researchers, and, per open-source reporting on other incidents, by foreign state and non-state actors near U.S. coastlines. "Uncrewed" is not a synonym for "unexplainable."
What This Doesn't Tell Us
An Open Case Is Not the Same as an Unexplainable One
1. "Approximately 100" is an estimate, not a count. AARO's own language hedges on the number. A radar or visual estimate of a busy patch of sky or water can inflate quickly, especially if it includes returns later attributable to birds, buoys, debris, or civilian vessel traffic that simply weren't sorted out before the report was filed.
2. No date means no way to cross-check. Without a specific date, there's no way for outside researchers to check the incident against maritime traffic records, weather data, military exercise schedules, or civilian AIS (ship-tracking) logs — all ordinary tools that have resolved plenty of past "unexplained" sightings.
3. AARO says its own data was insufficient. The report's stated constraint — "a lack of timely and actionable sensor data" — reads less like a hint that something extraordinary evaded detection and more like an admission that whatever was recorded wasn't good enough to work with, which is a mundane and common problem in real-world sensor and reporting pipelines.
4. This case did not make AARO's own "notable" list for exotic technology. AARO's report explicitly states that no resolved case — and this one isn't resolved either way — indicates "advanced foreign adversarial capabilities or breakthrough technologies." That statement covers the report as a whole, this case included.
What to Watch Next
- Whether AARO's FY2026 annual report updates this case's status — resolved, still open, or dropped without explanation, as has happened to older unresolved cases in past reports.
- Whether a specific date or location ever gets attached to it — through a FOIA request, a future PURSUE release, or congressional testimony referencing it by name.
- Whether any of the Navy personnel involved come forward independently — a coordinated ~100-object, two-vessel event would plausibly have been witnessed by more than a handful of people.
The Honest Conclusion
This is a real, government-documented, still-open case — not a leak, not an anonymous claim, and not resolved as anything mundane either. It's also the only entry of its kind in AARO's entire FY2025 dataset, which is worth knowing on its own, independent of what it turns out to be.
What it is not, yet, is evidence of anything exotic. AARO's own report explicitly says none of its findings point to breakthrough technology, and the specific reason this case stays open — insufficient sensor data — is a far more common failure mode than an inexplicable one. The honest position is to flag it as a genuinely open question and watch for whatever AARO says about it next, rather than either dismissing it or overselling it in the meantime.
Sources: DefenseScoop (Brandi Vincent, July 21, 2026) · AARO Fiscal Year 2025 Consolidated Annual Report on UAP (PDF)