Menu

MTTF (Mean Time to Failure): Formula and Examples

Learn what MTTF (mean time to failure) is, how to calculate it, how it differs from MTBF, and how to apply this reliability metric on the factory floor.

MTTF (mean time to failure) is a reliability metric that estimates the average operating time a non-repairable item runs before it fails permanently. You calculate it by dividing total operating hours by the number of units that failed. Because the item is replaced rather than repaired, MTTF describes a component's expected lifespan.

What MTTF measures and why it matters

MTTF answers a single practical question: how long, on average, does a part last before it dies for good. It applies to components you throw away and replace rather than fix, such as bearings, light bulbs, fuses, sensors, filters, batteries, and many electronic modules. Knowing this figure lets maintenance and operations teams plan replacements before failures cause unexpected stops.

  • Spare-parts planning: forecast how many replacement units you need over a year.
  • Budgeting: tie component lifespan to a realistic replacement cost cycle.
  • Design decisions: compare two suppliers' parts on expected life, not just price.
  • Downtime reduction: schedule swaps proactively instead of reacting to breakdowns that drive unplanned downtime.

The MTTF formula

The core formula is straightforward and works whenever you have a batch of identical non-repairable units observed until they fail.

MTTF = Total operating time of all units / Number of units that failed

The result is expressed in a time unit, usually hours. It represents a statistical average across a population, not a guarantee for any single part. One unit may fail early and another may run far longer, but the mean gives you a defensible planning number.

A worked numeric example

Suppose you test a batch of 6 identical proximity sensors until each one fails, recording these run times before failure:

  1. Sensor 1: 8,200 hours
  2. Sensor 2: 9,000 hours
  3. Sensor 3: 7,600 hours
  4. Sensor 4: 10,400 hours
  5. Sensor 5: 8,800 hours
  6. Sensor 6: 9,000 hours

Add the operating hours: 8,200 + 9,000 + 7,600 + 10,400 + 8,800 + 9,000 = 53,000 hours. Divide by the 6 units that failed:

MTTF = 53,000 / 6 = 8,833 hours

So each sensor lasts roughly 8,833 hours on average. If a machine runs about 6,000 hours per year, you would expect to replace each sensor a little less than every 18 months, letting you pre-stock spares and schedule the swap during planned downtime.

MTTF vs MTBF: the key difference

MTTF and MTBF and MTTR are often confused, but they describe different kinds of assets. The distinction comes down to one word: repairable.

  • MTTF (mean time to failure) applies to non-repairable items that are replaced once they fail. There is one failure per unit, then the unit is gone.
  • MTBF (mean time between failures) applies to repairable systems that are fixed and returned to service. It measures the average uptime between one failure and the next across the asset's life.

A quick test: if you fix the item and keep using it, use MTBF. If you toss it and fit a new one, use MTTF. A conveyor motor that gets rewound and reinstalled is an MTBF asset. The bearing inside it that gets discarded and replaced is an MTTF item. Using the right metric keeps your reliability analysis honest and your spare-parts math correct.

How to apply MTTF on the factory floor

MTTF only creates value when it drives action. These steps turn the number into fewer surprise stops and better parts planning.

  1. Log every failure accurately. Capture install dates, run hours, and failure dates for each replaceable component in a CMMS so the data is trustworthy.
  2. Group by identical part. Calculate MTTF per part number, not across mixed components, so the average is meaningful.
  3. Convert to a replacement interval. Divide MTTF by annual run hours to set a proactive swap schedule.
  4. Build preventive tasks. Turn that interval into recurring work orders so replacements happen before failure, shifting your team from reactive to proactive maintenance.
  5. Feed component risk into FMEA. Short-life parts that stop production deserve priority in a FMEA review.

Common mistakes to avoid

MTTF is simple to compute but easy to misread. Watch for these pitfalls before you trust the number.

  • Treating the average as a warranty. MTTF is a population mean, not a promise that every unit reaches that age.
  • Mixing repairable and non-repairable assets in one calculation, which produces a meaningless figure.
  • Ignoring operating conditions. Heat, vibration, and duty cycle change real lifespan, so the same part can show a very different MTTF in a different environment.
  • Too small a sample. A handful of units gives a shaky average; more data points tighten the estimate.

Frequently Asked Questions

Is a higher MTTF always better?

Yes, a higher MTTF means the component lasts longer on average before failing, which usually reduces replacement frequency, spare-parts spend, and downtime. That said, always weigh MTTF against cost, availability, and operating conditions. A part with a slightly lower MTTF that is cheaper and always in stock can still be the smarter choice for your line.

Can MTTF predict when a single part will fail?

No. MTTF is a statistical average across a population of identical units, not a countdown timer for one specific part. Individual components fail earlier or later than the mean. Use MTTF for planning replacement intervals and stocking spares, but pair it with condition monitoring if you need earlier warning about a particular asset.

How is MTTF different from service life?

MTTF is the calculated average time to failure derived from observed data across many units. Service life is often a manufacturer's rated or recommended usage period, which may include safety margins or assumptions about conditions. MTTF reflects how your parts actually perform in your environment, so it can differ from the published service life figure.

Want to track MTTF, replacement intervals, and preventive work orders in one place? Book a Fabrico demo to see how real-time monitoring and CMMS turn component reliability data into fewer surprise breakdowns on your line.

Latest from our blog

Define Your Reliability Roadmap
Validate Your Potential ROI: Book a Live Demo
Define Your Reliability Roadmap
By clicking the Accept button, you are giving your consent to the use of cookies when accessing this website and utilizing our services. To learn more about how cookies are used and managed, please refer to our Privacy Policy and Cookies Declaration