10.0

really awful
Crashes / Fires:
3 / 0
Injuries / Deaths:
2 / 0
Average Mileage:
5,708 miles

About These NHTSA Complaints:

The NHTSA is the US gov't agency tasked with vehicle safety. Complaints can be spread across multiple & redundant categories, & are not organized by problem. See the Back button — blue bar at the very top of the page — to explore more.

Get notified about new defects, investigations, recalls & lawsuits for the 2015 BMW X1:

Unsubscribe any time. We don't sell/share your email.

« Read the previous 20 complaints

problem #9

Feb 162016

X1

  • miles
Takata recall have been waiting since Feb 2016 for this issue to be resolved. BMW has no idea when it will be resolved.

- Mount Holly, NC, USA

problem #8

Mar 012016

X1

  • miles
Takata recall. The contact owns a 2015 BMW X1 sav. The contact received notification of NHTSA campaign number: 16V071000 (air bags); however, the part to do the repair was unavailable. The manufacturer exceeded a reasonable amount of time for the recall repair. The manufacturer was not notified. The contact had not experienced a failure. VIN tool confirms parts not available.

- Delmar, NY, USA

problem #7

May 022016

X1

  • miles
BMW refuses to let me out of my lease but do not want to fix the defect because the parts are out of stock for several months. I have a small child and am afraid for our safety.

- Staten Island, NY, USA

problem #6

Mar 022016

X1

  • miles
Takata recall. The contact owns a 2015 BMW X1 sav. The contact received notification of NHTSA campaign number: 16V071000 (air bags) and stated that the part needed for the repair was not available. The contact stated that the manufacturer exceeded a reasonable amount of time for the recall repair. The manufacturer was made aware of the issue. The contact had not experienced a failure. VIN tool confirms parts not available.

- Seattle, WA, USA

problem #5

Mar 012016

X1

  • miles
Takata recall. The contact owns a 2015 BMW X1 sav. The contact received notification of NHTSA campaign number: 16V071000 (air bags); however, the part to do the repair was not available. The contact stated that the manufacturer exceeded a reasonable amount of time for the recall repair. The manufacturer was not notified. The contact had not experienced a failure. VIN tool confirms parts not available.

- Woodland Hills, CA, USA

problem #4

Mar 152016

X1

  • miles
Takata recall. The contact owns a 2015 BMW X1 sav. The contact received a notification of NHTSA campaign number: 16V071000 (air bags); however, the parts for the recall repair were not available. The contact stated that the manufacturer exceeded a reasonable amount of time for the recall repair. The manufacturer was notified of the issue. The contact had not experienced a failure. VIN tool confirms parts not available.

- Tracy, CA, USA

problem #3

Nov 102015

X1

  • 8,500 miles
I crashed my car on 11/10/2015 and the airbag did not deploy. I drove through a heavy rail fence and struck a tree with the left front side of the bumper. A large section of the fence penetrated the front of the car and lodged in the vehicle. Cause of accident I became unconscious while driving due to heart problem

- Cumming, GA, USA

problem #2

Apr 012016

X1

  • 24,000 miles
Takata recall. BMW did not make me aware of this dangerous airbag recall. I was in the process of transferring my lease to another willing party when BMW notified me of the recall issue and blocked the lease transfer which they had previously agreed to. They also will not let me purchase the vehicle. Both these issues breach the lease agreement I signed with them. The car is unusable with such a defect and is likely to take 6months or more to fix. They offer no time line to fix the issue and request that I sign a waiver accepting an inferior rental care during the period it takes for them to resolve the issue and assume the cost and liability of storing the unusable BMW. I either want BMW to fix the issue immediately, let me cancel my lease with no penalty.

- Belmont, CA, USA

problem #1

Feb 072016

X1

  • 40 miles
On February 7th, 2016 at 3:15 am, on my way to work in the intersection between forest hill and military, a drunk driver traveling West bound while I was heading East drove into my lane, hitting me directly. After this head-on collision, the driver decided to flee the scene, leaving me stuck inside the vehicle in pain. I was lucky enough to be alive. The airbag inside of my vehicle did not deploy leaving me with excruciating pain in my neck, chest and knee. I could not breathe or talk, I was rush to the wellington regional hospital. I was approaching the light and I was going to turn left on military trail, the guy who crashed onto me was coming from the North on military trail trying to make a right onto forest hill blvd, but took the lane heading East instead of the one heading West. He was driving really fast while I was approaching the light to turn left.

- Wellington, FL, USA