RPO Past, Present, and Future: How Spacecraft Learned to Meet, Inspect, Service, and Remove Objects in Orbit

Key Takeaways

• RPO began with crewed spaceflight and now supports servicing, inspection, and debris removal.
• Commercial RPO is moving from demonstrations toward life-extension and disposal services.
• Security concerns make transparency, standards, and operator trust central to future RPO growth.

RPO Past, Present, and Future Began With Crewed Rendezvous

On March 16, 1966, Gemini VIII completed the first docking between two spacecraft, linking the crewed Gemini spacecraft with an Agena target vehicle before a stuck thruster forced an emergency return to Earth. That mission showed both sides of rendezvous and proximity operations, or RPO: the technical value of bringing spacecraft together and the safety risk created when control margins disappear. The phrase RPO past, present, and future begins with this combination of promise and constraint.

RPO means the planned maneuvering of one spacecraft near another spacecraft, rocket body, station module, payload, or debris object. Rendezvous brings objects close together. Proximity operations cover the controlled activity near the target. Docking, berthing, capture, inspection, servicing, refueling, relocation, repair, and deorbiting may follow, depending on the mission. NASA often uses the related term RPOD, meaning rendezvous, proximity operations, and docking, because docking systems and close-range navigation usually belong to the same mission architecture.

The early record was dominated by human spaceflight. Gemini VI-A and Gemini VII conducted the first crewed space rendezvous in December 1965, proving that two spacecraft could meet in orbit without physically docking. Gemini VIII took the next step by making contact. Apollo then used rendezvous as a mission requirement rather than a demonstration. Lunar missions depended on the lunar module leaving the command module, landing on the Moon, launching back into lunar orbit, and rejoining the command and service module before the crew returned to Earth.

Soviet and Russian spaceflight added another important branch. Salyut, Mir, Soyuz, Progress, and later International Space Station operations made repeated rendezvous and docking part of normal orbital life. Automated systems such as Kurs allowed Russian spacecraft to approach and dock with stations, with human crews able to supervise or intervene. Europe later developed the Automated Transfer Vehicle, a large cargo spacecraft capable of automated rendezvous and docking with the International Space Station.

The early period established lessons that still shape RPO. Close operations require accurate tracking, relative navigation, reliable propulsion, safe abort paths, controlled flight rules, and clear authority between the chaser spacecraft and the target. A small error can matter because orbital motion does not behave like aircraft motion. Two spacecraft may appear close together, yet both are traveling at orbital velocity. The problem is relative motion, limited propellant, sensor uncertainty, communications delays, and the difficulty of predicting how a disabled or tumbling target will behave.

RPO also moved beyond crewed spacecraft through technology demonstration missions. The 2007 Orbital Express mission, managed by the Defense Advanced Research Projects Agency, validated autonomous on-orbit refueling and reconfiguration concepts using two spacecraft. It showed that robotic servicing could be technically feasible, even though broad commercial adoption did not follow immediately. The mission helped prove that RPO could support satellite maintenance, not only space station logistics.

The present phase differs from the first space age because RPO is no longer limited to government missions. Commercial operators now see RPO as a service capability. Governments see it as a tool for space sustainability, national security, and future logistics. Civil agencies see it as a pathway toward active debris removal, in-space assembly, and long-duration exploration. The technical act of approaching another spacecraft has become a gateway capability for much larger questions about the use, protection, and management of Earth orbit.

The Mechanics That Make Close Spacecraft Operations Possible

A spacecraft performing RPO must know where it is, where the target is, how both objects are moving, and how much uncertainty remains in that estimate. Long-range tracking may begin with ground radar, optical telescopes, space surveillance networks, onboard orbit determination, or data shared by the target operator. Close-range operations add cameras, lidar, radar, infrared sensors, relative navigation software, and guidance algorithms. NASA’s Johnson Space Center describes RPO work as involving guidance, navigation, control, trajectory design, analysis, and operational verification.

