---
analysis-role: source-backed-analysis
confidence-level: medium
ai-analysis: true
accuracy-disclaimer: AI-assisted analysis; interpretations are provisional and may contain errors. Verify against cited source material.
ai-generated: true
companion-eligible: true
---

# DOD 111688723 Missile Explanation Assessment

## Source Basis

- Primary source video: [DOD 111688723 video](/?open=Release_1%2FDOD_111688723.mp4)
- Local source path: [DOD 111688723 video](/?open=Release_1%2FDOD_111688723.mp4)
- Captured frame: [local 2.710s, normal, 2.64x](/?open=Release_1%2FDOD_111688723.mp4&t=2.710&preset=normal&zoom=2.6444444444444444&panX=-672.0777777777778&panY=-1196.2&contrast=1.15&brightness=1)
- Captured image: ![Filtered capture from DOD_111688723.mp4](/media/Release_1/Analysis/images/dod-111688723-20260529t020819z-capture-lead.png)

## Observation

The captured frame shows a dark elongated body or streak moving across a bright, textured thermal background. A long, narrow, high-contrast trail extends behind or along the object line. The object/trail geometry is directional and plume-like rather than a compact self-contained orb, disc, or field envelope. The surrounding terrain/cloud texture is noisy and compressed, but the main visible feature is still a conventional-looking linear projectile/plume signature.

## Hypothesis To Test

The request asks whether this is misleading and whether the obvious explanation is a missile. On this captured frame, the missile or munition interpretation is the stronger working explanation. The source-observable clues are the elongated dark body, straight trail, and directional plume geometry. Those features are more consistent with a projectile, missile, rocket, or munition in thermal imagery than with a field-obscured craft.

## Speculative Synthesis

Under the field-prototype model, a genuine field body would more likely preserve a compact boundary, a coherent rim, or a sensor-visible envelope that stays attached to the object. This capture instead reads as a linear event: body plus trail. If there is anomalous behavior elsewhere in the clip, it would need to come from adjacent-frame motion, acceleration, or target context rather than from this single frame's morphology.

## Why It Matters

This is a useful negative control. The archive needs explainable cases alongside unresolved cases, because missile/plume imagery can mimic UAP language when viewed without context. Marking this as likely conventional helps protect the analysis set from promoting every high-contrast target into the field-propulsion lane.

## Working Assessment

Assessment: likely conventional missile/munition or projectile signature from this captured state. UAP promotion is not supported by this frame alone.

The possibility of intent is also relevant: a UAP archive that contains obvious conventional signatures may reflect broad responsive collection, classification uncertainty at intake, or public-release ambiguity rather than proof that every clip was anomalous. Treat this as misleading or explainable unless neighboring frames show a performance feature inconsistent with missile behavior.

## Follow-Up Amendment - Adjacent Frame Retest

Follow-up retest: reopened [DOD 111688723 video](/?open=Release_1%2FDOD_111688723.mp4) at the captured state, sampled five source frames around the original [2.710s](/?open=Release_1%2FDOD_111688723.mp4&t=2.71) capture, and kept the viewer controls at normal preset, view zoom 2.65x, contrast 1.15, and brightness 1. The sampled times were [2.310s](/?open=Release_1%2FDOD_111688723.mp4&t=2.31), [2.510s](/?open=Release_1%2FDOD_111688723.mp4&t=2.51), [2.710s](/?open=Release_1%2FDOD_111688723.mp4&t=2.71), [2.910s](/?open=Release_1%2FDOD_111688723.mp4&t=2.91), and [3.110s](/?open=Release_1%2FDOD_111688723.mp4&t=3.11). See the adjacent-frame contact sheet: ![Adjacent-frame retest for DOD_111688723.mp4](/media/Release_1/Analysis/images/dod-111688723-adjacent-frame-follow-up-contact-sheet.png)

Observed source facts: the dark feature is absent from the central scene at [2.310s](/?open=Release_1%2FDOD_111688723.mp4&t=2.31), appears as a short horizontal streak near the left edge by [2.510s](/?open=Release_1%2FDOD_111688723.mp4&t=2.51), crosses the lower central field as a tapered dark linear body at [2.710s](/?open=Release_1%2FDOD_111688723.mp4&t=2.71), moves to the lower right edge by [2.910s](/?open=Release_1%2FDOD_111688723.mp4&t=2.91), and is gone by [3.110s](/?open=Release_1%2FDOD_111688723.mp4&t=3.11). The visible signature remains narrow, directional, and plume-like across the sampled interval rather than resolving into a compact body, rim, orb, disc, or field envelope. The original captured frame remains available here: [local 2.710s, normal, 2.64x](/?open=Release_1%2FDOD_111688723.mp4&t=2.710&preset=normal&zoom=2.6444444444444444&panX=-672.0777777777778&panY=-1196.2&contrast=1.15&brightness=1).

Inference: the adjacent-frame motion strengthens the missile, munition, projectile, or fast linear debris explanation. The feature behaves like a transient object crossing the sensor field with a stable horizontal direction; it does not show a stop, reversal, hover, abrupt right-angle displacement, or trail loss that would reopen the case as anomalous from this short interval.

Speculative synthesis: under a field-envelope model, this would be a weak candidate because the sampled frames do not preserve a coherent boundary around a body. The best disclosure-forward use of this clip is as a negative control: it helps separate obvious linear projectile/plume signatures from cases where the sensor record shows compact morphology or non-ballistic behavior.

## Follow-Up

- Adjacent frames before and after 2.710s were sampled during the follow-up retest above.
- If a wider pass finds acceleration, stopping, reversal, or abrupt trail loss outside the [2.310s](/?open=Release_1%2FDOD_111688723.mp4&t=2.31)-[3.110s](/?open=Release_1%2FDOD_111688723.mp4&t=3.11) sample, reopen the case.
- Otherwise keep the case conventional likely / misleading.
