Mission Extension Vehicle 2

Overview

A geostationary life-extension vehicle has to dock with a satellite that was never built to be docked with, using whatever interface the client happens to carry, and it has to do this in a belt crowded with active traffic and no ground crew able to walk out and inspect a failed approach. Industry’s own economic argument for building such a vehicle at all rests on the observation that GEO comsats fail well short of their design life far more often than operators like to admit, which is what makes a fleet of clients worth visiting rather than one bespoke rescue [1]. MEV-2 is the second Mission Extension Vehicle built to that argument. It shares its docking mechanism, rendezvous and proximity operations sensor suite, and client interface with MEV-1, and differs from it only in which satellite it was sent to and the orbital regime that satellite occupied.

Design space

The interface both vehicles use, a capture tool driven into the client’s liquid apogee engine nozzle inside its launch adapter ring, is not a Northrop Grumman invention: the same nozzle-and-ring geometry, present on roughly 80 percent of geostationary communications satellites because it is a leftover of how those satellites reached orbit rather than a docking feature, is the interface SMART-OLEV proposed for the same market more than a decade earlier [2]. What changed between that proposal and MEV’s flights was less the mechanism than the sensing built around it: MEV’s rendezvous suite combines narrow- and wide-field visible imagers, long-wave infrared imagers and a scanning lidar, three dissimilar phenomenologies feeding one relative-navigation solution rather than one [3]. NASA’s own parallel attempt at comparable capability, RESTORE-L turned OSAM-1, took the opposite architectural path, a government-run refueling and dexterous-servicing demonstrator built on a LEO-modified GEO bus, and was canceled in 2024 after eight years and roughly 1.4 billion dollars spent against an original 750 million dollar, 2020-launch estimate, never having flown [4]. A third answer, worked out at far smaller scale on the SPHERES free-flyer testbed, is a standardized mechanical docking port with a lance and capture cone plus an optical relative sensor, tested on parabolic flights to derive the sub-1-centimeter-per-second approach velocity a capture needs, but never flown as a full docking on orbit [5]. A tutorial survey of on-orbit servicing demonstrators places MEV alongside ETS-VII, Orbital Express and SMART-OLEV as the small set of flown precedents this design space actually has to draw on [6]. The rendezvous guidance and navigation software behind approaches like MEV’s has its own separate lineage in ground testing: DLR’s EPOS facility validated a delay-compensated closed-loop rendezvous filter down to 1.8 m of standoff years before any commercial GEO servicer flew, the kind of ground rehearsal that de-risks the final approach phase [7].

What changed, and what it enabled

MEV-1 docked to Intelsat 901, a satellite already retired to the graveyard orbit roughly 300 km above the geostationary belt [3], which meant the operation had no active neighbors to avoid. MEV-2 docked to Intelsat IS-10-02, a satellite still carrying revenue traffic in its assigned geostationary slot, which removed the option of clearing the surrounding airspace before the approach and made MEV-2 the first vehicle to dock with an operating satellite in an active GEO slot [8]. Once docked, MEV-2 assumed the client’s station-keeping and pointing, letting Intelsat disable the satellite’s own propulsion and attitude control for the service period [9]. The same rendezvous camera suite that made that docking possible is idle for most of MEV’s operating life between the roughly four-week installation windows that recur four or five times a year, which is the basis on which a later proposal argued for reusing MEV-class servicer cameras as a part-time space domain awareness sensor, one whose in-track viewing geometry looks at the GEO belt from an angle ground radars cannot reach [9]. The taxonomy that later NASA surveys use to place MEV-2 in context, robotic manipulation; rendezvous, capture, docking and mating; relocation; repair and maintenance; refueling; and structural assembly, was set by the first of those surveys and has been carried forward largely unchanged since [10]. MEV’s own published thruster performance has in turn become a stand-in figure for GEO servicer logistics studies that model fleets of vehicles rather than one: a 2021 optimization framework for trading high- and low-thrust servicer architectures against cost took its XR-5 Hall thruster specific impulse and thrust figures directly from Northrop Grumman’s public MEV data [11], and a later depot-placement study used MEV’s own duty cycle to argue that a shared servicing depot could cut the combined logistics mass of servicing two large constellations by 15 to 21 percent relative to separate fleets [12].

Mission profile

Parameter	Value	Source
Launch	15 August 2020, rideshare with Galaxy 30	[13]
Client	Intelsat IS-10-02	[8], [9]
Docked	12 April 2021, in an active GEO slot	[8], [9]
Function assumed	station-keeping and pointing; client propulsion and attitude control disabled	[9]
Service	five years of extended life	[13]

The published record has the vehicle operating with its original client as of 2022 [14] and as of 2025 [15], and gives its launch as 2020 [9]; the vendor fact sheet gives the 15 August 2020 rideshare date [13].

What is not established

MEV-2’s own performance is documented mainly by the vendor and by two conference papers from the vehicle’s own sensor engineers; no independent flight-data review of the docking or station-keeping handover has been published [8], [9], [13]. The three NASA ISAM/OSAM state-of-play editions cited above for MEV-2’s program context share large blocks of verbatim text and should not be read as three independent confirmations of the same facts [10], [14], [15]. SMART-OLEV’s docking figures, offered here as the closest precedent for MEV’s nozzle-capture approach, were pre-flight design projections published by the company selling the vehicle, and SMART-OLEV itself never flew [2]. The SPHERES docking-port work that bounds what a much smaller free-flyer needs for reliable capture was validated on a flat floor and a reduced-gravity aircraft, never on orbit, and cannot be read as a measurement of MEV’s own hardware [5]. The GEO servicing market argument above rests on secondary insurance and failure-rate statistics assembled by policy researchers, not on operator data [1], and the thruster-reuse and depot-sharing figures drawn from MEV specifications are optimization outputs built on assumed, not measured, cost and performance parameters [11], [12].