Apollo 11system modelDashboardMissionOperationsTimelineFunctionsPhysicalBudgetsRequirementsCostReview notesNavigator

Apollo 11 launch, 16 July 1969 (NASA, public domain)

Physical architecture¶

The hardware that flew Apollo 11: the Saturn V launch vehicle, the Command and Service Module Columbia, the Lunar Module Eagle and the spacesuits. The page tells two stories. The type breakdown describes the designs as a library: what each kind of vehicle is made of, and its dry mass. The mission configuration shows how specific vehicles from that library are assembled for this one flight. The page then lists the components as a plain manifest, with focused tables for the engines and the propulsive stages; the interfaces, grouped by the boundary they cross; and the program's serial-numbered vehicles. It is for engineers who need to find a component, its key parameters or its interfaces. Mass, propulsion, power and reliability budgets are on Technical budgets.

19
hardware designs (part defs)
66
serial-numbered vehicles in the program
8
port definitions
8
interface definitions
10
interface connections
32
astronauts

System block diagram¶

Product System block diagram
The assembled Apollo 11 mission system as nested blocks (vehicle → module → stage), with the interface connections drawn between the blocks they join.
Use it to see at a glance what the mission system is made of and which elements exchange loads, power, data or propellant with each other.
flowchart TB
  subgraph nlaunchVehicle["launchVehicle : SA-506"]
    nlaunchVehicle_instrumentUnit["instrumentUnit : SaturnVInstrumentUnit"]
    nlaunchVehicle_stage1["stage1 : S-IC"]
    nlaunchVehicle_stage2["stage2 : S-II"]
    nlaunchVehicle_stage3["stage3 : S-IVB"]
  end
  subgraph nspacecraft["spacecraft : ApolloSpacecraft"]
    subgraph nspacecraft_csm["csm : CSM-107"]
      nspacecraft_csm_commandModule["commandModule : ApolloCommandModule"]
      nspacecraft_csm_serviceModule["serviceModule : ApolloServiceModule"]
    end
    nspacecraft_launchEscapeSystem["launchEscapeSystem : ApolloLaunchEscapeSystem"]
    subgraph nspacecraft_lm["lm : LM-5"]
      nspacecraft_lm_lunarModuleAscentStage["lunarModuleAscentStage : LunarModuleAscentStage"]
      nspacecraft_lm_lunarModuleDescentStage["lunarModuleDescentStage : LunarModuleDescentStage"]
    end
    nspacecraft_spacecraftLMAdapter["spacecraftLMAdapter : ApolloSpacecraftLMAdapter"]
  end
  subgraph nspaceSuits["spaceSuits : ExtravehicularMobilityUnit"]
    nspaceSuits_plss["plss : PortableLifeSupportSystem"]
    nspaceSuits_psa["psa : PressureSuiteAssembly"]
  end
  nlaunchVehicle_instrumentUnit <-->|"lvToPayload"| nspacecraft_spacecraftLMAdapter
  nspacecraft_csm_serviceModule <-->|"cmSMUmbilical"| nspacecraft_csm_commandModule
  nspacecraft_lm_lunarModuleDescentStage <-->|"lmInterstage"| nspacecraft_lm_lunarModuleAscentStage
  nspacecraft_spacecraftLMAdapter <-->|"StagingInterface"| nspacecraft_csm_serviceModule
  nspacecraft_csm_commandModule <-->|"cmLMDocking"| nspacecraft_lm_lunarModuleAscentStage
  nspacecraft_csm_commandModule <-->|"lesConnection"| nspacecraft_launchEscapeSystem
  nspaceSuits_plss <-->|"suitToPLSSUmbilical"| nspaceSuits_psa
  nlaunchVehicle_instrumentUnit <-->|"iuToStage3"| nlaunchVehicle_stage3
  nlaunchVehicle_stage1 <-->|"stage1ToStage2"| nlaunchVehicle_stage2
  nlaunchVehicle_stage2 <-->|"stage2ToStage3"| nlaunchVehicle_stage3

The mission system assembles 3 elements: launchVehicle (the individual SA-506), spacecraft (design ApolloSpacecraft), spaceSuits (design ExtravehicularMobilityUnit). Engines are omitted from the diagram (they declare no ports); the stage blocks contain them, see the type breakdown below. Only lvToPayload is declared by the mission system itself; the other 9 connections come with the vehicle designs.

