I got in my car started to drive and heard something snap then smoke came from the hood and the car pulled hard right. I immediately stopped and parked the car. The coil spring broke and dug into my front passenger tire and it pulled the axle out of the cv joint.I was in allentown,pa. On a main road in the city. Feb.8,2020.
2001 Mercury Sable: fire, smoke or burning smell
9 of the 430 complaints about the 2001 Mercury Sable describe fire, smoke or burning smell.
- owner complaints
- 9
- of this car's complaints
- 2%
- typical mileage
- 66,000
- recalls
- 0
Fire, smoke or burning smell by model year
What owners say
Tl* the contact owns a 2001 mercury sable. The contact stated that while the brakes being depressed, the engine rmps increased. The brake pedal was released and the vehicle accelerated. The contact was able to place the vehicle in park and there was smoke coming from under the hood. The vehicle was not diagnosed or repaired. The manufacturer was not notified of the failure. The failure mileage was 68,133 and the current mileage was 68,136.
My 2001 mercury sable accelerated as I entered the highway. The car would not stop even when I applied the brake. I called 911. The 911 operator suggested that I apply the parking brake which I did. I went about 15 miles riding the shoulder going between 60-70 miles per hour. I eventually exited the highway but could not stop even at the end of the exit ramp. I made a right hand turn. At this point I had reduced my speed to approximately 30 miles per hour. The car eventually landed in a ditch. At that point, I ended my call with 911. I looked to my left and found four men yelling to me to get out of the car. I then learned that the car was on fire. I exited the car. The four men put the fire out with a fire extinguisher. The car was towed to a mercury dealership where it is documented that it was in fact the speed control cable that caused the car to accelerate. Again, between the 911 call, the information on file with the mercury dealer and the insurance claim, the cause of the incident is documented.
I had a recall performed 2 years ago for the front coil springs. The driver side spring has broken and is cutting into the tire. The car was driven on 01/16/09 and ok. It was parked on the driveway until 01/18/09 when I started to drive, I heard a scraping sound which I thought was ice and snow in the wheel well. I drove aprox. A half block stopped and looked and the wheel wells were clear, I then drove the car back into the driveway and noticed smoke coming from the tire and a grove being cut into the tire. The coil spring is pressing into the tire.
Tl*the contact owns a 2001 mercury sable. The contact stated that there is a recall on the brake wire assembly (recall number 04s12). The recall repair was performed and the wire layover stopped at the steering knuckle. The wires were squeezed together at the top, which caused a fire and skewed the wires together at the harness. The recall was created to correct this failure. The wires became a fire hazard and the vehicle caught fire. The vehicle was taken to the dealer and they informed him that the repair would be his responsibility. The manufacturer stated that they would not honor the repair. The vehicle is currently at the dealer. The current and failure mileages were 66,000.
Emergency brake dashboard warning light failure. The dashboard brake warning light is not turning on when the emergency brake is applied. The dashboard light does test ok when the car is started. Because I was unaware the emergency brake was on I traveled 10 miles home on the freeway. Near my house the brakes failed, with the pedal going to the floor. I quickly pumped the brakes and was able to stop. There was a burning smell as well, which I assume was the pads, so I will mark the fire question as yes since "where there's smoke there's fire." brake function returned the next day but the pedal is now soft.
Recently my 2001 mercury sable ls caught fire very shortly after the power steering system completely failed.
While parked vehicle caught on fire underneath the hood. Due to severe fire damage vehicle was totaled.
While driving at 35 MPH consumer was notified by a passing motorist that trunk was on fire. Upon inspection, it had been determined that fire started in the rear tail light. One of the occupants sustained third degree burns. Ford advised that the cause of the problem is unknown. *ak *ts
Service bulletins that may apply
- Malfunction indicator lamp on with diagnostic trouble code P0133, P1131 or P2195
- Malfunction indicator lamp (MIL) illuminated - system lean diagnostic trouble codes (dtc's) - service tips
- Streamlined diagnostic procedure for vehicles with malfunction indicator lamp (MIL) on and diagnostic...
- Malfunction indicator lamp (MIL) on with multiple diagnostic trouble codes (DTCS)
- Streamlined diagnostic procedure for vehicles with malfunction indicator lamp on and diagnostic trouble...
- Malfunction indicator lamp illuminated with diagnostic trouble codes (DTCS) P0442, P0455, P0456, P0457 or...
- Remote keyless entry (RKE) - service tips
- Some vehicles may exhibit diagnostic trouble code B1213, B1342, B1601, B2431
Related recalls
No recalls on record for this model year.
Questions about the 2001 Mercury Sable fire or smoke
Is fire, smoke or burning smell a common problem on the 2001 Mercury Sable?
9 of 430 owner complaints about the 2001 Mercury Sable (2%) mention fire, smoke or burning smell. The model year with the most reports is 1995.
Is there a recall or service bulletin for this on the 2001 Mercury Sable?
There are 0 recalls and 12 service bulletins for the same area of the car. Check them below with your VIN.
Other symptoms on the 2001 Mercury Sable
Coil spring 147Sudden acceleration 15Tire blowout 15Adaptive cruise 13Brake failure 11Seat belt 10No deployment 9Won't start 8Transmission failure 7Grinding brakes 6Check engine light 5Jerking 5Wipers 5
VIN decoder
See the problems and recalls for an exact car
Buying a used 2001 Mercury Sable?
Check the exact car before you pay: accidents, salvage or flood titles, odometer readings and previous owners.
Check its history