Pierce CUSTOM CHASSIS recalls by model year
Explore the records behind recurring owner reports.
Key facts
0 owner complaints analyzed
4 distinct recall campaigns
Not available median reported failure mileage
Scope: 1996 to 2006 model years. Data updated: . 0 complaints include usable failure mileage. View data status.
Recalls by model year
All campaigns in the snapshot affecting each model year, including recalls announced years later.
Recall campaigns
Shared campaigns appear once in each affected model year.
| Category | Count |
|---|---|
| 1996 | 1 |
| 1997 | 1 |
| 1998 | 1 |
| 1999 | 1 |
| 2000 | 1 |
| 2001 | 2 |
| 2002 | 4 |
| 2003 | 3 |
| 2004 | 2 |
| 2005 | 1 |
| 2006 | 1 |
1996: 1; 1997: 1; 1998: 1; 1999: 1; 2000: 1; 2001: 2; 2002: 4; 2003: 3; 2004: 2; 2005: 1; 2006: 1
Year-by-year records
Recall history
4 distinct campaigns affect this selection. Announcement dates below are different from vehicle model years. A campaign may cover multiple years.
03V380000 · Steering:Linkages:Tie Rod Assembly
Reported: 2003-10-08 (October 8, 2003) · Model years: 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003
ON CERTAIN FIRE TRUCKS WITH TANDEM STEER AXLES. THE TRW TIE-ROD ON THE REAR-MOST AXLE OF A TANDEM AXLE IS RESTRAINED FROM ROTATIONAL MOVEMENT BY A PAIR OF ANTI-ROTATION SEALS LOCATED AT THE BALL SOCKET JOINTS. THESE ANTI-ROTATION SEALS WILL COMPRESS OVER TIME. IF THE ANTI-ROTATION SEAL ALLOWS TOO MUCH MOTION, THE SEALS CAN DETERIORATE, ALLOWING CONTACT BETWEEN THE BALL SOCKET AND THE BALL SHAFT. THIS METAL-TO-METAL CONTACT WILL TRANSMIT FORCES INTO THE TIE-ROD TUBE, CAUSING FATIGUE FAILURE INITIATING AT THE ROOT OF THE FEMALE TREADS.
Consequence: FAILURE OF THE TIE-ROD WILL ALLOW ONE OF THE WHEELS TO SWING TO THE LIMIT OF ITS STEERING STOP, POTENTIALLY CAUSING A LOSS OF VEHICLE CONTROL, INCREASING THE RISK OF A CRASH.
Remedy: DEALERS WILL REPLACE THE TIE ROD. NOTIFICATION TO OWNERS BEGAN NOVEMBER 7, 2003. OWNERS SHOULD CONTACT PIERCE AT 1-888-974-3723.
NHTSA campaign record ↗07V470000 · Suspension:Front:Control Arm
Reported: 2007-10-05 (October 5, 2007) · Model years: 2001, 2002, 2003, 2004, 2005, 2006
ON CERTAIN FIRE TRUCKS EQUIPPED WITH AN INDEPENDENT FRONT SUSPENSION, A PITMAN ARM MIGHT FRACTURE UNDER SEVERE LOAD CAUSED BY THREE LOADING CONDITIONS. IN ALL CASES, THE FRONT AXLE MUST BE TURNED FULL LEFT OR RIGHT WHILE (1) SIMULTANEOUSLY BACKING UP AND BRAKING HARD, (2) DRIVING ONE WHEEL OVER OR AGAINST A CURB OR (3) STEERING THE FRONT AXLE FULL LEFT OR RIGHT WHEN THE VEHICLE IS STATIONARY WITH THE SERVICE BRAKE APPLIED. THESE ARE ALL LOW OR NO -SPEED EVENTS.
Consequence: SUCH A BREAK COULD LEAD TO THE SUSPENSION LOSING ONE OF ITS ANCHOR POINTS, THEREBY POTENTIALLY CAUSING LOSS OF VEHICLE CONTROL WITHOUT PRIOR WARNING WHICH COULD RESULT IN A CRASH.
Remedy: DEALERS WILL REPLACE THE ORIGINAL PITMAN ARMS WITH PITMAN ARMS MADE OF HIGHER STRENGTH MATERIAL. THE RECALL BEGAN ON OCTOBER 29, 2007. OWNERS MAY CONTACT PIERCE AT 920-832-3000.
NHTSA campaign record ↗02V294000 · Steering
Reported: 2002-11-06 (November 6, 2002) · Model years: 2002
ON CERTAIN CUSTOM CHASSIS EQUIPPED WITH THE ALL WHEEL STEER (AWS) 2002 SYSTEM, THE VEHICLE INTERFACE MOBILE PROGRAM HAS A PROBLEM THAT CAUSES ONE OF THE STEERABLE AXLES TO LOCK IN THE STEERED POSITION RATHER THAN RETURNING TO CENTER.
Consequence: IF THIS CONDITION OCCURS, THE DRIVER CAN LOSE STEERING CONTROL, POSSIBLY RESULTING IN A VEHICLE CRASH.
Remedy: PIERCE IS SENDING A FACTORY TECHNICIAN TO ALL VEHICLES AND WILL UPGRADE THE AWS SYSTEM TO ELIMINATE THIS DEFECT. OWNER NOTIFICATION BEGAN ON NOVEMBER 2, 2002. OWNERS WHO TAKE THEIR VEHICLES TO AN AUTHORIZED DEALER ON AN AGREED UPON SERVICE DATE AND DO NOT RECEIVE THE FREE REMEDY WITHIN A REASONABLE TIME SHOULD CONTACT PIERCE AT 920-832-3000.
NHTSA campaign record ↗04V567000 · Steering
Reported: 2004-12-09 (December 9, 2004) · Model years: 2002, 2003, 2004
ON CERTAIN FIRE TRUCKS EQUIPPED WITH THE ALL WHEEL STEER OPTION, THE POSITION OF THE FRONT AXLE IS SENSED BY AN OPTICAL ENCODER MOUNTED TO THE BOTTOM OF THE FRONT AXLE KINGPIN, WHICH IS PROTECTED FROM THE ELEMENTS BY AN OUTER CASE. THIS CASE SHARES A COMMON GREASE CAVITY WITH THE KINGPIN. OIL THAT LEACHES FROM THE GREASE CAN MIGRATE THROUGH THE ENCODER SEAL, CAUSING CONTAMINATION OF THE OPTICAL ENCODER DISC.
Consequence: OIL ON THE DISC CAN CAUSE THE ENCODER TO SEND INCORRECT WHEEL POSITION INFORMATION AND CAN CAUSE THE REAR WHEELS TO STEER UNEXPECTEDLY CAUSING THE VEHICLE TO CRASH WITHOUT PRIOR WARNING.
Remedy: DEALERS WILL REPLACE THE ENCODERS WITH NEW ENCODERS WITH MORE ROBUST SEALS. THE CONTROL SOFTWARE WILL BE UPDATED TO PRODUCE AN ERROR CODE AND DISABLE THE REAR STEERING FUNCTION IF UNUSUAL ENCODER INPUTS ARE DETECTED. THE RECALL BEGAN JANUARY 25, 2005. OWNERS SHOULD CONTACT PIERCE AT 1-888-974-3723.
NHTSA campaign record ↗Vehicle analysis explorer
Inspect model-year patterns, reported mileage, monthly activity and the evidence behind each signal.
Data completeness
0 unique complaints in this selection. Analysis snapshot: 2026-10-01.
Missing, zero and invalid mileage is excluded. Dates after the snapshot are excluded. Examples are limited selections, not a representative sample.
Problems by model year
Model-wide comparison of the eight most reported components across the model. Cells show counts and shares within each model year. Open a cell for source examples.
| Component | 1996 | 1997 | 1998 | 1999 | 2000 | 2001 | 2002 | 2003 | 2004 | 2005 | 2006 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| No usable records for this analysis. | |||||||||||
Darker cells indicate a larger share of submitted complaints. Components overlap. This measures complaint composition, not failure probability.
Failure mileage by component
Median and middle 50% of usable owner-reported mileages. Ranges require at least five records.
| Component | Mileage range (25th–75th percentile) | Median | Usable records | Examples |
|---|---|---|---|---|
| No usable records for this analysis. | ||||
Complaint and recall timeline
Explore monthly filing activity alongside recall announcements. Up to ten years of monthly history is available.
Solid line: filed complaints. Dashed amber lines: recall announcement dates for this vehicle selection; markers include all recall components. The latest month is partial. Temporal proximity does not establish causation.
Monthly counts, recall campaigns and complaint examples
| Month | Complaints | Campaigns announced | Examples |
|---|---|---|---|
| 2024-11 | 0 | None | No examples available for this selection. |
| 2024-12 | 0 | None | No examples available for this selection. |
| 2025-01 | 0 | None | No examples available for this selection. |
| 2025-02 | 0 | None | No examples available for this selection. |
| 2025-03 | 0 | None | No examples available for this selection. |
| 2025-04 | 0 | None | No examples available for this selection. |
| 2025-05 | 0 | None | No examples available for this selection. |
| 2025-06 | 0 | None | No examples available for this selection. |
| 2025-07 | 0 | None | No examples available for this selection. |
| 2025-08 | 0 | None | No examples available for this selection. |
| 2025-09 | 0 | None | No examples available for this selection. |
| 2025-10 | 0 | None | No examples available for this selection. |
| 2025-11 | 0 | None | No examples available for this selection. |
| 2025-12 | 0 | None | No examples available for this selection. |
| 2026-01 | 0 | None | No examples available for this selection. |
| 2026-02 | 0 | None | No examples available for this selection. |
| 2026-03 | 0 | None | No examples available for this selection. |
| 2026-04 | 0 | None | No examples available for this selection. |
| 2026-05 | 0 | None | No examples available for this selection. |
| 2026-06 | 0 | None | No examples available for this selection. |
| 2026-07 | 0 | None | No examples available for this selection. |
| 2026-08 | 0 | None | No examples available for this selection. |
| 2026-09 | 0 | None | No examples available for this selection. |
| 2026-10 (partial) | 0 | None | No examples available for this selection. |
Emerging complaint spikes
Complete months in the latest six months with at least 10 complaints, at least twice the preceding 12-month average, and at least three square-root deviations above that average.
This is a descriptive screening rule, not a statistical defect finding. Publicity and reporting changes can increase submissions.
No complete months meet the spike thresholds for this selection.
Equal-age model-year comparison
Model-wide cumulative reports during the first three or five calendar years, starting with the model year (age 0). Only fully elapsed windows are compared.
2005: 0 complaints · 2006: 0 complaints
| Model year | Through age 0 | Through age 1 | Through age 2 |
|---|---|---|---|
| 2005 | 0 | 0 | 0 |
| 2006 | 0 | 0 | 0 |
Date coverage across each selected cohort
| Year | Incident dates used | Filing date fallbacks | Excluded dates |
|---|---|---|---|
| 2005 | 0 | 0 | 0 |
| 2006 | 0 | 0 | 0 |
Incident date is preferred when valid and no later than filing; otherwise filing date is used. Model year approximates age. Equal observation time does not adjust for sales, distance driven or reporting delays. One complaint linked to multiple model years can appear in each cohort.
Components reported together
Each cell counts unique complaints naming both components. Open a nonzero cell for examples.
| Component |
|---|
| No usable records for this analysis. |
Co-reporting does not establish that one component caused another concern.
Recurring narrative patterns
Specific keyword mentions beyond broad component labels. Matching includes negations and comparisons and does not confirm a diagnosis.
0 patterns with matching reports.
No narratives match the published patterns.