What the hardware looks like¶

The model holds no geometry: apart from SaturnV::height, the technical layer gives no dimensions, shapes or layout. The NASA illustrations below show the arrangement the blocks above stand for. They are illustrative only and are not drawn from the model.

Schematic of the Saturn V launch vehicle with the Apollo spacecraft on top
The Saturn V stack: S-IC, S-II and S-IVB stages, the instrument unit, and the Apollo spacecraft with its launch escape tower. NASA, public domain.
Cutaway of the Apollo spacecraft: launch escape system, command module, service module, and the lunar module inside its adapter
The Apollo spacecraft as launched: launch escape system, command module, service module, and the lunar module folded inside the spacecraft-LM adapter. NASA, public domain.
Diagram of the Apollo lunar module, ascent stage above descent stage
The lunar module: the ascent stage (crew cabin and ascent engine) on the descent stage (landing gear, descent engine and propellant). NASA/MSFC, public domain.

Type breakdown (library)¶

Product Type breakdown (library)
The designs (part definitions) as a library of types, broken down like a work breakdown structure: SaturnV, ApolloSpacecraft and ExtravehicularMobilityUnit are independent work items, each shown with the types it is made of and its dry mass. Propellants and other expendables are left out.
Use it to see what each design contains and what it weighs empty, independent of how many of each a mission uses. The mission configuration below shows how many of each fly.
  • SaturnV · 188,650 kg dry (sum of parts) (12)
    • instrumentUnit : SaturnVInstrumentUnit · 1,950 kg dry (dryMass)
    • stage1 : S-IC · 137,000 kg dry (dryMass) (5)
      • engine1 : F-1
      • engine2 : F-1
      • engine3 : F-1
      • engine4 : F-1
      • engine5 : F-1
    • stage2 : S-II · 36,200 kg dry (dryMass) (5)
      • engine1 : J-2
      • engine2 : J-2
      • engine3 : J-2
      • engine4 : J-2
      • engine5 : J-2
    • stage3 : S-IVB · 13,500 kg dry (dryMass) (1)
      • engine : J-2
  • ApolloSpacecraft · 22,330 kg dry (sum of parts) (6)
    • commandServiceModule : ApolloCommandServiceModule · 12,000 kg dry (sum of parts) (2)
      • commandModule : ApolloCommandModule · 5,840 kg dry (mass (no propellant stated))
      • serviceModule : ApolloServiceModule · 6,160 kg dry (dryMass)
    • launchEscapeSystem : ApolloLaunchEscapeSystem · 4,170 kg dry (mass (no propellant stated))
    • lunarModule : ApolloLunarModule · 4,320 kg dry (sum of parts) (2)
      • lunarModuleAscentStage : LunarModuleAscentStage · 2,220 kg dry (dryMass)
      • lunarModuleDescentStage : LunarModuleDescentStage · 2,100 kg dry (dryMass)
    • spacecraftLMAdapter : ApolloSpacecraftLMAdapter · 1,840 kg dry (mass (no propellant stated))
  • ExtravehicularMobilityUnit · 83 kg dry (massOnEarth) (2)
    • plss : PortableLifeSupportSystem
    • psa : PressureSuiteAssembly
Dry mass per work item, one unit of each design
Work item (design) Dry mass [kg] From Parts without a dry mass
SaturnV 188,650 sum of parts none
ApolloSpacecraft 22,330 sum of parts none
ExtravehicularMobilityUnit 83 massOnEarth none

A design's dry mass is its dryMass; where it states only mass and no propellant (ApolloCommandModule, ApolloLaunchEscapeSystem, ApolloSpacecraftLMAdapter), that mass is counted as dry; so the launch escape system's solid rocket motors are counted in its figure. ExtravehicularMobilityUnit states only massOnEarth. A design that states none sums its parts. The engines (F-1, J-2) carry no mass of their own: they are inside their stage's dryMass. Propellant loads are in the propulsive stages table, and the liftoff mass budget is on Technical budgets.

Mission configuration (instances)¶

