Fleet Breakdown Costs SA: Downtime, MTBF and MTTR

Published: 29 June 2026
Updated: 30 October 2026

Fleet breakdown costs in South Africa are much larger than the repair invoice. When a haul truck fails on a mine road or a tipper stops on the N12, you pay for recovery, emergency parts and after-hours labour, but the bigger losses are lost loads, contract penalties, a driver paid to wait and other trucks held up behind the problem. Most operators cannot say what downtime costs them because they do not track it consistently. This guide shows how to work out the real cost of a breakdown, how to measure downtime with clear categories and KPIs such as availability, MTBF and MTTR, how to use that data to cut unplanned failures, and how a written breakdown response protocol shortens the time a stopped vehicle costs you, with particular attention to mining transport.

For the wider method of analysing maintenance spend, see our pillar guide on maintenance cost analysis.

What a Fleet Breakdown Really Costs

Split every breakdown into direct and indirect costs. The direct costs are easy to find on invoices; the indirect costs are usually larger and rarely calculated.

| Cost layer | What to include | Where to find it |
|---|---|---|
| Recovery | Tow truck, heavy recovery, call-out fees | Supplier invoices |
| Parts | Emergency sourcing premiums, courier charges, parts damaged by the failure | Purchase orders, job cards |
| Labour | Overtime and after-hours rates, mobile technician travel | Workshop timesheets, payroll |
| Driver costs | Wages while waiting, accommodation and meals when stranded | Payroll, expense claims |
| Lost revenue | Loads missed or handed to a subcontractor while the vehicle is off the road | Trip and invoicing records |
| Contract penalties | Missed delivery windows, availability guarantees not met | Customer contracts, credit notes |
| Knock-on effects | Other vehicles delayed, loading or plant operations idled, rescheduled trips | Dispatch records |

A worked example

The figures below are illustrative only. Replace them with your own rates.

A tipper that earns R15,000 per day breaks down on a delivery run and is off the road for three days:

• Recovery: R12,000
• Parts, including an emergency sourcing premium: R9,000
• After-hours labour: R4,000
• Driver wages and accommodation while stranded: R3,000
• Lost revenue: 3 days x R15,000 = R45,000
• Total: R73,000, of which the repair itself (parts and labour) is R13,000, under a fifth of the total

If the customer contract carries a penalty for missed loads, or the breakdown blocks a loading point, the figure climbs further. Our sibling analysis of the true cost of a single unplanned breakdown in a tipper fleet walks through these layers in more detail.

Fixed costs keep running

While a vehicle stands, finance repayments, insurance, licensing and depreciation continue with no revenue against them. As an illustration, if a truck's kilometres scale with its availability, dropping from 85% to 70% availability spreads the same fixed costs over roughly 18% fewer kilometres, which raises the fixed cost per kilometre by about 21% (85 divided by 70). This is invisible unless you track downtime alongside your cost per kilometre.

Why Mining Transport Breakdowns Cost More

Mining transport puts far more stress on vehicles than general road freight, and failures have bigger consequences.

• Haul roads: surfaces change constantly with weather, traffic and grading. Potholes, corrugations and dust create vibration loads that accelerate wear on suspension, chassis and tyres.
• Load cycles: a haul truck completes many short load cycles per shift, each one loading the chassis, hydraulics and drivetrain, compared with a few long trips for a road freight vehicle.
• Heat: summer temperatures at Northern Cape and Limpopo operations put cooling systems, transmission fluid and hydraulic oil under sustained thermal stress.
• Dust: fine dust penetrates seals and clogs filters, which is why mining fleets usually run shorter service intervals than the same vehicle would need on tar.
• Gradients: loaded descents and empty climbs on ramps put heavy loads on brakes, retarders and transmissions.
• Blocking: one failed vehicle on a single-lane haul road can stop the trucks behind it, idle loading equipment and hold up the plant.

Mine sites also add a safety and legal dimension. The Mine Health and Safety Act and its regulations place duties on employers for trackless mobile machinery, including codes of practice, inspections and defect control. A vehicle with a safety-critical defect must not operate, and maintenance records are evidence in any inspection or incident investigation. Our mining transport compliance guide covers these obligations; confirm the current requirements with the Department of Mineral and Petroleum Resources or your mine's safety function.

How to Track Fleet Downtime

You cannot reduce what you cannot measure, and spreadsheet tracking usually fails in three ways:

1. Data is captured after the fact. By the time someone updates the sheet, nobody remembers whether the truck was down for four hours or six.
2. Categories are inconsistent. One supervisor writes "mechanical failure", another writes "engine problem" for the same type of fault, and trend analysis becomes impossible.
3. There is no live view. Decisions about recovery, replacement vehicles and customer communication need to happen immediately, not at month end.

