Overview

On 31 March 2026, Representative Anna Paulina Luna, chair of the House Oversight Committee's Task Force on the Declassification of Federal Secrets, sent Secretary of War Pete Hegseth a four-page letter requesting a specifically enumerated set of military UAP videos.

The Committee made the letter public on 1 April. Unlike a general demand for “all UFO files,” it named individual recordings by incident, callsign, date or uploader-defined title and requested delivery to the Task Force as soon as possible and no later than 14 April 2026. House Committee on Oversight and Government Reform — 31 March 2026 UAP request letter House Oversight — Luna Continues Transparency Investigation into UAPs

The list contained 46 numbered request items, several of which themselves specified multiple videos. The names ranged from immediately recognisable descriptions such as “4 UAP formation – Iran, 8/26/22,” “Syrian UAP instant acceleration, 2021,” “Cigar-shaped or fat spherical UAP, 10/15/22,” and the 2023 Lake Huron shootdown footage, to operational labels such as Wiley 2X Zinc, Warlock 4X, Hackney 6, Toxic 6, Hellhound 1X, Greed, Mad Dog 31 and Regulator 73. House UAP request letter

This specificity transformed the oversight problem. A defined request permits concrete questions about whether a record exists, who controls it, which restrictions apply, whether Congress received it privately, whether a public version followed, whether that version is native or derivative, which metadata accompany it and why any record remains withheld. That is more useful than debating an undefined body of alleged government UAP material.

The event became even more consequential because many titles overlapping the House list appeared publicly several weeks later through the Department of War's PURSUE Release 02 and AARO's Presidential UAP Transparency Initiative. Those releases included the Iran formation footage, Syrian “instant acceleration” clip, “cigar shaped or fast spherical” clip, spherical UAP videos, Coast Guard “Tic Tac” footage, the claimed USO-near-submarine recording and the Lake Huron shootdown video. AARO — UAP Report Documents Department of War — PURSUE Release 02

The chronology requires care. AARO’s metadata says the responsive files were identified after a separate 6 March 2026 request by eight House members for access to 51 potentially UAP-related records, and does not describe the 22 May public release as a direct response to Luna’s later letter. AARO — Presidential UAP Transparency Initiative The two requests overlap within the same transparency campaign, but the public record does not support attributing Release 02 to the March 31 letter alone.

Chronology

9 September 2025 — House UAP transparency hearing.
Witness testimony contributes to the Committee’s belief that further video records exist.

6 March 2026 — separate House request.
Eight House members ask AARO for 51 potentially UAP-related records.

31 March–1 April 2026 — Task Force letter and announcement.
Luna requests 46 numbered video-record items, with a 14 April requested deadline.

22 May 2026 — PURSUE Release 02.
AARO and the Department of War make many related records publicly accessible.

Congressional request and oversight

September 2025 context

The letter explicitly connects the request to the House Task Force's 9 September 2025 hearing on UAP transparency and whistleblower protection.

Luna wrote that whistleblowers had informed the Task Force that AARO possessed additional video records of potential UAP sightings and that the Committee wanted the specific files in order to continue its investigation. House UAP request letter

The 2025 hearing had concentrated heavily on access. Witnesses and lawmakers argued that the Department of War and Intelligence Community possessed material that Congress and the public had not been allowed to examine adequately. Luna also criticised AARO's responses to previous congressional inquiries. The March letter converted that dissatisfaction into a records-production request. This matters because the event was not itself a scientific finding about the listed videos. It was an oversight action generated by testimony that more records existed than had been publicly released. The evidential sequence therefore begins with a claim about government custody. Scientific interpretation comes later.

Requested record set

The request is often described as a demand for “46 videos.” That is approximately correct as shorthand but technically imprecise. The letter contains 46 numbered items. Several entries include multiple sub-videos. For example, the Spherical UAP Warlock 4X entry requests Video 0, Video 1 and Video 2. The Hackney 6 / Toxic 6 entry dated 2 November 2020 requests two videos. Another Toxic 6 / Hackney 6 entry from 31 August 2020 also specifies two videos. House UAP request letter A numbered request item can therefore correspond to more than one digital file. The same underlying sensor recording can also appear in multiple versions—original, edited, zoomed, colour-adjusted or duplicated under different uploader-defined names. AARO's later public records show this problem directly.

It has identified instances where two differently titled uploads were actually duplicates of the same underlying footage. For accountability, record count and incident count should therefore remain separate. A committee can request 46 named items without that meaning 46 independent physical events.

