1992 CHRYSLER NEW YORKER — Complaint #384949
Open-data reference.
NHTSA Complaint about VEHICLE SPEED CONTROL:SPRINGS filed December 11, 2002
NHTSA complaint #384949 (ODI reference 8024159) concerns a 1992 CHRYSLER NEW YORKER and was filed on December 11, 2002. The report was geocoded to Texas based on the filer's self-reported location. The affected component is categorized as vehicle speed control:springs, 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 CHRYSLER NEW YORKER cohort independently describe similar vehicle speed control:springs 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 1992 CHRYSLER NEW YORKER shows the complete component-level complaint distribution alongside any active investigations or recalls.
Complaint Description
CONSUMER CALLED COMPLAINING ABOUT HAVING PROBLEMS WITH FUEL LAYER. ALSO STATED THAT IS LEAKING AT O-RINGS IN TOP OF THE ENGINE.DEALER WAS CONTACTED AND STATED THAT AS FAR AS THEY KNOW THERE WERE NO RECALLS SO THERE WAS NOTHING THEY CAN DO. MR
Complaint Details
| NHTSA Complaint ID | 384949 |
| ODI Number | 8024159 |
| Date Filed | December 11, 2002 |
| VIN | PLEASE PROV |
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.