No complaints are listed for the 2002 Freightliner Classic. NHTSA's API and bulk file list none in this build.
Data build 2026-10-07.
NHTSA lists this vehicle as FREIGHTLINER CLASSIC.
At a glance
Complaints
0
With crash
0
With fire
0
With injury (complaints)
0
Injuries
0
Deaths
0
Recalls
0
Do not drive recalls
0
Park outside recalls
0
Recall potential units (maximum)
Unavailable
Investigations
1
Open investigations
0
Manufacturer communications
0
Complaints per 100k sold unavailable. No sales source is available for this record.
Model-generated complaint tags: No complaints are listed for tagging.
Recalls
0 recalls.
Investigations
1 investigations; 0 open.
PE02088
Opened: 2002-11-22. Closed: 2003-05-01.
INTEGRAL HUB AND BEARING ASSEMBLY
FREIGHTLINER SUBMITTED A DEFECT REPORT ON MARCH 21, 2003 IN WHICH THEY IDENTIFIED APPROXIMATELY 5000 TRUCKS AS POSSIBLY BEINGAFFECTED BY THIS PROBLEM.ARVINMERITOR (FRONT AXLE MFR) SUBMITTED A DEFECT REPORT ONAPRIL 16, 2003, WHICH IDENTIFIES 6098 FREIGHTLINER TRUCKS ASBEING AFFECTED BY THIS RECALL AND 1191 AXLES SOLD TO FREIGHTLINER IN THE AFTERMARKET. ODI NOTES THAT THERE ARE TWOINTEGRAL HUB AND B
Complaints from the API and bulk file are merged and deduplicated by ODI number; the API alone misses records.
System and subsystem counts are numbers of distinct complaints, recalls or communications that name them. One record can name several systems, so shares across systems can add to more than 100 percent; a single share never exceeds 100 percent.
Recalls are counted once per campaign, investigations once per action and manufacturer communications once per NHTSA id, even when NHTSA lists several model names for the same record.
A sales denominator is a calendar-year proxy, not the population of vehicles still in use. Rates are copied from verified pipeline output.
NHTSA's complaints API and bulk file list no complaint for this make, model and model year in this data build.