Gillibrand Questions AARO Director Kosloski at 2024 Senate UAP Hearing

You’ve seen this movie: another “UFO news” cycle blows up, clips fly, hot takes multiply, and you’re left asking the only question that matters. What actually changed in the 2024 Senate hearing, and what was just noise? This article is an oversight-themes analysis of that hearing and the public record it produced, focused on what was asked, what was answered on the record, and what the public documents show about institutional gaps.

The stakes are simple when trust is low. If the public record does not move, you are not getting new clarity, just new content. That is why this piece tracks oversight themes rather than chasing soundbites: process and documents beat vibes every time.

The complication is also obvious: a public hearing collides with institutional limits. The record you get is shaped by what the witness is allowed to say in open session, what is documented in a form that can be shared, and what questions are answered cleanly versus routed into procedural side channels. You can feel that tension even when no one says it out loud.

The witness here leads the All-domain Anomaly Resolution Office (AARO), the U.S. government office tasked with detecting, tracking, analyzing, and managing reports of unidentified anomalous phenomena across domains. Its scope is explicitly all-domain-airborne, seaborne, spaceborne, and transmedium-so the director sits at the intersection of sensors, reporting, and interagency coordination. Jon T. Kosloski serves as Director of AARO.

If you want to verify what happened without living off screenshot threads, anchor yourself to source-of-record material: official committee hearing pages often host the video and posted materials, and written transcripts can appear later as official publications through the Government Publishing Office on govinfo and then on Congress.gov once published.

That’s the lens for the rest of this piece: track what was asked, what was actually answered on the record, what was sidestepped, and what verifiable outputs follow.

What Congress Wants From AARO

That lens matters because Congress isn’t chasing “aliens on C-SPAN.” It’s trying to make UAP oversight boring: repeatable processes, auditable records, and answers you can track across quarters instead of viral clips. That’s why the most revealing parts of a hearing are often the least cinematic, like what gets logged, who gets notified, and whether follow-ups come back in writing.

In Congress-world, accountability lives in paperwork: formal Questions for the Record (QFRs) after officials testify and written agency responses that can be compared year over year. That’s the muscle memory lawmakers want around unidentified anomalous phenomena (UAP), because standardized intake and standardized replies are how you separate “we saw something” from “we can reproduce this analysis and defend it in an oversight file.”

The friction is that the raw material is messy. Reporting often starts as a short, stressed observation from a cockpit or a sensor operator, and a lot of cases turn out to be ordinary clutter like balloons, drones, or sensor artifacts. Congress still wants the boring breakdown: how many were resolved, how many were misidentified, and how many remain truly unknown after you’ve exhausted the obvious categories.

Sen. Kirsten Gillibrand’s role here is framework-builder, not vibe-checker. She introduced amendment SA.4281 to the FY2022 National Defense Authorization Act (NDAA) and publicly announced its inclusion. That amendment expanded on Section 1652 by setting up the office structure that became today’s AARO, and the FY2022 NDAA is credited to Gillibrand and Sen. Marco Rubio for creating the Anomaly Surveillance and Resolution Office / All-domain Anomaly Resolution Office construct that forces DoD to treat UAP as an oversight problem, not a watercooler topic.

That oversight mindset also explains why Congress cares about official artifacts like hearing publications and transcripts. Those documents create a stable record of what was promised, what was answered, and what got punted to classified channels, which is exactly what audit-friendly oversight needs.

Language has shifted for a reason: public and official usage now leans toward “UAP” instead of “UFO,” because it’s a broader bucket that fits weird radar tracks, undersea anomalies, and unresolved sensor events without smuggling in the cultural baggage that “UFO” carries.

Same deal with “disclosure.” In Congress terms, disclosure is a process: mandated reporting to committees, standardized intake so cases can be compared, and clear release pathways for whatever can be made public after classification review. It’s oversight plumbing, not a promise that the government is about to confirm extraordinary claims.

