BASELINE REPORT 001

Tower A System Recording

October 4, 2026 · UFO → IFO / UFODAP

Baseline datasetNo observational event identified

This report establishes a baseline for how UFO → IFO will document system recordings and future aerial observations. The supplied dataset is not being presented as a UFO event. Its purpose is to preserve the configuration and available sensor records and to demonstrate the evidence structure that will be used when an actual event is captured.

StationTower A
Report typeBaseline / System Recording
Primary systemUFODAP Mission Control
Final statusNo target established

OBSERVATION

What this dataset establishes

The recording package documents the operating configuration of Tower A and associated Mission Control data channels. Based on the supplied files, the dataset does not establish the observation of an unidentified aerial target. It is therefore classified as a baseline system record rather than an event report.

Evidence standard: No identification is assigned when no observational target has first been established by the available evidence.

INSTRUMENTATION

Recorded system configuration

Mission Control was configured with four OTDAU camera sensors, an MSDAU multi-sensor unit and an RF display channel. Cameras 1–4 were configured as trigger sources. The MSDAU and RF display were present as additional sensor channels.

OTDAU cameras4 tracking sensors, configured for 30 fps
MSDAUMulti-sensor DAU, 30 fps configuration
RF configuration1600–1614 MHz range recorded in the supplied MSDAU configuration
Mission recordingData, RF spectrum, weather and aircraft recording enabled
Trigger configurationOTDAU cameras 1–4 enabled as trigger sources; MSDAU and RF display not configured as trigger sources

ENVIRONMENTAL CONDITIONS

Weather record

The supplied weather record provides environmental context for the recording period. The recorded conditions were clear sky with 0% cloud cover, temperature 53.49°F, relative humidity 87%, wind 5.75 mph from 280°, barometric pressure 30.09 inHg and reported visibility of 10 km.

Environmental information is preserved as observation context. It does not, by itself, establish or identify an aerial target.

RECORDED EVIDENCE

Files supplied for this baseline

Mission configurationSensor assignments, trigger settings and enabled recording channels.
OTDAU configurationsFour tracking-sensor configuration records for Tower A.
MSDAU configurationMulti-sensor configuration including RF range and station parameters.
Mission Control dataRecorded MC data associated with the baseline session.
RF spectrum dataRFSA recording associated with the session.
Weather dataEnvironmental conditions recorded for the session.

ANALYSIS

What can—and cannot—be concluded

The supplied package is useful for documenting system state and establishing the reporting framework. It is not sufficient to establish that an anomalous or unidentified aerial object was observed. Accordingly, no attempt is made to identify a target that the dataset has not first established.

For future event reports, this same structure can be expanded with camera video, map and track information, timestamps, aircraft correlation, RF information, still images and other relevant sensor evidence. Competing explanations can then be compared according to the evidence available for that specific event.

LIMITATIONS

Limits of this baseline report

This report is based only on the files supplied for the October 4 baseline package. No claim is made here about evidence that is not contained in that package. The absence of an established target in this report should not be interpreted as evidence that no aerial activity occurred; it means only that this dataset does not establish a target suitable for identification.

CONCLUSION

No observational event identified

This recording is published as a baseline system dataset rather than an anomalous aerial event. The supplied files do not establish the observation of an unidentified aerial object.

Its value is as a reference dataset demonstrating the configuration, environmental information and sensor records available from the UFO → IFO system. Future event reports will use this same evidence structure when an actual observation occurs.

No identification is assigned because no observational target has been established by this dataset.

UFO → IFO 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.