Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
ISO 26869:2012 Space Systems — Small Auxiliary Spacecraft (SASC) to Launch Vehicle Interface Control Document
Standardized ICD Template for Secondary Payload Integration on Launch Vehicles
1. Introduction and Scope
ISO 26869:2012, developed by ISO/TC 20/SC 14 (Space systems and operations), provides small auxiliary spacecraft (SASC) and launch vehicle (LV) organizations with standardized rules and format for writing an Interface Control Document (ICD). A SASC is a small payload carried with the primary spacecraft by using surplus launch capability — by definition, it has no adverse impact on the primary spacecraft or its mission.
Establishing a common ICD baseline is a cost- and risk-minimizing strategy for international trade in space launch services. Standardized ICD requirements allow SASC providers to design for multiple launch vehicles without extensive customization, reducing development costs and expanding launch opportunities.
The standard is applicable to ICD items and restrictions peculiar to SASCs, which have minor priorities with respect to the main spacecraft. The scope is limited to SASCs that interface only with the LV (not directly with the primary spacecraft), making it suitable for ESPA-class rideshare adapters and similar secondary payload deployment systems.
2. Mechanical Interface Requirements
2.1 Structural Configuration and Adapter Design
The ICD must specify the mechanical configuration through detailed drawings showing the SASC and adapter assembly within the payload compartment, including reference axes and relative rotational orientation. Key mechanical parameters include the minimum allowable fundamental frequencies in axial and lateral directions, usable volume constraints (determined by static clearances and dynamic deflections of LV structures and primary payload), and the complete characteristics of the LV-SASC adapter interface.
| Mechanical Parameter | ICD Specification Requirements |
|---|---|
| Fundamental frequencies | Minimum allowable axial and lateral frequencies |
| Usable volume | Drawings with static/dynamic clearances and protrusion areas |
| Adapter characteristics | Type, material, geometry, separation system, ring diameters, mass properties |
| Connector/microswitch I/F | Type, quantity, location, push-on/push-off loads, separation force |
| Purge/fluid connection | Angular/radial position, height from separation plane, leakage rate |
2.2 Separation System Considerations
The separation system is one of the most critical interface elements. The ICD must specify the separation system type (lightband, clamp band, or other), its mass properties, shock spectrum at the interface, and the method for separation status confirmation. For SASCs providing their own adapter, the shock environment generated by the separation system must be characterized and provided to the LV contractor.
3. Electrical and RF Interfaces
3.1 Umbilical and Command Interfaces
SASCs face significant restrictions on command lines, flight telemetry, power supply, and RF link redundancy to prevent interference with primary spacecraft functions. The ICD must provide detailed umbilical wiring diagrams, connector specifications (supplier, part number, pin count, polarizing key orientation, shielding requirements), and complete pin-by-pin wiring link descriptions covering voltage, current, resistance, signal type, and frequency for every connector pin.
| Electrical Parameter | Typical Constraint |
|---|---|
| Pyrotechnic command pulse width | Defined in ms, with min all-fire / max no-fire current |
| Power supply voltage/current | As defined by LV, with ripple noise specification |
| Line isolation resistance | Verified end-to-end by LV contractor |
| Earth continuity resistance | Maximum between SASC metallic elements and reference point |
3.2 Radio Frequency Compatibility
The RF and electromagnetic interface section must characterize the radio-electrical systems, RF telemetry and command links, and electromagnetic compatibility. SASCs sometimes have restrictions on RF link redundancy to avoid distracting primary spacecraft functions — the ICD captures these constraints and defines the coordination path between LV, primary payload, and SASC contractors.
4. Engineering Design Insights
For secondary payload developers and integrators, ISO 26869 provides a comprehensive checklist that helps avoid costly integration surprises. The ICD structure follows the proven template from ISO 15863 for primary spacecraft but adds provisions specific to the unique constraints of secondary payloads — including reduced priority, simplified interfaces, and the option for a mass simulator. Key design considerations include:
SASC simulator provision: The standard explicitly allows for a SASC simulator that can maintain the launch schedule if the actual SASC development is delayed. This is a practical risk mitigation mechanism — the simulator must replicate all identified interfaces, allowing launch without the SASC and its replacement by the actual unit on a later mission.
Environmental qualification: The ICD must specify the SASC mechanical environment (static acceleration, quasi-static loads, low-frequency vibration, random vibration, acoustic noise, and shock) and thermal environment (air-conditioning parameters during ground operations, aerothermal flux during ascent). Verification tests include static load, modal survey, sinusoidal and random vibration, acoustic noise, and separation shock.
Launch range operations: The standard dedicates an entire section (Clause 12) to launch-range operations, covering preparation facilities, consumable loading, encapsulation, handling, transport, battery charging, and mission control interfaces — areas often overlooked by SASC developers focused solely on the space segment.
Interface compatibility management: The ICD template systematically addresses every potential interface conflict point: mechanical (frequencies, volumes, adapter loads), electrical (power quality, command timing, grounding), RF (frequency allocation, out-of-band emissions, receiver desensitization), and environmental (contamination, thermal, electromagnetic). This structured approach significantly reduces the risk of late-discovery interface incompatibilities that can delay launches or require costly redesigns.
A critical design consideration: SASC cleanliness is subject to the primary payload’s requirements, and the SASC must not have any harmful influence on the primary payload. This means SASC developers must understand and comply with contamination control requirements that may be driven by sensitive primary payload instruments such as optical telescopes or cryogenic sensors.
5. FAQs
Q1: What is a Small Auxiliary Spacecraft (SASC)?
A SASC is a secondary payload that uses surplus launch vehicle capacity, carried alongside the primary spacecraft with no adverse impact on the primary mission.
A SASC is a secondary payload that uses surplus launch vehicle capacity, carried alongside the primary spacecraft with no adverse impact on the primary mission.
Q2: Does ISO 26869 cover SASC-to-primary spacecraft interfaces?
No — the standard is limited to SASC-to-LV interfaces only. SASC-to-primary spacecraft interfaces, if any, are outside its scope and would require separate ICD agreements.
No — the standard is limited to SASC-to-LV interfaces only. SASC-to-primary spacecraft interfaces, if any, are outside its scope and would require separate ICD agreements.
Q3: How does the standard handle mission analysis for SASCs?
The standard requires the SASC contractor to provide input data for trajectory analysis, while noting that the SASC trajectory is subject to the primary payload trajectory. Launch windows are also subject to the primary payload’s constraints.
The standard requires the SASC contractor to provide input data for trajectory analysis, while noting that the SASC trajectory is subject to the primary payload trajectory. Launch windows are also subject to the primary payload’s constraints.
Q4: What verification tests are mandatory?
Match-mate, separation, umbilical connector pull-out, clearance measurement, EMC, end-to-end electrical, and RF link tests are all identified as verification tests applicable to the SASC.
Match-mate, separation, umbilical connector pull-out, clearance measurement, EMC, end-to-end electrical, and RF link tests are all identified as verification tests applicable to the SASC.
