Research and editorial method

You should be able to see where our answer stops.

The migrated catalogue has 135 editorial files and 1,086 selected official recall files. Every file links back to its named source, while live NHTSA data remains separate.

The source outranks our summary.

The document must name the exact vehicle, and its test procedure must fit the symptom.

Manufacturer records

Bulletins and warranty programs define the official scope. Recall documents carry a separate safety obligation.

Public safety data

NHTSA recalls provide official context. Owner complaints show what was reported, not how often a vehicle fails.

Professional repair context

Repair context helps us explain the test and mark work that belongs with a trained technician.

Community outcomes

Owner outcomes can show whether a repair held. They never outrank a recall instruction.

Six checks behind one problem file

Editorial files are written around manufacturer records. Imported recall files preserve the official campaign number, affected years, defect, consequence, remedy and VIN boundary from NHTSA. Neither layer is presented as a failure-rate study.

  1. Find the record

    We start with a manufacturer document or public safety record and keep its reference beside the explanation.

  2. Mark the limits

    Model years are copied as stated. Build dates and VIN rules stay visible instead of being widened to a whole badge.

  3. Translate the mechanism

    Technical language is explained around what the driver may notice, while uncertainty stays where the source left it.

  4. Join the vocabulary

    Everyday phrases point to one problem file. We do not publish a fresh page for each slightly different search phrase.

  5. Separate the actions

    An official remedy stays distinct from professional diagnosis. Low-risk observations get their own label.

  6. Show the source date

    Editorial files state when they were checked. Imported campaign files identify the NHTSA snapshot. The live federal lookup is available separately.

Several phrases can describe the same fault.

“Clunk over bumps” may be the phrase an owner remembers. The bulletin may use component language instead. We show both when they describe the same condition.

Ten complaints do not mean a ten-percent risk.

A public complaint total usually arrives without a dependable count of comparable vehicles still in service. It can reveal wording worth investigating, but not probability.

  • Catalogue: 1,221 source-backed files.
  • Editorial layer: 135 files prepared in the source.
  • Official recall layer: 1,086 selected campaign files.
  • Vehicle-year coverage: 1,875 pages with a static file.
  • Page order reflects safety relevance and source grouping, not reliability.

Source dates and migration scope

The FixCatalogue snapshot was generated on August 3, 2026. Migration preserves its problem text, symptoms, vehicle limits, diagnostic codes, manufacturer position, repair paths, cautions and source references. The original review dates remain on each record. Publication on AutoWarranty does not mean a new recall or document check.

Live owner feedback is outside this snapshot. The separately dated warranty cost and NHTSA count datasets remain distinct from the problem files.

Look up current NHTSA recalls and complaints

Open the same records we used.

AutoWarranty.autos is independent and is not affiliated with NHTSA or any vehicle manufacturer.