2000 Crane LDT2: 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: 2000 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.
02V231000 · Equipment:Other:Labels
Reported: 2002-09-05 (September 5, 2002)
ON CERTAIN TAG AND PUSHER AXLE ASSEMBLIES PURCHASED FROM RIDEWELL, THE AXLE ASSEMBLIES HAVE AN ACTUAL WEIGHT RATING LESS THAN THAT SPECIFIED ON THE LABEL AND THEREFORE FAIL TO COMPLY WITH THE REQUIREMENTS OF PART 567.5, "CERTIFICATION."
Consequence: LOADING THE TAG/PUSHER AXLE TO THE GAWR LABEL RATING OR LOADING THE VEHICLE TO THE GVWR LABEL RATING WILL CAUSE THE PUSHER/TAG AXLE TO BE OVERLOADED.
Remedy: CRANE WILL PROVIDE OWNERS WITH REPLACEMENT VEHICLE CERTIFICATION LABELS AND INSTALLATION INSTRUCTIONS. OWNER NOTIFICATION BEGAN OCTOBER 4, 2002. OWNERS WHO DO NOT RECEIVE THE FREE REMEDY WITHIN A REASONABLE TIME SHOULD CONTACT CRANE AT 1-918-832-7333.
NHTSA campaign record ↗03V167000 · Service Brakes, Air:Slack Adjusters:Automatic
Reported: 2003-05-01 (May 1, 2003)
ON CERTAIN TRAILERS EQUIPPED WITH A SPECIFIC COMBINATION OF REYCO SUSPENSION, EATON DRIVE AXLE, AND BENDIX SLACK ADJUSTERS, THE FAILURE OF A DRIVE AXLE SLACK ADJUSTER TO AUTOMATICALLY ADJUST AS REQUIRED TO COMPENSATE FOR BRAKE WEAR, WILL CAUSE AN OUT OF ADJUSTMENT CONDITION. IF THIS CONDITION OCCURS AND IS NOT IDENTIFIED AND CORRECTED THROUGH NORMAL INSPECTIONS AND MAINTENANCE, THE SLACK ADJUSTER WILL OVER-ROTATE AND MAY CONTACT THE SUSPENSION LOWER SPRING SADDLE.
Consequence: IF THIS OCCURS, BRAKING PERFORMANCE WILL BE INHIBITED, INCREASING THE RISK OF A CRASH WITHOUT WARNING.
Remedy: CRANE CARRIER WILL SUPPLY, AT NO CHARGE, GUNITE SLACK ADJUSTERS AND INSTALLATION INSTRUCTIONS TO REPLACE THE EXISTING BENDIX SLACK ADJUSTERS ON THE DRIVE AXLE. THE INSTALLING FACILITY WILL BE REIMBURSED BY CRANE FOR ONE (1) HOUR LABOR PER VEHICLE AT THEIR POSTED LABOR RATE. OWNER NOTIFICATION BEGAN ON JUNE 10, 2003. OWNERS SHOULD CONTACT CRANE AT 1-918-832-7305.
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-09-30.
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 | 2001 | 2002 | 2003 | 2004 | 2005 | 2006 | 2007 | 2008 | 2009 | 2010 | 2011 | 2012 | 2013 | 2014 | 2015 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 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-10 | 0 | None | No examples available for this selection. |
| 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 (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.
2014: 0 complaints · 2015: 0 complaints
| Model year | Through age 0 | Through age 1 | Through age 2 |
|---|---|---|---|
| 2014 | 0 | 0 | 0 |
| 2015 | 0 | 0 | 0 |
Date coverage across each selected cohort
| Year | Incident dates used | Filing date fallbacks | Excluded dates |
|---|---|---|---|
| 2014 | 0 | 0 | 0 |
| 2015 | 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.