Skip to content
FonteumPublic-records evidence

NHTSA RECALLS · MODEL

DODGE redundant RAM 3500 recall records

Public NHTSA recall rows listed for DODGE redundant RAM 3500, grouped by campaign, component, and model year.

Are DODGE redundant RAM 3500 recalls listed?

Loaded NHTSA rows list 2 distinct recall campaigns for DODGE redundant RAM 3500, across 2make/model/year/component rows. A row match is a public-record listing, not a VIN-specific status. Use NHTSA's VIN tool for a specific vehicle check. Snapshot 2026-06-24.

Source-backed recall facts

Components listed in recall rows

NHTSA recall rows by component
ComponentRowsCampaignsSource
AIR BAGS:FRONTAL:DRIVER SIDE:INFLATOR MODULE11Source:NHTSA Safety RecallsSnapshot 2026-06-24
AIR BAGS:FRONTAL:PASSENGER SIDE:INFLATOR MODULE11Source:NHTSA Safety RecallsSnapshot 2026-06-24

Model years listed

NHTSA recall rows by model year
Model yearRowsCampaignsSource
201022Source:NHTSA Safety RecallsSnapshot 2026-06-24

DODGE redundant RAM 3500 recent NHTSA rows

DODGE redundant RAM 3500 recent NHTSA rows
CampaignVehicleComponentReport dateFlagsListed issueSource
16V9470002010 DODGE redundant RAM 3500AIR BAGS:FRONTAL:DRIVER SIDE:INFLATOR MODULEDec 22, 2016None listedChrysler (FCA US LLC) is recalling certain model year 2009 Dodge Durango and Chrysler Aspen vehicles manufactured January 17, 2007, to December 18, 2008, and 2010 RAM 3500 cab cha...Source:NHTSA Safety RecallsSnapshot 2026-07-18
16V3520002010 DODGE redundant RAM 3500AIR BAGS:FRONTAL:PASSENGER SIDE:INFLATOR MODULEMay 24, 2016None listedChrysler (FCA US LLC) expanded the affected population to include 73,712 2005-2009 RAM 2500 trucks produced at the St. Louis North Assembly Plant. With this change, Chrysler is re...Source:NHTSA Safety RecallsSnapshot 2026-07-18

Limits and source notes

  • NHTSA's flat file is row-grained by make, model, model year, and component. Fonteum dedupes distinct campaign counts by campaign number.
  • Potentially affected totals are read once per campaign in aggregate views to avoid counting the same campaign across repeated DODGE redundant RAM 3500 rows.
  • A make/model page is not a VIN-specific result. Use NHTSA's recall site for the vehicle-level check.

Recall questions

What does a DODGE redundant RAM 3500 recall row mean?

A NHTSA row is a public-record slice of a recall campaign, usually tied to a make, model, model year, and component. It is not an owner-specific finding. Fonteum groups rows into distinct campaigns when reporting campaign counts and affected-unit aggregates.

Why can row counts and campaign counts differ?

NHTSA's flat file can repeat the same campaign across multiple models, years, or component labels. Row counts show the published slices. Campaign counts dedupe by campaign number so the same administrative campaign is not counted repeatedly in the headline total.

How do I check a specific vehicle?

Use NHTSA's official recall site for a VIN-specific check. Fonteum pages show public make/model records and source dates, which are useful for research, but a VIN check is the right source for a specific vehicle's current recall status.

What’s on file, by the numbers

Platform snapshot · 2026-08-29

13.4Mproviders & companiesProviders, organizations, owners, and facilities on file
26.2Msource-linked factsSource-linked field facts in the dated platform snapshot
90sources with dataDistinct snapshot source IDs with at least one positive record count
19fresh sourcesDistinct source IDs whose latest positive-data snapshot falls within the preceding 45 days
111sources integratedActive registry rows; integration does not establish a load
13state Medicaid jurisdictionsDistinct states represented in the state-exclusions serving table

Integrated, with-data, and fresh-observation counts are separate. No platform-wide source-completeness count is published. Completeness is source-specific and must be evaluated against the named source's expected scope. State coverage is a separate jurisdiction measure.

Source authority is record-specific

Use the issuer named on the record.

Fonteum spans federal, state, and global public publishers. A source page or returned record identifies its issuer and dataset where that metadata is available. A platform registry count does not assign every page to one authority or establish loaded, fresh, or complete coverage.

Browse source records and their stated limitations →

Reproducible by design

Inspect the evidence each published figure actually supplies.

Source and date

Research pages expose the named public file and observation date where those fields are available. Source-file SHA-256 coverage is separate; facts do not currently link deterministically to signatures.

Available derivation

Studies with a retained release and committed derivation link the SQL or method used. Other studies state the evidence and reproduction limits they actually have.

Daily observations

Dated table row-count observations can detect local drift. They do not imply that an upstream publisher released or Fonteum ingested new data that day.

Named medical review

Reviewed by Jennifer Montecillo, MD, medical reviewer. Non-practicing medical reviewer.

Read the full provenance and attestation methodology →

Request access