There are 3 stored owner reports matching the engine leading-label group for the 2024 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)I got this 2024 vehicle brand new with 15 miles on it in August of 2025 . It is now January of 2026 by check engine light had came on 7 times since November of 2025. I had to shut down work because of this . It came on the 8th time today and I was told by the delearship that they didn’t know what to do . My truck is at 43,000 miles and literally a piece of junk.
After the engine replacement, the tractor continues to operate unreliably, and I cannot use it in my business because it is unreliable.
The contact owned a 2024 RAM 3500. The contact stated that after starting the vehicle and idling on the driveway, it caught on fire in the engine compartment. The vehicle was engulfed in flames. The fire department arrived and extinguished the fire. The origin of the fire was unknown. The entire engine compartment was burnt and the vehicle was destroyed. The vehicle remained at the scene where it caught on fire. No injuries were sustained. A fire department report was filed. The manufacturer was notified of the failure. The failure mileage was approximately 2,600.
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.