Record provenance and missing data
Question tested
What public materials are original, derivative, retrospective, missing, or unverified?
Current read
The official FLIR1 derivative is authentic, while the ship and airborne radar records are absent and witness accounts are mostly retrospective. Conflicting removal and erasure claims remain unresolved. A leaked contractor report is useful for leads but unauthenticated.
Established Observations
- FACTFLIR1 existed publicly before its official release, and DoD later authenticated and released a derivative.
- FACTThe public case record lacks raw radar tracks, complete cockpit telemetry, and full contemporaneous debriefs.
- DISPUTEDUnknown personnel removed or erased all key data immediately after the encounter.
- UNVERIFIED CLAIMThe leaked BAASS report is a complete and authentic contractor record of the event.
Evidence Quality
Administrative records establish the later video release. FOIA files and technical reports illuminate provenance but do not produce the decisive radar or telemetry. The evidentiary bottleneck is access, not a lack of narratives.
Accepted / Conventional Reading
- Routine overwrite, retention schedules, classification, and fragmented custody can explain missing records without a coordinated suppression effort.
- The video leak and later official release show confused handling rather than a clean, secret evidentiary archive.
- Retrospective interview projects can unintentionally standardize language and chronology across witnesses.
Challenge / Alternative Reading
- Rapid data collection by unidentified personnel, if documented, would suggest institutional interest and possibly withheld evidence.
- Missing radar and electronic-warfare data may conceal stronger corroboration than the public clip provides.
- Official ambiguity after authentication can appear inconsistent with the seriousness witnesses attach to the event.
Chain of custody
The official 2020 release settles authenticity of the public Navy video, not whether the file is native or analytically complete. Earlier leaked versions and later transcodes should be treated as derivatives of a source recording whose full are unavailable.
Claims about personnel taking data conflict with Fravor's own account that tapes were not taken and that the event received little formal investigation. Different ships and record types may partly reconcile the accounts, but no public removal log resolves them.
The leaked contractor report
The BAASS document helps trace how later calculations and narrative details developed. Because DIA has not authenticated the public file as a complete official record, uses it as an unverified lead, not proof.
Open Questions
- Which original files were retained, overwritten, transferred, or classified, and under what record schedules?
- Can the complete native file be released without exposing sensitive system capabilities?
- Is there documentary support for removal or erasure claims beyond retrospective testimony?
PARALLAX Assessment
The case cannot be closed confidently in either direction from the public archive. Provenance is sufficient to authenticate FLIR1 but insufficient to reproduce the radar and performance narrative.
Sources
- Official recordnimitz-dod-videos
Statement by the Department of Defense on the Release of Historical Navy Videos
Official recordInstitutional record; weight depends on evidence, method, provenance, corroboration, and limits.- Provenance
- Official DoD release statement.
- Directness
- Direct for authenticity and release status; indirect for the event itself.
- Method
- Administrative review and public release.
- Corroboration
- Consistent with the NAVAIR release file and classification-review emails.
- Limit
- Does not establish the target identity, performance, or origin.
- Verification
- Verified official page.
Authenticates one November 2004 Navy video and records that the depicted phenomenon remained unidentified.
- Primary evidencenimitz-flir1
FLIR1 official UAP footage from the USG for public release
Primary evidenceDirect material, dataset, exhibit, transcript, or record; directness does not remove context checks.- Provenance
- Officially released derivative; local site copy is a public-domain Wikimedia transcode of that file.
- Directness
- Direct visual-sensor record of the later target track.
- Method
- ATFLIR infrared recording displayed with aircraft and sensor symbology.
- Corroboration
- Authenticated by DoD and documented in Navy review correspondence.
- Limit
- Compressed derivative without complete native metadata, a reliable target range, or the full sortie context.
- Verification
- Verified official file and public-domain derivative.
The inspectable public FLIR1 video, recorded during a later sortie on November 14, 2004.
- Archival materialnimitz-classification-emails
2020-006828 email - AFOSI / Navy cockpit videos review
Archival recordHistorical or FOIA/source-file material; relevance depends on provenance, completeness, and context.- Provenance
- Official FOIA release.
- Directness
- Direct for later administrative provenance only.
- Method
- Classification and public-release correspondence.
- Corroboration
- Consistent with the 2020 DoD release statement.
- Limit
- Does not analyze the target or reconstruct the encounter.
- Verification
- Verified official PDF.
Administrative correspondence documenting institutional review and release handling for FLIR1 and other cockpit videos.
- Independent technical analysisnimitz-scu-report
A Forensic Analysis of Navy Carrier Strike Group Eleven's Encounter with an Anomalous Aerial Vehicle
Independent critiqueTechnical analysis outside the principal institution; judged by methods and source trail, not outsider status.- Provenance
- Public report by an independent organization focused on anomalous-aircraft research.
- Directness
- Secondary reconstruction drawing heavily on attributable and anonymous retrospective testimony.
- Method
- Interview synthesis, document collection, geometry, and performance estimates.
- Corroboration
- Collects accounts across ships and aircraft and exposes assumptions in its calculations.
- Limit
- No raw radar data; important calculations depend on recalled timing, range, and geometry. The organization has an anomaly-investigation mission.
- Verification
- Verified report copy; claims assessed individually.
Extensive witness interviews, FOIA appendices, chronology, and conditional performance modeling.
- Independent technical analysisnimitz-video-provenance
Original FLIR1, GIMBAL, and GOFAST video files
Independent critiqueTechnical analysis outside the principal institution; judged by methods and source trail, not outsider status.- Provenance
- Open technical forum with preserved file comparisons.
- Directness
- Direct comparison of public derivatives; not a Navy chain-of-custody record.
- Method
- File, frame, and metadata comparison.
- Corroboration
- Official NAVAIR and DoD links allow independent checking.
- Limit
- Forum publication and incomplete access to the native recording.
- Verification
- Verified thread and linked official files.
Compares leaked and official video derivatives and records direct official file links.
- Unverified materialnimitz-baass
Summary Report on BAASS UAP Analysis Capabilities: Tic Tac and Sphere Assessments
Needs verificationLogged for traceability but not treated as established.- Provenance
- Publicly leaked in 2025; hosted by The Black Vault.
- Directness
- Purported contractor analysis, not an authenticated government release.
- Method
- Witness interviews, performance modeling, and capabilities assessment.
- Corroboration
- Parts overlap later public accounts and the SCU report.
- Limit
- Public file provenance, authorship chain, and completeness have not been authenticated by DIA.
- Verification
- Logged as unverified and not used as evidentiary backbone.
Lead source for contractor-era modeling, witness material, and development of the later case narrative.
- Archival materialnimitz-air-plan
Nimitz CSG Daily Air Plan and Flight Schedule 11.14.2004
Archival recordHistorical or FOIA/source-file material; relevance depends on provenance, completeness, and context.- Provenance
- Public FOIA request and correspondence record.
- Directness
- Direct for the records request, not for the encounter.
- Method
- FOIA request tracking.
- Corroboration
- Illustrates continuing gaps in the public operational record.
- Limit
- A request is not evidence that responsive records exist or support any interpretation.
- Verification
- Verified request page.
Documents targeted attempts to locate contemporaneous flight and operational records.