NEO CLOSE APPROACH OBSERVATORY - JPL CAD + SCOUT
DUAL WATCH JPL SBDB CAD API / CNEOS SCOUT API
ASTROPHYZIX NEO PHA DUAL-WATCH
ASTEROID TRACKING & SCOUT SYSTEM V8.0
[LIVE] On-Demand NEO / PHA Monitoring Console.
Confirmed close approaches are pulled from the NASA JPL SBDB Close-Approach Data (CAD) API. Unconfirmed objects on the Minor Planet Center NEO Confirmation Page are pulled from the NASA CNEOS Scout API. The monitoring window is generated dynamically at the moment of data retrieval. Each page load produces a fresh window from current source data. Manual data sync is available. JPL SSD endpoints do not permit direct browser embedding, so requests are relayed through a deterministic public CORS-proxy fallback chain (allorigins, thingproxy, corsproxy). The relay used for each sync is recorded in the provenance line below. If manual sync fails reload the page in a new tab.
Alternatively, you can use our backup NeoWs API powered system by clicking here
Astrophyzix NEO / PHA ARI V2 Integrated | Asteroid Monitoring Interface V8.0 | (c) Astrophyzix 2026
🌟 Launch the Live Orbital Viewer to monitor an asteroid’s orbit
ℹ️ NEED HELP UNDERSTANDING THIS PAGE? CHECK THE USER GUIDE HERE
Confirmed close approaches are pulled from the NASA JPL SBDB Close-Approach Data (CAD) API. Unconfirmed objects on the Minor Planet Center NEO Confirmation Page are pulled from the NASA CNEOS Scout API. The monitoring window is generated dynamically at the moment of data retrieval. Each page load produces a fresh window from current source data. Manual data sync is available. JPL SSD endpoints do not permit direct browser embedding, so requests are relayed through a deterministic public CORS-proxy fallback chain (allorigins, thingproxy, corsproxy). The relay used for each sync is recorded in the provenance line below. If manual sync fails reload the page in a new tab.
Alternatively, you can use our backup NeoWs API powered system by clicking here
Astrophyzix NEO / PHA ARI V2 Integrated | Asteroid Monitoring Interface V8.0 | (c) Astrophyzix 2026
🌟 Launch the Live Orbital Viewer to monitor an asteroid’s orbit
ℹ️ NEED HELP UNDERSTANDING THIS PAGE? CHECK THE USER GUIDE HERE
Awaiting first sync...
Auto-Sync: 10 min
Provenance: pending first sync.
[LIVE] Current Closest Approaching Object
Contacting NASA JPL...
--
[LIVE] Approach Radar - Lunar Distance Scale
Earth at centre | Rings = 10, 20, 30 LD | RED = PHA-class | BLUE = NEO | AMBER = Scout
Bearing is schematic (rank-ordered, not true sky position)
Bearing is schematic (rank-ordered, not true sky position)
Total Objects
--
PHA-class
--
Within 10 LD
--
Closest LD
--
Avg km/s
--
Largest
--
Window
Max approach
LD
Search
Units
The ARI is a non-official heuristic index developed by Astrophyzix for educational
visualisation only. It is not affiliated with, equivalent to, or a substitute for the
Palermo Scale or Torino Scale used by NASA and ESA for
formal impact probability assessment.
For full ARI documentation click HERE.
ARI v2 (R)(c) VXgCjiGFoHI9Gn1w Protected under international copyright.
For full ARI documentation click HERE.
ARI v2 (R)(c) VXgCjiGFoHI9Gn1w Protected under international copyright.
ARI Scoring Model (0 to 100 points) - preserved exactly from V6
Miss distance
Up to 40 pts
40 * e^(-0.1386 * missLD) - exponential decay, half-life = 5 LD
Relative velocity
Up to 20 pts
min(20, 10 * log10(speed km/s)) - logarithmic. v_rel (CAD) or v_inf fallback
Estimated diameter
Up to 20 pts
min(20, diameter_m * 0.05)
PHA-class designation
+18 pts bonus
if PHA-class true (see derivation below)
Parameter Provenance and Derivations
Sources. Confirmed close approaches: NASA JPL SBDB Close-Approach Data (CAD) API,
Time scale. CAD close-approach epochs (
Distance. CAD nominal approach distance
Diameter. When CAD returns a measured
PHA-class (derived). CAD does not return the official MPC PHA flag or the orbit MOID. A window-local PHA-class proxy is used: H <= 22.0 AND minimum approach in window <= 0.05 AU. This is a heuristic, not the official PHA designation, and can differ from the MPC list. Scout objects use the Scout phaScore (PHA-class true if phaScore >= 50).
Orbit class / period. The CAD and Scout summary endpoints do not return osculating elements, so orbit-class and orbital-period fields and the Apollo/Aten filters from V6 have been removed rather than fabricated. Source, confirmation status, close-approach time uncertainty (
Validation. On each load a benchmark sanity check confirms 1 LD parses to 384,400 km and Apophis-scale inputs (about 0.0003 AU, 7.4 km/s) yield ARI in the expected high band; failures are surfaced in the provenance line.
Engineering. Numeric columns are held in Float64Array structure-of-arrays state vectors. Parsed datasets are cached in IndexedDB (scientific store, 10 min TTL) with an in-memory fallback. The sync pipeline is a deterministic finite state machine (IDLE -> CACHE -> CAD -> SCOUT -> MERGE -> RENDER / ERROR). Heavier compute elements (N-body, symplectic/RK integrators, WebGPU/WASM SIMD, FLRW, particle-mesh) are intentionally not used: this console displays JPL's authoritative orbit solutions and does not integrate trajectories, so re-deriving them in-browser would reduce accuracy.
ARI scores are recalculated on each load and are not stored or published as impact predictions. ARI does not incorporate orbital covariance, observation-arc uncertainty, or n-body perturbation effects. Astrophyzix CNEO Observatory is a public-facing scientific division of Astrophyzix.org.
ssd-api.jpl.nasa.gov/cad.api. Unconfirmed NEOCP objects: NASA CNEOS Scout API,
ssd-api.jpl.nasa.gov/scout.api. JPL SSD policy prohibits direct website
embedding, so the two requests are relayed (serially, one at a time, per the SSD fair-use
policy) through a fallback chain: direct, allorigins/raw, allorigins/get, thingproxy,
corsproxy. The active relay, API versions, fetch time, and HTTP status are recorded in the
provenance line and exported with the CSV.Time scale. CAD close-approach epochs (
cd, jd) are reported
by JPL in TDB (Barycentric Dynamical Time). They are displayed as-is and labelled TDB. The
observatory clock is UTC. TDB - UTC is presently about 69.2 s; this offset is not applied to
approach epochs as it is far below CAD time resolution for monitoring use. SOFA-grade
time-scale conversion is not performed because this is a display console, not an
ephemeris-generation tool.Distance. CAD nominal approach distance
dist and the
dist_min/dist_max 3-sigma band are in AU and converted with
1 AU = 149,597,870.7 km, 1 LD = 384,400 km.Diameter. When CAD returns a measured
diameter (km) it is used directly
with diameter_sigma as the band; size source = JPL. Otherwise diameter is
estimated from absolute magnitude H using D(km) = 1329 / sqrt(pV) * 10^(-0.2 H), with
nominal albedo pV = 0.14 and a band from pV = 0.25 (bright/smaller) to pV = 0.05
(dark/larger); size source = H-derived. Scout objects always use the H-derived estimate.PHA-class (derived). CAD does not return the official MPC PHA flag or the orbit MOID. A window-local PHA-class proxy is used: H <= 22.0 AND minimum approach in window <= 0.05 AU. This is a heuristic, not the official PHA designation, and can differ from the MPC list. Scout objects use the Scout phaScore (PHA-class true if phaScore >= 50).
Orbit class / period. The CAD and Scout summary endpoints do not return osculating elements, so orbit-class and orbital-period fields and the Apollo/Aten filters from V6 have been removed rather than fabricated. Source, confirmation status, close-approach time uncertainty (
t_sigma_f), and the 3-sigma distance band are shown instead.Validation. On each load a benchmark sanity check confirms 1 LD parses to 384,400 km and Apophis-scale inputs (about 0.0003 AU, 7.4 km/s) yield ARI in the expected high band; failures are surfaced in the provenance line.
Engineering. Numeric columns are held in Float64Array structure-of-arrays state vectors. Parsed datasets are cached in IndexedDB (scientific store, 10 min TTL) with an in-memory fallback. The sync pipeline is a deterministic finite state machine (IDLE -> CACHE -> CAD -> SCOUT -> MERGE -> RENDER / ERROR). Heavier compute elements (N-body, symplectic/RK integrators, WebGPU/WASM SIMD, FLRW, particle-mesh) are intentionally not used: this console displays JPL's authoritative orbit solutions and does not integrate trajectories, so re-deriving them in-browser would reduce accuracy.
ARI scores are recalculated on each load and are not stored or published as impact predictions. ARI does not incorporate orbital covariance, observation-arc uncertainty, or n-body perturbation effects. Astrophyzix CNEO Observatory is a public-facing scientific division of Astrophyzix.org.
Contacting NASA JPL CAD + Scout...