—·
Northrop Grumman’s mission-extension vehicles have demonstrated commercial satellite docking. The next test is turning a small number of missions into repeatable, measurable service.
Use CISA KEV as a measurable “patch supply chain” drill: score risk by integration path, stage safely, and audit remediation lag end to end.
As NHTSA spotlights remote assistance and ADS behavioral competencies, AV makers are redesigning escalation AI: handoff triggers, logging, operator authority, and safety evidence now have to be measurable and auditable.
Indonesia’s SKP pathways are shifting from “learning completion” to “credit assurance,” where interoperability, e-certificate timing, and verification status checks shape provider competition and audit risk.
A satellite operator considering a mission extension needs more than proof that a servicing vehicle can dock. It needs to know whether the service can be completed reliably, fit the spacecraft and customer’s needs, and be available on a useful schedule.
The supplied sources do not document Starship Flight 14, so they cannot support an assessment of its orbit insertion, payload deployment, engine reliability, recovery or launch cadence. This article instead examines what the validated material can show about commercial satellite servicing: what has been demonstrated, and what still stands between individual missions and routine service.
Northrop Grumman’s Mission Extension Vehicle (MEV) docks with a satellite and provides propulsion and attitude control, allowing the client satellite to continue operating. The company’s documented missions offer a practical case study in orbital servicing, while newer efforts from NASA and DARPA point to the next technical tests. The evidence supports a measured conclusion: docking and service are no longer only concepts, but a few demonstrations do not establish a high-cadence, broadly available service industry. (Northrop Grumman; NASA; DARPA)
MEV-1 launched in 2019 and docked with Intelsat 901 in 2020. MEV-2 launched in 2020 and docked with Intelsat 10-02 in 2021. Northrop Grumman describes both as commercial mission-extension services. The missions involved two separate vehicles and two client satellites, not repeated sorties by a single vehicle. (Northrop Grumman)
These missions moved satellite servicing from a proposed capability to a customer-facing operation. A servicing vehicle must do more than reach orbit: it has to approach a client satellite, manage relative motion, make contact and establish a stable connection without disrupting the client’s operation. “Relative navigation” means determining one spacecraft’s position and movement in relation to another.
Northrop Grumman presents the vehicles as capable of extending satellite missions by five years. That figure gives operators a concrete planning horizon, but it is not a universal guarantee across satellite fleets. The public material cited here does not establish that every spacecraft can accept the same service or that the same duration applies to every mission. Satellite condition, interface compatibility and the customer’s operating plan all affect what an extension means in practice. (Northrop Grumman)
The MEV cases establish that commercial docking and subsequent support have been carried out. They do not, by themselves, disclose enough detail to assess every navigation, fault-response or servicing performance measure an operator would want. Two client missions are stronger evidence than one isolated demonstration, but they do not establish compatibility across a fleet.
The NASA and DARPA announcements extend the evidence base, but they do not yet provide the same kind of evidence as the MEV missions. Northrop’s record here includes two named client dockings: Intelsat 901 in 2020 and Intelsat 10-02 in 2021. NASA’s 2026 account reports a robotic servicing mission launched with NASA support; DARPA’s 2026 account reports a technology launch for its Robotic Servicing of Geosynchronous Satellites (RSGS) effort. These are identifiable mission milestones, not reported demonstrations of completed customer service. (Northrop Grumman; NASA; DARPA)
The orbital setting matters. Geosynchronous orbit is a high orbit in which a satellite appears to remain over roughly the same region of Earth. DARPA’s RSGS focus makes it relevant to servicing in that environment, but a technology launch does not establish that a robotic servicing task has been completed there. Likewise, NASA’s reported launch establishes activity with NASA support, not a recurring commercial service or a record of completed customer tasks. The available accounts do not provide comparable task-level outcomes for either effort.
Read the evidence as a sequence, not a tally. A launch establishes that a mission has begun; proximity operations and capture would establish further capabilities; a completed service task and continued client operation would answer different questions again. The next meaningful updates from NASA and DARPA are therefore not simply additional launch announcements, but verifiable accounts of which tasks were completed, under what conditions, and with what effect on the client spacecraft.
The cited record contains different kinds of evidence that should not be collapsed into a single “success” rate. MEV-1 and MEV-2 each docked with a named Intelsat satellite, while the NASA and DARPA accounts cited here report launches. That is enough to distinguish demonstrated commercial docking from newer mission activity, but not enough to compare reliability across programs. The sources do not supply common figures for approach success, anomalies, task duration, client-service interruptions or post-service performance. (Northrop Grumman; NASA; DARPA)
For a customer, reliability needs to be assessed in stages. A provider’s record should say whether the vehicle launched, reached the client, completed the planned contact, delivered the contracted service and left the client able to continue operating. Those stages are not interchangeable: successful docking is evidence of rendezvous and capture, but it does not by itself quantify service continuity or the likelihood of completing a future mission.
A useful mission report would identify those stages, record anomalies and explain how each outcome was measured. Providers can protect customer-sensitive details while still reporting comparable performance categories and the limits of the available data. Operators can use those records to set mission-specific acceptance criteria, contingency plans and schedule margins. Until comparable outcomes exist, demonstrated capability should count as evidence only for the stages actually completed, not as proof of end-to-end reliability.
The two documented MEV missions involved separately named vehicles, MEV-1 and MEV-2, and two client satellites. That establishes two instances of commercial docking and support, but the record presented here does not show one MEV vehicle completing a client mission, returning for refurbishment and then serving another customer. Reuse of a servicing vehicle is different from repeatability across a fleet: the first requires evidence about recovery, inspection, replenishment or refurbishment, and redeployment. The cited material supplies no such turnaround record. (Northrop Grumman)
The dates also do not establish a commercial service rate. MEV-1 launched in 2019 and MEV-2 in 2020, with their respective dockings in 2020 and 2021. These adjacent-year milestones show that two missions were flown in successive years; they do not reveal how long each vehicle took to prepare, how much capacity was available, what customers’ wait times were, or whether the provider could meet an unscheduled demand. NASA’s and DARPA’s 2026 launch reports add activity to the field, but not a public record of commercial servicing cadence. (Northrop Grumman; NASA; DARPA)
A prospective customer should ask whether a quoted service depends on a new vehicle for each mission or on a vehicle being redeployed, what the provider has actually reused, and what interval between contract, launch and service it can substantiate. Providers should distinguish flown operations from planned capabilities and offer schedule assumptions customers can evaluate. Until that evidence exists, routine availability and rapid response should not be treated as established features of the market.
A sound readiness review should separate four questions: Can the servicer reach the client? Can it complete the planned operation? Can the customer’s spacecraft continue its mission afterward? Can the provider repeat the service on a schedule that meets commercial needs? The MEV cases give concrete evidence for commercial docking and mission extension; the NASA and DARPA sources document newer mission activity. The available material does not answer all four questions across a broad customer base. (Northrop Grumman; NASA; DARPA)
NASA and DARPA should publish clear, mission-level descriptions of what their supported or funded demonstrations have actually completed, while commercial providers should report client-service outcomes in terms customers can compare. Operators should make demonstrated compatibility, defined service boundaries and contingency procedures explicit in procurement documents. These requirements do not prejudge whether a technology will succeed; they make the evidence needed for a responsible decision visible.
By 2028, the most useful test of progress will not be the count of servicing announcements, but whether providers can show repeat customer operations, transparent performance records and a credible schedule for new missions. That is a forecast, not a claim that the current sources prove such a cadence is in place. Buy demonstrated service, and make every unproven step earn its own readiness gate.