NARA’s 2024 UAP Records Collection: All Agencies Must Identify Files

You’ve probably seen the same cycle a dozen times: “UFO disclosure is here,” “UAP bombshell incoming,” “this changes everything,” and then… nothing you can actually verify. The counterintuitive part is that the stuff that forces real movement rarely looks like a headline at all. It looks like a records workflow nobody outside government wants to read, because process beats hype every time.

So you’re stuck with an annoying question: do you treat 2024 as a turning point, or just another false start dressed up as “new revelations”? If you care about what can become public instead of what can go viral, the difference comes down to one unglamorous choke point: you don’t release what you haven’t identified, and agencies don’t have to reckon with what they haven’t surfaced on paper.

That’s why a quiet push in early February 2024 matters. NARA began implementing the UAP records law in early February 2024, publishing a public notice titled “Establishment of the UAP Records Collection” (National Archives and Records Administration, Public Notice, February 6, 2024), which states in part “NARA will create a UAP Records Collection to aggregate copies of Government, Government-provided, or Government-funded records relating to UAP and related technologies” (see the public notice on the NARA website). Around the same time, NARA issued records-management memorandum AC-13-2024, titled “AC-13-2024: Guidance for Identification and Handling of UAP-Related Records” (Office of the Chief Records Officer, National Archives and Records Administration, February 6, 2024), which briefs records managers on the law and instructs agencies to begin identifying UAP-related records. Both the public notice and AC-13-2024 are available from NARA so readers can verify the source documents in one click (Public Notice; AC-13-2024). This is the step most people skip over because it feels like bureaucracy, but it’s the bottleneck that turns “some office knows something” into “there’s a trackable set of records that has to be handled.” And to keep expectations grounded: “identifying records” is a records-management action and does not equal immediate public release.

Takeaway: treat early-2024 “disclosure” news as real only when you see process signals that prove agencies are inventorying and tagging UAP records, because the paperwork trail moves the needle long before the loudest allegation does.

What the UAP Records Collection Is

That process-first mindset is also the easiest way to understand what NARA is actually building here. The headline you’ve seen floating around makes it sound like NARA is about to drop a single, definitive UAP “dump.” That’s not what this is. The UAP Records Collection is a long-game aggregation mechanism designed to force discoverability over time, not a one-and-done report you read once and move on from.

NARA has created the UAP Records Collection (Record Group 615). The National Archives Catalog entry for Record Group 615 (UAP Records Collection) summarizes the scope as “copies of all Government, Government-provided, or Government-funded records relating to UAP and related technologies,” and notes that materials will be described and published in the Catalog as they are ingested (National Archives Catalog, Record Group 615). The point is ongoing growth: records get added on a continuing basis and the public-facing trail shows up in the National Archives Catalog as materials are described and published. The scope is deliberately broad: NARA’s described intent is that the collection will consist of copies of all Government, Government-provided, or Government-funded records relating to UAP and related technologies. “Copies” matters here because it signals aggregation and centralized tracking, even when originals remain in other places.

The friction is obvious once you think about how federal records actually exist: UAP-related material isn’t one neat folder sitting in one agency. It can be spread across offices, contractors, formats, and decades. Without a durable “home” that keeps accumulating, “disclosure” turns into a vague promise you can’t verify. Record Group 615 is meant to make that verifiable by giving UAP-related records a single, named collection you can repeatedly check as it expands.

You’ll encounter this effort through NARA’s normal organization and description layers, not through a flashy standalone portal. A Record Group is NARA’s way of grouping records: each Record Group corresponds to all records of a small agency or some records of a larger agency. That structure is why a cross-agency topic like UAP needs a dedicated container; it creates a consistent label you can search, cite, and monitor even when the underlying sources are scattered.

Inside that container, the most common unit you’ll see is a series, meaning records accumulated and used together for a specific purpose during a distinct period. Practically, series titles and descriptions are what you’ll scan in the catalog to understand what a set of records covers and how it’s bounded. When you need help orienting, a finding aid is the tool that helps you locate and understand materials within a record group, collection, or series, usually by giving context and navigation cues that a single catalog line can’t carry on its own.

