Fleet Recall Workflow Guide

When to use this

• → Quarterly compliance check on your active fleet
• → Onboarding a recently acquired fleet or merged carrier's vehicles
• → Investigating a customer concern after a media-reported recall
• → Preparing for a CSA audit where open recalls would be flagged

1. Check a single VIN

For a one-off check, paste any 17-character VIN below. You'll be redirected to /vin/{vin}/, which decodes the make/model/year and shows every open NHTSA recall campaign matched to that vehicle, plus consumer safety complaints and roadside inspection history. This is the right flow when you've just acquired a vehicle, are investigating a customer-reported issue, or want to confirm a specific VIN before scheduling a dealer visit.

2. Batch check across a fleet

For full-fleet sweeps, NHTSA publishes a free public recalls API. There's no API key, no rate limit advertised for normal use, and no cost. The standard pattern is to query by make, model, and model-year for each unique combination in your fleet, then match the returned campaigns against your VIN list locally. The endpoint lives at api.nhtsa.gov/recalls/recallsByVehicle and accepts make, model, and modelYear query parameters.

Example request (Freightliner Cascadia, 2022):

curl 'https://api.nhtsa.gov/recalls/recallsByVehicle?make=freightliner&model=cascadia&modelYear=2022'

Example response (truncated):

{
  "Count": 4,
  "Message": "Results returned successfully",
  "results": [
    {
      "Manufacturer": "Daimler Trucks North America LLC",
      "NHTSACampaignNumber": "22V123000",
      "parkIt": false,
      "parkOutSide": false,
      "ReportReceivedDate": "21/02/2022",
      "Component": "STEERING",
      "Summary": "Daimler Trucks North America LLC (DTNA) is recalling certain ...",
      "Consequence": "A loss of steering control may increase the risk of a crash.",
      "Remedy": "Dealers will inspect and replace the steering shaft, free of charge.",
      "Notes": "Owners may contact DTNA customer service at 1-800-547-0712.",
      "ModelYear": "2022",
      "Make": "FREIGHTLINER",
      "Model": "CASCADIA"
    }
  ]
}

Loop through every (make, model, year) tuple represented in your fleet, collect the campaign numbers, and join back against your VIN list. For a fleet of any size this takes seconds. NHTSA also offers a per-VIN endpoint at /recalls/recallsByVin, but coverage for commercial truck VINs is incomplete — the make/model/year query is more reliable for heavy-duty vehicles.

3. Track remediation

Once a recall hits a vehicle in your fleet, federal law (49 USC 30120) requires the manufacturer to repair the defect free of charge at any authorized franchise dealer. There is no out-of-pocket cost to the owner, regardless of whether you're the original purchaser, and no time limit for vehicles less than 15 years old (10 years for tires). The cost to your operation is the downtime to schedule and complete the repair.

Track remediation in your fleet management system, not on the NHTSA side. NHTSA's per-VIN remedy-status flag often lags 30–60 days behind the dealer's actual repair completion. For each affected unit, record:

• The NHTSA campaign number (e.g., 22V123000)
• The dealer where the repair was performed and the repair-order number
• The date the remedy was completed
• Mileage at remedy and any post-repair test notes

This record is what you'll produce during a CSA audit, an insurance review, or post-incident litigation if the cited defect is later involved in a crash. Do not rely on NHTSA's status flag alone — in a dispute, your internal repair-order log carries more weight.

4. Subscribe to alerts

Periodic checks catch existing campaigns; alerts catch new ones. Two complementary feeds:

• NHTSA email alerts. Subscribe to recall notices for the manufacturers in your fleet at nhtsa.gov/recalls. Notifications arrive within hours of a campaign being posted.
• TruckCodex recall feed. Browse all active campaigns affecting commercial vehicles at /recalls/. Filter by manufacturer, component, or campaign year to see what's relevant to your fleet composition.

Combining email alerts with a monthly batch sweep against the API closes the gap: alerts catch brand-new campaigns the same day, the monthly sweep catches anything you missed and any newly acquired vehicles that need a first-time check.

