Did the Pentagon release a video of six spheres going 480 mph? What DOW-UAP-PR135 actually says

DOW-UAP-PR135 is a public DVIDS video, not a closed AARO case card. Verified title: DOW-UAP-PR135, Unresolved UAP Report, Middle East, 2025.

Video ID 1023397. Final URL stayed on that ID. HTTP 200 this run. Date Posted 09.18.2026 07:15. Length 00:00:59. Location undisclosed. Category B-Roll. Courtesy All Domain Anomaly Resolution Office. Filename DOD_111985782. VIRIN 250101-D-D0360-6771.

The description says the United States Central Command submitted a report of an unidentified anomalous phenomenon to AARO consisting of 1 minute of video from an infrared sensor aboard a U.S. military platform in 2025. Metadata length is 59 seconds. Treat both as the public packaging of one short clip, not as two different videos.

Courtesy AARO on a DVIDS page is hosting and release packaging. It is not a confidence-rated resolution and not a finding that the objects were anomalous.

Use the hub Release 06 inventory when the question is the featured September 18 mix. Use this page when the question is the six-sphere speed claim itself.

The extractable block for this brief is a claim-layer table. Read each row as a separate product. Mixing them is how a 480 mph sentence becomes fake kinematics.

Layer | What official text supports | What it does not prove

DVIDS title and Video ID 1023397 | A public unresolved report label exists: Middle East, 2025, posted September 18, 2026, 59 seconds, undisclosed location | Object identification, anomaly, or extraterrestrial origin

CENTCOM-to-AARO sentence | A report and about one minute of infrared footage were submitted from a U.S. military platform in 2025 | Native telemetry export, range, or a closed performance card

D108 as named on DVIDS | The video page attributes six-sphere, seeming-agile, direction-change, and 480 mph language to mission report DOW-UAP-D108 | That this brief has quoted the PDF interior

480 mph sentence | A reporter estimate is in the public description | Reconstructed physical velocity

Timeline 00:05 to 00:47 | Contrast areas transit the frame. The sensor pans to keep them centered. Magnification later changes | That pan rate or zoom is object speed or agility

Informational-only disclaimer | AARO says the description is not a judgment, conclusion, or factual determination | A finished case resolution

Same-morning post window | DVIDS posted this clip at 07:15 on September 18, 2026, the morning of the sixth PURSUE tranche | That the live war.gov highlight table lists PR135. That row was not re-read this run

The official sentence is narrow. The reporter estimated the speed of the UAP to have been 480 miles per hour. Estimate is the limiter. Reporter is the source of the number on this page.

A reporter estimate is not reconstructed physical velocity. The public page does not give range, platform velocity, aspect geometry, or sensor field angle. Those inputs are still required before a screen clip becomes a speed.

Do not upgrade the sentence into Central Command confirmed 480 mph, or AARO measured 480 mph, or the objects outran the aircraft. The page does not say any of those things.

The behavior words sit in the same attributed sentence family. The page's wording is seem[ingly] agile and frequently changing direction, attributed to DOW-UAP-D108. The brackets are on the DVIDS page. Do not drop them and turn seeming agile into an AARO performance finding.

Use the hub velocity data-limits brief when the question is why pixel motion and mission-report speed talk are not kinematics. This page does not import a closed GoFast card onto PR135.

The official timeline is about the sensor, not a reconstructed track.

00:00 to 00:04: no content. 00:05 to 00:10: several areas of contrast transit the field of view, entering from the top and exiting from the bottom. 00:11 to 00:47: the sensor pans to track those areas and keep them generally centered. 00:48 to 1:00: the sensor changes magnification, then no content.

A pan that recenters contrast is camera behavior. A magnification change is camera behavior. Neither sentence is an object turn rate.

Secondary writeups that say the video shows spheres making changes in direction are restating the mission-report paraphrase, not reading a finished track. Cite the timestamp bands if you describe what the public timeline actually says.

The page also says the description is for informational purposes only. Readers should not treat any part of it as an analytical judgment, investigative conclusion, or factual determination about the event's validity, nature, or significance.

DOW-UAP-D108 is the mission-report ID named on the verified DVIDS page. That is the safe use of the ID today.