Record titles

Many names in the letter sound as though the physical nature of the event had already been established. “Instant acceleration.” “In and out of water.” “Erratic movement.” “Tic Tac.” “Formation.” “Cigar-shaped.” The later AARO releases reveal why those labels require caution.

For many of the May 2026 files, AARO explicitly identifies the name as an uploader-defined title attached before the media entered the classified network on which AARO later found it. The office repeatedly states that its descriptive captions should not be interpreted as analytical judgments or factual determinations about the nature or significance of the event. AARO — UAP Report Documents

This creates a subtle but important distinction. The House was correct to use exact titles when requesting records. A records request needs enough specificity for custodians to locate the item. That does not mean Congress was validating the wording. If a government network contains a file named Syrian UAP instant acceleration, the committee can legitimately ask for that exact file while remaining agnostic about whether physical instantaneous acceleration occurred. Search terminology and scientific conclusion are different things.

Separate March request

AARO's public May material repeatedly includes the same contextual note. On 6 March 2026, eight members of the U.S. House of Representatives requested access to 51 potentially UAP-related records allegedly held by the Department of War and Intelligence Community. AARO says it then identified a collection of responsive materials on a classified network. Many lacked a substantiated chain of custody. AARO — Presidential UAP Transparency Initiative This earlier request is crucial to interpreting the March 31 event. The publicly available AARO metadata does not identify Luna's March 31 Task Force letter as the originating request for the May 22 file set. Instead, it repeatedly cites March 6. The safest reconstruction is therefore that congressional pressure operated through multiple overlapping requests.

The March 31 letter publicly formalised and enumerated a large group of desired records. The March 6 request is the one AARO explicitly links to the later responsive material. It is possible that many titles derived from the same underlying list supplied by congressional or whistleblower sources. The public record reviewed here does not establish the exact internal relationship between the two requests. That uncertainty should remain visible.

Deadline and public record

Luna asked for delivery no later than 14 April 2026. The publicly available House Oversight material reviewed through 26 August does not include a posted Department of War response letter demonstrating whether the files were delivered privately to the Task Force by that deadline. This is an important limitation. Congressional committees routinely receive classified or non-public productions that do not appear on public websites. The absence of a public delivery record therefore does not prove that the Department failed to comply. Likewise, the later appearance of overlapping videos on 22 May does not prove that the April deadline was met. The public record supports two separate statements: the Committee demanded delivery by April 14; and many overlapping records became publicly available on May 22.

Whether classified congressional access occurred between those dates is not established by the public sources reviewed here. That is a narrower conclusion than calling the deadline either complied with or ignored.

Public release and requested records

Release 02

PURSUE Release 02 was published on 22 May 2026. AARO simultaneously made a large set of military video records available through its Presidential UAP Transparency Initiative and UAP Report Documents interface.

The release dramatically changed the evidential position of the March request because the public could now inspect many of the named files directly. Department of War — PURSUE Release 02 AARO — Presidential UAP Transparency Initiative

The scientific result was not a wave of confirmed extraordinary cases. In many instances, the release made the limitations of the material clearer. AARO disclosed incomplete custody histories. It noted prior digital alteration. It separated uploader titles from neutral descriptions. It described sensor panning and zoom changes capable of influencing apparent motion. This is an important form of transparency. A public file can become less mysterious when its provenance is known. The value of disclosure is not limited to finding evidence in favour of an extraordinary interpretation.

Record-level evidential limits

Iran formation video

The first item in Luna's list was “4 UAP formation – Iran, 8/26/22.” AARO released it as DOW-UAP-PR050. The office assesses that the footage was likely derived from an infrared sensor aboard a U.S. military platform operating within the CENTCOM area of responsibility in 2022. The video shows several areas of contrast moving through the field of view. AARO says a user uploaded the media to a classified network in June 2024. AARO / DVIDS — DOW-UAP-PR050 The word formation remains descriptive. The public file does not provide the range information necessary to prove that the image-plane objects were physically close together in three-dimensional space or moving as a coordinated formation. They may have been. The released video alone does not establish it.

The House request was therefore successful in making a named piece of evidence available for scrutiny, while the scrutiny itself did not validate the title's strongest implication.

Syrian video

