Navy Authenticated FLIR, Gimbal, GoFast Footage as Genuine Navy/DoD Recordings and Treated Them as UAP (Unidentified)

If you’ve spent any time around UFO or UAP discourse, you’ve seen the same three clips everywhere: FLIR (often tied to the “Tic Tac”), Gimbal, and GoFast. The part that trips people up is the phrase “Navy confirmed.” In the sources people cite, the confirmation isn’t “aliens,” it’s much narrower: the videos are real U.S. military imagery, and the objects shown are described with official-sounding language as an “unidentified aerial phenomenon.” For the official Navy guidance and reporting updates that moved this language into formal channels, see reports summarizing the Navy’s 2019 guidance on UAP reporting and the Department of Defense’s later releases (examples cited below).

That distinction is exactly why the Navy and Pentagon-style wording in 2019 mattered culturally. These clips weren’t just internet artifacts anymore. They got pulled into government-facing language that treats them as UAP, not as hoaxes, not as fan edits, and not as solved trivia. One source even frames the public arc plainly: the videos were leaked in 2017 and later “officially released,” which is a very different posture than letting a clip drift around online without ownership. For the Department of Defense official release of the clips in 2020, see the DoD announcement linked below.

Here’s the guardrail that keeps the conversation honest: “real UAP” in this context means real, observed and recorded phenomena on Navy systems, not confirmed extraterrestrial craft. Official acknowledgment raises the floor on authenticity and credibility, but it doesn’t answer the question everyone actually cares about: what the object was. The only useful way to read “confirmed” is evidence-first: separate what the government authenticated (the footage and its military origin) from what it did not (a definitive identification).

What the Navy Actually Confirmed

The key 2019 shift wasn’t “the Navy confirmed aliens.” It was the government drawing a clean line between authenticity versus identification: confirming a clip is real Navy imagery of an unidentified aerial phenomenon (UAP) tells you the footage is genuine and the object wasn’t immediately recognized, not what the object ultimately was. Coverage of the Navy’s 2019 guidance and its encouragement that aircrew report UAP is available via reporting that quotes Navy officials and the updated internal guidance on reporting (see primary references below). For the 2020 DoD official publication of the three videos, see the Department of Defense release linked below.

2017: the videos hit the public domain through To The Stars Academy and major media coverage, after circulating as leaks. 2019: the Navy’s on-record acknowledgment focused on the videos as authentic military recordings and treated the objects/events as UAP, meaning “unidentified” in the straightforward sense of not being immediately identified. 2020: the Department of Defense officially released the clips itself, moving them from leaked-public to formally published government material. For contemporaneous reporting and the DoD release, see the links in the source list below.

Those dates matter because they explain why people argue past each other: a clip can be “known online” for years and still not be formally owned by the government in public-facing language. Once you keep that timeline straight, the three videos people lump together are easier to talk about precisely.

The three clips most people mean are commonly nicknamed FLIR1, Gimbal, and GoFast. FLIR1 is the one tied to the 2004 USS Nimitz encounters and is widely referred to as the “Tic Tac” video. Gimbal and GoFast are tied to the mid-2010s Navy encounter wave, with Gimbal commonly associated with a 2014 incident and GoFast associated with a 2015 incident in many summaries. All three are cockpit FLIR-style military recordings, which is exactly why “authentic footage” is the part the Navy can actually confirm without making a leap about what’s on screen.

Two misunderstandings drive most of the online overclaiming. First: authentic footage does not equal an identified object. A real Navy video can still show something the crew didn’t recognize in the moment, and that’s all “UAP” is doing as a label: it marks a case as unidentified pending better data or analysis. Second: “unidentified” is a status, not a permanent conclusion. Some UAP cases get explained later as more information comes in; others stay unresolved because the data is limited, not because a paranormal answer was proven.

If you want a clean way to talk about the 2019 confirmation without overselling it, use a sentence like: “The Navy confirmed the videos are authentic and show UAP (unidentified, not ‘confirmed alien’), and the objects haven’t been publicly identified.” For primary documentation and contemporaneous reporting, see the primary sources linked later in this article.

FLIR, Gimbal, and GoFast Explained

Once you accept what was (and wasn’t) confirmed, the next question is what these clips can actually show you on their own. They hit harder than most UAP stories because they are sensor-based, not just someone’s memory-but that’s also the trap.

