First UAP Hearing in 54 Years: 400 Reports, 11 Near-Misses Disclosed

Every UFO news cycle claims “this time it’s different.” You see the “400 reports” and “11 near-misses” headlines everywhere, and you’re stuck in the same spot: is this real momentum for UAP disclosure, or just another spike that fades when the next story hits?

You’re also making a real decision with real consequences. Do you believe it, ignore it, share it, or wait for harder proof? The May 17, 2022 hearing made that choice feel less like entertainment and more like civic literacy, because it treated UAP as an oversight and safety problem that Congress is supposed to interrogate, not a curiosity to gawk at. It was held by members of a U.S. House Intelligence Subcommittee, and multiple outlets described it as the first public congressional UAP or UFO hearing in over 50 years.

That shift in tone doesn’t erase the core tension: the public wants transparency, the government guards national-security limits, and “lots of reports” isn’t the same thing as “clear evidence.” Those viral figures are a perfect example. The phrasings “~400 reports” and “11 near-misses” are widely repeated in reporting and secondary summaries, but sourcing is messy. A search of the provided FAA-origin 255-page PDF did not locate those exact phrasings as quoted, so they shouldn’t be treated as direct quotes from that document.

You’ll leave knowing what’s verifiable, what’s still ambiguous, and which signals actually indicate progress the next time UAP disclosure numbers start trending.

The 54 Year Gap Explained

The “54 years” part isn’t trivia. It explains why today’s UAP conversation shows up in oversight letters, reporting pipelines, and classification fights instead of the old culture-war script of “believers vs skeptics.” When Congress last leaned in hard, it was the late 1960s era, commonly tied to attention from members such as then-Rep. Gerald Ford after high-profile sightings drew public pressure. That moment did not end with a grand reveal; it ended with the government moving to close the book on a formal, centralized investigative program.

That’s where the gap starts doing real work. Project Blue Book, the U.S. Air Force’s long-running UFO program, is commonly dated to 1952 through 1969, with the program’s public termination announced in 1969. For an authoritative timeline and archival record of Project Blue Book and related Air Force actions, see the National Archives’ overview of Air Force UFO records (Project Blue Book), which documents the program’s dates and disposition of records. That late-1960s congressional and public attention is the benchmark people use when they say “first hearing in over 50 years” or similar formulations: they mean the modern hearing is the first comparable public congressional engagement since the Project Blue Book era and the late-1960s oversight moments that accompanied it (for background, see the National Archives summary cited below).

Calling it Unidentified Anomalous Phenomena (UAP), a government umbrella term for anomalous detections or observations that can’t be immediately identified, makes reporting easier because it sounds like an analysis and operations problem, not a late-night punchline. DoD and intelligence community usage shifted toward UAP in the 2000s as a more neutral label than “UFO,” specifically to reduce stigma and keep the focus on aviation safety and national security reporting rather than pop-culture baggage.

The newer “all-domain” framing tightens that screw even more. It’s not just “lights in the sky” anymore; it’s anything anomalous showing up across operational domains, which forces the question into radar, sensors, training ranges, restricted airspace, maritime activity, and data fusion. Once you treat it as cross-domain operational awareness, the conversation naturally shifts from debating stories to auditing what systems saw, who logged it, and where the data went.

The modern resurgence is basically one arc: 2017 reporting by the New York Times put AATIP in public view, the DoD stood up a UAP Task Force in 2020, the DNI delivered a preliminary assessment in 2021, and 2022 to 2024 brought the creation and ongoing updates around AARO. That sequence pulled UAP out of rumor space and back into the machinery of government briefings, collection priorities, and accountability.

Here’s the nuance people miss: stigma and incentives shape what gets reported. Pilots and operators don’t want to be branded unreliable, officials don’t want to brief uncertainty, and nobody gets promoted for submitting a weird report that creates work and attracts ridicule. That’s why “public clarity” lags behind “internal attention” even when institutions are actively tracking the issue.

