Buried in the Pentagon’s newly published annual UAP report is a single paragraph that does more work than the other forty pages combined. US Navy assets operating off the coast of Virginia reported, in the report’s own careful phrasing, approximately 100 airborne UAP and two, likely uncrewed, surface systems. The All-domain Anomaly Resolution Office says it is still investigating, in coordination with the unit that filed it.
That’s it. That’s the entry. No date. No named platform. No indication of what the sensors were, how long the event lasted, or whether anybody was scrambled. One hundred airborne objects and two boats nobody can account for, in the approaches to the largest naval base on earth, summarised in a sentence and a half.
The interesting thing is not that it’s unexplained. Plenty of things are unexplained. The interesting thing is that in an entire fiscal year of reporting, this is the only maritime case AARO received — and it happens to be the biggest single count of objects in the document.
What the report actually says
The document is the FY2025 Consolidated Annual Report on Unidentified Anomalous Phenomena, released in July 2026 and covering reports received between 2 June 2024 and 30 May 2025. AARO logged 319 reports in total: 284 from within the reporting window and 35 older incidents that had never made it into a previous edition.
The domain breakdown is where the Virginia case starts to look strange. Of those 319 reports, 274 were in the air domain and 44 in the space domain. One was maritime. Just the one.
Of the full set, AARO resolved 114 — attributed to the usual cast of balloons, birds, satellites, aircraft and small uncrewed systems, plus a single rocket launch and, magnificently, one manned jet pack. Around two hundred remain open, which is not the same as inexplicable; most will be sitting in a queue waiting for data that will never arrive. Nine cases were flagged as warranting further analysis by intelligence and scientific partners, which is the closest thing the report has to a shortlist. And the office repeats, as it has every year, that it has found no evidence of extraterrestrial or breakthrough technology.
The satellite section deserves a mention, because it’s the report at its best. Of the 44 space-domain reports, 42 came not from space-based sensors but from FAA civilian pilot reports, with two from US Space Command ground sensors. AARO ran three-dimensional modelling and all-source analysis and concluded the lot were consistent with sunlight reflecting off satellites. That is genuinely good work — dull, methodical, and exactly what the office exists to do. It also rather neatly illustrates a point we’ve made before about why pilot reports are rising without the skies necessarily getting stranger: a pilot seeing a bright moving light is reporting accurately. The light just isn’t a craft.
So the office can resolve things when it has something to work with. Which makes the Virginia paragraph’s emptiness a statement in itself.
Why one maritime case is the odd number
Set aside the hundred objects for a moment and consider the denominator. The US Navy operates continuously off the mid-Atlantic coast. The Virginia Capes operating area is one of the busiest stretches of military water anywhere — carrier qualifications, air wing workups, submarine transits, live-fire ranges. Thousands of watch hours, radar-equipped ships, and trained observers whose entire job is noticing things.
And the reporting system received exactly one maritime UAP report from all of it in twelve months.
There are two readings, and neither is comfortable. Either the sea genuinely produces almost nothing anomalous — plausible, but hard to square with decades of Navy anecdote — or the maritime reporting pathway barely functions. AARO’s own text gestures at the second: it notes, again, that a lack of timely and actionable sensor data continues to constrain its ability to resolve cases. A reporting channel that yields one case a year isn’t a filter. It’s a blockage.
Which means the Virginia event may not be the year’s only maritime anomaly. It may simply be the only one somebody bothered to write up — or the only one so large that not writing it up became impossible.
These are not unfamiliar waters
If “unexplained objects swarming Hampton Roads” rings a bell, it should. In December 2023, unidentified drones flew over Langley Air Force Base in Virginia on 17 consecutive nights, arriving reliably in the 45 minutes to an hour after sunset. The first was estimated at around 20 feet long, moving at over 100 mph at 3,000 to 4,000 feet. Others were spotted over Naval Station Norfolk before crossing the James River toward Hampton and Langley — which is to say, over the world’s largest naval port and the neighbourhood of some of the most sensitive units in the US military.
The FBI, Defense Department officials and AARO staff held two weeks of meetings about it. The incursions showed no obvious hostile intent. The Pentagon only confirmed the episode publicly in October 2024, ten months later, and admitted it still did not know where the drones had come from. As far as the public record goes, it still doesn’t.
That’s the context the new paragraph lands in: the same airspace, the same institutional shrug, a demonstrated inability to attribute a sustained incursion over a defended base. The reason that inability persists is less mysterious than it looks, and mostly a question of which office is allowed to act. Whatever was off Virginia, the relevant precedent is not a 2004 gun-camera video. It’s an unsolved case from two years ago in the same postcode.
The boring explanation that should worry you more
Here is the hypothesis that fits the fewest exotic assumptions and the most available facts: this was drones and uncrewed boats, and the question is whose.
The phrase “two, likely uncrewed, surface systems” is doing a lot of quiet work. It is not UFO language. It is procurement language — the vocabulary of a service that is currently awash in exactly that hardware. The Navy has been running 16-foot Global Autonomous Reconnaissance Craft in multinational exercises, including UNITAS 2025 along the US East Coast between Naval Station Mayport in Florida and Naval Station Norfolk. At NATO’s Dynamic Messenger 2025 off Portugal, GARCs were deployed specifically to disrupt attacking uncrewed surface vessels and defend infrastructure. In June 2026 the Navy named seven companies to compete in at-sea trials for its Medium Unmanned Surface Vessel programme.
So: uncrewed surface craft operating off the East Coast in company with a large number of small airborne systems is a decent description of a US Navy experiment. It is also a decent description of a US Navy exercise that a ship’s watch team wasn’t briefed on — the most deflating outcome available, and one that would explain both the size of the count and the absence of any follow-up drama.
But there is a third possibility that nobody should find soothing. If a hundred airborne objects and two autonomous vessels can loiter off Virginia and the resulting official record is a single paragraph marked “under investigation”, then the same event conducted by somebody else’s navy would look identical in the paperwork. Sean Kirkpatrick, AARO’s first director, has consistently argued that the unresolved residue — two to five percent of the pile, on his estimate — is most likely prosaic, and has pointed at large spherical drones and at technology being tested by private citizens or other states. He means that as reassurance about aliens. Read it again as a statement about air and maritime domain awareness and it is nothing of the kind. Europe spent much of late 2025 closing airports over drone sightings near sensitive infrastructure precisely because “probably somebody’s drone” stopped being a comforting sentence.
The sceptic’s read, in full
Give the deflationary case its due, because it’s strong.
First, “approximately 100” is not a sensor count; it’s a report, and reports of swarms are notoriously elastic. Sceptics like Mick West of Metabunk have spent years demonstrating how quickly a handful of lights becomes a formation once human pattern-matching gets involved, and how confidently witnesses misjudge number, range and size at sea, at night, with no reference points. A hundred could be a dozen, seen twice.
Second, “airborne UAP” in AARO’s taxonomy means unidentified, not unidentifiable, and not anomalous in performance. Nothing in the entry claims impossible acceleration, no infrared signature, no absence of propulsion — none of the markers that make a case interesting. Compare that with the Nimitz encounter, where the strength was never the object count but the cross-sensor corroboration. Here we have a headline number and nothing behind it.
Third, the base rate is brutal. Of everything AARO has ever managed to run to ground, essentially all of it has been mundane, and the categories that dominate — balloons, drones, birds, satellites, aircraft — are precisely the categories that a hundred lights over water would fall into. Our read of the annual figures came to the same conclusion: the resolutions are the story, and the residue is mostly a data problem.
The honest position is that we do not know what this was, that the smart money is on drones, and that “drones” is an answer which raises its own questions rather than closing the file.
The bit that’s AARO’s own fault
There is a process failure sitting underneath all of this, and it isn’t a conspiracy.
The report arrived months after the statutory reporting cycle Congress had in mind — a lateness documented by John Greenewald Jr’s Black Vault, which has been prising these documents loose via FOIA since Greenewald started filing requests as a teenager in 1996. The FY2025 edition therefore describes events up to May 2025 and reaches the public in July 2026. The Virginia case may be fourteen months old or more. Nobody outside the building knows, because the paragraph doesn’t say.
This is how avoidable suspicion gets manufactured. AARO, under Dr Jon Kosloski — a former NSA Research Directorate scientist who took the job in August 2024 — has done demonstrably rigorous work; the satellite-glint analysis proves it. Then it publishes the single most striking incident in its inventory as an undated fragment, a year late, with no sensor detail and no commitment to a follow-up date. Lawmakers who have spent three years complaining that the office is opaque are handed a fresh exhibit, and it’s a fair cop. The same instinct is what makes the House’s disclosure push so hard to argue against on the merits, whatever one thinks of its more excitable supporters.
You cannot ask the public to trust your negative findings while rationing the positive ones.
The UAP Times take
Credibility 2, and the rating is about the document, not the objects. This is a primary Pentagon report describing an event its own investigators can’t yet close — which is about as solid as sourcing gets in this field, and worlds away from a shaky phone clip. What the event was remains genuinely open, and we’d put our money, without much enthusiasm, on uncrewed systems of terrestrial manufacture.
That’s the deflating part and the unsettling part at once. A hundred drones and two robot boats off Virginia is not evidence of visitors. It is evidence that the approaches to the largest naval base on the planet can host a small mechanised crowd, and that the resulting institutional response is one paragraph, filed fourteen months late, with the word “likely” in it.
We’d like a date. We’d like to know which sensors saw what. And we’d like to know whether anyone has yet checked the simplest question of all — whether it was ours.
Update: the government’s newly formed UAP Science Advisory Council would be an obvious body to examine this case. On present arrangements it cannot see the underlying data either.
Source: AARO FY2025 Consolidated Annual Report on UAP; DefenseScoop; The Black Vault