2004 Mercury Sable
Safety record from NHTSA: recalls, owner complaints, investigations and service bulletins.
Vehicles › Mercury › Sable › 2004
Safety record from NHTSA: recalls, owner complaints, investigations and service bulletins.
These records cover every 2004 Mercury Sable. To see whether one car still needs a recall repair, decode its VIN or check it with NHTSA.
2 recalls name the 2004 Mercury Sable. Newest first.
Bosch Brake Components LLC (Bosch) is recalling certain aftermarket replacement front brake pads, models Bosch QuietCast BC598 and BP765, Bosch Blue BE598 and BE598H, Prostop PD598 and PD765M, Duralast Gold DG598, Duralast MKD598, Stop Master ST598, UltraStop ULT598, UltraLife MX598 and MX765, BrakeBest MKD765, and Prostop Platinum PGD598. These brake pads…
A damaged or broken brake disc may reduce a vehicle's braking power, increasing the risk of a crash.
Bosch will instruct the owners how to have the affected brake pads replaced, free of charge. The recall began on May 26, 2016. Owners may contact Bosch customer service at 1-888-715-3616.
Certain passenger vehicles equipped with power adjustable seats may have been inadequately welded.
The seat may not perform as intended during a crash which could increase the risk of injury.
Dealers will replace the upper support assembly on the power seats. the recall began on july 20, 2004. owners should contact ford at 1-800-392-3673.
TL* the contact owns a 2004 mercury sable. The contact stated that while brake lights were activated, the contact was unable to shift the vehicle from park into drive. Fred beans ford of doylestown (876 n easton rd, doylestown, pa 18902), (215) 348-2901) was contacted and informed of the failure. The contact was informed that the stop lamp switch needed to be replaced. The vehicle was repaired. The contact stated that the failure was related to nhtsa campaign number: 16e026000 (service brakes, hydraulic) however, the recall was for the year 2003 vehicles. The manufacturer was notified of the failure. The approximate failure mileage was 99,800.
While parked, tried to put car in reverse to back out of driveway but car will not shift out of park. Only way to get car to shift out of park IS to apply emergency brakes then shift car into neutral while key turned to off position. Break lights will not illuminate when brake pedal applied. I checked all the fuses and replaced the break lamp bulbs to troubleshoot issue according to owners manual however problem still exists. When researching online I read about the same exact issues occurring in same model and make that were recalled. I went to my nearest ford dealership to inform them about this issue and get some assistance in fixing the problem. However they would not help in the matter, and stated that my particular vin # and year model 2004 had no recalls. The recall was issued for faulty break light switches in 2003 and previous year models of mercury sables. I've read about numerous issues occurring with other 2004 mercury sable owners that also cannot get help with this matter. This IS obviously a safety issue and it IS my hope that the nhtsa investigates to find out why 2004 models are also exhibiting same recall safety issues. The problem obviously lies with the part (same break light switch) ford installed on these vehicles and not necessarily the year the vehicle was made. It has always been my understanding that the primary mission and role of the nhtsa IS to help keep the public safe and informed about potential safety issues. Therefore, I hope they not only investigate why ford used the same faulty part on other year model vehicles but also issue the necessary recall for said vehicles with those parts. If, while traveling with my family, a car slams into us because no break lights will engage, whose fault IS that? I've brought this safery issue concern to the attention of ford and now the nhtsa. Failure to address this issue puts the public in danger!
The airbag warning light has started coming on intermittently while the car IS running on a city street. I don't know why but it appears to be a critical safety problem. the car has never been in an accident and only has 78,000 miles , very low for a 2004 vehicle. ford motor dealer says there IS no recall of any kind on this car. I am a retired senior citizen and this IS my only form of transportation.
Car accelerated by itself to above 55 mph at local road, when put to parking, the engine kept running at more than 3500 rpm, it was crazy, nearly killed some kids.
The brake light switch failed causing inability to get shift lever out of park mode. Brake lights stay on all the time or not come on at all. The problem was noted after parking in our garage and noticing the brake lights being on all the time. I discovered that turning the ignition switch to first indent that the shift lever can be placed in the neutral mode so engine can be started. In driving the car, the brake lights do not work. When stopping the car and shifting to the park mode, the shift lever cannot be taken out of the park mode without going through the sequence described above. There was a recall to repair this on the 2000-2004 sables (reference 04v106000), but ford tells me the 2004 sables are not under recall although the 2004 models use the same defective brake light switch causing the exact problems as the 2000-2003 models. *tr
I contacted ken grody ford in buena park,ca 2-3 months ago to ask if there were any recalls on my car? The manager I spoke with told me "no!" he also mailed me a copy of his "oasis" search which showed no recalls! Help! [Xxx] please mail me recall alerts on my car! information redacted pursuant to the freedom of information act (foia), 5 u.s.c. 552(B)(6). *tr
TL* the contact owns a 2004 mercury sable. The contact stated that the security light randomly flashed and the alarm randomly sounded within less than than two days of owning the vehicle. The vehicle was not diagnosed nor repaired. The manufacturer was notified of the failure. The failure mileage was not available.
TL* the contact owns a 2004 mercury sable. While driving at high speeds, the rpms increased without warning. The vehicle surged forward and exhibited rapid acceleration. The vehicle was not diagnosed or repaired. The manufacturer was notified of the failure. The failure mileage was approximately 135,000.
Driving along residential area, extremely loud bang with burning rubber smoke. stopped in road looked under hood found nothing wrong. tried to drive again and there was a bumping noise and more rubber smell and smoke. repeat inspection determined that the drivers wheel clearance was dropped and rubbing on the wheel. search of internet shows that springs are routinely breaking and causing injury and death.
Car will not come out of park, nor will brake lights operate when pedal depressed. Exact symptoms as described in previous model year recalls. Only wayto get car out of park IS to place in neutral after turning key in ignition to first avaialble position, then applying brake pedal to release shift lock. this IS a recurring problem w/ a failed brake light switch assembly. it's too dangerous of a problem to not have a recall. Many other model vehicles have been recalled for the same exact problem. why not this model?
TL* the contact owns a 2004 mercury sable. The contact stated that the rear tail lights remained illuminated when the brake pedal was not depressed. The vehicle was not diagnosed or repaired. The manufacturer stated that the vehicle was not included in nhtsa campaign number: 04v106000 (exterior lighting). The vehicle was not repaired. The approximate failure mileage was 90,000.
The car will not come out of park, nor do the brake lights work and sometimes the brake lights stay on. There was a recall for this very issue. Recall #04s12 or 04v106000. However the recall stops at 2003. My vehicle has the same defective switch in it but ford IS refusing to replace it. They claim my vehicle was made a few days after the recall stopped. Well that doesn't make my brake pedal switch any safer. I'm being handed a line of crap by ford. They installed a defective switch and have admitted its defective and wont fix mine because of a manufacture date. What court wouldn't prosecute ford if I have a serious accident because of this defective switch that they know IS defective but refuse to fix it. *tr
Car will not come out of park, nor will brake lights operate when pedal depressed. exact symptoms as described in previous model year recalls. only wayto get car out of park IS to place in neutral after turning key in ignition to first available position, then applying brake pedal to release shift lock. *tr
The driver side, three point seat belt assembly comes unlatched while the vehicle IS in motion. this IS even after the belt tongue IS in place, you hear a click from the latch closing and locking and the belt has been pulled on to test the connection. I took it to the dealership today and the attendant said that the seat belt latch was likely not working due to normal wear and tear. the vehicle IS 10 years old and has less than 200,000 miles and IS very much still drivable. the dealership tried to charge the vehicle owner over $300.00 for the repair and will not repair without payment. the seat belts should be guaranteed to work properly over the life of the vehicle. this IS not an expensive fix as very few people drive their cars over 120,000 miles as IS. *tr
While driving on the freeway the engine keeps constant speed even after removing foot from accelerator pedal. It's like a stuck throttle. The only way to stop it IS to apply brake and shift to neutral and stamp on the accelerator. Traffic had come to a stop and my engine was still revving at 3500 rpms pretty scary, only thing holding car back IS brakes. *tr
Started sudden acceleration while driving at 25 mph. Pressed hard on brakes to stop, put it on park mode. Still rpm was around 4000. Turned off engine. When cranked back, rpm kept on increasing without foot on accelerator. Tapped hard on accelerator couple of times, rpm went back to normal. *tr
TL* the contact owns a 2004 mercury sable. The contact stated that the vehicle surged forward and exhibited rapid accelerated. The vehicle was taken to an independent mechanic on several occasions, who was not able to replicate. The manufacturer was notified of the failure. The approximate failure mileage was 71,000.
While driving and I go over 50 mph my car will speed up which cause the throttle cable to come apart an d the engine or transmission speeds up. *tr
I received a panicked phone call from my 16 year old daughter after a life threatening experience. She was driving at 35 mph when the car began to accelerate on it's own, the engine raced to 4,000 rpm and stayed there, while she frantically pressed the brake. Thankfully she was able to contain control of the vehicle as she pulled off it the road. She immediately turned off the engine, after waiting a few minutes she started the car, again it raced to 4,000 rpm. After trying this multiple times I had the car towed home. a call to ford verified there has been no recalls or recall work done on this vehicle. I researched this issue online, to my amazement there are many people who have experienced this same issue.in fear for my child and anyone else who might drive this vehicle I have removed it from use, and feel stuck with unsafe vehicle. I am highly disappointed in the lack of response/resolve from the manufacture. *tr
Throttle gets stuck. this was repaired in february of 2009 and has occurred again now in october 2013. statement from ford dealership nov 4, 2013: speed control cable broken needs replace may be causing throttle linkage to bind. dealership indicates that a recall on the 2000-2003 mercury sables covers the exact repairs that are necessary on my vehicle but my vehicle IS not covered as it IS a 2004. contacted ford at 1-800-392-3673 and they are currently not willing to pay for repairs to my vehicle. *tr
TL* the contact owns a 2004 mercury sable. The contact stated that while traveling approximately 30 mph, the vehicle erroneously accelerated. The contact was able to merge to the shoulder and turn the vehicle off. The vehicle was taken to the dealer where it was found that the speed control cable had failed. The vehicle was repaired. The manufacturer was not contacted about the failure. The failure mileage was 76,794.
TL* the contact owns a 2004 mercury sable. The contact stated that the vehicle suddenly accelerated independently while the contact was sitting idle at a traffic stop. The vehicle lunged forward and the rpms increased before the sudden acceleration occurred. Failure was experienced several times. The vehicle was not taken to the dealer to have a diagnostic performed. The vehicle was not repaired. The manufacturer was made aware of the failure. The approximate failure mileage was 198,000 and the current mileage was 203,000.
Brake light switch at pedal faulty with same symptoms as recall nhtsa I.D. # 04v10600...brake lights won't activate when pedal depressed while driving or parked and when parked transmission range selector IS stuck in park position. these symptoms could cause an accident from the rear and or leave family members stranded. curiously this recall doesn't list the recalled switches part number and certainly ford motors won't admit that a few were installed on 2004 models. *tr
TL* the contact owns a 2004 mercury sable. The contact stated that while attempting to brake, the vehicle accelerated independently. The contact had not depressed the accelerator pedal. The contact had to shift into neutral and engage the brakes in order to stop the vehicle. The vehicle was not taken to the dealer. The manufacturer was not made aware of the failure. The vehicle was not repaired. The failure and current mileage was 82,000.
My mercury sable 2004 began accelerating on its own. The first time I was cruising at 35mph and had trouble stopping at a stop sign. Braking caused a vibration the rpm's were not going down. Driving further I noted the car would accelerate by itself. Tapping the the gas pedal quickly sometimes caused the rpm's to go back to normal. I took the vehicle to a local garage and had the throttle (cables, etc) checked. All were reported ok. The issue has happened off and on but yesterday (11/28/12) was the worst. I did some research and my issue IS exactly the unintended acceleration issue reported by many other taurus/sable owners. I have two children and am now concerned for my safety and the safety of my family. I contacted ford and got a case number assigned. I am waiting to hear back from them. *tr
NHTSA’s Office of Defects Investigation opened these reviews into vehicles including this one.
Preliminary Evaluation (PE)12-005 was opened to investigate allegations of speed control cables detaching from the throttle body and subsequently interfering with the throttle closing fully to the idle position in model year (MY) 2005 and 2006 Ford Taurus vehicles.The speed control cable, throttle body attachment arm (?nail head?) for the speed control cable, cable mounting bracket and cable routing for the MY 2005 and 2006 Ford Taurus are common to all MY 2004 through 2006 Ford Taurus and Mercury Sable vehicles equipped with either the 155 HP 3.0L 2-valve Vulcan engine or the 200 HP 3.0L 4-valve Duratec engine (the ?subject vehicles?). Figures 1 and 2 show the throttle body cam and speed control cable installed and a cable interference condition caused by contact between a detached cable and the ?nail head.?Ford?s assessment of the condition in incident vehicles noted that the interference conditions produced tended to be short in duration as the cable end tended to dislodge itself from the throttle body due to vibration, road loads or engine roll in addition to tapping the acceleration pedal.Ford inspected three incident vehicles and measured maximum throttle openings of 5.8% to 14.9%, resulting in engine speeds ranging from 1600 to 2200 rpm with the transmission selector in Drive.A Ford stack-up analysis of the speed control cable length from the attachment bracket to the throttle body indicated a maximum theoretical throttle opening of 16.4% that could result from the alleged defect. Engineers at the NHTSA Vehicle Research and Test Center (VRTC) inspected an incident vehicle to evaluate throttle positions and engine speeds that could result from the alleged defect and performed brake testing of a vehicle with the throttle stuck at the worst case throttle opening that could result from the condition.The VRTC vehicle inspection noted that, depending on the orientation of the detached cable end, the amount of throttle opening that could result from interference by a detached speed control cable end varied from 4.8% to 11.3%.VRTC brake testing of a MY 2006 Taurus with a Vulcan engine and the throttle held open at 16% found that, even with multiple brake applications, sufficient vacuum was available for the brake booster assist and the brake pedal efforts required to stop the vehicle did not increase significantly from normal operating conditions. ODI?s analysis of 100 complaints related to the alleged defect found that drivers were generally able to free the interference condition or safely brake to a stop without incident.Approximately one-third (32) reported that the stuck throttle condition was corrected with no action or by tapping the accelerator pedal while the vehicle was still moving, another third (34) reported braking to a stop with the vehicle in Drive prior to correcting the condition, and the remaining third (34) reported that the driver responded to the incident by shifting to Neutral before stopping the vehicle.One complaint alleged that stuck-throttle type symptoms caused the vehicle to pass partially through a traffic light and into an intersection before stopping, however,ODI was unable to contact the owner to verify the cause or relationship to the alleged defect condition.ODI has not identified any crashes related to the alleged defect. Tables 1 and 2 provide a breakdown of complaints and warranty claims related to the alleged defect by engine and model year.A safety-related defect has not been identified at this time and further use of agency resources does not appear to be warranted.Accordingly, this investigation is closed.The closing of this investigation do
On october 11, 2006, public citizen petitioned odi to investigate reports of engine stalls caused by E85 fuel in certain model year (my) 2003 - 2005 ford taurus flex-fuel vehicles (ffv). Odi's review of the petition and other available data found a low stall rate attributable to E-85 fueling and that the main concerns,prolonged engine start and rough idle during cold engine startup at winter temperatures, were resolved by an engine software update.to ensure that all subject vehicles receive this update, ford initiated a notification campaign to offer free engine computer recalibration.based on this information, this defect petition IS denied. This denial should not be construed as a finding that no safety defect exists.odi reserves the right to reconsider this issue if future data warrant.additional details can be found in the federal register notice posted in the dp06-005 public file.
Technical service bulletins and other communications the manufacturer sent dealers about this vehicle. Ask a dealer for the full document by its number.
Bars are owner complaints, dots mark years with recalls. Select a year to open its report.