CF26802

Altitude through the night

In the staralt style: the object's altitude (solid) and the Moon's altitude (dashed), across dusk to dawn. The shaded band is the window pipeline.py judged actually usable; the red dashed line is the 20° floor below which MPC's normal fetch never sends a row at all.

Any remaining "no data" span is a real hole, not a bug: it means neither MPC's normal ephemeris nor the wider, floor-free fetch scoped to this plot returned a position for that stretch. The Moon's own curve is computed independently (it needs no orbit fit, unlike the object) and so stays gap-free even across a hole in the object's curve. Clock times are CET, local to the observatory — hover any point on the object's curve for UT and its exact separation from the Moon.

History on NEOCP

Every value NEOCP has reported for this object since neocp_history.py started polling — 53 snapshots so far. MPC's own confirmation page keeps no such record; this is built by polling it on a schedule and keeping every reading rather than overwriting the last one.

Sky-plane uncertainty

Drawn from MPC's own variant-orbit offsets, at the same epoch as their plot. Each orbit is one solution consistent with the observations so far; the ring marks the nominal position, and the field box appears only when it is comparable in size to the cloud.

Dot size shows how many variants share a position. MPC publishes these offsets rounded to whole arcseconds, so a tightly constrained object has thousands of orbits landing on a handful of grid points — their own picture is drawn from unrounded values and looks smoother. Sizing by count puts that density back rather than stacking invisible dots. Hover any dot for its share.