PCBA failure analysis uses electrical testing, visual inspection, X-ray imaging, microscopy, material analysis, and manufacturing records to determine why a circuit board failed.
A good investigation does more than locate a damaged component. It identifies the failure mechanism, confirms the underlying cause, evaluates affected products, and verifies corrective action.
Replacing a failed component may restore board operation, but it does not prove why the component failed. The true cause may involve soldering, PCB fabrication, contamination, electrical overstress, firmware, thermal design, component quality, or customer use.
For OEM buyers, an accurate root cause is essential before approving rework, restarting production, or accepting another shipment.
What Is PCBA Failure Analysis?
PCBA failure analysis is a structured investigation used to determine what failed, where it failed, how the failure occurred, and why the process allowed it to happen.
The investigation may cover:
- Printed circuit boards
- Electronic components
- Solder joints
- Connectors
- Cables
- Firmware
- Test fixtures
- Mechanical structures
- Manufacturing processes
- Product operating conditions
NASA describes failure analysis as determining what, why, and how a component, system, or structure failed. The results support product improvements and corrective actions.
A complete investigation should answer five questions:
- What is the verified failure symptom?
- Which physical or electrical mechanism created it?
- What caused that mechanism?
- Which products may have the same risk?
- Which corrective action prevents recurrence?
What Is The Difference Between A Defect And A Failure?
A defect is a condition that does not meet a specified requirement. A failure occurs when the product cannot perform a required function.
A defect does not always create an immediate failure. A product can also fail without displaying an obvious visual defect.
Examples include:
- A solder void may meet acceptance criteria but still affect thermal performance.
- A cosmetic residue may look unacceptable without affecting reliability.
- A cracked via may remain invisible while causing an intermittent open.
- Incorrect firmware may cause a functional failure on a physically acceptable PCBA.
- A damaged component may pass visual inspection but fail under electrical load.
The PCB assembly defects guide explains common manufacturing defects, inspection methods, and prevention strategies.
Failure analysis must connect physical evidence with the reported symptom. Finding an abnormal feature does not automatically prove causation.
Why Is PCBA Failure Analysis Important?
Without root cause analysis, the manufacturer may repeatedly repair the same symptom while the underlying problem continues.
Accurate failure analysis can help:
- Contain affected products
- Reduce repeat defects
- Prevent field returns
- Improve manufacturing yield
- Verify supplier quality
- Identify design weaknesses
- Improve test coverage
- Support customer communication
- Reduce warranty costs
- Protect product reliability
A failed circuit board may also indicate a wider process problem. One returned unit could represent an isolated event, or it could identify risk across an entire production lot.
The investigation should determine which conclusion the evidence supports.
When Should A PCBA Failure Investigation Begin?
The investigation should begin when the team receives a credible failure report.
Possible triggers include:
- Incoming inspection failure
- First article failure
- Programming failure
- In-circuit test failure
- Functional test failure
- Burn-in failure
- Environmental test failure
- Production yield decline
- Customer return
- Field failure
- Repeated intermittent behavior
- Safety-related incident
The team should preserve evidence immediately. Continued powering, cleaning, soldering, or mechanical handling can alter the failure condition.
Stop Uncontrolled Rework
Operators should not immediately replace components or reflow suspicious solder joints.
These actions may:
- Remove the original failure
- Create new damage
- Destroy residue evidence
- Change solder-joint structure
- Reset an intermittent connection
- Prevent meaningful analysis
If rework is necessary for business reasons, the team should first document the original condition and obtain approval.
What Information Should Be Collected Before Analysis?
A reliable investigation requires more than the failed board.
The manufacturer should collect:
- Product number
- PCBA revision
- Serial number
- Production lot
- Failure date
- Failure location
- Reported symptom
- Operating conditions
- Test results
- Firmware version
- Component traceability
- Rework history
- Environmental exposure
- Customer photographs
- Returned accessories
- Power-supply information
- Cable and connector information
Capture The Exact Failure Symptom
“Board does not work” provides too little information.
A useful symptom description may state:
- The 5 V output drops to 2.1 V after ten minutes.
- Communication stops above 70°C.
- The board resets during motor startup.
- Channel three reports unstable sensor values.
- The unit draws 600 mA instead of 120 mA.
- The fault occurs only after vibration.
Precise symptoms guide test selection and reduce unnecessary analysis.
Record Customer Use Conditions
The failure may depend on:
- Input voltage
- Load current
- Temperature
- Humidity
- Installation orientation
- Connected equipment
- Cable length
- Power sequence
- Firmware settings
- Mechanical vibration
A laboratory may not reproduce the issue if it tests the board under different conditions.
How Should Failed PCBAs Be Handled And Preserved?
The failed assembly should receive a unique identification number. The team should also record every person who handles it.
Preservation steps may include:
- Use ESD-safe packaging
- Avoid unnecessary power application
- Protect loose particles
- Preserve contamination
- Avoid cleaning
- Do not remove labels
- Photograph all sides
- Record connector positions
- Keep associated cables
- Control storage conditions
If moisture or contamination is part of the suspected cause, improper storage can change the evidence.
A chain-of-custody record becomes especially important for safety, regulatory, legal, or high-value investigations.
What Are The Main Steps In PCBA Failure Analysis?
A practical investigation usually follows a controlled sequence.
- Verify the reported symptom.
- Collect production and field history.
- Preserve the failed sample.
- Compare it with known-good units.
- Isolate the failing circuit.
- Perform non-destructive inspection.
- Develop failure hypotheses.
- Select targeted tests.
- Perform destructive analysis when necessary.
- Confirm the failure mechanism.
- Identify the root cause.
- Define containment and corrective action.
- Verify the corrective action.
- Issue the final report.
The sequence may change according to the product and risk. However, the team should normally complete non-destructive analysis before destroying the sample.
How Do Engineers Reproduce A PCBA Failure?
Reproducing the symptom provides strong evidence that the laboratory understands the failure conditions.
The reproduction plan may control:
- Supply voltage
- Current limit
- Electrical load
- Temperature
- Humidity
- Vibration
- Power sequence
- Connected peripherals
- Firmware
- Test duration
- Mechanical position
Avoid Causing Additional Damage
Engineers should use safe current limits and controlled power supplies.
Repeatedly applying full power to a shorted board can:
- Burn damaged traces
- Destroy components
- Remove evidence
- Create carbonized material
- Produce secondary failures
The first objective is to observe and isolate the original failure.
Intermittent Failure Reproduction
Intermittent failures may require:
- Thermal cycling
- Controlled board flexing
- Vibration
- Connector movement
- Long-duration operation
- Power cycling
- High-speed event logging
- Continuous resistance monitoring
The team should avoid random tapping, bending, or heating without documentation. Uncontrolled stress produces weak evidence.
What Is Failure Isolation?
Failure isolation narrows the problem from the complete product to a specific circuit, net, component, connection, or software function.
Engineers may begin with:
- Power rails
- Clock signals
- Reset circuits
- Communication buses
- Analog inputs
- Output stages
- Thermal protection
- Memory
- Connectors
Useful tools include:
- Digital multimeters
- Oscilloscopes
- Logic analyzers
- Power analyzers
- Current-limited supplies
- Boundary scan
- In-circuit testers
- Functional test fixtures
- Thermal cameras
The in-circuit testing guide explains how ICT checks component values, shorts, opens, polarity, and electrical connectivity.
Why Should Non-Destructive Testing Come First?
Non-destructive methods preserve the board for additional investigation.
They can locate likely failure areas before the team cuts, removes, or opens anything.
Common methods include:
- Visual inspection
- Microscopy
- X-ray inspection
- Computed tomography
- Electrical testing
- Thermal imaging
- Acoustic inspection
- Functional comparison
- Ultraviolet inspection
No single method can detect every defect. Engineers should choose methods that match the suspected failure mechanism.
How Does Visual Inspection Support Failure Analysis?
Visual inspection often provides the fastest first evidence.
Inspectors should examine:
- Burn marks
- Cracked components
- Missing parts
- Contamination
- Corrosion
- Lifted leads
- Damaged connectors
- Broken wires
- Discolored solder joints
- Foreign material
- Coating defects
- Mechanical impact
Use Magnification
Microscopy can reveal details that the unaided eye misses.
Inspectors may find:
- Hairline cracks
- Incomplete wetting
- Pad damage
- Component termination cracks
- Solder balls
- Metal debris
- Corrosion products
Photographs should include an overview and detailed images. A scale or magnification reference improves the report.
Visual Abnormality Does Not Prove Root Cause
A darkened solder joint may look suspicious but remain electrically sound. A nearby cracked via may be the real failure.
The team should correlate visual evidence with electrical measurements and the failure symptom.
How Does X-Ray Inspection Find Hidden PCBA Failures?
X-ray inspection helps evaluate solder joints hidden under component bodies.
It can support analysis of:
- BGAs
- QFNs
- DFNs
- Bottom-terminated components
- Through-hole barrels
- Connectors
- Large thermal pads
- Internal PCB structures
X-ray may reveal:
- Solder bridging
- Voids
- Missing solder
- Head-in-pillow conditions
- Misalignment
- Foreign material
- Barrel-fill problems
- Cracked structures in favorable orientations
The PCB X-ray inspection guide explains 2D X-ray, angled inspection, and computed tomography.
X-Ray Limitations
A crack aligned with the X-ray beam may remain difficult to see. Overlapping structures can also hide small defects.
A two-dimensional image compresses several layers into one view. Computed tomography can provide more spatial information, but it costs more and may require longer scanning.
X-ray results should support, not replace, electrical and physical evidence.
How Does Thermal Imaging Locate Electrical Failures?
A thermal camera shows surface-temperature differences while the assembly operates.
It can help locate:
- Short circuits
- High-resistance connections
- Overloaded components
- Excessive current paths
- Thermal-design weaknesses
- Components that fail after heating
Engineers may also apply a controlled voltage and observe where heat develops.
Thermal Imaging Limitations
A component may appear hot because another circuit drives it incorrectly. The hot component is not always the root cause.
Surface finish, airflow, viewing angle, and emissivity can also affect the measured temperature.
The team should confirm thermal findings with electrical measurements.
What Is Comparison Testing?
Comparison testing measures the failed board against a known-good assembly.
Engineers may compare:
- Resistance
- Diode readings
- Current consumption
- Waveforms
- Power rails
- Thermal patterns
- Signal timing
- Component values
- X-ray images
A comparison board should match the same design and firmware revision.
Golden Sample Limitations
A “golden sample” may contain undocumented rework or component substitutions. It may also represent a different production lot.
The team should verify its configuration before treating it as a perfect reference.
Difference does not always mean defect. Component tolerances can create normal variation.
Which Destructive Analysis Methods Are Used?
Destructive analysis exposes internal structures that non-destructive methods cannot fully evaluate.
Common methods include:
- Cross-sectioning
- Dye-and-pry analysis
- Component decapsulation
- Scanning electron microscopy
- Energy-dispersive X-ray spectroscopy
- Chemical analysis
- Metallographic examination
- PCB layer removal
The team should use destructive methods only after documenting the original condition.
What Is PCB Cross-Section Analysis?
Cross-section analysis cuts through a selected area, mounts the sample, polishes the surface, and examines the internal structure.
It can evaluate:
- Solder-joint structure
- Intermetallic layers
- Plated-through holes
- Microvias
- Copper thickness
- Barrel cracks
- Pad separation
- Delamination
- Component terminations
Cross-Section Location Matters
A cross-section examines only a narrow physical area. Cutting beside the actual crack can produce a misleading result.
Engineers should use X-ray, electrical measurements, and photographs to select the exact section location.
Cross-Sectioning Destroys Evidence
Once cut, the board cannot return to its original state. The team should retain the remaining sample and document the cutting orientation.
What Is Dye-And-Pry Analysis?
Dye-and-pry analysis helps examine hidden solder-joint separation under area-array packages.
A typical process introduces dye into cracks before mechanically separating the component from the board.
The dye can indicate where separation existed before removal.
This method may support analysis of:
- BGA solder cracks
- Pad cratering
- Interfacial separation
- Mechanical overstress
- Drop-related damage
Improper dye penetration, drying, or separation can create artifacts. Trained personnel should interpret the resulting fracture surfaces.
How Does Electron Microscopy Support Failure Analysis?
Scanning electron microscopy provides high-magnification images with greater depth of field than conventional optical microscopy.
It can help examine:
- Fracture surfaces
- Intermetallic structures
- Corrosion products
- Microcracks
- Component damage
- Material interfaces
Energy-dispersive X-ray spectroscopy can identify elements within selected areas. This capability can help investigate contamination, corrosion, and foreign material.
NIST describes scanning electron microscopy and related techniques as useful for defect analysis and advanced materials characterization in its electron microscopy overview.
Elemental detection does not always identify the exact chemical compound or contamination source. Engineers should combine microscopy with process history and other analysis.
What Are The Most Common PCBA Failure Modes?
| Failure Mode | Possible Causes | Useful Analysis Methods |
|---|---|---|
| Open Circuit | Cracked joint, broken trace, via failure | Resistance test, X-ray, cross-section |
| Short Circuit | Solder bridge, debris, damaged component | Current limiting, thermal imaging, microscopy |
| Intermittent Connection | Fatigue crack, connector fretting, pad damage | Continuous monitoring, vibration, thermal cycling |
| Parametric Drift | Component damage, contamination, aging | Functional comparison, component analysis |
| Excessive Current | Shorted IC, wrong component, design error | Thermal imaging, rail isolation |
| Communication Failure | Clock, firmware, signal integrity, connector | Oscilloscope, logic analyzer, comparison |
| Corrosion Failure | Moisture, ionic residue, chemical exposure | Microscopy, ionic analysis, material analysis |
| Mechanical Failure | Impact, vibration, board flex | X-ray, dye-and-pry, cross-section |
The same symptom can have several causes. For example, a communication failure may result from firmware, a cracked oscillator joint, unstable power, or connector damage.
How Are Solder-Joint Failures Analyzed?
Solder-joint failures may involve:
- Insufficient solder
- Non-wetting
- Cracking
- Brittle fracture
- Head-in-pillow
- Pad lifting
- Excessive voiding
- Intermetallic growth
- Fatigue
- Mechanical overstress
The investigation should review:
- Pad design
- Stencil design
- Solder paste
- Paste volume
- Placement
- Reflow profile
- Component finish
- PCB finish
- Board flex
- Environmental exposure
- Rework history
The PCB reflow soldering guide explains thermal profiling, paste behavior, wetting, and common SMT soldering problems.
Do Not Assume Every Crack Comes From Reflow
Cracks can also develop during:
- Depanelization
- Connector insertion
- Screw installation
- Drop impact
- Vibration
- Thermal cycling
- Rework
- Customer handling
Fracture location and surface characteristics can help identify the likely mechanism.
How Are BGA Failures Investigated?
BGA failures require special attention because the solder joints remain hidden under the package.
Possible BGA failure modes include:
- Solder bridging
- Head-in-pillow
- Open joints
- Pad cratering
- Warpage-related separation
- Voiding
- Brittle interfacial fracture
- Package cracking
- Underfill defects
A BGA investigation may use:
- Electrical net testing
- 2D X-ray
- Angled X-ray
- Computed tomography
- Thermal cycling
- Dye-and-pry analysis
- Cross-sectioning
- Package removal
Removing the BGA too early can destroy fracture evidence. The team should complete non-destructive examination first.
How Are PCB Via And Microvia Failures Analyzed?
Via failures can create permanent or intermittent opens.
Possible causes include:
- Insufficient copper plating
- Barrel cracking
- Corner cracking
- Resin recession
- Pad separation
- Stacked-microvia weakness
- Thermal fatigue
- Material delamination
Standard electrical tests may miss a microvia that opens only after reflow or temperature cycling.
IPC previously issued an official warning about microvia reliability. It noted that some failures appeared after assembly, environmental screening, or field use, even though boards had passed traditional acceptance testing.
Analysis may require:
- Daisy-chain resistance monitoring
- Thermal stress
- X-ray or CT
- Microsectioning
- Material review
- Fabrication-record review
How Are Component Failures Investigated?
A failed component should not automatically be classified as a supplier defect.
Possible causes include:
- Incorrect part
- Counterfeit component
- Electrical overstress
- Electrostatic discharge
- Excessive temperature
- Moisture damage
- Mechanical stress
- Reverse polarity
- Overvoltage
- Firmware misuse
- Internal manufacturing defect
The investigation should compare the component’s ratings with actual circuit conditions.
Component Replacement As A Diagnostic Tool
Replacing a suspected component can confirm that the failure follows that location.
However, replacement alone does not identify the original cause.
The team should preserve the removed component for:
- External inspection
- Electrical characterization
- X-ray
- Decapsulation
- Supplier analysis
- Material examination
How Can Engineers Distinguish ESD From Electrical Overstress?
Electrostatic discharge and electrical overstress can both damage semiconductor structures.
ESD usually involves a short-duration electrostatic event. Electrical overstress may involve excessive voltage, current, power, or temperature over a longer period.
Possible evidence includes:
- Damage location
- Burn pattern
- Circuit protection
- Operating history
- Test conditions
- Semiconductor microscopy
- ESD handling records
- Power-supply logs
Physical damage patterns can overlap. Engineers should avoid claiming ESD or overstress without supporting evidence.
A statement such as “component electrically damaged” may be more accurate when the available evidence cannot identify the exact event.
How Does Contamination Cause PCBA Failure?
Ionic contamination, flux residue, fingerprints, and environmental chemicals can contribute to:
- Corrosion
- Leakage current
- Reduced insulation resistance
- Electrochemical migration
- Dendritic growth
- Sensor drift
- High-impedance circuit failure
The investigation may use:
- Visual microscopy
- Ultraviolet inspection
- Localized extraction
- Ion chromatography
- Surface insulation testing
- Elemental analysis
Cleaning the failed board before analysis can remove important evidence.
Conformal coating may also trap contamination against the PCB surface. The PCB conformal coating guide explains how cleanliness affects adhesion and long-term protection.
Can Firmware Or Software Cause A PCBA Failure?
Yes. Not every apparent circuit board failure has a physical manufacturing cause.
Firmware-related symptoms may include:
- Unexpected resets
- Communication failure
- Incorrect output
- Memory corruption
- Timing errors
- Sensor-calibration errors
- Watchdog events
- Boot failure
The investigation should preserve:
- Firmware version
- Configuration
- Error logs
- Programming records
- Calibration data
- Bootloader version
Replacing the PCBA may appear to solve the problem because the replacement contains different firmware.
The team should test hardware and software hypotheses separately.
Can A Test Fixture Cause False PCBA Failures?
Yes. Test fixtures, cables, probes, software, and power supplies can create false failures.
Possible fixture problems include:
- Worn test probes
- Dirty contacts
- Loose cables
- Incorrect software limits
- Ground loops
- Inadequate power
- Unstable communication
- Incorrect board support
- Misaligned connectors
Before rejecting a PCBA lot, the team should verify the test system with controlled reference units.
The PCBA functional testing guide explains fixture maintenance, test limits, coverage, and false-failure control.
What Is The Difference Between Failure Analysis And FMEA?
Failure analysis investigates a failure that has already occurred.
Failure Mode and Effects Analysis predicts how a design or process could fail before the failure occurs.
IEC 60812:2018 describes how organizations plan, perform, document, and maintain FMEA and FMECA activities.
The two processes support each other.
Failure-analysis results can update:
- Design FMEA
- Process FMEA
- Control plans
- Inspection plans
- Test coverage
- Work instructions
- Supplier controls
A previously unknown failure mechanism should not remain only inside one customer-return report.
How Do Engineers Determine The Root Cause?
A root cause is the underlying condition that allowed the failure to occur.
Useful analysis tools include:
- Five Whys
- Fishbone diagrams
- Fault-tree analysis
- Is-and-is-not analysis
- Process mapping
- Design-of-experiments
- Statistical comparison
These tools organize thinking, but they do not replace physical evidence.
Separate Failure Mechanism From Root Cause
The failure mechanism describes how the item failed.
Example:
- Failure mechanism: cracked BGA solder joint.
- Direct cause: excessive PCB bending.
- Root cause: the depanelization fixture lacked support near the component.
- System cause: the process-control plan did not include board-strain verification.
Stopping at “cracked solder joint” leaves the real process problem unresolved.
Verify Each Hypothesis
A strong investigation tests competing explanations.
For example:
- If reflow caused the crack, similar joints may show related evidence.
- If depanelization caused it, strain location should match the fracture.
- If field impact caused it, the enclosure may show mechanical evidence.
The final conclusion should explain all verified facts with the fewest unsupported assumptions.
What Is An 8D Failure Analysis Report?
An 8D report organizes containment, root cause, corrective action, and verification.
A typical structure includes:
- D1: Establish the team
- D2: Describe the problem
- D3: Implement containment
- D4: Identify root cause
- D5: Select corrective action
- D6: Implement and validate action
- D7: Prevent recurrence
- D8: Recognize completion
An 8D template does not guarantee a correct investigation. A polished report can still contain an unsupported root cause.
The report should include evidence, measurements, images, and verification results.
What Is The Difference Between Containment And Corrective Action?
Containment protects the customer while the investigation continues.
Possible containment actions include:
- Stop shipment
- Quarantine inventory
- Increase inspection
- Screen finished products
- Replace suspect material
- Notify affected customers
- Review work in progress
Corrective action removes or controls the confirmed root cause.
Examples include:
- Modify stencil design
- Adjust the reflow profile
- Improve PCB support
- Change a component
- Update firmware
- Add test coverage
- Improve cleaning
- Revise work instructions
- Qualify a new supplier
Containment may detect bad units without preventing new defects. The team needs both short-term protection and long-term correction.
How Should Corrective Action Be Verified?
The manufacturer should demonstrate that the corrective action prevents recurrence without creating new problems.
Verification may include:
- Repeat production trials
- First article inspection
- Capability analysis
- Environmental testing
- Functional testing
- X-ray comparison
- Cross-section analysis
- Extended monitoring
- Customer approval
A small successful trial may not prove long-term process stability. The verification plan should match the failure risk.
The PCBA first article inspection guide explains how buyers confirm materials, workmanship, documentation, and process readiness before larger production.
How Does Traceability Improve Failure Analysis?
Traceability helps determine which materials, processes, and products share the same risk.
Useful records include:
- PCB lot
- Component lot
- Date code
- Feeder position
- SMT machine
- Reflow oven
- Thermal profile
- Operator
- Inspection results
- Test data
- Rework history
- Shipment number
The PCBA traceability guide explains how production records connect components, machines, operators, testing, rework, and delivery.
Without traceability, the manufacturer may need to contain a larger quantity because it cannot isolate affected units.
What Should A PCBA Failure Analysis Report Include?
A professional report should include:
- Case number
- Product and revision
- Sample identification
- Failure description
- Customer conditions
- Production history
- Analysis sequence
- Test equipment
- Inspection images
- Electrical data
- Failure mechanism
- Root cause
- Affected scope
- Containment action
- Corrective action
- Verification results
- Remaining risks
- Final conclusion
The report should separate confirmed facts, engineering interpretations, and unverified possibilities.
Use Clear Confidence Language
Suitable terms include:
- Confirmed
- Consistent with
- Probable
- Possible
- Not supported
- Inconclusive
Avoid stating certainty when the evidence supports only probability.
What Are The Most Common Failure Analysis Mistakes?
Reworking Before Documenting
Reflowing or replacing parts can destroy the original evidence.
Stopping At The Failed Component
A damaged IC may be the result of overvoltage, poor grounding, or thermal design.
Blaming The Operator Without Evidence
“Operator error” often hides inadequate instructions, fixtures, training, or process controls.
Using Only Visual Inspection
Hidden cracks, internal component damage, and firmware problems require additional methods.
Confusing Correlation With Cause
An unusual feature near the failure does not automatically create the failure.
Testing Only At Room Temperature
Intermittent problems may require temperature, vibration, load, or time to appear.
Ignoring Test Equipment
A fixture fault can produce false failures across acceptable boards.
Declaring “No Trouble Found”
A laboratory may fail to reproduce the customer’s conditions. “No trouble found” does not prove that the original failure never occurred.
How Long Does PCBA Failure Analysis Take?
Analysis time depends on:
- Failure complexity
- Symptom repeatability
- Sample condition
- Available records
- Required equipment
- External laboratory work
- Destructive testing
- Component supplier response
- Corrective-action validation
A visible solder bridge may require only a short investigation. An intermittent field failure may take several weeks.
Buyers should distinguish between:
- Initial containment report
- Preliminary analysis
- Confirmed root cause
- Corrective-action verification
- Final closure
Rushing the final conclusion can produce an incorrect root cause and repeated failure.
How Much Does PCBA Failure Analysis Cost?
Cost depends on:
- Engineering time
- Test-fixture development
- X-ray or CT inspection
- Environmental testing
- Cross-sectioning
- Dye-and-pry analysis
- Electron microscopy
- Component decapsulation
- External laboratory fees
- Report requirements
High-level microscopy and material analysis cost more than basic electrical troubleshooting.
However, incomplete analysis can create larger expenses through repeated returns, production stoppages, warranty claims, and customer dissatisfaction.
What Information Should Buyers Provide With A Failed PCBA?
Buyers should provide:
- Clear symptom description
- Product serial number
- Installation location
- Operating voltage
- Connected load
- Firmware version
- Temperature and humidity
- Time to failure
- Failure frequency
- Photographs
- Error logs
- Related cables
- Power supply
- Previous repair history
- Requested report format
Do not remove components or clean the board unless the manufacturer requests it.
Original condition provides the best opportunity to identify the failure mechanism.
How Should Buyers Evaluate A PCBA Manufacturer’s Failure Analysis Capability?
Ask the supplier:
- Can you reproduce functional failures?
- Do you preserve failed samples?
- Can you perform X-ray inspection?
- Can you isolate power-rail faults?
- Do you support cross-sectioning?
- Can you access external material-analysis laboratories?
- How do you manage 8D reports?
- Can you trace samples to production records?
- How do you verify corrective action?
- Can you distinguish containment from root cause?
- How do you communicate inconclusive results?
- How do you protect confidential design information?
A reliable supplier should show evidence rather than immediately assign blame.
Frequently Asked Questions About PCBA Failure Analysis
Can X-Ray Inspection Find Every PCB Failure?
No. X-ray works well for many hidden structural defects but cannot identify every crack, firmware issue, electrical defect, or contamination problem.
Can A Failed Component Prove The Component Supplier Is Responsible?
No. The surrounding circuit may have exposed the component to excessive voltage, current, heat, or mechanical stress.
Should A Failed Board Be Cleaned Before Analysis?
Usually not. Cleaning can remove residue, corrosion products, and contamination evidence. The analysis team should approve any cleaning.
Can Reflowing A BGA Confirm A Solder-Joint Failure?
Temporary recovery after reflow suggests a connection-related issue, but it does not prove the original failure mechanism. Reflow also destroys useful evidence.
What Does “No Fault Found” Mean?
It means the laboratory did not reproduce or detect the failure under its test conditions. It does not necessarily mean the customer’s report was incorrect.
Can Functional Testing Detect Latent Failures?
Functional testing detects many current failures. It may not reveal every weakened component, intermittent joint, or condition-dependent defect.
Is Cross-Section Analysis Always Required?
No. Engineers use it when internal physical evidence is necessary. Electrical measurements, X-ray, or process records may resolve simpler cases.
Can Firmware Cause An Intermittent PCBA Failure?
Yes. Timing, memory, power-sequence, communication, and watchdog issues can appear intermittently.
How Many Failed Samples Are Needed?
One sample may provide useful evidence. Multiple samples improve comparison and help determine whether the problem is isolated or systematic.
Who Owns The Final Root Cause?
The responsible organization depends on the confirmed cause. The OEM, PCB fabricator, component supplier, assembler, test laboratory, or user may need to support the final investigation.
Turn PCBA Failure Evidence Into Permanent Improvement
Effective PCBA failure analysis does not stop when the board starts working again. It connects the symptom, failure mechanism, root cause, containment, corrective action, and verification.
The investigation should preserve the original sample, reproduce the failure, complete non-destructive inspection, and use destructive methods only when necessary.
Manufacturers should support conclusions with photographs, measurements, production records, and controlled experiments. If evidence remains incomplete, the report should clearly state the uncertainty.
Haode PCBA can review failed assemblies, Gerber files, BOM data, inspection records, test results, rework history, and production traceability. Early cooperation helps isolate failures, reduce repeat defects, and improve reliability across future PCB assembly orders.