The five downtime categories

Record every hour a vehicle is unavailable against one of these categories.

| Category | Examples | Key data to capture |
|---|---|---|
| Planned maintenance | Scheduled services, inspections, COF preparation | Planned vs actual duration, cost per service |
| Unplanned repair | Roadside breakdowns, depot failures | Component, root cause, location, parts wait time |
| Accident and incident | Collisions, rollovers, damage on site | Incident type, driver, days out of service, claim status |
| Compliance hold | Expired COF or licence disc, overloading, failed inspection | Hold reason, days to resolve, fines |
| Driver unavailable | No qualified driver, expired PrDP, fatigue, scheduling gaps | Reason, duration, loads affected |

Planned maintenance counts as downtime too. Excluding it makes your availability figures fiction, and a service planned for eight hours that routinely takes twelve is a workshop problem worth fixing. Accident downtime should link to your incident process, and compliance holds are almost always preventable with expiry alerts.

Under unplanned repairs, add subcategories that fit your fleet, such as engine and drivetrain, electrical, tyres and suspension, brakes, cooling, hydraulics and trailer coupling.

Capture points and ownership

Downtime must be recorded when it starts and when it ends:

• A driver app or call-in procedure for roadside breakdowns
• Workshop check-in and check-out for depot repairs
• Dispatch updates when trips are reallocated
• Compliance calendar alerts for planned holds

Make one person, usually the workshop manager or fleet controller, responsible for data accuracy, and include it in their KPIs. Review incidents weekly, availability monthly and failure trends quarterly.

Downtime KPIs: Availability, MTBF and MTTR

Three numbers tell you most of what you need to know.

Availability

Availability = (Scheduled hours - Downtime hours) / Scheduled hours x 100

Worked example: a truck is scheduled for 20 hours a day over 26 days, giving 520 scheduled hours. It loses 60 hours to downtime across all five categories. Availability is (520 - 60) / 520 = 88.5%.

Use the same definition of scheduled hours for every vehicle, and decide whether you measure against calendar time or operating time. Many mining and contract haulage agreements specify an availability level, so measure it the way your contract does.

Mean time between failures (MTBF)

MTBF = Operating hours (or km) / Number of unplanned failures

Worked example: a truck ran 2,400 engine hours in six months and had four unplanned failures. MTBF is 600 hours. A falling MTBF on a vehicle tells you it is becoming less reliable; comparing MTBF across vehicles of the same type identifies problem units.

Mean time to repair (MTTR)

MTTR = Total repair hours / Number of repairs

Worked example: those four failures took 48 hours to repair in total. MTTR is 12 hours. Long MTTR usually points to parts availability, technician availability or slow recovery, not the failure itself. Measure from the moment the vehicle stopped to the moment it was back in service, not just workshop hours, or you will miss the time spent waiting for recovery and parts.

Other useful measures

• Planned vs unplanned ratio: share of maintenance jobs, and hours, that were scheduled
• Cost per downtime hour: labour, parts, external services and lost revenue divided by downtime hours
• Repeat failures: the same component failing again within a short period, a sign of poor root-cause work
• Maintenance cost per operating hour or per km: the core figure for comparing vehicles and tracking trends

Using Downtime Data to Cut Breakdowns

After three to six months of consistent data, patterns emerge.

Identify problem vehicles. Data turns a hunch into a case. If one unit's unplanned repair cost is several times the fleet average and its MTBF keeps falling, you can justify replacing it rather than repairing it again.

Set intervals from your own failure history. Manufacturer intervals assume average conditions. If a component consistently fails well before its expected life on your routes, move its replacement into a planned service window. This is preventive maintenance driven by your data; our guide to choosing a preventive maintenance system covers the scheduling side.

Use condition monitoring on high-value assets. Oil analysis, temperature trends and telematics fault codes show developing problems before they become failures. A rise in fuel consumption against a vehicle's own baseline is often an early warning.

Stock critical spares. For each vehicle type, list the parts that fail most often and have the longest lead times. A low-cost part with a two-week lead time can turn a one-day repair into a fortnight off the road.

Target driver training. If accident or abuse-related downtime clusters around particular drivers or behaviours, such as over-revving, harsh braking or overloading, address it through coaching before it becomes a maintenance problem.

Fix haul roads and speed on mine sites. Road surface, drainage, gradients and speed all affect tyre life and component wear. Downtime data by route helps make the case for road maintenance spend.

Breakdown response for mining operations

Even good maintenance will not prevent every failure. The difference between a four-hour and a four-day delay is often your response capability:

