ECSS Structures — Leak-Tightness Assessment (space-systems/ecss/leak-tightness)
Use when the task is to determine the maximum allowable leak rates for
pressurized spacecraft structures and verify that the leak-tightness design
complies with ECSS-E-ST-32C clause 4.2.1.
Domain quick reference
- Clause 4.2.1 requires the designer to define a maximum allowable leak rate
for each pressurized system and to verify by analysis or test that the
actual or predicted rate does not exceed it. The allowable is linked to a
tightness class (LT1 through LT4) that reflects mission criticality: LT1
is the most stringent (propellant tanks, safety-critical vessels), LT4 the
least (non-critical sealed volumes).
- Each potential leak interface is assigned to exactly one physical category:
seal interface, mechanical penetration, weld or fusion joint, adhesive bond
line, or threaded/swaged fitting. The category drives the inspection and
acceptance method; an interface with no recognized category must be resolved
before it enters the rate budget.
- A design margin is applied to the class allowable before checking
individual paths and the system total. This reserves compliance headroom
against manufacturing scatter and measurement uncertainty. A margin factor
of 2.0 (effective limit = allowable / 2) is a common starting point;
tighter systems may use 4.0 or higher.
- The system total leak rate is the arithmetic sum of all individual path
rates. Both the per-path check and the system-total check must pass; a
system total that exceeds the effective limit is a finding even when every
individual path rate is within the limit on its own.
Workflow
- Define the tightness class for the pressurized system based on its role
and criticality (LT1–LT4). Confirm the class with the system engineer
before proceeding; the class sets the allowable for all subsequent steps.
- Inventory every potential leak interface in the pressurized boundary.
Assign each interface one of the five recognized path types: seal,
penetration, weld, bond_line, or fitting. Reject any interface whose type
is not in that set — it must be re-examined and correctly categorized
before it can enter the budget.
- Establish a design margin factor (≥ 1.0; default 2.0). Compute the
effective limit as the class allowable divided by the margin factor. This
effective limit governs all individual-path and system-total checks.
- For each path, obtain the measured or predicted leak rate in consistent
units (mbar·L/s). If the rate was measured at a test pressure different
from the operating pressure, scale it to operating conditions using the
linear pressure-ratio rule before comparing.
- Check every path: if the path rate exceeds the effective limit, record a
finding identifying the path, its type, its rate, and the exceedance
factor.
- Sum all path rates to obtain the system total. If the system total exceeds
the effective limit, record a system-level finding. A system exceedance is
a separate finding from any path-level findings.
- The system is leak-tight compliant only when all path-level findings and
the system-level finding list are empty. Any open finding must be resolved
by design change, re-measurement, or a documented waiver before compliance
is declared.
Pitfalls
- Skipping the design margin and comparing path rates directly against the
class allowable — this removes the compliance reserve and leaves no
headroom for measurement uncertainty or manufacturing variation.
- Omitting the system-total check after verifying individual paths — paths
that each pass on their own can still drive the system total above the
effective limit when summed, which is a separate compliance failure.
- Applying a test-pressure leak rate to an operating-pressure budget without
scaling — a rate measured at higher test pressure understates the
operating-condition rate, giving a false pass for a system that will exceed
the limit in service.
- Leaving an interface with an unrecognized type in the budget rather than
resolving it — an unknown interface type means the acceptance method is
undefined, which is itself a compliance gap regardless of the rate.
- Treating a zero finding count as proof of margin — if the margin factor
was set to 1.0 by default without engineering justification, the assessment
carries no reserve; the margin factor choice must be documented.
Behavior contract (gate 3)
The path-categorization, rate-validation, pressure-scaling, per-path
compliance check, system-total summation, and full-assessment logic are
exercised by the gate 3 contract test:
scripts/test_leak_tightness.py against scripts/leak_tightness_logic.py
(stdlib unittest, offline). Run:
python3 scripts/test_leak_tightness.py
Compliance
- ECSS standards are freely downloadable from ESA; cite the source and
paraphrase per standards-map.yaml.
- compliance: STANDARDS-REF, gated: false.
1---2name: leak-tightness3description: "Use when determine maximum allowable leak rates for pressurized spacecraft structures and verify that the leak-tightness design meets ECSS-E-ST-32C clause 4.2.1 requirements: categorize each potential leak path by interface type (seal, penetration, weld, bond line, or fitting), apply the tightness class allowable with a design margin, check that every individual path rate and the total system rate stay within the effective limit, and document any exceedance or unrecognized path type as a finding. Trigger: ecss, e-st-32-structures-scope, leak-tightness, leak-rate, pressurized-structure, seal, pressure-vessel, leak-path."4license: Apache-2.05compliance: STANDARDS-REF6standards:7 - id: ecss8 reference-only: true9gated: false10domain: space-systems11pack: space-systems12compatibility: "agentskills.io SKILL.md; any SKILL.md host (Claude Code, Hermes, OpenClaw)"13metadata:14 source: https://skillmd.com/skills/ashfordeou/leak-tightness15 domain: space-systems16 subdomain: ecss17 tags: [ecss, e-st-32-structures-scope, leak-tightness, leak-rate, pressurized-structure, seal, pressure-vessel, leak-path]18 version: 0.1.019 author: Aero Agent Skills20---2122# ECSS Structures — Leak-Tightness Assessment (space-systems/ecss/leak-tightness)2324Use when the task is to determine the maximum allowable leak rates for25pressurized spacecraft structures and verify that the leak-tightness design26complies with ECSS-E-ST-32C clause 4.2.1.2728## Domain quick reference2930- Clause 4.2.1 requires the designer to define a maximum allowable leak rate31 for each pressurized system and to verify by analysis or test that the32 actual or predicted rate does not exceed it. The allowable is linked to a33 tightness class (LT1 through LT4) that reflects mission criticality: LT134 is the most stringent (propellant tanks, safety-critical vessels), LT4 the35 least (non-critical sealed volumes).36- Each potential leak interface is assigned to exactly one physical category:37 seal interface, mechanical penetration, weld or fusion joint, adhesive bond38 line, or threaded/swaged fitting. The category drives the inspection and39 acceptance method; an interface with no recognized category must be resolved40 before it enters the rate budget.41- A design margin is applied to the class allowable before checking42 individual paths and the system total. This reserves compliance headroom43 against manufacturing scatter and measurement uncertainty. A margin factor44 of 2.0 (effective limit = allowable / 2) is a common starting point;45 tighter systems may use 4.0 or higher.46- The system total leak rate is the arithmetic sum of all individual path47 rates. Both the per-path check and the system-total check must pass; a48 system total that exceeds the effective limit is a finding even when every49 individual path rate is within the limit on its own.5051## Workflow52531. Define the tightness class for the pressurized system based on its role54 and criticality (LT1–LT4). Confirm the class with the system engineer55 before proceeding; the class sets the allowable for all subsequent steps.562. Inventory every potential leak interface in the pressurized boundary.57 Assign each interface one of the five recognized path types: seal,58 penetration, weld, bond_line, or fitting. Reject any interface whose type59 is not in that set — it must be re-examined and correctly categorized60 before it can enter the budget.613. Establish a design margin factor (≥ 1.0; default 2.0). Compute the62 effective limit as the class allowable divided by the margin factor. This63 effective limit governs all individual-path and system-total checks.644. For each path, obtain the measured or predicted leak rate in consistent65 units (mbar·L/s). If the rate was measured at a test pressure different66 from the operating pressure, scale it to operating conditions using the67 linear pressure-ratio rule before comparing.685. Check every path: if the path rate exceeds the effective limit, record a69 finding identifying the path, its type, its rate, and the exceedance70 factor.716. Sum all path rates to obtain the system total. If the system total exceeds72 the effective limit, record a system-level finding. A system exceedance is73 a separate finding from any path-level findings.747. The system is leak-tight compliant only when all path-level findings and75 the system-level finding list are empty. Any open finding must be resolved76 by design change, re-measurement, or a documented waiver before compliance77 is declared.7879## Pitfalls8081- Skipping the design margin and comparing path rates directly against the82 class allowable — this removes the compliance reserve and leaves no83 headroom for measurement uncertainty or manufacturing variation.84- Omitting the system-total check after verifying individual paths — paths85 that each pass on their own can still drive the system total above the86 effective limit when summed, which is a separate compliance failure.87- Applying a test-pressure leak rate to an operating-pressure budget without88 scaling — a rate measured at higher test pressure understates the89 operating-condition rate, giving a false pass for a system that will exceed90 the limit in service.91- Leaving an interface with an unrecognized type in the budget rather than92 resolving it — an unknown interface type means the acceptance method is93 undefined, which is itself a compliance gap regardless of the rate.94- Treating a zero finding count as proof of margin — if the margin factor95 was set to 1.0 by default without engineering justification, the assessment96 carries no reserve; the margin factor choice must be documented.9798## Behavior contract (gate 3)99100The path-categorization, rate-validation, pressure-scaling, per-path101compliance check, system-total summation, and full-assessment logic are102exercised by the gate 3 contract test:103scripts/test_leak_tightness.py against scripts/leak_tightness_logic.py104(stdlib unittest, offline). Run:105106```107python3 scripts/test_leak_tightness.py108```109110## Compliance111112- ECSS standards are freely downloadable from ESA; cite the source and113 paraphrase per standards-map.yaml.114- compliance: STANDARDS-REF, gated: false.