Mission Atlas
← Mission directory

Mission record

MESSENGER

Also known as MErcury Surface, Space ENvironment, GEochemistry, and Ranging, Mercury Surface, Space Environment, Geochemistry and Ranging

NASA, Johns Hopkins University Applied Physics Laboratory · Launched

Explore trajectory

Completed · Success

NASA Discovery-class orbiter, built and operated by the Johns Hopkins University Applied Physics Laboratory, that became the first spacecraft to orbit Mercury. After one Earth, two Venus and three Mercury gravity-assist flybys it entered Mercury orbit on 18 March 2011 UTC, characterised the planet's surface composition, geological history, magnetic field and exosphere, verified water ice in permanently shadowed polar craters, and ended by impacting Mercury on 30 April 2015 after exhausting its propellant.

Destinations
Launch vehicle
Delta II 7925H
Launch site
Cape Canaveral, Florida (SLC-17B)
Countries
United States
Mission types
Orbiter, Flyby

Chronology

Mission timeline

  1. Launch

    Launch on a Delta II 7925H from Cape Canaveral

    Launched on a Delta 7925H (a Delta II Heavy with nine strap-on solid-rocket boosters); the spacecraft was injected into solar orbit 57 minutes later. Recorded at minute precision because sources disagree on the second (06:15:56 vs 06:15:57 UT).

    Earth
  2. Gravity assist

    Earth gravity-assist flyby

    One year after launch MESSENGER flew by Earth at an altitude of 2,347 km; the flyby was also used to calibrate the spacecraft's instruments.

    Earth
  3. Gravity assist

    First Venus gravity-assist flyby

    Flyby at an altitude of 2,990 km, set up by a 524-second thruster burn on 12 December 2005 that changed the spacecraft velocity by 316 m/s.

    Venus
  4. Gravity assist

    Second Venus gravity-assist flyby

    Flyby at an altitude of approximately 338 km, during which MESSENGER returned visible and near-infrared imaging of the upper atmosphere and particles-and-fields data.

    Venus
  5. Flyby

    First Mercury flyby

    First of three Mercury flybys, all at roughly 200 km altitude; returned the first images of the side of Mercury not seen by Mariner 10.

    Mercury
  6. Flyby

    Second Mercury flyby

    Second Mercury gravity-assist flyby at roughly 200 km altitude.

    Mercury
  7. Flyby

    Third Mercury flyby

    Third Mercury flyby at a distance of 228 km. The spacecraft entered safe mode during the encounter, which truncated the planned science observations but did not eliminate the flyby's science return.

    Mercury
  8. Orbit insertion

    Mercury orbit insertion

    First spacecraft to orbit Mercury. A 15-minute burn beginning at 00:45 UT on 18 March 2011 (8:45 p.m. EDT on 17 March) supplied a delta-V of 0.862 km/s, placing MESSENGER in the orbit NSSDCA publishes: a periapsis of 200 km at 60 degrees N latitude, an apoapsis of 15,193 km, a period of 12 hours and an inclination of 80 degrees.

    Mercury
  9. Milestone

    Orbital science observations begin

    Science observations from Mercury orbit began on 4 April 2011.

    Mercury
  10. Milestone

    Primary one-year orbital mission completed

    MESSENGER completed its primary yearlong mission on 17 March 2012, having taken nearly 100,000 images of Mercury's surface; the mission was subsequently extended twice.

    Mercury
  11. Impact

    Planned impact on Mercury's surface

    After exhausting its propellant, MESSENGER impacted Mercury as planned at 19:26 UT (3:26 p.m. EDT) at about 8,750 mph (14,080 km/h), creating a new crater. NASA gives approximate impact coordinates near 54.4 degrees north, 149.9 degrees west, near Janacek crater in Suisei Planitia. The impact occurred on the side of the planet facing away from Earth and was not directly observed.

    Mercury
  12. Mission end

    End of operations confirmed

    Mission control confirmed end of operations a few minutes after impact, at 3:40 p.m. EDT, when no signal was detected by the Deep Space Network station at Goldstone at the time the spacecraft would have emerged from behind the planet. The mission ended after more than four years and 4,105 orbits of Mercury.

    Mercury