The second listed item became DOW-UAP-PR051. This is one of the clearest examples of why exact video titles should not be treated as conclusions. AARO says the footage was likely derived from a U.S. military infrared sensor operating in the CENTCOM area in 2021. The media had been digitally altered before it was uploaded to the classified network in June 2024. The released file contains replays, enhancement and changes in display treatment. Most importantly, AARO's own timeline says that at the moment of the apparent rapid departure the sensor stops tracking the area of contrast, causing it to rapidly exit the right side of the frame. AARO / DVIDS — DOW-UAP-PR051 This does not establish that the underlying object was conventional. It means the public clip does not establish instantaneous physical acceleration.

A change in camera tracking can generate rapid image-plane displacement without extraordinary target motion. The House's request was valuable precisely because public release allowed the title to be compared with the sensor description.

Morphology and alteration

The fourth request item appeared publicly as DOW-UAP-PR053, titled “Cigar Shaped or Fast Spherical UAP clip 15 OCT 22.” AARO says the file was likely derived from an infrared sensor on a U.S. military platform operating in CENTCOM in October 2022. It had been digitally altered before upload to the classified network. The public version contains a short transit with slowed replay. AARO — UAP Report Documents The title itself exposes the uncertainty. Was the object cigar shaped? Was it spherical but motion blurred? Was the displayed elongation a sensor or processing effect? Without the native source and adequate range information, those possibilities cannot be separated confidently. The record request makes the footage visible. It does not turn image morphology into physical morphology.

Apparent movement

The fifth request item, “Spherical UAP erratic movement remix (RUST), 2022,” is especially instructive. AARO's public entry says the media had been digitally altered before upload and warns that the alterations significantly influence the area's apparent performance characteristics. The video is associated with DOW-UAP-PR054 in AARO's public records. AARO — UAP Report Documents This is a direct demonstration of why the coding AI should not convert file titles into website taxonomy labels without reading the provenance notes. An uploader can call a file “erratic movement.” An analyst still has to determine how much apparent motion belongs to the target, camera, edit, stabilisation or replay process. Release without provenance would have preserved the mystery. Release with provenance changes the evidential question.

Coast Guard records

Items 13 and 14 requested two U.S. Coast Guard C-144 recordings from 24 April 2024, each carrying “Tic Tac” wording. AARO later released DOW-UAP-PR065 and PR066. It assesses the videos as likely derived from an infrared sensor aboard a U.S. Coast Guard platform operating in the southeastern United States. A user uploaded them to a classified network in June 2024. DVIDS — PR065 AARO — UAP Report Documents The public descriptions are deliberately neutral. They record areas of contrast and sensor panning. They do not state that a physical white oblong craft with the dimensions implied by the cultural term “Tic Tac” was established. The label is useful for locating the requested file. It should not become evidence by repetition.

Submarine footage

Item 15 requested “Multiple Spherical UAP USO near Sub. Cactus 1X in and out of water, 3/25/22.” AARO later released DOW-UAP-PR067. The uploader-defined title contains two strong interpretations: the objects are USOs; and they move in and out of water. AARO's public description is more restrained. It describes areas of contrast entering and leaving the sensor field of view while the sensor pans. The public metadata does not itself establish a physical crossing of the air-water interface. AARO — UAP Report Documents A transmedium claim requires more than apparent proximity to the sea. Investigators need three-dimensional position and a reliable relationship between the line of sight and water surface. The House request brought a high-interest title into the public evidence chain.

AARO's publication demonstrates that the title's strongest interpretation still needs to be tested rather than assumed.

Lake Huron engagement

Item 19 requested footage of the 12 February 2023 Lake Huron shootdown.

The incident had already attracted exceptional public attention because a U.S. Air National Guard F-16 shot down an unidentified object over the lake during the series of North American high-altitude-object incidents that followed the Chinese surveillance balloon episode.

AARO later released the requested video as DOW-UAP-PR071. Its uploader-defined title describes an F-16C shooting down a UAP with a weapon system. AARO assesses that the clip was likely derived from an infrared sensor aboard a U.S. military platform operating in the NORTHCOM area of responsibility.

Its neutral description says the footage appears to depict a kinetic interaction between two areas of contrast, after which the initial subject fragments in a radial displacement pattern suggesting a high-energy event. DVIDS — DOW-UAP-PR071

This is unusually valuable public evidence because it directly documents the engagement. It does not identify what the target was before engagement. Release of shootdown footage and identification of the object are separate outcomes.

Operational use of UAP

