The UAP Report Congress Mandated Landed Months Late. Nobody Enforced the Clock.

Congress wrote a clock into the law that created the Pentagon’s UFO office. The office just showed everyone what happens when nobody’s watching that clock.

The All-domain Anomaly Resolution Office released its Fiscal Year 2025 Consolidated Annual Report on Unidentified Anomalous Phenomena in July 2026, according to documents obtained and published by The Black Vault. The report covers activity from June 2, 2024 through May 30, 2025. Do the subtraction yourself: that’s over a year between the close of the reporting period and the public release. The previous year’s report, covering FY2024, came out in November 2024, on something close to the schedule everyone had come to expect. This one blew through that window by months.

TL;DR: AARO’s annual UAP report is required by federal statute, and the FY2025 edition arrived months after the pattern set by prior years would predict, with no public explanation for the gap. It logs 319 newly received reports, resolves 370 cases total, and attributes every single resolved case to a conventional cause, including a batch of “space-domain” sightings the office now says were satellites catching sunlight. None of that changes the more basic problem: a disclosure law with no functioning enforcement mechanism produces disclosure on the agency’s schedule, not the law’s.

The mandate is statutory, and it carries a deadline

The reporting mandate lives at 50 U.S.C. § 3373(k)(1)(A). The text requires a report “not later than 180 days after December 23, 2022, and annually thereafter for four years.” Run that forward: the first report was due by roughly late June 2023, with subsequent reports due on that same yearly mark for the four years following. That puts the FY2025 report’s due date somewhere in the June 2026 range, not July, and the reporting period it’s supposed to cover should already be old news by the time the ink is dry on a document like this.

Two things are worth separating here, because they get collapsed constantly in coverage of this office. There is the statutory deadline for submission to Congress, and there is the public release date, which nothing in the text of § 3373 actually pins down. AARO can, in theory, submit on time to the relevant committees and still sit on the public version for months. Whether that’s what happened here isn’t something a public document dump can settle on its own, and I’m flagging that distinction rather than asserting a specific number of days late, because the honest answer is I don’t have AARO’s classified submission date and neither does the outlet reporting this.

What I can say with confidence: the four-year clause means this reporting requirement has a sunset built into it. If FY2023 was year one, FY2025 is year three, which means there are at most one or two more of these mandated before the statute stops requiring them at all. That’s the story nobody’s telling yet. A disclosure law that expires on its own schedule, quietly, is functionally identical to a disclosure law that gets repealed, except nobody has to vote on it.

How late is this report, really, and does it matter?

Compare publication dates directly. FY2024’s report, covering a similar twelve-month window, was out by November 2024, a few months after its own reporting period closed. FY2025’s report covers a period that closed May 30, 2025, and didn’t surface until July 2026. That’s over a year of lag, not a few months, if you’re measuring from the end of the reporting period rather than from an internal submission date nobody outside the government can verify.

Does the size of the gap matter if the report eventually shows up? For anyone treating this as a transparency mechanism rather than a compliance checkbox, yes. A report on twelve months of aviation and defense anomaly activity that lands over a year after that window closes isn’t timely oversight. It’s an archival document. The people who filed the original reports, the pilots and radar operators whose sightings make up the raw case count, get zero real-time signal about whether their report mattered, got investigated, or got filed under “satellite reflection” and closed.

319 new cases, 284 of them inside the window

319 new UAP reports came in during the covered period: 284 from incidents that happened within the window, plus 35 older incidents surfacing for the first time. AARO says it resolved 114 of the new cases, plus 256 previously reported cases from earlier reporting periods, for 370 total resolutions this cycle. Every one of those resolutions, according to the report, traces back to a conventional explanation.

The headline resolution method this cycle is the “expanded satellite analysis” in the title of the underlying release. AARO used three-dimensional modeling and all-source analysis to work through 44 space-domain reports, 42 of which came in from FAA civilian pilot reports, and concluded the observations were consistent with reflected sunlight off satellites. That’s a real methodological advance if the modeling holds up, and it’s also a pattern worth watching: as satellite constellations multiply in low orbit, “satellite flare” is going to keep absorbing a larger share of unexplained aerial sightings, which means the residual unexplained caseload should, in theory, keep shrinking for reasons that have nothing to do with anyone getting more forthcoming about anything.

Where does the paper trail go from here?

The obvious next document to pull is whatever congressional committee correspondence exists around the FY2025 submission, since that’s the only way to separate “AARO filed on time and sat on the public copy” from “AARO missed its own statutory window entirely.” FOIA requests targeting that correspondence, not the report itself, are the actual lever here. The report is already public. The submission date to the relevant committees isn’t, and that’s the fact that would resolve the timeline question instead of leaving it as an inference from two publication dates a year and a half apart.

There’s also the sunset clause. If FY2025 is year three of a four-year mandate, someone in Congress needs to decide, before that clock runs out, whether this reporting requirement gets extended, made permanent, or allowed to lapse quietly the way plenty of sunset provisions do. That’s a legislative question, not a records request, and it’s the one with an actual deadline attached that someone should be tracking now rather than after the fact.

Frequently asked questions

What law requires AARO to release these UAP reports?

50 U.S.C. § 3373(k)(1)(A) requires an annual report, with the first one due 180 days after December 23, 2022, and further reports due annually for four years after that. The statute sets a deadline for submission; it doesn’t set a separate deadline for public release, which is the gap this whole story lives in.

Does this mean the UAP reporting requirement is ending soon?

Based on the “four years” language in the statute, yes, on the current trajectory. If the count starts with the first required report, the mandate covers a finite window that’s already most of the way through. Whether Congress extends it, replaces it, or lets it expire is an open legislative question, not a settled fact, and it’s worth tracking independently of any single year’s report.