Buried in the Pentagon's latest annual accounting of unidentified anomalous phenomena is a single maritime-domain case that stands apart from the usual mix of infrared blips and archival FBI interviews: a report from U.S. Navy assets describing approximately 100 airborne objects and two likely uncrewed surface vessels operating off the coast of Virginia, according to DefenseScoop, which reviewed the document. The All-domain Anomaly Resolution Office says it is still actively looking into it.
One Case, a Very Different Scale
The incident appears in AARO's Fiscal Year 2025 Consolidated Annual Report on UAP, covering the period from June 2, 2024 through May 30, 2025. Of the hundreds of reports the office logged that year, this was the only one in the maritime domain — and it's an outlier in scale as well as setting. Most publicly discussed UAP cases involve a single object, or at most a handful, tracked by one sensor over a few minutes. A Navy report describing roughly 100 airborne objects alongside two surface vessels operating without a crew is a different category of event: either a genuinely unusual mass sighting, or a report that will eventually resolve into something far more mundane, like a drone swarm exercise or a fishing fleet's unmanned buoys misread by an unfamiliar sensor operator. AARO's own language leaves that question open. Asked about the case, officials told DefenseScoop only that "AARO is actively investigating this event in coordination with the reporting unit" — confirmation that a report was filed and taken seriously, not a finding of any kind.
What "Uncrewed Surface Systems" Actually Means Here
The report's reference to "likely uncrewed surface systems" is worth unpacking, since the phrase covers a wide range of real-world possibilities before it gets anywhere near anomalous. Autonomous or remotely piloted surface vessels are a rapidly growing category of maritime hardware — used by militaries, oceanographic researchers, and increasingly by adversary nations probing coastal waters near U.S. installations. AARO's own careful wording, "likely uncrewed" rather than a firm identification, signals that the Navy personnel who filed the report couldn't conclusively determine what the surface vessels were, only that they didn't appear to have anyone aboard. That's precisely the kind of ambiguity AARO's investigative process exists to resolve — and precisely why this case, unlike hundreds of others in the same report, hasn't yet been closed out.
The Numbers Around the Case
The Virginia incident sits inside a much larger data set. AARO's report says the office received 319 total UAP reports during the covered period and resolved 114 of them as mundane objects — balloons, birds, satellites, aircraft, and similar conventional explanations. That leaves the office's total caseload at 1,870 reports as of May 30, 2025, a backlog that has been building since the office's creation and that officials have previously acknowledged growing faster than it can be closed. A Pentagon spokesperson did not immediately respond to DefenseScoop's request for additional detail on the Virginia case specifically.
Why a Maritime Case Stands Out
Most of the public UAP conversation over the past several years has centered on aerial encounters — fighter jet gun-camera footage, FBI witness interviews about lights in the sky, drone incursions over military installations. A case combining a large number of airborne objects with uncrewed vessels on the water below adds a dimension that's much harder to explain away with a single conventional culprit, since it would require two separate misidentifications happening in the same place at the same time — or, alternatively, a single coordinated event, of whatever origin, spanning both domains. Neither AARO nor DefenseScoop's reporting offers a resolution to that question, and it's worth being honest about what that means: this is a genuinely open case, not a story with an ending yet.
What Would Actually Resolve This
AARO's investigative process typically leans on multi-sensor corroboration — radar tracks, IFF (identify friend or foe) transponder data, other ships or aircraft in the vicinity, and personnel debriefs — to either identify a conventional explanation or formally classify a case as unresolved. Whether that corroborating data exists for the Virginia incident, and whether AARO will eventually publish more than a status update on it, isn't yet public. Given that this is the only maritime case in an entire fiscal year of reporting, and given the specificity of the numbers involved, it's a case worth tracking as future AARO reports and any Freedom of Information Act releases work their way through the pipeline.
For now, the report stands exactly where AARO left it: a Navy account of a hundred airborne objects and two vessels that shouldn't have had anyone driving them, filed, taken seriously enough to warrant an active investigation, and not yet explained.