The term UAP in a military record can mean an object not attributed at the time it became operationally relevant. A decision to engage an object can therefore coexist with uncertainty about its exact nature. The 2023 North American incidents occurred in a heightened air-defence environment after detection criteria had been adjusted. Different unidentified objects were tracked and, in several cases, shot down. The Lake Huron clip is evidence that a military engagement occurred. It should not be used as evidence that the Air Force fired on extraterrestrial technology merely because the target was labelled UAP. This is precisely the kind of category confusion the House request helps resolve when the underlying records become available.

Persian Gulf file

The request's item 45 asked for “UFOs in formation over Persian Gulf.” AARO later published DOW-UAP-PR098, a much longer infrared sequence than many of the other requested clips. AARO describes a sensor tracking an area of contrast, changing zoom and eventually resolving several distinct areas of contrast while the image quality and grain vary. AARO — UAP Report Documents The longer duration makes the file useful. It does not solve the scale problem. Several targets appearing close together in an image can be physically close, separated substantially in range or affected by changing zoom. The file can support the proposition that several image-plane areas of contrast were tracked. It cannot, without additional geometry, establish an extraordinary coordinated formation.

Again, the requested title is more assertive than the publicly supportable physical conclusion.

Provenance, classification and access

Custody warning

The House letter was motivated by the belief that AARO possessed unreleased military videos. AARO's later response through public release introduced a complication that was not visible from the titles alone. Many of the materials were indeed found on a classified network. But AARO says many lack a substantiated chain of custody. This distinction is fundamental. A file being stored on a classified system proves that the file entered a classified government information environment. It does not automatically prove who originally exported it from the sensor, whether it is generation-one media, whether it was edited before upload, or whether its title accurately records the incident. The resulting evidence chain can look like this: a military sensor records an event; someone exports or copies the media; someone edits, zooms or annotates it;

someone assigns a descriptive filename; the derivative is uploaded to a classified network months or years later; AARO later finds the file. Every stage matters. Government custody at the final stage does not reconstruct all earlier stages.

Classification and object identity

The request also illustrates why public withholding of a military video should not automatically be interpreted as evidence that the object itself was exceptionally secret. Military imagery can be classified because it reveals: sensor resolution; spectral band; field of view; operating altitude; platform location; mission profile; tracking behaviour; weapon employment; communications; or intelligence collection in a sensitive region. A mundane object recorded by a classified sensor can therefore produce a classified video. Conversely, declassifying the image does not necessarily reveal every associated sensor parameter required for scientific analysis. This is one of the central tensions in military UAP transparency.

The public may receive enough imagery to see that something was recorded while still lacking the metadata needed to calculate what it did. That is not unique to UAP. It is a general consequence of releasing intelligence-derived imagery.

Congressional and public access

The March 31 letter asked for videos to be delivered to the Task Force. It did not say every file had to be immediately posted on the public internet. This distinction matters when evaluating compliance. Congress can receive classified material in a secure facility. Members with the necessary committee authority may inspect records that cannot be released publicly. The public can later receive declassified or redacted versions. A video may therefore move through several stages: withheld from public access; shown to authorised members; reviewed for classification; released in a derivative or redacted form; and later supplemented with additional metadata. The absence of public release on April 14 would not prove that Congress did not receive the record.

Likewise, public release on May 22 does not prove what Congress had received privately beforehand. The most useful accountability metric would track both.

Oversight authority

The March letter closes by noting that the Committee on Oversight and Government Reform is the principal oversight committee of the House and possesses broad investigative authority under House Rule X. This is not the same as a subpoena. The March 31 document is a formal committee request for production. Its political and institutional weight is substantial, but the letter itself does not describe compulsory process or contempt consequences. That distinction is useful because UAP discussion often treats any congressional request as though it were a binding judicial order. Congressional oversight works through several escalating tools: informal staff requests; formal letters; classified briefings; requests for transcribed interviews; subpoenas; legislative conditions; appropriations restrictions; and public hearings.

The March 31 request is best understood as a highly specific formal oversight demand within that wider toolkit. Its specificity made escalation easier if records later proved difficult to obtain.

Recordkeeping

There is another advantage to asking for named files. If a custodian says the record cannot be found, the problem becomes diagnostic. Was the title unofficial? Was the file uploaded under another name? Was it duplicated? Was it deleted? Was it transferred? Was it classified under another programme? Was the underlying sensor recording never preserved? A general request for “UAP videos” can fail because agencies search different terms. A request for DOW-UAP-PR051 / Syrian UAP instant acceleration is much easier to trace after AARO assigns a stable identifier. The 2026 public releases therefore improved accountability not merely by publishing media, but by creating record identifiers that can be compared across AARO, PURSUE, DVIDS and congressional requests. This is a quiet but important transparency improvement.

