There are 2 stored owner reports matching the engine leading-label group for the 2023 BMW i4 in our NHTSA-sourced dataset. These are unverified consumer reports and may not reflect confirmed defects.
This group counts stored reports whose component label starts with one of this site's matching prefixes, ignoring case. Each matching report counts once within the group. Components mentioned later in the label or only in the narrative are not searched. How component counts work
Loaded 2 of 2 matching reports.
Open the full vehicle complaint log (all categories)The contact owns a 2023 BMW i4. The contact stated that while driving at 20-30 MPH with a fully charged battery, the engine seized on two separate occasions. There was an abnormal grinding sound detected. The inoperable do not drive message was displayed after the failure. The vehicle was towed to the local dealer, where it was diagnosed with drive unit failure. The drive unit, rear axle, and battery were replaced, but the failure recurred. While his son was driving at approximately 30 MPH, the engine seized. There were no warning lights illuminated. The vehicle was towed two weeks later to the local dealer again, where it was diagnosed that the drive unit and drive axle needed to be replaced. The vehicle was not repaired. The manufacturer was contacted, who opened a case; the contact requested a buyback, but no additional assistance was provided. The failure mileage was approximately 16,000.
Drivetrain malfunction, made car inoperable. Went into park mode. No neutral ability to move. Had to be special tow. Car is 2 days old. Only 200 miles on odometer. Check internet, many many same issues.
Complaints are unverified consumer reports submitted to NHTSA. A high complaint count may reflect vehicle popularity, not defect severity. Data sourced from NHTSA public records.
NHTSA source checks for this vehicle year
Checks are recorded separately for each dataset, not for the whole page. Dates use UTC. A missing check date does not mean no records exist.
Vehicle import recorded: Apr 28, 2026. This is the stored import date, not confirmation that every source was successfully refreshed.