Browse Car Models

Explore all 3,559 car models with NHTSA safety data

Model Complaints
220 35
220 1
220I 1
228I 92
230 39
230I 27
240 186
240 116
240SX 238
242 1
244 9
244 DL 1
245 15
2500 7,213
2500HD 12
260E 2
280 124
280 SL 1
280Z 7
3-SERIES 28
3.0L 8
300 6,450
300 288
300 AWD 126
300 LWB 3
300 SERIES 79
300 SERIES 1
3000 4
3000 8
3000GT 535
3000GT SPYDER 3
300C 1,758
300D 1
300E 57
300M 1,130
300S 5
300SD 14
300SE 9
300ZX 386
308 1
30HD 4
318 169
318I 113
318IA 5
318IC 17
318IS 37
318TI 31
320 332
320 29
320 5

Methodology

Every model in this browser comes from the same three federal sources used on every detail page: the NHTSA Office of Defects Investigation (ODI) complaints database (consumer-filed, unverified safety reports), the NHTSA recall campaign API (official recall actions), and NHTSA New Car Assessment Program (NCAP) crash-test ratings. Complaint counts reflect raw owner filings and are heavily influenced by fleet size — a high-volume bestseller will accumulate more complaints than a low-volume niche model even at identical defect rates per vehicle. Recall counts reflect what manufacturers were compelled to remedy, not current risk. See the full methodology page for processing steps, data currency, and documented limitations.

More PlainCars Browsers

PlainCars covers more than just model directories. Browse our other entry points:

Reading complaint counts in context

Complaint volume on its own can be misleading. A best-selling sedan with hundreds of thousands of vehicles on the road will accumulate more raw consumer reports than a low-volume luxury or specialty model, even when the per-vehicle defect rate is similar or lower. When comparing models in this directory, treat complaint count as a starting signal — not a verdict. Look for clusters of complaints around a specific component (transmission, airbag, electrical), check whether NHTSA opened a formal Office of Defects Investigation review, and cross-reference the recall ledger to see if any verified manufacturer action was taken. Models that combine high complaint volume with multiple repeated recalls on the same subsystem carry stronger evidence of an underlying engineering issue than models with isolated reports.

How recall counts are interpreted

Recall numbers reflect the count of distinct manufacturer recall campaigns linked to a given model in the NHTSA Recalls API, deduplicated across years and trims. A high recall count does not always equal high current risk: many recalls are for fully remediable issues (software updates, supplier-side fixes, label changes) and may already have been completed by the time you read this page. Conversely, low recall counts on newer model years can simply reflect the natural lag between vehicle release and the surfacing of long-tail defects. We list recall counts here so you can spot historical patterns; for a specific VIN, always check NHTSA.gov/recalls directly with that VIN entered.

Why we publish this directory

The federal data behind every model card in this browser is fully public and free, but it lives across three separate NHTSA systems — the complaints database, the recall campaign API, and the New Car Assessment Program — each with its own search interface and export format. PlainCars stitches the three together at the model level so that a curious buyer, a journalist, or a fleet manager can see complaints, recalls, and crash ratings on one page without learning three government UIs. We do not editorialize on whether a model is "good" or "bad" — we surface the underlying counts and link straight to NHTSA for the source filings.