So when you see “UFO” replaced by “UAP,” read it as a bureaucratic signal about scope and process: more channels, more data, more oversight pressure. Don’t read it as automatic proof of alien disclosure. The terminology shift tells you the system is trying to treat anomalies as operational risk and intelligence gaps, and that’s a big change all by itself.

Once the government rebuilt those channels, the next question became what was actually flowing through them-and that’s where the headline numbers come from.

What 400 Reports Really Mean

“400 reports” sounds like a bombshell because it feels like 400 separate, confirmed mysteries. The real story is more procedural: how reporting works, who counts what, and how the same underlying event can inflate or shrink the number depending on what’s being tallied. A big number is completely compatible with uncertainty, especially when the inputs are uneven and the data needed to resolve cases is missing or classified.

The All-domain Anomaly Resolution Office (AARO) exists because the government wanted an official intake and analysis lane for UAP across military and intelligence reporting. That “intake lens” matters: AARO is not counting every UFO story on the internet, it’s counting what gets routed into its system, with whatever supporting data arrives attached. If one unit is diligent and another is inconsistent, the totals reflect that reality.

That’s also why broad headlines can mislead. AARO’s most defensible baseline is cumulative: it accumulated 801 total UAP reports from 2019 through 2023. That figure is published in AARO’s Historical Record submitted pursuant to FY2023 NDAA Section 1683 (see AARO, “AARO Historical Record” (Pursuant to Section 1683, FY2023 NDAA), published March 2024, available from AARO’s public site). That number tells you the scale of what entered the pipeline, not how many were “real anomalies,” and definitely not how many were extraordinary.

Here’s the counting snag that trips people up: a UAP report (the intake item) doesn’t map cleanly to a single incident in the real world. One event can generate multiple reports if it’s observed by different crews, different platforms, or different sensors. A pilot sighting plus radar data plus an electro-optical or infrared clip can be logged and tracked in ways that change the count over time, especially if follow-ups get filed later with extra context.

That’s the cleanest way to interpret the “400” number you’ve seen everywhere. It’s commonly cited around the May 2022 moment, when Congress was being briefed and the running total being discussed had reached roughly that scale, as was discussed in the May 17, 2022 House Intelligence Subcommittee public hearing (see the hearing transcript/video linked in the Sources / Further Reading below). Treat “400” as context-specific, basically a snapshot of where the intake stood at that point, not the current total and not a claim that 400 incidents were still unsolved.

“Unresolved” is an evidentiary status, not a conclusion. AARO itself points to plenty of ordinary explanations and false positives that show up in UAP reporting: windborne debris like plastic bags and mylar balloons, and birds. Those are not punchlines, they’re reminders that humans and sensors both get fooled, especially when you’re looking at distant objects against cluttered backgrounds.

The bigger limiter is missing data. In the same AARO Historical Record, a majority of cases have incomplete descriptive metadata: for example, the report notes that 53 percent of cases have morphology recorded as “Not reported” in the available intake fields (see the AARO Historical Record appendix on case-level metadata completeness for the 2019-2023 period). When the basic descriptive field is blank in over half the dataset, you should expect a large unresolved bucket. Add real-world friction like incomplete metadata, inconsistent reporting pipelines across units, and classification that can strip out location, capabilities, or context, and you get a backlog where “unknown” often means “not enough to call it.” Sensor artifacts can stall things too, because a weird-looking track is not the same as a weird object.

Most official UAP reports start where you’d expect: pilots, military operators, and people monitoring systems that detect objects. The supporting information can range from narrative witness descriptions to sensor outputs like radar tracks and EO/IR video. When that supporting package is thin, delayed, or locked behind classification, resolution slows down, and the count of “reports” keeps growing while the number of “explained with confidence” lags.

• What exactly is being counted? Reports received, cases opened, incidents consolidated, or unresolved items?
• What’s the date range? A snapshot (like May 2022) or a cumulative total (like 2019-2023)?
• What data is attached? Just a sighting narrative, or radar plus EO/IR plus timing and location metadata?
• How much is missing or classified? If key fields are “not reported,” unresolved tells you very little.
• What are the common mundane bins? Balloons, birds, and airborne clutter belong in your mental model before anything exotic.

