ECSS Impact Risk Assessment (space-systems/ecss/e1004-impact-risk)
Use when the task is running the meteoroid/space-debris impact risk
assessment for a space element under ECSS-E-ST-10-04C clause 10.2.5:
turning per-population damaging flux into a probability of no
penetration (PNP) and probability of damage via the Annex J method,
and checking the result against the mission's PNP requirement.
Domain quick reference
- ECSS-E-ST-10-04C clause 10.2.5 requires an impact risk assessment
once the damaging flux at the element's ballistic-limit critical
diameter is known: the flux is converted into a probability of
penetration/damage over the mission, per the Annex J method.
- Each contributing particle population (debris, meteoroid background,
meteoroid streams) evaluated at the same critical diameter has a
cumulative flux (impacts/m^2/year); independent populations sum
linearly into a total damaging flux.
- The expected number of damaging impacts is N = total_flux *
exposed_area * mission_duration.
- Annex J treats impacts as a Poisson process: probability of no
penetration Po = exp(-N); probability of one or more damaging
impacts, Pd = 1 - Po.
- An element meets its risk-acceptance requirement only when Po is at
or above the mission's minimum acceptable PNP; otherwise the
shortfall (requirement - Po) drives further mitigation (shielding,
reduced exposed area, added margin) upstream of this leaf.
- A system built from independently-assessed elements (panels,
subsystems) has a system-level PNP equal to the product of the
element PNPs, under the independence assumption used by the Annex J
method.
- This leaf does not select or run the debris/meteoroid flux models
(siblings e1004-debris, e1004-meteoroid) and does not apply design
margins to flux or damage predictions (sibling e1004-mm-margins); it
consumes already-selected, already-margined flux values and runs the
probability calculation and requirement check.
Workflow
- Determine the critical diameter for the element (from the
ballistic-limit equation for its shielding/structure) and collect
the cumulative damaging flux at that diameter from each
contributing population (debris, meteoroid background, meteoroid
streams).
- Sum the per-population fluxes into a total damaging flux for the
element.
- Compute the expected number of damaging impacts N over the
element's exposed area and mission duration.
- Compute the probability of no penetration (Po = exp(-N)) and the
probability of damage (Pd = 1 - Po).
- Compare Po against the mission's PNP acceptance requirement for the
element; if Po falls short, record the shortfall and flag the
element for mitigation (added shielding, reduced exposed area,
reorientation) or margin review before proceeding.
- When assessing a system of multiple independently-assessed elements,
combine their individual PNPs multiplicatively to get the
system-level PNP, and check that combined value against the
system-level requirement.
Pitfalls
- Summing fluxes evaluated at different critical diameters (each
element/shielding configuration has its own ballistic-limit
diameter; fluxes must be compared at the same diameter before
summing).
- Treating Pd (probability of damage) as the PNP, or comparing it
against a PNP-style requirement without inverting it first.
- Averaging element PNPs instead of multiplying them when rolling up
to a system-level result (independence assumes multiplication, not
averaging).
- Applying design margin inside this leaf's calculation instead of
margining the input flux upstream (sibling e1004-mm-margins) so the
probability step stays a pure flux-to-probability conversion.
- Reporting a shortfall as met because Po is close to the requirement;
the check is a strict Po >= pnp_requirement comparison.
Behavior contract (gate 3)
The flux-combination, expected-impact, probability, requirement-check,
and system-PNP-rollup logic is exercised by the gate 3 contract test:
scripts/test_e1004_impact_risk.py against
scripts/e1004_impact_risk_logic.py (stdlib unittest, offline). Run:
python3 scripts/test_e1004_impact_risk.py
Compliance
- ECSS standards are freely downloadable (ESA); cite the source and
paraphrase per standards-map.yaml.
- compliance: STANDARDS-REF, gated: false.
1---2name: e1004-impact-risk3description: "Use when running a meteoroid/space-debris impact risk assessment for a space element under ECSS-E-ST-10-04C clause 10.2.5: combine the cumulative damaging flux from each contributing particle population at the ballistic-limit critical diameter, turn it into an expected impact count over the exposed area and mission duration, and compute the probability of no penetration (PNP) and probability of damage via the Annex J Poisson method, checking the result against the mission's PNP acceptance requirement. Distinct from the sibling e1004-debris and e1004-meteoroid leaves, which select and evaluate the flux models this leaf consumes, and from the sibling e1004-mm-margins leaf, which applies design margins to flux or damage predictions rather than running the probability calculation itself. Trigger: ecss, e-st-10-04c, impact risk, damage probability, probability of no penetration, pnp, annex j, meteoroid debris risk, ballistic limit, space environment."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/e1004-impact-risk15 domain: space-systems16 subdomain: ecss17 tags: [ecss, e-st-10-04c, space-environment, meteoroid, debris, impact-risk, annex-j, pnp]18 version: 0.1.019 author: Aero Agent Skills20---2122# ECSS Impact Risk Assessment (space-systems/ecss/e1004-impact-risk)2324Use when the task is running the meteoroid/space-debris impact risk25assessment for a space element under ECSS-E-ST-10-04C clause 10.2.5:26turning per-population damaging flux into a probability of no27penetration (PNP) and probability of damage via the Annex J method,28and checking the result against the mission's PNP requirement.2930## Domain quick reference3132- ECSS-E-ST-10-04C clause 10.2.5 requires an impact risk assessment33 once the damaging flux at the element's ballistic-limit critical34 diameter is known: the flux is converted into a probability of35 penetration/damage over the mission, per the Annex J method.36- Each contributing particle population (debris, meteoroid background,37 meteoroid streams) evaluated at the same critical diameter has a38 cumulative flux (impacts/m^2/year); independent populations sum39 linearly into a total damaging flux.40- The expected number of damaging impacts is N = total_flux *41 exposed_area * mission_duration.42- Annex J treats impacts as a Poisson process: probability of no43 penetration Po = exp(-N); probability of one or more damaging44 impacts, Pd = 1 - Po.45- An element meets its risk-acceptance requirement only when Po is at46 or above the mission's minimum acceptable PNP; otherwise the47 shortfall (requirement - Po) drives further mitigation (shielding,48 reduced exposed area, added margin) upstream of this leaf.49- A system built from independently-assessed elements (panels,50 subsystems) has a system-level PNP equal to the product of the51 element PNPs, under the independence assumption used by the Annex J52 method.53- This leaf does not select or run the debris/meteoroid flux models54 (siblings e1004-debris, e1004-meteoroid) and does not apply design55 margins to flux or damage predictions (sibling e1004-mm-margins); it56 consumes already-selected, already-margined flux values and runs the57 probability calculation and requirement check.5859## Workflow60611. Determine the critical diameter for the element (from the62 ballistic-limit equation for its shielding/structure) and collect63 the cumulative damaging flux at that diameter from each64 contributing population (debris, meteoroid background, meteoroid65 streams).662. Sum the per-population fluxes into a total damaging flux for the67 element.683. Compute the expected number of damaging impacts N over the69 element's exposed area and mission duration.704. Compute the probability of no penetration (Po = exp(-N)) and the71 probability of damage (Pd = 1 - Po).725. Compare Po against the mission's PNP acceptance requirement for the73 element; if Po falls short, record the shortfall and flag the74 element for mitigation (added shielding, reduced exposed area,75 reorientation) or margin review before proceeding.766. When assessing a system of multiple independently-assessed elements,77 combine their individual PNPs multiplicatively to get the78 system-level PNP, and check that combined value against the79 system-level requirement.8081## Pitfalls8283- Summing fluxes evaluated at different critical diameters (each84 element/shielding configuration has its own ballistic-limit85 diameter; fluxes must be compared at the same diameter before86 summing).87- Treating Pd (probability of damage) as the PNP, or comparing it88 against a PNP-style requirement without inverting it first.89- Averaging element PNPs instead of multiplying them when rolling up90 to a system-level result (independence assumes multiplication, not91 averaging).92- Applying design margin inside this leaf's calculation instead of93 margining the input flux upstream (sibling e1004-mm-margins) so the94 probability step stays a pure flux-to-probability conversion.95- Reporting a shortfall as met because Po is close to the requirement;96 the check is a strict Po >= pnp_requirement comparison.9798## Behavior contract (gate 3)99100The flux-combination, expected-impact, probability, requirement-check,101and system-PNP-rollup logic is exercised by the gate 3 contract test:102scripts/test_e1004_impact_risk.py against103scripts/e1004_impact_risk_logic.py (stdlib unittest, offline). Run:104python3 scripts/test_e1004_impact_risk.py105106## Compliance107108- ECSS standards are freely downloadable (ESA); cite the source and109 paraphrase per standards-map.yaml.110- compliance: STANDARDS-REF, gated: false.