There are 2 stored owner reports matching the lighting leading-label group for the 2003 Nissan Xterra 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)HEADLIGHTS CAME ON AND OFF WHILE VEHICLE WAS IN MOTION. CONSUMER TOOK VEHICLE BACK TO THE DEALER ON THREE OCCASSIONS TO HAVE THE PROBLEM RESOLVED. HOWEVER, THE PROBLEM RECURRED. *AK
MY HEADLIGHTS JUST WENT OUT IN THE MIDDLE OF DRIVING AT NIGHT. LUCKILY THERE WASN'T ANYONE ELSE AROUND ME ON THE INTERSTATE, BECAUSE THAT COULD HAVE BEEN A REALLY NASTY WRECK. I PULL OVER ON THE SHOULDER OF THE ROAD AND WIGGLE THE WIRES AND THEY CAME BACK ON. I DROVE HOME AND CHANGED THE LIGHT BULBS, THINK THAT WOULD FIX THEM. ABOUT TWO MONTHS LATER IT HAPPENED AGAIN, THAT IS WHEN I FOUND OUT THAT THE HEADLIGHT SOCKETS ON MY TRUCK WERE BURT UP. I WAS TOLD THAT IT WAS CAUSED BY HEAT FROM THE HEADLIGHTS. I WENT TO AUTO ZONE AND BOUGHT NEW ONES AND REPLACED THEM. I CALLED NISSAN AND THEY SAID BECAUSE MY TRUCK WAS OUT OF WARRANTY THEY COULDN'T DO ANYTHING ABOUT IT. I JUST WANT TO MAKE SURE THAT SOMEONE KNOWS THAT A TRUCK THAT IS ONE YEAR OLD IS ALREADY HAVING PROBLEMS WITH ITS HEADLIGHTS. ALSO TO MAKE SURE THAT THERE ISN'T SOMETHING WRONG WITH THE HEAD LIGHTS THAT NISSAN PUTS INTO THE CARS.*AK
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.