EVENT REPORT 001

Optical Track & Interceptor Handoff Test

October 4, 2026 · Tower A · UFODAP

Optical track recordedInterceptor acquisition unsuccessfulProbable aircraft

Tower A recorded a moving optical target and Mission Control displayed a subsequent DAU4/Interceptor pointing solution. The Interceptor did not record the target in either its wide or narrow video channels. The event therefore demonstrates detection and software-side handoff behavior, but not successful physical acquisition.

DetectionConfirmed optical track
HandoffMC/DAU4 cue supported
InterceptionNot achieved
IdentificationProbable aircraft; provisional

OBSERVATION

A target was recorded and tracked

The supplied camera recordings contain a moving bright/white optical feature. This distinguishes Event 001 from the earlier baseline dataset: an observational target is present in the recorded evidence.

Mission Control's map recording subsequently displays DAU4, the Interceptor, with a pointing solution in the target area. This supports the conclusion that Mission Control generated and/or relayed a handoff cue to the Interceptor.

Important distinction: a displayed DAU4 pointing solution establishes software-side pointing behavior; it does not by itself prove that the physical camera acquired the target.

HANDOFF RESULT

The cue occurred; the interception did not.

Scout / optical detectionSupported by the recorded camera imagery.
Mission Control processingSupported by the recorded map behavior.
DAU4 / Interceptor cueStrongly supported by the DAU4 azimuth/elevation display and pointing indication after detection.
Physical Interceptor acquisitionNot established. The Interceptor's own configured wide and narrow recordings contained no target track.
Overall test resultDetection and software-side handoff behavior observed; narrow-field interception unsuccessful.
Engineering implication: the failed acquisition is consistent with a pointing/calibration error large enough for a narrow-field camera to miss the target even when the commanded direction is generally correct. PT offsets, camera/mount alignment, coordinate transformation, and other pointing-calibration factors remain candidates for testing; this dataset does not determine which is responsible.

IDENTIFICATION

A strong aircraft candidate, not a closed identification

The aircraft telemetry recorded with this event contains a plausible conventional aircraft candidate, AAL986. The available record makes an aircraft explanation a strong working hypothesis.

However, temporal proximity alone is not sufficient to close the identification. A defensible identification requires correlation of the optical track with the aircraft's position, direction and timing. Until that comparison is completed, the event is classified as probable aircraft / identification provisional.

SYSTEM CONTEXT

Configuration relevant to the test

Mission Control sensorsFour OTDAU channels, MSDAU multi-sensor channel and RF display channel.
Trigger sourcesDAU1 through DAU4 configured as trigger sources; MSDAU and RF display not configured as trigger sources.
Mission recordingMission Control data, RF spectrum, weather and aircraft recording enabled.
Interceptor recordingSeparately configured at the OTDAU to record wide and narrow video on detection; no target track was recorded during this test.

ANALYSIS

What the evidence supports

The most defensible reconstruction is: a Scout camera recorded a moving optical target; Mission Control processed the observation; DAU4/Interceptor was presented with a pointing solution; and the Interceptor failed to record the target.

The failure does not establish why acquisition was missed. A pointing offset is a reasonable engineering hypothesis because the Interceptor has a much narrower field of view, but the present evidence does not distinguish among PT-offset error, alignment error, coordinate-transform error, timing error, or another cause.

A separate timing issue also remains relevant to future correlation work: camera and Mission Control timestamps have shown an approximately one-hour discrepancy in portions of the recorded material. Clock/DST synchronization should therefore be verified before relying on cross-device timestamps for precise event matching.

NEXT TEST

Turn the failed interception into calibration data

The next controlled test should preserve the same detection/handoff workflow while independently verifying the Interceptor's physical pointing. Known targets or deliberately generated tracks can be used to compare the commanded azimuth/elevation with the center of the Interceptor image. Any repeatable angular error can then be measured before changing PT offsets.

The objective is not to assume that PT offsets are wrong, but to determine whether a repeatable pointing error exists, measure its direction and magnitude, and then correct the appropriate part of the system.

CONCLUSION

Detection successful; interception unsuccessful

Event 001 records the first publishable UFO → IFO test in which an optical target was tracked and Mission Control showed evidence of an Interceptor handoff/cue. The Interceptor did not record the target, so successful acquisition cannot be claimed.

The available aircraft telemetry provides a strong conventional identification candidate, but the optical-to-aircraft correlation has not yet been completed. The identification therefore remains provisional.

Current classification: Probable aircraft. Handoff/cue supported. Interceptor acquisition failed. Pointing calibration requires further testing.

EVIDENCE STANDARD

Preserve first.
Interpret second.
Conclude last.

Don't manufacture detail the instruments didn't capture. Don't manufacture facts the evidence didn't establish.