FRACAS Fundamentals
Quality & Inspection Standards
PRODUCTS CENTER
Get Custom Quote
PRODUCTS CENTER
FRACAS Fundamentals Under GJB9001C
FRACAS — Failure Reporting, Analysis, and Corrective Action Systems — is a foundational requirement of GJB9001C-2017 for all organizations in the military supply chain. Clause 10.2 mandates that "the organization shall establish and operate a product and service failure reporting and corrective action system in accordance with GJB 841." FRACAS is a closed-loop system designed to systematically identify, report, analyze, and correct failures that occur during product development, production, and field use. Its ultimate purpose is to prevent failure recurrence and drive continuous reliability growth.
For PCB manufacturers, FRACAS provides the essential discipline for capturing failures in materials, fabrication processes, assembly operations, and field performance. Without a functioning FRACAS, organizations cannot demonstrate effective failure management, corrective action, or reliability improvement — all of which are critical for military program compliance. This guide covers the fundamental principles of FRACAS, its relationship to GJB9001C and GJB 841, the closed-loop process, key roles and responsibilities, and practical implementation for PCB manufacturing.
Engineering Summary
- FRACAS is a mandatory closed-loop system per GJB9001C Clause 10.2 and GJB 841.
- Purpose: timely reporting, analysis, corrective action, and prevention of failure recurrence.
- Core activities: Failure Reporting, Failure Verification, Failure Analysis, Corrective Action, and Closure.
- FRACAS is GJB 450 Work Item 104 and the engine for reliability growth.
- For PCB manufacturers, FRACAS covers design defects, process variations, material nonconformances, assembly defects, and field failures.
- Key outputs include failure reports, analysis reports, corrective action records, and status summaries.
- FRACAS supports the "Double Five Return to Zero" for serious quality issues.
1. What Auditors Check — A Quick Overview
| Audit Focus | What External Auditors Verify | Expected Evidence |
|---|---|---|
| FRACAS Existence | Is a FRACAS established and documented per GJB 841? | FRACAS procedure, system documentation, plan |
| Failure Reporting | Are failures reported in a timely and complete manner? | Failure reports, logs, timeliness records |
| Root Cause Analysis | Is root cause analysis conducted and documented? | Analysis reports, 5 Whys, fishbone records |
| Corrective Action & Verification | Are corrective actions implemented and verified effective? | Corrective action records, verification results, closure reports |
| Closed-Loop Management | Is the system operating as a closed loop? | Tracking records, closure status, trend analysis |
| Documentation | Are failure records, analysis, and corrective action records retained? | Documented information, failure files, summary reports |
KEY INSIGHT:
FRACAS is a non-negotiable requirement under GJB9001C. Auditors will verify that a closed-loop failure reporting system is established and that failure data is used for corrective action and reliability improvement.
2. Standard Requirements — The Regulatory Basis
2.1 GJB9001C Clause 10.2 — Nonconformity and Corrective Action
GJB9001C-2017 Clause 10.2 explicitly requires the establishment of a FRACAS:
"The organization shall establish and operate a product and service failure reporting and corrective action system in accordance with GJB 841, and shall report quality-related issues concerning the final product and service, as well as corrective actions and their results, to the customer."
This makes FRACAS mandatory for all organizations supplying products or services to military programs.
2.2 GJB 841 — Failure Reporting, Analysis, and Corrective Action Systems
GJB 841-1990 is the foundational military standard for FRACAS. It defines the system's purpose, scope, and detailed requirements. Key aspects include:
- Purpose: To report product failures in a timely manner, analyze failure causes, formulate and implement effective corrective actions, prevent recurrence, and improve reliability and maintainability.
- Scope: Primarily applicable to the development phase, and also applicable to production and early use phases.
- General Requirements: A FRACAS plan shall be established (with purchaser approval), a failure review board shall be formed, and all failure documentation shall be preserved.
- Detailed Requirements: Cover failure reporting, failure verification, failure analysis, corrective action, and closure of failure reports.
Note: GJB 841A-2024 (effective March 2025) supersedes GJB 841-1990, expanding scope to "general quality characteristic issues." Organizations should transition to the new standard as applicable.
2.3 FRACAS as GJB 450 Work Item 104
FRACAS is also Work Item 104 of GJB 450《General Requirements for Equipment Reliability Work》— the foundational reliability work standard. It is the primary mechanism for capturing and correcting reliability deficiencies during development and production, thereby enabling reliability growth.
2.4 The "Double Five Return to Zero" Connection
For serious and major quality issues, GJB9001C requires "technical and management problem closure" — known as "Double Five Return to Zero" (双五归零). FRACAS is the operational tool that supports both:
- Technical Return to Zero : Accurate positioning, clear mechanism, problem reproduction, effective measures, and apply lessons learned.
- Management Return to Zero : Clear process, clear responsibility, measures implemented, serious handling, and improve regulations.
3. The Closed-Loop FRACAS Process — Five Core Steps
FRACAS operates on the principle of "information feedback, closed-loop control." The five core steps form a continuous cycle that drives improvement.
3.1 The Five Core Activities
| Step | Activity | Description | PCB Example |
|---|---|---|---|
| 1 | Failure Reporting | Timely and complete reporting of all failures with identification, conditions, and environment. | Report impedance failure on PCB lot during incoming inspection. |
| 2 | Failure Verification | Confirm reported failures against actual conditions; ensure accuracy. | Re-test failed PCB to confirm impedance out of spec. |
| 3 | Failure Analysis | Determine root cause(s) using structured methodologies (5 Whys, fishbone, etc.). | Trace impedance deviation to etching process parameter drift. |
| 4 | Corrective Action & Verification | Formulate, implement, and verify effectiveness of corrective actions. | Adjust etching parameters; re-test subsequent batches to confirm compliance. |
| 5 | Closure & Documentation | Close the item only after verification; retain all documentation and report to customer. | Close FRACAS item; archive records; notify customer of corrective action. |
3.2 Key Stakeholders and Their Roles
| Stakeholder | Responsibilities in FRACAS |
|---|---|
| Contractor | Establish FRACAS; ensure timely reporting, analysis, and correction; maintain documentation; implement corrective actions. |
| Subcontractor | Summarize failure information and report to contractor's FRACAS. |
| Purchaser/User | Provide timely failure feedback; participate in failure review board. |
| Failure Review Board | Review major failures, trends, and corrective actions; composed of design, production, reliability, quality representatives. |
3.3 Failure Review Board Responsibilities
- Regularly review failure information from development and production phases.
- Analyze failure trends and corrective action effectiveness.
- Conduct timely analysis of major failures, frequent failures, and failures of critical components.
- Propose corrective recommendations and require subcontractors to investigate failures.
- Investigate unresolved issues and report to higher authorities when necessary.
4. Implementation Essentials for PCB Manufacturers
4.1 Establishing a FRACAS
- Develop a documented FRACAS plan per GJB 841 — include reporting procedures, analysis methods, corrective action processes, and tracking mechanisms.
- Obtain purchaser approval of the FRACAS plan.
- Form a failure review board with representatives from design, process, quality, reliability, and production.
- Define reporting criteria — what failures must be reported, when, and in what format.
4.2 Failure Reporting and Tracking
- Use standardized failure report forms with all required fields (item identification, failure description, test conditions, observer, environment).
- Implement a unique numbering system for each failure report.
- Maintain a central log or database for tracking all open and closed items.
- Ensure timely reporting — failures should be reported as soon as they are detected.
4.3 Root Cause Analysis
- Use structured methodologies such as 5 Whys, fishbone diagrams, or FMEA for root cause analysis.
- Ensure analysis identifies the underlying cause — not just symptoms.
- Document analysis findings and conclusions in a failure analysis report.
- For serious failures, conduct in-depth investigation involving cross-functional teams.
4.4 Corrective Action and Verification
- Formulate corrective actions by the responsible organization — design changes, process adjustments, training, or specification updates.
- Follow engineering change procedures for any design or process changes.
- Implement corrective actions and verify effectiveness through re-test, re-inspection, or analysis.
- Do not close FRACAS items until corrective action is verified effective.
4.5 Documentation and Customer Communication
- Retain all failure reports, analysis reports, corrective action records, and closure documentation.
- Prepare periodic failure summary or status reports for management and customer review.
- Report quality-related issues and corrective actions to customers as required by Clause 10.2.
- Ensure all records are complete, traceable, and retained per requirements.
5. PCB-Specific FRACAS Scenarios — Practical Examples
5.1 Process Nonconformance — Plating Thickness Variation
| FRACAS Element | Description |
|---|---|
| Failure Report | Copper plating thickness below specification (target 25μm, measured 18μm) on PCB lot during microsection inspection. |
| Verification | Re-measured on multiple samples using calibrated equipment — confirmed thickness below specification. |
| Root Cause Analysis (5 Whys) | Why? → Plating time insufficient. Why? → Timer malfunction. Why? → Preventive maintenance not performed. Why? → Maintenance schedule not followed. Why? → No automated reminder system. |
| Corrective Action | Repair plating timer; implement preventive maintenance schedule with automated reminders; update maintenance procedure; retrain maintenance staff. |
| Verification | Next three production lots measured — plating thickness within specification (24.5-25.5μm). |
| Closure | FRACAS item closed; documentation archived; customer notified of corrective action. |
5.2 Material Nonconformance — Laminate Delamination
| FRACAS Element | Description |
|---|---|
| Failure Report | Laminate delamination observed on PCB assembly during thermal cycling test (failure after 50 cycles). |
| Verification | Microsection analysis confirmed delamination at multiple locations; re-test on additional samples confirmed failure pattern. |
| Root Cause Analysis (Fishbone) | Materials: Low Tg laminate (Tg=150°C) not suitable for high-temperature application; Methods: Lamination profile not optimized for this material. |
| Corrective Action | Replace laminate with high-Tg material (Tg≥170°C); revise lamination profile; re-qualify material and process; update material specification. |
| Verification | Re-test with new material — 200 thermal cycles with no delamination; qualification testing passed. |
| Closure | FRACAS item closed; material specification updated; customer notified of design change and re-qualification. |
6. Key Control Points in FRACAS Management
6.1 Plan and Procedure
- Documented FRACAS plan approved by purchaser.
- Clear procedures for reporting, analysis, corrective action, and closure.
- Defined roles and responsibilities.
6.2 Reporting Discipline
- All failures reported without delay.
- Complete and accurate information in every report.
- Standardized forms and numbering.
6.3 Analysis Rigor
- Root cause analysis using structured methodologies.
- Cross-functional investigation for serious failures.
- Documented analysis findings.
6.4 Corrective Action Discipline
- Corrective actions address root causes — not symptoms.
- Effectiveness verified before closure.
- Changes follow engineering change procedures.
6.5 Closed-Loop Tracking
- Each item tracked from opening to closure.
- Periodic status reviews by failure review board.
- Trend analysis to identify systemic issues.
7. Audit Preparation Checklist for PCB Manufacturers
| # | Check Item | Clause/Standard | Status | Notes |
|---|---|---|---|---|
| FRACAS Plan | ||||
| 1 | FRACAS plan is documented and approved by purchaser | GJB 841 3.2 | ☐ | |
| 2 | Failure review board is established | GJB 841 3.3 | ☐ | |
| Reporting | ||||
| 3 | All failures are reported in a timely manner | GJB 841 4.1 | ☐ | |
| 4 | Failure reports are complete and accurate | GJB 841 4.1 | ☐ | |
| Analysis | ||||
| 5 | Failure verification is conducted | GJB 841 4.2 | ☐ | |
| 6 | Root cause analysis is conducted and documented | GJB 841 4.3 | ☐ | |
| Corrective Action | ||||
| 7 | Corrective actions are formulated and implemented | GJB 841 4.4 | ☐ | |
| 8 | Corrective action effectiveness is verified | 10.2 | ☐ | |
| Closure & Documentation | ||||
| 9 | FRACAS items are closed only after verification | GJB 841 4.5 | ☐ | |
| 10 | All failure documentation is retained | GJB 841 3.4 | ☐ | |
| 11 | Customer is notified of quality issues and corrective actions | 10.2 | ☐ | |
8. Common Audit Findings and How to Avoid Them
| Finding | Why It Happens | How to Avoid |
|---|---|---|
| "No FRACAS established" | System not recognized as mandatory | Establish FRACAS per GJB 841; document plan and obtain approval |
| "Failures not reported" | Informal handling without documentation | Implement timely reporting; use standardized forms |
| "No root cause analysis" | Failures addressed at symptom level | Require structured root cause analysis (5 Whys, fishbone) |
| "Corrective actions not verified" | Actions closed without confirmation | Verify effectiveness before closure |
| "No closed-loop tracking" | Items opened but never closed | Maintain tracking log; review status periodically |
| "Records incomplete" | Documentation gaps | Retain complete files; follow retention requirements |
9. Frequently Asked Questions
What is FRACAS?
FRACAS stands for Failure Reporting, Analysis, and Corrective Action Systems. It is a closed-loop system mandated by GJB9001C Clause 10.2 for reporting, analyzing, and correcting product failures to prevent recurrence and improve reliability.
Why is FRACAS required?
FRACAS is required to ensure that failures are systematically captured, analyzed, and corrected, thereby driving reliability growth and preventing recurrence. It is a mandatory requirement for all organizations in the military supply chain.
What are the five core activities of FRACAS?
The five core activities are: Failure Reporting, Failure Verification, Failure Analysis, Corrective Action and Verification, and Closure and Documentation.
What is the failure review board?
The failure review board is a cross-functional team (design, production, reliability, quality) responsible for reviewing major failures, failure trends, and corrective actions. It ensures that failures are properly investigated and addressed.
How does FRACAS relate to "Double Five Return to Zero"?
FRACAS is the operational tool that supports the "Double Five Return to Zero" for serious quality issues — covering both technical return to zero and management return to zero.
Is FRACAS applicable to PCB manufacturing?
Yes. PCB manufacturers must establish a FRACAS to capture failures in design, materials, fabrication processes, assembly, testing, and field use. It is essential for demonstrating corrective action and reliability improvement.
What documentation is required for FRACAS?
Required documentation includes: failure reports, failure analysis reports, corrective action implementation reports, and periodic failure summary or status reports. All records must be retained.
What is GJB 841A-2024?
GJB 841A-2024 is the updated version of the standard, effective March 2025, that expands the scope from "failure" reporting to "general quality characteristic issues" reporting. Organizations should monitor this transition.
Related Standards & Topics
PCB and PCBA Manufacturing for Military and Aerospace Programs
UltroNiu Electronics Group provides PCB and PCBA manufacturing services with GJB9001C-compliant FRACAS implementation. Contact our engineering team for program-specific failure management and corrective action requirements.
Request Engineering ReviewReferences: GJB9001C-2017 Clause 10.2 (Central Military Commission Equipment Development Department); GJB 841-1990 Failure Reporting, Analysis, and Corrective Action Systems; GJB 841A-2024 General Quality Characteristic Issue Reporting, Analysis, and Corrective Action Systems; GJB 450-2008 Equipment Reliability Work General Requirements (Work Item 104). FRACAS definition and purpose sourced from GJB 841-1990. General and detailed requirements sourced from GJB 841-1990. "Double Five Return to Zero" requirements sourced from GJB9001C-2017 Clause 10.2. PCB-specific FRACAS practices based on industry best practices for military and aerospace PCB manufacturing. Courtesy of UltroNiu Engineering Knowledge Center.
Get Custom Quote
PRODUCTS CENTER
World-class PCB & PCBA manufacturer focused on high-frequency and high-reliability boards for defense, aerospace, automotive and industrial electronics.
You can unsubscribe at any time with a single click.
Copyright © 2025 UltroNiu Electronics Group All Rights reserved.
Sorry, there is currently no content in the current column
You can check other sections
Business License