The phrase “non-human intelligence” is where hearings can start talking past each other. Available documents mention the term, but they do not include an official statutory, DoD, or ODNI definition, so witnesses and senators can use the same words while meaning different things, which makes accountability harder, not easier.

Progress should look like consistent reporting artifacts, measurable closure categories, documented cross-agency cooperation, and a public release process that reliably produces declassified updates on a predictable cadence.

Gillibrand’s Sharpest Lines of Questioning

That’s the backdrop for why Gillibrand’s questions land the way they do. Her most important move isn’t chasing beliefs about UAP-it’s forcing the conversation into testable oversight: what can you measure, store, corroborate, and report in a way that survives scrutiny.

No verbatim transcript was available at time of writing, so what follows is a themes-level summary of the oversight targets, not quotes.

Her intake-and-standards theme is basically: if your front door is messy, everything downstream becomes vibes. Congress has already mandated a publicly discoverable and accessible process for safe disclosure, and the Pentagon has announced a secure reporting mechanism for U.S. government personnel to report to AARO, which sounds like the hard part is done. The catch is that “a pathway exists” does not guarantee reports are collected with consistent fields, triaged against the same criteria, and documented in a way that lets Congress compare apples to apples across months, bases, and commands.

A good answer looks like a single, defined intake workflow with explicit minimum data requirements, consistent triage categories, and a way to show Congress that cases do not mutate just because they entered through different doors.

The second theme is sensor corroboration: if a case is real enough to brief, it should be real enough to cross-check. Congress directed AARO to use data sources to determine whether reported phenomena have a discernible signature, which is oversight-speak for “stop treating each incident like a campfire story and start treating it like an analytics problem.” The friction is that sensor stacks are not uniform, data quality varies wildly, and even when you have multiple streams, they do not always line up in time, geometry, or calibration, so “corroborated” can quietly become “we have more than one blurry thing.”

A good answer looks like clear criteria for multi-source corroboration and a concrete plan for signature work that produces repeatable patterns, not just one-off narratives.

Theme three is evidence handling and traceability: what happens to the report after it’s filed. Public expectations about “UAP disclosure” often collapse into a single question, “What do they know?”, but Congress is aiming at something more boring and more powerful: can the system preserve what’s reported so it can be audited later. The complication is chain-of-custody in the real world, data lives in different systems, attachments get stripped, and context gets lost when a case gets reclassified, re-routed, or summarized into a slide.

A good answer looks like an end-to-end record that keeps original submissions and associated data linked, time-stamped, and reviewable so an outside auditor can reconstruct what AARO saw and when.

Her cooperation-and-access theme is the one that decides whether the whole project is real or performative. People hear “Pentagon office” and assume AARO can just pull whatever it wants from across DoD and the Intelligence Community. The practical limit, based on available public documents, is straightforward: none of the publicly available documents establishes AARO’s authority to compel information from DoD components or the Intelligence Community, and the referenced materials in those documents do not supply statutory or directive language that would answer that gap directly.

That matters because voluntary cooperation fails in predictable ways: slow-walking, partial production, “we searched and found nothing” with no ability to verify, and cross-agency “equities” that keep the most relevant data out of the room. If Congress cannot tell whether AARO is seeing everything it is supposed to see, then the public cannot tell whether non-answers are due to emptiness, bureaucracy, or refusal.

A good answer looks like named data-holders, defined access agreements, and a way to report cooperation rates and gaps without laundering them into bland reassurances.

She also uses classification friction as a question-driver, not as a legal seminar but as a reality check. The public wants clarity, but classification routinely blocks public-facing specificity, which can make every denial sound like a dodge and every vague answer sound like a cover-up. The nuance is that “we cannot say” becomes a habit unless there is a disciplined process for separating what must stay protected from what can be released without harming sources, methods, or operations, and for proving that the classified material is still being investigated seriously.