Mission architecture

Vehicles

Trajectory record

Precise trajectory

Sun-centred J2000 states sampled offline from NASA/JPL NAIF SPICE kernels with geometric (NONE) aberration correction, using the official full-mission merged reference trajectory msgr_040803_091031_120401.bsp (JHU APL, produced 2010-01-21) with DE440s furnished last so planetary positions match the committed body ephemerides. This single merged SPK is what the modern archive ships in place of Voyager's per-encounter kernels, so all six gravity-assist flybys - one Earth, two Venus, three Mercury - are searched against it with no dedicated encounter kernel; each declares its own sampleWindowSeconds instead. The kernel's own embedded PDS label and SPKMERGE log (read via SPICE's DAF comment area) show it merges the mission's segment-by-segment navigation reconstructions, recon001 through recon006a, with each of the six flybys landing inside one of them; the file's own name records the merge's coverage as running from launch (2004-08-03) through 2009-10-31 in this delivery, and coverage stops there rather than continuing through the 2011 orbit insertion or 2015 impact this record's events describe: the file's remaining span to 2012-04-01 is orbit-determination prediction layered on top of the reconstructed tour, and extending the record into the multi-year orbital mission is a data change of its own, left uncommitted here, mirroring how Task A7 (New Horizons) committed only the Pluto encounter phase. Computed closest-approach distances agree with APL's own published centre-relative figures (Flyby Information page) to within 0.041 km at every encounter - Earth -0.005 km, Venus 1 -0.019 km, Venus 2 +0.019 km, Mercury 1 +0.006 km, Mercury 2 +0.041 km, Mercury 3 -0.003 km - and the recorded barycentre-to-centre offset is exactly 0.000 km at all six: Mercury and Venus have no moons, so their NAIF barycentre and body-centre coincide, and Earth's committed ephemeris targets the body centre (NAIF 399) rather than the Earth-Moon barycentre (NAIF 3), so this encounter's barycenterNaifId is 399 to match it. The Earth-Moon barycentre does genuinely sit some 4,336-4,942 km from Earth's centre, but because this encounter is measured against the same point the committed Earth ephemeris uses, that offset never enters the check - so the wide allowance lib/trajectory/validate.ts once carried for Earth was removed rather than corrected, and the tight 400 km default applies here instead. Four of the merged segments - the ones covering the second Venus flyby and all three Mercury flybys - carry a caveat in their own comments, and it is stronger than a footnote: each embeds a planetary ephemeris re-fitted locally from the navigation tracking data (named NAVPE001, NAVPE004, NAVPE005 and NAVPE006) and warns explicitly against pairing that segment with DE405, the ephemeris it was fitted from. Each also publishes a table of how far its own fit moved the planets; the largest of the eight figures those four tables give is 6.551 km, for Earth's position at the second Venus flyby, and every one of them is the length of a three-axis difference vector whose components are committed in this record's cited kernel excerpt. This dataset furnishes DE440s regardless, matching the body positions the rest of the catalogue draws - and that substitution was tested rather than assumed harmless. Re-running with DE440s left out entirely, so that each segment answers from its own embedded planets, reproduces the committed closest-approach distance exactly, to 0.000000 km, at all four: two of them carry a direct spacecraft-to-Mercury arc that needs no planetary ephemeris to complete, and the other two resolve through a barycentre sitting exactly where the planet does, since neither Venus nor Mercury has a moon. What the difference tables bound is where a flyby is drawn against the Sun, by at most that 6.551 km; they do not move the closest-approach distances above.

Provenance

Sources

Each source is listed once and labeled with the mission, event, trajectory, or destination/body context it supports.

Data verified through August 31, 2026