Native media and case packages

Original files and technical context are essential to any public assessment. The later AARO disclosures reinforce that point. A public analyst ideally needs: the native sensor file; exact timestamp; platform trajectory; sensor type; zoom and field-of-view state; range or slant-range information; aircraft attitude; weather and wind; radar or other sensor correlation; and the history of any edits or exports. Without range, image-plane displacement does not establish linear speed. Without platform motion, parallax cannot be separated from target motion. Without optical configuration, apparent shape can be misleading. Without chain of custody, it may be unclear whether the displayed file preserves the sensor's original temporal and spatial properties.

Congress was therefore asking for potentially important evidence. The scientific usefulness of that evidence depends upon whether the case package accompanies the clip.

Missing native sources

Several May files were marked as digitally altered before upload. That is one of the most consequential findings generated by the transparency process. The problem is not that enhancement is inherently illegitimate. Slow motion can help an analyst inspect a brief transit. Contrast changes can make a low-signal target easier to see. Zoom can help viewers follow an object. The problem is that processing changes the relationship between displayed pixels and the original sensor record. If the unaltered source is unavailable, the derivative cannot always support quantitative claims about speed, morphology or brightness. This means a House records request should ideally distinguish the named circulating file from the native source from which it derives. The March letter mostly requested titles.

The later public record shows why future requests may need to ask for the entire custody chain.

Outcomes and institutional context

Publicly observable outcomes

By the UAPRAD review date, the event had produced a mixed but meaningful outcome. First, the request established a public list of specific government records lawmakers believed existed. Second, many overlapping files became publicly available through AARO and PURSUE, including several of the most high-profile titles. Third, AARO attached provenance caveats and more neutral descriptions that substantially improved how those files could be interpreted. Fourth, stable identifiers now make future congressional or archival follow-up easier.

What remains less clear publicly is whether every numbered item was delivered to the Task Force by the requested deadline, whether every underlying native file has been preserved, and whether the public copies represent all versions or associated technical records held by government.

Those are not minor details. They determine whether transparency has moved from seeing the clip to being able to analyse the event.

Limits of causal attribution

The timing can create an attractive causal story. Luna requests 46 video items on March 31. The Pentagon releases numerous matching videos in May. Therefore, the letter caused the release. The public AARO metadata complicates that story. AARO repeatedly states that the material was identified in response to the earlier March 6 request from eight House members. PURSUE itself was also already being built under the President's February transparency directive. The May release therefore had at least two independent institutional drivers: an executive government-wide records-release programme; and congressional requests for specific UAP records. The March 31 letter belongs within that pressure environment. The evidence does not isolate its causal contribution precisely. A strong historical account should resist claiming more.

Committee criticism and case analysis

The letter states that the Task Force had found AARO's responses to UAP questions and data less than adequate. That is a significant congressional criticism. It does not establish that AARO's technical assessments were wrong. The committee was primarily criticising transparency, responsiveness and access. AARO's later May releases, by contrast, frequently supplied technical and provenance caveats that weakened extraordinary readings of the same files Congress wanted. Those positions can coexist. A committee can be correct that government should release more material. AARO can be correct that the released material does not substantiate the title attached to it. The relevant standard is evidence, not institutional allegiance.

Evidence assessment

The March 31 request was a consequential procedural intervention because it converted a broad transparency dispute into a finite, auditable record set. That change did not establish that any listed object was extraordinary; it made claims of government custody, classification and withholding more capable of being tested against identifiable records.

The subsequent releases demonstrate why that distinction matters. Several dramatic titles were attached to derivative media with incomplete custody histories, while AARO identified tracking changes, digital alterations or insufficient range information that limit inferences about acceleration, erratic movement and coordinated formation. The Lake Huron footage documents a military engagement and apparent high-energy interaction with an unidentified object, but it does not identify the target.

The principal unresolved accountability question is completeness. The public record does not establish whether the Task Force received all requested material by 14 April, and the May release does not necessarily include every native sensor file, telemetry package or classified case record that Congress sought. Public availability of overlapping videos is therefore a meaningful transparency gain, not proof of complete compliance with the production request.

The event may be understood as an evolution in congressional UAP oversight from broad questions about secret evidence to requests for named records. Its enduring value will depend on whether those records can be compared across public and classified versions, traced to native sources and supplied with the metadata needed for reproducible analysis. Transparency may make a case appear less extraordinary as readily as it strengthens one; its value lies in making either result testable.