A good answer looks like a repeatable way to produce public outputs that track the same underlying cases and metrics Congress sees, even if details are abstracted.

Put together, these themes signal what Congress thinks is broken: not a lack of stories, but a lack of infrastructure. Gillibrand is pushing AARO to behave like a modern investigative and analytics shop, with a public-facing reporting pathway, a secure channel for government personnel, signature-driven use of data sources, and records that can be audited, while also surfacing the hard limit that access and cooperation can bottleneck everything. If you want to judge “UAP disclosure” like an adult, judge it by whether those systems produce consistent, corroborated, auditable outputs-not by whether a hearing produces dramatic lines.

Kosloski’s Answers and Their Gaps

Those demands are the standard Kosloski is being measured against, and they also explain why his public-facing posture can read as unsatisfying. The tension in Kosloski’s posture, at least as it shows up in what AARO can put on the public record, is “process first, proof later.” That plays well inside a security bureaucracy because it prioritizes chain-of-custody, sensor provenance, and analytic standards. It plays terribly in a public hearing where people came for one thing: show the evidence. So the answers you tend to hear sound like guardrails instead of revelations, and that’s exactly where public trust gets stressed.

The cleanest reality check is the unclassified dataset AARO and ODNI released with their report: 366 UAP sightings examined, and 171 still listed as uncharacterized. (See All-domain Anomaly Resolution Office and Office of the Director of National Intelligence, “Unidentified Anomalous Phenomena: Unclassified Report,” published June 2024; the unclassified dataset and summary tables correspond to the May 1, 2023 to June 1, 2024 reporting period and are available in the public unclassified report posted by ODNI/AARO.) That single data point does two jobs at once. First, it shows AARO is operating in a data-driven, scientific framework, meaning cases move based on what the reporting, sensor data, and corroboration can actually support, not on vibes. Second, it puts a hard number on the gap between “we looked” and “we can explain”: almost half the examined cases, in that unclassified slice, still did not have enough resolved information to put them in a named bucket publicly. If you’re trying to interpret hearing answers, start here. The official record already admits limits in available data or analysis, even before classification enters the picture.

Public hearings collide with a basic structural problem: the person testifying is often not the person who can authorize release. Original Classification Authority (OCA) is the role that makes the initial call that specific information must be classified to protect national security, and that authority lives where the information originated, not automatically where it gets discussed later. Even when information is eligible to become public, automatic declassification only kicks in when a date or event set by the original classifier is reached, which means “we cannot discuss that here” can be a timing and authority issue, not a dodge. When people want receipts anyway, Mandatory Declassification Review (MDR) is the formal pathway: a structured request to review classified records for possible declassification and release. That process exists precisely because public confirmation and denial are constrained, and because declassification is a governed decision, not something a director can improvise at a microphone.

When you hear procedural answers, references to ongoing work, or limits tied to classification and interagency equities, treat them as signals about what is releasable, not as proof of what’s true. “No evidence presented publicly” is not the same statement as “evidence does not exist.” The first describes the current public record; the second claims certainty about everything behind closed doors, and nobody in that room can responsibly make that leap either way. The grounded way to listen is to keep two rails in view at the same time: the unclassified dataset tells you what AARO has been able to document and characterize openly, and declassification mechanisms like MDR tell you what the system uses when it’s time to move specific material into daylight. That keeps you out of the two traps that hearings tend to trigger: cynicism that assumes every non-answer is a cover-up, and wishful thinking that treats every non-answer as confirmation.

How This Fits the Whistleblower Era

If Kosloski is stuck defending the limits of the public record, the obvious next question is where new, checkable information is supposed to come from. The Gillibrand Kosloski exchange lands differently because the UAP conversation has moved into a whistleblower era. Attention isn’t the bottleneck anymore. Protected reporting and verifiable documentation are. A hearing can surface sharp questions, but it cannot substitute for records that can be audited, cross checked, and lawfully shared.

