The Gap Nobody Talks About During Launch Planning
A typical university CubeSat mission runs two to four years from proposal to launch. Teams focus on the hard problems: mission design, power budgets, communication link margins, payload integration, launch vehicle selection. Conjunction screening gets treated as something that happens "after launch" — a box to check, not a capability to plan for.
Then the satellite reaches orbit. The Space-Track CDM (Conjunction Data Message) feed starts generating alerts. And the team realizes they have raw probability figures, object IDs, and miss distances — but no way to interpret them. Is a 1-in-10,000 collision probability worth a maneuver? Which conjunction events are actionable vs. noise? What does the debris population in their orbital shell actually look like right now?
Legacy SSA vendors will answer all of these questions. For $30,000 per year. For a program that spent $150,000 building the satellite.
What Happens When You Skip Conjunction Screening
The honest answer: most of the time, nothing. LEO is big and most satellites complete their missions without experiencing a high-risk conjunction. The Space-Track CDM feed will catch the most dangerous events. If you're careful about which alerts you act on, you can get by.
But "most of the time" isn't the same as "low risk." Three failure modes are worth understanding:
Debris field exposure. When a breakup event occurs in the same orbital shell as your satellite — like the Starlink 34343 fragmentation in early 2025 — the debris population shifts suddenly. Raw CDM data tells you about individual conjunction pairs. It doesn't tell you that the overall debris density around your orbit just increased by 15% in the last 48 hours, or that three new fragments from the breakup are now in similar orbits. That contextual analysis is what conjunction screening provides.
FCC licensing compliance. The FCC's experimental license framework requires applicants to address orbital debris mitigation — including a credible plan for monitoring conjunction risk and executing avoidance maneuvers when warranted. A program that can't demonstrate it has access to conjunction data may face scrutiny during license renewals. With the FCC increasingly scrutinizing small satellite debris compliance, "we rely on the public CDM feed and manually check it when we remember" is not a defensible answer.
Insurance and liability exposure. University programs carrying mission insurance are increasingly asked to document their conjunction monitoring approach. A satellite without any conjunction screening coverage is a harder underwriting case. As the orbital debris liability framework evolves — and it is evolving — the absence of systematic monitoring creates institutional exposure, not just technical risk.
"Raw CDM data tells you about individual conjunction pairs. It doesn't tell you the overall debris density around your orbit just increased 15% in 48 hours."
Three University Programs That Illustrate the Problem
The conjunction screening gap isn't hypothetical. It shows up repeatedly across programs of different sizes and missions.
KUbeSat-1 — University of Kansas
Launched in July 2024 via NASA's ELaNa 43 mission, KUbeSat-1 marked the University of Kansas's first orbiting satellite. The mission demonstrated that mid-tier universities can reach orbit through NASA's CubeSat Launch Initiative — which provides free launches for qualifying educational programs. What CLSI doesn't provide is post-launch conjunction monitoring. Teams in the ELaNa program rely on Space-Track's public CDM feed for conjunction data, with no built-in analysis layer. For a first mission with no prior operations experience, interpreting raw conjunction probabilities without context is exactly the kind of operational gap that can lead to missed warnings.
AlsaceSat — University of Strasbourg
AlsaceSat participated in ESA's "Fly Your Satellite" Design Booster program in late 2024, receiving structured training across all satellite subsystems — including legal and regulatory aspects of CubeSat missions. ESA's training program specifically covers debris mitigation obligations under the IADC guidelines and European Space Agency requirements. Yet the training stops at design guidance. Post-launch operational monitoring — continuous conjunction screening, real-time alerts, risk assessment — requires tools that the program budget typically doesn't include. AlsaceSat is representative of a pattern across European university programs: well-trained teams, under-resourced for operational monitoring.
Virginia Tech CubeSat Research (Grad Programs)
Graduate research programs at Virginia Tech have developed sophisticated orbit determination and debris conjunction analysis software — including work on sigma-point propagation for debris cloud dispersion and multi-objective evolutionary algorithms for trajectory optimization. This is serious SSA research. But research-grade conjunction analysis tools built for academic study aren't the same as production operational monitoring. The irony: programs deep in conjunction analysis research are subject to the same gap as programs that don't think about the problem at all. Building the tools is not the same as running them continuously against a live catalog.
What Conjunction Screening Actually Requires for a CubeSat
University programs don't need the full suite that government agencies and large commercial operators use. They need a specific subset of capabilities — and understanding what that subset is helps cut through the vendor pricing confusion.
| Capability | What It Does | Clearwatch | Legacy Vendors |
|---|---|---|---|
| TLE-based conjunction screening | Monitor your satellite against the full tracked catalog using current TLE data | ✓ Included | ✓ Core feature |
| Plain-language risk summary | AI-assisted assessment of what each conjunction event means operationally | ✓ Included | Analyst add-on |
| Debris field context | Orbital environment overview — breakup events, density trends in your shell | ✓ Included | Enterprise tier |
| Historical event catalog | Full conjunction history for your satellite and nearby objects | ✓ Included | Varies by plan |
| Documentation export | Monitoring records for FCC compliance and insurance documentation | ✓ Included | ✓ Included |
| Maneuver planning | Precision collision avoidance maneuver computation | Not required for most CubeSats without propulsion | Core feature |
| Annual cost | $1,188/year | $30,000+/year |
The maneuver planning gap is worth acknowledging directly: most university CubeSats don't have propulsion systems. If your satellite can't maneuver, precision maneuver planning is irrelevant. What you actually need is awareness — knowing when a conjunction is high-risk, understanding the orbital environment, having documentation that you're monitoring. That's a fundamentally different capability profile, and legacy vendors price their maneuver planning capability into every tier.
The FCC Compliance Angle
The FCC's experimental license framework for CubeSats — historically the primary licensing path for university programs — requires applicants to submit an orbital debris mitigation plan. The FCC has become increasingly specific about what that plan needs to contain, particularly as the debris population grows and the agency faces pressure to enforce compliance more actively.
A credible debris mitigation plan includes: a description of how the operator will monitor conjunction risk during operations, what threshold triggers a response, and what response options are available given the satellite's capabilities. For a satellite without propulsion, the response options are limited — but the monitoring requirement remains.
Having documented, systematic conjunction monitoring matters. Not because the FCC is currently auditing every university program — it's not. But because the direction of regulatory enforcement is toward accountability, and programs that have been monitoring and can demonstrate it are in a categorically different position than programs that haven't.
"Legacy vendors price maneuver planning capability into every tier. But most university CubeSats can't maneuver — so you're paying for something you can never use."
What Clearwatch Costs for a University Program
The full platform is $99/month. That's $1,188 per year.
For context: that's 4% of the annual cost of a legacy SSA contract. It's less than most university satellite programs spend on a single component. It fits comfortably within the operational budget line of a NASA ELaNa mission or an ESA Fly Your Satellite program.
What you get: continuous TLE-based conjunction screening against the full tracked catalog, AI-assisted plain-language risk summaries for every flagged event, orbital environment context including debris field updates, full historical event catalog, and the monitoring documentation trail that FCC compliance and insurance conversations require.
What you don't get: precision maneuver planning, high-cadence sensor fusion from proprietary radar networks, or dedicated human analysts. If your program needs those capabilities — because you operate a propulsive spacecraft and need maneuver computation, or because you have regulatory requirements that mandate sensor-fused tracking — legacy vendors exist for that reason.
But for the majority of university CubeSat programs, the capability gap between Clearwatch and a $30K enterprise contract is a gap you will never encounter in operations.
Getting Started
If your program has a satellite in orbit, or is preparing for launch, setting up monitoring takes minutes. The platform requires your satellite's NORAD ID — available from Space-Track after your satellite is catalogued, typically within days of deployment. Once you have the NORAD ID, the conjunction history and current alert status are immediately available.
If you're in pre-launch planning, Clearwatch is also useful for understanding the orbital environment you're launching into — reviewing conjunction activity in your target altitude band, tracking recent debris field changes, and building the monitoring documentation you'll need for FCC and insurance processes.
University programs get the same platform as commercial operators. The price is the same. The data is the same. The gap between what legacy vendors charge and what conjunction monitoring actually costs is not a quality difference — it's a market structure that never adapted to the scale of the modern CubeSat era.