Skip to content
RichseenAtlas← AtlasSign in

MESSENGER

node

The first spacecraft to orbit Mercury, ending on its surface in 2015. Operated by NASA; launched 2004-08-03; completed. Encounter dates are the operator’s mission record; the encounter order is an order, not a trajectory, and Atlas draws no path for it.

A node is not a place. Drawing it on a map would assert something about the world that no stored fact supports.

Read in · 1

Evidence · 1
Timeline

No dated observations are stored for this object. Atlas shows what was observed and when — it does not infer a history.

Connections · 1
Assembled narrative · 1

Assembled from 23 blocks · 1 evidence · 12 related

  1. Story
  2. The first spacecraft to orbit Mercury, ending on its surface in 2015. Operated by NASA; launched 2004-08-03; completed. Encounter dates are the operator’s mission record; the encounter order is an order, not a trajectory, and Atlas draws no path for it.
  3. Knowledge
  4. Mercury
  5. MESSENGER
  6. Connections
  7. Mercury
  8. MESSENGER’s first Mercury pass — the first visit since 1975
  9. MESSENGER enters orbit around Mercury — the first craft to do so
  10. MESSENGER strikes Mercury at the end of its mission
  11. Mariner 10
  12. MESSENGER
  13. BepiColombo
  14. Mariner 10 passes Mercury — the first spacecraft to reach it
  15. Mariner 10’s third and final Mercury pass
  16. MESSENGER’s first Mercury pass — the first visit since 1975
  17. MESSENGER enters orbit around Mercury — the first craft to do so
  18. MESSENGER strikes Mercury at the end of its mission
  19. BepiColombo’s first Mercury flyby
  20. BepiColombo’s sixth and final Mercury flyby
  21. BepiColombo Mercury orbit insertion — declared target
  22. Evidence
  23. Launch, Mercury flybys, orbit insertion and the 2015 surface impact.
Close the narrative
Observed changes · 0

No public Signals are attached to this object. Signals show what changed and when it was observed — never a direction or a rank.

Actions

Read the assembled narrativeContinue in StudioOpen TwinTwin does not start a decision from this kind of object.ShareSaveSaved objects are part of the authenticated projection, which is declared and not yet built.

/atlas?object=MISSION_MESSENGER&experience=MISSION_MESSENGER