What AARO Reported About Virginia

The entire public description occupies three sentences. AARO says the case came from U.S. Navy assets operating off the coast of Virginia, involved approximately 100 airborne UAP and two likely uncrewed surface systems, and remains under active investigation with the reporting unit.

Confirmed In The Report Not Disclosed
The report came from U.S. Navy assets The date and precise location of the event
The assets were operating off Virginia The ships, aircraft or reporting unit involved
Approximately 100 contacts were described as airborne UAP Whether the contacts appeared simultaneously or in sequence
Two surface systems were assessed as likely uncrewed Who owned or controlled the surface systems
AARO is investigating with the reporting unit Imagery, radar data, duration, movement or an initial attribution

The report does not call the event a swarm, incursion or transmedium encounter. It also does not describe unusual speed, acceleration, manoeuvring, signatures or any movement between air and water. Those details cannot be added to the case from the published text.

What UAP Means In This Report

AARO defines a UAP as an anomalous detection in the air, sea or space that has not been attributed to a known actor and is not readily understood by sensors or observers. The label records the unresolved status of a detection; it does not identify an extraterrestrial, adversarial or secret US origin.

The office places reports into domains according to where the detection occurred. A maritime UAP is detected at or below sea level, while an airborne UAP is between sea level and the Karman line. Our UFO and UAP explainer covers how the terms overlap and where the newer official definition is broader.

AARO classified the Virginia case as the one maritime-domain report even though most of its described contacts were airborne. The presence of two likely uncrewed surface systems appears to be the reason, but the annual report does not explain the classification decision or describe a connection between the two domains.

How The Case Fits The FY2025 Report

AARO received 319 UAP reports for the cycle covering events from 2 June 2024 to 30 May 2025, plus earlier events not included in a previous annual report. Of those, 284 concerned events during the reporting period and 35 concerned events from 2010 to 2024.

The domain split was heavily weighted towards the air:

  • 274 reports in the air domain
  • 44 reports in the space domain
  • 1 report in the maritime domain

AARO's total case holdings reached 1,870 reports by 30 May 2025. The office also warned that its files reflect a collection bias towards the continental United States, nearby waters and global U.S. military operating areas. Places with more military sensors and assets naturally generate more reports.

That bias affects how the Virginia case should be read. A report from a heavily monitored military operating area may contain valuable multi-sensor data, but the location alone does not establish a higher concentration of genuinely anomalous objects.

What AARO Resolved During The Year

AARO resolved 114 of the 319 incoming reports. It also closed 256 cases from earlier periods, bringing its total number of resolutions during the reporting cycle to 370.

Every resolved case was attributed to a prosaic object or event, including balloons, satellites, birds, aircraft, uncrewed aerial systems, one commercial rocket launch and one manned jet pack. None indicated an advanced foreign adversarial capability or a breakthrough technology.

A new three-dimensional modelling capability helped analysts resolve 238 reports as satellite flaring across the office's wider workload. Reflected sunlight can make satellites appear as intense moving or stationary lights from particular viewing angles. AARO used related modelling in its public analysis of the GoFast UAP encounter.

The unresolved workload remains substantial. AARO sent nine reports to intelligence, science and technology partners for further analysis. Another 191 of the 319 reports went into the active archive because the available data was not sufficient to determine whether the underlying events were natural, conventional technology or something beyond known performance.

The Missing Sensor Record

AARO says a lack of timely, actionable sensor data continues to limit its ability to resolve cases. For the Virginia event, the public report does not identify which sensors detected the airborne contacts or the two surface systems.

The distinction between a visual count, radar tracks, electronic detections and fused observations is critical. A hundred reported lights over several hours would present a different analytical problem from a hundred simultaneous radar tracks manoeuvring in a coordinated pattern. The report does not provide enough information to choose between those possibilities.

No public image, video, track plot, map or technical appendix accompanies the case. AARO may hold classified data from the reporting unit, but the annual report does not confirm what evidence it possesses or whether any of it can be declassified.

Electronic Interference And Flight Safety

Two other reports in the FY2025 collection described electronic or avionic interference near operational aircraft. AARO has not determined whether the reported effects were attributable to the associated UAP.

The annual report does not connect either interference report to the Virginia event. It also says no reports during the period indicated a flight safety concern. Claims that the Navy contacts disabled systems, endangered aircraft or interfered with equipment would therefore go beyond the released record.

Nuclear-Site Drone Reports Were Separate

AARO received 50 reports of uncrewed aerial systems near U.S. nuclear infrastructure, weapons and launch sites, up from 18 in the previous annual report. None of those incidents was reported as UAP.

The nuclear-site reports involved one to seven drones, usually during evening or overnight hours. AARO provides no public link between those incidents and the Virginia case. The distinction shows that the office does not automatically place every unidentified or unauthorised drone event in its UAP count.

What Could Be Released Next

A useful case update would identify the event date, reporting unit, detection methods, duration and number of independent sensors. Even if operational details stay classified, a declassified timeline or track reconstruction could show whether the roughly 100 airborne detections formed one event or several.

AARO already publishes imagery, calculations and resolution reports for selected cases. The office could add the Virginia event to that record whether it reaches a conventional explanation or remains unresolved. The proposed UAP Disclosure Act 2026 would create a separate records-review process, while the reported UAP NDA waiver concerns information supplied through authorised government interviews.

The next public update should answer four basic questions:

  1. When and where did the event occur?
  2. Which sensors or observers produced the count of approximately 100 airborne contacts?
  3. What caused the two surface systems to be assessed as likely uncrewed?
  4. Did AARO find evidence that the airborne and surface contacts were coordinated?

Source Trail

Verdict

The Virginia event is unresolved in the public record. AARO confirms that a Navy report described about 100 airborne UAP and two likely uncrewed surface systems, but it has released no source material showing what the contacts were or how they behaved.

The published information supports an active investigation, not a conclusion about extraterrestrial craft, advanced technology or a coordinated incursion. A case resolution, declassified sensor record or detailed event reconstruction is needed before the larger claims circulating around the report can be tested.