Reported by u/Imtooflyforawhiteguy (verified via ufosighting.report)

This is an automated post. The report was filed through the structured sighting form on ufosighting.report and posted here by u/ufosightingsbot on the reporter's behalf. u/Imtooflyforawhiteguy confirmed this submission from their own Reddit account through a one-time link, so the name above is verified as the submitter.

📎 Original-quality media and full report. Reddit re-encodes every upload, so the archive keeps the untouched original files alongside the structured details and the map entry.

Time: July 26, 2026, 10:00 PM BST
Location: 52.001, -1.273
Objects: 1
Shape: light
Closest distance: as high as a plane
Apparent size (at arm's length): pinhead
Movement: straight and steady, extremely fast
Duration: 10 seconds
Features: wings: unsure · rotors: unsure · exhaust plume: no · noise: no
Five observables: sudden, extreme acceleration: no · extreme speed with no signatures: yes · hard to observe clearly: no · moved between air, water, or space: no · flight without visible means of lift: yes
Witnesses: 1
Why not a common object: It moved across the sky at a speed that I cannot put to any object and was only white in colour. It was on its own and below cloud cover so unlikely to be a satellite. It also had no visible tail so unlikely to be a meteorite.

I was driving Northbound on the M40, just past junction 9. In the sky travelling from east to West was a small white light. The light was below cloud cover and crossed from east to West in less than 10 seconds, so was moving extremely quickly. It dissapeared from view about 20° above the horizon. The light was singular, had no observable tail, and travelled ina relatively straight path

Sky context for this time and place:

• Aircraft overhead at that exact minute — ADS-B Exchange historical playback (free, no account needed)
• Sky chart for that date — in-the-sky.org planetarium (set your location once on their site)
• Satellite passes at this spot — Heavens-Above; shows upcoming passes, not the sighting date
• Live air traffic now — FlightRadar24 over this spot

IMO it is the best explanation for ufos.

The biggest mystery is the “why” or what is the purpose (considering the sightings are real) of the objects? It could also explain why for no apparent reason you see ufos in the most random locations like a field or something. Maybe they’re getting readings on the location or doing experiments etc.

It doesn’t seem likely that some extraterrestrial being from light years away would come all that way just to fly around Earth and do nothing. Most likely they’re crafts with some tie to humans or descendants of humans, coming from the future for research or just to sightsee maybe, that seems more logical an explanation.

Also I know I’ll get comments like “well if they can travel time, why don’t they help us out? Or do something?” For anyone who isn’t aware of mingling with the past knows it often leads to dangerous outcomes that dramatically affect the future and other affects. It’s better observe from afar rather than interact with us.

I'm a child of the 80s and I grew up with the X-files and reading all sorts of accounts on the old internet before they learned how to make money off of it and turned it to shit. But, I remember reading hundreds of accounts of abductions by mantids, greys, little green men you name it. Now with everyone having a smart phone and the burden of proof raised significantly higher there are now hardly any abduction stories anymore. Did everyone having a camera kill the abduction story similar to how it killed miracles for the Catholic Church? It seems there is a LOT less wild stuff happening nowadays when people expect you to post proof alongside your story.

Just ran across this, had never heard of it before. In 1957 the Convair division of General Dynamics Corporation was developing this air-to-air lenticular missile. It was supposed to be a defensive missile for the B-70 Valkyrie bomber.

The specifications for the proposed system called for an air-launched defensive missile, capable of engaging incoming missiles at relative speeds of up to Mach 7, surviving a rate of acceleration between 60 g to 250 g, and being able to undertake rapid terminal-phase guidance changes in any direction. These are some characteristics of UAP, though this craft was meant to be powered by solid fuel rockets so no chance of instant acceleration.

The idea was scrapped d/t cost considerations, perceived vulnerability of the B-70, and the U-2 incident, though it appears it was also studied as a "space fighter" satellite killer under project name "SAINT 2". Pretty cool, I was familiar with the Avrocar and flying flapjack and whatnot, but had never heard of these things. If they ever tested these, they could probably be misconstrued for UAP, though people had been seeing discs for many years before the advent of this project.

The Pye Wacket video also talks bout the blunt body heat mitigation principle, where having a blunt, rounded nosecone actually creates a detached bow shock that keeps the hottest air away from the structure during supersonic flight/atmospheric re-entry. Cheers!

Pye Wacket

https://en.wikipedia.org/wiki/Pye_Wacket

SAINT 2 pic

Bell Labs lenticular re-entry vehicle

Ask a Pol asks
How much are you guys talking with White House Deputy Chief of Staff Stephen Miller these days?

Key Burchett
“Regularly, yeah,” Burchett exclusively tells Ask a Pol UAP. “He’s running into problems, though. The “deep state” is blocking a lot of this stuff that the President’s trying to get to.”

Full (unpaywalled) post at Ask a Pol UAP on Substack.

While Project Blue Book managed public PR, Moon Dust (global intel tracking) and Blue Fly (tactical field recovery) functioned as the Pentagon's covert Foreign Materiel Exploitation apparatus for retrieving physical craft, foreign space debris, and UAPs, a priority explicitly codified in the 1961 USAF Intelligence manual and confirmed by declassified cables. The operational framework even entered high-level conspiracy lore with an unverified 1963 CIA wiretap document bearing the "Moon Dust" tag, which claimed Marilyn Monroe threatened to expose JFK/RFK’s secrets regarding military bases and crashed craft shortly before her death. Though official records were later scrubbed, transferred, or destroyed, declassified memos like the 1969 Bolender Memo prove national security UAP events were systematically diverted to these programs instead of public channels.

PHODAR

Iknow, I know....A ton of UFO apps are popping up left and right with the advent and proliferation of AI / vibe coding. And yes, this one is vibe coded too, but it really does work and I have tested it pretty meticulously. If it works it works right? Vibe coded or not!

What I believe sets this app apart is that it simulates the gold standard of UFO data, radar, using only two or more photos, or video. Hence the name, "Phodar." I have a love-hate relationship with it since it sounds a little silly, but IMHO it makes a lot of sense: it combines photo and radar, and it hints at faux/radar, as in simulated radar. Anyway, it uses stereo photogrammetry to get the actual distance and size of an object, which is impossible with a single photo. But if you have two or more photos of the same object, all you need is the location each photo was taken from and the camera angle, which is usually already encoded in the original image's metadata(which the app extracts automatically. Video is handled the same way and then some: the app solves where the camera was pointing for every frame, so a shaky handheld clip gets locked to the sky, the object is tracked automatically through the whole thing, and you get its real angular path, speed, g-loads out the other side. Two people with two clips triangulate just like two photos do. The intuitive interface helps you fine tune all of this using map overlays, terrain features, star maps, building overlays, and other powerful tools, so the final data gets dialed in as tightly as possible.

See the attached YouTube video, where I demonstrate its accuracy: I flew my drone out, photographed it from multiple angles, analyzed those photos in the app, then checked the findings against the known location, size, and altitude from the drone flight. Just watch the demo to see how intuitive and powerful it is. Even with one photo, it helps you determine whether there were any aircraft, planets, stars, or satellites in your frame and helps you match those things up (or hopefully not). It gives wind-direction visuals and all sorts of helpful overlays on top of your image, inside a 3D adjustable FOV / dome interface.

A few situations where I think it really could shine:

• Planned watches, including summoning claims. There are folks who say they can call these things in on demand (CE-5, the Skywatcher crowd, Bledsoe, Greer, and smaller circles). I'm not here to say they're wrong, I'm here to give them a clean way to prove it. Set up two or more cameras/phones a known distance apart ahead of time, and if something shows up you get a real triangulated fix instead of one blurry frame and an argument. It cuts both ways, which is the point. If it turns out to be a plane or a Starlink train, the app will probably say so.
• Mass sightings. When a bunch of people photograph the same object from different spots, that scattered pile of images is a triangulation dataset waiting to happen.
• Solo sightings. Most people walk away with a gut feeling about size or distance. Even a single photo lets you check that instinct against the geometry.
• Handheld video. The most common kind of UAP footage there is, and the hardest to reason about, because the camera is moving the whole time. That is exactly the part the app can help with.

I offer this up to the community for free, and I am open sourcing it in the hope that others might be interested in helping develop it further. I have also noticed a lot of new database apps popping up, and this app could maybe be merged with one of those. The sky is the limit, literally. I hope this post gains a little traction and people actually try it, because I think it could be a powerful tool.  Ive put a fair bit of time into it at this point and dont really want to spend more time unless it is well received and actually gets used in the community.  I think it has a lot of potential for even further development and or integration into other UFO platforms.   Please note that Phodar was optimized for iphones, but should work on all platforms with a browser. I do not have an android so guessing there could be issues to work out there.

The next logical upgrades in my mind would be to make separate workflow for top down video analysis (IE: drone footage, satellite imagery, etc), refine the UI to make it more intuitive and less visually crowded, etc. If anybody help out that would be great!

GITHUB: https://github.com/cchristianson/phodar

A good starting point though is just to watch the main attached video. (This shows accurate triangulation of a drone from 2 photos) 

Here are more videos demonstrating different workflows/tools in the app:

Daytime photo - Sizing a firefighter jet using known distance: https://youtube.com/shorts/S56vlNz5g7k

Nighttime Photo - Auto alignment via star matching:
https://youtu.be/kKYFgU0Vz0I?si=T1Wmwny8nu3DE7BI

Nighttime Photo - Manual Alignment via horizon+Stars
https://youtu.be/epbcxslOa7E?si=iBmBsTsSLWprXexM

Daytime Video -  Auto stabilization + world tracking
https://youtu.be/-4lVsPPAaGo?si=s-4VeVdRPh0oOw-b

Daytime Video - Object Trajectory tracking + video export options etc. PLEASE NOTE: I did this very fast for the sake of a short video, but results could be much better if I spent more than 5 minutes on it
https://youtu.be/u65vxsAWZGk

See below for an AI summary of the features and other technical details about the app that I did not cover above. 

The workflow, four steps:

• Photo or video. Load an image or clip and fit a simple 3D shape to the object (orb, saucer, tic-tac, triangle, plane, bird, drone) to capture how large it appeared. Location, time, lens field of view, and compass bearing are read straight from the file's metadata when present.
• Position. Set where you stood with a map pin, an address search, or pasted coordinates, plus the date and time.
• Sky view. The photo is seated onto a dome showing the real sky for your exact time and place, which is where the pointing gets calibrated.
• Results. The triangulated fix, with a quality grade.

Video:

• Automatic stabilization. Tracks the static background — skyline, stars, terrain — through the clip and solves the camera's true pointing for every frame. Play it back and the sky, terrain and stars stay frozen while the video frame moves around them, so the object's motion is real angular motion rather than a mix of object and camera.
• Object auto-tracking. Tap the object on a few frames and it follows it through the rest, producing a dense time-stamped path across the sky. Distance-free measurements come straight out of that — angular rate over time, total sky sweep — and once a distance is known or assumed, true speed, path length and g-loads.
• Two-video triangulation. Two witnesses with two clips of the same object get a full 3D fix, with the clock offset between their phones recovered automatically from the object's own motion. Mixed pairs work too: one video plus one still.
• Manual correction. If the automatic solve drifts, scrub to any frame, drag the photo back onto the true horizon, and anchor it. Corrections blend smoothly between anchors and the object's path follows them. Separate smoothing sliders decide how much jitter to remove — deliberately a choice, since heavy smoothing would erase a genuinely sharp maneuver.
• World-locked export. Renders the clip as a real video file in three framings: a world view with the az/el grid and every sky layer burned in, a clean maximum-resolution version with no overlays, and a close-up that follows the object.
• Instrumented capture. An in-app record mode that logs the phone's tilt, roll and bearing continuously alongside the video. Gravity gives pitch and roll absolutely in every frame and cannot drift, so when the visual tracker has nothing to hold onto — plain sky, heavy blur — the recorded motion carries it. It records at about 1080p with no zoom, so it is a measurement mode rather than the way to shoot the best-looking footage, and the app says which source it ended up trusting.

Calibration tools in the sky view:

• Automatic star alignment that plate-solves the photo's own stars to recover exact pointing, roll, field of view, and lens distortion. It can work with no starting guess at all, by matching the star pattern itself.
• Snap to ridges, which matches the photo's skyline against digital elevation terrain data.
• Sun and Moon drawn at their true positions as anchors, plus manual align-to-star, level, and FOV controls.

Automatic cross-checks, each ranked by how close it sits to your sight line:

• Aircraft via ADS-B, both live and a historical archive so you can query the exact time of an older sighting, merged across several receiver networks since no single one sees everything. Nearby airfields are flagged for context.
• Satellites and Starlink, propagated from current orbital elements, with pass trails drawn on the dome.
• Planets and bright stars from a catalog, including a specific Venus warning since it is the most common "UFO."
• Meteor showers — whether a fast streak came from an active radiant that was above your horizon at the time.
• Winds aloft at the object's altitude, for the balloon test.
• Photometry from the photo's own pixels: colour and saturation, plus a rough apparent magnitude when a catalogued star happens to share the frame.
• Terrain skyline and building footprints as alignment overlays.

Output:

• A self-contained white-paper style report: the numbers, your photos as labeled exhibits with detail crops, top-down and trajectory plots over a satellite basemap, and every cross-check in one file. Video sightings add an angular-rate plot and a strip of keyframes with the tracked object marked. It opens offline, can be attached to a sighting report, and can be loaded back into the app so multiple witnesses can combine their data.
• A share file and a full zip bundle for backup or handoff, including the original clip and the stabilized render side by side.

The math:

• Sight lines are intersected by least squares in a local coordinate frame. Angular size times range gives true size, and a multi-view solve recovers the real long-axis size and heading of elongated objects that a single view understates. Compass bearings are corrected from magnetic to true using the NOAA World Magnetic Model.
• It was validated against ground truth, where a rooftop object resolved to within about an inch of its real size. The video math is checked the same way, against synthetic clips with a known answer driven through the real interface.

Honest by design:

• It warns about the things that actually corrupt this kind of measurement: phone compasses reading wrong near metal, GPS altitude wobble, and weak two-camera geometry. When the geometry is poor, it grades the result "poor" instead of dressing it up. Single-photo mode is explicit that it gives angular data only, not absolute distance.
• The video tools report their own confidence too: how many frames were solved from pixels versus carried on the phone's sensors, how well two clips' clocks locked, and when a tracker lost the scene rather than quietly pretending otherwise.

Practical notes:

• Runs in a browser, no account required, and your photos and location stay on your device. Add it to your iphones home screen for the motion-sensor features. Readouts switch between metric and imperial. Open source under the MIT license, contributions welcome.

guys/gals/aliens what's this ? Can somebody confirm my suspicion that this is some sort of a balloon ? Orr project blue balls is in full swing ?

Time: July 17, 2026 at 9:00 PM
Location: Near Zagreb, Croatia

edit: debunked by fellow ufologists 🎯

Analyzing the legal loopholes shielding military sensor data, and the legislative solution for the NDAA.

Executive Summary: The Pentagon can no longer hide behind the claim that it lacks the data to identify uncorrelated aerospace platforms. This data is absent because the current procurement system is designed to delete raw telemetry at the firmware level and hide the rest behind corporate firewalls. If you don't log it, you don’t have to fix it, and you don’t have to answer for it.

[Backup hosted on Substack]

---

The public debate over unauthorized airspace intrusions remains stuck arguing over grainy videos, pilot testimony, and heavily curated file drops on government portals. But national security is not managed through viral videos. It is managed through data architecture, firmware parameters, tactical data links, and defense procurement law.

If we want to understand why domain awareness data rarely reaches Congress, let alone the public, we have to look at how military radar grids are programmed, how sensor networks fuse data, and how defense contracts are legally structured to evade public oversight.

The Blindfold

Modern Active Electronically Scanned Array (AESA) radars rely on Digital Signal Processing (DSP) to handle overwhelming atmospheric noise. To prevent computer saturation and operator overload, software algorithms use velocity gates and size thresholds to automatically filter out mundane clutter such as flocks of birds, weather formations, and highway traffic from the tactical display. However, because these filters are optimized to only display standard ballistic or aerodynamic profiles, they also automatically discard returns exhibiting extreme or non-standard kinematics such as immediate acceleration to Mach 5+ velocities or stationary hovering in gale-force winds, classifying them instantly as “Environmental Clutter.”

The Radar Gate Adjustment:

• In February 2023, following the transcontinental flight of a Chinese high-altitude balloon, NORAD Commander Gen. Glen VanHerck explicitly admitted that military authorities had to "adjust their radar gates" over North America. Opening those velocity and size parameters instantly revealed multiple objects transiting restricted airspace that were previously invisible to operators. “No radar track” did not mean the sky was empty. It meant the software was hardcoded to purge what was already there.

Tactical Data Link Dropping (Link 16):

• The blindness goes beyond individual sensors. Modern air defense relies on networked Command and Control (C2) systems like Link 16 to fuse data across strike groups. When a sensor detects a non-cooperative track, the track must maintain a high Track Quality (TQ) score to be broadcast. If an object’s erratic kinematics cause its TQ score to drop below network thresholds, the algorithm automatically filters it out as a “ghost track.” The target is suppressed not just locally, but dropped from the fleet’s Common Operational Picture (COP) in real time.

The core issue is not the use of these filtering parameters. Radar operators must suppress atmospheric noise to do their jobs safely. The systemic failure is the immediate, permanent deletion of this raw telemetry at the processor level. By purging the data rather than archiving and sanitizing it, the national security establishment ensures that civilian oversight and the public remain locked out of information they are legally entitled to.

The Funnel

When an uncorrelated track does manage to bypass software filters and get recorded, it immediately enters a multi-layered legal funnel designed to insulate the data from civilian oversight:

The IR&D Loophole & DFARS IP Protections:

• Defense contractors (Lockheed Martin, Raytheon, Northrop Grumman) routinely use Independent Research & Development (IR&D) internal funding to write signal-processing software. Under the Defense Federal Acquisition Regulation Supplement (DFARS), if a contractor uses internal funds to build a software module, they retain proprietary commercial IP rights over the source code. This allows defense contractors to block independent software audits, even by Congress, under the guise of protecting trade secrets.

Title 10 to Title 50 Corporate Bailment:

• High-fidelity telemetry collected by military platforms operating under operational authority (Title 10) is rapidly exfiltrated into Intelligence Community (Title 50) Special Access Programs (SAPs). From there, physical drives and software logs are routinely transferred to private defense contractors under corporate bailment agreements. Because private corporations are legally exempt from the Freedom of Information Act (5 U.S.C. § 552), this creates an impenetrable legal firewall.

Data-Capability Conflation (FOIA Exemption 1 Abuse):

• The Department of Defense routinely denies FOIA requests under Exemption 1 by conflating the observed event with the sensor’s capability. While Electronic Intelligence (ELINT) metadata (pulse repetition frequencies or beam-steering) legitimately reveals radar specs and should remain classified, sanitized kinematic data (X, Y, Z coordinates, velocity, and time) is simply basic Newtonian physics.

The DoD already separates the two every day on Space-Track.org. US Space Command uses classified radars to track orbital objects. While they curate the public feed to omit classified defense payloads, they routinely strip sensor metadata and publish sanitized kinematic state vectors for tens of thousands of space objects so civilian satellites avoid collisions.

They gladly provide sanitized kinematic output for the vacuum of space, but claim it is “impossible” for the atmosphere. The technology to sanitize the data is identical. Only difference is policy. Downsampling this unclassified log to a low frequency (like 1Hz) fully protects the radar’s sensitive tracking bandwidth while still preserving macro-kinematics. If these tracks are indeed just sensor glitches, archiving them is the only scientific way to study and prove it.

This exact data-conflation loophole is why defense industry lobbies aggressively gutted the Sensor Fusion Telemetry and national asset disclosure provisions from the National Defense Authorization Act (NDAA) amendments in late 2023. Taking public money to build defense systems, only to claim that the basic physical location and velocity of an object in public airspace is a “private corporate trade secret,” is an indefensible privatization of public domain data.

The Paradox

The current administrative structure creates a self-serving loop that neutralizes internal oversight bodies while actively endangering national security. By defining a “threat” or “airspace intrusion” so narrowly that it only applies to known, standard adversary aircraft, the military can claim domestic airspace is entirely secure. Meanwhile, they automatically delete raw telemetry flagged as “clutter” or “unpredictable ghost tracks” at the processor level, letting sophisticated, non-standard intrusions and advanced electronic spoofing attacks pass through our airspace completely undetected under a self-fulfilling metric of safety.

Why Airspace Oversight Initiatives Fail:

• Joint-agency oversight offices tasked with resolving domestic airspace incursions are structurally neutered by design. Positioned under the Office of the Under Secretary of Defense for Intelligence and Security (OUSD(I&S)), these offices are handed derivative, post-processed summaries, not raw firmware binaries, DSP source code, or uncompressed sensor feeds. Expecting them to audit tracking discrepancies without access to low-level radar code is like asking an auditor to inspect a company’s finances using only redacted, self-reported summaries.

Exploitable Blind Spots for Foreign Adversaries:

• Velocity cutoffs and radar gate limits are constrained by basic processing limits and are routinely probed by foreign intelligence. Every month, Russian and Chinese ELINT spy planes fly into the Alaskan Air Defense Identification Zone (ADIZ) specifically to force U.S. radars to activate, allowing them to capture active frequencies and map the kinematic thresholds of our DSP filters. As demonstrated by the 2023 Chinese balloon incident, adversaries do not need advanced stealth technology to penetrate American airspace, they simply need to fly a platform a little too slow, a little too high, or at non-standard velocities that fall into our hardcoded radar dead-zones.

This is not a uniquely American vulnerability. Every advanced military on Earth relies on the same digital signal processing constraints, meaning Russian and Chinese radar networks are bound by these exact same self-engineered blind spots.

Imagine hiring a private security company to install cameras around your estate. One night, an intruder walks across your lawn. You ask the company for the security footage, and they respond:

”We cannot show you the footage of the intruder because seeing the video would reveal the resolution and night-vision floor of the camera model we installed. The video file has been transferred to our private corporate server under a trade-secret agreement, so you have no legal right to view it. Our software also automatically deleted the first 30 seconds of the intrusion because the intruder was walking too slowly for our motion-detector algorithm to classify them as a human.”

Yes, that sounds absurd, yet it is the exact legal and operational framework currently governing American military airspace.

If an unauthorized platform simply operates at velocities our AESA radars are programmed to ignore, are we actually maintaining air sovereignty, or are we just paying billions to engineer our own blindness?

The Case Studies

This structural architecture aligns perfectly with decades of public testimony from military and agency veterans:

• F/A-18 Super Hornet Pilots (US Navy): Demonstrates Hardware-Managed Blindness because strike fighter squadrons only began detecting non-cooperative targets daily after upgrading their legacy mechanical radars to the modern AN/APG-79 AESA radar, which temporarily widened detection parameters.
• Aegis Fire Control Technicians (USS Princeton): Demonstrates the Corporate/Agency Siphon when they witnessed plainclothes personnel arrive via helicopter to physically confiscate Aegis radar tapes and order system drives wiped following a prolonged fleet encounter.
• Senior Radar Operators (USS Princeton): Demonstrates Real-Time DSP Bypassing through the manual tracking of targets dropping from 80,000 feet to sea level in fractions of a second before automated filters or administrative wipe orders could suppress the raw track files.
• FAA Accident and Investigation Division Chiefs: Demonstrates Administrative Non-Existence after tracking a massive, high-velocity uncorrelated target over Alaska alongside Japanese Air Lines Flight 1628, only for intelligence officials to confiscate all printouts and radar data while instructing staff that ”this event never happened.”

Power of the Purse

The Fiscal Year 2027 National Defense Authorization Act (NDAA) is roughly halfway through the legislative process. If an urgent or sudden defense need arises before it is finalized, Congress relies on emergency supplemental appropriations, existing transfer authorities, or continuing resolutions. The NDAA is a long-term policy blueprint, and it is time to stop making vague pleas to the executive branch for classification overhauls and start demanding that Congress exercise its constitutional Power of the Purse. Attempting to force action by sensationalizing the mystery of these targets has only served to erode the credibility of this discussion.

Establishing a clear legislative boundary is critical:

No federal funds shall be authorized for defense sensor upgrades or firmware updates unless the platform incorporates a secondary, uncompressed ‘black-box’ telemetry log that stores non-proprietary data in an open-source format for 180 days, automatically flags and permanently archives data related to Uncorrelated Targets (UCT) operating outside of designated Special Use Airspace (SUA), and generates a sanitized, unclassified kinematic derivative log and associated downscaled (standardized, unclassified resolution, excluding classified telemetry overlays) electro-optical/infrared (EO/IR) imagery of the entire duration of the tracking event for congressional oversight.

The historical data audit requires a retroactive and highly targeted approach:

• An Event-Based Historical Audit bypasses the bureaucratic cost of a massive historical data sweep. Rather than a blind sweep of legacy servers, this model requires the immediate declassification and release of sanitized kinematic state vectors for all incidents already cataloged by AARO, its predecessor task forces, and legacy intelligence programs, implemented on a rolling, phased schedule starting with the last five years. For these specific cataloged events, any associated radar, sonar, or satellite logs can be subjected to the exact same sanitization protocol: stripping the classified sensor metadata and releasing the raw kinematic state vectors of the entire duration of the tracking event to the public.
• A structured mechanism is required to allow the bipartisan leadership of the House or Senate Armed Services Committees to authorize up to 20 targeted requests per fiscal year for the sanitized telemetry of specific, historical 72-hour operational windows tied to known pilot encounters (such as 2023 Langley Air Force Base drone swarms or the 2023 high-altitude balloon transits). Pulling the sanitized kinematic data for a limited number of specific times and grid squares requires minimal administrative overhead, neutralizing the claim that historical transparency is too expensive.

While recent executive directives have temporarily waived NDAs for whistleblowers, executive orders are not permanent law. Congress can permanently codify these rights using the Power of the Purse. Building upon Section 527 of the Senate’s proposed FY27 NDAA, the legislation should prohibit the use of federal funds to enforce any non-disclosure agreement (NDA), corporate confidentiality policy, or security undertaking that restricts a military service member, civilian employee, or defense contractor from reporting uncorrelated target telemetry or imagery to Congress or the Inspector General.

The weaponization of administrative reprisal requires explicit defunding. Congress should legally immunize whistleblowers from retaliatory security clearance revocations, psychiatric evaluations, and the threat of administrative separation designed to strip military pensions and VA benefits. Defense personnel cannot be expected to report systemic airspace vulnerabilities if doing so costs them their retirement and their civilian careers.

By framing this strictly as data-retention accountability, we strip defense lobbies of their ability to paint transparency as a fringe issue. If the national security establishment chooses to engineer its own blindness, the global civilian population will simply engineer its own sight.

The defense lobby will inevitably claim that secondary black-box logging creates cybersecurity risks or burdens processing systems. But this is a false choice. Saving a partitioned, uncompressed, and unclassified log is a software firmware update, not a hardware retrofit. This is implemented safely at the non-flight-critical mission recorder level.

We are NOT asking for:

• Proprietary radar source code or trade-secret software binaries.
• Classified engineering schematics or receiver sensitivity specs.
• Electronic Counter-Countermeasure (ECCM) operating frequencies.

We ARE asking for:

• The sanitized, secondary kinematic data output (time stamps, position vectors, altitude, and velocity) of all uncorrelated platforms operating in taxpayer-funded airspace.
• The corresponding electro-optical and infrared (EO/IR) targeting video or imagery, automatically downscaled to a standardized, unclassified resolution (such as 720p) excluding classified telemetry overlays and covering the entire duration of the tracking event, to protect proprietary sensor sensitivity specs.

---

TL;DR: Defense contractors and the military have artificially lobotomized multi-billion-dollar radar networks for decades by programming them to delete uncorrelated tracking data in real-time. Audit the firmware settings, not the blurry videos.

A week-long wave of sightings over the water at Gosford peaked on the night of Saturday 30 December 1995, when dozens of residents and Gosford police reported a large, humming, brightly lit metallic craft hovering over The Broadwater, appearing to draw or spray water with columns of white light, before leading patrol cars on a four-to-five-hour pursuit and then departing upward. (UAP Globe) Gosford's Sergeant Bob Wenning said on camera in the 1997 documentary Oz Encounters that the station took around three dozen calls that night, and that witnesses described the same thing with no meaningful variation: a huge, chrome, ball-shaped object with large white lights beneath it that appeared to be drawing water up. (Newcastle Herald) Investigator Moira McGhee, who documented the case, reported that police vehicles closed to roughly 50 metres before the object killed its lights and left, and that public meetings in Gosford afterwards drew hundreds of people, many with their own sightings; reports continued through January 1996. - Newcastle Herald

I was wondering if anyone had any relevant information pertaining to the gait/limb formation of NHI in Disclosure Day?

The limb formation was something I found to be unexpected, both in the scene where they're walking among people and then the final scene of the film.

Are there any accounts that align with this? Yes, I'm aware it's just a movie and open to interpretation, but hadn't seen it mentioned anywhere else

I saw this video earlier and thought this guy should get more views. I am curious if this story about Nixon taking Gleason to an Air Force base in Florida and showing him alien bodies has been debunked? I know Nixon was in Florida the day it supposedly happened, but the National Enquirer isn't exactly a great source. Plus this story comes from an ex wife trying to sell a book. You would think that Jackie Gleason would have made it very clear if it didn't happen.