01
What an owner complaint represents
The National Highway Traffic Safety Administration accepts vehicle-safety complaints from consumers. A complaint record can include the vehicle identity, components selected by the reporter, an incident narrative, incident timing, mileage, and structured outcomes such as a crash, fire, injury, or death when those fields are provided.
A complaint is a report, not an automatic finding that a defect exists. NHTSA may use complaints alongside other information in safety-defect work, but the presence of a complaint alone does not verify its cause or establish that every vehicle in the population is affected.
02
Why raw totals need context
A larger complaint count does not automatically identify a less reliable vehicle. Different models have different production volumes, years on the road, usage patterns, owner populations, and levels of public attention. Reporting is voluntary, so not every event is reported and not every report has the same level of detail.
Model-year comparisons also involve exposure time. An older model year has generally had more opportunity to accumulate reports than a newer one. Is This A Good Car? therefore displays raw complaint counts as descriptive records and does not turn the difference between two years into a reliability ranking.
- Do not treat a complaint count as the number of confirmed failures.
- Do not treat the absence of complaints as proof that a vehicle is problem-free.
- Do not compare counts as rates unless the population denominators are trustworthy and comparable.
03
Read component patterns carefully
Component categories can help organize a large complaint set. Repeated mentions show what reporters selected or described within the retrieved records. They do not by themselves show the root cause, severity, repair cost, or percentage of vehicles affected.
A single complaint can identify more than one component, so component totals may overlap. Is This A Good Car? keeps this distinction visible and uses normalized categories to summarize records without adding unrelated systems together.
04
Mileage and outcome fields can be incomplete
Reported incident mileage can help describe when complaints occurred among records that include a usable value. Median or quartile mileage should be read together with coverage: if many records omit mileage, the available subset may not represent the full complaint set.
Crash, fire, injury, and death fields describe structured values reported in complaint records. They should not be assumed equivalent to one another, and Is This A Good Car? does not infer missing values. Narratives may contain useful context, but they are consumer-submitted accounts and should be read as such.
05
Why production normalization matters
A population denominator can provide context for raw complaint volume. Where a model year has a verified, correctly matched production figure, complaints can be expressed per a fixed number of vehicles produced. Even then, the result is a reporting rate based on records and production—not a mechanical failure rate or a prediction for an individual vehicle.
A denominator must match the same vehicle population and reporting scope. Is This A Good Car? leaves normalized metrics unavailable when official production data cannot be matched confidently. It does not estimate missing production simply to fill the field.
06
A practical reading sequence
Begin with source status and Data Confidence, then review the total retrieved records and data-completeness measures. Look at component patterns, mileage coverage, recent narratives, recalls, manufacturer communications, and investigations as separate evidence. Cross-source overlap can identify topics that appear in more than one official record type without proving prevalence or severity.
Use what you learn to form questions for the seller and an independent inspector. Always check a candidate vehicle's VIN for open recalls because year, make, and model research cannot determine the recall status of a specific car.