A guessed war.gov PDF URL for D108 returned HTTP 403 HTML this run, not a PDF. Direct fetches of war.gov PURSUE files often do that. Do not quote interior lines, unit names, altitudes, headings, or incident clocks from secondary transcripts until the official PDF body is extracted and checked.

Safe citation of D108: the video page attributes the six-sphere description, the seeming-agile and direction-change language, and the 480 mph reporter estimate to that file ID. Unsafe citation: paste a third-party OCR as if this brief had opened the mission report.

Date Taken on the video card is 01.01.2025. The VIRIN starts 250101, the same calendar stamp. A different Middle East 2025 unresolved clip posted the same minute, DOW-UAP-PR133 at Video ID 1023396, carries Date Taken 01.01.2025 and a 250101 VIRIN prefix. Shared card stamp is not an incident day.

Until D108 is extracted, this page does not state an incident date. 2025 and Middle East are the official year and region labels. January 1 is a card field.

Do not guess neighbor DVIDS IDs. A URL built as if Video ID 1023396 were PR134 resolved to DOW-UAP-PR133, Unresolved UAP Report, Middle East, 2025. Cite 1023396 only as PR133. Do not attach any other numeric ID to PR134 or PR135 unless that exact final URL body matches the claimed title.

Do not import the Gulf of Oman cold-orb caveat onto this clip, and do not upgrade this clip past what the page says. PR117 through PR122 are a different product: secondary cellphone-of-screen captures with not-finally-evaluated report language. PR135's page says infrared footage from a sensor aboard a U.S. military platform. That sentence is not a published telemetry export. Missing range is still missing range.

Do not collapse this clip with PURSUE Release 04 Yellow Sea and East China Sea 2025 videos (PR104 and PR105). Different file IDs, different region labels, different tranche.

Do not import western United States mother-orb language. Orange mother orb, red orbs, and orbs launching orbs are a separate unresolved analysis. Six small spherical objects in a 2025 Middle East mission-report paraphrase are not that case.

Do not treat the hub Release 06 highlight inventory as if it already listed PR135. That inventory's featured rows are the rotator set: D102, D110, D111, D117, D129, D154, PR159, PR160, and two LLE Colorado clips. PR135 is a same-morning DVIDS post, not one of those highlight rows.

Live war.gov/ufo Release 06 HTML returned HTTP 403 this run. Same-day posting is not table-row proof. Say DVIDS posted the labeled unresolved report on the morning of the sixth tranche. Do not say the live highlight table contains PR135 until that filter is re-read.

Name the product: DOW-UAP-PR135, DVIDS Video ID 1023397, posted September 18, 2026 at 07:15, runtime 00:00:59, undisclosed location, courtesy AARO.

Name the submission sentence: Central Command submitted about one minute of infrared footage from a U.S. military platform in 2025.

If you mention six spheres, agility, direction changes, or 480 mph, keep the attribution in the same clause: mission report DOW-UAP-D108, as paraphrased on the DVIDS page, including the reporter estimate and the bracketed seem[ingly] agile wording.

Keep the informational-only fence in the same sentence family. Description is not judgment.

If you describe motion, quote the sensor timeline. Pan and magnification change are not object kinematics.

Cite D108 as a file ID named on the video page. Do not paste secondary transcript pages as the official PDF.

Keep January 1, 2025 off the incident line. It is Date Taken on the card, paired with VIRIN prefix 250101, and it repeats on at least one other same-morning Middle East 2025 clip.

Safe citation: On September 18, 2026, DVIDS posted DOW-UAP-PR135, a 59-second unresolved infrared clip (Video ID 1023397). The page says Central Command sent AARO about one minute of footage from a U.S. military platform in 2025, and that DOW-UAP-D108 described six small spherical objects as seeming agile and frequently changing direction, with a reporter estimate of 480 mph. That description is informational only. A reporter estimate is not reconstructed speed. Unresolved release is not extraterrestrial proof.

Unsafe upgrade: the Pentagon confirmed six orbs flying at 480 mph, the video shows the objects turning because the sensor panned, January 1, 2025 is the incident date, or this clip proves alien craft.