Skip to content

2004 Peterbilt 330 Recalls, Complaints & Specs

2 safety recalls list the 2004 Peterbilt 330, and owners have filed 1 complaint with NHTSA. Check your own VIN below.

2
safety recalls
1
owner complaint to NHTSA

2 safety recalls for the 2004 Peterbilt 330

Most recent first. Recall repairs are free at any authorised dealer. Click a recall for the full defect, consequence and remedy text.

  1. Engine and engine cooling

    NHTSA 04V406000 Reported 106 vehicles potentially affected PACCAR INCORPORATED

    On certain trucks built with cummins isc and isl engines, plugs were assembled incorrectly creating stress and cracks which could cause an oil leak.

    Remedy: Cummins will notify owners and arrange for installation of a steel cup plug boss cap. Owners should contact cummins at 1-800-343-7357.

  2. Fan (engine and engine cooling)

    NHTSA 03V306000 Reported 1,858 vehicles potentially affected PACCAR INCORPORATED

    On certain trucks equipped with caterpillar c7 or 3126e 2002 engines and horton fan hubs, the fan hub mounting bolts can fail resulting in the hub and fan assembly separating from the engine. This loss of clamp load causes unwanted vibration in the assembly that leads to bolt failure.

    Remedy: Dealers will add a rigid spacer across the two lower mounting holes of the fan hub to maintain the clamping force and replace all the bolts and washers. Owner notification began october 22, 2003. Owners should contact…

1 owner complaint filed with NHTSA

Owners of the 2004 Peterbilt 330 have filed 1 complaint with NHTSA. The average mileage at failure in those reports is 8 miles. Complaints peaked in 2005 with 1 filed that year.

Most-reported components

What owners are reporting

“Dt: the vehicle experienced numerous problems. The vehicle currently has an engine problem (no power) that the dealer is unable to locate. The dealer told the consumer to take the vehicle to another d”

Owner complaint to NHTSA, July 12, 2005 · Engine and engine cooling

Compare Peterbilt 330 model years

Recall and complaint counts for every Peterbilt 330 model year in NHTSA's database.

Model yearRecallsComplaints
1996 Peterbilt 33010
1997 Peterbilt 33010
1998 Peterbilt 33010
1999 Peterbilt 33061
2000 Peterbilt 33060
2001 Peterbilt 33040
2002 Peterbilt 33020
2003 Peterbilt 33030
2004 Peterbilt 33021
2007 Peterbilt 33010
2008 Peterbilt 33030
2009 Peterbilt 33040
2010 Peterbilt 33020
2011 Peterbilt 33030
2012 Peterbilt 33030
2013 Peterbilt 33020
2014 Peterbilt 33030
2015 Peterbilt 33020
2016 Peterbilt 33020
2017 Peterbilt 33030
2018 Peterbilt 33020
2019 Peterbilt 33020
2020 Peterbilt 33011
2022 Peterbilt 33010
2023 Peterbilt 33010

Checking a specific 2004 Peterbilt 330

How do I know if my 2004 Peterbilt 330 has an open recall?

Enter your 17-character VIN above. The VIN is on the driver's side dashboard (visible through the windshield), the driver's door jamb sticker, and your registration or insurance card. The check runs against NHTSA's live database and tells you which campaigns list your vehicle. 2 campaigns currently list the 2004 Peterbilt 330; your car may already have been repaired under some of them.

Is the recall repair free?

Yes. Under federal law, manufacturers must fix safety recalls at no charge for vehicles up to 15 years old from the date of sale to the first owner. Contact any authorised Peterbilt dealer with your VIN and the NHTSA campaign number (for example 03V306000).

What is the difference between a recall and a complaint?

A recall is a safety campaign filed by the manufacturer or ordered by NHTSA, with a defined defect and remedy. A complaint is a report an owner sent to NHTSA; it is not verified, but patterns of complaints are what trigger NHTSA investigations and, eventually, recalls.

Other Peterbilt models

Source: NHTSA recall and complaint databases and EPA fuel economy data, October 2026. Complaint counts are owner reports to NHTSA, not verified defects. Recall counts are safety campaigns that list this model year; whether a particular car was already repaired depends on its VIN. How this data is compiled.