Why it happens:

Students see both acronyms as NASA ISS-related and assume the first program automatically equals the operational one. They then map the idea of “resupply” to the earliest acronym they remember, ignoring that COTS is explicitly a demonstration framework while CRS is explicitly operational resupply.

✓ Correct understanding:

COTS is a demonstration contract program that funded development and demonstration of commercial cargo/crew resupply capabilities. CRS is the follow-on operational program that funded routine commercial resupply missions to the ISS. So the cause-effect chain is: demonstration funding and milestones under COTS enabled capabilities like Dragon cargo deliveries, and later CRS enabled operational ISS resupply cadence.

How to avoid:

Use a two-step anchor: (1) Label COTS as “demonstration” and CRS as “operational.” (2) When you see “demonstration,” connect it to capability-building milestones (Dragon development and early cargo demonstrations). When you see “operational,” connect it to sustained ISS resupply missions.

Why it happens:

Students overgeneralize the reusability theme from later years and apply it backward to the first rocket they studied. They may also confuse “private liquid-fueled rocket to orbit” with “reusable rocket,” because both are major milestones but refer to different technical emphases.

✓ Correct understanding:

Falcon 1 is described as expendable. The reusability milestones emphasized in the knowledge base belong to Falcon 9 first-stage recovery and reflight (2012-2017). The correct cause-effect chain is: Falcon 1’s repeated failures and eventual success proved private liquid-fueled orbital capability, which then led to focus on Falcon 9, where reusability became a cost-reduction strategy.

How to avoid:

Separate “orbital capability proof” from “reusability strategy.” Treat Falcon 1 as the early testbed for reaching orbit (after failures), and treat Falcon 9 first-stage reusability as the later cost-reduction mechanism.

Why it happens:

Students hear “Star-” branding and assume it indicates one product line with different names. They then compress the relationship into identity: if Starlink exists, Starshield must be the same thing for military use, rather than a distinct military counterpart enabled by Starlink’s existence.

✓ Correct understanding:

Starlink is the satellite constellation providing global broadband and becomes the bulk of SpaceX income starting in 2019. Starshield is described as a military counterpart enabled by Starlink, not the same system. The correct cause-effect chain is: Starlink becomes operational and creates recurring revenue, which supports broader technology and business expansion, including development of Starshield.

How to avoid:

Use the “enabled by” relationship. When you see Starshield, explicitly think “military counterpart enabled by Starlink,” not “identical system.”

Why it happens:

Students anchor on the earliest rocket name they remember (Falcon 1) and then apply the “three boosters” idea from Falcon Heavy without checking which booster family is used. They may also confuse “three rockets” with “three Falcon 1” due to a superficial similarity in naming rather than the explicit “Falcon 9-derived boosters” detail.

✓ Correct understanding:

Falcon Heavy uses three Falcon 9-derived boosters, not Falcon 1 rockets. The correct conceptual link is: Falcon 9’s booster technology and architecture enable Falcon Heavy’s heavy-lift configuration. Falcon 1 is an earlier expendable testbed, and its role is not the basis for Falcon Heavy’s booster selection in the knowledge base.

How to avoid:

When you see Falcon Heavy, immediately recall the dependency: “Falcon 9-derived boosters.” Do not reuse Falcon 1 as the default booster family.

Why it happens:

Students compress multiple milestones into one because both involve the same hardware returning to Earth. They may also treat “reflight” as a synonym for “landing,” ignoring that reflight requires refurbishment and another launch attempt after the landing.

✓ Correct understanding:

The knowledge base distinguishes two milestones: (1) first successful landing of an orbital-class rocket’s first stage occurred in December 2015, and (2) first reflight of an orbital-class booster occurred in 2017. The correct cause-effect chain is: successful landings and recovery architecture created the technical foundation, and then reflight milestones followed once the system could be reused operationally.

How to avoid:

Use a milestone checklist: landing means “recover and touch down,” while reflight means “launch again after recovery.” Always map each term to its required steps.

Why it happens:

Students see a mission failure and then connect it to the most prominent theme (reusability) without checking the described mechanism. They also may assume that because SpaceX was working on recovery technology, any later failure must be related to that same subsystem.

✓ Correct understanding:

The knowledge base describes a specific failure mechanism for CRS-7: a failed steel strut caused a helium pressure vessel breach, helium escaped into a low-pressure propellant tank, and that triggered the failure sequence. The correct reasoning chain is not “reusability caused CRS-7 failure,” but rather: specific hardware/pressurization failure mechanism caused the mission failure, followed by troubleshooting before returning to flight.

How to avoid:

When analyzing failures, force yourself to cite the mechanism. Do not substitute a broad theme (like reusability) for the specific described cause-effect chain.

Why it happens:

Students remember a “protest to GAO” story and then connect it to the most famous later SpaceX outcome (reusability and cost reduction). This is a timeline compression error: they treat one regulatory event as if it directly produced the later technical program, skipping the intermediate program creation (COTS).

✓ Correct understanding:

The knowledge base cause-effect chain is: NASA withdrew a sole-source contract after SpaceX protested to the GAO, and NASA formed the COTS program. COTS then enabled demonstration funding and milestones that later supported capabilities like Dragon cargo resupply. Reusability milestones are driven by landing recovery architecture and the engineering approach, not by the GAO protest event directly.

How to avoid:

Practice “immediate effect first.” Identify the direct next step in the chain (COTS formation), then only later connect to downstream capabilities (Dragon and operational cadence), and separately connect reusability to landing recovery architecture.