ECSS Structures — FOS Tables Application (space-systems/ecss/fos-tables-application)
Use when the task is selecting and applying the tabulated factors of safety from
ECSS-E-ST-32C clause 4.2.5 to structural load cases — covering yield, ultimate
(burst), and proof factors for both unmanned and human spaceflight missions.
Domain quick reference
- ECSS-E-ST-32C clause 4.2.5 provides two sets of FOS tables: one for unmanned
spacecraft and one for human spaceflight (human-rated) missions. The correct
table is selected based on mission type before any FOS value is read.
- Three factor categories apply: the yield factor (jY) limits permanent
deformation under design loads; the ultimate factor (jU) guards against
fracture or collapse; the proof factor (jP) is used when verifying pressure
retention via a proof pressure test. Each category has a distinct tabulated
minimum.
- For unmanned missions the tabulated minimums are: jY = 1.10, jU = 1.25,
jP = 1.10. For human spaceflight missions the more conservative values are:
jY = 1.25, jU = 1.40, jP = 1.50. Using the unmanned table for a human-rated
programme is a non-conformance.
- Margin of safety is defined as: MS = (allowable / (FOS × limit load)) − 1.
A non-negative MS indicates the design meets the requirement; a negative MS
is a finding that must be resolved before the stress analysis is closed.
- Mixed-mission programmes (a payload flying on both an unmanned carrier and a
human-rated vehicle) must use the higher (human spaceflight) FOS for the
joint design unless a formal tailoring waiver is in place.
Workflow
- Determine the mission type for the hardware under analysis: unmanned or human
spaceflight. When there is uncertainty (dual-manifest or multi-mission), default
to human spaceflight until a tailoring decision is formally recorded.
- Select the applicable FOS table column (unmanned or human spaceflight) and
record the three required minimum factors: jY, jU, jP. Do not blend values
from both columns without a documented tailoring rationale.
- For each structural load case, identify the governing factor category:
— yield-critical cases: use jY;
— ultimate/burst cases: use jU;
— proof pressure cases: use jP.
A single component may have separate yield and ultimate load cases that each
require their own FOS application and margin check.
- Compute the design load for each case: design load = FOS × limit load. The
design load is the value that the allowable (material strength, test capability,
or burst pressure) must equal or exceed.
- Compute the margin of safety: MS = (allowable / design load) − 1. Record the
governing (minimum) MS across all load cases for the component.
- Accept the component if every MS ≥ 0. Reject (flag as a finding) if any MS < 0.
A component whose FOS source (unmanned vs human spaceflight table) is not
documented is also flagged, even if the numeric MS appears positive.
Pitfalls
- Reading the FOS from the unmanned column when the mission is human-rated, or
vice versa — the distinction is not a minor conservatism; it is a mandatory
normative requirement of clause 4.2.5 and will be checked at design review.
- Applying the yield FOS to a burst or fracture load case (or the ultimate FOS
to a yield-only case) — each factor category applies to a specific failure mode
and they must not be substituted for one another.
- Treating a positive MS as proof of compliance without confirming the allowable
was derived from the correct material coupon population (A-basis vs B-basis)
and the correct FOS column.
- Omitting the proof factor for a pressure-bearing component on the grounds that
a proof test was not performed — if no proof test is conducted, an analysis-only
proof margin must still be demonstrated using jP and the maximum expected
operating pressure as the limit load.
Behavior contract (gate 3)
The mission-type selection, FOS lookup, design-load computation, and margin-of-safety
logic is exercised by the gate 3 contract test:
scripts/test_fos_tables_application.py against
scripts/fos_tables_application_logic.py (stdlib unittest, offline). Run:
python3 scripts/test_fos_tables_application.py
Compliance
- ECSS standards are freely downloadable (ESA); cite the source and paraphrase
per standards-map.yaml.
- compliance: STANDARDS-REF, gated: false.
1---2name: fos-tables-application3description: "Use when determine the required factor of safety (FOS) for a structural4 component under ECSS-E-ST-32C clause 4.2.5: select the applicable yield, ultimate,5 or proof FOS from the tabulated values based on mission type (unmanned or human6 spaceflight), apply that factor to limit loads to obtain design loads, and compute7 the resulting margin of safety for each load case. Trigger: ecss, e-st-32-structures-scope,8 factor-of-safety, yield-factor, ultimate-factor, proof-factor, unmanned-spaceflight,9 human-spaceflight, margin-of-safety, structural-sizing."10license: Apache-2.011compliance: STANDARDS-REF12standards:13 - id: ecss14 reference-only: true15gated: false16domain: space-systems17pack: space-systems18compatibility: "agentskills.io SKILL.md; any SKILL.md host (Claude Code, Hermes, OpenClaw)"19metadata:20 source: https://skillmd.com/skills/ashfordeou/fos-tables-application21 domain: space-systems22 subdomain: ecss23 tags: [ecss, e-st-32-structures-scope, factor-of-safety, yield-factor, ultimate-factor, proof-factor, unmanned-spaceflight, human-spaceflight, margin-of-safety]24 version: 0.1.025 author: Aero Agent Skills26---2728# ECSS Structures — FOS Tables Application (space-systems/ecss/fos-tables-application)2930Use when the task is selecting and applying the tabulated factors of safety from31ECSS-E-ST-32C clause 4.2.5 to structural load cases — covering yield, ultimate32(burst), and proof factors for both unmanned and human spaceflight missions.3334## Domain quick reference3536- ECSS-E-ST-32C clause 4.2.5 provides two sets of FOS tables: one for unmanned37 spacecraft and one for human spaceflight (human-rated) missions. The correct38 table is selected based on mission type before any FOS value is read.39- Three factor categories apply: the **yield factor** (jY) limits permanent40 deformation under design loads; the **ultimate factor** (jU) guards against41 fracture or collapse; the **proof factor** (jP) is used when verifying pressure42 retention via a proof pressure test. Each category has a distinct tabulated43 minimum.44- For unmanned missions the tabulated minimums are: jY = 1.10, jU = 1.25,45 jP = 1.10. For human spaceflight missions the more conservative values are:46 jY = 1.25, jU = 1.40, jP = 1.50. Using the unmanned table for a human-rated47 programme is a non-conformance.48- Margin of safety is defined as: MS = (allowable / (FOS × limit load)) − 1.49 A non-negative MS indicates the design meets the requirement; a negative MS50 is a finding that must be resolved before the stress analysis is closed.51- Mixed-mission programmes (a payload flying on both an unmanned carrier and a52 human-rated vehicle) must use the higher (human spaceflight) FOS for the53 joint design unless a formal tailoring waiver is in place.5455## Workflow56571. Determine the mission type for the hardware under analysis: unmanned or human58 spaceflight. When there is uncertainty (dual-manifest or multi-mission), default59 to human spaceflight until a tailoring decision is formally recorded.602. Select the applicable FOS table column (unmanned or human spaceflight) and61 record the three required minimum factors: jY, jU, jP. Do not blend values62 from both columns without a documented tailoring rationale.633. For each structural load case, identify the governing factor category:64 — yield-critical cases: use jY;65 — ultimate/burst cases: use jU;66 — proof pressure cases: use jP.67 A single component may have separate yield and ultimate load cases that each68 require their own FOS application and margin check.694. Compute the design load for each case: design load = FOS × limit load. The70 design load is the value that the allowable (material strength, test capability,71 or burst pressure) must equal or exceed.725. Compute the margin of safety: MS = (allowable / design load) − 1. Record the73 governing (minimum) MS across all load cases for the component.746. Accept the component if every MS ≥ 0. Reject (flag as a finding) if any MS < 0.75 A component whose FOS source (unmanned vs human spaceflight table) is not76 documented is also flagged, even if the numeric MS appears positive.7778## Pitfalls7980- Reading the FOS from the unmanned column when the mission is human-rated, or81 vice versa — the distinction is not a minor conservatism; it is a mandatory82 normative requirement of clause 4.2.5 and will be checked at design review.83- Applying the yield FOS to a burst or fracture load case (or the ultimate FOS84 to a yield-only case) — each factor category applies to a specific failure mode85 and they must not be substituted for one another.86- Treating a positive MS as proof of compliance without confirming the allowable87 was derived from the correct material coupon population (A-basis vs B-basis)88 and the correct FOS column.89- Omitting the proof factor for a pressure-bearing component on the grounds that90 a proof test was not performed — if no proof test is conducted, an analysis-only91 proof margin must still be demonstrated using jP and the maximum expected92 operating pressure as the limit load.9394## Behavior contract (gate 3)9596The mission-type selection, FOS lookup, design-load computation, and margin-of-safety97logic is exercised by the gate 3 contract test:98scripts/test_fos_tables_application.py against99scripts/fos_tables_application_logic.py (stdlib unittest, offline). Run:100python3 scripts/test_fos_tables_application.py101102## Compliance103104- ECSS standards are freely downloadable (ESA); cite the source and paraphrase105 per standards-map.yaml.106- compliance: STANDARDS-REF, gated: false.