RPO can be cooperative or non-cooperative. Cooperative RPO occurs when the target helps the chaser by sharing data, carrying a docking adapter, providing navigation aids, maintaining attitude control, or following a preplanned operations protocol. Space station visiting vehicles are cooperative targets because station and vehicle teams coordinate approach corridors, hold points, communications, docking geometry, and abort procedures. Non-cooperative RPO is harder because the target may be dead, unresponsive, tumbling, unprepared for capture, or poorly characterized. A spent rocket stage, defunct satellite, or debris object does not help the servicer.

The technical sequence often begins far away from the target. The chaser adjusts its orbit through phasing maneuvers, then enters approach corridors where relative distance and closing speed shrink. Mission rules may require hold points where controllers verify navigation performance before allowing the vehicle to continue. Near the target, the chaser uses relative sensors and onboard software to estimate shape, motion, attitude, and range. Contact operations may involve docking rings, grappling fixtures, robotic arms, magnetic plates, adhesive pads, capture arms, nets, or other interfaces, depending on the mission.

The risk profile changes as distance falls. At long range, a bad maneuver may waste propellant or miss the target. At close range, a bad maneuver can create a collision, damage solar arrays, contaminate sensors, generate debris, or push a target into an unsafe attitude. Safe RPO design uses keep-out zones, approach cones, retreat paths, fault detection, and passive safety planning. Passive safety means that a spacecraft should drift away or remain safe if control is lost during defined portions of the approach.

Autonomy has become more important because future RPO missions may involve faster decision cycles, limited ground contact, and targets that behave unpredictably. Autonomy does not remove the need for human oversight. It changes the division of labor. Ground teams may approve mission phases and safety rules, but onboard systems may execute relative navigation, collision checks, and final approach corrections. Commercial software demonstrations such as the Starfish Space and Impulse Space Remora mission point toward more autonomous RPO in low Earth orbit.

The following table summarizes common RPO mission types and the technical demands associated with each category.

RPO also depends on mission design choices made years before launch. Satellites designed for servicing can include docking ports, fiducial markers, refueling interfaces, grapple fixtures, standardized software protocols, and clear physical access to service points. Legacy satellites usually lack these features. That mismatch explains why many servicing concepts are shifting toward prepared clients, attached life-extension pods, or specialized capture systems rather than universal robotic repair.

Cooperative Docking Turned RPO Into Routine Space Station Infrastructure

The International Space Station turned RPO into a repeated operational discipline. Soyuz crew vehicles, Progress cargo craft, Space Shuttle orbiters, SpaceX Dragon vehicles, Northrop Grumman Cygnus spacecraft, Japan’s HTV cargo vehicle, and Europe’s ATV all used forms of rendezvous and close approach to support the station. Some docked directly. Others approached close enough for capture by the station’s robotic arm. Each method required carefully planned approach paths, communications procedures, crew coordination, and abort options.

This routine should not be mistaken for simplicity. Station RPO has the advantage of cooperative design, trained crews, extensive flight rules, and decades of procedural experience. The ISS knows when a visiting vehicle is coming, where it should approach, what sensors it uses, what failures may occur, and when the vehicle must retreat. The station can orient itself, communicate with the vehicle, and manage visiting-vehicle traffic. Those advantages do not exist when a spacecraft approaches a silent rocket body, an aging communications satellite, or an unknown object in geosynchronous orbit.

Space station operations created a culture of incremental authority. A visiting vehicle may hold at specific distances before entering the next zone. Controllers review navigation data and system status. Crew members may monitor or command retreat. The approach corridor limits where the visiting vehicle can go. These practices influenced later commercial servicing concepts because they show how close operations can be managed by layered safety decisions rather than a single automated maneuver.

Commercial crew and cargo systems extended the RPO heritage into private operations under government oversight. SpaceX Dragon conducts automated approach and docking operations as part of NASA commercial resupply and crew missions. Boeing’s Starliner was designed for autonomous docking with the ISS under NASA’s Commercial Crew Program, although its 2024 crewed flight test became better known for propulsion and helium-system issues than for routine docking performance. The relevant lesson for RPO is that private vehicles can conduct complex close operations when the destination, interface, and certification framework are defined in advance.

