What we found when we looked at the MOT history of over 62.7m vehicles.
We analysed over 560m individual MOT tests from 2005-2020.
Date Published: 9th July 2020
Author: David James, CEO
Source of the data used
We analysed over 560 million individual MOT test records, from over 62.7 million unique vehicles to see if we could find any interesting data or trends. The data used in this analysis comes from the DVSA (Driver and Vehicle Standards Agency) who make the full MOT history database available for registered businesses and users to download.
This bulk DVSA MOT history data gives us a wonderful insight into vehicle usage and mileage fraud trends spanning over a decade. Our findings detail one of largest and most comprehensive analysis of the MOT data since it was made available in bulk format. The analysis highlights, more than ever, the need to get a full vehicle history check before you buy a used vehicle as there are so many data points to analyse now, it would be easy to miss some important history without one. We hope you enjoy our findings and if you have any questions or queries please do get in touch via email at firstname.lastname@example.org
- Mileage fraud
- Most affected vehicles
- Vehicle age and mileage fraud
- Distances travelled per year
- Issues with the MOT data input methods
Our top 5 findings:
- Across all 62.7m vehicles, 3.42m, 5.45% (1 in 18) of vehicles showed a reduction in mileage between MOT’s, when removing data anomalies.
- The accuracy of the mileage data depends heavily on it being entered correctly by the MOT tester, small errors can cause large data issues. We found 1.43m mileage reductions that look like data input errors.
- The most ‘clocked’ vehicle in the UK was the Ford Transit, followed by the Ford Focus and Ford Fiesta.
- Average miles travelled per year has reduced from 7,883 miles in 2007 to 7,262 miles in 2019 a -7.8% decrease in 12 years.
- On average vehicles have their mileage reduced by 46,089 miles when they are ‘clocked’.
Mileage fraud/Clocking is the act of reducing a vehicles mileage in an attempt to mislead someone as to its genuine mileage. This may happen in order to increase a vehicles value at sale, or to avoid paying extra as part of strict mileage limits imposed on new car finance deals such as PCP (Personal contract purchase).
Some very interesting figures came out of our analysis of the MOT mileage data. Firstly, we found 3.42m vehicles (from the total set of 62.7m vehicles) that had an odometer reading reduction (potential mileage fraud) from the year previous.
This is a means 5.45% of the vehicles in the data set showed a reduction in their odometer value, or 1 in every 18 vehicles.
The average number of miles an odometer would reduce over all 3.42m vehicles was 46,089 miles.
There were an additional 1.43m vehicles that showed a reduction in mileage but on further analysis appeared to be data input errors, see detailed analysis in our issues with the MOT data input methods. Suggesting there could be improvements made to the way the data is input during MOT tests.
Most affected vehicles
We analysed both manufacturer and model specific data to build a picture of the vehicles most affected by mileage fraud. We looked a vehicles that had a recent MOT (2019 or 2020) to focus the results on vehicles currently on the road.
TABLE 1: Top 50 Vehicle models with mileage reductions for all vehicles that had an MOT in 2019 Or 2020.
|Rank||Manufacturer||Model||% Of Total|
|50||LAND ROVER||RANGE ROVER||0.8|
Vehicle age and mileage fraud
As you may expect, older vehicles are more likely to have been subject to mileage fraud, this is for two main reasons
i) Older vehicles have travelled further and thus there is more incentive to reduce their mileage in order to increase the value of the vehicle
ii) Older vehicles have existed for longer, and there has simply been more opportunity to adjust their mileage, older vehicles are likely to have a higher number of previous owners and thus more likely to have had an owner who intended on adjusting the mileage.
Vehicles manufactured more than 10 years ago are far more likely to have be subject to mileage fraud by reducing the odometer reading.
Distances travelled per year
Below are the average (and median) mileages per year since 2007. It is interesting to see the general downward trend in average mileage, only to be exacerbated in 2020 so far with the consequences of COVID-19 on travel.
|Year||Average Mileage||Median Mileage|
Issues with the data input methods
When the data was being analysed it became immediately apparent that the data contained some errors. This is expected, as the data is entered manually by MOT testers, and any manual entry of data will be subject to errors.
Generally, these manual input errors can be classified in one of two ways transcription errors (errors in pressing the wrong key or option) or transposition errors (entering data in the wrong order).
Nowadays MOT testers complete MOT tests on vehicles and enter the results electronically via the DVSA’s MOT service, since 2015 the DVSA’s MOT testing service has been used to record all MOT’s, you can see an example of the system on the DVSA Matters Of Testing Blog.
Small adjustment issues
We found two main groups of error when analysing the MOT data, the first one concerns what we expect to be a transcription error in most cases. We found a large number of vehicles (669,525, 13% of all mileage discrepancies) were flagged as having a mileage reduction but had their mileage adjusted by less than 300 miles. In addition to this we found the average level of mileage reduction below 300 miles was just 69 miles.
As the main objective of clocking/mileage fraud is to increase the value of the vehicle (or, more accurately, to prevent a reduction in its value), it is highly unlikely that someone would attempt to adjust the odometer to read less than 300 miles fewer miles as it would have almost zero effect on the vehicles overall value. These errors are small errors caused by incorrect entry by MOT testers, who often write down the vehicle mileage on a piece of paper when conducting the test, then enter the values on a computer later on.
You can see in the image below an example, where an MOT tester has accidently typed 69,124 instead of 69,134 to make it appear as though the vehicle has travelled -10 miles on the same day, when it was re-tested after an MOT failure.
Large adjustment issues
Similarly we found that there was a large number of vehicles (255,735 5% of all mileage discrepancies) that had a mileage reduction of more than 300,000 miles. The average of those vehicles that appeared to have been ‘clocked’ more than 300,000 miles was 592,000 miles. Looking at the records it is clear to see what happens in most of these cases:
Generally, it is as simple as the MOT tester entering one to many digits into the odometer reading field for example, if the true odometer reading was 63,580 miles, but the MOT tester entered 633,580 miles (note the extra number 3), the vehicle appears to have travelled and extra 570,000 miles. A year later at the vehicles next MOT, assuming the correct mileage is entered, say 75,250 miles, it looks like the vehicle has reduced its mileage by over 500,000 miles.
We know that most modern vehicles have a design life of 150,000 miles, so can assume any vehicle appearing to have been ‘clocked’ by more than 300,000 miles is simply a mistake. You can see in the below image below an example, it is clear to see an MOT tester has entered an extra zero, they should almost certainly have entered 53,023 miles instead of 530,023 miles.
Mix of miles and kilometres in the odometer format
In modern vehicles, with digital dashboards, it is possible to change the format of odometer and speedometer from miles to kilometres, generally in the U.K we use miles as this is way our speed limits are enforced. Therefore, whilst possible, it should be rare for a vehicle to move from recording it’s distance in miles to recording it in kilometres.
We noticed, when analysing the data that many vehicles would change the format of the odometer reading, this would often result in the vehicle appearing to be ‘clocked’, for example if a vehicle moves from 1000 miles to 1500 kilometres (932 miles) this is actually a reduction of 68 miles. We suspected, that in many cases MOT testers were simply selecting the wrong odometer format when recording the MOT result.
In order to test this we measured the total number of vehicles with a mix of odometer formats that showed a mileage reduction, this was found to be 626,820 (12.9% of all mileage discrepancies). To see if this issue was due to input error we ran an experiment and assumed all of the odometer formats were identical, we found that 81.3% of suspected mileage fraud cases would not be recorded as mileage fraud if the odometer formats were the same. To put this simply, it would appear in the vast majority of cases, these ‘clocking’ issues are actually input errors.
As you can see in the below image, an entry 81,209 miles makes the vehicle appear to have it’s mileage reduced at its next MOT, when if it were recorded as kilometres, it would not.
If you remove the entries explained above from the set of vehicles we found had mileage reductions between MOT’s (i.e. Less than 300 miles, more than 300,000 miles and a mix of miles and kilometres that looks like a mileage reduction, but would not be if you assume the odometer format change was an input error), it would account for 29.5% of all records identified as ‘clocking’. This level of errors is not uncommon when entering information once, one study showing that visual checking resulted in 2958% more data entry errors than double entry (see references 1 & 2 below)
How do MOT testers enter the odometer value?
We were lucky enough to be shown a demonstration of the MOT testing system, here is what the user currently sees when they have to enter an odometer reading (The vehicle we were using had 68k miles on the odometer at the last MOT):
If a tester enters a lower odometer value, or a value significantly higher they are warned (it is quite small text, below the numerical value of miles), but, importantly, this warning only appears later in the flow, no warning is present on the page in which the odometer reading is entered. The tester has already entered the value and is likely moving on to other tasks:
There was no warning on screen if the MOT tester entered a odometer format that was different to the last MOT, i.e. going from miles to kilometres.
Once you move past the above screen, you are no longer warned about the odometer issues again, see the MOT summary screen here, this is the last screen before the results are saved:
It would appear, that with a few small changes (detailed below) there could be significant improvements in the data accuracy of the odometer readings.
Can the data be altered when it is incorrect?
The DVSA do have a process for fixing mileage issues recorded at an MOT, it is significantly easier to do if the issue is spotted withing 28 days of the MOT date, after which more documentation is required in order to enact a change.
Feedback to the DVSA
We fed-back all of our findings to the DVSA and made a few suggestions in order to improve the current system:
- Ask the MOT Tester to verify the odometer reading by entering it twice (Shown to improve accuracy, see references 1 & 2 below)
- Warn the user when entering an odometer value that is less than the previous entry, ask them to re-check and confirm on the odometer reading entry page, make it clear and obvious.
- Warn the user when entering an odometer value that is significantly higher than the previous entry, e.g. more than 100,000 miles more, ask them to re-check and confirm on the odometer reading entry page, make it clear and obvious.
- Warn the user when entering an odometer format (miles or kilometres) that is different to the previous entry, ask them to re-check and confirm on the odometer reading entry page, make it clear and obvious.
- Show a warning message on the MOT test review page to indicate if are any of the above four issues are present.
Hopefully these suggestions will help the DVSA reduce the transcription and transposition errors we have seen the MOT data.
- Barchard, Kimberly & Pace, Larry. (2011). Preventing human error: The impact of data entry methods on data accuracy and statistical results. Computers in Human Behavior. 27. 1834-1839. 10.1016/j.chb.2011.04.004.
- Goldberg, Saveli & Niemierko, Andrzej & Turchin, Alexander. (2008). Analysis of Data Errors in Clinical Research Databases. AMIA Annual Symposium proceedings / AMIA Symposium. AMIA Symposium. 2008. 242-6.