Satellite Close Approach Defense: COSMOS 2612 and ICEYE X36 Encounter Analysis
Summary
The speaker details the orbital mechanics and engineering challenges of satellite close approach defense, citing the October 2026 encounter between Russian satellite COSMOS 2612 and ICEYE X36. They argue that public tracking data lacks the precision to detect such maneuvers, necessitating onboard relative sensing and significant propellant reserves. The analysis highlights the regulatory conflicts between avoidance maneuvers and FCC disposal requirements, as well as the thin legal framework governing liability and export controls for such technologies.
Episode sections
- 0:00 – 0:59
Introduction and Encounter Overview
The speaker introduces the engineering requirements for satellite close approach defense, citing a 5-10 m/s reserve and precise navigation. They describe the October 2026 encounter between Russian satellite COSMOS 2612 and ICEYE X36, noting the closure from 400 km to 500 meters.
- 0:59 – 2:18
Propellant Budget and Public Tracking Limitations
The speaker argues that a radar satellite operator cannot match the propellant budget of an attacker (67-117 m/s). They state that a 5-10 m/s reserve only buys 85-170 km of separation, which is insufficient against the ~10 km standoff states maintain. Public tracking data has too much uncertainty (1.9 km) to detect such close approaches.
- 2:18 – 3:57
Detailed Timeline of COSMOS 2612 Maneuvers
The speaker details the multi-week approach of COSMOS 2612 to ICEYE X36 between September 30 and October 19, 2026. The satellite raised its orbit, descended to match altitude, closed from 480 km to 3 km, held station within 500 meters, and then departed.
- 3:57 – 6:15
First-Order Orbital Mechanics Calculations
The speaker presents calculations showing that a 47.8 km descent costs ~26 m/s and a 0.88-degree plane change costs ~117 m/s. They conclude that evasion must be in-plane and early, as plane changes are outside a defender's budget.
- 6:15 – 9:15
Navigation and Sensing Requirements
The speaker compares satellite tracking to submarine warfare, noting that public element sets with 1.9 km uncertainty are useless for a 0.5 km miss distance. They argue for onboard GNSS receivers and relative sensing (optical cameras, star trackers, passive radio) to detect uncooperative neighbors.
- 9:15 – 10:34
Regulatory and Propellant Trade-offs
The speaker discusses the conflict between avoidance reserves and disposal requirements under FCC rules (47 CFR 25.114D.14). They note that ICEYE X36 likely added propulsion capability, as earlier microsatellite designs avoided consumables.
- 10:34 – 13:13
Legal Liability and Export Controls
The speaker analyzes the thin legal framework for deliberate close approaches, citing the Outer Space Treaty and Liability Convention. They highlight that spent propellant may not qualify as 'damage' and that relative navigation hardware may be subject to US Munitions List or Commerce Control List export controls.
- 13:13 – 14:53
Open Questions and Future Risks
The speaker poses open questions about intent, the potential for repeat maneuvers by COSMOS 2611 and 2613 against ICEYE X37, and whether the FCC's traffic coordination system will screen for intent. They conclude by teasing the next episode on insurance implications.
Claims worth verifying
ICEYE X36 is a 90 kg synthetic aperture radar satellite registered in the United States.
Unidentified speaker (speaker_0) ·0:39
How to verify: SEC EDGAR filings for ICEYE A/S (if publicly traded) or US FCC licensing records for the satellite. For recent events, verify 2026-08-14 through 2026-11-14. Use another period only when the speaker explicitly names it.
Primary sourceThe COSMOS 2612 to ICEYE X36 encounter ran from October 15 to October 19, 2026.
Unidentified speaker (speaker_0) ·0:39
How to verify: Public orbital data providers (e.g., LeoLabs, CelesTrak) or news archives from October 2026. For recent events, verify 2026-08-14 through 2026-11-14. Use another period only when the speaker explicitly names it.
COSMOS 2612 spent about 67 m/s of delta-v after September 30 and 105-117 m/s in May to match the orbital plane.
Unidentified speaker (speaker_0) ·0:59
How to verify: Public orbital element sets (TLEs) from September and May 2026, analyzed for orbital plane changes. For recent events, verify 2026-08-14 through 2026-11-14. Use another period only when the speaker explicitly names it.
LeoLabs reported a closest approach distance of roughly 500 meters.
Unidentified speaker (speaker_0) ·1:19
How to verify: LeoLabs public reports or press releases from October 2026. For recent events, verify 2026-08-14 through 2026-11-14. Use another period only when the speaker explicitly names it.
Public element sets for small objects in this orbit carry in-track uncertainty near 1.9 km.
Unidentified speaker (speaker_0) ·1:19
How to verify: Analysis of public TLE covariance matrices for COSMOS 2612 and ICEYE X36 from October 2026. For recent events, verify 2026-08-14 through 2026-11-14. Use another period only when the speaker explicitly names it.
COSMOS 2612 was launched on a Soyuz 2.1B from Plesetsk in April 2026.
Unidentified speaker (speaker_0) ·2:37
How to verify: Roscosmos launch manifests or Space.com launch logs for April 2026. For recent events, verify 2026-08-14 through 2026-11-14. Use another period only when the speaker explicitly names it.
The FCC adopted a rule on September 29, 2022, requiring disposal within five years for satellites launched after September 29, 2024.
Unidentified speaker (speaker_0) ·9:34
How to verify: Federal Register or FCC.gov for the specific rulemaking document dated September 29, 2022. For recent events, verify 2026-08-14 through 2026-11-14. Use another period only when the speaker explicitly names it.
ICEYE announced a January 2026 agreement with a Ukrainian defense customer.
Unidentified speaker (speaker_0) ·12:53
How to verify: ICEYE A/S press releases or news archives from January 2026. For recent events, verify 2026-08-14 through 2026-11-14. Use another period only when the speaker explicitly names it.
COSMOS 2611 and COSMOS 2613 are converging on ICEYE X37 with orbital plane crossings expected around November 6 and November 15, 2026.
Unidentified speaker (speaker_0) ·13:32
How to verify: Public orbital data providers (e.g., LeoLabs, CelesTrak) for November 2026 conjunction predictions. For recent events, verify 2026-08-14 through 2026-11-14. Use another period only when the speaker explicitly names it.
The Department of Commerce is building a traffic coordination system for space under Space Policy Directive 3 of June 18, 2018.
Unidentified speaker (speaker_0) ·7:35
How to verify: White House or Department of Commerce archives for Space Policy Directive 3. For recent events, verify 2026-08-14 through 2026-11-14. Use another period only when the speaker explicitly names it.
Do your own research
- Verify the specific orbital parameters and maneuver timeline of COSMOS 2612 and ICEYE X36 using public TLEs or operator filings.
- Check FCC rule 47 CFR 25.114D.14 for current disposal requirements and any exemptions for maneuverable satellites.
- Review the Outer Space Treaty and Liability Convention for definitions of 'damage' and 'hazardous interference' in the context of propellant release.
- Assess export control classifications for relative navigation hardware under the US Munitions List (USML) and Commerce Control List (CCL).
- Research ICEYE's public disclosures regarding propulsion capabilities and collision avoidance protocols for their X-series satellites.
- Investigate potential conflicts of interest if the speaker has ties to satellite operators or defense contractors.
- Look for counter-arguments regarding the feasibility of passive radio sensing for detecting uncooperative neighbors.
- Check for any official statements from Roscosmos or ICEYE regarding the intent behind the COSMOS 2612 maneuver.
Full transcriptexpand
- 0:00
- Unidentified speaker (speaker_0): A radar satellite needs 5-10 meters per second of reserve, precise navigation, and onboard sensing to answer a Cosmos 2612-style close approach. Radar satellite close approach defense after Cosmos 2612. An ISI X36 executive summary: a radar imaging satellite needs
- 0:19
- Unidentified speaker (speaker_0): 5-10 meters per second of reserve. Onboard on board precise navigation and relative sensing to answer a close approach like Cosmos 2016. 2612. One that figure comes from first-order orbital mechanics applied to the October 2026 encounter, which the Russian satellite Cosmos 2612 closed from about 400 kilometers to roughly
- 0:39
- Unidentified speaker (speaker_0): 500 meters of ISI X-36, a 90 kilogram synthetic aperture radar satellite registered in the United States. 2. The encounter ran from October 15 to October 19, 2016. 2026. Public orbital elements show Cosmos 2612 spent about 67 meters per second of change in speed after September
- 0:59
- Unidentified speaker (speaker_0): 32 arrive, and about 105 to 117 meters per second in May to match the orbital plane of its target. 2. A radar satellite operator cannot Not match that budget. A reserve of 5 to 10 meters per second buys a separation of 85 to 150. 170 km per orbit after a coplanar lowering burn, which
- 1:19
- Unidentified speaker (speaker_0): exceeds the roughly 10 km standoff that states have generally kept, for propellant is half the answer. Public element sets for small objects in this orbit carry in track uncertainty near 1.9 km, which is nearly four times the distance Leo Labs reported at closest approach. To a satellite that depends on public tracking.
- 1:39
- Unidentified speaker (speaker_0): data cannot see an event of this size. It needs its own satellite navigation receiver, a way to sense a neighbor directly, and a software path that turns a detection into a burn within one orbit. The legal exposure follows the engineering. Operators licensed under 47 CFR 25.114D. 4D. 14 already
- 1:58
- Unidentified speaker (speaker_0): disclose collision avoidance capability, and the Liability Convention of 1900. 1972 assigns fault-based liability for damage in space. Neither text addresses a deliberate approach that causes no collision. Detailed findings what happened between Cosmos 2612 and ISI X36. Cosmos 2612 made a
- 2:18
- Unidentified speaker (speaker_0): controlled, multi-week approach to ISI X-36 between September 30 and October 19, 2026, and held positions. position within about 500 meters of the target on October 17 and 18. According to the commercial tracking firm Leo Labs, one the Russian satellite was one of six, Cosmos
- 2:37
- Unidentified speaker (speaker_0): 2609 through 2614, launched on a single Soyuz 2.1B from Plesitsk. April 2026, three public element sets show the approach began with phasing, not speed. Cosmos 2612 raised its orbit about 47 km on September 30,
- 2:57
- Unidentified speaker (speaker_0): descended 47.8 km on October 11 and 12 to match the target altitude, and closed from about 480 km to about 3 km on October 15 and 16, with burns of under 2 meters per second each. 2, it then held station behind the target on a loop about 1.5. 1.6 km tall. And on
- 3:17
- Unidentified speaker (speaker_0): October 18, it raised its orbit 2.3 km to leave. By October 19, it was 292 kilometers behind and drifting away at about 350 km per day, to the closest distance carries uncertainty. Leo Labs reported about 500 meters with high confidence. An independent reading of the public catalog
- 3:37
- Unidentified speaker (speaker_0): supports a range of roughly 100. 150 to 650 meters in the early hours of October 18, and a 25-meter figure that circulated cannot be derived from public data at all. 2-3 ISI reported moving its own satellite and told the press its constellation architecture is designed for continuity. 2. The Pentagon declined. To comment, 4 how much
- 3:57
- Unidentified speaker (speaker_0): propellant does a radar satellite need to respond to a close approach? A radar imaging satellite needs a dedicated avoidance reserve of 5 to 10 meters per second, sized for a coplanar phasing burn instead of a plane change. These figures are the author's first-order calculation, using a circular orbit near 500 km,
- 4:17
- Unidentified speaker (speaker_0): an orbital speed of about 7.6 km per second, and a semi-major axis of about 6,871 km. kilometers. The altitude is an assumption drawn from published descriptions of the I-Sai constellation. 6. The calculation reproduces the Russian numbers, which is the reason to trust it.
- 4:36
- Unidentified speaker (UNKNOWN): A
- 4:36
- Unidentified speaker (speaker_0): two-burn altitude change of delta costs a total change in speed near V times Δ divided by twice the semi-major axis. For the 47.8 km descent, that gives about 26 meters per second, and public estimates put the real burn. near 27 to 28. 2. A plane change of 0.88 degrees costs about V times the angle
- 4:56
- Unidentified speaker (speaker_0): and radians, or about 117 meters per second, which sits at the top of the 105 to 117 meter per second range estimated for the May burns. 2 applied to the defender. The same equations give the exchange rate that matters. ISI lowered its satellite about 0.5 km on June 25 and 26, 2015. 2026, a maneuver
- 5:16
- Unidentified speaker (speaker_0): under 1 m per second, and the calculation puts that burn near 0, 3 meters per second. 2. A 5 meter per second reserve raises the altitude change to about 9 km. An altitude offset produces an along track drift of roughly 3 times times the offset per orbit, so a 9 km offset opens about 85 km per orbit,
- 5:36
- Unidentified speaker (speaker_0): and a 10 m per second reserve opens about 170 km. Plane changes lie outside any defender's budget. Moving the orbital plane by even 0.1 degree costs about 13 meters per second, and the attacker holds the geometry advantage because it has already matched the plane to within 0.002
- 5:56
- Unidentified speaker (speaker_0): degrees.2 evasion Invasion, therefore has to be in plane, early, and repeatable. Cosmos 2612 closed. at about 400 km per day with a 2.3 km altitude offset, which covers the last 3 km in about 11 minutes. A defender that waits for confirmation inside that range has minutes to
- 6:15
- Unidentified speaker (speaker_0): act, far less than the 95 minute orbit. Two in my years as a nuclear submarine Marine officer, the closest point of approach was a number the watch team computed continuously from bearings and range. ranges that each carried error. A plot whose error exceeded the predicted miss distance gave us nothing to act on, and we treated it as a contact of unknown
- 6:35
- Unidentified speaker (speaker_0): intent. A satellite operator reading public elements with a 1-9-kilometer in track covariance against a 0.5km miss distance holds the same plot.2 How accurately must a satellite know its own position and its neighbors? A satellite needs onboard position knowledge in the meter range and neighbor knowledge
- 6:55
- Unidentified speaker (speaker_0): within a few hundred meters to make an avoidance decision at these separations. Public element sets cannot supply either. Keep track's analysis put the in-track uncertainty for Cosmos 2612 near 1.9 km, Kilometers, and it found gaps in the public record of about 14 hours for Cosmos 2612. and about 8
- 7:15
- Unidentified speaker (speaker_0): hours for ISI X36 on October 17 and 18. During the closest approach to a dual frequency satellite navigation receiver gives the host satellite its own position independent of any catalog, the neighbor's position still comes from outside, which makes the quality of the conjunction data service the limit on what the operator can know. The Department of
- 7:35
- Unidentified speaker (speaker_0): Commerce is building the traffic coordination system for space under space. Policy Directive 3 of June 18, 2018, and its September 2025 pilot plan called for up to five commercial conjunction assessment screening providers and one independent data quality monitor. The pilot describes screening for collisions, not detection of a deliberate approach by an
- 7:55
- Unidentified speaker (speaker_0): object that stays outside collision thresholds. What onboard sensing detects an uncooperative neighbor? Onboard sensing for an uncooperative neighbor requires a sensor that reports relative bearing without help from the neighbor, and the practical candidates are a wide field optical camera, a star tracker run in a detection mode, and a passive radio
- 8:15
- Unidentified speaker (speaker_0): frequency receiver. This is the author's engineering assessment. No public document describes what sensing, if any, ISI X36 carries for this purpose. A star tracker or already images the sky many times per second. A tracker modified to report any moving point source inside a defined range would give bearing and bearing rate for a
- 8:35
- Unidentified speaker (speaker_0): neighbor inside a few kilometers, which is the range Cosmos 2612 occupied for about two days. Range then comes from the change in bearing as the host maneuvers, a technique the submarine force knows as target motion analysis. A passive receiver tuned to expected crosslink and telemetry bands adds a second line of evidence and
- 8:55
- Unidentified speaker (speaker_0): tells the operator whether the neighbor is transmitting. The mass cost is small against a 90 kilogram bus. The harder cost is software because a detection that does not reach an operator inside one orbit, which is about 95 minutes at this altitude, does not support a burn. Operators designing for this must write the detection threshold, the
- 9:15
- Unidentified speaker (speaker_0): escalation path, and the maneuver authority into the concept of operations before launch. Does the reserve compete with deorbit and mission life? An avoidance reserve competes directly with the disposal reserve and with orbit maintenance for a Sun's synchronous imaging satellite. The Federal Communications Commission adopted a rule on September 29,
- 9:34
- Unidentified speaker (speaker_0): 2022, requiring disposal within five years after mission end for satellite. satellites launched after September 29, 2024, and operators disclose their disposal plan and collision avoidance capability under 47 CFR 25.114 D14. A satellite that spends its reserve on a hostile approach may lack the propellant for compliant disposal.
- 9:54
- Unidentified speaker (speaker_0): An operator who carries an extra 5 to 10 meters per second must account for it in the debris disclosure and in the mass budget, and a satellite already built without it carries the shortfall for its life. The same reserve helps with ordinary conjunction avoidance, which is the argument for including it in a design that answers to investors
- 10:14
- Unidentified speaker (speaker_0): who see only the military threat as a cost. A 2024 overview of the early ISI micro satellite design described a bus that avoided consumables such as propellant, while X-36 changed its altitude in. 2026. 2. The operator has evidently added propulsion capability across generations. The public record does
- 10:34
- Unidentified speaker (speaker_0): not state its size. Legal and regulatory implications: the body of law on a deliberate close approach that causes no damage is thin, and the existing texts address collisions, licensing, and state responsibility, with no text on harassment of a commercial satellite. Article Roman 9 of the Outer Space Treaty of 1967
- 10:54
- Unidentified speaker (speaker_0): requires states to conduct activities with due regard for the corresponding interests of other states and to consult before activities that could cause harmful interference. 9 Article VI makes each state responsible for national space activities, including those of non-governmental entities and requires authorization and continuing supervision of private
- 11:14
- Unidentified speaker (speaker_0): operators. 9 liability is the second text. Article Roman III of the Convention on International Liability for Damage Caused by Space Objects of 1972 makes a launching state liable for damage caused elsewhere than on the surface of the Earth only if the damage is due to its fault. A near miss that causes loss of imaging capacity, fuel
- 11:33
- Unidentified speaker (speaker_0): expenditure, or a lost collection window may not qualify as damage under Article I. which speaks of loss of life, personal injury, and loss of or damage to property. Whether spent propellant is damage to property is a point no state has litigated. The operator's own obligations sit in licensing and export control. The Federal Communications
- 11:53
- Unidentified speaker (speaker_0): Commission requires an orbital debris showing under 47 CFR 25.114D. 14. And an operator who adds an avoidance reserve and onboard sensor. sensing should update that showing. 7 relative navigation hardware and autonomy software for proximity operations may fall under Category Roman 15 of the United States Munitions List at 22 CFR.
- 12:13
- Unidentified speaker (speaker_0): 121.1, or under Export Control Classification No. 9, a 515 on the Commerce Control List at 15 CFR Part 774. Supplement No. 1. And a classification review belongs in the design phase. before any foreign supplier or customer sees the specification. Two customer contracts add a third layer.
- 12:33
- Unidentified speaker (speaker_0): An operator that sells imagery to a government customer in a conflict zone should expect that customer to ask for avoidance capability, and an operator that promises it assumes a performance obligation that a deliberate approach can test. The January 2026 ISI agreement with a Ukrainian defense. customer, which the operator
- 12:53
- Unidentified speaker (speaker_0): announced, is the type of contract that draws this attention. Four open questions: What was Cosmos 2612 doing? Leo Labs states that its observations do not establish hostile intent, and an independent analyst in the same coverage called the event the first low Earth orbit rendezvous of two active satellites where one owner had not
- 13:13
- Unidentified speaker (speaker_0): agreed to it. Three 3. of the answer sets were. whether insurers and licensing agencies treat the event as harassment, inspection, or preparation for attack, will the same cohort repeat the maneuver? Cosmos 2611 and Cosmos 2613 are converging on ISI X-37, the launch sibling of X-36,
- 13:32
- Unidentified speaker (speaker_0): with orbital plane crossings expected around November 6 and November 15, 2026, to those Do dates. give operators a test of whether any lessons from October reach the Burn Authority and the detection software? Does the traffic coordination system for space screen for intent? The September 2025 pilot plan describes conjunction screening and
- 13:52
- Unidentified speaker (speaker_0): data quality monitoring, and the public record does not show a service that flags a sustained approach inside a collision threshold. 5. Who pays for the reserve? The Federal Communications Commission disclosure rule asks for a collision avoidance plan and does not set a minimum reserve. Seven operators with fixed mass budgets face a choice between payload,
- 14:12
- Unidentified speaker (speaker_0): propellant, and sensing that no rule resolves. Does spent propellant count as damage? The liability convention defines damage by loss of life, injury, and property, and no state has claimed compensation for a maneuver forced by a non-damaging approach. The next piece in the series examines how launch and an orbit insurance policies treat an
- 14:32
- Unidentified speaker (speaker_0): intentional proximity operation and whether the war exclusions in standard satellite. Policies apply when the approach causes no collision but forces a burn that shortens mission life. Interested in analysis about the intersection of tech, policy, and the law? Check out my Substack channel, HTTPS/slash https slash slash Thanovation thainovation Attorney at Substack. orny com
- 14:51
- Unidentified speaker (speaker_0): slash.