Source library

House Committee on Oversight and Government Reform — UAP Request Letter, 31 March 2026

The controlling source for this event. The four-page letter from Task Force Chairwoman Anna Paulina Luna to Secretary Pete Hegseth requests 46 numbered UAP video items, several with multiple sub-videos, and asks for delivery by 14 April 2026. It provides the exact titles, dates and operational labels used in the records request.
Read the official House request letter

House Oversight — “Luna Continues Transparency Investigation into UAPs,” 1 April 2026

The Committee's public announcement contextualising the request. It connects the letter to the September 2025 transparency hearing, whistleblower claims that AARO possessed additional video records and the Task Force's criticism of AARO's responsiveness.
Read the House Oversight announcement

House Oversight — September 2025 UAP transparency hearing

The principal earlier oversight event cited in the March letter. It provides the political and whistleblower context from which the request for specific military records developed.
View the official hearing page

AARO — Presidential UAP Transparency Initiative

The most important follow-up source. AARO states that on 6 March 2026 eight House members requested access to 51 potentially UAP-related records and that AARO identified responsive material on a classified network. It also states that many of the materials lack a substantiated chain of custody.
Browse AARO's Presidential UAP Transparency Initiative

AARO — UAP Report Documents

The central public index for the later video releases. It preserves uploader-defined titles, AARO provenance assessments, prior digital alteration warnings, neutral video descriptions and explicit cautions that descriptions should not be treated as investigative conclusions.
Browse AARO's UAP Report Documents

Department of War — PURSUE Release 02, 22 May 2026

The public release tranche through which many titles overlapping the House request became available. The release included 5.6 GB of video alongside documentary material. Its timing is relevant but does not establish that the March 31 letter was the sole cause; AARO attributes the responsive collection to the earlier March 6 congressional request.
Browse PURSUE Release 02

AARO / DVIDS — DOW-UAP-PR050, “4 UAP Formation Iran 26 Aug 2022”

Primary government-hosted copy of the first named item in Luna's list. AARO describes multiple areas of contrast in infrared imagery while retaining the uploader-defined “formation” title as a title rather than a validated three-dimensional physical relationship.
View PR050

AARO / DVIDS — DOW-UAP-PR051, “Syrian UAP instant acceleration”

Primary government-hosted video and metadata. AARO states the media had been digitally altered before upload and describes the apparent rapid exit as occurring when the sensor stopped tracking the area of contrast, materially limiting claims of verified instantaneous physical acceleration.
View PR051

AARO — DOW-UAP-PR053 and PR054

Primary AARO records for the “cigar shaped or fast spherical” and “spherical UAP erratic movement” videos requested by Congress. AARO says both files were digitally altered before upload; for the erratic-movement media it explicitly states that the alterations significantly influence apparent performance characteristics.
Inspect PR053 and PR054 through AARO's report-document index

AARO / DVIDS — DOW-UAP-PR065, Coast Guard “Tic Tac” video

One of the two 24 April 2024 Coast Guard recordings named in the House letter. AARO describes an area of contrast tracked by an infrared sensor rather than treating “Tic Tac” as an established physical morphology.
View PR065

AARO — DOW-UAP-PR067, “Multiple Spherical UAP USO near Sub.”

Primary AARO record for the requested 25 March 2022 file. The uploader-defined title says the objects moved in and out of water, while AARO's neutral description concerns areas of contrast moving through the sensor field of view. The public record does not itself establish a transmedium trajectory.
Inspect PR067 in AARO's report-document index

AARO / DVIDS — DOW-UAP-PR071, Lake Huron shootdown, 12 February 2023

Primary government video responsive to one of the highest-profile items in the House request. AARO describes an apparent high-energy kinetic interaction and fragmentation pattern, documenting the military engagement while not identifying the target's physical nature.
View the Lake Huron video

AARO — “UFOs in formation over Persian Gulf?” / PR098

Primary government record for the Persian Gulf formation footage named near the end of the House request. The longer infrared recording shows multiple areas of contrast and changes in zoom/tracking but lacks enough public geometry to establish extraordinary coordinated formation flight.
Browse the PR098 record through AARO

Department of War — PURSUE programme

The wider executive transparency programme active during the congressional request. Its rolling-release structure provides essential context for why the later public release should be understood as the product of overlapping executive and congressional transparency pressure rather than attributed to one letter alone.
Visit the official PURSUE programme