Product Mission configuration (instances)
How Apollo11MissionSystem assembles the library types for this one flight: how many of each element it uses (the multiplicity in the model), which serial-numbered vehicle fills each slot, and the logical role each element plays.
Use it to see exactly what flies on Apollo 11, as opposed to what the designs could contain.
Element How many Design Serial-numbered vehicles Logical role Dry mass per unit [kg]
launchVehicle 1 SaturnV SA-506 LaunchSystem 188,650
spacecraft 1 ApolloSpacecraft csm : CSM-107, lm : LM-5 Spacecraft 22,330
spaceSuits 0..2 ExtravehicularMobilityUnit none (any unit of the design) EVASystem 83 
flowchart TB
  ms["Apollo11MissionSystem"]
  ms -->|"1"| nroot_launchVehicle["launchVehicle : SA-506 (design SaturnV)"]
  ms -->|"1"| nroot_spacecraft["spacecraft : ApolloSpacecraft"]
  nroot_spacecraft --> nroot_spacecraft_csm["csm : CSM-107 (design ApolloCommandServiceModule)"]
  nroot_spacecraft --> nroot_spacecraft_lm["lm : LM-5 (design ApolloLunarModule)"]
  ms -->|"0..2"| nroot_spaceSuits["spaceSuits : ExtravehicularMobilityUnit"]

With the upper bound of each multiplicity, the mission flies 1 × SaturnV, 1 × ApolloSpacecraft, 2 × ExtravehicularMobilityUnit: 211,146 kg of dry hardware, before propellant, crew and consumables.

How the model assembles the mission
  • spaceSuits[0..2] is a constituent system of the mission system, alongside launchVehicle and spacecraft, not part of the Lunar Module's payload. On the real flight, the two EVA suits went to the surface with Armstrong and Aldrin, in the Lunar Module. The multiplicity also allows a mission with no suits. No suit is serial-numbered: no individual realizes ExtravehicularMobilityUnit.
  • In the model the launch system is the launch vehicle alone: SaturnV specializes the logical component LaunchSystem, and ApolloSpacecraft specializes Spacecraft. Nothing but Apollo11MissionSystem holds the launch vehicle and the spacecraft together, so no element stands for the stack that is launched; they are joined only by lvToPayload.
What the technical layer leaves out
  • Ground systems. The technical layer has no ground system designs. The ground segment appears only as the 6 external systems of the mission context (CrawlerTransporter, LaunchControlCenter, MannedSpaceFlightNetwork, MissionControl, RecoveryForces, VehicleAssemblyBuilding), defined in ContextPackage with no parts or ports, though in the real program several of them, such as Launch Complex 39 and the crawler-transporters, were built for Apollo. See the mission context.
  • Program versus mission. No annotation in the designs or the vehicles (0 metadata) marks which items are shared across the Apollo program and which were built for Apollo 11 alone, beyond the split between the designs (shared by every mission) and the serial-numbered vehicles (one per flight).

Component register¶