Station logistics also showed the economic value of repeatability. Once procedures, interfaces, training, and ground systems exist, each mission can use a known operational pattern. That repeatability lowers risk and supports cost control. Future RPO markets will likely need the same effect. A one-off servicing demonstration proves technical ability. A market requires repeat missions, repeat customer interfaces, repeat pricing models, and repeat regulatory handling.

RPO near the ISS remains a special case because human safety dominates operational rules. Crewed spacecraft and cargo vehicles receive higher scrutiny because a collision could threaten astronauts. Commercial satellite servicing outside station operations faces a different balance. Human life is usually not directly at risk, but debris creation, customer asset loss, insurance exposure, and national security concerns remain significant. The discipline learned from station operations still matters because it provides a mature reference model for planned approach, hold, retreat, and coordination.

Satellite Servicing Moved RPO From Demonstration to Business

On February 25, 2020, Northrop Grumman’s SpaceLogistics Mission Extension Vehicle-1 docked with Intelsat 901 in geosynchronous graveyard orbit, then returned the satellite to commercial service. That mission marked a turning point because it moved RPO from demonstration toward revenue-generating satellite life extension. MEV-1 remained attached for about five years, then undocked from Intelsat 901 in April 2025 after moving the client spacecraft back into a graveyard orbit.

The second SpaceLogistics vehicle, MEV-2, docked with Intelsat 10-02 in April 2021. Both MEV missions used a servicing approach suited to geostationary communications satellites that were not originally built with standard servicing ports. The servicing vehicle docked with the client satellite’s liquid apogee engine nozzle area, then supplied attitude and orbit-control capability. This was not repair in the everyday consumer sense. It was orbital life extension through attached propulsion and control.

The business case for life extension is straightforward. Large geostationary satellites cost hundreds of millions of dollars to build, launch, insure, and operate. If a satellite remains functional but runs low on propellant, the operator may gain revenue by extending service instead of replacing the asset immediately. Servicing can also give operators more flexibility when replacement satellites face manufacturing delays, launch delays, or uncertain demand. The economics depend on service price, remaining satellite health, replacement cost, insurance treatment, customer contracts, and confidence in the servicing provider.

Northrop Grumman has also described a next-generation approach involving a Mission Robotic Vehicle and smaller Mission Extension Pods through its SpaceLogistics services. The pod model seeks to separate the expensive robotic servicer from the attached life-extension hardware. A reusable robotic vehicle would install pods on multiple satellites, and each pod would provide years of orbit-control support. If the model works at scale, it could reduce the cost per customer and create a more service-like market.

NASA’s experience shows that commercial adoption is not automatic. The agency decided in 2024 to discontinue OSAM-1, its On-orbit Servicing, Assembly, and Manufacturing 1 project, citing technical, cost, schedule, and customer-partner problems. The cancellation did not end RPO or in-space servicing. It revealed that refueling an unprepared spacecraft is expensive, technically demanding, and hard to justify without committed customers. It also pushed attention toward servicing missions with clearer customer value and simpler interfaces.

Commercial RPO is now taking a more segmented form. One segment focuses on geostationary satellite life extension. Another targets low Earth orbit inspection and disposal. Another supports government mobility and logistics. Another explores future refueling, repair, upgrade, and assembly. The common capability is close approach, but the customers, risk tolerance, revenue model, and technical interface differ by orbit and mission.

Debris Inspection and Removal Are Expanding the Mission Set

Active debris removal has become one of the most visible future uses of RPO because orbital debris already threatens spacecraft, stations, and future commercial activity. The European Space Agency’s ClearSpace-1 mission is planned to remove the 95 kg PROBA-1 satellite from low Earth orbit. ESA describes the mission as the first attempt to remove an unprepared and uncooperative object from orbit through precise close-proximity operations. As of June 6, 2026, ClearSpace lists a planned 2028 launch for the mission.

