DOW-UAP-D20: March 2023 report of 10-20 possible UAP

Official PDF

D20 source metadata

Document type

Mission report approved for release to AARO

Operation

Operation Inherent Resolve

Reported platform

F-16CM two-ship

Reported observation

Possible 10-20 bright objects, with a brief targeting-pod TV-mode observation

Missing public layer

Underlying targeting-pod video, radar/Link 16 data, and follow-up analysis are not included on the public page

Mission context

This is one of the strongest contemporary military records in the first coverage set because it includes aircraft context, sensor language, and a specific count range.

Incident summary

The mission report describes an F-16CM two-ship during Operation Inherent Resolve and records multiple bright objects that were briefly observed visually and through a targeting pod.

Confirmed mission-report facts

• The report is a six-page mission report approved for release to AARO.
• The mission involved a two-ship of F-16CM aircraft during Operation Inherent Resolve.
• The UAP section lists possible 10-20 objects sighted.
• The report says objects were briefly obtained on a targeting pod in TV mode before becoming dim and disappearing.

Document notes

• The report’s UAP value comes from the combination of pilot observation, targeting pod reference, and comparison to a star.
• The public record does not include the underlying targeting-pod footage.
• The reported count range, 10-20 possible objects, is a report field rather than a confirmed object count.

What the report records

The report records several bright objects maneuvering quickly and notes a comparison between targeting-pod observations of the possible UAP and a star.

Metadata worth resolving

• The core metadata to resolve includes platform, sensor mode, location, operation, incident date, and reported object behavior.
• The main follow-up question is whether associated imagery, radar, or additional AARO materials exist.

Why the count range matters

The phrase “10-20 possible UAP” makes DOW-UAP-D20 a high-interest Release 01 record, but it should be read as a report field rather than a confirmed inventory of separate objects. The count range tells readers the event was perceived as a group or cluster, while the word “possible” keeps the identity unresolved.

• The count range is analytically useful because it points away from a single-object interpretation.
• It also introduces uncertainty: range, angular separation, background reference points, and possible duplication by sensor or visual perception are not resolved in the public record.
• A stronger page later would compare the PDF against any releasable targeting-pod frames or mission logs if they appear in a later tranche.

Sensor chain and targeting-pod limits

D20 is stronger than a bare witness statement because it includes aircraft and targeting-pod context. It is still incomplete because the public article has the report but not the underlying sensor media. That distinction matters: a targeting-pod reference is valuable metadata, but without the actual footage, range, zoom, aircraft movement, and calibration context cannot be checked independently.

Conventional explanations to test first

A serious UAP analysis should test mundane explanations before making larger claims. For D20, the comparison set should include stars or planets near the horizon, flares, other aircraft, balloons, debris, sensor contrast artifacts, and formation effects. The released PDF keeps the case unresolved; it does not eliminate those possibilities by itself.

How public discussion should handle D20

D20 is less instantly viral than a dramatic video, but it is more useful for source-led research because it has mission context and a named record ID. Public discussion should focus on whether later Release 01 material connects D20 to raw media or companion files, not on treating the count range as proof of non-human technology.

• The exact record ID matters because it lets readers verify they are discussing the same PDF.
• The reader value is the explanation of why “10-20 possible UAP” is interesting but not conclusive.
• Community indexes are useful for finding related files, but claims should stay tied to the official PDF until additional source material is verified.

What the report does not identify

The report does not identify the objects, publish video evidence, or prove extraordinary origin.

Follow-up evidence

Is the targeting-pod footage releasable, and are there radar, Link 16, or additional mission records connected to this event?

Tags

Sources

• DOW-UAP-D20 mission report PDF - Six-page mission report describing a March/April 2023 possible UAP observation.
• Department of War PURSUE UFO portal - Primary official portal for PURSUE UAP releases.
• Reddit discussion: Release 01 archive indexing - Public discussion signal about Release 01 archive usability and file counts; not a primary source.