Product Component register
A plain manifest of the hardware designs (part types): what each one is, what it is in the CoSMA architecture (hardware component, system, power provider or consumer, the logical component it realizes) and the designs it is part of. Physical properties are not repeated here: they are in the focused tables below, the type breakdown above and the budgets.
Use it to look up a component's role and where it is used; filter by typing a name or a role.
Component Role Realizes (logical) Part of Description
ApolloCommandModule hardware component, power consumer ApolloCommandServiceModule The conical crew cabin, control center, and reentry vehicle.
ApolloCommandServiceModule hardware component, power provider, power consumer ApolloSpacecraft The combined Command and Service Module (CSM), which functions as the primary spacecraft for lunar transit and Earth return.
ApolloLaunchEscapeSystem hardware component, power consumer ApolloSpacecraft A solid-fueled rocket tower mounted atop the Command Module to pull it away from the launch vehicle in an emergency.
ApolloLunarModule hardware component, power provider, power consumer ApolloSpacecraft The two-stage vehicle that performed the lunar landing and ascent.
ApolloServiceModule hardware component, power provider, power consumer, fuelled ApolloCommandServiceModule The primary support module for the Command Module, containing the main engine, power systems, and consumables.
ApolloSpacecraft system Spacecraft (a work item) The complete payload stack for the Apollo mission, including the CSM, LM, SLA, and Launch Escape System.
ApolloSpacecraftLMAdapter hardware component ApolloSpacecraft A conical structure that housed the Lunar Module during launch and connected the Apollo spacecraft to the Saturn V.
ExtravehicularMobilityUnit system EVASystem (a work item) The 'A7L' spacesuit, a self-contained personal spacecraft providing life support for lunar EVAs.
F-1 hardware component S-IC A single-chamber liquid-propellant rocket engine, the most powerful ever built, used in the S-IC first stage.
FuelledComponent (abstract) hardware component —
J-2 hardware component S-II, S-IVB A liquid-fuel cryogenic rocket engine used in the S-II and S-IVB stages, notable for its restart capability.
LunarModuleAscentStage hardware component, power provider, power consumer, fuelled ApolloLunarModule The upper portion of the Lunar Module, which served as the crew cabin and ascent vehicle to leave the lunar surface.
LunarModuleDescentStage hardware component, power provider, power consumer, fuelled ApolloLunarModule The lower portion of the Lunar Module, used for the powered landing and as a launch platform for the ascent stage.
MultistageRocket (abstract) system — An abstract representation of a rocket composed of multiple stages.
PortableLifeSupportSystem hardware component ExtravehicularMobilityUnit The 'backpack' containing oxygen, CO2 scrubbers, cooling water, and communications equipment.
PressureSuiteAssembly hardware component ExtravehicularMobilityUnit The main suit portion, providing pressure and mobility.
PropelledSpacecraft (abstract) hardware component, fuelled —
RocketEngine (abstract) hardware component — An abstract representation of a rocket engine, defining its core performance attributes.
RocketStage (abstract) hardware component, fuelled — An abstract representation of a single stage of a rocket, containing engines and propellant.
S-IC hardware component, fuelled SaturnV The first stage of the Saturn V, providing the initial ~7.7 million pounds of thrust for liftoff.
S-II hardware component, fuelled SaturnV The second stage of the Saturn V, providing massive thrust in the upper atmosphere and vacuum of space.
S-IVB hardware component, fuelled SaturnV The third stage of the Saturn V, responsible for the final push into Earth orbit and the critical Translunar Injection burn.
SaturnV system LaunchSystem (a work item) The three-stage, super heavy-lift launch vehicle used to send the Apollo spacecraft to the Moon.
SaturnVInstrumentUnit hardware component, power consumer SaturnV The 'brain' of the Saturn V, providing guidance and control during ascent.
Elements whose mass the model does not give
  • launchVehicle.instrumentUnit (SaturnVInstrumentUnit): instrumentUnit.mass has no value; it states only dryMass = 1,950 kg
  • spaceSuits (ExtravehicularMobilityUnit): spaceSuits.mass has no value (nor do its parts)

Engines and propulsive stages¶

Product Engines and propulsive stages
Two focused tables in place of property columns in the register: the engines of each propulsive stage with their thrust and specific impulse, and each propulsive stage's dry mass and nominal propellant load.
Use it to compare the propulsion elements and check the inputs of the Δv budget.
Engines
Stage Engine Engines Thrust per engine, sea level [kN] Thrust per engine, vacuum [kN] Total vacuum thrust [kN] Isp, vacuum [s]
S-IC F-1 5 6,770 7,770 38,850 304
S-II J-2 5 1,033 5,165 421
S-IVB J-2 1 1,033 1,033 421
ApolloServiceModule main engine (not modeled as a part) 1 91 91 314
LunarModuleAscentStage main engine (not modeled as a part) 1 16 16 311
LunarModuleDescentStage main engine (not modeled as a part) 1 45 45 305
Propulsive stages
Stage or module Dry mass [kg] Nominal propellant load [kg] Propellant fraction
S-IC 137,000 2,077,000 94%
S-II 36,200 443,000 92%
S-IVB 13,500 109,500 89%
ApolloServiceModule 6,160 18,440 75%
LunarModuleAscentStage 2,220 2,370 52%
LunarModuleDescentStage 2,100 8,250 80%

