2002 Land Rover Defender 2.5L Diesel · KC02 ADC

The vehicle is currently roadworthy, but the maintenance history reveals a trend of reactive repairs rather than preventative care. While it passed the May 2026 test at 111,822 miles, this followed a significant failure just one month prior. That failure involved multiple hydraulic brake leaks at the central pipe and the ABS pump connection, alongside an active ABS fault light, indicating that critical safety components were only addressed when they necessitated an immediate test failure. The mileage profile is exceptionally low for a vehicle of this age, covering only 111,822 miles over 24 years. This averages to fewer than 4,700 miles per year, suggesting the vehicle has spent long periods stationary or seen minimal use. Between April 2024 and April 2025, the vehicle covered only 419 miles. Such low usage on a Land Rover Defender often leads to the degradation of rubber components and internal corrosion within fluid lines, which aligns with the recent brake pipe leaks and hose corrosion noted in the records. A buyer must conduct a thorough inspection of the structural integrity of the chassis and body mounting points. Although the April 2025 test noted holes in the body mounting outer skin outriggers, these were classified as non-structural at the time. The recurring mention of heavy undersealing across several years suggests an attempt to manage rust, but the buyer needs to verify that this thick coating is not hiding deeper structural corrosion in the chassis rails, particularly around the torsion bar areas where skin issues were previously identified. The electrical system and braking assembly also require scrutiny. The April 2025 failure for total headlamp malfunction and aim issues suggests potential wiring loom failures or switch failures that may recur. Given the recent ABS fault and multiple pipe leaks in April 2026, the hydraulic system should be pressure tested for further leaks and the ABS module scanned for stored fault codes to ensure the electronic issue was fully resolved.