← Back to the page you were readingYou opened this term from another page.
R&D · MethodsTask: Plan R&D

Root cause analysis (RCA)

Also called RCA, root cause investigation

Published by Patsnap Team Updated 3 sources
DefinitionRCA

Root cause analysis (RCA), in the US Department of Energy's 1992 guidance, investigates an occurrence by working back from immediate causes to their fundamental reason1.

NASA's 2026 NID 8621.157 defines RCA as a structured evaluation method to identify root causes of an undesired outcome and actions adequate to prevent occurrence2. IEC's public summary of IEC 62740:2015 describes a process for analyzing events that have already occurred3.

AppliesIEC's 2015 public summary: analysis of events that have occurred3
Comes upThe US Department of Energy's 1992 guidance: occurrence investigations1
Also seeNASA’s 2026 NID 8621.157 defines root cause analysis for NASA mishap investigations2.
Not to confuse withThe US Department of Energy's 1992 guidance distinguishes direct, contributing and root causes1
01

How the agencies define a root cause

SourceMeaning in that source
US Department of Energy, 19921The US Department of Energy's 1992 guidance defines a root cause as a cause whose correction would prevent recurrence of the occurrence and similar occurrences1.
NASA, 2026 NID 8621.1572NASA's 2026 NID 8621.157 defines a root cause as an event or condition primarily associated with organizational factors that preceded and directly produced an intermediate cause, indirectly caused or contributed to the proximate cause and undesired outcome, and whose elimination or modification would have prevented the intermediate cause and undesired outcome2.

NASA's 2026 NID 8621.157 states that multiple causes typically contribute to an undesired outcome and permits the root cause to be identified as undetermined in the absence of a prevalent organizational factor2.

02

How the DOE guidance organizes an investigation

  1. Collect dataThe US Department of Energy's 1992 guidance calls for collecting conditions before, during and after the occurrence, personnel involvement and actions, environmental factors, and other relevant information, without compromising safety or recovery1.
  2. Assess the occurrenceThe US Department of Energy's 1992 guidance calls for identifying the problem, determining its significance, identifying immediate and surrounding causes, and working back to the reasons those causes existed1.
  3. Address corrective actionsThe US Department of Energy's 1992 guidance includes corrective actions as the third phase of its investigation and reporting process1.
  4. Inform the relevant peopleThe US Department of Energy's 1992 guidance includes reporting through its Occurrence Reporting and Processing System and discussing analysis results and corrective actions with management and personnel involved1.
  5. Follow upThe US Department of Energy's 1992 guidance includes checking whether corrective actions have been implemented and whether they have resolved the problems1.
03

Distinctions and scope

Term or scopeAttributed description
Direct cause1The US Department of Energy's 1992 guidance calls the cause that directly resulted in the occurrence the direct cause1.
Contributing cause1The US Department of Energy's 1992 guidance describes a contributing cause as one that contributed to an occurrence but would not have caused it by itself1.
Standards scope3IEC's public summary of IEC 62740:2015 says its techniques are not designed to assign responsibility or liability, which falls outside the standard's scope3.

IEC's public summary of IEC 62740:2015 says RCA can analyze events with positive or negative outcomes and is most commonly used for failures and incidents3.

04

Questions people ask

Patsnap EurekaEureka R&D

Plan R&D

R&D AI Agent

An AI technical research assistant for R&D and engineering problems.

Ask Eureka Engineering
Is a root cause the same as the immediate cause?

No, under the US Department of Energy's 1992 guidance: a direct cause directly produced the occurrence, while a root cause is defined by whether correcting it would prevent recurrence and similar occurrences1.

Must an investigation identify one root cause?

Under NASA’s 2026 NID 8621.157, investigators may record the root cause of a mishap as undetermined if no prevalent organizational factor is identified2. NASA’s 2026 NID 8621.157 also says several causes typically contribute to an undesired outcome2.

When does root cause analysis stop?

Under NASA's 2026 NID 8621.157, RCA should continue until organizational factors have been identified or the data are exhausted2.

05

How it connects

PublishedPatsnap Team
Updated 18 November 2026
Sources
  1. DOE-NE-STD-1004-92: Root Cause Analysis Guidance Document. U.S. Department of Energy · guidance document · 1992. Accessed 18 November 2026.
  2. NID 8621.157: Requirements for Mishap and Close Call Reporting, Investigating, and Recordkeeping. NASA · interim directive · 2026. Accessed 18 November 2026.
  3. IEC 62740:2015: Root cause analysis (RCA). IEC · standard summary page · 2015. Accessed 18 November 2026.
Disclaimer

General information only. This page explains a term and is provided for general information and reference only. It is not legal advice and must not be relied upon as such. It does not create an attorney-client relationship.

Sources and accuracy. Statements on this page are intended to be either general background or linked to a source listed under Sources. The explanations summarize and simplify those sources and leave out detail. Where this page differs from a cited source or from the current official text of a law or standard, rely on that source or text.

Rules vary and change. The law, standards and practice described here differ between jurisdictions and change through legislation, court decisions and revisions to official guidance and standards. This page was last checked against its sources on 18 November 2026 and may not reflect later changes. Check the current rules and official guidance in each jurisdiction that applies to you.

No FTO or validity opinion. Nothing on this page constitutes a freedom-to-operate, novelty, validity or infringement opinion. Any decision touching a live patent dispute should be verified independently and reviewed with qualified patent counsel.

Third-party names and marks. Party, attorney, judge and company names appear for identification only. Company names may be trademarks of their owners; their appearance does not, by itself, imply affiliation with or endorsement by Patsnap.

Corrections. If you believe a statement on this page is inaccurate or out of date, use “Share feedback” at the bottom of this page and tell us which statement and why.

R&D AI AgentAsk Eureka Engineering in Patsnap EurekaStart →

Help us improve

Something wrong, out of date, or missing on this page? Tell us and it goes straight to the team that maintains it.