patent.fyi
Applications  /  US 2026/0356500
United States Patent Application Publication

US 2026/0356500 A1

Published
Nov 12, 2026
Filed
May 6, 2025
Earliest date on the face
May 6, 2025
Classification
B64G 1/244
First published here
Nov 20, 2026

Generated automatically. Not reviewed by a person. Not legal advice or an opinion.

Section 1 · machine-generated

What if?

Questions about how individual parts of claim 1 might be changed. A question may describe something different from what the claim language recites, or a version of it; no view is offered on which.

1.1Separate orbital altitude bands

What ifWhat if spacecraft stay in separate altitude bands under standing operating rules?
Claim language“identifying a predicted collision”

A flight computer estimates perigee and apogee from navigation measurements and commands stationkeeping burns as either value approaches its assigned limit. A guard band between neighboring assignments provides clearance for orbit estimation error and altitude drift.

1.1Reserve crossing time slots

What ifWhat if controlled spacecraft cross a shared orbital region only during assigned time slots?
Claim language“identifying a predicted collision”

A ground scheduler allocates nonoverlapping time slots for passage through a defined region, with guard intervals for navigation and burn timing errors. Each spacecraft waits in a holding orbit until its assigned departure time, then executes the transfer burn.

1.2Transfer force through grapples

What ifWhat if the satellites attach mechanical grapples to the target and move it with thrusters?
Claim language“respective electromagnetic deflection modules”

Two servicing satellites synchronize with a cooperative target and latch robotic end effectors onto separate structural fixtures. After both latches confirm engagement, the satellites fire their thrusters along coordinated thrust vectors to change the combined orbit while limiting rotation.

1.2Use independent local responses

What ifWhat if each satellite determines its own intervention from local measurements without a shared deflection plan?
Claim language“a collaborative deflection strategy”

Each satellite uses range and range rate to estimate the target trajectory and applies a short field pulse when the measured track falls inside its intervention window. Later satellites measure the trajectory again and act only if the remaining predicted miss distance is below their threshold.

1.3Command one servicing satellite

What ifWhat if a single servicing satellite performs the entire maneuver?
Claim language“controlling the plurality of satellites”

A ground controller selects one satellite with enough propellant and lead time to rendezvous and dock with a cooperative target. The docked satellite performs a tangential burn that changes the target's arrival time at the predicted encounter point.

Section 2 · machine-generated

Variations

Further arrangements of the same subject matter, described here as of the publication date at the foot of this page.

Other field of use

Collision separation in a ground testbed

Two air-bearing vehicles coast across a level granite table while smaller air-bearing vehicles carry electromagnet assemblies. An overhead camera tracks fiducials on every vehicle, and a controller projects the closest approach of the two coasting vehicles. When the projected separation falls below a set threshold, the controller directs two or more electromagnet carriers to pass beside a steel plate on one vehicle and pull it laterally in successive passes.

Component substitution

Permanent magnet rotors for field control

Each servicing satellite uses a motor-driven permanent magnet rotor in place of a current-driven field coil. A shaft encoder measures rotor angle, and the attitude controller points the rotor axis so the magnetic field gradient pulls on a soft iron fixture on the target. The encounter controller commands rotor angle and satellite standoff to set the direction and strength of the interaction. The planner assigns successive passes to multiple satellites so their lateral impulses add in the intended direction.

Parameter or scale variation

Four passes at fixed standoff

Four servicing satellites make sequential passes beside a 20-kilogram cooperative target at a nominal magnet-to-fixture gap of 0.25 meters. Each satellite applies a mean lateral force of 10 millinewtons for 2 seconds, with consecutive pulses beginning 60 seconds apart. The planner aligns all four impulses with the same direction in the target's local orbital frame and propagates the resulting trajectory to the predicted encounter. The four pulses provide a nominal cumulative velocity change of 4 millimeters per second.

Combination with existing systems

Secondary tracking with laser retroreflectors

A ring of corner-cube retroreflectors surrounds the target's magnetic coupling fixture, and each servicing satellite carries a scanning laser rangefinder. The rangefinder measures line of sight and distance to the ring during approach, and the navigation filter combines these measurements with inertial data. Each satellite uses the resulting relative position estimate to hold the commanded gap during its assigned pulse. The encounter planner uses an independent post-pass range track to update the target trajectory before releasing the next satellite for its pass.

Impulse control with a force sensor

A three-axis strain-gauge force sensor mounts between each electromagnet assembly and its satellite structure. The controller compensates the measured force for the assembly's inertial load using spacecraft accelerometer readings, then rotates the force vector into a common orbital frame using the attitude estimate. It integrates the opposite of the measured magnetic force to estimate the impulse delivered to the target and ends the pulse when the commanded lateral impulse reaches its setpoint. Each satellite reports its delivered impulse to the planner for use in the remaining passes.

Automated or data-driven variant

Feedback from measured deflection impulses

