1995 MERCURY VILLAGER — Complaint #389688
Open-data reference.
NHTSA Complaint about EQUIPMENT:RECREATIONAL VEHICLE/TRAILER:LPG SYSTEMS:TANK ASSEMBLY filed January 17, 2003
NHTSA complaint #389688 (ODI reference 10004158) concerns a 1995 MERCURY VILLAGER and was filed on January 17, 2003. The report was geocoded to Massachusetts based on the filer's self-reported location. The affected component is categorized as equipment:recreational vehicle/trailer:lpg systems:tank assembly, one of NHTSA's standardized taxonomy codes used to group defect patterns across make, model, and year.
The filer flagged the following severity indicators: crash: no, fire: no, injuries: 0, fatalities: 0. No crash, fire, or fatality was associated with this report, which places it in the early-warning stream rather than the priority-review stream. Because a VIN was supplied, this complaint is tied to a specific vehicle and not just a model-year cohort.
Individual complaints are consumer-submitted and unverified by NHTSA engineers — the agency's role at this stage is to collect, index, and make them searchable. What matters for federal action is the pattern: when many owners of the same MERCURY VILLAGER cohort independently describe similar equipment:recreational vehicle/trailer:lpg systems:tank assembly failures, defect investigators have grounds to open a PE and request manufacturer data. Related filings for the same vehicle and component appear below, and the detail page for the full 1995 MERCURY VILLAGER shows the complete component-level complaint distribution alongside any active investigations or recalls.
Complaint Description
WHEN DRIVING IN COLD WEATHER, CONSUMER STATES YOU CAN SMELL GAS FUMES IN THE CAB. CAUSE IS UNKNOWN. PLEASE PROVIDE ANY FURTHER INFORMATION. TS
Complaint Details
| NHTSA Complaint ID | 389688 |
| ODI Number | 10004158 |
| Date Filed | January 17, 2003 |
| VIN | NOT AVAILAB |
Source: NHTSA Vehicle Complaints Database. Component taxonomy and severity codes are standardized by NHTSA Office of Defects Investigation.
Read our methodology — how this data is sourced, computed, and verified.