“Identify files” sounds like a hunt for a secret binder. In plain English, it means surfacing what exists so it can be managed and described as part of a trackable body of records. That doesn’t automatically mean instant public access to every page. It does mean the universe of relevant federal material stops being hand-wavy: items can be named, placed into context, and accounted for, even if some stay restricted.

NARA also already holds UFO and UAP-related records across numerous record groups and collections, so this isn’t a claim that nothing existed before. The difference is aggregation and discoverability: one place to accumulate copies, one place to describe them, and one place for you to follow.

If you want a simple sanity check that this is actually moving, keep an eye on the National Archives Catalog and watch for the presence and growth of entries tied to UAP Records Collection (Record Group 615), including new descriptions and updates over time.

The Legal Backbone Behind the Search

Once you see the collection as an ongoing container, the next question becomes: what forces agencies to feed it? Implementation is the real battleground, and 2024 is where it started to bite. The shift isn’t more talk about “UAP transparency.” It’s that transparency talk began showing up in places that agencies have to operationalize: enacted authorizations, counsel guidance, records instructions, and internal tasking that turns a public issue into a day-to-day workflow.

The clean dividing line is simple: enacted law creates obligations; proposed language creates pressure. For 2024, the enacted anchor is the National Defense Authorization Act for Fiscal Year 2024, which became Public Law 118-31 after moving through Congress as H.R. 2670. That matters because “Public Law 118-31” is not a slogan. It’s the thing agencies route through leadership and general counsel, then translate into compliance tasks people actually get assigned.

By contrast, the most-circulated “UAP Disclosure Act” language has largely operated as proposal context in public discussion. A UAP-related amendment described as providing for the expeditious disclosure of UAP records was introduced in the Senate during the 118th Congress, and it’s often referred to in shorthand as “Schumer UAP Disclosure Act” language. Treat that shorthand as introduced-amendment territory unless you are looking at the final enacted text in Public Law 118-31.

Same story in the House: Rep. Eric Burlison publicly said he submitted a “UAP Disclosure Act 2025” amendment. The available framing indicates submission, not adoption. In practice, “submitted” can influence negotiations and headlines, but it does not bind an agency the way enacted text does.

Here’s the typical chain from Capitol Hill to your records queue:

1. Congress acts by passing an authorization or inserting report language that signals intent and oversight focus.
2. Text becomes law when the final bill is enacted and published as a public law (for FY2024, that’s Public Law 118-31 from H.R. 2670).
3. Agency leadership and general counsel interpret what the enacted language requires in operational terms, including risk, scope, and who owns it.
4. Records officers and compliance teams translate that interpretation into controlled actions: inventories, preservation holds where appropriate, coordination across components, and standardized ways to track what exists and where it sits.
5. Programs execute by pulling lists, identifying systems of record, documenting provenance, and resolving ownership disputes between offices.

The non-obvious friction is that the last three steps can start even when the public debate is still stuck at step one. Agencies respond to enacted requirements with formal tasking. They respond to proposals and political heat with preparatory work that looks similar from the outside, but has a different legal posture.

2024 mattered because the enacted NDAA gave agencies a concrete legal backdrop, while simultaneous “expeditious disclosure” proposals and public statements amplified scrutiny. That combination changes behavior. You see more internal coordination, tighter documentation norms, and more sensitivity around preserving UAP-adjacent material that could become relevant to oversight.

Keep one constraint front of mind: in the provided excerpts for this topic, there is no quoted enacted statutory text explicitly mandating a UAP records collection at NARA. That absence is exactly why careful readers separate what’s verifiable in enacted law from what’s being pushed in amendments, letters, and commentary.

Whistleblower-protection discussions add another layer. When allegations and testimony are circulating, preservation and handling discipline tends to tighten because the downside of sloppy retention, inconsistent indexing, or informal transfers is higher. That’s not a hearing recap. It’s basic risk management for records teams.

Use a three-question filter for every UAP “disclosure” headline you read: Is it enacted (a public law like Public Law 118-31)? Is it implemented (agency guidance and tasking you can point to)? Or is it a proposal (introduced amendment language or a public submission that hasn’t been adopted)? Answering those three questions keeps you anchored to obligations, not noise.

What Agencies Must Identify and Report

