There are 3 stored owner reports matching the lighting leading-label group for the 2015 Ram 3500 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 3 of 3 matching reports.
Open the full vehicle complaint log (all categories)WATER GETS INTO THE HEADLIGHT HOUSING AND STAYS IN THERE UNLESS HEADLIGHTS ARE REMOVED AND WATER IS RELEASED. *TR
TL* THE CONTACT OWNS A 2015 RAM 3500. THE CONTACT STATED THAT THE HEADLIGHTS KEPT GOING OUT SEVERAL TIMES. THE CONTACT REPLACED ALL OF THE BULBS, SPECIFICALLY THE LOW BEAM HEADLIGHTS, BUT THE FAILURE RECURRED SEVERAL TIMES. THE CONTACT STATED THAT THE HIGH BEAM HEADLIGHTS OPERATED NORMALLY. THE DEALER (CLASSIC CHRYSLER DODGE JEEP RAM, 1102 WALTON DR, TEXARKANA, TX 75503, (903) 716-0600) SCHEDULED A DIAGNOSTIC APPOINTMENT FOR NEXT WEEK. THE CONTACT INDICATED THAT HE HAD TWO OTHER 2016 RAM 3500 VEHICLES THAT EXHIBITED THE SAME FAILURE. THE MANUFACTURER WAS NOT CONTACTED. THE FAILURE MILEAGE WAS 58,000.
TL* THE CONTACT OWNS A 2015 RAM 3500. AFTER DRIVING THE VEHICLE, THE CONTACT STATED THAT THE FOG LAMP GLASS COVERS FRACTURED ON THE DRIVER'S SIDE. THE VEHICLE WAS TAKEN TO THE DEALER WHERE THEY DIAGNOSED THAT THE FOG LAMP ASSEMBLY NEEDED TO BE REPLACED ENTIRELY. THE VEHICLE WAS NOT REPAIRED. THE MANUFACTURER WAS MADE AWARE OF THE ISSUE. THE APPROXIMATE FAILURE MILEAGE WAS 15,000.
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.