Why PURSUE UAP videos cannot prove how fast an object moved

This brief answers one high-intent question: can public PURSUE UAP sensor videos prove how fast an object moved?

It is not a craft-identification page. It is not a claim that every PURSUE clip is ordinary clutter. It is an evidence-quality densify off the PURSUE records trail, paired with AARO's public GoFast reconstruction lesson and forced-perspective / parallax methodology.

Use the hub PURSUE parent brief for program definition. Use the Release 05 inventory for the full tranche mix. Use the Pacific Ocean 2019 sibling for secondary-capture fidelity. Use this page when the question is velocity recovery from the public sensor-video set.

From released pixels alone, a careful reader can often measure how fast an image feature crosses the frame, the image size of that feature, and the container frame rate.

Those quantities describe image motion. They do not automatically become ground speed, air speed, or absolute velocity.

Converting pixels-per-frame into a physical velocity also requires range to the object, observer or platform velocity, the aspect angle between the relative-velocity vector and the line of sight, and the sensor angular scale or field of view at the object position.

If any of those inputs is missing, redacted, or only assumed, a confident Mach-class claim is not a measurement. It is a guess wearing telemetry clothing.

The extractable block for this brief is a checklist. Read each item as a hard gate, not optional flavor text.

1. Range to the object, ideally sampled over time, or a validated range proxy with stated assumptions.

2. Observer or platform ground velocity, not just a guess that the aircraft was flying fast.

3. Aspect geometry between the relative-velocity vector and the line of sight, or enough range-rate context to bound it.

4. Sensor angular scale or field of view at the object position in the frame.

5. Honest statement of what is redacted, missing, digitally altered, or secondary-capture limited in the public product.

6. Separate apparent screen motion from reconstructed kinematics. Do not quote pixels-per-frame as Mach speed.

7. Do not upgrade informational-only PURSUE captions into performance findings.

8. Keep closed AARO case cards separate from PURSUE unresolved packaging. GoFast method lessons transfer; GoFast object conclusions do not automatically transfer to every PURSUE clip.

If a claim skips the checklist, treat it as incomplete analysis, not as proof of exotic performance.

war.gov/ufo frames materials on the site as unresolved cases, meaning the government is unable to make a definitive determination on the nature of the observed phenomena. Resolved cases are reported under separate statutory paths.

The Department of War fifth-release statement on August 7, 2026 confirms another tranche of declassified and historical UAP files and says additional files will continue on a rolling basis.

Public DVIDS product pages for sensor clips often carry informational-only description footers. Readers should not treat those captions as analytical judgment, investigative conclusion, or factual determination of validity, nature, or significance.

Many public clips also show redacted on-screen telemetry or limited display metadata. Redaction is an evidence-access limit. It is not, by itself, proof of a cover-up of alien craft, and it is not proof that the object broke physics.

Tracked pods can keep a target near frame center. Near-zero pixel rate in a tracked clip can be sensor behavior, not a closed proof that the object matched the aircraft's velocity.

Verified DVIDS product: DOW-UAP-PR113, Unresolved UAP Report, Western United States, 1996. Video ID 1014119.

Official caption stack: Navy Unidentified Anomalous Phenomena Task Force transferred the media to AARO in 2022; about 2 minutes 57 seconds of footage likely captured by an infrared sensor aboard a U.S. military platform in 1996; digitally altered before reported to the UAPTF and presented as received by AARO; packaging includes frame-by-frame, slower playback, and still-frame sections; informational only; unresolved label.

Independent analysis highlights why PR113 is useful as a method example: visible depression-angle markings can support field-of-view reconstruction. Even with that help, the public clip still cannot separate a near slow object from a distant fast object because range and the rest of the kinematics set remain incomplete.

Safe citation: PR113 is a public unresolved IR product with an alteration-as-received caveat and partial angular markings that still leave absolute velocity underdetermined. Unsafe upgrade: PR113 proves a Mach-class craft because the image crosses the frame quickly, or digitally altered means exotic authenticity.

Verified DVIDS product: DOW-UAP-PR149, Unresolved UAP Report, Middle East, 2023. Video ID 1017799.

Official caption stack: U.S. Central Command submitted a report to AARO consisting of about 51 seconds of infrared sensor footage from a U.S. military platform in 2023; an area of contrast first transits, then the sensor pans to track it near frame center; informational only; unresolved label.

Independent analysis treats an in-frame vessel as a size reference and derives a relative-velocity upper bound under stated assumptions, on the order of about Mach 0.4 in that paper's worked example. That is a bound under assumptions, not a full object ID, not an absolute ground-track solution, and not an AARO case card.

Safe citation: PR149 is a public unresolved IR product where a ship reference can support a limited relative-speed bound if assumptions are explicit. Unsafe upgrade: PR149 proves exotic performance, or the upper bound is a government finding.

AARO's public GoFast case resolution covers a January 2015 U.S. Navy F/A-18F FLIR recording over the Atlantic Ocean off Florida.

AARO assesses with high confidence that the object did not demonstrate anomalous speeds or flight characteristics. Public AARO materials put the object at about 13,000 feet above sea level with a reconstructed speed range of roughly 5 to 92 miles per hour and a path consistent with wind drift near about 69 mph winds at that altitude.

The methodological contrast is the point. GoFast is the case where enough on-screen telemetry and reconstruction work existed to test the viral speed impression. Many public PURSUE clips lack an equivalent complete public kinematics set.

Do not import GoFast object conclusions onto PR113, PR149, or the full PURSUE corpus. Import the method lesson: reconstruct before you claim performance.

On August 12, 2026, Jacob Haqq-Misra and Ravi Kopparapu posted an arXiv preprint titled Limits on Velocity Recovery from the PURSUE Sensor Videos (arXiv:2608.12445).

The paper reviews the public PURSUE sensor-video corpus through Release 05, states that no released clip supplies the full kinematics set needed for physical velocity, and works PR113 and PR149 as examples. It cites AARO GoFast as the contrast case with more usable on-screen telemetry.

Rate it as secondary independent analysis of a primary corpus. It is a preprint, not peer-reviewed journal final form in the public trail used here. Author affiliation notes and the paper's own acknowledgment say views do not necessarily reflect agency or employer positions. Do not cite it as an AARO finding or a NASA official position.

Use the paper for method language and worked-example structure. Lead public citations with war.gov/ufo packaging, verified DVIDS product pages, and AARO GoFast method products.

Name the public product layer: PURSUE unresolved sensor videos released through war.gov/ufo, including the Release 05 tranche announced August 7, 2026.

Separate measurable image motion from reconstructed physical velocity. List the missing inputs: range, platform velocity, aspect geometry, and sensor field angle.

If using PR113 or PR149, use the verified DVIDS IDs only: 1014119 and 1017799. Do not invent neighboring numeric IDs.

Keep PR113 alteration-as-received and informational-only captions. Keep PR149 as a relative-bound example under assumptions, not a closed performance card.

Cite AARO GoFast for the reconstruction contrast, not as a blanket ID for every PURSUE clip.

If citing arXiv:2608.12445, label it independent preprint analysis of the public corpus, not agency doctrine.

Safe citation: public PURSUE sensor videos show unresolved reports and measurable screen motion, but the public clips do not supply a complete kinematics set for confident physical-velocity claims. Missing range and related inputs are an evidence limit. Unresolved is not anomalous performance proof and not extraterrestrial confirmation.

Unsafe upgrade: redacted telemetry proves aliens, pixel transit proves Mach 5, PR113 or PR149 are closed AARO anomalous findings, or the preprint is an official NASA or AARO conclusion.