ECSS Structures — PFCIL / FCIL / FLLIL Documentation and Configuration Control (space-systems/ecss/pfci-fci-flli-lists)
Use when the task is compiling, verifying, and maintaining the fracture
control item lists required by ECSS-E-ST-32C clause 6.4.2 — the
Potentially Fracture Critical Items List (PFCIL), the Fracture Critical
Items List (FCIL), and the Flight Limited Life Items List (FLLIL) — and
placing them under configuration control.
Domain quick reference
- Clause 6.4.2 of ECSS-E-ST-32C requires three controlled lists to be
compiled, maintained, and submitted for approval at defined programme
milestones. The PFCIL captures every structural item that is fracture
sensitive and whose failure consequence is critical or catastrophic;
the FCIL is the subset of PFCIL where fracture compliance cannot be
demonstrated through analysis or proof test alone (safe-life ratio
below 4.0); the FLLIL is the subset of FCIL where a specific life
limit is assigned and the item must be retired or replaced before that
limit is reached.
- An item enters the PFCIL through a screening step: if its material is
fracture sensitive (low fracture toughness, pre-existing flaw
sensitivity) and its failure consequence is critical or catastrophic,
it is placed on the PFCIL. Items whose failure consequence is
non-critical are exempt from all three lists.
- An item on the PFCIL escalates to the FCIL if the fracture control
analysis or proof test cannot demonstrate a safe-life ratio of at
least 4.0 (safe life divided by design life). Items that achieve
the required ratio remain on the PFCIL as compliant and do not
escalate further.
- An item on the FCIL receives a life limit when crack growth analysis
yields a finite safe life shorter than the design life; that item
then moves to the FLLIL and requires a defined replacement or
retirement plan with a stated life limit in cycles or flight hours.
- Each list must carry an issue number, an approval date, and the name
of the authorised signatory. Items added to or removed from a list
require documented justification; removal without justification is a
configuration control finding.
Workflow
- Screen every primary and secondary structural item for fracture
sensitivity (material fracture toughness, flaw sensitivity, stress
concentration) and failure consequence (catastrophic, critical, or
non-critical). Items with non-critical failure consequence are exempt
and excluded from all three lists. Place all remaining items on the
PFCIL with an entry recording the basis for their fracture-sensitive
designation.
- For each item on the PFCIL, evaluate the fracture control compliance
method: analyse using fracture mechanics (crack growth from the
initial assumed flaw under the full load spectrum) or perform a
proof test. Compute the safe-life ratio (demonstrated safe life
divided by design life). An item achieving a ratio of 4.0 or greater
is compliant and stays on the PFCIL without further escalation; an
item below 4.0 escalates to the FCIL.
- For each item on the FCIL, determine whether a finite life limit can
be derived from the crack growth analysis. If a life limit is
defined, move the item to the FLLIL and record the life limit in
cycles or flight hours; define the replacement or retirement plan.
Items on the FCIL without a life limit remain pending a compliance
demonstration or design change.
- Verify documentation for each item's category against the required
document set: PFCIL items need a screening record and a fracture
sensitivity justification; FCIL items additionally need a fracture
control analysis, an initial flaw assumption, and an inspection
plan; FLLIL items additionally need a life-limit calculation and a
replacement or retirement plan. Flag every missing document before
the list is submitted.
- Verify each list at the list level: confirm an issue number, an
approval date, and an authorised signatory are recorded. Confirm
that any item removed since the previous issue has a removal
justification on file. Confirm there are no duplicate item
identifiers within a list.
- Deliver the three lists to the programme configuration control
board together with the per-item documentation evidence package.
The lists are compliant when all documentation findings are
resolved and all list-level configuration control findings are
cleared.
Pitfalls
- Treating the PFCIL as a pass/fail verdict rather than a mandatory
screening list — every fracture-sensitive item with critical failure
consequence must appear on it regardless of whether compliance is
later demonstrated; an empty or minimal PFCIL almost always means
the screening was incomplete.
- Stopping at the PFCIL when items have not yet completed the
compliance step — items with no analysis or proof test on record
must stay on the PFCIL as pending, not be removed as "no concern".
- Confusing the FCIL and the FLLIL: an item with a defined life limit
belongs on the FLLIL rather than the FCIL; failure to make this
distinction misrepresents the programme's fracture risk profile.
- Accepting a list without an issue number or approval date as "draft
acceptable" — unsigned, unissued lists are not under configuration
control and cannot serve as the programme fracture control record.
- Removing an item from a list without a formal justification and
approval — undocumented removals break the traceability chain and
are treated as findings in any independent review or audit.
Behavior contract (gate 3)
The item categorization, list compilation, documentation check, and
configuration control check logic is exercised by the gate 3 contract
test: scripts/test_pfci_fci_flli_lists.py against
scripts/pfci_fci_flli_lists_logic.py (stdlib unittest, offline). Run:
python3 scripts/test_pfci_fci_flli_lists.py
Compliance
- ECSS standards are freely downloadable (ESA); cite the source and
paraphrase per standards-map.yaml.
- compliance: STANDARDS-REF, gated: false.
1---2name: pfci-fci-flli-lists3description: "Use when document, compile, and verify the ECSS-E-ST-32C clause 6.4.2 fracture control item lists (PFCIL, FCIL, FLLIL): categorize each structural item as Potentially Fracture Critical (PFCI), Fracture Critical (FCI), or Flight Limited Life (FLLI) based on fracture sensitivity and demonstrated compliance, confirm required documentation is present for each item category, and verify that each list carries an issue number, approval date, and authorised signatory before submission to configuration control. Trigger: ecss, e-st-32-structures-scope, fracture-control, pfcil, fcil, fllil, flight-limited-life, configuration-control, fracture-critical-items."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/pfci-fci-flli-lists15 domain: space-systems16 subdomain: ecss17 tags: [ecss, e-st-32-structures-scope, fracture-control, pfcil, fcil, fllil, flight-limited-life, configuration-control, fracture-critical-items]18 version: 0.1.019 author: Aero Agent Skills20---2122# ECSS Structures — PFCIL / FCIL / FLLIL Documentation and Configuration Control (space-systems/ecss/pfci-fci-flli-lists)2324Use when the task is compiling, verifying, and maintaining the fracture25control item lists required by ECSS-E-ST-32C clause 6.4.2 — the26Potentially Fracture Critical Items List (PFCIL), the Fracture Critical27Items List (FCIL), and the Flight Limited Life Items List (FLLIL) — and28placing them under configuration control.2930## Domain quick reference3132- Clause 6.4.2 of ECSS-E-ST-32C requires three controlled lists to be33 compiled, maintained, and submitted for approval at defined programme34 milestones. The PFCIL captures every structural item that is fracture35 sensitive and whose failure consequence is critical or catastrophic;36 the FCIL is the subset of PFCIL where fracture compliance cannot be37 demonstrated through analysis or proof test alone (safe-life ratio38 below 4.0); the FLLIL is the subset of FCIL where a specific life39 limit is assigned and the item must be retired or replaced before that40 limit is reached.41- An item enters the PFCIL through a screening step: if its material is42 fracture sensitive (low fracture toughness, pre-existing flaw43 sensitivity) and its failure consequence is critical or catastrophic,44 it is placed on the PFCIL. Items whose failure consequence is45 non-critical are exempt from all three lists.46- An item on the PFCIL escalates to the FCIL if the fracture control47 analysis or proof test cannot demonstrate a safe-life ratio of at48 least 4.0 (safe life divided by design life). Items that achieve49 the required ratio remain on the PFCIL as compliant and do not50 escalate further.51- An item on the FCIL receives a life limit when crack growth analysis52 yields a finite safe life shorter than the design life; that item53 then moves to the FLLIL and requires a defined replacement or54 retirement plan with a stated life limit in cycles or flight hours.55- Each list must carry an issue number, an approval date, and the name56 of the authorised signatory. Items added to or removed from a list57 require documented justification; removal without justification is a58 configuration control finding.5960## Workflow61621. Screen every primary and secondary structural item for fracture63 sensitivity (material fracture toughness, flaw sensitivity, stress64 concentration) and failure consequence (catastrophic, critical, or65 non-critical). Items with non-critical failure consequence are exempt66 and excluded from all three lists. Place all remaining items on the67 PFCIL with an entry recording the basis for their fracture-sensitive68 designation.692. For each item on the PFCIL, evaluate the fracture control compliance70 method: analyse using fracture mechanics (crack growth from the71 initial assumed flaw under the full load spectrum) or perform a72 proof test. Compute the safe-life ratio (demonstrated safe life73 divided by design life). An item achieving a ratio of 4.0 or greater74 is compliant and stays on the PFCIL without further escalation; an75 item below 4.0 escalates to the FCIL.763. For each item on the FCIL, determine whether a finite life limit can77 be derived from the crack growth analysis. If a life limit is78 defined, move the item to the FLLIL and record the life limit in79 cycles or flight hours; define the replacement or retirement plan.80 Items on the FCIL without a life limit remain pending a compliance81 demonstration or design change.824. Verify documentation for each item's category against the required83 document set: PFCIL items need a screening record and a fracture84 sensitivity justification; FCIL items additionally need a fracture85 control analysis, an initial flaw assumption, and an inspection86 plan; FLLIL items additionally need a life-limit calculation and a87 replacement or retirement plan. Flag every missing document before88 the list is submitted.895. Verify each list at the list level: confirm an issue number, an90 approval date, and an authorised signatory are recorded. Confirm91 that any item removed since the previous issue has a removal92 justification on file. Confirm there are no duplicate item93 identifiers within a list.946. Deliver the three lists to the programme configuration control95 board together with the per-item documentation evidence package.96 The lists are compliant when all documentation findings are97 resolved and all list-level configuration control findings are98 cleared.99100## Pitfalls101102- Treating the PFCIL as a pass/fail verdict rather than a mandatory103 screening list — every fracture-sensitive item with critical failure104 consequence must appear on it regardless of whether compliance is105 later demonstrated; an empty or minimal PFCIL almost always means106 the screening was incomplete.107- Stopping at the PFCIL when items have not yet completed the108 compliance step — items with no analysis or proof test on record109 must stay on the PFCIL as pending, not be removed as "no concern".110- Confusing the FCIL and the FLLIL: an item with a defined life limit111 belongs on the FLLIL rather than the FCIL; failure to make this112 distinction misrepresents the programme's fracture risk profile.113- Accepting a list without an issue number or approval date as "draft114 acceptable" — unsigned, unissued lists are not under configuration115 control and cannot serve as the programme fracture control record.116- Removing an item from a list without a formal justification and117 approval — undocumented removals break the traceability chain and118 are treated as findings in any independent review or audit.119120## Behavior contract (gate 3)121122The item categorization, list compilation, documentation check, and123configuration control check logic is exercised by the gate 3 contract124test: scripts/test_pfci_fci_flli_lists.py against125scripts/pfci_fci_flli_lists_logic.py (stdlib unittest, offline). Run:126python3 scripts/test_pfci_fci_flli_lists.py127128## Compliance129130- ECSS standards are freely downloadable (ESA); cite the source and131 paraphrase per standards-map.yaml.132- compliance: STANDARDS-REF, gated: false.