Those obligations still have to become real work inside real systems, and this is where the “identify files” language stops sounding abstract. “All agencies must identify files” sounds like somebody just needs to run a search for “UAP” and call it a day. In practice, it’s a scavenger hunt across government systems, not a single filing cabinet. The messiness is exactly why this step matters: you can’t preserve, schedule, or eventually transfer records you haven’t actually located across the sprawl of email, databases, and contractor environments that make up modern government work.

Start with the obvious places people picture: program folders on shared drives, office SharePoint sites, and the email accounts where decisions actually get made. Then add the places that quietly do most of the work: case management systems, incident tracking tools, service desks, and internal portals where people log sightings, route questions, or attach supporting material. UAP-related material can also sit inside contracting files (statements of work, deliverables, invoices), briefing decks for leadership, meeting notes, taskers, budget justifications, and the attachments that travel with coordination chains.

The tricky part is that UAP records are rarely born “as UAP records.” A pilot report can live as an aviation safety item, an intelligence note can sit in a daily brief workflow, a sensor anomaly can be filed as a systems issue, and a procurement action can be labeled as routine R and D support. That’s why the hunt isn’t just inside one program office. It’s spread across the systems where those day-to-day artifacts are created and stored.

At a practical level, identification usually begins where records managers already have a foothold: the agency’s inventory of information systems and its existing records schedules. NARA guidance directs agencies to maintain an inventory of agency information systems and provides practical guidance on managing electronic records and system inventories (see NARA Records Management Guidance). From there, agencies push outward into subcomponents, field offices, and any external partners who created or received government records as part of the work.

The first slowdown is vocabulary. “UFO,” “UAP,” “unidentified,” “anomalous,” “range fouler,” “unknown track,” “unresolved sensor,” and program nicknames don’t line up cleanly across offices. If one unit tags something as “air safety” and another tags the same phenomenon as “intelligence interest,” a simple keyword approach misses huge chunks of the universe you’re supposed to identify.

Then you hit metadata, or the lack of it. A lot of older repositories have weak indexing: attachments stripped of context, files with meaningless names, migrated folders that lost creator fields, and emails exported without consistent retention tagging. NARA maintains a metadata requirements reference resource for agencies, and that matters here because identification depends on being able to say what a record is, who created it, when, and under what authority. If that information is missing, agencies end up doing manual triage, which is slow and easy to get wrong.

Classification and compartments add another layer of friction. Even when a record can’t be widely shared, someone still has to determine what exists, what organization has “equities” in it (who owns the information and who must be coordinated with), and what rules govern its handling. That coordination problem gets worse when multiple agencies touched the same material, or when the record mixes operational details, sources and methods, and contracting data in one package.

Contractors are the other predictable pain point. Some UAP-adjacent work flows through government-funded R and D, analysis support, sensor development, and data processing. That can leave relevant records sitting in contractor environments, or in hybrid systems where the government is the customer but not the day-to-day administrator. Identification has to include those realities, because “not on our server” doesn’t mean “not a federal record.”

And “all agencies” is bigger than most people assume. DoD is the obvious center of gravity, but interfaces can include DHS components, FAA pathways (especially where airspace reporting and safety processes intersect), NASA-adjacent research and data threads, and any other office that generated reports, coordination emails, or analysis products as part of routine operations.

Identification isn’t just “find everything.” It’s “separate what must be kept forever from what can eventually be disposed of.” Agencies must identify permanent records and ensure timely transfers to NARA, because permanent records are the ones that ultimately move into the National Archives for long-term custody. That transfer event is an accession, meaning the formal handoff where NARA takes legal custody (accession) and the records become part of the archival holdings over time.

That’s where records management governance stops being paperwork and starts being a forcing function. Agencies must assign records management responsibility to a person or office under 36 CFR, because someone has to own the inventory, the schedules, and the decisions about what is permanent. On the technical side, NARA provides guidance on acceptable file formats for permanent electronic record transfers, which matters when agencies discover that “the record” exists only as proprietary files, brittle exports, or formats that won’t survive long-term preservation workflows.

One nuance that keeps getting lost in public conversation: identification is not release. A record can be identified, described, and queued for archival handling while still being classified, controlled, or otherwise withheld.