Once you’re looking through a modern targeting pod, a lot of what feels like “the object did something” can actually be “the camera system did something,” and the public versions of these clips are short enough that it’s easy to over-infer.

The footage is commonly associated with the AN/ASQ-228 ATFLIR, a gimbal-mounted electro-optical and infrared targeting pod that shows stabilized imagery plus tracking symbology. The pod is designed to keep a track while the jet moves, zooms, and slews, so the picture is always a mash-up of object motion, aircraft motion, and the pod’s own stabilization behavior.

Here’s a clean way to watch: track the object against the background, not against the center of the screen. Notice when a lock or track seems to “stick” versus when the pod is hunting or slewing. And don’t assume the on-screen numbers tell you everything, because you’re missing the rest of the sensor picture that crews and analysts would normally use to interpret what they’re seeing.

Those limitations matter because these videos sit inside a bigger “data quality plus sensor fusion” problem. An unclassified assessment reported 144 UAP reports, with 143 unexplained at the time, and it also noted that many incidents involved multi-sensor corroboration, meaning more than one sensor stream (for example, radar plus electro-optical) rather than a single witness account. For that 144/143 finding, see the Office of the Director of National Intelligence’s June 2021 “Preliminary Assessment: Unidentified Aerial Phenomena” linked below. The public clips are just the sliver we can all see.

What you’re seeing: a white-hot looking blob in infrared that seems to drift, then “skate” as the camera zoom and tracking change. The clip’s power comes from how clean and instrument-like it feels compared to shaky phone video.

Why it seemed anomalous: trained aviators expect the pod view to help separate “weird target” from “weird camera,” and this clip doesn’t give you much time to build confidence either way. The object’s presentation stays ambiguous, with no obvious wings, no clear exhaust, and a heat signature that reads as a compact shape rather than a familiar aircraft profile. With only the public snippet, you also lose the longer lead-in where a crew might have tried multiple zooms, polarity changes, or alternate tracking behaviors that would usually settle the question.

Most-cited conventional explanation and its caveats: a lot of analysts argue FLIR1 is a distant airplane whose infrared “shape” is being dominated by viewing angle, sensor settings, and atmospheric effects, not by the actual outline of the aircraft. Leonard David, for example, summarizes the view that it is most likely a distant airplane. The caveat is straightforward: without the full sensor metadata, range, and a longer sequence showing how the track behaves over time, “distant aircraft” remains a best-fit story, not something the public clip can conclusively prove.

What you’re seeing: an object with a bright core that appears to rotate while it moves laterally, with excited audio in the background. Visually, it’s the most “science-fictional” of the three because the rotation reads like a maneuver rather than a camera artifact.

Why it seemed anomalous: crews are trained to trust stabilized targeting video as an aid to identification, and the apparent rotation looks like a physical change in attitude. The friction is that gimbal-mounted systems are doing a lot of hidden work, including stabilizing the horizon, compensating for aircraft movement, and managing their own mechanical limits. When the clip is only a few seconds long, you can’t easily test the simplest field check, which is whether the “rotation” tracks with sensor behavior (like zoom changes or slews) or with the object’s relationship to the world.

Most-cited conventional explanation and its caveats: the leading prosaic explanation is that the “rotation” is driven by the camera system, specifically gimbal derotation behavior and glare artifacts that can make a bright source appear to twist as the pod adjusts. Jamie West has shown, in analysis covered by Vice, that gimbal-mounted cameras can reproduce effects that look a lot like what you see in the Navy’s Gimbal clip. Other write-ups and online analyses focus on glare as the dominating factor. The caveat is that “camera artifact” is a category, not an ID. It can explain the rotation without fully explaining what the underlying source is, and the public clip does not include the broader context that would let outside analysts check the hypothesis against additional sensor modes or longer tracking runs.

What you’re seeing: a small object over what looks like ocean, with the camera tracking while the audio reacts to how fast it seems to be moving. Media descriptions often frame it as a radar recording of an object apparently moving at very high speed just above the sea surface, which is exactly why it grabs attention.

