FOD Prevention Case Studies: Four Lessons from the Field

A checklist can tell a technician to verify tools after a task. A well-told story shows what happens when that check confirms presence but not identity. That is why the complete FOD Prevention Program Guide includes a chapter of FOD case studies. An important note on how to read them: the guide states that these are composite scenarios built from documented failure modes, investigation findings and industry experience across multiple organizations. They represent realistic event chains and recurring failure patterns, not reconstructions of specific individual incidents. Each includes the event, the investigation, the root cause, the systemic failures and the lessons for your own program.

Case Study 1: The Missing Socket

The event. During a routine borescope inspection of a commercial turbofan engine, a 10mm socket was found lodged between compressor blades in the high-pressure compressor. The engine had about 200 flight hours since its last maintenance, a compressor blade replacement. The socket showed signs of having been in the engine the whole time: peened by contact with rotating blades, carried aft through several compressor stages and causing progressive blade damage across multiple stages.

What the investigation found. The tool control log for that maintenance event showed every tool accounted for. But the socket in the engine belonged to a set assigned to the technician who did the work, and the shadow board position for a 10mm socket was occupied by a 10mm socket from a different manufacturer. The technician had borrowed a socket from a colleague when their own rolled under a work stand. Their own socket fell into an open compressor cavity and was never recovered. The borrowed socket was placed on the shadow board at task completion, which satisfied the visual check, so the loss stayed hidden.

Systemic failures. Serial numbers existed but were not verified during the post-task check because they were small and hard to read without removing the socket. The borrowed-tool practice needed no documentation, so tools moved between technicians without any inventory update. The independent post-task verification was a presence check, not an identity check. And the technician did not report the drop because they believed it had rolled under the stand and intended to retrieve it later, then forgot.

Corrective actions. The guide lists four: laser-etch all tools in FOD Critical areas with large, readable serial numbers; change post-task verification from a visual board check to a physical serial number check where the verifier removes each tool and matches it to the board label; implement a borrowed-tool procedure with a shared tool movement log; and adopt an if it drops, find it now policy that stops the task step until the item is found or the area is formally cleared.

The lesson. A tool sitting on a shadow board does not prove the right tool is there, so verification has to confirm identity as well as presence. Informal borrowing is a predictable failure point, and an item that is probably under the stand is sometimes probably in the engine. The post-task check is the last barrier before a tool becomes a potential catastrophe, so it must be thorough enough to carry that weight. See our articles on the FOD tool control program and missing tool protocol for more.

Case Study 2: The Runway Debris Chain

The event. An Airbus A320 departing a regional airport suffered a tire failure during the takeoff roll. The crew rejected the takeoff at about 120 knots and the aircraft stopped on the runway. Inspectors found a steel piece roughly 3 inches long and 0.5 inches wide embedded in the failed tire. It was traced to a fragment of a ground support equipment tow bar that had fractured and been left on the ramp. Vehicle traffic kicked the fragment onto the adjacent taxiway, and an aircraft ahead of the incident aircraft moved it onto the runway.

What the investigation found. The tow bar fractured about 4 hours before the incident. The GSE operator told their supervisor, but the report did not mention that the fractured piece had not been recovered. The supervisor raised a work order for the tow bar and did not start a FOD search. The ramp had been swept during the morning FOD walk, before the fracture, and the next walk was scheduled for the following morning.

Root cause. There was no procedure for starting an immediate FOD sweep after a known debris-generating event. The reporting system treated equipment damage and FOD as separate categories, so the operator reported an equipment problem, not a debris problem.

Corrective actions. An event-triggered sweep procedure: any event that generates or may have generated debris, such as equipment damage, a dropped item, a spill, a collision or a weather event, triggers an immediate sweep of the affected area plus a buffer zone. The GSE damage form gained mandatory debris fields. Supervisors were trained on the link between equipment damage reports and FOD risk. Ramp walks increased from daily to twice daily, with one timed about 1 to 2 hours before the first departure of the afternoon or evening bank.

The lesson. Scheduled walks are necessary but not sufficient, and known debris events need an immediate response. Debris migrates, so the search area must be larger than the event location. Forms and reporting systems should capture both equipment damage and debris. The guide notes that the cost of an immediate sweep is trivial compared with the cost of the event it prevents. Read more in FOD incident response.

Case Study 3: The Cultural Decay

The event. An MRO facility with a historically strong FOD program saw FOD-related customer findings creep up over 18 months, roughly 5 to 10 percent per quarter, with no single event to sound an alarm. By the time the trend was recognized, the facility had fallen from industry benchmark to industry average, and two major customers had issued formal corrective action requests citing FOD control as a systemic weakness.