That’s why this Senate hearing, officially titled “To Receive Testimony on the Activities of the All-domain Anomaly Resolution Office,” felt like part of a longer chain rather than a one off spectacle. It took place on November 19, 2024, and Kosloski delivered roughly 40 minutes of testimony (see the official U.S. Senate committee hearing listing for “To Receive Testimony on the Activities of the All-domain Anomaly Resolution Office,” Nov. 19, 2024, for the hearing record and posted materials).

Place that next to the most famous recent UAP whistleblower moment: David Grusch testifying under oath at a House Oversight Committee hearing. Under oath, Grusch said he believes the U.S. has possibly had knowledge of non-human life or craft. The important nuance is how he framed it. He presented key allegations as second hand, rooted in what others told him, not in artifacts he personally handled in public view. And while he had previously claimed he’d heard accounts that people were killed to maintain secrecy, he did not repeat the “people were killed” allegation at the hearing, per available summaries.

That gap between “credible enough to investigate” and “provable in public” is also why public pressure never really drops. A wider ecosystem of advocates and amplifiers, including Lue Elizondo, Christopher Mellon, and George Knapp, keeps the topic in the public eye. They are not the point here as personalities. They are the reason the demand signal stays high even when the evidence pipeline stays constrained.

If you want allegations to turn into evidence, whistleblower protections are the hinge. For many federal employees and applicants, the Whistleblower Protection Act, 5 U.S.C. § 2302(b)(8), creates a defined retaliation shield for protected disclosures. That legal baseline changes the risk calculation: people can report and keep their careers.

The complication is subtler than a blanket exclusion. Certain Intelligence Community employees and contractors do not have the same remedial rights under the Whistleblower Protection Act; instead, IC-affiliated personnel use IC-specific processes established by Presidential Policy Directive 19 and implemented through the IC Inspector General and other IC mechanisms. See Presidential Policy Directive 19, “Protecting Whistleblowers with Access to Classified Information” (Oct. 10, 2012), for the framework establishing IC-specific reprisal and review processes: https://obamawhitehouse.archives.gov/the-press-office/2012/10/10/presidential-policy-directive-strengthening-protections.

That process is real, but it is also structurally less visible to the public, which means even serious, well routed disclosures can produce outcomes you cannot easily point to on a public docket.

That legal split feeds directly into AARO’s two layer reality: a public layer that can be cited, and a classified layer where the most specific sourcing and methods often live. The public layer is what you can inspect without clearance, and it’s why AARO’s “Official UAP Imagery” page matters. It’s an auditable surface area: you can see what’s been released and how it’s being described.

The friction is that a lot of the strongest material, if it exists, will come in through classified reporting, often from operational commands. AARO’s imagery page even references submissions from military commands, including an example tied to a United States European Command submission. That’s exactly the kind of provenance that can be investigated thoroughly while still being hard to litigate in public.

Takeaway: if you want claims to become evidence, demand two things every time: confirmation that disclosures went through protected channels (including IC IG processes like PPD-19 where applicable), and some piece of the story that becomes an auditable public record, such as officially released imagery, formal reports, or documented Inspector General determinations.

The Real Levers for UAP Disclosure

Whistleblowers can raise the pressure, but Congress still needs levers that work even when nobody can talk freely in public. If you want “UAP disclosure” to move, the levers are painfully unglamorous: an annual reporting cadence you can track, classification guide audits that decide what can be said out loud, appropriations pressure that forces prioritization, and mandates with deadlines that create consequences for non-compliance.

The reporting model itself is built as a two-track system. The Department of Defense released an annual UAP report covering May 1, 2023 to June 1, 2024. A classified report was submitted to Congress, and an unclassified version was published publicly. If you’re trying to stay anchored to what’s official, the unclassified report is available on dni.gov and also on defense.gov and aaro.mil.

