There are 2 stored owner reports matching the powertrain & transmission leading-label group for the 2017 BMW X3 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 2017 BMW X3. The contact stated that while the contact's wife was pulling into a driveway, the vehicle sporadically accelerated and crashed into another vehicle. The contact stated that his wife was pumping the brakes but the vehicle failed to stop immediately. No air bags were deployed. The contact's wife was not injured and did not receive medical attention. A police report was filed. The vehicle was towed to a repair shop. The manufacturer was made aware of the failure. The approximate failure mileage was 100,000. The VIN was not available.
ENGINE SEIZED AT 65MPH HIGHWAY SPEEDS DURING COMMUTE TO WORK ON BUSY BOSTON HIGHWAY. NARROWLY AVOIDED SEVERAL COLLISIONS AS VEHICLE COASTED TO STOP. VEHICLE WAS PURCHASED NEW FROM A BMW DEALER THREE WEEKS AGO AND HAS LESS THAN 2,000 MILES ON IT. DEALER ADVISES AN "OVERSIZED BEARING WAS FOUND IN THE ENGINE CAUSING IT TO OVERHEAT AND SEIZE". ENGINE REQUIRES REPLACEMENT. TRANSMISSION, TRANSFER CASE, ELECTRONICS AND COOLING SYSTEM DAMAGE ARE SUSPECTED BY THE DEALER TECH AND WILL REQUIRE MONITORING.
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.