The ClearSpace-1 target history shows how difficult debris-removal planning can be. The mission originally targeted a Vega payload adapter from a 2013 launch. ESA changed the target after the adapter appeared to be struck by another piece of debris, creating extra trackable fragments. The change from one target to another underscores a basic reality of debris removal: the target itself may change, fragment, tumble, or become riskier before the removal spacecraft ever arrives.

Japan has become another important center for debris-inspection RPO. Astroscale’s ADRAS-J mission was designed to approach and characterize an existing large debris object through RPO. On March 25, 2026, Astroscale announced that ADRAS-J had completed operations and begun controlled deorbit after 293 days in orbit. The follow-on ADRAS-J2mission is planned to approach, capture, and deorbit the same type of rocket body using a robotic arm as part of Japan’s Commercial Removal of Debris Demonstration program.

Astroscale’s mission sequence matters because inspection often comes before removal. Operators need to understand the target’s rotation, surface condition, structural integrity, orbit, and capture points. A debris-removal spacecraft cannot assume that a rocket stage or dead satellite behaves like a cooperative client. It may tumble. It may have fragile components. It may lack a safe grasping point. It may carry residual fuel or pressure. It may also be difficult to image from Earth at the level needed for robotic capture planning.

Low Earth orbit debris removal also faces an economic puzzle. A dead object does not pay for its own removal. A commercial satellite operator may pay to deorbit its own spacecraft at end of life, particularly if regulations, insurance, or customer expectations require it. Older debris may require government procurement, international funding, or liability-driven agreements. That makes active debris removal both a technical service and a public-policy problem.

Starfish Space is pursuing another commercial path. Its Otter vehicle is designed for autonomous rendezvous, proximity operations, and docking. The company’s Otter Pup 2 mission is intended to demonstrate RPO and docking with an unprepared commercial spacecraft in low Earth orbit. The Starfish and Impulse Space Remora mission, announced on December 15, 2025, validated autonomous rendezvous software using Impulse’s Mira spacecraft. These steps suggest that low Earth orbit servicing may develop through software, sensors, and capture methods tailored to smaller satellites.

Debris missions also connect RPO to future constellation operations. Large low Earth orbit constellations may include hundreds or thousands of spacecraft. Even with high reliability, some satellites will fail. Regulators and customers increasingly expect operators to manage post-mission disposal. RPO-based deorbit services could become a backup option for satellites that cannot dispose of themselves. That market will depend on failure rates, legal obligations, deorbit reliability, and whether operators design future satellites with servicer-friendly interfaces.

Defense and Security Uses Make RPO Politically Sensitive

RPO is inherently dual-use. The same basic capability can inspect a satellite, extend its life, remove debris, reposition a friendly asset, or approach a foreign spacecraft in a way that raises security concerns. The Secure World Foundation has described RPO as both a potential source of instability and a tool for safer, more sustainable space activity. That dual character explains why commercial servicing, debris removal, and defense inspection are hard to separate in policy discussions.

The United States operates the Geosynchronous Space Situational Awareness Program, whose satellites support space surveillance in the near-geosynchronous orbit regime. The U.S. Space Force and United Launch Alliance launched the USSF-87 mission on February 12, 2026, carrying national security spacecraft connected with geosynchronous surveillance. GSSAP shows how close observation can serve defensive awareness by helping operators understand objects in high-value orbits. The same presence may appear suspicious to another state if the inspected spacecraft belongs to it. Intent is difficult to prove from orbital behavior alone.

China’s Shijian-21 added another public example of RPO ambiguity. Public tracking analysis reported that Shijian-21 docked with or grappled a defunct Chinese navigation satellite and moved it out of the geostationary belt in 2022. From one perspective, the activity resembled debris mitigation. From another, it demonstrated that a spacecraft could approach, attach to, and move another object in geosynchronous orbit. Such activities can be beneficial, but they also make other operators ask how similar systems might behave in a dispute.

Russian inspector satellites have also drawn attention. The Secure World Foundation’s Russian RPO fact sheet describes Russian robotic rendezvous and proximity operations in low Earth orbit and geostationary orbit since 2014. Public reporting and open-source tracking have associated Luch/Olymp spacecraft with close approaches to other satellites in geostationary orbit. A January 2026 fragmentation event involving a retired Luch/Olymp spacecraft raised debris concerns in the graveyard region above geostationary orbit.