• Mobile workshop vehicles with common parts, fluids and tools on each shift
• Recovery equipment sized for your heaviest loaded vehicle
• Technician cover matched to your shift pattern, costed against your downtime cost per hour
• Maintenance work planned into natural gaps between shifts

Map your response time from breakdown to technician on site and from breakdown to return to service. Those two numbers, tracked over time, show whether your response capability is improving.

Building a Breakdown Response Protocol

Most of the cost of a breakdown builds up in the hours after the vehicle stops: waiting for someone to decide what to do, phoning around for a recovery truck, and telling the customer too late. A written protocol that every driver and controller knows turns that into a routine. Keep it on paper in the cab as well as on the phone, because phones go flat.

Driver actions

1. Make the scene safe. Move off the road if possible, switch on the hazard lights and place the warning triangle at least 45 metres from the vehicle on the side of approaching traffic, as the National Road Traffic Regulations require. Wear a reflective vest.
2. Secure the load. Make sure cargo cannot shift or spill. For dangerous goods, follow the emergency information carried with the load.
3. Report straight away to the control room using the agreed channel (phone, radio or driver app). Never assume someone else has reported it.
4. Give the controller the essentials: exact location (GPS position or nearest kilometre marker or landmark), registration and fleet number, what happened and any warning signs beforehand, load details and customer, and whether the driver is injured or at risk.
5. Take photos of the vehicle, any damage and the surroundings. They support insurance claims and the root-cause record.

If the breakdown involves a collision, the National Road Traffic Act also requires the driver to report the accident to a police or traffic officer, within 24 hours where someone is injured or killed, otherwise on the first working day after it.

Control room actions and escalation

The controller needs the authority, and the contact list, to act without waiting for approval. Set target times that suit your operation, for example: log the event and confirm driver safety first, decide roadside repair or recovery next, then call the service provider, update the customer and decide on a replacement vehicle or load transfer. Logging the start time is what later feeds your MTTR.

Grade each event so the response matches the impact:

| Level | Situation | Typical response |
|---|---|---|
| 1 | Minor fault, vehicle continues after a roadside fix | Controller handles, logs the event |
| 2 | Vehicle immobilised but repairable on site the same shift | Mobile technician or roadside service, customer told of delay |
| 3 | Vehicle needs recovery, repair time unknown | Recovery provider called, replacement vehicle or load transfer considered, operations manager informed |
| 4 | Injury, cargo damage, spill or third-party involvement | Senior management, insurer and the relevant authorities notified at once |

Communication chain: who is told and when

Write down who must be told at each level, and in what order:

• Immediately: control room or transport manager (with a named backup) and the workshop manager, who decides on repair or recovery.
• For level 3 and 4 events: operations manager or director, plus finance where large costs or penalties are likely, and HR where driver welfare is involved.
• The customer: as soon as a delay is confirmed, with a realistic revised arrival time, any alternatives (partial delivery, a different vehicle) and written confirmation afterwards. Update them before they have to chase you. Early, honest notice is often what keeps a penalty clause from being enforced.
• Insurer: as early as your policy requires for any event likely to lead to a claim.
• Authorities: accidents to the police as above; dangerous goods incidents as your emergency procedures and the dangerous goods regulations require; incidents on a mine to the mine's safety function, which handles reporting under the Mine Health and Safety Act.

Agree how often open events are updated (for example every two hours) and record every call and message against the event, so the timeline is available for the customer, the insurer and your own review.

Recovery and service provider agreements

A recovery operator you have never used will charge emergency rates and may not have a vehicle that can lift your heaviest combination. Set up agreements before you need them:

• Coverage: at least two recovery providers for each section of your regular routes, plus the dealer or approved workshops for your vehicle makes, with after-hours numbers
• Capability: confirm they can recover your heaviest loaded vehicle, including interlinks and mining trucks
• Response time: a written target response time for each corridor
• Pricing: call-out fee, rate per kilometre or flat rate, after-hours premium and waiting time, agreed in advance
• Payment: account terms, so nobody has to find cash at 3am
• Storage and security: a secure yard if the vehicle or load cannot be moved on the same day

Store these contacts against routes in your fleet system so the controller is not searching a phone. Pay on time and review the relationship once a year; providers prioritise the clients who treat them well. Telematics helps here too: an unexpected stop on route, an engine fault code or a panic alert can tell the controller about a problem before the driver calls, and the vehicle's position can be shared with the recovery provider directly. See our telematics guide for what to expect from a tracking contract.

Train drivers on the protocol at induction and refresh it regularly, ideally with a short drill, so the first time they use it is not at night on the side of the N3.