Recommended fleet-recall workflow

1. Build a current VIN list. Pull every active power unit and trailer VIN from your fleet management system. Verify each VIN is 17 characters, alphanumeric, with no I, O, or Q. Group the list by make + model + model-year.
2. Spot-check a single VIN. For a one-off check, paste any VIN into the lookup form on this page or visit /vin/{vin}/ directly. The page shows decoded vehicle identity, every open NHTSA recall campaign matched to the make/model/year, and consumer safety complaints.
3. Batch via the NHTSA API. For a full sweep, call api.nhtsa.gov/recalls/recallsByVehicle once per (make, model, year) tuple. The endpoint is free and unauthenticated. Collect campaign numbers and join back against your VIN list locally.
4. Cross-check borderline VINs. For VINs flagged by the make/model/year query, confirm whether the specific VIN falls inside the affected serial-number range. NHTSA's per-VIN lookup at vinrcl.safercar.gov is the authoritative confirmation.
5. Schedule remedy with the manufacturer's dealer. Federal law requires recalls to be repaired free of charge at any authorized franchise dealer for the brand. Call the dealer with the campaign number; book during planned downtime when possible.
6. Track remediation in your FMS. Record campaign number, dealer, repair-order number, completion date, and mileage at remedy against the VIN in your fleet management system. NHTSA's status flag often lags 30-60 days behind actual completion — your internal log is the authoritative record.
7. Subscribe to NHTSA email alerts. Sign up for recall notifications at nhtsa.gov/recalls for every manufacturer in your fleet. Alerts catch new campaigns the day they post.
8. Re-run the batch sweep monthly. Schedule a recurring monthly batch check against the API. Always re-check immediately when adding a new VIN to the fleet, and after any acquisition or merger.

Frequently Asked Questions

How do I check a fleet for open NHTSA recalls?

For a single VIN, use the lookup form on this page or visit /vin/{vin}/. For a full fleet, query NHTSA's free public API at api.nhtsa.gov/recalls/recallsByVehicle by make, model, and model-year, then match the returned campaigns against your VIN list locally.

Are recalls free to fix?

Yes. By federal law (49 USC 30120), manufacturers must repair recalled vehicles at no cost to the owner at any authorized franchise dealer, regardless of vehicle age or whether you are the original owner. The exception is recalls older than 15 years (10 for tires) which manufacturers may decline to remedy.

Why does my VIN show no recalls when I know there's a recall on my model?

NHTSA campaign data is keyed by VIN serial-number range — your specific VIN may fall outside the affected range even if the make/model/year is generally affected. Cross-check the official NHTSA per-VIN lookup at vinrcl.safercar.gov for confirmation.

How fresh is the NHTSA recall data?

NHTSA's API and TruckCodex's /recalls/ feed refresh continuously. New campaigns typically surface within 24-48 hours of their official posting. Remedy-status updates from dealers flow through within the same window.

Does NHTSA's recallsByVin endpoint work for commercial trucks?

Coverage for commercial truck VINs is incomplete — many heavy-duty makes and models don't fully resolve through the per-VIN endpoint. The recallsByVehicle endpoint (queried by make + model + year) is more reliable for fleet sweeps.

How often should I run a fleet-wide recall check?

At least monthly for the full fleet, plus immediately whenever you add a vehicle. Subscribing to NHTSA email alerts for the manufacturers in your fleet catches new campaigns the day they post, between scheduled sweeps.

Does this cover Canadian and Mexican vehicles?

The NHTSA database covers vehicles sold or registered in the US. Canadian recalls are tracked separately by Transport Canada (transportcanada.gc.ca). Vehicles imported and registered in the US should appear in NHTSA data.

What's the difference between a recall and a service bulletin?

A recall is a mandatory remedy for a safety defect or non-compliance, supervised by NHTSA, with free repair required by federal law. A Technical Service Bulletin (TSB) is an advisory from the manufacturer for known issues that don't rise to the recall standard — repair costs are not necessarily covered.