And when those reports stop being distant, ambiguous detections and start being close to aircraft, the stakes shift from curiosity to safety.

The 11 Near Misses

Once a UAP story includes a near-miss, it stops being entertainment and turns into risk management. A radar oddity is interesting. A close-proximity event with an aircraft is a hazard signal, because aviation safety is built around catching precursors before they become accidents.

Safety systems treat a “near miss” as more than a spooky anecdote: it’s an occurrence with potentially important safety-related effects that was prevented from developing into harm. That framing matters because it tells investigators where the system almost failed, even though nobody got hurt.

A Near midair collision (NMAC) is the aviation version of that warning light: if two aircraft, or an aircraft and an unknown object, get uncomfortably close, the industry treats it as a serious event even without an impact. NASA’s Aviation Safety Reporting System (ASRS) treats NMACs as a safety problem and analyzes reports for patterns, including concentration by area, because clusters often point to a repeatable operational or airspace issue, not a one-off fluke.

“11 near-misses” is widely reported in UAP coverage, but that number needs an on-the-record document, testimony transcript, or dataset citation attached to it before you treat it as a confirmed count. In the source materials provided for this section, there isn’t a clean primary reference that states “11,” defines the time window, or spells out the criteria used to label each event as a near-miss. Treat it as “reported as 11” until someone can point to the originating record.

That distinction isn’t pedantic. “Near-miss” can mean anything from a vague “got close” narrative to a formally classified event based on minimum separation criteria used in reporting and investigation. Without the criteria and context, the headline number doesn’t tell you the actual risk level.

In the U.S. system, FAA reporting pathways already exist, and FAA guidance has explicitly pushed UAP reports into established safety channels rather than creating a separate, sensational lane. For certain incidents, operators can also be required to submit formal reports using NTSB forms such as 6120.1 or 6120.2, depending on what happened and who is operating. For clarity: NTSB Form 6120.1 and 6120.2 are pilot/operator aircraft accident/incident report forms used when an event meets the NTSB’s reportable-accident or serious-incident thresholds, so they are relevant to UAP-related events only when the event rises to the level of a reportable accident or serious incident (see NTSB reporting guidance linked below).

Operational context drives both risk and reporting pressure. Training ranges, restricted airspace, and complex multi-aircraft operations pack more jets, more speed, more task loading, and more unusual profiles into the same sky. That raises the odds of proximity events and raises the odds those events get documented, because crews and controllers are already operating inside tighter safety management guardrails.

1. Check the source: Is the claim tied to an FAA/NTSB record, an ASRS report, or a verbatim transcript, or is it just “officials say”?
2. Demand operational context: Where did it occur (range, restricted area, standard airway), and what was the mission complexity?
3. Look for classification details: Does the report reference minimum separation criteria or a formal NMAC label, versus a subjective “felt close” account?
4. Track outcomes: Did it trigger procedural changes, airspace coordination, or updated reporting guidance, or did it vanish after the headline?

If near-misses are the safety hook, the obvious next question is what Congress can actually do about it-and the answer is usually paperwork that forces follow-through.

The Disclosure Laws on Deck

Disclosure is a compliance story. If you want to know whether UAP disclosure is real, watch the paperwork: mandates, deadlines, and record-collection requirements that force agencies to produce something that can be audited later. Viral clips tell you what’s captivating; statutes and compliance memos tell you what the government is obligated to do.

The mechanism Congress uses most often is the National Defense Authorization Act (NDAA), an annual defense policy statute that authorizes funding levels and provides authorities for military and other defense priorities. That “annual” part matters: when UAP oversight gets written into the NDAA, it becomes a recurring reporting and implementation job for DoD and the intelligence community, not a one-off press cycle.

This is also why UAP “disclosure” provisions look less like a transparency dump and more like a records-production pipeline. Disclosure policies can compel the collection of new information, not just the release of old files. That changes the game because agencies have to build processes, not just answer a FOIA request.