Common Downtime Tracking Mistakes

• Tracking only breakdowns and ignoring planned maintenance
• Ignoring partial downtime, such as a vehicle running derated or at reduced payload because of a fault
• Not capturing driver waiting time, which is a real cost of the breakdown
• Leaving events open, which creates phantom downtime that never ends in your reports
• No root cause, recording "brake failure" without noting whether it was wear, adjustment, a defective part or driver abuse

How T-ERP Helps

T-ERP records maintenance jobs and downtime against each vehicle with standard categories, so availability, repair history and costs come from the same records rather than a separate spreadsheet. Work orders capture parts, labour and external costs, telematics readings keep service schedules current, and maintenance spend flows into vehicle and cost-per-kilometre reporting. For mining contractors, inspection, defect and service records stay with the vehicle for audits and incident investigations. See how this works on our fleet maintenance software page.

Conclusion

The repair invoice is usually the smallest part of a breakdown. Lost revenue, penalties, driver costs and knock-on delays make up most of the total, and in mining transport those indirect costs are amplified by harsh conditions and site safety obligations. The fix starts with measurement: record every hour of downtime against five consistent categories, calculate availability, MTBF and MTTR, and cost each event properly. Then use the data to replace problem units, adjust service intervals, stock the right spares and target training.

Operators who measure downtime carefully are the ones who reduce it systematically. If you would like to see how T-ERP would track downtime and maintenance costs across your fleet, schedule a consultation.

Sources

• Department of Mineral and Petroleum Resources - administers the Mine Health and Safety Act and its regulations for mine sites
• Road Transport Management System (RTMS) - industry self-regulation scheme for heavy vehicle operators
• National Road Traffic Act 93 of 1996, section 61: duty of driver in event of accident - accident reporting to police within 24 hours or the next working day
• Arrive Alive: the emergency triangle and safety on the road - summary of the National Road Traffic Regulations on carrying and placing a warning triangle at least 45 metres from the vehicle

---

The information in this article is for general guidance only. Regulations and requirements may change - always verify current requirements with the relevant South African regulatory authority.

Frequently Asked Questions

How do I calculate the cost of a fleet breakdown?

Add the direct costs (recovery, parts, labour, driver wages and accommodation) to the indirect costs (revenue from loads missed while the vehicle is off the road, contract penalties, and delays to other vehicles or operations). Use your own invoices, rates and trip records. In most cases the repair bill is a small share of the total, and lost revenue is the largest single item.

How do I calculate fleet availability?

Availability is scheduled hours minus downtime hours, divided by scheduled hours, multiplied by 100. For example, a truck scheduled for 520 hours in a month that loses 60 hours to downtime is 88.5% available. Include planned maintenance as downtime, and use the same definition of scheduled hours for every vehicle, or the way your customer contract defines it.

What are MTBF and MTTR in fleet maintenance?

MTBF, mean time between failures, is operating hours or kilometres divided by the number of unplanned failures; it measures reliability. MTTR, mean time to repair, is total repair time divided by the number of repairs; it measures how quickly you get vehicles back in service. Measure MTTR from breakdown to return to service so recovery and parts waiting time are included.

Should planned maintenance be counted as downtime?

Yes. Planned maintenance still makes a vehicle unavailable. Tracking it lets you compare planned and actual service durations, spot workshop overruns and schedule services into natural gaps. Leaving it out overstates availability and hides workshop inefficiency, which makes your downtime reporting misleading.

How can mining transport operators reduce vehicle downtime?

Shorten service intervals for dusty and severe-duty work, use oil analysis and telematics fault codes on high-value vehicles, hold critical spares with long lead times, build on-site breakdown response for each shift, and track availability, MTBF and MTTR per vehicle. Haul road condition and speed control also have a large effect on tyre and component wear.

What should be in a fleet breakdown response plan?

Written driver steps (make the scene safe, secure the load, report with exact location and details, take photos), a control room procedure with escalation levels, a communication chain that names who is told and when, including the customer and insurer, and pre-agreed recovery and service providers for every route section. Record the start and end of every event so the plan's effect shows up in your MTTR.

Should I have agreements with recovery and towing companies?

Yes. Agreeing response times, rates, after-hours premiums, account terms and storage in advance avoids emergency pricing and delays at night, and confirms the provider can actually recover your heaviest loaded vehicle. Hold at least two providers per route section so one being busy does not leave a truck stranded.

How long does it take to see results from downtime tracking?

Problem vehicles and obvious gaps, such as long parts waits, usually show up within the first one to two months. Reliable trend data for adjusting service intervals needs three to six months of consistent capture. Improvements in availability then depend on how quickly you act on what the data shows.