Security concerns do not make RPO illegitimate. They make transparency and communication more important. A planned debris-removal mission with a declared target, licensed operator, published mission phases, and cooperative customer presents a different risk profile from an unexplained close approach to another nation’s satellite. Mission intent, notification, consent, approach distance, target ownership, maneuver history, and communications channels all shape how an RPO activity is interpreted.

Defense and security users may become important RPO customers. Military operators want satellites that can maneuver, refuel, relocate, inspect, and recover from anomalies. Commercial companies want to serve those customers, but the security market brings export controls, classified requirements, procurement barriers, and greater concern about dual-use perception. RPO providers serving civil and commercial customers may need different mission rules and governance structures when serving defense clients.

The future challenge is not simply preventing misuse. It is creating enough confidence for beneficial uses to grow without making every close approach look like a threat. That requires space situational awareness data, operator-to-operator communication, norms of behavior, pre-mission transparency, and technical standards that distinguish responsible servicing from destabilizing activity.

Standards, Regulation, and Trust Are Lagging Behind Capability

RPO missions sit at the boundary of engineering, law, insurance, diplomacy, and operations. The technical ability to approach another satellite is only one part of the problem. Operators need authorization, spectrum rights, liability coverage, customer consent, debris-mitigation plans, safety analysis, and operational coordination. In many jurisdictions, existing licensing systems were built for launch, remote sensing, communications, and ordinary satellite operations, not for one spacecraft approaching and interacting with another.

The Consortium for Execution of Rendezvous and Servicing Operations was created as an industry-led initiative to develop best practices and standards for RPO and on-orbit servicing. DARPA’s CONFERS program supported an independent forum where industry could engage with government on servicing standards. CONFERS later influenced international standards activity, including ISO 24330:2022, which establishes programmatic principles and practices for RPO and on-orbit servicing providers.

Standards help define expectations before a mission flies. They can address mission planning, safety zones, information sharing, client consent, system reliability, anomaly response, operator competence, and end-of-mission disposal. Standards cannot solve every political problem, but they give regulators, insurers, customers, and operators a shared vocabulary. That matters because RPO failures can affect more than the two spacecraft involved. A collision or debris event can create hazards for other operators that had no role in the mission.

The United Nations Committee on the Peaceful Uses of Outer Space adopted 21 long-term sustainability guidelines in 2019. Those guidelines cover policy and regulatory frameworks, safety of space operations, international cooperation, capacity-building, awareness, and research. They do not function as detailed RPO operating rules, but they support the wider principle that space activities should protect the long-term usability of orbital regions.

Regulators face a timing problem. If they move too slowly, companies may develop incompatible systems and mission practices. If they move too aggressively, they may freeze a young market before flight experience clarifies what rules work. The best near-term path is likely a combination of mission-specific licensing, voluntary consensus standards, customer-contract requirements, insurance review, and public transparency for non-sensitive operations. Defense and intelligence missions may remain less transparent, which makes international trust harder.

Insurance and finance will also shape trust. Insurers will want evidence that RPO missions can be planned, tested, and flown with acceptable risk. Investors will want signs that customers will pay for repeat services. Satellite operators will want contractual protection if a servicer damages their asset. Governments will want assurance that RPO does not create debris or escalate diplomatic disputes. These requirements may be as important as robotics or sensors in determining which companies survive.

RPO standards also need to account for mission diversity. A cooperative docking between two commercial spacecraft in low Earth orbit differs from a debris-removal attempt involving an uncontrolled rocket stage. A geostationary life-extension mission differs from inspection of a foreign satellite. A single rulebook cannot treat all missions as identical. A more practical approach classifies missions by consent, target cooperation, proximity distance, contact type, orbit, consequence of failure, and transparency level.

The Next RPO Market Depends on Autonomy, Interfaces, and Customers

