Overview
AARO’s FY2025 report records how new analytical tools changed the handling of earlier observations as well as current intake. It reports 114 resolutions among 319 incoming reports and another 256 resolutions from earlier periods. The 370 total therefore measures work on more than one intake group.
The document became public in 2026, although its principal reporting window runs from 2 June 2024 to 30 May 2025. The fiscal-year label should not be used as the publication date. Report intake, analytical work and publication belong to different parts of the chronology.
Chronology
2 June 2024–30 May 2025 Main reporting window; newly submitted accounts of older events are also included.
30 May 2025 Information cut-off and date attached to the cumulative holding of 1,870 reports.
July 2026 AARO’s publication listing places the public report in July; its visible and machine-readable entries differ on the precise day.
Incoming reports and work on older cases
The 319 incoming reports comprise 284 about events in the principal window and 35 about earlier events from 2010–2024. AARO assigned 274 to the air domain, 44 to the space domain and one to the maritime domain. As in the preceding report, none of the space-domain accounts came from space-based sensors. Forty-two came through the FAA and two through ground-based U.S. Space Command sensors. Report, printed pp. 4–5.
For the incoming group, the report records 114 resolved cases, three recommended closures awaiting review and authorisation, nine cases selected for further analysis and 191 placed in the Active Archive. Those figures total 317. It also records two mergers of reports referring to single events. The merger statement matters because report intake and distinct incident files are not necessarily the same counting unit.
The further 256 resolutions concern cases from earlier reporting periods. Adding these to the 114 incoming cases gives the stated 370 resolutions. Comparing 370 directly with the 319 incoming reports would mix the office’s total workload with one year’s intake.
What the satellite figures describe
The executive summary and programme update say a new modelling capability enabled 238 satellite-flare resolutions. Section IV.C states that 44 UAP-related events were resolved as satellite flaring during the reporting period. The wording alone does not clearly explain the relationship between those totals. Executive summary, printed p. 2; Satellite discussion, printed p. 8.
Figure 1 provides a useful population check. Its labels show 60 balloon cases, 44 satellite cases, four aircraft, two uncrewed aircraft, two birds, one rocket and one jet pack. These sum to 114, matching the resolved incoming group rather than all 370 resolutions. The chart therefore places 44 within that smaller group. A broader total including older cases could accommodate 238, but the report does not provide the case ledger needed to allocate the remaining satellite resolutions securely. Closure chart, printed p. 6.
The modelling concerns sunlight reflected from satellite surfaces at particular viewing angles. Pilot descriptions of bright lights at apparently modest altitudes can then be compared with orbital geometry instead of accepting the estimated distance. The report attributes a large reduction in the share of observations reported above 45,000 feet partly to the earlier FAA intake and its satellite identifications. It would be premature to read that change as a change in the altitude distribution of one physical phenomenon.
Unresolved observations and security reporting
The single maritime-domain case described Navy reporting off Virginia of about 100 airborne objects and two likely uncrewed surface systems. AARO said it was still investigating with the reporting unit. The annual document does not contain the full observation logs or sensor package, so that description supports a report-history entry rather than a completed technical reconstruction.
Two reports attributed electronic or avionic interference to nearby UAP. AARO had not determined whether the reported effects were caused by the observed phenomena. A simultaneous observation and equipment problem supplies a question for analysis; establishing causation would require the equipment state, timing and possible alternative faults. Report, printed p. 9.
A separate section describes 50 incidents near nuclear infrastructure, weapons or launch sites. The supplying authorities classified these as uncrewed aircraft systems, and the report expressly says none was reported as UAP. Thirty-three involved one aircraft; the rest involved between two and seven. These figures describe a drone-security reporting stream and should remain separate from the unidentified-report total.
Access, triage and further collection
AARO received 262 contacts through its authorised reporting mechanism during the window. It judged 255 out of scope and selected seven for requests for further interviews. The mechanism prioritised people with first-hand knowledge of U.S. government UAP-related programmes. Its screening figures describe eligibility decisions; they do not report the final evidential findings from seven completed investigations. Report, printed p. 10.
The office described new sensor and algorithm prototypes across the air, maritime and space domains, alongside modelling intended to make older reports more tractable. The distinction between a prototype initiative and demonstrated field coverage remains necessary when judging progress: the annual report supplies an activity account, not a public performance evaluation for each system.
Evidence assessment
The FY2025 report shows why an investigation can make progress without receiving a uniformly better new dataset. A tool capable of comparing reported lights with satellite geometry can identify earlier observations, increasing the resolution total through work on the backlog. The separation between incoming cases and earlier holdings makes that gain intelligible.
The closure chart also improves interpretation of the 44/238 satellite figures. Its arithmetic anchors 44 to the 114-case incoming group, making a difference in reporting populations a plausible explanation for the larger capability total. The remaining allocation is still undocumented. Publishing that allocation, with the dated case decisions, would turn a reasonable reconciliation into an auditable one. Neither the chart nor the backlog total supports a general identification of the reports retained in the archive.
Source library
AARO, FY2025 consolidated annual report
Complete report. Intake and mergers on printed pp. 4–5; closure chart on p. 6; satellite passage on p. 8; security and disclosure reporting on pp. 9–10; capability total on p. 11. Read source
AARO congressional and press products
Publisher’s current listing and report access. The report’s cut-off date is not its public-release date. Read source
FY2024 report for comparison
Earlier intake and altitude reporting. Compare populations and observation windows before calculating trends. Read source