2016 SUBARU CROSSTREK — Complaint #2089157
Open-data reference.
NHTSA Complaint about LATCHES/LOCKS/LINKAGES:HOOD:LATCH filed May 5, 2025
NHTSA complaint #2089157 (ODI reference 11658990) concerns a 2016 SUBARU CROSSTREK and was filed on May 5, 2025. The owner reports the failure occurred on March 23, 2025. The report was geocoded to Wisconsin based on the filer's self-reported location. The affected component is categorized as latches/locks/linkages:hood:latch, 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 SUBARU CROSSTREK cohort independently describe similar latches/locks/linkages:hood:latch 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 2016 SUBARU CROSSTREK shows the complete component-level complaint distribution alongside any active investigations or recalls.
Complaint Description
Hood latch failed causing hood to fly open, smashing and breaking my windshield.
Complaint Details
| NHTSA Complaint ID | 2089157 |
| ODI Number | 11658990 |
| Date Filed | May 5, 2025 |
| Failure Date | March 23, 2025 |
| VIN | JF2GPABC3G8 |
Similar LATCHES/LOCKS/LINKAGES:HOOD:LATCH Complaints for 2016 SUBARU CROSSTREK
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.