FOD Classification System: The Ten-Category Framework

Two technicians find the same length of safety wire. One logs it as hardware, the other as a consumable. Multiply that by a few hundred findings a month and the trend data is meaningless. A shared FOD classification system solves that problem by giving everyone the same vocabulary at the moment of logging.

Why Classify FOD at All

The guide gives classification three jobs:

1. Trending. Consistent codes across shifts, areas and time let you see patterns. If one shift calls safety wire HARD and another calls it CONS, the trend is useless.
2. Accountability. Each category has an owning function. When hardware findings rise, maintenance and production know to look at their processes. When packaging findings rise, receiving and kitting look at theirs.
3. Severity assessment. Categories identify the likely owner and mandatory escalation triggers, but they do not assign a fixed severity. Severity is judged from location, exposure, potential consequence, likelihood and uncertainty, and the category triggers the appropriate level of response. See the FOD severity and risk matrix for how that scoring works.

The Ten-Category System

The guide notes that this ten-category taxonomy is its own recommended scheme, not a mandated NAS412 or SAE/AS9146 standard, and that you should adapt the categories to your operation. The codes and typical owners are:

• HARD, hardware and fasteners: owned by maintenance or production. Escalation is assessed from location, exposure and consequence.
• TOOL, tools and tooling: owned by tool control. A missing tool is escalated under the missing tool protocol. A found tool is assessed by where it was found.
• CONS, consumables: owned by the work crew or supervisor. Routine, but assess for a repeat pattern.
• PACK, packaging: owned by receiving and kitting. Routine, but assess for a repeat pattern.
• NAT, natural debris: owned by facilities or airfield operations. Assess location and exposure.
• FAC, facility deterioration: owned by facilities. Routine unless it occurs in a critical zone.
• PERS, personal items: owned by the supervisor or the individual. Assess location and exposure.
• PART, suspected parts: owned by quality or maintenance. Escalate for investigation regardless of location.
• HAZ, hazardous material: owned by safety or hazmat. Isolate, do not handle, and escalate immediately.
• UNKN, truly unknown: owned by quality or safety. Escalate until assessed by a qualified person.

The full classification table in the complete guide adds examples, typical sources and visual detection tips for each category. It also feeds the category dropdown used in digital FOD capture and trend tracking.

Classification Discipline: The UNKN and HAZ Rules

The rule for UNKN. UNKN is valid only after a qualified person has assessed the item as non-hazardous and its identity or origin remains unclear. An item that has not been assessed is unassessed, must not be handled, and must be escalated as a suspected HAZ until qualified personnel finish the assessment. UNKN is not a shortcut for being unsure and in a hurry.

Repeated UNKN entries in the same area signal one of two problems: the inspection team lacks the knowledge to identify common FOD items, which is a training gap, or an unusual debris source is operating there, which is a process gap. Either way, investigate the pattern.

The rule for HAZ. When in doubt about hazard potential, classify as HAZ. It is always acceptable to escalate a harmless item out of caution and never acceptable to treat a hazardous item as harmless because the hazard went unrecognized.

Consistency check. The program owner should periodically sample recent findings to confirm that similar items are classified the same way across shifts, that UNKN is being used properly, and to give feedback to walk leaders and scribes when inconsistency appears.

Making Classification Stick

Classification is only as good as the people doing it, so build it into FOD training and keep the code list visible at the point of collection, for example on FOD cans and FOD signs in work areas. Assign the code when the item is logged, since the finder knows best what it looked like and where it came from. From there the code drives the response covered in FOD finding response and disposition codes.

Get the full category table, examples and the findings log in the free FOD Prevention Program Guide.