BMW X5 fire or smoke problems

Filed Nov 5, 2026 · Engine · VA · fire

While driving home vehicle began to smoke. Pulled over thinking it may be overheating, not realizing it was smoke. No warnings or messages were displayed. Parked, turned off ignition and called husband from vehicle. When smoke became overwhelming I got out of vehicle. Noticed sparks dripping from under vehicle. Called 911 as sparks became a fire. Entire engine was engulfed in flames as fire department arrived. Police arrived on scene and vehicle was towed and inspected the following day by Geico who declared vehicle a total loss.

Filed Oct 16, 2026 · Engine · NJ

On October 15, 2026, at approximately 5:50 PM EDT, my 2022 BMW X5 (VIN: 5UXCR6C06N9L45925, approximately 43,797 miles) caught fire in the engine compartment. I noticed a burning smell while driving in Bound Brook, NJ, pulled over, and saw flames coming from the engine bay. There was no collision. The Bound Brook Fire Department responded and extinguished the fire. The vehicle was purchased new in 2022 and regularly maintained. No injuries occurred.

Filed Sep 18, 2026 · Electrical · CA · fire

Two incidents accured with 24hrs. My wife called me informing that the 2018 x5 was smoking from the front and making a weird noise, she stopped the vehicle and the vehicle started again. When she got home, I checked the under the hood, but could not see anything. But, can smell like burned wiring, but not visible. I connected EV wire to the vehicle and next morning disconnected the cable and when I started the vehicle, I saw smoke coming out of the inside bottom of the rear where the batteries are located. I opened the rear door and raised the cover to see smoke coming from melted wiring. I immediatelly disconnected one of the battery wires.

Filed Sep 9, 2026 · Engine, Fuel system · 160,000 miles · CO · fire

The contact owned a 2015 BMW X5. The contact stated that while driving 60 MPH, the contact became aware of sparks outside the driver's and passenger's side of the vehicle. The contact became aware that there were flames coming from under the hood. The contact stated that the fire had started in the engine compartment. The message "Add Coolant" was displayed, and there was an abnormal odor while the vehicle was on fire. The contact immediately exited the vehicle. The Fire Department responded to the scene and extinguished the fire. A fire report was filed. The vehicle was completely burned and was towed to a tow yard, where it was deemed a total loss by the insurance company. The vehicle was previously repaired under the federal safety agency Campaign Number: 21V907000 (Fuel System, Diesel). Additionally, the EGR cooler and the diesel particulate sensor were replaced under warranty; however, the repairs failed to fix the vehicle. The manufacturer, BMW, was notified of the failure. The failure mileage was approximately 160,000.

Filed Jun 29, 2026 · Engine, Transmission · TX

I purchased my vehicle around Labor Day of 2020. I still own and operate the vehicle. Since I have owned my vehicle, I have repeatedly been told my turbos are leaking oil, etc. I have even had several oil leaks repaired on my car. Fast forward six years, and I am buying 5 quarts of oil every two weeks and topping up the oil in my vehicle every week, at least 2-3 quarts per week. I also have smoke coming out of the tail pipes intermittently. The car also smells like it is burning oil, but there are no visible oil drips on the ground currently. I discovered by research there have been two lawsuits: Isley v. BMW of North America LLC, et al., Case No. [XXX] in the U.S. District Court for the District of New Jersey ([XXX] [XXX]), and Bang v. BMW (Original [XXX]) ([XXX]). I have had repeated documented repairs and I never received a notice for these cases. I need my vehicle repaired and I need BMW to take ownership of this defect. I never received one notice regarding these lawsuits, or I would have had my vehicle repaired. I only have 102,000 miles (currently), so my vehicle should be covered in terms of mileage. INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)

Filed Mar 10, 2026 · MD · fire