The cleanest enacted anchor is the FY2023 NDAA, Section 1683: it requires AARO to produce a Historical Record. That’s the opposite of vibes. A “Historical Record” requirement is a concrete deliverable with an obvious oversight hook: Congress can ask whether it exists, what it contains, how it was compiled, and what categories of records were included or excluded.

The friction is that “produce a record” does not automatically mean “publish everything.” Even when Congress demands reporting, classification and protection of sources and methods can narrow what becomes public. You can get a real compliance product that still has redactions, compartmentalization, and annexes reserved for cleared briefings.

The practical takeaway: treat enacted requirements like Section 1683 as your baseline reality. If you see claims that disclosure is “happening,” your first question should be whether the mandated products are being delivered on time and updated as required, not whether a dramatic anecdote is trending.

Separate from what’s already law, reporting and advocates have pushed a “UAP Disclosure Act” concept, often framed in the Schumer and Rounds era. The text is described as pursuing the expeditious disclosure of UAP records, with mandatory timelines and processes that would push agencies through a structured review instead of letting UAP records sit indefinitely.

In the versions described publicly, the muscle comes from process design: a review-board concept and agency deadlines, with a defined pathway for what gets reviewed and when. That is a big deal if it becomes law, because it turns “we should declassify” into “you have to decide by this date, using this process.”

The catch is negotiation. Timelines get watered down, authorities get narrowed, and carve-outs expand when bills move from headline language to final text. So treat “it would require” as conditional until the final enacted language matches the promise.

On the whistleblower lane, H.R.10111 (118th Congress) was introduced to provide whistleblower protections for federal personnel disclosing the use of federal taxpayer funds to evaluate or research UAP. Introduced is not enacted, but it signals where lawmakers are trying to reduce the personal risk that keeps people quiet.

1. Check the verb: “requires” and “shall” in enacted law are different from “would” in a proposal. Start by asking: is it already in force, or is it still an idea?
2. Track the deliverables: look for the Section 1683 Historical Record, updates to it, and any related briefings or annexes referenced in oversight conversations.
3. Audit the deadlines: when proposals promise timelines, watch whether final language keeps them, and whether agencies meet them. “Disclosure” usually means controlled release through a process, not a sudden data dump.

If you keep your eyes on mandated products, missed deadlines, and whether briefings and records actually materialize, you’ll see disclosure progress long before social media agrees on what it means.

Paperwork, though, isn’t the only way this issue moves. The other accelerant is a person with access deciding to go on the record.

Whistleblowers Versus Official Silence

Whistleblower claims are the fastest way UAP stories escalate, because they swap vague sightings for a simple accusation: someone inside the system says there’s a cover-up. The catch is that this is also where the public evidence gap is widest. You get names, job titles, and official attention, but the key materials are usually locked behind classification, NDAs, and compartmented programs.

Public employees also have a right to communicate privately with Congress, which is why these stories can jump straight from rumor to “briefed lawmakers” without you seeing a single photo, memo, or sample. And for Intelligence Community cases, the Intelligence Community Inspector General (ICIG) is the pipeline that lets classified allegations be made as protected disclosures and routed into oversight or referred to Congress without becoming public immediately.

On the record, David Grusch is identified as a former National Reconnaissance Officer Representative, and he provided sworn testimony. Those points are publicly checkable: his role, that he testified under oath, and that Congress took the claims seriously enough to hear them.

What stays in the “alleged” bucket is the headline substance. Grusch stated that, according to his knowledge, the U.S. collected debris from crash sites of “non-human” craft. Separate media reporting also described claims about “non-human biologics,” reported July 27, 2023. Reporting further notes that he provided Congress and the ICIG with extensive classified information. That last part is a big deal procedurally, but it still doesn’t give the public anything concrete to evaluate.

Here’s the credibility bottleneck in plain language: oversight bodies can verify that a person with access made a complaint, testified under oath, and provided supporting material in classified form. They can even assess consistency across witnesses and documents. But you can’t independently confirm what those materials show if you can’t see them.