That split is the whole game. The classified channel is where detail can live without compromising sources and methods. The unclassified channel is where the public record is built. If the unclassified report gets thinner, later, or more vague, that’s not “the internet being impatient.” It’s a signal the pipeline is clogged.

The hearing gave you the human tension. The mechanism that turns tension into repeatable accountability is the National Defense Authorization Act (NDAA) UAP provisions, because NDAA language is the strongest recurring lever Congress has: requirements get written down, deadlines get attached, and compliance hooks get renewed year after year.

Here’s the kind of mandate that matters in practice: the NDAA requires AARO to account for all security classification guides governing UAP-related reporting and investigations. That sounds inside-baseball until you’ve felt the “classification friction” firsthand, where everyone claims they are being transparent while the rules about what can be shared are scattered across components and compartments.

Accounting for those guides is how you find the real choke points. If AARO cannot name which classification guides control UAP reporting, it cannot consistently challenge over-classification, standardize what analysts are allowed to say, or explain why one office can brief a detail that another office claims is untouchable.

Senator Schumer’s UAP Disclosure Act enters the conversation at the intent-and-structure level. The stated purpose in the Senate amendment is expeditious disclosure of unidentified anomalous phenomena records, and reporting on the effort describes mandatory timelines and processes for declassification.

The catch is the one you already recognize: “intent to disclose” can still get trapped in classification guides, slow coordination cycles, and uneven interagency compliance. The value of that push is that it frames disclosure as a process with clocks and procedures, not a vibe or a press conference.

• Release timing: does the next annual report arrive on a predictable schedule, or does it drift later each year?
• Two-track consistency: do officials explicitly acknowledge both outputs each cycle (classified submission to Congress plus an unclassified public report), or does one quietly disappear from the narrative?
• Classification guide accounting: do disclosures about the set of UAP-related security classification guides get more complete over time (more specificity, fewer hand-waves)?
• Stable case taxonomy: do case categories and definitions stay consistent year over year so trends are comparable, or do shifting labels make the numbers impossible to track?
• Interagency participation: does the report reflect broad contributions across DoD and the Intelligence Community, or does it read like a single office reporting in a vacuum?

Stay anchored by treating official outputs like a ledger: pull the unclassified annual report from dni.gov, defense.gov, or aaro.mil, note the covered date range and publication date, and track whether mandated items like classification guide accounting are getting clearer or staying stuck. Headlines come and go. The paperwork trail tells you whether disclosure is actually moving.

What the Hearing Really Revealed

All of that brings you back to the question from the start: what actually changed, and what was just noise. The hearing’s real reveal was the mismatch between a public that wants clear, testable answers and a government process that delivers slowly, through classification filters and compliance paperwork.

Gillibrand kept steering the conversation toward standards and sensor-backed accountability, while Kosloski described an environment where “process” often outruns “proof” and where even the anchor numbers (366 examined, 171 still uncharacterized) underline how much sits in limbo. The whistleblower-era pressure is real too, but it is bottlenecked by protected channels and verification requirements, plus different protection regimes depending on who you are and where you work (WPA vs PPD-19). One constraint upfront: no verified verbatim transcript excerpts for the Gillibrand to Kosloski exchange were available at time of writing, so this conclusion is drawn from documented mandates and official outputs that can be checked in official postings, transcripts, and follow-up mechanisms like QFRs.

Progress will not look like a single “disclosure moment.” It looks like measurable execution: annual unclassified reports plus classified submissions arriving on cadence, secure and public reporting pathways that are visibly implemented (not just described), and NDAA-style mandates that force accounting for classification guides so Congress can measure what is being withheld and why. Oversight is cumulative, and congressional committees have signaled continued pressure through planned hearings on UAP transparency and whistleblower protection.

If you want to stay grounded, ignore the noise and track three signals: the yearly unclassified reports plus classified submissions, proof of working secure and public reporting routes, and real follow-through on classification guide accounting, using primary sources like GovInfo and Congress.gov for receipts.

Frequently Asked Questions