Clouds Periodically Obscured a Moving Phenomenon in the Gulf
A US military member reported it during a mission. The report doesn't reveal what was seen.
A US military member reported it during a mission. The report doesn't reveal what was seen.
A US military member reported a moving phenomenon in the Arabian Gulf. Dense clouds periodically interfered with video recording, and the report did not identify what it was.
USCENTCOM Mission Report (MISREP 4592219) from the 482d Attack Squadron documenting a 21-hour ISR sortie over the Arabian Gulf, Strait of Hormuz, and Gulf of Oman on 8 August 2020 in support of NAVCENT. The aircraft (callsign and asset type redacted under 1.4a) collected SIGINT via AIRHANDLER and conducted FMV scans of identified IRIN/IRGCN vessels. At 0726Z the crew observed 1x UAP transiting in the vicinity of grid 39RWL957[redacted], with no impact to mission; dense cloud coverage intermittently impacted FMV collection. The aircraft was also hailed once on GUARD by Iranian Air Defense at 1250Z and gave a standard response.
During an ISR mission supporting NAVCENT, the aircraft observed 1x UAP transiting; observation made via FMV. No impact to mission. Dense cloud coverage intermittently impacted FMV collection effectiveness.
Aircraft hailed on GUARD by Iranian Air Defense; standard call/standard response exchanged. Tone professional. No impact to mission.
"AT 0726Z,[1.4a] OBSERVED 1X UAP IVO 39RWL957[1.4a][1.4a] NO IMPACT TO MISSION."
Why it matters: Primary UAP observation entry in the OBSERVATION GENTEXT.
Page 5
"DENSE CLOUD COVERAGE INTERMITTANTLY IMPACTED FMV COLLECTION"
Why it matters: Weather caveat on the ISR sensor that observed the UAP.
Page 6
"AT 1250Z,[1.4a] WAS HAILED ON GUARD [1.4a] BY IRANIAN AIR DEFENSE. ORDERS GIVEN: STANDARD CALL [1.4a] RESPONDED STANDARD RESPONSE. NO IMPACT TO THE MISSION"
Why it matters: Documents an Iranian Air Defense radio interaction during the same sortie.
Page 4
"FROM 0513Z TO 2256Z,[1.4a] SUPPORTED NAVCENT TO OPERATION [1.4a] IVO. ARABIAN GULF, STRAIT OF HORMUZ AND GULF OF OMAN."
Why it matters: Establishes operational context for the UAP observation.
Page 1
"20.3 MISSION HOURS, 17.7 IMINT HOURS, 1 IMINT TASKING PROSECUTED, 18.4 SIGINT HOURS, 1 SIGINT TASKING PROSECUTED, 2 TOTAL TASKINGS PROSECUTED"
Why it matters: Mission scale summary for the sortie during which the UAP was observed.
Page 1
MG Richard A. Harrison
USCENTCOM Chief of Staff (declassification authority) · USCENTCOM · Page 1
OKAS (takeoff/landing ICAO), Kuwait
Page 1
Arabian Gulf
Page 1
Strait of Hormuz
Page 1
Gulf of Oman
Page 1
Persian Gulf
Page 1
Observed activity location 39RVL901[redacted]
Page 4
UAP location IVO 39RWL957[redacted]
Page 5
482d Attack Squadron (482ATKS)
U.S. Air Force · Page 1
432 AEW
U.S. Air Force · Page 2
609th AOC / 609 CAOC
U.S. Air Force · Page 2
603 AOC
U.S. Air Force · Page 2
NAVCENT
U.S. Navy · Page 6
DGS1 (Distributed Ground System 1)
U.S. Air Force · Page 1
Aircraft callsign and asset type throughout narrative
Likely reason: 1.4a (military plans, weapons systems, operations)
Operation name supported with NAVCENT
Likely reason: 1.4a
POC names, phone numbers, and emails (rank SrA, Cir, 1st Lt)
Likely reason: (b)(3) and (b)(6) — personal privacy / statutory
Air-to-Ground weapon load entry
Likely reason: 1.4(a)
INGEST section content
Likely reason: (b)(6)
Aircraft location grid coordinates digits in GUARDCALL (40RCP981...)
Likely reason: 1.4a
Observation aircraft and activity grid coordinates (39RWK9 / 39RVL901)
Likely reason: 1.4a
UAP location grid coordinate suffix (39RWL957...)
Likely reason: 1.4a
Tasked Start Point grid (39RVN34...) and operation name
Likely reason: 1.4a
USCENTCOM MISREP 4592219 from 482ATKS / 432 AEW, declassified by MG Richard A. Harrison and approved for release to AARO under USCENTCOM MDR 26-0038 to MDR 26-0046. Declassification date set to 20450301. Heavy redaction of callsign, asset type, weapons, and grid coordinates limits identification of the platform; ANDAS4 primary sensor and AH_GMESH avionics, plus AIRHANDLER SIGINT, suggest a long-endurance ISR/attack platform operating from OKAS (Ali Al Salem, Kuwait). Single UAP observed at 0726Z 8 Aug 2020 via FMV near MGRS 39RWL957 in the Arabian Gulf during NAVCENT IRIN/IRGCN pattern-of-life tasking.
The report describes a single moving phenomenon but does not identify it or describe its appearance.
No. According to the report, it had no impact on the mission.
ANDAS4 (targeting/primary sensor)
sensor · Page 3
AH_GMESH (additional avionics / sensor)
sensor · Page 3
AIRHANDLER (SIGINT collection system)
sensor · Page 1
FMV (Full Motion Video)
sensor · Page 5
In the Arabian Gulf, in August 2020, a US military member reported seeing an unidentified phenomenon. The report describes it as something that moved from place to place.
There's a detail here that complicates the picture: dense clouds periodically interfered with video recording. The report mentions movement, but the documentation was not collected without interruption. Nevertheless, according to the record, the phenomenon did not affect the mission.
The incident was included in a US military mission report. The person who reported it was a military member in an operational role; the record does not specify their exact position. It describes a single sighting, not several separate events.
The term "unidentified" here simply means that the observed object was not identified. The report adds that the phenomenon moved from place to place. That's all that can be learned from it about the movement: it contains no details of a trajectory or direction.
The record states that dense cloud cover periodically interfered with video documentation. This means that the clouds made recording difficult for part of the time. The report does not say that recording stopped entirely, or how much of the phenomenon was captured.
This creates a partial picture: there's a report of something moving, and at the same time, clouds interfered with the documentation. The record does not describe the phenomenon beyond this. It also does not say what was seen in the video, if any additional details could be learned from it. In other words, the only thing clearly described is the movement itself, alongside the difficulty in filming it.
Despite the interference with filming, the report notes that the phenomenon had no impact on the mission. Parts of the record were redacted, but it was not stated whether the redacted information was related to the sighting.
It is unknown what the phenomenon was or what caused it. The record does not offer a conventional explanation, nor does it describe its shape, color, or size.
What remains is a brief report of movement, with clouds repeatedly passing between the observation and the camera.