Why it seemed anomalous: speed is one of the hardest things to eyeball from a stabilized, zoomed sensor view. A target that is closer than you think, or farther than you think, can completely flip the apparent velocity. Add jet motion, wind, and a tracking box that keeps the object centered, and your brain naturally interprets “fast across the screen” as “fast through the air,” even when the geometry is doing most of the work. The shortness of the public clip matters here, because you do not get a long baseline where range and track stability can be stress-tested.

Most-cited conventional explanation and its caveats: the dominant prosaic read is parallax, plus assumptions about wind and groundspeed. If the object is moving with the wind or is at a different altitude and range than casual viewers assume, the apparent “zipping” can be largely a perspective effect created by the jet’s own motion and the pod’s attempt to keep the target framed. The caveat is the same structural problem as the other clips: without the full set of corroborating data that may exist in the original event record, the public video alone cannot lock down range, true speed, or the nature of the object.

Put plainly, these clips can show you what the sensor saw, but they cannot, by themselves, prove what the object was. The most productive way to talk about them is to separate (1) what’s on-screen (a stabilized track with specific apparent motions), (2) what’s inferred (speed, rotation, distance), and (3) what isn’t in the public record (longer tracks, alternate sensor modes, and any multi-sensor corroboration tied to the specific incident). More time-on-target, range-validated telemetry, and correlated radar or other sensor logs would change confidence fast, because they turn a compelling image into a measurable event.

Why the Navy Shifted Publicly

The Navy’s 2019 shift reads less like “sudden alien disclosure” and more like plain risk management: protect pilots, reduce blind spots, and build better data for security decisions. Once leadership treats UAP (unidentified events) as a reporting and safety problem, public acknowledgment stops being mysterious and starts being operational.

Fighter crews weren’t eager to be the person who filed a report that sounded weird. Pilots described holding back because of stigma and career concerns, which is exactly how you end up with underreporting and thin data. The fix wasn’t debating what every object “really” was; it was making reporting normal. That’s why the military publicly urged pilots to report strange sightings, explicitly aiming to remove the stigma and get hazards into the system where they can be analyzed like any other aviation risk. Reporting guidance and public statements from the period are summarized in contemporary coverage and in Navy guidance documents referenced below.

Culture change doesn’t stick without process change. In March and April 2019, the Navy established and publicized standardized reporting guidance so sightings were not handled ad hoc, lost in informal channels, or buried as “no big deal.” Rather than asserting that one service literally copied another, reporting processes expanded and were later standardized across the Department of Defense so that UAP incidents would be captured in a consistent, auditable way across services. Those institutional changes are reflected in the Navy guidance and subsequent DoD reporting and are cited below.

The most practical driver is also the least glamorous: unidentified incursions around training ranges and sensitive sites can be drones, foreign surveillance, or something misidentified in a complex environment. Officials raised concerns about drones, range incursions, and surveillance of sensitive installations, and DoD messaging emphasized the safety and security implications even when identification is unknown. You don’t get to shrug at an unknown track near a carrier workup just because it sounds strange.

Cover-up narratives gained traction because, for years, the public saw leaks and silence instead of formal records. The Navy’s move partially counters that by creating a paper trail. When future Navy or DoD statements drop, ignore the sensational framing and look for the real signal: new reporting channels, updated guidance, and how data gets captured and shared.

Congress, Laws, and the Disclosure Push

Once the Navy put a public, on-the-record stamp on the issue, Congress did what Congress does: it demanded process, reporting, and accountability. The story stopped being only about a few videos and started being about how the federal government collects UAP-related records, who gets briefed, what stays classified, and how claims get evaluated inside lawful oversight channels. For official congressional text and proposals relevant to FY2024 NDAA debates, see the Congress.gov entries and bill text linked in the sources below.

Congressional attention isn’t a vote for any single explanation. It’s a response to three hard, practical problems that lawmakers can’t ignore: airspace safety (unknown objects near training ranges are a readiness and collision-risk issue), counterintelligence (unidentified incursions can be adversary platforms or sensor deception), and classification discipline (programs spread across compartments are harder to audit). The friction is that the public wants clarity fast, while the national security system is built to move slowly, restrict access, and minimize disclosure. Oversight is the pressure-release valve: force agencies to standardize what they collect, who they tell, and how they justify secrecy.