So what should you watch for if you want to know whether agencies are taking the identification requirement seriously? Look for consistent, repeatable language in official statements: acknowledgments of specific holdings (not just “we searched”), signs of interagency coordination and referral (especially where equities are shared), and status terms that imply real workflow movement like “identified,” “under review,” “referred,” and “scheduled for transfer.” Those phrases don’t guarantee disclosure, but they do signal the government is doing the hard part: turning a scattered trail of artifacts into something that can actually be managed, preserved, and eventually accessioned.

AARO, Congress, and the Public Narrative

That back-end work doesn’t happen in a vacuum; it gets nudged along by oversight, deadlines, and the public pressure that follows. Oversight and reporting cycles don’t just shape the UAP story. They change incentives inside agencies, which changes paperwork behavior: what gets written down, what gets routed up the chain, and what people feel compelled to go back and locate when the spotlight hits.

The easiest place to see this incentive shift is in the report cadence. ODNI and DoD jointly published the Fiscal Year 2024 Consolidated Annual Report on UAP, and DoD also released an annual UAP report covering May 1, 2023 to June 1, 2024. That DoD report explicitly includes UAP reports from previous time periods that weren’t included in earlier reports. Those are the kinds of “paper trail tells” that matter: not that a report proves a sensational claim, but that reporting cycles force summaries, comparisons against prior numbers, and explanations when the dataset changes.

The complication is that readers treat these reports like verdicts. They’re not. They’re snapshots constrained by what got reported into official channels, what could be shared at that classification level, and what the compilers can stand behind. The practical takeaway is to read them as process artifacts: they reveal what the government is tracking and how consistent the tracking is over time.

Congress is the pressure valve in this system. The House Committee on Oversight and Government Reform has held UAP-related hearings and pushed for more transparency, and that posture alone changes behavior inside agencies. A scheduled hearing creates a hard calendar deadline that triggers coordination: people ask for briefings, recheck prior statements, and chase down supporting material so nobody gets surprised under questioning.

That’s why a House Oversight hearing scheduled for September 2025 matters before anyone testifies. The point isn’t the theatrics. The point is the institutional scramble that happens in advance. For readers who want to monitor committee schedules and hearing listings directly, the House Oversight Committee maintains a public hearings page where upcoming dates and witness lists are posted (House Oversight Committee hearings page).

AARO sits in the middle of this as the Pentagon’s UAP office, which is exactly why the public expects “the government knows more.” When public narrative pressure spikes, offices like AARO get more inbound claims, more media attention, and more congressional interest, all of which increases the premium on defensible documentation.

David Grusch is a clean example of the dynamic: his sworn testimony and public claims intensified attention, but testimony isn’t the same thing as documentary corroboration. That gap is where incentives shift. Under scrutiny, agencies get more careful about how records are retained and how assertions are backed, because unsupported statements become liabilities when Oversight staff start asking for specifics.

When you’re watching AARO updates, ODNI and DoD reporting cycles, or upcoming hearings, look for process signals that correlate with records surfacing: explicit mentions of newly included back-period reports, tighter sourcing language, clearer references to which channels generated the data, and sharper explanations of discrepancies across years. Those aren’t instant disclosure. They’re the signs that incentives have shifted toward finding, reconciling, and preserving what can be defended on paper.

What Gets Released and What Stays Classified

Even when those incentives push records to the surface, what you can actually read still depends on access rules, not attention. NARA’s public-facing side of the UAP Records Collection is going to look like normal archival access: catalog entries, accession notices, and restriction statements that tell you what’s open, what’s redacted, and what’s closed. The key detail is that NARA doesn’t just say “restricted” in a vague way; it flags restrictions using an Access Restriction Status element that signals the specific access condition attached to the material (NARA). That’s why two records can sit next to each other in the same collection but present very different viewing experiences.

The friction point is time. NARA’s rule for transferred federal records that are less than 30 years old is strict: NARA will remove or relax restrictions only with written concurrence from the transferring agency, unless a law requires access (NARA). So if a tranche of UAP-related material is newer than that 30-year mark, the public catalog can still show it exists while the underlying pages remain constrained by the originating agency’s written position.

Some withholding really is plain national security classification. Executive Order 13526, the federal order that sets the rules for classifying and protecting national security information, governs how agencies mark, handle, and keep certain records classified (EO 13526). If a UAP-related record is marked and protected under that framework, NARA can’t just decide it’s interesting and put it online. The decision authority sits with the classifying agency, not the archivist.

