Wells Cargo TRAILER recalls by model year
Explore the records behind recurring owner reports.
Key facts
2 owner complaints analyzed
1 distinct recall campaigns
7,500 mi median reported failure mileage
Scope: 2004 to 2004 model years. Data updated: . 1 complaints include usable failure mileage. View data status.
This selection has limited data. It remains available for lookup but is excluded from search indexing.
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 |
|---|---|
| 2004 | 1 |
2004: 1
Year-by-year records
| Model year | Complaints | Recalls | Change in recalls |
|---|---|---|---|
| 2004 | 2 | 1 | Not available |
Recall history
1 distinct campaigns affect this selection. Announcement dates below are different from vehicle model years. A campaign may cover multiple years.
08V211000 · Equipment:Recreational Vehicle/Trailer
Reported: 2008-05-09 (May 9, 2008) · Model years: 2004
WELLS CARGO IS RECALLING 1 MY 2004 BUMPER PULL UTILITY TRAILER EQUIPPED WITH A TWO-DOOR REFRIGERATOR MANUFACTURED BY THE DOMETIC CORPORATION. THE REFRIGERATOR MAY HAVE A DEFECT IN THE BOILER TUBE. PRESSURIZED COOLANT SOLUTION COULD BE RELEASED INTO AN AREA WHERE AN IGNITION SOURCE (GAS FLAME) IS PRESENT.
Consequence: RELEASE OF COOLANT UNDER CERTAIN CONDITIONS COULD IGNITE AND RESULT IN A FIRE.
Remedy: WELLS CARGO WILL BE WORKING WITH DOMETIC IN ORDER TO REPAIR THESE REFRIGERATORS (PLEASE SEE 06E076). DOMETIC WILL REPAIR THESE REFRIGERATORS BY INSTALLING A SECONDARY BURN HOUSING, A THERMAL FUSE, AND A MELT FUSE FREE OF CHARGE. DOMETIC HAS RETAINED STERICYCLE INC. TO MANAGE THIS CAMPAIGN. STERICYCLE WILL ASSIST THE OWNER IN LOCATING DEALERSHIPS OR SERVICE CENTERS AND WILL PROVIDE ASSISTANCE WITH SCHEDULING OF APPOINTMENTS. OWNERS MAY CONTACT DOMETIC/STERICYCLE AT 1-888-446-5157 OR WELLS CARGO AT 1-623-936-8150.
NHTSA campaign record ↗Vehicle analysis explorer
Inspect model-year patterns, reported mileage, monthly activity and the evidence behind each signal.
Data completeness
2 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 | 2004 |
|---|---|
| Structure | 2100.0%ODI 10192024TL*THE CONTACT OWNS A 2007 WELLS CARGO TRAILER. THE CONTACT STATED THAT THE LEFT FENDER DETACHED FROM THE TRAILER AND LANDED ON THE TIRE. AS A RESULT, THE TIRE WAS COMPLETELY DESTROYED. THE FAILURE OCCURRED ON MAY 9, 2007. THE CONSUMER NOTICED TREAD SEPARATION ON ONE OF THE TIRES. UPDATED 02/01/08. *LJ THE CONSUMER STATED THE TIRES DID NOT APPEAR TO BE ADEQUATE FOR HIGHWAY SPEEDS. HE ALSO NOTICED ANOTHER TIRE SUFFERING FROM TREAD SEPARATION, BUT HAS NOT SEPARATED TOTALLY. |
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 |
|---|---|---|---|---|
| Structure | Too few reports for a range | 7,500 mi | 1 (sparse) | ODI 10247960 · 7,500 miTL*THE CONTACT OWNS A 2005 (NA) WELLS CARGO SW121V (NA). WHILE DRIVING 65 MPH, ONE OF THE TIRES FLATTENED ON THE TRAILER. THE CONTACT ATTEMPTED TO PULL OVER AND THE TRAILER DROPPED, WHICH CAUSED THE FENDER TO DETACH. THE TIRE WAS SHREDDED. HE CHANGED THE TIRE AND MANAGED TO LOCATE THE FENDER ON THE HIGHWAY. THE VIN WAS UNKNOWN. THE FAILURE AND CURRENT MILEAGES WERE APPROXIMATELY 7,500. |
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.
2004: 0 complaints
| Model year | Through age 0 | Through age 1 | Through age 2 |
|---|---|---|---|
| 2004 | 0 | 0 | 0 |
Date coverage across each selected cohort
| Year | Incident dates used | Filing date fallbacks | Excluded dates |
|---|---|---|---|
| 2004 | 2 | 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 | Structure |
|---|---|
| Structure | — |
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.