7 Common Causes of Unplanned Downtime (and How to Fix Them)

Quick answer: The 7 most common causes of unplanned downtime in manufacturing are: equipment failure, operator error, lack of training, poor maintenance, material shortages, process bottlenecks, and IT or system outages. Equipment failure and operator error account for 60% of incidents; the rest is preventable with better PM, training, and stocking.

Related deep-dives: 6 root causes deep-dive · iceberg cost effect · Pareto analysis · why PM fails (82% rule).

Cause 1: Mechanical wear. Bearings, belts, seals, chains degrading over usage cycles. Predictable from sensor data once you measure it.

• Cost: 18-25% of unplanned downtime in typical EU plants
• Fix: condition-based PM triggered by sensor thresholds (vibration, temperature, acoustic), not the calendar. How condition-based PM works.
• Time to result: 3-6 months for MTBF to rise 15-25%

Cause 2: Lubrication failure. Missed re-greasing, contamination, wrong viscosity. Easy to prevent, often overlooked because nobody owns it.

• Cost: 12-15% of unplanned downtime, but disproportionately destructive (one missed bearing grease destroys the bearing in a week)
• Fix: route-based lubrication PM with mobile checklists. Lock the route, name the technician, set frequency by bearing load curve not calendar.
• Time to result: 4-8 weeks. The fastest-return cause to fix.

See how these causes map to the 6 OEE losses.

Cause 3: Operator error. Wrong setup, missed alarm, parameter typo. Almost never the operator's fault — it is a process gap.

• Cost: 20-25% of unplanned downtime in typical EU plants
• Fix: standardized setup procedures with visual confirmations + Computer Vision verifying each step. Operators do not memorize, they follow.
• Time to result: 8-12 weeks. Heavily depends on operator buy-in.

Cause 4: Changeover overrun. The planned 45-minute changeover took 78 minutes. That extra 33 minutes is unplanned downtime hidden as planned.

• Cost: 15-20% of unplanned downtime when measured properly
• Fix: SMED methodology (Single-Minute Exchange of Die). Break the changeover into internal (machine stopped) and external (machine running) steps, move as much as possible to external.
• Time to result: First-pass SMED on one line takes 6-10 weeks. Subsequent lines go 3-4x faster.

See the broader 6 root causes framework.

Cause 5: Spare parts unavailable. The part you need is the one you do not have. Single-day events become multi-day waits.

• Cost: 8-12% of unplanned downtime, often the longest single events
• Fix: failure-mode-driven spare parts policy with min/max levels tied to MTBF data. The 80/20 rule applies: 20 critical-path SKUs cover 80% of failures.
• Time to result: 3-4 weeks to set up min/max + reorder triggers. Effects show within 2-3 months.

Cause 6: Sensor failure. The sensor says the machine is down when it is running, or vice versa. Triggers false alarms, missed real ones.

• Cost: 5-8% of unplanned downtime directly, but inflates other cost categories because trust in the data breaks
• Fix: redundant sensors on critical paths + cross-check with Computer Vision as second source. CV catches sensor drift before it becomes a failure.
• Time to result: 4-6 weeks for installation + tuning.

See data collection methods that catch sensor drift.

Cause 7: Software glitch. PLC freezes, HMI hangs, scheduling conflict locks the line. Modern plants see this more than they should.

• Cost: 4-6% of unplanned downtime, but trending upward as plants digitize
• Fix: watchdog timers + automated restart scripts for known failure modes. Manual recovery becomes the exception, not the rule.
• Time to result: 2-4 weeks per failure mode.

How to actually use this list. Do NOT try to fix all 7 at once. The order matters:

1. Run a Pareto analysis on your last 12 weeks of downtime data, classified by cause
2. Pick the top 2 causes for your specific plant
3. Apply the matched fix from this list, one cause at a time
4. Measure for 4 weeks, then move to the next cause

A modern OEE solution with native CMMS classifies events by cause automatically. You walk into the weekly review with the Pareto already done, not a half-day spreadsheet exercise. That is the difference between Fabrico and a generic "things broke" dashboard.