Two cargo companies can still share a launch system. The latest Cygnus and Dragon updates offer a concrete way to see the distinction.
## What happened
NASA reported that Northrop Grumman’s Cygnus XL left the International Space Station on October 9, 2026, after a cargo-delivery stay. NASA’s earlier departure update identifies the flight as CRS-24 and states that it launched on April 11 aboard a SpaceX Falcon 9. [1][2]
Separately, NASA’s October 7 advisory targets October 13 for SpaceX CRS-35: a Dragon spacecraft launching aboard Falcon 9. This remains a scheduled mission, not a completed launch. NASA’s mission overview repeats that vehicle assignment. [3][4]
## The connection: distinguish the roles
The two source-backed paths are Northrop Grumman → Cygnus XL / CRS-24 → launch by SpaceX Falcon 9, and SpaceX → Dragon / CRS-35 → planned launch by SpaceX Falcon 9. The first describes a past launch; the second describes a future assignment. They do not identify the same individual rocket or prove that both missions face the same risk today. [2][3]
NASA also identifies Space Launch Complex 40 at Cape Canaveral Space Force Station for both the April launch and the planned October flight. That is another shared layer in these two paths, not evidence that every mission of either provider must use that site. [2][4]
## Orbion analysis
Counting cargo providers answers one question: who delivers the cargo service? Tracing the launch role answers another: which underlying transport system is used to reach orbit?
For these two missions, the launch-vehicle family is shared despite different cargo spacecraft and providers. Supplier diversity at one layer therefore does not, by itself, demonstrate independence at another. This is a bounded inference from the reported mission configurations, not a quantified concentration score or a claim of exclusive dependence. [2][3][4]
A hypothetical interruption affecting a shared launch family could matter to multiple customers that plan to use it. Whether a particular mission would actually be delayed depends on timing, inventory, alternatives, integration work and contractual arrangements. None of those effects is established merely by drawing the shared connection.
The distinction matters when assessing options: two proposals may differ at the customer-facing level while relying on a common underlying capability. A useful comparison identifies the specific shared service, the period of exposure and the evidence for a feasible alternative.
## Challenge and limitations
Sharing Falcon 9 does not show that NASA’s cargo strategy is ineffective. Different spacecraft can still provide useful diversity in their own systems and operations. This two-mission comparison is not a census of station supply routes and cannot establish the probability or consequence of a future interruption.
The four opened pages are NASA program reporting, treated as one institutional source lineage, not four independent confirmations. Contracts, alternate-vehicle readiness and switching times were not inspected. A later change to the CRS-35 vehicle assignment would require revision of that path.
The departure updates also give different planned Cygnus deorbit dates: October 11 in the earlier post and October 12 in the later post. Neither planned date is a completed-reentry observation. That difference is retained rather than silently converted into a settled event. It is not needed for the launch-system inference. [1][2]
## The decision question
When comparing suppliers, ask: “Do these alternatives diversify the capability I need, or do they share a critical service underneath?” Then request evidence for substitution time, compatible capacity and the specific failure the alternative is intended to cover.
That is the analytical value of connecting the news: not another list of launches, but a better question about how the system works.