A navigation filter estimates the target's relative position and velocity from camera and range measurements collected before and after each magnetic pass. The estimator fits the velocity step across the pulse while accounting for the predicted unforced relative motion. A guidance computer subtracts the measured impulse from the requested cumulative impulse and redistributes the remainder among the satellites still scheduled to act. Each satellite receives updated pulse commands bounded by its available force and the permitted approach geometry.

Specific version of a part

Allocate thrust from live measurements

A controller updates the target state from relative navigation measurements and recomputes the required change in velocity after each control interval. It allocates the next thrust commands using current actuator limits and ends the maneuver when the updated encounter estimate meets the clearance threshold.

Propagate radar tracked orbits

A tracking processor fits position and velocity estimates from radar range, range rate, and angle measurements. It propagates both orbits to the time of closest approach and uses the position uncertainty and combined physical radii to estimate collision probability.

Plan staged ion beam passes

A planner assigns successive passes to satellites fitted with gridded ion sources and beam neutralizers. It calculates the duration and pointing of each pass from the target mass estimate, beam momentum flux, and required cumulative change in velocity.

Plan magnetic gradient pulses

A planner assigns close passes to satellites fitted with current driven coils for a target carrying a characterized permanent magnetic dipole. It uses the measured target attitude and the coil field gradient to estimate the force and select the current, direction, and duration of each pulse.

Execute time tagged beam commands

A ground controller uploads each satellite's commanded attitude, beam current, and start and stop times. Each satellite checks relative range and pointing before energizing its ion source and reports beam current and pointing telemetry after the pass.

Section 3 · quoted from USPTO records

Other work

Passages reproduced word for word from two earlier-published U.S. patent documents, placed beside the language of claim 1. No characterization is offered. Each passage is marked A or B for the document it comes from; ¶ numbers are the paragraph numbers in the USPTO’s published full text of that document.

Document AUS 2023/0188203 A1
Published
Jun 15, 2023
Filed
Dec 13, 2022
Class
H04B 7/18519
Document BUS 11,780,612 B1
Published
Oct 10, 2023
Filed
Sep 23, 2020
Class
B64G 1/24
Claim 1
Document A
Document B
1.1identifying a predicted collision between space objects;
The method S100 further includes: computing a probability of collision between the first satellite and a second satellite based on the first orbital trajectory and the second orbital trajectory in Block S130; and, in response to identifying the first satellite as maneuverable based on the first set of satellite characteristics, in response to identifying the second satellite as maneuverable based on the second set of satellite characteristics, and in response to the probabili
A · US 2023/0188203 A1 · ¶ 11
The Conjunction Assessment Supplier (CAS) 290 uses information from supplemental data suppliers (SSAs) and S3s 260 to identify potential conjunctions, which are instances where two or more resident space objects (RSOs) approach within a hazardous distance of each other.
B · US 11,780,612 B1 · ¶ 30
1.2determining a collaborative deflection strategy for deflecting at least one of the space objects to avoid the predicted collision, the collaborative deflection strategy including deflections by a plurality of satellites equipped with respective electromagnetic deflection modules; and
In another example, the computer system can generate cooperative avoidance plans, such that each operator can select any of the presented avoidance maneuvers without conflicting with an avoidance maneuver presented to the other operator.
A · US 2023/0188203 A1 · ¶ 19
1.3controlling the plurality of satellites to deflect the at least one of the space objects in accordance with the collaborative deflection strategy.
Thus, in this implementation, the computer system can autonomously execute avoidance maneuvers for both satellites involved in a conjunction event while abiding by agreement-related constraints, maneuverability constraints, and collision constraints without involvement of satellite operators.
A · US 2023/0188203 A1 · ¶ 68

An empty cell means only that no passage was reproduced there.

Statements in these documents
This invention relates generally to the field of satellite operation and more specifically to a new and useful automated method for orbital conjunction assessment and collision avoidance in the field of satellite operation.
A · US 2023/0188203 A1 · ¶ 2
However, this system is entirely manual, difficult to coordinate, and does not scale.
B · US 11,780,612 B1 · ¶ 6
As ever larger numbers of spacecraft seek to make use of Earth's limited orbital volume in increasingly dense orbital regimes, greater coordination becomes necessary to ensure these spacecraft are able to operate safely while avoiding physical collisions, radio-frequency interference, and other hazards.
B · US 11,780,612 B1 · ¶ 8
Cite aspatent.fyi, US 2026/0356500 A1, claim 1, first published 2026-11-20T02:22:52-05:00, https://patent.fyi/US20260356500/, SHA-256 a29096497073bbac72040c4f5cf2a3ca60d7ed9d9cf3f67015ca81843b7bc502
First published
Permanent addresshttps://patent.fyi/US20260356500/
Content fingerprint (SHA-256)a29096497073bbac72040c4f5cf2a3ca60d7ed9d9cf3f67015ca81843b7bc502
Methodv2026-11-18.2 · automated, not reviewed by a person
Correctionscorrections@patent.fyi