RPO past, present, and future now points toward a practical question: which services will pay for repeat missions. The answer will differ by orbit. In geostationary orbit, life extension has already been demonstrated with commercial clients. In low Earth orbit, deorbit and inspection services may become more attractive as satellite counts increase and disposal expectations tighten. In cislunar space, future RPO may support logistics, depots, infrastructure assembly, and inspection, but those markets remain less mature.

Prepared interfaces may decide how fast the market grows. Servicing is easier when satellites include docking plates, grapple fixtures, refueling ports, optical markers, and software protocols from the start. Older satellites force servicers to adapt to designs that were never meant to be touched after launch. The more new spacecraft are designed for servicing, the less each RPO mission has to solve the same problem from scratch. Standard interfaces can turn bespoke missions into repeatable services.

Autonomy will also shape cost. A mission that requires large ground teams, long campaigns, and custom analysis for each target may work for expensive geostationary assets or government contracts. It may not work for lower-value satellites in low Earth orbit. Autonomous navigation, onboard safety checks, reusable software, and common hardware can reduce operating cost. Starfish Space’s mission portfolio reflects the market interest in making close operations less dependent on large bespoke mission teams.

Government procurement may anchor several early markets. ESA’s ClearSpace-1, Japan’s CRD2 program, DARPA’s earlier Orbital Express and CONFERS work, and U.S. defense interest in space mobility all show that governments often fund first-of-kind RPO activity. On January 21, 2026, Starfish Space announced a Space Development Agency contract for end-of-life disposal services using an Otter spacecraft targeting launch in 2027. Commercial adoption tends to follow when a service has clear value, manageable risk, and repeatable demand.

The following table outlines likely future RPO service lines and the factors that may limit or accelerate adoption.

The strongest early business cases share a common feature: the value of the saved, moved, inspected, or removed asset exceeds the mission cost by a clear margin. A multihundred-million-dollar geostationary satellite can justify life extension more easily than a small low Earth orbit satellite unless that smaller satellite is part of a high-value constellation or carries sensitive government payloads. Active debris removal may require public funding because the benefit is shared across many operators.

RPO will also link to in-space servicing, assembly, and manufacturing. NASA’s 2025 State of Play describes rendezvous, proximity operations, capture, docking, and mating as a capability area that enables interaction between spacecraft. Large space telescopes, modular stations, orbital data centers, fuel depots, and lunar logistics systems all become easier if spacecraft can approach, attach, exchange resources, and separate safely.

The field could split into two cultures. One culture will focus on open, cooperative commercial servicing using published standards and customer consent. The other will focus on defense mobility, inspection, and resilience under more restricted disclosure. Both will use RPO. The health of the overall market may depend on whether those cultures can coexist without making every commercial close approach look suspicious.

RPO Will Shape the Future Space Economy

RPO changes the space economy by challenging the old model of build, launch, operate, abandon, and replace. Servicing allows some satellites to stay useful longer. Inspection allows operators to understand failures rather than guess from telemetry. Debris removal offers a path to reduce hazards that previous missions left behind. Refueling and mobility could let satellites shift missions after launch. Assembly could allow larger structures than a single rocket fairing can carry.

This change does not mean that every satellite will be serviced. Many satellites will remain cheaper to replace than repair. Some orbits may not justify servicing traffic. Some spacecraft will lack interfaces or carry designs that make contact risky. Some operators may prefer rapid replacement cycles over complex maintenance. RPO will grow where the economics, safety case, and mission value align.

Defense and security demand may accelerate the market. Spacecraft that can maneuver, inspect, refuel, or receive service become more resilient. Governments may pay for capabilities that commercial operators view as too expensive. Defense procurement can fund early demonstrations, but it can also increase secrecy and geopolitical concern. A commercial servicing company that works with defense customers may need to prove that its civil missions remain transparent and consent-based.

RPO also creates ancillary markets. Sensor manufacturers, propulsion suppliers, robotics firms, mission-planning software providers, space situational awareness companies, insurance underwriters, standards bodies, and ground-system operators all gain work when close-proximity missions increase. Universities and research institutions gain new demand for autonomy, control systems, and orbital dynamics expertise. Workforce needs will include flight dynamics, robotics, software assurance, safety analysis, regulation, and customer mission integration.