My family and I were traveling from Maryland to Florida, with a planned stop in Atlanta. We were driving our 2013 BMW X5 x Drive 35i and were traveling southbound on [XXX] through Greenville, South Carolina when the incident occurred. While driving at highway speed, my husband suddenly noticed multiple error messages appearing on the vehicle’s display screen - air bag malfunction, 4x4 malfunction, stabilization, etc. He immediately began pulling the vehicle over. Within moments, he observed smoke and visible flames coming from the rear driver’s-side area of the vehicle. He urgently shouted for me and our daughter to get out of the car. What followed happened extremely fast, within approximately 15 seconds. I yelled for my daughter to unbuckle and run. In a state of panic, I grabbed our dog, and as we tried to exit the vehicle, the fire spread rapidly and aggressively. Thick, black smoke engulfed the area and we fled on foot, coughing and struggling to breathe from the smoke. By the time we reached a safe distance, the vehicle was fully engulfed in flames. Thankfully, we were able to escape without physical injury, but the incident was terrifying and could very easily have resulted in serious injury or loss of life. The vehicle was completely destroyed, along with all of our personal belongings - cell phones, laptops, clothing, luggage, etc. We have since checked for recalls associated with the vehicle’s VIN and were told none were listed. However, a vehicle should not spontaneously catch fire while being operated normally on a highway. The sudden onset, rapid spread of the fire, and lack of warning raise serious concerns about a potential defect, whether electrical, fuel-related, or otherwise. We believe this incident was preventable and that there may have been a failure in design, manufacturing, or warning. We had the insurance company and BMW inspect the vehicle, but the fire destroyed the car entirely, and a cause "could not be determined." INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION AC

Filed Mar 5, 2026 · Electrical, Engine · CA · fire

While driving through west Los Angeles, the vehicle suddenly began emitting white smoke from the engine compartment. There were no prior warning lights, messages, or symptoms indicating a problem. The smoke quickly intensified and turned dark. Thick smoke filled the air, and the cockpit, with the smell of toxic fumes. I safely maneuvered to the shoulder and exited the vehicle with my passenger. Flames erupted from the front of the vehicle. We called 911, which dispatched the fire department. The LAFD responded, cutting open the hood in order to extinguish the fire. The vehicle was towed to a yard following the incident. The vehicle and its contents were declared a total loss. Â BWM North America dispatched a technician to inspect the vehicle. After inspection, the manufacturer indicated that the starter was the source of the fire. At the time of the incident, the vehicle was subject to a safety recall related to the starter with no remedy available. The failure occurred without warning. Both occupants were exposed to heavy smoke.

Filed Mar 2, 2026 · Electrical, Engine · GA

While driving, the vehicle displayed a 'Drivetrain malfunction' warning on the dashboard and began jerking. I safely pulled over and turned off the vehicle. Immediately after stopping, there was a distinct, strong electrical burning smell coming from the engine compartment. The vehicle was inspected by an authorized BMW dealership. The dealer diagnosed a catastrophic failure of the starter motor. The vehicle's computer logged fault codes 21611A (excessive counter-torque), 21A511 (Start system: Timeout), and 216119 (Line disconnection). These codes confirm the starter motor suffered a severe electrical overload and thermal event. This premature failure and fire hazard identically matches the safety risks outlined in BMW's recent massive starter motor recalls (such as the federal safety agency Recalls 25V‑636 and 26V‑056), but my specific vehicle is currently excluded from those recall campaigns. The starter requires complete replacement due to this overheating damage

Filed Jan 9, 2026 · NY · fire

Incident Date: [XXX] Vehicle: 2025 BMW X5 xDrive50e Issue: car fire On [XXX], while operating my 2025 BMW X5 xDrive50e (purchased new on [XXX]), a malfunction warning appeared on the infotainment screen. Immediately following this alert, the vehicle cabin filled rapidly with smoke. ​Upon stopping and exiting the vehicle, I observed flames coming from underneath the car. The fire quickly spread to the rear and trunk area of the vehicle. The car is likely a total loss. ​This fire created a life-threatening situation, as the cabin filled with smoke while the vehicle was in motion, requiring an emergency exit before the flames spread. ​A police report was filed on the date of the incident ([XXX]); a copy of the report is pending. My insurance provider has been notified and is scheduled to inspect the vehicle early next week. Prior to this event, the vehicle had not been involved in any collisions and had no aftermarket modifications. ​The vehicle is currently located at All Star Collision in Farmingdale, though it is expected to be relocated by Progressive, my insurance carrier, in the near future. A police report was filed today but I have yet to receive a copy. I'm happy to provide if needed upon receipt. INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)

Filed Jan 3, 2026 · CA · fire

My car was sitting on the driveway and spontaneously caught on fire. It has not been driven for the last week or two. Nobody was home, when it caught on fire. Our neighbors called 911