That’s why “I told Congress in classified form” is meaningful and unsatisfying at the same time. Meaningful, because Congress can compel briefings, compare accounts, and follow money and program authorities. Unsatisfying, because the public hears a conclusion without the underlying evidence. The ICIG’s statutory whistleblower protections for Intelligence Community employees and contractors reporting fraud, waste, or abuse are designed to protect the reporting channel, not to publish the payload.

1. Separate what’s confirmable (job role, sworn testimony, complaint/briefing exists) from what’s alleged (craft origin, bodies, reverse-engineering).
2. Demand firsthand clarity: did the source personally see materials, or are they relaying what others told them?
3. Look for named programs, dates, offices, contract vehicles, and where the evidence supposedly sits; vagueness is where exaggeration thrives.
4. Check for corroboration: multiple on-the-record officials, documents released, or independent confirmations, not just “people familiar.”
5. Track official process signals: inspector general actions, documented referrals, and whether Congress says it reviewed specific records in a classified setting.
6. Hold two truths at once: whistleblowers face real career and legal risk, and incentives to overstate significance also exist. The investigation pathway matters, but allegations still aren’t proof.

Whether the pressure comes from laws or from whistleblowers, the next tell is the same: do you get primary material and deadline-driven follow-up, or do you just get louder claims?

What to Watch Next

The next phase of UAP disclosure won’t look like a Hollywood reveal. It’ll look like scheduled briefings, recurring reports, and agencies either hitting mandated milestones or getting called back to explain why they missed them.

The cleanest “what happens next” anchor is already bureaucratic: the NDAA directs expanded congressional briefings related to UAP. If you’re trying to stay grounded, track whether those briefings happen on time, whether members describe getting specific materials (not just oral summaries), and whether follow-up requests produce documents.

Expect ambiguity and delays. Drafts change, timelines slip, and agencies lawyer their way through wording. That’s normal in oversight fights, so don’t let it whiplash you.

One concrete signal, clearly not final: a Senate committee draft of the fiscal 2026 NDAA reportedly includes multiple provisions that would impact the Pentagon. “Draft” is the key word. Treat it as a direction of travel until it’s enacted and implemented.

If UAP Disclosure Act style mechanisms ever advance and are enacted, the model people describe is straightforward: a Review Board plus agency submission and declassification milestones. The only thing that matters is whether the deadlines are real and enforced.

Disclosure progress shows up as new primary material, not recycled chatter. Strong disclosure policies force collection and production of new information, not just access to what already exists.

1. Look for primary documents: filings, letters, directives, and released datasets.
2. Verify hearing transcripts and written Q&A, not secondhand summaries.
3. Track inspector general actions and referrals, because they create paper trails.
4. Check deadline compliance: was the deliverable posted, briefed, or formally logged?
5. Ignore recycled clips, anonymous “insiders,” unsourced numbers, and headlines like “UFO sightings 2026” with no underlying data.

Oversight isn’t about satisfying curiosity. It’s about aviation and national security safety, public trust in institutions, and giving science something solid to evaluate. The boring deliverables are the point, because they’re how accountability actually happens.

Conclusion

The May 2022 hearing mattered because it shifted UAP talk from rumor to process. The most responsible stance stays simple: track the evidence pipeline, not the vibes.

On the numbers, keep your anchors straight. AARO has reported 801 accumulated reports from 2019 to 2023, which is the scale baseline the government is actually publishing (see AARO Historical Record citation in Sources / Further Reading). The “400 reports” figure belongs to the May 2022 moment and shouldn’t be treated as the current total. And the urgency argument isn’t “aliens,” it’s safety: near-miss reporting is a recognized leading indicator in safety contexts, so even imperfect near-miss data deserves serious attention. The oft-repeated “11 near-misses” claim is still uncorroborated in the public record discussed here, so treat it as a lead to verify, not a settled fact.

When the next UFO disclosure or UAP disclosure headline hits, do three things: pull the primary document, check whether it ties to mandated AARO and NDAA-driven reporting and briefings (in force), and demand sourcing on every number. If it’s about a Disclosure Act style review board, timelines, or added whistleblower expansions, read it as proposed until enacted. If you want updates when the next official report drops, subscribe for the filings, not the frenzy.

Frequently Asked Questions