RecallMyCar

2000 Peterbilt 330 Recalls, Complaints & Specs

6 safety recalls list the 2000 Peterbilt 330. Check your own VIN below.

6
safety recalls
0
owner complaints to NHTSA

6 safety recalls for the 2000 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. Tie rod assembly (steering)

    NHTSA 02V037003 Reported 4,513 vehicles potentially affected PACCAR, INCORPORATED

    Heavy duty trucks equipped with trw tie rod ends on certain arvinmeritor and dana axles. Peterbilt will recall 1,434 vehicles equipped with arvinmeritor axles manufactured from december 11, 1999, to may 14, 2000, and from july 22 to september 30, 2000. Kenworth will recall 859 vehicles equipped with arvinmeritor vehicles manufactured…

    Remedy: Dealers will remove and replace all affected tie rods and drag links with different designed ends. Owner notification began july 15, 2002. Owners who take their vehicles to an authorized dealer on an agreed upon…

  2. Tie rod assembly (steering)

    NHTSA 01V140006 Reported 2,294 vehicles potentially affected PACCAR, INCORPORATED

    Vehicle description: heavy duty trucks equipped with trw tie rod ends on certain meritor axles. The tie rod and drag link ball stud ends contain bearings that are below the specified case depth and/or hardness.

    Remedy: Dealers will remove and replace all affected tie rods and drag links with different designed ends. Owner notification began october 24, 2001. Owners who take their vehicles to an authorized dealer on an agreed upon…

  3. Latch (latches/locks/linkages)

    NHTSA 01V179000 Reported 52,500 vehicles potentially affected PACCAR, INCORPORATED

    Vehicle description: heavy duty trucks. A change in the internal linkage of certain cab doors has created a possible binding condition.

    Remedy: Dealers will modify the door linkage to correct the potential of binding. Owner notification began june 22, 2001. Owners who take their vehicles to an authorized dealer on an agreed upon service date and do not receive…

  4. Suspension

    NHTSA 01V167001 Reported 390 vehicles potentially affected PACCAR, INCORPORATED

    Vehicle description: heavy duty trucks equipped with chalmers 1000 series and 800 series suspension kits. These suspension kits may have insufficient penetration of the weld attaching the torque rod eye to the torque rod tube.

    Remedy: Dealers will replace all chalmers fixed torque rods on these vehicles. Owner notification began july 27, 2001. Owners who take their vehicles to an authorized dealer on an agreed upon service date and do not receive…

  5. Anchorage (seat belts)

    NHTSA 01V054000 Reported 6,623 vehicles potentially affected PACCAR, INCORPORATED

    Vehicle description: class 7 and class 8 vehicles. These vehicles do not comply with the requirements of FMVSS no. 207, "seating system," and no. 210, "seat belt assembly anchorages." some fasteners used to attach the shoulder belt anchor bracket to the cab structure were omitted during production.

    Remedy: Dealers will add the necessary fasteners. Owner notification began march 19, 2001. Owners who take their vehicles to an authorized dealer on an agreed upon service date and do not receive the free remedy within a…

  6. Automatic transmission (power train)

    NHTSA 00V131001 Reported 490 vehicles potentially affected PACCAR, INCORPORATED

    Vehicle description: heavy duty trucks equipped with eaton autoshift gen ii transmission assemblies. Due to a software problem in the transmission assemblies, the transmission will select the wrong gear.

    Remedy: Dealers will replace the autoshift transmissions. Eaton performed the campaign for the kenworth portion. However peterbilt will be conducting their own campaign.

No owner complaints on file

NHTSA has no owner complaints on file for the 2000 Peterbilt 330. For context, the average model year in NHTSA's database has dozens; a zero can mean a reliable vehicle, a rare one, or both.

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 2000 Peterbilt 330

How do I know if my 2000 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. 6 campaigns currently list the 2000 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 00V131001).

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.