The market will reward reliability more than spectacle. A dramatic docking demonstration can attract attention, but customers will buy repeatability, pricing clarity, regulatory confidence, and low probability of loss. This makes the future of RPO less like a single invention and more like an industrial discipline. The winners will likely be operators that combine flight heritage, conservative safety culture, scalable autonomy, and service contracts that make sense to satellite owners.

By June 6, 2026, RPO had crossed from heritage skill to commercial infrastructure candidate. It remained technically demanding and politically sensitive, but the direction was visible. Spacecraft were beginning to inspect, dock with, service, and prepare to remove objects in orbit. The next phase will test whether these missions become routine operations with shared rules, or remain specialized demonstrations serving a limited set of high-value customers.

Summary

RPO began as a human-spaceflight necessity. Gemini, Apollo, Soyuz, Progress, Mir, and the International Space Station proved that spacecraft could meet and connect in orbit under planned conditions. The same discipline later moved into robotic demonstrations, satellite life extension, debris inspection, and proposed active debris removal. Each step expanded the meaning of RPO from docking to a broader set of close-spacecraft operations.

The present market is no longer theoretical. Northrop Grumman’s Mission Extension Vehicles demonstrated commercial life extension in geosynchronous orbit. Astroscale’s ADRAS-J showed commercial debris inspection and entered deorbit operations in March 2026. ESA and ClearSpace are preparing a 2028 mission to remove PROBA-1. Starfish Space and Impulse Space demonstrated autonomous rendezvous software in low Earth orbit in December 2025. NASA’s OSAM-1 cancellation showed that some ambitious servicing models remain too costly or weakly supported by customers.

The future of RPO will depend on repeatable interfaces, trusted autonomy, clear standards, and customers with assets valuable enough to justify servicing. It will also depend on political restraint because the same tools that enable inspection and repair can generate suspicion when used near another operator’s spacecraft. The most successful RPO market will likely be the one that makes close operations ordinary, transparent, insurable, and safe enough to support the next generation of orbital services.

Appendix: Useful Books Available on Amazon

• Space Warfare: Strategy, Principles and Policy
• The Politics of Space Security
• Space Strategy in the 21st Century
• Space Is Open for Business
• Developing National Power in Space

Appendix: Top Questions Answered in This Article

What Does RPO Mean in Spaceflight?

RPO means rendezvous and proximity operations. It refers to planned spacecraft maneuvers that bring one spacecraft near another object in orbit. The target may be a spacecraft, space station, satellite, rocket body, payload, or debris object. RPO can support docking, inspection, servicing, refueling, capture, relocation, or deorbiting.

Why Did RPO First Matter for Human Spaceflight?

RPO first mattered because crewed lunar and station missions required spacecraft to meet in orbit. Gemini proved rendezvous and docking techniques. Apollo depended on lunar-orbit rendezvous after the lunar module returned from the Moon’s surface. Space stations later made docking and visiting-vehicle operations part of routine orbital logistics.

What Is the Difference Between Cooperative and Non-Cooperative RPO?

Cooperative RPO occurs when the target supports the approach through communications, navigation aids, docking hardware, or controlled attitude. Non-cooperative RPO occurs when the target does not help. Dead satellites, rocket bodies, and debris objects are harder targets because they may tumble, lack interfaces, and provide no direct data to the servicer.

Why Is Satellite Life Extension an Early Commercial RPO Market?

Satellite life extension can preserve revenue from expensive spacecraft that still work but have limited propellant. Geostationary communications satellites are particularly attractive because replacement satellites cost significant capital and may take years to manufacture and launch. A servicer can attach to the satellite and provide orbit-control support.

Why Is Active Debris Removal Difficult?

Active debris removal is difficult because old debris usually lacks capture interfaces and may be unstable or poorly characterized. The removal spacecraft must approach safely, understand the target’s motion, capture it without creating new debris, and control the combined object. The business case is also difficult because old debris does not pay for removal.

Why Does RPO Raise Defense and Security Concerns?