The National Defense Authorization Act (NDAA) is the annual law that authorizes defense policy, and it’s where Congress routinely bakes in oversight: mandated reports, recurring briefings, and formal tasking that outlives any single news cycle. In practice, post-2019 NDAA-style oversight tends to do a few things consistently: require regular updates to armed services and intelligence committees, centralize how UAP incidents and related records are reported, and tighten classification management so “who can see what” is written down instead of improvised. That last point sounds bureaucratic, but it’s the difference between an auditable system and a handful of stovepipes that can dodge scrutiny.

You can see the institutional shift in congressional materials that explicitly tie official UAP activity to 2019, including references to the UAP Task Force as part of the oversight conversation. That matters because once an effort is discussed in hearings and committee work, it becomes easier to attach deadlines, deliverables, and accountability hooks to it. Primary congressional bill language and amendment proposals during the FY2024 NDAA debate, including proposed “UAP Disclosure Act” language, can be found on Congress.gov and are linked in the sources section below. Remember that draft language often changes substantially during negotiations, so consult the official enacted text for final authority.

“Disclosure” bills are often less about declaring what UAP are and more about building a records-handling machine: inventory requirements, review procedures, and declassification pathways. During the FY2024 NDAA debate, proposed language in various amendments and draft bills floated concepts like a records review board and definitions referencing “non-human intelligence,” “technologies of unknown origin,” and related record-collection and declassification mechanisms. That wording is proposal language, not a government confession, and its survival into final enacted text must be verified during drafting because NDAA negotiations routinely rewrite or drop provisions. The relevant Congress.gov pages and committee reports are cited below.

A separate concept described in later UAP Disclosure Act amendment discussions frames a default timeline: disclose UAP records within 25 years unless delayed for clear national security reasons. That’s a classic “sunset the secrecy unless justified” structure. Likewise, Congress.gov bill text and amendment summaries have included phrases such as “technologies of unknown origin and biological evidence of non-human intelligence,” which read like rules for handling allegations and materials, not proof that the allegations are true.

Public leaks get attention, but they don’t automatically trigger lawful review. A protected disclosure is a legally defined whistleblower communication made to authorized oversight channels, such as an inspector general or relevant committees, with anti-retaliation protections attached. The mechanic here is simple: it creates a path for cleared personnel to share classified concerns with people who are allowed to receive them, without playing telephone through the media or risking unauthorized disclosure charges.

If you want to read this moment clearly, ignore viral summaries and scan for the boring stuff: mandated deliverables, required briefings, and official publications of record. That’s where “disclosure” becomes a real process shift instead of a headline. See the Congress.gov links below for the primary legislative texts and amendment history discussed in this article.

Does This Point to Non-Human Intelligence?

All of this institutional attention can make it feel like the government is quietly endorsing a specific answer. It isn’t, at least not in the public record.

“Real UAP” is a narrower claim than most headlines imply. The Navy confirming certain videos as authentic and describing the incidents as UAP is a statement about identification, not origin.

Going from “unidentified” to “non-human intelligence” is a much bigger leap, and it requires a much higher evidence bar than a compelling story or a hard-to-parse clip.

The cleanest proof looks boring on paper: physical material you can trace. If someone claims “non-human,” you need artifacts with documented chain of custody (who had it, when, how it was stored), repeatable measurements (composition, isotopes, manufacturing marks), and independent verification by qualified labs that can be audited. The same goes for sensor data: multi-sensor correlation (radar, EO/IR, telemetry) tied to time, location, and calibration records, so analysts can rule out glitches, geometry, and misidentification. Without that documentation, you don’t have “alien tech,” you have an untestable assertion.

That’s why the All-domain Anomaly Resolution Office (AARO) matters: it’s the government’s dedicated analytic shop for separating rumor from the record by pulling cases into a consistent investigative workflow. AARO and the Pentagon’s public reporting say the record today supports no evidence of extraterrestrial spacecraft or alien technology in the cases they’ve reviewed. Those same public findings conclude most sightings are attributable to ordinary objects or natural phenomena, and some remain unresolved because investigators don’t have enough data to make a call. See AARO’s official reporting and the Department of Defense consolidated reports linked below for the primary numbers and context.

