Skip to content
Palanor is in early release, with our founding customers.Become a founding customer →
PalanorPalanor
← All signals

regulatory

NHTSA Vehicle Safety Recalls (Monthly)

Latest

67campaigns

Methodology

## What this measures

The number of vehicle safety recall campaigns (Part 573 defect or noncompliance reports for vehicles) the National Highway Traffic Safety Administration received in each month.

## Why it matters

Recalls are a direct cost to automakers (repairs, parts, warranty reserves) and a read on quality as vehicles take on more electronics, software and new powertrains.

## How to read it

Higher means more recall campaigns. Monthly counts swing; compare a quarter or year with the same period before.

## What it does not say

A campaign is dated by when NHTSA received the manufacturer’s defect report, not when owners were told or the repair was ready. Units are those the manufacturer estimates may be affected, not vehicles found defective. One defect can produce several campaigns (one per manufacturer or report).

## How it's built

Campaigns of report type V (vehicle) counted by the month NHTSA received the report. History from January 2010.

## Source

National Highway Traffic Safety Administration, recalls data (static.nhtsa.gov/odi/ffdd/rcl/FLAT_RCL_POST_2010.zip, layout RCL.txt), refreshed daily by NHTSA; U.S. government work. Refreshed daily by /api/cron/risk-events-sync?source=nhtsa.

Read this signal inside the lattice.

Palanor weighs every signal against the world your organization is watching. Methodology is public; integration is the platform.

See it in Palanor →

Cookies

We only use essential cookies to keep you signed in and remember your theme. No analytics, no tracking, no ads. See the Privacy Policy for the full read.