The propellant figures are nominal loads: the model gives one propellantMass per stage. A design would bound it instead, between the minimum the mission needs (plus its margin) and the tank capacity, with the flight load set just before launch. The model states neither bound; the propellant budget is on Technical budgets. The engines carry no mass of their own in the model (their mass is inside their stage's dryMass). Only the F-1 states a sea-level thrust.

Interface register¶

Product Interface register (ICD summary)
Every interface connection in the mission system, grouped by the boundary it crosses (inside a vehicle, between vehicles, between flight and ground), with what flows across it. The port and interface definitions behind the connections are collapsed at the end.
Use it to check what crosses a boundary between two elements and in which direction, as a starting point for an interface control document.

Within the launch vehicle (3 connections)

Connection Interface definition End 1 (component.port) End 2 (component.port) Flows (from end 1) Declared in
iuToStage3 GuidanceInterface SaturnVInstrumentUnit.stageControlPort S-IVB.controlPort ← telemetry (TelemetryData), → thrustCmds (CommandSignal), → power (ElectricalPower), → guidanceCmds (CommandSignal) SaturnV
stage1ToStage2 StagingInterface S-IC.upperStagePort S-II.lowerStagePort ↔ loads (StructuralLoad), → commands (CommandSignal) SaturnV
stage2ToStage3 StagingInterface S-II.upperStagePort S-IVB.lowerStagePort ↔ loads (StructuralLoad), → commands (CommandSignal) SaturnV

Within the spacecraft (5 connections)

Connection Interface definition End 1 (component.port) End 2 (component.port) Flows (from end 1) Declared in
(StagingInterface) StagingInterface ApolloSpacecraftLMAdapter.csmInterfacePort ApolloServiceModule.launchVehicleInterfacePort ↔ loads (StructuralLoad), → commands (CommandSignal) ApolloSpacecraft
cmLMDocking DockingInterface ApolloCommandModule.dockingPort LunarModuleAscentStage.dockingPort ↔ power (ElectricalPower), ↔ loads (StructuralLoad), ↔ data (TelemetryData) ApolloSpacecraft
cmSMUmbilical CSMInterface ApolloServiceModule.umbilicalPort ApolloCommandModule.umbilicalPort → lifeSupport (LifeSupportFlows), → power (ElectricalPower), → dataAndControl (CommandSignal) ApolloCommandServiceModule
lesConnection LESInterface ApolloCommandModule.lesInterfacePort ApolloLaunchEscapeSystem.cmInterfacePort ↔ loads (StructuralLoad), → abortSignal (CommandSignal), → jettisonSignal (CommandSignal) ApolloSpacecraft
lmInterstage LMStagingInterface LunarModuleDescentStage.upperStagePort LunarModuleAscentStage.lowerStagePort ↔ loads (StructuralLoad), → powerAndData (ElectricalPower), → commands (CommandSignal) ApolloLunarModule

Within the space suits (1 connection)

Connection Interface definition End 1 (component.port) End 2 (component.port) Flows (from end 1) Declared in
suitToPLSSUmbilical EVAInterface PortableLifeSupportSystem.umbilicalPort PressureSuiteAssembly.umbilicalPort ↔ commsAndData (TelemetryData), → power (ElectricalPower), → lifeSupport (LifeSupportFlows) ExtravehicularMobilityUnit

Launch vehicle ↔ spacecraft (1 connection)

Connection Interface definition End 1 (component.port) End 2 (component.port) Flows (from end 1) Declared in
lvToPayload LVPayloadInterface SaturnVInstrumentUnit.payloadInterfacePort ApolloSpacecraftLMAdapter.launchVehicleInterfacePort ← telemetry (TelemetryData), ↔ loads (StructuralLoad), → commands (CommandSignal), → power (ElectricalPower) Apollo11MissionSystem

Flight ↔ ground: no connection. The model declares no interface between the mission system and the ground systems of its context.

Port definitions (8): the items each connection point carries
Port definition Items (direction seen from the port)
ControlPort guidanceCmds (out), power (out), telemetry (in), thrustCmds (out)
DockingPort data (in/out), loads (in/out), power (in/out)
EVAUmbilicalPort commsAndData (in/out), lifeSupport (out), power (out)
LMStagingPort commands (out), loads (in/out), powerAndData (out)
LaunchEscapeSystemPort abortSignal (out), jettisonSignal (out), loads (in/out)
PayloadInterfacePort commands (out), loads (in/out), power (out), telemetry (in)
StagingPort commands (out), loads (in/out)
UmbilicalPort dataAndControl (out), lifeSupport (out), power (out)
Interface definitions (8): contracts between two ports; ~ marks a conjugated port, whose directions are reversed, so what one end sends the other receives
Interface definition End 1 End 2
CSMInterface supplier : UmbilicalPort consumer : ~UmbilicalPort
DockingInterface vehicle1 : DockingPort vehicle2 : DockingPort
EVAInterface plss : EVAUmbilicalPort psa : ~EVAUmbilicalPort
GuidanceInterface controller : ControlPort controlled : ~ControlPort
LESInterface commandModule : LaunchEscapeSystemPort launchEscapeSystem : ~LaunchEscapeSystemPort
LMStagingInterface platform : LMStagingPort ascender : ~LMStagingPort
LVPayloadInterface launchVehicle : PayloadInterfacePort payload : ~PayloadInterfacePort
StagingInterface source : StagingPort target : ~StagingPort

Interface diagram: which components connect to which (one edge per connection).

flowchart LR
  nSaturnVInstrumentUnit["SaturnVInstrumentUnit"] <-->|"lvToPayload"| nApolloSpacecraftLMAdapter["ApolloSpacecraftLMAdapter"]
  nApolloServiceModule["ApolloServiceModule"] <-->|"cmSMUmbilical"| nApolloCommandModule["ApolloCommandModule"]
  nLunarModuleDescentStage["LunarModuleDescentStage"] <-->|"lmInterstage"| nLunarModuleAscentStage["LunarModuleAscentStage"]
  nApolloSpacecraftLMAdapter["ApolloSpacecraftLMAdapter"] <-->|"StagingInterface"| nApolloServiceModule["ApolloServiceModule"]
  nApolloCommandModule["ApolloCommandModule"] <-->|"cmLMDocking"| nLunarModuleAscentStage["LunarModuleAscentStage"]
  nApolloCommandModule["ApolloCommandModule"] <-->|"lesConnection"| nApolloLaunchEscapeSystem["ApolloLaunchEscapeSystem"]
  nPortableLifeSupportSystem["PortableLifeSupportSystem"] <-->|"suitToPLSSUmbilical"| nPressureSuiteAssembly["PressureSuiteAssembly"]
  nSaturnVInstrumentUnit["SaturnVInstrumentUnit"] <-->|"iuToStage3"| nS_IVB["S-IVB"]
  nS_IC["S-IC"] <-->|"stage1ToStage2"| nS_II["S-II"]
  nS_II["S-II"] <-->|"stage2ToStage3"| nS_IVB["S-IVB"]

7 of the 8 interface definitions pair a port with its conjugate; DockingInterface uses the same symmetric port on both sides. ApolloCommandModule provides no power of its own; power reaches it through cmSMUmbilical (from ApolloServiceModule) and cmLMDocking (from LunarModuleAscentStage).

What the interface register does and does not say
  • The interfaces are functional connections: each pairs two ports and names the items that flow between them. No element of the technical layer stands for a harness, a cable or a separation plane, so the model does not say how the connections are physically realized, such as which ones share an umbilical harness or which cables cross each stage joint.
  • Flight ↔ ground: no connections. In the real system, telemetry and commands between the vehicles and Mission Control pass a flight/ground link through the tracking network; the model has none, so the register is a partial bottom-up account: it covers the connections within the launch vehicle, within the space suits, within the spacecraft and between the launch vehicle and the spacecraft, not the links to the ground.

As-flown configuration¶

Product As-flown configuration
The serial-numbered vehicles of the Apollo program (individuals) and the design each one realizes, with the vehicles that flew Apollo 11 highlighted.
Use it to tell a design from a specific vehicle, and see which vehicles flew which mission.
Apollo 11 flew
  • LM-5 Eagle, a ApolloLunarModule: Eagle, Apollo 11. Descent stage on lunar surface in Sea of Tranquility, ascent stage left in lunar orbit (could be still orbiting the moon)
  • SA-506, a SaturnV: Apollo 11. First crewed lunar landing, at Sea of Tranquility.
  • CSM-107 Columbia, a ApolloCommandServiceModule: Columbia Apollo 11. Command module on display at National Air and Space Museum, Washington, D.C.

Program vehicles by mission (from each vehicle's documentation; Apollo 11 highlighted)

Mission SaturnV ApolloCommandServiceModule ApolloLunarModule
Apollo 4 SA-501 – LTA-10R
Apollo 5 – – LM-1
Apollo 6 SA-502 – LTA-2R
Apollo 7 – CSM-101 –
Apollo 8 SA-503 CSM-103 –
Apollo 9 SA-504 CSM-104 (Gumdrop) LM-3 (Spider)
Apollo 10 SA-505 CSM-106 (Charlie Brown) LM-4 (Snoopy)
Apollo 11 SA-506 CSM-107 (Columbia) LM-5 (Eagle)
Apollo 12 SA-507 CSM-108 (Yankee Clipper) LM-6 (Intrepid)
Apollo 13 SA-508 CSM-109 (Odyssey) LM-7 (Aquarius)
Apollo 14 SA-509 CSM-110 (Kitty Hawk) LM-8 (Antares)
Apollo 15 SA-510 CSM-112 (Endeavour) LM-10 (Falcon)
Apollo 16 SA-511 CSM-113 (Casper) LM-11 (Orion)
Apollo 17 SA-512 CSM-114 (America) LM-12 (Challenger)

66 vehicles in all; 31 name no Apollo mission they flew. 5 of them flew later programs, Skylab or the Apollo–Soyuz Test Project (CSM-111, CSM-116, CSM-117, CSM-118, SA-513); the other 26 are documented as test, training, backup, unused or incomplete hardware. The mission each vehicle flew is recorded only in its documentation; the model places vehicles on a mission only in Apollo11MissionSystem, for Apollo 11.

Crew¶

Apollo 11 crew
  • Commander: Neil Armstrong
  • Command Module Pilot: Michael Collins
  • Lunar Module Pilot: Buzz Aldrin
Astronaut Apollo 11 role Apollo missions named in the astronaut's documentation
Neil Armstrong Commander Apollo 11
Michael Collins Command Module Pilot Apollo 11
Buzz Aldrin Lunar Module Pilot Apollo 11
Alan Bean Apollo 12
Alan Shepard Apollo 14
Alfred Worden Apollo 15
Charles Duke Apollo 11, Apollo 16
David Scott Apollo 9, Apollo 15
Donn Eisele Apollo 7
Ed White Apollo 1
Edgar Mitchell Apollo 14
Eugene Cernan Apollo 10, Apollo 17
Frank Borman Apollo 8
Fred Haise Apollo 13
Gus Grissom Apollo 1
Harrison Schmitt Apollo 17
Jack Swigert Apollo 13
James Irwin Apollo 15
James Lovell Apollo 8, Apollo 13
James McDivitt Apollo 9
John Young Apollo 10, Apollo 16
Ken Mattingly Apollo 13, Apollo 16
Pete Conrad Apollo 12
Richard Gordon Apollo 12
Roger B. Chaffee Apollo 1
Ronald Evans Apollo 17
Russell Schweickart Apollo 9
Stuart Roosa Apollo 14
Thomas Stafford Apollo 10
Wally Schirra Apollo 7
Walt Cunningham Apollo 7
William Anders Apollo 8
Official portrait of the Apollo 11 crew: Armstrong, Collins and Aldrin
The Apollo 11 crew, from left: Neil A. Armstrong, commander; Michael Collins, command module pilot; Edwin E. Aldrin Jr., lunar module pilot. NASA, April 1969, public domain.

Modeling issues on this page¶

Found while building this page
  • HardwareComponent::totalMass is defined as mass + sum(subcomponents.totalMass), but no component subsets subcomponents, so the model's own roll-up cannot sum anything. The type breakdown above takes each design's own dry mass, and sums the parts only where a design states none.
  • Vehicle-to-mission assignments other than Apollo 11 exist only as prose in documentation comments.
ModelwareProduced on 07 Nov 2026 from the Apollo 11 SysML v2 model v0.0.1 with Modelware's Sysight tool, © 2026 Modelware.