Root Cause Analysis for FOD: Five Whys, Fishbone and Barrier Analysis

A FOD program that only collects debris is a cleaning program. The step that turns it into a prevention program is investigation: finding out why the item was on the floor, in the tool crib or inside the assembly, and changing the system so it stops happening. The right root cause analysis FOD method depends on the problem in front of you, and the complete guide devotes a chapter to choosing between them. This article walks through that chapter.

Choosing the Right Method

Not every finding needs a full investigation. The guide separates two situations. A single occurrence with low severity and a clear cause can simply be logged, fixed and closed. A single occurrence with high severity, or any repeat occurrence regardless of severity, warrants formal root cause analysis, and the method should scale with the complexity of the problem. If you are not sure what counts as a repeat, the guide’s investigation triggers include three or more findings of the same category of item in the same zone within 30 days, or two findings of the same specific item type in the same zone within 30 days. The repeat FOD investigation worksheet in the free toolkit supports exactly this trigger.

Five Whys for Simple, Linear Problems

Five Whys is best for single-source problems with a straightforward cause-and-effect chain. You start with the finding and ask why, then treat each answer as the basis for the next question. By the fifth answer you should have reached a systemic cause rather than a person.

The guide illustrates this with safety wire found on a hangar floor in Bay 2 for the third time in a month. The chain runs like this:

• The wire is on the floor because it falls during maintenance tasks and is not always recovered.
• It is not recovered because technicians cut the wire and the offcut drops, with no designated place to put offcuts during the task.
• There is no place because the work stands have no offcut containers, and the procedure says clean as you go without saying where offcuts go.
• The work stands have no containers because nobody specified them as a requirement.

The fix that follows is a system fix: add small magnetic collection containers to every work stand used for safety wire tasks and update the procedure to say where offcuts go. The guide is explicit that the wrong answer would have been to remind technicians to be more careful. Point-of-use containers such as FOD cans are the kind of physical control that a good Five Whys often ends up requiring.

The method has limits worth knowing. It tends to produce a single-cause answer when the real cause is multifactorial. Different people asking why can reach different conclusions based on their own knowledge. And it can stall at a proximate cause such as the technician was careless, instead of a systemic one such as the work area layout makes offcuts hard to contain.

Fishbone (Ishikawa) Diagrams for Multi-Factor Problems

When several factors interact, a fishbone diagram is the better tool. You draw a horizontal arrow pointing at the problem statement, then branch off six categories: people, process, equipment, materials, environment and measurement. For each category the team brainstorms contributing factors.

The guide applies this to repeat fastener findings in an assembly area. Contributing factors included new technicians not trained on FOD containment, fatigue on extended shifts, no post-task FOD check step in the assembly procedure, fastener kit packaging that generates loose items when opened, work benches without raised edges, no magnetic trays at every station, static-prone kit bags that release fasteners after they cling, extra fasteners loose in the supplier kit, dim lighting at bench edges, foot traffic that kicks dropped items under benches, walk findings that were not trended, and no completeness check of the kit before starting.

The important step comes after the brainstorm. Not every factor needs its own corrective action. Group them by common root cause. In the example, several factors pointed to work station design (bench edges, lighting, magnetic trays) and several to procedure gaps (no post-task check, no kit verification). Two well-chosen corrective actions could therefore address many contributing factors at once.

Barrier Analysis: Why Did the Controls Fail?

Barrier analysis is best when you want to understand why existing controls did not work and which need strengthening. For a given finding, you list every barrier that should have prevented it and determine why each one failed. Barriers can be physical, procedural, behavioral or detection-based.

The guide uses a socket found on the floor under an engine after maintenance. Four barriers failed together:

• Physical: the shadow board had a socket silhouette, but the socket was returned to the wrong position, a similar-sized socket, and a visual check did not catch it.
• Procedural: the post-task tool count was pencil-whipped, signed without physically verifying, under time pressure at shift end.
• Behavioral: the technician was fatigued at the end of a 12-hour shift and confident that everything had been returned.
• Detection: the post-maintenance FOD walk was completed, but the socket was under the engine stand and the walker did not kneel or use a flashlight.

Each failed barrier produced a targeted corrective action: individual tool serialization so a wrong-position return is detectable, independent second-person verification that physically touches each tool position, limits on task duration before mandatory breaks, and adding under equipment as a mandatory inspection point on the FOD walk checklist with flashlight use specified. For more on the tool side of this scenario, see our article on the missing tool protocol.

Human Factors Analysis: Was the Error Inevitable?

When human error contributed to an event, the guide asks one key question: would another qualified person, in the same circumstances and with the same information, likely have made the same error? If yes, the root cause sits in the system and the system must be fixed. The factors to examine are:

• Time pressure and whether the schedule was achievable without cutting corners.
• Fatigue, including hours worked, time since last break and sleep history.
• Training and competence on the specific task and the specific FOD control.
• Procedure clarity, meaning whether it is usable at the point of work or a generic document nobody references.
• Distractions and interruptions, which the guide calls a leading cause of omission errors.
• Equipment and environment, such as lighting, ergonomics and whether tools and containers were within reach.
• Habit and normalization, where a procedure skipped without consequence becomes the norm.

A finding of technician error should always be followed by asking what about the system made the error likely and what change will make it unlikely. Only when the honest answer is nothing, and there is evidence of recklessness rather than just error, is it a performance management issue. The guide says this conclusion should be rare. See FOD safety culture and human factors for the wider picture.

What Every RCA Must Produce

An investigation is only complete when it produces four things:

• A clear root cause statement. Poor housekeeping is too vague; work stations lack point-of-use offcut collection, leading to debris on the floor is a usable statement.
• Specific corrective actions with owners and due dates.
• A verification method defined before the action is implemented, for example inspecting the zone on the next four walks and reopening the investigation if any finding of that type appears.
• An entry in the corrective action tracker for visibility and accountability.

The guide is blunt about the alternative: conducting an RCA and not implementing the findings is worse than not conducting one, because it trains people to see participation in investigations as pointless. Physical fixes often include clearer boundaries and reminders at the point of work, and FOD floor tape and FOD signs can support them, but the fix must always trace back to the root cause statement.

Where to Go Next

The complete guide includes worked examples, the investigation triggers and the tracking process. For a look at how these methods play out in full event narratives, read our FOD prevention case studies, then request the free guide and toolkit.