17 of the
105 complaints about the 2025 BMW X5 are about the
driver-assist systems — 16% of everything
reported for this model year.
Half of the failures with a mileage on record happened before
80 miles.
F
17
Complaints
7
Crashes
0
Fires
1
Injuries
Exactly what failed
Automatic Emergency Braking
529.4%
Warnings
423.5%
Warnings
211.8%
Rearview System Braking
211.8%
Back Over Prevention
15.9%
Blind Spot Detection
15.9%
Adaptive Cruise Control
15.9%
Steering Assist
15.9%
Driver Assist & Collision Avoidance across every BMW X5 year
FORWARD COLLISION AVOIDANCE: ADAPTIVE CRUISE CONTROL
While driving eastbound on [XXX] on XXX between approximately 9:29 and 10:21 AM, the vehicle suddenly displayed a red warning instructing the driver to “Take over braking function immediately.” At that moment, adaptive cruise control braking and automated braking assistance disengaged without warning, requiring the driver to manually brake while in traffic. This created an unexpected safety hazard for the driver, passengers, and surrounding motorists. Prior to this event, the vehicle had exhibited repeated Driver Assistance instability across multiple service visits, including inconsistent adaptive cruise control behavior, braking‑related restrictions, and GPS mislocation affecting ADAS functions. The vehicle has been inspected by the manufacturer’s authorized dealer across five service visits, including replacement of the head unit and multiple software resets. The underlying malfunction has occurred repeatedly, but the specific braking alert has not been reproduced by the dealer. No crash, fire, or injury occurred. INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)
NHTSA complaint #11757153 — an unverified report by a vehicle owner.
While driving eastbound on [XXX] on XXX between approximately 9:29 and 10:21 AM, the vehicle suddenly displayed a red warning instructing the driver to “Take over braking function immediately.” At that moment, adaptive cruise control braking and automated braking assistance disengaged without warning, requiring the driver to manually brake while in traffic. This created an unexpected safety hazard for the driver, passengers, and surrounding motorists. Prior to this event, the vehicle had exhibited repeated Driver Assistance instability across multiple service visits, including inconsistent adaptive cruise control behavior, braking‑related restrictions, and GPS mislocation affecting ADAS functions. The vehicle has been inspected by the manufacturer’s authorized dealer across five service visits, including replacement of the head unit and multiple software resets. The underlying malfunction has occurred repeatedly, but the specific braking alert has not been reproduced by the dealer. No crash, fire, or injury occurred. INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)
NHTSA complaint #11757153 — an unverified report by a vehicle owner.
Fountain Hills, AZ
FORWARD COLLISION AVOIDANCE: WARNINGS
While driving eastbound on [XXX] on XXX between approximately 9:29 and 10:21 AM, the vehicle suddenly displayed a red warning instructing the driver to “Take over braking function immediately.” At that moment, adaptive cruise control braking and automated braking assistance disengaged without warning, requiring the driver to manually brake while in traffic. This created an unexpected safety hazard for the driver, passengers, and surrounding motorists. Prior to this event, the vehicle had exhibited repeated Driver Assistance instability across multiple service visits, including inconsistent adaptive cruise control behavior, braking‑related restrictions, and GPS mislocation affecting ADAS functions. The vehicle has been inspected by the manufacturer’s authorized dealer across five service visits, including replacement of the head unit and multiple software resets. The underlying malfunction has occurred repeatedly, but the specific braking alert has not been reproduced by the dealer. No crash, fire, or injury occurred. INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)
NHTSA complaint #11757153 — an unverified report by a vehicle owner.
Our 2025 BMW X5 50e was involved in an accident while slowly pulling into a parking spot at Bryce Canyon National Park in Utah. While turning right into the striped parking spot, the car suddenly accelerated, swiping the car parked to the right and continued on to break through a rung of the log fence barrier before manual hard braking stopped it from plunging into the canyon below. There was no audible alarm heard and apparently no emergency braking engaged to prevent impact with the other car or log fence. No airbags deployed. Emergency braking was enabled. Drive mode was Hybrid. With the grill damaged and a front sensor hanging below the damaged bumper. We are still awaiting the Park Ranger report.
NHTSA complaint #11753465 — an unverified report by a vehicle owner.
Mesquite, NVCrash
BACK OVER PREVENTION: WARNINGS
Our 2025 BMW X5 50e was involved in an accident while slowly pulling into a parking spot at Bryce Canyon National Park in Utah. While turning right into the striped parking spot, the car suddenly accelerated, swiping the car parked to the right and continued on to break through a rung of the log fence barrier before manual hard braking stopped it from plunging into the canyon below. There was no audible alarm heard and apparently no emergency braking engaged to prevent impact with the other car or log fence. No airbags deployed. Emergency braking was enabled. Drive mode was Hybrid. With the grill damaged and a front sensor hanging below the damaged bumper. We are still awaiting the Park Ranger report.
NHTSA complaint #11753465 — an unverified report by a vehicle owner.
at 30 milesSaint Loius, MO
BACK OVER PREVENTION
The contact owns a 2025 BMW X5. The contact stated that while reversing, the back-over prevention camera display audio system failed to function as intended. The back-over prevention camera audio alert failed to beep when the vehicle was close to other vehicles or objects. The vehicle was taken to the dealer; however, the failure was not duplicated. The contact stated that a computer test was performed; however, the failure was not duplicated. Additionally, the technician test drove the vehicle, but the failure was not duplicated. The vehicle was not diagnosed or repaired by an independent mechanic or dealer. The contact had a neck injury and stated that the failure of the back-over prevention system was an inconvenience. The manufacturer was not made aware of the failure. The failure mileage was approximately 30.
NHTSA complaint #11724566 — an unverified report by a vehicle owner.
NY, NYCrash
BACK OVER PREVENTION: WARNINGS
While attempting to park forward into a handicapped parking space, the car lurched forward approximately 4 feet instead of braking/stopping. The braking system appeared to fail and the electrical/sensors/ADAS warnings did not engage. The vehicle drove over a cement parking block and struck a building shrub, signage and hvac unit.
NHTSA complaint #11706385 — an unverified report by a vehicle owner.
While attempting to park forward into a handicapped parking space, the car lurched forward approximately 4 feet instead of braking/stopping. The braking system appeared to fail and the electrical/sensors/ADAS warnings did not engage. The vehicle drove over a cement parking block and struck a building shrub, signage and hvac unit.
NHTSA complaint #11706385 — an unverified report by a vehicle owner.
Atlanta, GACrash1 injured
FORWARD COLLISION AVOIDANCE: WARNINGS
On September 2, 2025, my 2025 BMW X5 xDrive50e was involved in a head-on collision with another vehicle. Despite the severity of the impact, the following safety systems failed to deploy: Front airbags Driver seatbelt pretensioner BMW Assist / automatic emergency notification Witnesses reported that my vehicle briefly went airborne before landing with the rear wheels up on a curb. I suffered neck injuries, and my vehicle sustained significant frontal damage. BMW later downloaded the Event Data Recorder (EDR) and confirmed: A frontal non-deployment event Three fault codes in the airbag control module (ACSM) post-crash The crash algorithm activated and reset ΔV reached approx. 12.4 mph longitudinal Forward Collision Mitigation system issued an acute warning 0.5 seconds before impact BMW states the “impulse was not sufficient” to trigger restraint deployment BMW has refused to provide: The deployment thresholds (ΔV criteria) for airbags or pre-tensioners Any engineering explanation for why restraint systems did not activate Any technical rationale for the ACSM fault codes Any escalation beyond Customer Relations All I have been given is an unsigned summary letter and the raw EDR file. BMW Customer Relations stated that engineering is “not customer-facing” and that no additional information will be provided. This leaves serious concerns that: The restraint systems did not function properly in a real-world impact. BMW is refusing to disclose the engineering basis for its conclusions. Consumers may be at risk if this is a repeatable failure mode. I am requesting NHTSA review this incident as a potential defect in the airbag, pretensioner, and/or crash-sensing system in the 2025 BMW X5. I can provide the EDR report, photos, BMW’s letter, and full correspondence upon request. VIN: [XXX] Mileage: ~10,700 Crash Date: 09/02/2025 BMW Case #: XXX INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)
NHTSA complaint #11701093 — an unverified report by a vehicle owner.
New Hyde Park, NY
BACK OVER PREVENTION: REARVIEW SYSTEM BRAKING
The rear cross traffic alert on this vehicle either does not work at all or, when it does work, it is ineffective in warning the driver. I brought the vehicle into my BMW dealer and they told me that it is operating as intended. In most cases, when backing out of a parking space or my driveway, I get no warning at all. In some cases, I did get some faint warning that was not obvious enough to actually get my attention. Many times, when I was backing up, I almost was hit by a passing car because I expected to get a warning and did not. There is a very large number of complaints about this problem on the internet. Unfortunately, I did not see these complaints before buying the vehicle. Had I known that this safety feature was ineffective in what it was designed to do, I would not have bought the vehicle. I am actually considering selling vehicle after only 7 months of ownership and taking a loss as a result of this problem. If there is a loss to be taken, it should be by BMW not me as the consumer. I believe that BMW has committed fraud with respect to rear cross traffic alert. They falsely represent that the vehicle has rear cross traffic alert which is a material fact known by them to be false. Buyers, to their own detriment, rely on this false representation in deciding to buy the vehicle. The buyer is not getting an important safety feature that they paid for and the absence of the safety feature puts them at risk of a collision.
NHTSA complaint #11689222 — an unverified report by a vehicle owner.
Monroe, MI
BACK OVER PREVENTION: REARVIEW SYSTEM BRAKING
My cross traffic warning system is inoperative. Dealer said the sensors are operating normally. This is a safety hazard.
NHTSA complaint #11672440 — an unverified report by a vehicle owner.
Driving home on a two lane road that is joined by a side road at a 45degree angle. A woman ran the stop sign and suddenly appeared on my road right in front about 40-50 feet away. The BMW did not show any visual or audible warning and the forward collision mitigation system functioned in a substandard way not mitigating the crash into the woman’s drivers door. Damages amounted to 25.8k to my vehicle and took 48 days to repair at my local BMW dealer in Albany NY. BMW states to me that the system worked properly. If that was the case how come I had massive front end damage impacting about 30 mph. The BMW manual shows a frontal cross traffic intrusion and leads one to believe in the system. It is substandard and needs revision by BMW engineering.
NHTSA complaint #11671130 — an unverified report by a vehicle owner.
Queensbury, NYCrash
FORWARD COLLISION AVOIDANCE: WARNINGS
Driving home on a two lane road that is joined by a side road at a 45degree angle. A woman ran the stop sign and suddenly appeared on my road right in front about 40-50 feet away. The BMW did not show any visual or audible warning and the forward collision mitigation system functioned in a substandard way not mitigating the crash into the woman’s drivers door. Damages amounted to 25.8k to my vehicle and took 48 days to repair at my local BMW dealer in Albany NY. BMW states to me that the system worked properly. If that was the case how come I had massive front end damage impacting about 30 mph. The BMW manual shows a frontal cross traffic intrusion and leads one to believe in the system. It is substandard and needs revision by BMW engineering.
NHTSA complaint #11671130 — an unverified report by a vehicle owner.
Multiple issues with the software. 1. Since yesterday, [XXX] car failed to start with the message "software upgrade failed". Sitting like a brick now - engine doesn't start and can't get the car off parking mode. 2, Last week, the remote functions of the software as well as emergency call system stopped working. Called the local dealer BMW of North Canton on June 25, Ohio to check and fix and they scheduled it for Monday June 30. But car refused to start per point 1. 1. Couple of times got the message while driving that driver inability to drive detected and suddenly slowing down the car and veering it to a side. Transient actions. Took it to the dealership, supposedly a software bug was fixed but then the message flashed one more time recently. INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)
NHTSA complaint #11669880 — an unverified report by a vehicle owner.
at 80 milesMiami, FL
LANE DEPARTURE: BLIND SPOT DETECTION
The contact owns a 2025 BMW X5. The contact stated while driving at approximately 35 MPH, the blind spot warning light was inoperable, and the Forward Collision Avoidance assist sensor warning light was deactivated on the instrument cluster. The contact had taken the vehicle to the dealer, where it was diagnosed and determined that the electrical system and harness had failed and needed to be replaced. The vehicle was repaired. The contact stated that the Lane Keep Assist System was inoperable. The contact had taken the vehicle back to the same dealer. The vehicle was not diagnosed or repaired. The manufacturer was informed of the failure. The failure mileage was approximately 80.
NHTSA complaint #11659880 — an unverified report by a vehicle owner.
at 80 milesMiami, FL
LANE DEPARTURE: LANE KEEP: STEERING ASSIST
The contact owns a 2025 BMW X5. The contact stated while driving at approximately 35 MPH, the blind spot warning light was inoperable, and the Forward Collision Avoidance assist sensor warning light was deactivated on the instrument cluster. The contact had taken the vehicle to the dealer, where it was diagnosed and determined that the electrical system and harness had failed and needed to be replaced. The vehicle was repaired. The contact stated that the Lane Keep Assist System was inoperable. The contact had taken the vehicle back to the same dealer. The vehicle was not diagnosed or repaired. The manufacturer was informed of the failure. The failure mileage was approximately 80.
NHTSA complaint #11659880 — an unverified report by a vehicle owner.
Frankfort, IL
FORWARD COLLISION AVOIDANCE: WARNINGS
Forward Collision Braking, a safety system, is deactivated when cruise control is activated. Further BMW sells the X5 with the mode button of the Driver Assistance Package available on the steering wheel. This to me is deceptive. My previous X5 had the system a when I activated it by pressing the mode button it worked. I assumed by pressing the mode button on the new X5 it would also work. To me this is like activating the turn signal- the feature is there, you activate it, you expect it to work.
NHTSA complaint #11658853 — an unverified report by a vehicle owner.