SPACEX FALCON (01) PDF Document

The SPACEX FALCON launch vehicles incorporate several key safety features in their design and operations. These features improve reliability for payloads and are designed to meet NASA human-rating margins.

The SPACEX FALCON has the following dimensions and characteristics for its first and second stages:

The SPACEX FALCON offers a variety of typical injection orbits from its operational launch sites. The available services are detailed below. Note that Falcon Heavy is only available from the Eastern Range and some options are subject to mission-specific performance considerations.

For the SPACEX FALCON, customers are required to adhere to the following guidelines to maximize launch availability:

1. Remove constraints that may restrict launch windows to no less than a daily four-hour window as far as possible.

2. Avoid selecting launch windows that result in a high statistical probability of violation (POV) for launch weather constraints as defined for the Eastern and Western Ranges.

3. For missions that require a near-instantaneous launch window, customer constraints shall not limit SpaceX to less than a 15-second daily launch window. This provides SpaceX the flexibility to shift the liftoff time by a few seconds based on the final conjunction assessment results performed by the Combined Space Operations Center (CSpOC) prior to launch.

For multiple payload deployments on the SPACEX FALCON that require different insertion orbits or burns as part of a single launch, the maximum CG shift Δ (above the Payload Attach Fitting, or PAF) that is allowed between orbits or burns is 5 cm RSS lateral (in the launch vehicle coordinate system).

This requirement applies to both customer-provided and SpaceX-provided dispensers:

Customer-provided dispenser: Customers must meet this requirement. Verification by analysis is acceptable.

SpaceX-provided dispenser: SpaceX will work with the customer to meet this requirement through stack CG analysis. SpaceX does not intend to supply any mass simulators to help meet the requirement.

When planning a mission on the SPACEX FALCON, you should select and plan for interfaces, masses, and keep-in volumes according to the following guide. Note that masses are for initial guidance and further limitations may exist from mission-specific analyses.

The SPACEX FALCON supports two standard configurations for constellation payloads, a Cube Arrangement and an Octagon Arrangement.

The maximum payload mass per constellation configuration is provided as a guide. Additional limitations may exist on the center of gravity and from coupled loads analysis (CLA) results. This guide assumes a forward mounted payload is present and is identical to the side mounted payloads.

IMPORTANT: Payloads flying with any of the configurations above will need to meet acoustic MPE levels for Falcon 9 without blankets. Otherwise, additional restrictions may apply to the keep-in volumes.

The SPACEX FALCON can offer a gaseous nitrogen (GN2) purge interface as a nonstandard service. The specifications are as follows:

As a nonstandard service, the SPACEX FALCON can provide cryogenic propellant loading of liquid oxygen (LOX) and liquid methane (LCH4) at launch complex LC-39A. Customers must demonstrate that the payload passes successful integrated leak checks.

The SPACEX FALCON provides standard electrical connectivity for payloads, summarized below. Additional capabilities are available as nonstandard services.

For the SPACEX FALCON, PL-side breakwire channels must transition from a low resistance state to a high resistance state, or vice-versa. The required properties for each state are defined below:

Payloads for the SPACEX FALCON will experience the following maximum predicted quasi-static load factors during transportation from the Payload Processing Facility (PPF) to the launch pad. These limits are inclusive of both static and dynamic loads, including gravity.

The standard service environmental conditions for a payload during various processing phases for a SPACEX FALCON launch are as follows:

The quasi-static flight limit load factors for the SPACEX FALCON vary based on the total payload mass. The factors are provided for heavy, medium, and light-class payloads.

Payload transmitters on a SPACEX FALCON mission may only be enabled after a minimum time after payload separation. This time depends on the payload’s Effective Isotropic Radiated Power (EIRP) and its separation velocity. Standard launch services do not permit the use of payload transmitters while integrated to the launch vehicle hardware.

Additionally, transmitters centered in the following bands may need to wait until “end of mission” (defined by mission-specific second stage re-entry time or stage passivation):

Band 1: 2206.0 – 2216.0 MHz

Band 2: 2227.5 – 2237.5 MHz

Band 3: 2242.5 – 2260.5 MHz

Band 4: 2267.5 – 2277.5 MHz

Band 5: 2365.5 – 2375.5 MHz

Band 6: 2377.5 – 2387.5 MHz

Customers must inform SpaceX prior to LSA finalization if transmitting inside one of these bands or in any GNSS band.

Payload systems and structural components for the SPACEX FALCON should adhere to the minimum design and peaking factors shown below.

The design and test factors for pressure vessels, lines, and other pressurized components on a SPACEX FALCON payload are as follows:

Payloads for the SPACEX FALCON must undergo verification testing according to one of three approaches: Unit/Fleet Qualification and Acceptance, or Flight Unit Protoqualification. The required levels and durations are detailed below.

Customers must provide specific documents and data for all payloads on a SPACEX FALCON mission.

Additional documents are required for non-US persons and non-US government payloads.

After a SPACEX FALCON launch, customers have several responsibilities for payload registration and situational awareness.

