2005 Thor California FURY: complaints, problems and recalls
Explore the records behind recurring owner reports.
Key facts
0 owner complaints analyzed
2 distinct recall campaigns
Not available median reported failure mileage
Scope: 2005 model year. Data updated: . 0 complaints include usable failure mileage. View data status.
Most common problems
No owner complaints are recorded for this selection. A complaint can name multiple components.
Component breakdown
Number of unique complaints naming each component. Top eight shown.
No usable records for this chart.
| Category | Count |
|---|
No records.
Reported problems by failure mileage
Complaint counts in mileage bands. These are not failure rates per vehicle or mile.
| Category | Count |
|---|---|
| Under 25,000 | 0 |
| 25,000 to 49,999 | 0 |
| 50,000 to 74,999 | 0 |
| 75,000 to 99,999 | 0 |
| 100,000 to 149,999 | 0 |
| 150,000 and above | 0 |
Under 25,000: 0; 25,000 to 49,999: 0; 50,000 to 74,999: 0; 75,000 to 99,999: 0; 100,000 to 149,999: 0; 150,000 and above: 0
No usable failure mileage is recorded. 0 complaints have missing, zero or invalid mileage.
Complaints over time
Year the complaint was filed, not the vehicle model year or incident year. The snapshot year is partial.
No usable records for this chart.
| Category | Count |
|---|
No records.
Pattern summary
There is not enough complaint evidence to summarize patterns.
Calculated from recorded counts. An AI narrative has not been published for this selection.
Examples from the source records
Examples provide context, not a representative sample or a verified diagnosis.
Recall history
2 distinct campaigns affect this selection. Announcement dates below are different from vehicle model years. A campaign may cover multiple years.
06V466000 · Structure
Reported: 2006-12-04 (December 4, 2006)
ON CERTAIN CARGO/TRAVEL TRAILERS, THERE IS A POSSIBILITY OF OVERLOADING IN THE REAR CARGO AREA. TOO MUCH WEIGHT INCORRECTLY POSITIONED IN THIS AREA CAN RESULT IN A LIGHT HITCH WEIGHT AND AFFECT STABILITY.
Consequence: DEPENDING ON THE SPECIFIC TOW VEHICLE AND ITS HITCH EQUIPMENT, A SUFFICIENTLY LIGHT HITCH WEIGHT CAN RESULT IN SWAY AT HIGHWAY SPEEDS. THIS COULD CAUSE A CRASH INVOLVING THE TRAILER AND TOW VEHICLE.
Remedy: OWNERS WILL BE ASKED TO INSPECT THEIR TRAILER, TOW VEHICLE, AND HITCH EQUIPMENT AND TO FOLLOW PROPER LOADING PROCEDURES AS EXPLAINED IN THE OWNER'S GUIDE SUPPLEMENT WHICH WILL BE PROVIDED WITH THE OWNER LETTER. THE RECALL BEGAN ON NOVEMBER 15, 2006. OWNERS SHOULD CONTACT THOR AT 1-888-697-8467. NOTE: THIS CAMPAIGN SUPERSEDES A PREVIOUS RECALL (PLEASE SEE 04V242).
NHTSA campaign record ↗06V468000 · Structure
Reported: 2006-12-04 (December 4, 2006)
ON CERTAIN CARGO/TRAVEL TRAILERS, OVERLOADING AND INCORRECTLY POSITIONING CARGO IN THE REAR CARGO AREA CAN RESULT IN ALIGHT HITCH WEIGHT AND AFFECT STABILITY.
Consequence: DEPENDING ON THE SPECIFIC TOW VEHICLE AND ITS HITCH EQUIPMENT, A SUFFICIENTLY LIGHT HITCH WEIGHT CAN RESULT IN SWAY AT HIGHWAY SPEEDS. TOO MUCH WEIGHT INCORRECTLY POSITIONED CAN ALSO RESULT IN SEVERE BENDING OF THE A-FRAME ASSEMBLY, FAILURE OF THE COUPLER ASSEMBLY, AND/OR FAILURE OF THE SAFETY CHAINS. THIS CAN CAUSE A CRASH INVOLVING THE TRAILER AND TOW VEHICLE.
Remedy: DEALERS WILL INSPECT THE TRAILER, TOW VEHICLE AND HITCH EQUIPMENT; INSTALL NEW CARGO LOAD LIMIT LABELS AND PLACARDS IN THE CARGO AREA; FURNISH LOADING LIMIT INFORMATION; REPLACE THE COUPLER AND SAFETY CHAINS; AND REINFORCE THE A-FRAME. THE RECALL BEGAN ON NOVEMBER 15, 2006. OWNERS SHOULD CONTACT THOR AT 1-888-697-8467. NOTE: THIS CAMPAIGN SUPERSEDES A PREVIOUS RECALL (PLEASE SEE 04V243).
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 | 2005 |
|---|---|
| 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
| Model year | Through age 0 | Through age 1 | Through age 2 |
|---|---|---|---|
| 2005 | 0 | 0 | 0 |
Date coverage across each selected cohort
| Year | Incident dates used | Filing date fallbacks | Excluded dates |
|---|---|---|---|
| 2005 | 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.