FIELD INTEL — OCTOBER 25, 2026

A 141-page BAASS report released in the October 23 PURSUE tranche opens a useful window into how contractors tried to quantify the 2004 Nimitz encounter. The November 23, 2010 document contains analytical calculations and computer modeling. Its most consequential qualification appears before the speed tables: the authors say they had little hard data and relied on parameter studies or assumptions drawn from witness testimony.

The timing was an input

On PDF page 33, numbered page 32, the report describes a reported descent from about 60,000 feet to sea level. Because the duration was not known precisely, the analysis explored intervals from 0.5 to 10 seconds. Those alternatives were inputs to a calculation, rather than independently timed measurements of the encounter.

The report also compares fluid-flow models for simplified shapes and includes technical plots and input files. That documents analytical work. It does not turn an assumed flight path into a calibrated sensor track, nor establish the material or propulsion system of the reported object.

A separate witness record matters

In his 2023 congressional statement, retired Navy Commander David Fravor described the November 2004 visual encounter and the object's departure. He also recounted being told that it had appeared at the patrol's rendezvous point. This is important firsthand testimony about what he saw, combined with information relayed to him; it is not the missing raw radar series needed to audit every numerical performance claim.

Space journalist Leonard David's October 23 release coverage independently places BAASS technical material within the new document tranche. His coverage corroborates the publication context, not the numerical results. The released report and Fravor's later statement should therefore remain separate evidence layers.

How to read the numbers

Our editorial assessment is that the report is most valuable as an auditable account of assumptions. A reader should ask which inputs came from instruments, which came from recollection, how uncertainty was propagated, and whether different plausible inputs change the conclusion. Large computed values cannot answer those questions on their own.

NASA's UAP study provides relevant independent context by emphasizing data collection and analysis methods. It does not certify this BAASS model. UFOsoldier reviewed the report's text and visually checked the critical page; we did not rerun the simulations or independently reconstruct the encounter. The October 2026 development is access to the historical analysis, not a newly measured flight.

Hero: original AI-generated editorial illustration of an engineering office; not a photograph of BAASS facilities or UAP evidence.