Other withholding is less intuitive because it’s not “just classification,” it’s nuclear law. The Atomic Energy Act of 1954 establishes the government-wide Restricted Data regime, which covers certain nuclear weapons and nuclear material information regardless of who holds the record (Atomic Energy Act). EO 13526 even recognizes that Restricted Data (RD), Formerly Restricted Data (FRD), and Transclassified Foreign Nuclear Information (TFNI) are classified under the Atomic Energy Act, not under the normal executive-order-only pathway (EO 13526; Atomic Energy Act). If a UAP file brushes up against nuclear propulsion, detection systems, or related technical details, those AEA categories can keep content locked down even when the surrounding narrative feels harmless.

This is where “NARA access” and “agency constraints” split apart in practice. NARA can describe the record, house it, and expose its metadata, but the originating agencies control classification equities, and in specialized areas like DOE there are defined procedures tied to EO 13526 decisions (for example, DOE’s 10 CFR Part 1045 framework) that sit outside NARA’s day-to-day control (EO 13526).

If you’re trying to separate “withheld because of process” from “withheld because it truly can’t be released,” the two public levers people confuse are FOIA and Mandatory Declassification Review. Mandatory Declassification Review (MDR), a process that lets any individual ask an agency to review classified national security information subject to Executive Order 13526 for possible declassification, is available regardless of the record’s age or origin for documents classified under that executive-order regime (see NARA MDR guidance). Note that Atomic Energy Act Restricted Data regimes follow different authorities and processes and are governed separately, for example through DOE rules at 10 CFR Part 1045, and thus do not follow the same MDR pathway (DOE 10 CFR Part 1045).

FOIA and MDR can point at the same document, but they don’t run on the same track. MDR is an alternative route in addition to FOIA, and agencies generally make you choose one lane for the same ask, often refusing to process the same request as both at the same time or consolidating it into a single bucket (MDR). The practical takeaway: a “no” in the catalog isn’t the end of the story, but it’s also not proof of bad faith. It usually reflects which authority controls the information, whether that’s EO 13526, the Atomic Energy Act, or a newer-than-30-years transfer limitation that NARA can’t unilaterally override (NARA; EO 13526; Atomic Energy Act).

How to Track the Next Signals

If hype is the problem and process is the solution, this is where you can actually watch the gears turn. The real change is structural: once agencies have to identify and aggregate UAP records, accountability compounds over time. That February 2024 AC-13-2024 memo functions as the trigger for identification work that forces offices to stop treating “UAP” as a vague rumor bucket and start treating it like a trackable records problem. The public-facing payoff is slower because the UAP Records Collection is built in the open as NARA ingests and posts materials in the National Archives Catalog, while continuing to add to Record Group 615 on a rolling basis. Progress also won’t look smooth: scattered systems, contractor-held data, and classification constraints create uneven outputs across agencies, even when the mandate is the same. Add oversight rhythms, like ODNI and DoD report cycles and the scheduled September 2025 hearing, and you get predictable bursts of documentation pressure that can look like “sudden disclosure” if you’re only watching headlines.

Use this as your tracking checklist, and treat it like a signal filter:

• Check NARA’s National Archives Catalog for new entries or updates under Record Group 615. Real signal: new catalog items, updated descriptions, or newly posted unclassified copies. Recycled headline: “NARA is creating a collection” with no new catalog movement.
• Watch the Federal Register and Regulations.gov for implementing rules, policy changes, and dockets (Federal Register entries often point to docket numbers). Real signal: a docket with actual agency text, deadlines, or instructions, not commentary.
• Verify legislation on Congress.gov. Real signal: enacted text, recorded votes, or an updated bill status, not screenshots or “sources say” threads.
• Track DoD, ODNI, and AARO report pages for schedule changes, new submissions, or revised reporting language. These reporting-cycle shifts can correlate with records surfacing, but correlation ≠ causation.

As 2025 to 2026 rolls on, expect UFO and UAP news spikes to cluster around filings, reports, and hearings, not around viral claims. The healthier baseline is the same one from the start: follow the paperwork trail-catalog growth, standardized reporting, and documented handling-because that’s what you can verify, even if it doesn’t resolve every “non-human intelligence” question. If you want a clean feed of primary-source signals as they appear, subscribe to our newsletter for updates.

Frequently Asked Questions