What the review found. The FOD Program Owner role had been vacant for eight months after a retirement, and three supervisors each assumed the others were handling trend analysis. Walks continued but findings log review had slipped from weekly to monthly to when someone asks. Corrective actions were closed on the owner’s word without independent verification. The monthly dashboard was still produced but had not reached leadership in over a year. Tool control audits dropped from monthly to quarterly, so trends took three times as long to detect, and new-hire training shrank from a 2-hour classroom session plus supervised walk to a 30-minute online module.

Root cause. The program became hollow. Visible elements, walks, logs and dashboards, persisted while analysis, corrective action and verification atrophied. Because the decline was gradual, nobody noticed until customers did.

Corrective actions. The owner position was filled within 60 days, with a documented interim owner in the meantime. A separate program health dashboard was added, tracking walk completion, log review cadence, corrective action time-to-close and verification rate, audit and training completion, and management review cadence. Automated alerts fire when a walk is missed, an action passes its due date or a monthly review is skipped. A leadership FOD briefing joined the quarterly safety review agenda, and the 2-hour classroom training was restored with the online module as pre-work.

The lesson. A program that looks active but is not analyzed is motion without progress. Leading indicators matter as much as findings, and gradual decline is the most dangerous kind. Key-person dependency is a program risk, so document the program and cross-train a deputy. Our article on FOD leading and lagging indicators explains the health metrics in detail.

Case Study 4: The Packaging Cascade

The event. A composite component manufacturer saw a sudden spike in hard-category FOD findings, such as fasteners, washers and small metal fragments, in a cleanroom assembly area that normally recorded near-zero. The spike coincided with a new supplier for a major sub-component, and findings clustered in the unpacking area and adjacent assembly cells.

What the investigation found. The new supplier sealed component bags with metal staples instead of heat-sealing. Personnel cut the bags open and staples fell to the floor, and some clung to bag surfaces through static electricity and were carried into assembly cells. The supplier’s threaded inserts were also shipped uncapped, so metal debris from insert manufacturing, trapped in the threads, fell out during unpacking.

Root cause. The sourcing decision weighed cost, quality and delivery but not packaging or FOD control. The contract set no packaging or FOD requirements, and incoming inspection checked dimensions and material conformity but not FOD generation potential. The link to the new supplier was made by an alert receiving inspector, not by any systematic process.

Corrective actions. Supplier selection criteria now include FOD program assessment and packaging review. A standard packaging specification calls for no metal staples, no cardboard in FOD Control or Critical areas, capped threaded features and items free of manufacturing debris. First-article inspection for new suppliers includes unpacking the component in a controlled area the way the supplier intended and checking for debris. Incoming inspection adds a FOD check for all shipments from new suppliers during the first 90 days and from any supplier with a history of FOD escapes.

The lesson. FOD risk can be imported, and a cost-driven sourcing choice can cost more than it saves. Packaging is a FOD control, not just logistics. The best moment to catch a supplier problem is the first shipment, not the tenth. And a clean area with historically zero findings is a sensitive detector, so protect it by controlling what enters. For the full approach, read supplier and vendor FOD management.

Key Themes Across the Cases

The guide draws four themes that recur across FOD case studies:

• Normalization of deviance. Small deviations with no immediate consequence become the new normal, each making the next easier, until practice bears little resemblance to procedure.
• The missing barrier. Events rarely come from one failure. In the socket case the behavioral barrier (the dropped tool), the procedural barrier (the post-task check) and the detection barrier all failed together. A healthy program has enough independent barriers that no single failure reaches the aircraft or product.
• The data-rich, information-poor program. Data is collected but not analyzed, logged but not trended, reported but not read.
• The engagement gap. Leadership sees walks happening and logs filled and assumes health, while walks are perfunctory and logs unread.

The guide’s closing point is that a FOD program is a system rather than a collection of activities. It depends on defined standards, measured performance, analysis of deviations, corrective action and verification that the action worked. Take away one element and the system degrades; take away enough and it fails, gradually at first, then catastrophically. For a method to dig into your own findings the same way, see root cause analysis for FOD.

Turn the Lessons into Controls

Many of these fixes are visible and physical: FOD signs that define area classification, FOD cans at the point of work and FOD bags for personal containment. The rest are procedures, verification steps and measurements, and the free 216-page guide and toolkit give you the structure to build them. Request the guide here.