Skip to main content
When Timeline is available in your Operations sidebar, it brings the separate Passes, AOI and Burn Plan timelines into one view. Each spacecraft is a collapsible group with a shared UTC time axis. Stations and AOIs identify events within those groups. Choose Spacecraft, a 24-hour, 3-day or 7-day window, and the event Layers you want to see. Use the arrow buttons to move through time, Now to start the window at the current instant, and Compact / Wide to change detail. The URL preserves spacecraft, layers and explicit time selections for reopening. Available layers are contacts, AOI opportunities, burns, eclipses, SAA crossings, apsis and nodes. Opening Timeline from Passes, AOIs or Burn Plan selects the corresponding layers. Those areas keep their original timeline when the combined view is unavailable.

​
Read and inspect events

  • Contacts: dashed bars are computed candidates; solid bars are saved bookings. Select a candidate to inspect its timing and geometry, then Book contact when the required geometry is available. Saved bookings replace the matching candidate.
  • AOI opportunities: marks locate entry instants. Select one for its area, spacecraft, entry, exit and payload; Open AOI returns to the area workflow.
  • Burns: select a burn for its status, epoch, duration and delta-V, or Open burn to review it in Burn Plan. An unavailable duration is stated explicitly.
  • Orbital events: inspect bands or instant markers for the measurements recorded by the event source.
Overlapping events occupy separate tracks inside their spacecraft’s layer. Export opens the existing schedule exporter for the selected time window; its supported event categories are unchanged.

​
Coverage and unavailable results

A layer’s warning button opens its source notices. These distinguish stale contact results, missing station coverage, AOI computation failures, unavailable orbital data and time outside computed coverage. Shaded intervals indicate coverage gaps in the named source; another source may still have results there. No events in this window means the loaded layer has no events and no reported availability problem. A loading or failure notice is a different state. Failed contact refreshes keep the previous result visible and label it accordingly. Refresh retries the selected sources; it does not start an AOI recomputation or produce new stored pass evidence. Orbit-age restrictions still apply to computed contacts. Show stored result acknowledges an eligible stale-orbit restriction; saved bookings remain readable.