Misrep 4871281
AREC mission from 482ATKS. Received multiple guard calls and observed 1x UAP at 1829Z.
Two electromagnetic interference events knocked the aircraft's link dead -- 11 minutes the first time, 27 the second -- causing flight path deviations. Three hours after the second EMI event, at 1732Z, a UAP appeared on FMV in the same general grid area. The 482nd Attack Squadron was running armed recon over the Strait of Hormuz on September 15-16, 2020. Iranian Air Defense broadcast three guard calls during the flight (two directive, one professional). The crew also identified an SA-5 launcher on Abu Musa Island and possible Houdong patrol boats at pierside.
- UAP observed at 1732Z via FMV (full motion video) sensor at grid 39RVM5, aircraft at FL180 and 90 KIAS
- Two EMI/lost-link events of unknown type caused flight path deviations and complete system impact (11 min and 27 min duration)
- UAP observation occurred approximately 3 hours after second EMI event in the same general grid area
- Three guard calls from Iranian Air Defense during mission; all responded to with standard procedures, no mission impact
- Iranian military assets identified: SA-5 launcher at Abu Musa Island, 2x possible Houdong WPTG docked at pierside
- Mission focused on characterizing IRGCN vessels, UAS activity, and establishing pattern of life
- Intelligence gap NOT filled despite 15.2 hours of IMINT and 19.3 hours of SIGINT collection
Page 1
View PDF ↗- 2020-09 | mission month (specific date redacted)
- 2302Z | aircraft takeoff from OKAS
- 2313Z | handover from LRE
- 2346Z to 1902Z | SIGINT collection period
- 0318Z to 1829Z | IMINT collection supporting NAVCENT operations
- 0408Z | guard call 1 received
- 0421Z | guard call 2 received
- 1141Z | guard call 3 received
- 1248Z | lost link event 1
- 1414Z | lost link event 2
- 1732Z | UAP observed
- 1829Z | cleared to RTB
- 1923Z | handed back to LRE
- 1958Z | landed at OKAS
- 2026-01-22 | declassification date
- 482 ATKS (482nd Attack Squadron) | originating unit
- USCENTCOM | command authority
- NAVCENT (Naval Forces Central Command) | supported unit
- DGS1 (Defense General Support 1) | FMV exploitation entity
- AARO | approval authority
- OKAS (base identifier) | takeoff and landing location
- Arabian Gulf | operational area
- Strait of Hormuz | operational area
- Gulf of Oman | operational area
- 2302Z: takeoff
- 2313Z-1902Z: SIGINT collection via airhandler
- 0318Z-1829Z: IMINT operations supporting NAVCENT in Arabian Gulf, Strait of Hormuz, and Gulf of Oman
- 0408Z: guard call 1 (details in GUARD CALL LINE 1)
- 0421Z: guard call 2 (details in GUARD CALL LINE 2)
- 1141Z: guard call 3 (details in GUARD CALL LINE 3)
- 1248Z: lost link event 1 (details in EMI LINE 1)
- 1414Z: lost link event 2 (details in EMI LINE 2)
- 1732Z: UAP observation (details in OBS LINE 1)
- 1829Z: cleared to RTB
- 1923Z: handed back to LRE
- 1958Z: landed at OKAS
- Total Mission Hours: 20.9 hours
- IMINT Hours: 15.2
- IMINT Taskings Prosecuted: 1
- SIGINT Hours: 19.3
- SIGINT Taskings Prosecuted: 1
- Total Taskings Prosecuted: 2
- ISR LINE 1 | intelligence surveillance and reconnaissance details
- GUARD CALL LINE 1 | guard call 1 details
- GUARD CALL LINE 2 | guard call 2 details
- GUARD CALL LINE 3 | guard call 3 details
- EMI LINE 1 | lost link event 1 details
- EMI LINE 2 | lost link event 2 details
- OBS LINE 1 | UAP observation details
- Misrep 4782130 | mission report identifier
- MDR 26-0019 | document control number
- Classification level | shown as black bar
- Associated Caveats | shown as black bar
- Takeoff time details | 1.4a redaction
- Handover time | 1.4a redaction
- SIGINT collection period | 1.4a redaction
- Supported operation | 1.4a redaction
- Multiple guard call and lost link times | 1.4a redactions
- UAP observation time | 1.4a redaction
- Cleared to RTB | 1.4a redaction
- Handed back to LRE | 1.4a redaction
- Landing | 1.4a redaction
- Operation name | 1.4a redaction
- General section | 3.5c, (b)(6)
- Mission from older timeframe (September 2020) compared to 2022 and 2023 missions
- Recent declassification (22 January 2026)
- Long mission duration of approximately 20.9 hours
- Significant IMINT and SIGINT collection operations
- Three separate guard calls received during mission
- Two lost link events recorded
- One UAP observation at 1732Z during NAVCENT operations
- FMV exploitation by DGS1
- Approved for Release to AARO
Page 2
View PDF ↗- Tasking Order (ATO): [redacted via 1.4a]
- Mission Type: AREC (Armed Reconnaissance)
- ATO Mission Number: [redacted via 1.4a]
- Country Tasked: US - UNITED STATES
- Service Tasked: A - AIR FORCE
- SSgt (Staff Sergeant) [name redacted via 3.5c, (b)(3), 130b, (b)(6)] | POC, 482 ATKS, 432 AEW, Air Force
- Ctr (Controller) [name redacted via 3.5c, (b)(6)] | QC, 12 AF Det 3 PAROC, Air Force
- SrA (Senior Airman) [name redacted via 3.5c, (b)(3), 130b, (b)(6)] | Approver, 609th AOC, Air Force
- 482 ATKS | originating unit
- 432 AEW | wing assignment
- 12 AF Det 3 PAROC | QC unit
- 609th AOC | approver's operations center
- 609 CAOC | operations center for POC and approver
- Tasking Order (ATO) | 1.4a redaction
- ATO Mission Number | 1.4a redaction
- POC Full Name | 3.5c, (b)(3), 130b, (b)(6)
- POC Phone Number | 3.5c, (b)(6)
- POC Email | 3.5c, (b)(6)
- QC Full Name | 3.5c, (b)(6)
- QC Phone Number | 3.5c, (b)(6)
- QC Email | 3.5c, (b)(6)
- Approver Full Name | 3.5c, (b)(3), 130b, (b)(6)
- Approver Phone Number | 3.5c, (b)(6)
- Approver Email | 3.5c, (b)(6)
- General section | 3.5c, (b)(6)
- Mission Type AREC indicates armed reconnaissance mission
- Similar personnel structure to other 482 ATKS missions
- Declassified by MG Richard A. Harrison, USCENTCOM Chief of Staff on 22 January 2026
- Approved for Release to AARO
Page 3
View PDF ↗- Rank: [blank]
- Full Name: [blank]
- Unit: [blank]
- Wing: [blank]
- Phone Number: [blank]
- Email: [blank]
- Service: [blank]
- Operations Center: [blank]
- Aircraft Callsign: [redacted via 1.4a]
- TGT Pod Name or Designator: ANDAS4 (targeting pod)
- Additional Avionics: AH_GMESH (air-to-air radar and GMESH network)
- Air-to-Ground Wpn to Include Num of Each: [redacted via 1.4a]
- Radar Name or Destination: not applicable
- Radar Software Load: not applicable
- Radar Warning Receiver (RWR) | not applicable
- MWS | not applicable
- IRCM | not applicable
- ECM | not applicable
- CMD | not applicable
- Chaff/Flare systems | not equipped
- Towed Decoys | not equipped
- Air-to-Air Missiles (AAM) | not equipped
- Gun armament | not equipped
- Data Link: not shown
- Aircraft Callsign | 1.4a redaction
- Air-to-Ground Weapons | 1.4a redaction
- General section | 3.5c, (b)(6)
- INGEST section empty/incomplete
- Aircraft equipped for armed reconnaissance with targeting pod
- Similar weapons/avionics configuration to other 482 ATKS missions
- ANDAS4 targeting pod consistent with previous mission reports
Page 4
View PDF ↗- 2020-09-15 23:02Z | takeoff time
- 2020-09-15 23:13Z | on station time
- 2020-09-16 03:18Z | ISR time-on station
- 2020-09-16 18:29Z | ISR time-off station
- 2020-09-16 19:58Z | landing time
- 2020-09-16 20:08Z | last engine shutdown time
- Callsign: [redacted via 1.4a]
- Number of Aircraft: 1
- Asset Type (Aircraft): [redacted via 1.4a, 1.4g]
- Aircraft Tail Number(s): [redacted via 1.4a]
- Mode 3 (IFF Codes): not provided
- Total Mission Time: 20 hours 56 minutes
- Time On Station: approximately 17 hours 46 minutes (from 0318Z to 1829Z)
- Mission Type: AREC (Armed Reconnaissance)
- JTAR Number: not applicable
- Killbox: not applicable
- JTAC Callsign: not applicable
- Callsign (multiple sections) | 1.4a redactions
- Asset Type | 1.4a, 1.4g redactions
- Aircraft Tail Number | 1.4a redaction
- General section | 3.5c, (b)(6)
- AREC mission type (differs from ISR designation on other missions)
- Extended mission duration of approximately 21 hours
- UAP observation occurred at 1732Z during this mission (from page 1)
- Multiple guard calls and lost link events during mission
- Data exploited by DGS1
Page 5
View PDF ↗- 2020-09-16 03:18Z | arrived on station
- 2020-09-16 09:30Z | IR launcher observed
- 2020-09-16 13:21Z | Houdong WPTG observed
- 2020-09-16 04:08Z | guard call 1
- 2020-09-16 04:21Z | guard call 2
- 2020-09-16 11:41Z | guard call 3
- 2020-09-16 17:32Z | noteworthy activity observed
- 2020-09-16 18:29Z | cleared off tasking
- NAVCENT (Naval Forces Central Command) | supported unit
- Iranian Islamic Revolutionary Guard Corps Navy (IRGCN) | observed entity
- Arabian Gulf (AG) | operational area
- 40RCQ3 [coordinates redacted] | tasked start point
- Abu Musa Island | IR launcher location
- 40RCP0 [coordinates redacted] | launcher location (Abu Musa Island)
- 39RXL6 [coordinates redacted] | Houdong WPTG location
- 1 IR-SA-5 launcher observed at Abu Musa Island
- 2x possible Houdong WPTG (wheeled patrol torpedo gun) observed docked at pierside
- Noteworthy activity observed at 1732Z (UAP observation - referenced in OBS LINE 1)
- Multiple guard calls received from Iranian sources
- Primary Sensor: ANDAS4 (targeting pod)
- Sensors Available: AH\GMESH (air-to-air radar and network)
- Tasking Type: PLANNED
- Activity Description: ISR
- Precoord Time: 24 HOURS
- Precoord Effectiveness: SATISFACTORY
- Mission objective: Characterize Iranian/IRGCN vessels, UAS activity, activity outside ports, establish pattern of life
- From 0318Z to 1829Z: Conducted scans per target deck in Arabian Gulf
- Identified Iranian military assets and vessels
- Three guard call events during operations
- Intel Gap Filled?: No
- Weather: Was not a factor
- Classification level | shown as red bar
- Start point coordinates | 1.4a redactions
- Operation name | 1.4a redactions
- Various observation times | 1.4a redactions
- Specific observation locations | 1.4a redactions
- General section | 3.5c, (b)(6)
- "COORDINATED NAVCENT 24 HOURS PRIOR TO TAKE OFF. PRECOORD WAS SATISFACTORY"
- "CHARACTERIZE IRNV/RGCN VESSELS, UAS ACTIVITY, ACTIVITY OUTSIDE OF PORTS, AND TO ESTABLISH PATTERN OF LIFE"
- "OBSERVED AN IR-SA-5 LAUNCHER"
- "OBSERVED 2X POSSIBLE HOUDONG WPTG"
- Comprehensive surveillance of Iranian naval assets
- Focus on pattern of life and military capabilities
- Multiple layers of operational security (guard calls, sensor data)
- "Noteworthy Activity" at 1732Z is the UAP observation referenced in page 1
Page 6
View PDF ↗- 2020-09-16 04:08Z | guard call 1
- 2020-09-16 04:21Z | guard call 2
- 2020-09-16 11:41Z | guard call 3
- Time Off Station: 161923:00ZSEP20 (2020-09-16 19:23Z)
- Total Time On Station: 20 hours 10 minutes
guard_call_1:
- GUARDCALL DTG: 160408:00ZSEP20
- Aircraft Callsign: [redacted via 1.4a]
- Ground Station Callsign: IRANIAN AIR DEFENSE
- Aircraft Location: 40RCP7 [coordinates redacted via 1.4a]
- Aircraft Heading: 360T (true north)
- Aircraft Altitude: FL180 (18,000 feet)
- Aircraft Airspeed: not provided
- Number of Calls from Same Agency: 1
- Guardcall Tone: DIRECTIVE
- Gentext: At 0408Z, [aircraft] WAS HAILED ON GUARD FREQ BY IRANIAN AIR DEFENSE. STANDARD ORDERS GIVEN. [Aircraft] RESPONDED WITH THE STANDARD RESPONSE. NO IMPACT TO MISSION
guard_call_2:
- GUARDCALL DTG: 160421:00ZSEP20
- Aircraft Callsign: [redacted via 1.4a]
- Ground Station Callsign: IRANIAN AIR DEFENSE
- Aircraft Location: 40RCP7 [coordinates redacted via 1.4a]
- Aircraft Heading: 010M (magnetic)
- Aircraft Altitude: FL180
- Aircraft Airspeed: not provided
- Number of Calls from Same Agency: 1
- Guardcall Tone: DIRECTIVE
- Gentext: At 0421Z, [aircraft] WAS HAILED ON GUARD FREQ BY IRANIAN AIR DEFENSE. STANDARD ORDERS GIVEN. [Aircraft] RESPONDED WITH THE STANDARD RESPONSE. NO IMPACT TO MISSION
guard_call_3:
- GUARDCALL DTG: 161141:00ZSEP20
- Aircraft Callsign: [redacted via 1.4a]
- Three separate guard calls from Iranian air defense
- All guard calls directive in tone (commanding rather than informational)
- All occurred in same geographic area
- No operational impact from any guard calls
- Aircraft responded with standard response procedures each time
- Iranian air defense maintained active radar/radio tracking
- Aircraft callsign (multiple instances) | 1.4a redactions
- Aircraft locations | 1.4a redactions
- Guard call frequencies | 1.4a redactions
- General section | 3.5c, (b)(6)
- Classification level | shown as red bars
- "STANDARD ORDERS GIVEN"
- "RESPONDED WITH THE STANDARD RESPONSE"
- "NO IMPACT TO MISSION"
- Multiple directive (commanding) guard calls from Iranian air defense
- All three calls occurred early in mission (0408Z-1141Z)
- Aircraft maintained operations despite guard calls
- Standard protocol followed for all interactions
- Guard call 3 details continue on next page
Page 7
View PDF ↗guard_call_3_continued:
- Ground Station Callsign: IRANIAN AIR DEFENSE
- Aircraft Location: 40RCP2 [coordinates redacted via 1.4a]
- Aircraft Heading: 277T
- Aircraft Altitude: FL040 (4,000 feet)
- Aircraft Airspeed: not provided
- Number of Calls from Same Agency: 1
- Guardcall Tone: PROFESSIONAL (different from first two which were DIRECTIVE)
- Gentext: At 1141Z, [aircraft] WAS HAILED ON GUARD 243.000 FREQ BY IRANIAN AIR DEFENSE. STANDARD ORDERS GIVEN. [Aircraft] RESPONDED WITH STANDARD RESPONSE. NO IMPACT TO MISSION
emi_event_1:
- EMI Start DTG: 161248:00ZSEP20 (2020-09-16 12:48Z)
- EMI End DTG: 161259:00ZSEP20 (2020-09-16 12:59Z)
- EMI Duration: 11 minutes
- Aircraft Callsign: [redacted via 1.4a]
- Type of EMI: UNKNOWN
- Aircraft Location: 39RXK0 [coordinates redacted via 1.4a]
- Aircraft Heading: 290T
- Aircraft Altitude: FL180
- Aircraft Airspeed: 89 KIAS
- EMI Location: 39RXK0 [coordinates redacted via 1.4a]
- Mission Changed: Flight Path Deviation
- EMI Impact to System: Complete
- Affected System: [redacted via 1.4a]
- Frequency Affected: [redacted via 1.4g]
- Mission Impact: MEDIUM
- Gentext: At 1248Z, [aircraft] EXPERIENCED LOST LINK TO POSSIBLE [redacted via 1.4g and 1.4a]. REGAINED LINK AT 1259Z. THIS RESULTED IN A MEDIUM IMPACT TO THE MISSION
- JSIR ID: 330412
emi_event_2:
- EMI Start DTG: 161414:00ZSEP20 (2020-09-16 14:14Z)
- EMI End DTG: 161441:16ZSEP20 (2020-09-16 14:41:16Z)
- Two separate lost link events during mission
- First event lasted 11 minutes
- First event caused flight path deviation
- Complete system impact for first EMI event
- Medium mission impact from first EMI event
- Possible Iranian jamming or electronic interference
- Second EMI event approximately 1 hour 15 minutes after first
- Aircraft locations | 1.4a redactions
- Affected systems | 1.4a redaction
- Frequency affected | 1.4g redaction
- Source of EMI interference | 1.4g, 1.4a redactions
- Guard call frequency | 1.4a redaction
- Aircraft heading on guard call 3 | 277T
- General section | 3.5c, (b)(6)
- Classification level | shown as red bars
- Guard call 3 tone PROFESSIONAL indicates shift in Iranian interaction
- Lost link events documented with JSIR ID
- First EMI event forced flight path deviation
- EMI likely associated with Iranian air defense systems
- Aircraft recovered link and continued operations
- Second EMI event details continue on next page
Page 8
View PDF ↗emi_event_2_continued:
- EMI Start DTG: 161414:00ZSEP20 (2020-09-16 14:14Z)
- EMI End DTG: 161441:16ZSEP20 (2020-09-16 14:41:16Z)
- Aircraft Callsign: [redacted via 1.4a]
- Type of EMI: UNKNOWN
- EMI Duration: 27 minutes
- Aircraft Location: 39RVM9 [coordinates redacted via 1.4a]
- Aircraft Heading: 264T
- Aircraft Altitude: FL180
- Aircraft Airspeed: 120 KIAS
- Mission Changed: Flight Path Deviation
- EMI Impact to System: Complete
- EMI Location: 39RVM9 [coordinates redacted via 1.4a]
- Affected System: [redacted via 1.4a]
- Frequency Affected: [redacted via 1.4g]
- Mission Impact: MEDIUM
- Gentext: At 1414Z, [aircraft] EXPERIENCED LOST LINK TO POSSIBLE [redacted via 1.4g and 1.4a]. REGAINED [link] AT 1441Z. THIS RESULTED IN A MEDIUM IMPACT TO THE MISSION
- JSIR ID: 330414
- Observation DTG: 161732:00ZSEP20 (2020-09-16 17:32Z)
- Aircraft Callsign: [redacted via 1.4a]
- Aircraft Location: 39RVM5 [coordinates redacted via 1.4a]
- Aircraft Altitude: FL180
- Aircraft Airspeed: 90 KIAS
- Aircraft Heading: not provided
- Relative Bearing or Clock Position: not provided
- Range: not provided
- Observed Activity Location: 39RVM5 [coordinates redacted via 1.4a]
- Observed Activity Description: UAP
- Method of Observation: FMV (Full Motion Video)
- Gentext: At 1732Z, [aircraft] OBSERVED A UAP IVO 39RVM5 [coordinates redacted via 1.4a]
- UAP observed via FMV sensor
- Observation occurred approximately 3 hours after second EMI event
- Observation occurred at FL180, same altitude as aircraft when experiencing EMI events
- Location in grid 39RVM5 (slightly different grid than EMI events in 39RVM9)
- UAP observation represents the "noteworthy activity" referenced in page 1 and page 5
- Aircraft callsign | 1.4a redaction
- EMI location | 1.4a redactions
- Affected systems | 1.4a redaction
- Frequency affected | 1.4g redaction
- Source of EMI | 1.4g, 1.4a redactions
- UAP location coordinates | 1.4a redactions
- General section | 3.5c, (b)(6)
- Classification level | shown as red bars
- Second EMI event longer duration (27 minutes vs 11 minutes for first event)
- Both EMI events caused flight path deviation
- Both had complete system impact
- Both resulted in medium mission impact
- UAP observation occurred in same general area as EMI events
- Observation conducted via FMV provides direct visual record
- Weather section follows but not shown on this page
Page 9
View PDF ↗- Classification level | shown as red bar
- General section | 3.5c, (b)(6)
- Final page of mission report Misrep 4782130
- Weather conditions did not impact mission operations
- All mission objectives completed despite three guard calls and two EMI events
- UAP observation successfully captured via FMV
- Mission declassified by MG Richard A. Harrison, USCENTCOM Chief of Staff on 22 January 2026
- Approved for Release to AARO