Blog / Downtime
Downtime · Guide

Unplanned Downtime Examples by Type and Machine

OL By OEE Lab Editorial |Updated 2 November 2026 |5 min read
Short answer

Unplanned downtime is any stop inside planned production time that was not on the schedule. Examples: a motor fails, a labeller jams, cartons run out, the operator loads the wrong recipe, a batch fails a test, a changeover runs past its standard time. The test is one question: was this stop on the schedule before the shift began?

Examples by type

Teams often picture a breakdown when they hear "unplanned". The list is wider than that, and only the first group is about broken equipment.

The equipment failed

  • A motor bearing seizes on a conveyor.
  • A drive trips on overcurrent and will not reset.
  • A photo eye gives false readings because of dust.
  • A hydraulic hose bursts on a press.

Someone or some procedure caused it

  • The operator loads the wrong recipe, and the run stops for a reset.
  • A wrong label roll goes on after a changeover.
  • A machine is set outside its window, then starts to jam.

Something from outside stopped the machine

Quality stopped the run

  • A lab result holds the line until someone releases the batch.
  • Raw material arrives out of spec, and the process will not run.
  • Extra tests are ordered after a customer complaint.

One shift, stop by stop

Example: a packaging line runs 06:00 to 14:00, which is 480 minutes. The crew breaks for 30 minutes and nobody relieves them, so this plant leaves that out and plans 450 minutes.

06:00 14:00 Unplanned Planned Excluded Running
The unplanned blocks are the stops in the table below. They are hard to spot from any total.
TimeWhat happenedMinClass
06:20Sensor fault at startup12Unplanned, technical
07:10Changeover, to standard30Planned
08:05No cartons at the line18Unplanned, induced
09:30Break, no relief30Excluded
10:25Drive trip on the filler35Unplanned, technical
11:40Wrong label roll9Unplanned, operational
12:30Cleaning, 15 planned, 21 taken15 + 6Planned + unplanned
13:20Quality hold on a batch14Unplanned, quality
Hypothetical shift. Note how the cleaning overrun splits into two classes.

Unplanned minutes are 12 + 18 + 35 + 9 + 6 + 14 = 94. That is 94 / 450 = 20.9% of planned time.

Planned stops are 30 + 15 = 45 minutes, so run time is 450 - 94 - 45 = 311 minutes. Availability is 311 / 450 = 69.1%.

Technical faults explain only 47 of the 94 unplanned minutes, so a team that watches breakdowns alone would see half the problem. The full method is on the unplanned downtime formula page.

Gray areas: which way do they go?

These cases cause most of the arguments. Agree on them once and write the answers on the log sheet.

SituationUsual classWhy
Maintenance decided the morning of the shiftUnplannedIt was not on the schedule beforehand
Changeover runs past its standardSplitThe standard part is planned, and the rest is not
Extra clean after a spillUnplannedA routine clean is planned, but this one is not
Power cut at the siteUnplannedIt was outside the plant's control, but it still cost planned time
Line idle, no ordersExcludedThe line was not planned to run
Jam cleared in 40 secondsShort stopBelow the threshold, it falls in performance
Line running slower than idealNot downtimeThe machine is running, so it counts as a speed loss
Plants differ on some of these. What matters is one answer per plant.

For the last two rows, see minor stops vs breakdowns and speed losses. The broader definitions are on planned vs unplanned downtime.

Examples by machine type

The same class looks different in each process. These are typical of what appears on a stop log, not a ranking.

Use these examples to train the crew

Definitions on a slide rarely survive the first night shift. Examples from your own line do.

  • Take ten stops from last week and classify them with each crew.
  • Where two people disagree, write the answer on the log sheet.
  • Replace the examples above with your own machine names and faults.
  • Repeat it when a new product or machine arrives, since new stops bring new arguments.

Once crews agree, the unplanned figure can be compared from week to week. Without that, a change in the number may only mean a different person filled in the log.

The rules for a log that crews keep up are on operator downtime logging.

How these examples hit OEE

Every example above, once over the threshold, comes off availability in the same way. So 45 minutes of no cartons costs as much OEE as 45 minutes of a failed motor.

The cost can differ, though, since a failure may also bring parts, overtime and scrap at restart. For the wider view, read the cost of downtime.

The first step for any of them is the same: log each stop with a time and a reason. Then rank them, as in how to reduce unplanned downtime.

See it live in Fabrico

A log like the one above takes discipline to keep by hand. Fabrico takes stops, speed and counts live from PLCs or IoT sensors, with add-on AI cameras counting output where a machine has no usable signal, and operators tag the cause at the line. See Fabrico, a light MES for OEE.

What people ask next

What is an example of unplanned downtime?

A conveyor motor that fails during a run is the classic case. Running out of cartons and waiting on a held batch are also unplanned. See machine downtime reasons for a fuller list.

Is a changeover unplanned downtime?

A changeover within its planned time is planned, though it still lowers availability. Any time past the standard counts as unplanned. See how to count changeovers in OEE.

Is preventive maintenance ever unplanned downtime?

If it was on the schedule before the shift, it is planned. If it was decided that morning because something looked wrong, treat it as unplanned. See does maintenance count in OEE.

What is the difference between planned and unplanned downtime?

Planned stops were on the schedule, and unplanned ones were not. Both lower availability when they fall inside planned production time. The full comparison is on planned vs unplanned downtime.

How do I calculate how much unplanned downtime I have?

Divide unplanned stop minutes by planned production minutes and multiply by 100. The unplanned downtime formula page has a full example.

See OEE per line and shift on your own machines

Fabrico is a light MES for OEE. It takes stops, speed and counts from PLCs or IoT sensors, with add-on AI cameras counting output where a machine has no usable signal, and operators tag the cause at the line.

Book a Fabrico demo

← More OEE Lab guides · Unplanned downtime formula →

OEE essentials: OEE calculator · What is OEE · Six big losses · Availability · TEEP · Cost of downtime · OEE benchmark · Free OEE tracker · Free OEE software · How to track downtime · How to implement OEE · Light MES vs full MES