(2006 CM10) is catalogued in this registry as an asteroid, held in the frame of Sol, from Potentially Hazardous Asteroids (JPL SBDB).
Registry id SBDB_50321651 ·
source layer sbdb ·
provenance PROCESSED — derived deterministically from source catalogues (unit, frame and epoch conversions, cross-source reconciliation) — no value invented
Open (2006 CM10) in the live scene → The scene composes a position for any date and is where a figure becomes a picture. It downloads the whole catalogue first: measured against the built product, an object outside the core resolves after about 16 s over a local network and about 147 s over a 4 Mbit link, having transferred roughly 70 MB. If you cannot wait that long, this page is the answer.
These are the sourced elements. This page does not print a position: a position is a function of time, and a single one dated to the bake would be stale the moment it was read. The registry composes a position for any date, past or future, from these elements — open the scene below and set the clock.
| Quantity | Value | Uncertainty | Source |
|---|---|---|---|
| Semi-major axis | 3.19092258203×10^11 m (2.133 au) | ± 1.07710466904×10^9 m (1077104.66904 km) (1σ) | Potentially Hazardous Asteroids (JPL SBDB) |
| Eccentricity | 0.701 | ± 0.0012 (1σ) | Potentially Hazardous Asteroids (JPL SBDB) |
| Inclination | 0.31957 rad (18.31°) | ± 0.0005410520681182421 rad (0.031°) (1σ) | Potentially Hazardous Asteroids (JPL SBDB) |
| Longitude of ascending node | 2.501406 rad (143.32°) | ± 7.155849933176751×10^−5 rad (0.0041°) (1σ) | Potentially Hazardous Asteroids (JPL SBDB) |
| Argument of periapsis | 1.607099 rad (92.07999°) | ± 5.759586531581287×10^−5 rad (0.0033°) (1σ) | Potentially Hazardous Asteroids (JPL SBDB) |
| Mean anomaly at epoch | 5.985607 rad (342.95°) | ± 0.0016755160819145565 rad (0.096°) (1σ) | Potentially Hazardous Asteroids (JPL SBDB) |
Elements are expressed in the frame of
SOL at epoch
2006-02-17 00:00:00 UTC (JD 2453783.5). Gravitational parameter of the primary:
1.3271244×10^20 m³/s². Semi-major axis in astronomical units uses the
IAU 2012 definition (1 au = 1.495978707×10^11 m exactly).
| Kind | asteroid |
|---|---|
| Origin | natural |
JPL orbit solution [Otto Matic]: 68 obs, 18 d arc 2006-02-07→2006-02-25, rms 0.54, MPC U=8 (9°–41°/decade) · on the NASA/JPL Sentry impact-risk list (snapshot 2026-07-28): cumulative impact probability 1.0e-6 (≈ 1 in 989,120) across 1 potential impact 2092-2092 · Palermo scale -4.26 cumulative / -4.26 max · Torino scale 0
Reproduced as the source wrote it. Author-year citations link to their DOI where one is registered.
These are absences in the catalogues aggregated here, not measurements of zero, and not statements that the quantity is unknown to science:
| Database | Potentially Hazardous Asteroids (JPL SBDB) |
|---|---|
| Authority | NASA/JPL Small-Body Database (SBDB) Query API |
| Address | https://ssd-api.jpl.nasa.gov/sbdb_query.api?fields=spkid,full_name,a,e,i,om,w,ma,epoch,diameter,H,albedo,sigma_a,sigma_e,sigma_i,sigma_om,sigma_w,sigma_ma,diameter_sigma,condition_code,rms,n_obs_used,n_del_obs_used,n_dop_obs_used,producer,data_arc,first_obs,last_obs,two_body,class&sb-group=pha |
| How it entered | RAW snapshot via scripts/ingest-sbdb.ts |
| Snapshot | 2026-07-29 |
| Coverage | 2547 PHAs incl. 99942 Apophis; heliocentric osculating elements at per-row epoch; radius only where SBDB measures a diameter (340). 2547 of 2547 carry their JPL orbit solution. Each object carries its JPL orbit solution: observations used, arc, residual rms, producer and the MPC uncertainty parameter U (0-9), whose in-orbit longitude runoff band is derived from the MPC's published definition. The MPC states that "the U value should not be used as a predictor for the uncertainty in the future motion of NEAs" — it classifies the SOLUTION, not the future. The published 6x6 covariance is deliberately NOT carried: it is stated at the solution epoch, a median 2,994 days from the epoch of the elements served here (measured over a 45-object sample), and transporting a correlated uncertainty across that gap needs JPL's own force model, which this registry does not have. |
This database remains the property of its owners and is reused under its own licence. If you quote a value from this page, name that database alongside SolarSystemRegistry.org.