There are 2 stored owner reports matching the tires & wheels leading-label group for the 2008 Lincoln Navigator in our NHTSA-sourced dataset. These are unverified consumer reports and may not reflect confirmed defects.
This group counts stored reports whose component label starts with one of this site's matching prefixes, ignoring case. Each matching report counts once within the group. Components mentioned later in the label or only in the narrative are not searched. How component counts work
Loaded 2 of 2 matching reports.
Open the full vehicle complaint log (all categories)FACTORY CHROME PAINTED WHEELS PEELING CAUSED TIRE BLOWOUT ON THE HIGHWAY. THE CHROME SEPARATES FROM THE ALUMINUM WHEEL AND THE TIRE STARTS TO LOSE AIR OR IN MY CASE BLOW OUT. THIS IS A HUGE SAFETY RISK AND THERE'S NOT ANYTHING I'M ABLE TO DO. THIS IS HAPPENING WITH MANY OTHER LINCOLN VEHICLES THAT HAVE CHROME PAINTED WHEELS FROM 2007 TO 2014. LINCOLN HAS NO ANSWERS FOR ME AND SUGGEST I ORDER FACTORY WHEELS. NEW FACTORY WHEELS WILL JUST START PEELING AGAIN.
TL*THE CONTACT OWNS A 2008 LINCOLN NAVIGATOR. THE CONTACT STATED THAT HIS WIFE HAD A FLAT TIRE ON THE REAR PASSENGER SIDE OF THE VEHICLE. HE NOTICED THAT THERE WERE TWO DIFFERENT TIRE SIZES ON THE VEHICLE. THE FRONT TIRES WERE LARGER THAN THE REAR TIRES. HE BELIEVED THAT THE DIFFERENCE IN THE TIRE SIZES COULD POSSIBLY CAUSE A POTENTIAL SAFETY HAZARD. AT THE TIME OF THE COMPLAINT, THE CONTACT COULD NOT LOCATE THE TIRE SIZES. THE CURRENT MILEAGE WAS APPROXIMATELY 7,000 AND FAILURE MILEAGE WAS APPROXIMATELY 3,000. THE TIRE HAD A NAIL IN IT. ALSO THE TIRE PRESSURE SENSOR WAS INOPERATIVE. UPDATED 07/08/08
Complaints are unverified consumer reports submitted to NHTSA. A high complaint count may reflect vehicle popularity, not defect severity. Data sourced from NHTSA public records.
NHTSA source checks for this vehicle year
Checks are recorded separately for each dataset, not for the whole page. Dates use UTC. A missing check date does not mean no records exist.
Vehicle import recorded: Apr 28, 2026. This is the stored import date, not confirmation that every source was successfully refreshed.