For scale and to avoid confusion, cite the exact report once: AARO’s Annual Report to Congress for Fiscal Year 2024, published June 2024, covers the reporting period May 1, 2023 through June 1, 2024. That report provides the office’s counts for reports received and cases under active review during that specific reporting window; consult the AARO FY2024 Annual Report (linked below) for the exact enumerations and definitions the office used. All subsequent references in this article to AARO counts refer to that AARO FY2024 Annual Report and its May 1, 2023 to June 1, 2024 reporting window.

Sworn testimony is serious, but it’s not the same thing as publicly verifiable evidence. David Grusch testified under oath in late July and alleged “Non-Human Reverse Engineering Programs.” Treat that as a lead: important to investigate, not something you can independently confirm from his public statements alone.

Similarly, some official documents and briefings have repeated allegations about “alien craft” and even extraterrestrial bodies tied to crash reports, but allegations on paper still need corroborating, checkable documentation before they move from claim to fact.

1. Separate “unidentified” from “non-human” and demand the extra proof for the second claim.
2. Ask for chain of custody, calibration records, and multi-sensor data, not summaries.
3. Weigh firsthand, documented evidence above secondhand accounts, even under oath.
4. Check whether AARO’s public record supports the specific claim being made by consulting the AARO FY2024 Annual Report and related DoD consolidated reporting.

What to Watch Next in UAP News

It’s one thing to have a standard for evidence; it’s another to actually follow the story without getting dragged around by the algorithm. If you want to follow UAP disclosure without losing your mind, you need a process. Sources first, hype last. Real updates land in boring places on boring timelines, and the internet fills every quiet week with “big reveal” chatter.

Start by training yourself to look where the paper trail appears, not where the loudest clip goes viral. The House Oversight Committee’s public hearings calendar is where scheduled oversight sessions surface first. The Senate Armed Services Committee maintains hearings pages by Congress, which is where you’ll see defense-facing oversight and nominations that sometimes pull UAP (and AARO) into the record. For transcripts, use Congress.gov, but remember the sequencing: Congress.gov publishes committee hearing transcripts after they’ve been published by the Government Publishing Office (GPO). If a “transcript” is circulating before that, treat it as unofficial until it matches the GPO version. See the Congress.gov links below for committee materials and enacted bill text related to FY2024 NDAA and UAP oversight.

Expect periodic reports and incremental releases, not one cinematic dump. The Department of Defense released an annual consolidated UAP report covering May 1, 2023 to June 1, 2024. Those annual reports can also pull in UAP reports from earlier time periods that weren’t previously covered, which is why you’ll sometimes see “new” cases that are actually older events finally being added to the official ledger. That cadence naturally creates gaps that rumor accounts will try to “fill.” Don’t let them. Refer to the AARO FY2024 Annual Report and the DoD consolidated report for authoritative counts and the office’s methodology; links are provided below.

1. Check provenance: Who had it, when, and how did it leave custody? Vague “a guy sent it” stories don’t clear this bar.
2. Demand corroboration: Look for cross-confirmation from primary channels (DoD/AARO releases, statutory text, the Congressional Record, Inspector General statements), not reposts.
3. Match the primary source: Names, dates, headers, pagination, and filing context should align with the official version once posted.

Routine that keeps you sane: when “UFO sightings 2025/2026” trends, wait 24 hours, check the committee hearing pages and DoD/AARO releases, then search Congress.gov for the item after GPO publication. If it doesn’t land in that chain, don’t amplify it.

Conclusion

The real shift in 2019 wasn’t a new clip hitting the internet. It was the government letting “unidentified” live in the official record while still not naming what, exactly, the object was. That’s the same evidence-first distinction from the beginning of this article: authenticity got affirmed, identification didn’t.

That gap between “real footage” and “real explanation” is where people get misled, because short sensor clips are easy to overread. The Gimbal-style visuals, for example, can be recreated by how a gimbal-mounted system renders glare and perspective, which is exactly why a viral moment can’t carry the full evidentiary load by itself.

The process side is slower, but it’s also more measurable than the internet makes it feel. If you want to stay evidence-first, anchor your language to what’s actually confirmed, treat NHI claims as a higher-evidence category, and follow primary sources like AARO and DoD releases plus committee records. Use viral clips as starting points, not endpoints.

If you want more updates like this, you can follow this blog or subscribe so you catch incremental releases without the hype cycle.

Frequently Asked Questions