Princeton radar and the CAP point
Question tested
Do the reported ship radar tracks independently establish extraordinary altitude changes or continuity with the visual object?
Current read
Radar operators later described repeated unusual tracks and a contact at the flight . If accurate and correctly associated, these reports strongly deepen the case. The public record lacks raw tracks, calibration logs, quality indicators, synchronized timestamps, and a reproducible association among events.
Established Observations
- FACTUSS Princeton personnel later reported radar contacts that prompted aircraft tasking on November 14.
- UNKNOWNThe raw , Cooperative Engagement Capability, and airborne-radar records are not publicly available for independent analysis.
- DISPUTEDA tracked object descended from very high altitude to near sea level in less than a second.
- DISPUTEDThe later contact at the was the same object Fravor had seen.
Evidence Quality
Multiple retrospective operator accounts and official summaries support that radar anomalies were reported. Quantitative performance claims rely on remembered displays and later reconstruction, with some published altitude details in tension.
Accepted / Conventional Reading
- Track initiation, clutter, , software settings, and track association can create apparent motion that no single object performed.
- A series of unrelated conventional returns may have been grouped after controllers expected an unusual target.
- The CAP-point contact may reflect coincidence, information leakage, or a separate target rather than anticipation by the observed object.
Challenge / Alternative Reading
- Experienced personnel reported repeated tracks over several days, reducing the plausibility of one momentary display artifact.
- A radar contact corresponding with the visual tasking and later appearing near the would be difficult to dismiss if the original track data confirm continuity.
- Reported post-upgrade sensitivity and cross-platform observations could indicate a real low-observable target.
The quantitative gap
Claims ranging from roughly 28,000 feet to above 80,000 feet appear in later accounts. Without the display history and track file, cannot decide whether these describe the same returns, different systems, or narrative compression.
A radar symbol is a processed track, not a transparent photograph. Track quality, dwell, mode, filter settings, velocity confidence, and operator actions all matter before a kinematic claim can be calculated.
Recalibration and radar upgrade claims
Some witnesses describe contacts appearing around a radar-system upgrade or recalibration. That can support either a newly detectable target or a changed false-track environment. The missing calibration and maintenance records prevent discrimination.
Open Questions
- Do original radar files, screenshots, system logs, or synchronized tactical data still exist?
- What were track-quality values and altitude-source methods for the dramatic descent claim?
- Can the CAP-point track be associated with the visual object rather than merely sequenced after it?
PARALLAX Assessment
The radar narrative may be the most discriminating part of INV-005, but it is currently one of the least inspectable. It supports an unresolved multi-witness event, not a verified extreme trajectory.
Sources
- Eyewitness / testimonynimitz-fravor-statement
David Fravor Statement for the House Oversight Committee
Witness recordFirsthand or witness-adjacent material; important even when mediation and memory limits remain.- Provenance
- Written statement published by the congressional committee receiving the testimony.
- Directness
- Direct for what Fravor recalls seeing and doing.
- Method
- Retrospective witness statement under a congressional hearing record.
- Corroboration
- Core visual outline is independently supported by Alex Dietrich.
- Limit
- Nineteen-year-old recollection that also includes interpretation beyond direct observation.
- Verification
- Verified committee record.
Attributable account of the close visual encounter, reported CAP-point contact, later FLIR sortie, and handling of the incident.
- 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.
- Technical / scientific analysisnimitz-knuth
Estimating Flight Characteristics of Anomalous Unidentified Aerial Vehicles
Technical sourceScientific, engineering, forensic, or specialist analysis; weight follows method and reproducibility.- Provenance
- Open-access conference-proceedings paper.
- Directness
- Technical analysis of secondary case inputs, not raw Nimitz measurements.
- Method
- Kinematic models with stated input assumptions.
- Corroboration
- Equations are inspectable and overlap the SCU reconstruction.
- Limit
- Results inherit testimony, timing, track association, and assumed geometry; peer review does not validate those inputs.
- Verification
- Verified paper and DOI.
Formalizes conditional speed, acceleration, energy, and power estimates for several UAP cases, including Nimitz.
- Secondary analysisnimitz-fightersweep
There I Was: The X-Files Edition
Context sourceUseful synthesis or historical framing; claims should be traced back when possible.- Provenance
- Aviation publication relying substantially on sources then kept anonymous.
- Directness
- Early secondary narrative, not a primary operational record.
- Method
- Reported reconstruction from participant-adjacent interviews.
- Corroboration
- Many broad elements later appear in attributable accounts.
- Limit
- Key sources were anonymous and several details cannot be independently checked.
- Verification
- Verified publication; claims are not promoted solely because they appeared early.
An important pre-2017 public narrative of the encounter and its chronology.