Rendezvous & Proximity Operations (RPO) with Unprepared Satellites: Technical & Licensing Gates

Aerial dusk view over Puget Sound aerospace manufacturing corridor with Mount Rainier in the distance

Regulatory gates verified against 47 CFR Part 25 and 15 CFR Part 960 as of 2026-11-16.

ORBITAL SUSTAINABILITY · WA SERVICING & HABITATS · FCC / NOAA / NASA RPO STANDARDS
RPO with Unprepared Satellites
Docking with or servicing an uncooperative or unprepared client satellite—the core capability tested by Starfish Space's Otter Pup 2 and Remora—triggers multi-agency RPO disclosures, non-interference RF rules, and NOAA imaging-of-space-objects review.
Primary Authority / Source: FCC / NOAA / NASA  |  As-Of / Horizon: Active Nov 2026
ORBITAL SUSTAINABILITY · PDF & MARKDOWN TWIN
RPO with Unprepared Satellites — Reference Brief
Download the 2-page printable reference PDF or read the clean Markdown twin for AI and briefing workflows.
Unprepared-Client RPO: Technical & Regulatory Gates
Unprepared-Client RPO: Technical & Regulatory Gates

Documented Instrument & Engineering Record

  • Why unprepared clients matter: Nearly all legacy LEO and GEO satellites launched before 2024 lack standardized grappling fixtures, fiducial markers, or refueling ports.
  • Technical risk: Tumbling rates, plume impingement from servicer thrusters, and optical sensor glare complicate close-range capture.
  • FCC licensing gate: RPO operators must disclose approach trajectories, abort/safe-mode corridors, and combined-stack disposal plans in their FCC Part 25 or Part 5 ODMP.
  • NOAA Part 960 intersection: Optical cameras used for RPO navigation can trigger NOAA remote-sensing review when imaging other artificial space objects.

RPO Licensing & Engineering Gate Matrix

GateGoverning AuthorityRequired Proof
Safe-Approach TrajectoryFCC Part 25 / Part 5Passive-safe abort ellipse if thrusters fail
RPO Optical SensorsNOAA 15 CFR Part 960Non-Earth imaging / shutter-control clearance
Combined-Stack DisposalFCC § 25.283 / NASA ODARPassivation & deorbit math for mated stack
Third-Party LiabilityCommercial Contract / FAAClient consent & cross-waiver of liability

Mission Designer, Compliance Lead & Founder Takeaways

  • An RPO servicer cannot legally approach or capture a third-party satellite without explicit operator consent and U.S. government coordination.
  • Designers should model the *combined* servicer-plus-client mass and cross-section for post-capture 5-year deorbit and 1:10,000 casualty risk.
  • Starfish Space's Remora (Dec 2025) proved single-camera closed-loop RPO software, reducing hardware mass for future Otter missions.

Connected Census Profiles, Segments & Rules

Primary Sources & Official Records

BC ESG

ESG Strategy, Sustainability Intelligence, and Business Continuity for Forward-Thinking Organizations

© 2026 BC ESG — Business Continuity, ESG & Sustainability Intelligence