RPO raises security concerns because close approach, inspection, attachment, and movement can serve both peaceful and military purposes. A spacecraft that can inspect or service one satellite could worry another operator if it approaches without consent or explanation. Transparency, communication, and standards help reduce misinterpretation.

What Role Do Standards Play in RPO?

Standards give operators, regulators, customers, and insurers common expectations for mission planning and safety. They can address consent, mission phases, anomaly response, operational transparency, and responsible behavior. Standards do not remove all risk, but they reduce uncertainty and support repeat commercial operations.

How Does RPO Connect to the Space Economy?

RPO supports satellite servicing, debris removal, inspection, refueling, logistics, and in-space assembly. These services can extend asset life, reduce replacement pressure, and support new infrastructure. RPO also creates demand for sensors, robotics, propulsion, software, flight dynamics, insurance, standards, and mission operations expertise.

Will Every Satellite Be Designed for Servicing?

No. Some satellites will remain cheaper to replace than service. Others may operate in orbits or markets where servicing does not make financial sense. Servicing is most likely for high-value satellites, government spacecraft, constellation failures that threaten compliance, and future systems designed with docking or refueling interfaces.

What Is the Most Likely Future for RPO?

The most likely future is selective growth rather than universal servicing. RPO will expand in high-value missions such as geostationary life extension, debris inspection, low Earth orbit deorbit services, defense mobility, and prepared-interface servicing. Wider adoption will depend on cost, safety, standards, customer demand, and trust.

Appendix: Glossary of Key Terms

Rendezvous and Proximity Operations

Rendezvous and proximity operations describe planned spacecraft maneuvers that bring one object near another in orbit. The mission may end with docking, capture, inspection, servicing, refueling, relocation, or separation. The concept includes navigation, control, safety planning, communication, and operational coordination.

RPOD

RPOD means rendezvous, proximity operations, and docking. NASA often uses the term when docking hardware and close-range operations are part of the same mission architecture. RPOD focuses on how spacecraft approach, interact, connect, and separate safely.

Cooperative RPO

Cooperative RPO occurs when the target spacecraft supports the operation. The target may provide navigation aids, communications, attitude control, docking hardware, or known geometry. Space station visiting vehicles usually operate in cooperative conditions because both sides plan the approach.

Non-Cooperative RPO

Non-cooperative RPO occurs when the target does not support the operation. The target may be dead, unresponsive, tumbling, or never designed for servicing. Debris removal and inspection missions often involve non-cooperative targets, making close operations harder and riskier.

Geosynchronous Orbit

Geosynchronous orbit is an orbit where a satellite’s orbital period matches Earth’s rotation period. Many communications and surveillance satellites use this orbital region because it allows persistent coverage of large geographic areas. Servicing missions in this region often involve expensive, high-value spacecraft.

Low Earth Orbit

Low Earth orbit is the orbital region relatively close to Earth, commonly used by crewed spacecraft, Earth observation satellites, and large communications constellations. RPO in this region may support station logistics, constellation disposal, inspection, and debris-removal missions.

Active Debris Removal

Active debris removal means sending a spacecraft to capture, move, or deorbit a defunct satellite, rocket body, or other debris object. The goal is to reduce long-term collision risk. These missions are difficult because the target often lacks helpful interfaces.

On-Orbit Servicing

On-orbit servicing refers to maintenance, life extension, repair, inspection, refueling, upgrade, relocation, or disposal services performed after a spacecraft has launched. RPO is usually the first operational step because the servicer must safely approach the client spacecraft.

Space Situational Awareness

Space situational awareness means detecting, tracking, characterizing, and understanding objects and activities in space. It supports collision avoidance, mission planning, anomaly analysis, and security monitoring. RPO missions rely on this information before and during close approach.

Mission Extension Vehicle

A Mission Extension Vehicle is a satellite-servicing spacecraft developed by Northrop Grumman’s SpaceLogistics business. It attaches to a client satellite and provides propulsion and attitude-control support. MEV-1 and MEV-2 demonstrated commercial life extension for geostationary satellites.