Pre-Launch Registration: The customer is responsible for registering all deployed objects with the 18th SPCS to assist with tracking and identification. If required, SpaceX can provide direct contact information with personnel from the 18th SPCS.

ISS Conjunction Deconfliction: If any of the payload’s operational, transfer, or disposal orbits cross the ISS altitude, NASA requests direct coordination for ISS conjunction deconfliction.

Post-Launch Registration: The customer is responsible for publishing forward predicted satellite ephemerides with covariance to Space-Track and SpaceX Space Traffic Coordination. An important benchmark is uploading ephemerides within Launch + 3 hours when the Launch COLA analysis expires.

If customers are unable to generate propagated ephemeris and covariance, SpaceX strongly recommends working with a commercial provider for this service.

A standard launch integration schedule for a SPACEX FALCON mission starts at contract signature and proceeds through post-flight summary. A detailed schedule is developed during contract negotiation.

A sample flight timeline for a Geosynchronous Transfer Orbit (GTO) mission on the SPACEX FALCON is as follows. Note that each flight profile is unique and will differ.

A sample flight timeline for a Low-Earth Orbit (LEO) mission on the SPACEX FALCON is as follows. Note that each flight profile is unique and will differ.

For a SPACEX FALCON mission, the customer must provide a simplified payload CAD model in NX Parasolid (.x_t) or STEP 214 or lower format. The model should focus on outer mold line and interface fidelity.

The CAD model must include:

Payload interface to launch vehicle, including:

Payload mechanical interface

Electrical connectors and associated brackets

Pusher pads

Components for clearance analysis, including:

External components like solar array panels, antennas, and reflectors

Any components within 20 cm of the interface components

Any components that protrude below the separation plane

Any points requiring access after encapsulation.

Simple payload bus structure.

The CAD model must NOT include:

Internal payload or bus components.

Spurious details like individual solar array cells, fasteners, etc., that do not add to the understanding of external volumes.

Before delivery, you must verify:

All SpaceX hardware has been removed.

The entire payload is within the desired flight configuration keep-in volume.

Unnecessary detail has been removed.

Simplified bodies fully envelop the OML of the actual payload.

All direct LV interface bodies are included.

The payload is properly configured (origin at SpaceX standard interface, clocked correctly) and agrees with corresponding mass properties.

The file size is 100 MB or less.

For a SPACEX FALCON mission, the payload dynamic model shall be provided as a Craig-Bampton reduced model. The requirements are as follows:

Model Requirements:

The model file should be no larger than 500 MB.

The units of the model shall be clearly defined (English or SI).

The model will be delivered as a multipoint interface model.

The model shall be Craig-Bampton formatted.

Modal damping shall be specified.

Any uncertainty factor applied to the modal responses shall be defined.

The model shall have frequency content up to 150 Hz.

All output requests shall be clearly defined.

The model shall be an accurate representation of the payload.

Slosh effects shall be included, with modes identified and scaling method defined.

Interface Requirements:

The interface to the launch vehicle shall remain physical with six degrees of freedom at each interface node.

The interface location shall match the payload-to-launch vehicle mechanical interface definition.

Boundary node locations shall be clearly defined according to the provided table for standard interface diameters.

Interface points not at the payload-to-launch vehicle interface plane are not allowed, unless necessity and stiffness can be proven.

The coordinate system for boundary degrees of freedom shall be a cylindrical output coordinate system with the origin at the center of the interface. Boundary nodes will be numbered sequentially and ordered counterclockwise.

For a SPACEX FALCON mission, the customer must provide a coarsened thermal model of the payload(s) in Thermal Desktop (.dwg) format. The following checklist outlines the requirements:

Each payload must have a unique name ([NAME]). For missions with duplicate payloads, each must have a unique filename (e.g., [NAME_1], [NAME_2]).

Thermal Desktop “External References” (XREFs) are not permitted.

All sub-model names must begin with PL_[NAME]_ and not exceed 800 total.

All optical and thermophysical properties must begin with PL_[NAME]_.

All Thermal Desktop Symbols must begin with PL_[NAME]_ and be in a symbol group named “Payload”, not exceeding 2,000 total.

All Thermal Desktop Layers must begin with _PL_[NAME]_.

Radiating surfaces must be in a Radiation Analysis Group named “Payload”.

Surfaces subject to convection must be in a tag set named “PL_CONVECT”.

Surfaces mechanically connected to the launch vehicle must be in a tag set named “PL_ATTACH”.

A SINDA/FLUINT include file or logic object may be provided for manually coded thermal logic.

The payload model must contain specific Thermal Desktop symbols (PL_OnPad, PL_[NAME]_HeatersOn, PL_[NAME]_AvPower) to drive changes based on the mission phase (e.g., on pad, ascent) and power status.

A summary document (Word, PowerPoint, or PDF) must be provided outlining details for running and integrating the payload model.

The model must include a test case in the Thermal Desktop Case Set Manager that demonstrates the model runs faster than real time.

A table of temperature requirements must be provided using the SpaceX template Excel file.

For clarity, the customer shall provide a table defining the values for key symbols during different analysis phases: