Mercury Sable 2004

• Recall 116662 [USA]: A damaged or broken brake disc may reduce a vehicle's braking power, increasing the risk of a crash.
  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, manufactured october 1, 2014, to october 31, 2015 are intended for use on 2001-2007 ford taurus, 2001-2005 mercury sable, 1995-1999 ford taurus sho, 1995-2002 lincoln continental, and 1993-1998 lincoln mark viii vehicles. The brake pad shim may shift out of position causing the shim to contact the brake disc resulting in damage to the disc.
  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.
  owners may also contact the national highway traffic safety administration vehicle safety hotline at 1-888-327-4236 (tty 1-800-424-9153), or go to www.Safercar.Gov.

  Show Content

• Recall 54997 [USA]: The seat may not perform as intended during a crash which could increase the risk of injury.
  Certain passenger vehicles equipped with power adjustable seats may have been inadequately welded.
  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.
  customers can also contact the national highway traffic safety administration auto safety hotline at 1-888-dash-2-dot (1-888-327-4236).

  Show Content

To ensure accuracy and for your safety, it is recommended to do a free VIN recall check here or here [USA] - UK - Canada.

Bulletins are notices put out by manufacturers in conjunction with the NHTSA to notify the public of manufacturing issues or changes.

• Stuck throttle investigation # PE12005

  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 does not constitute a finding by nhtsa that a safety-related defect does not exist.The agency will monitor this issue and reserves the right to take further action if warranted by the circumstances.
  

  Show Content

• Engine stalling ffv investigation # DP06005

  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). Odis 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.
  

  Show Content

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.

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.

Common OBD-II Error Codes

• P2195 [2] O2 Sensor Signal Stuck Lean Bank 1 Sensor 1
• P0133 [1] 02 Sensor Circuit Slow Response (Bank 1 Sensor 1)
• P1131 [2] Throttle Position (Narrow Range) Sensor Circuit Malfunction
• P2197 [1] O2 Sensor Signal Stuck Lean Bank 2 Sensor 1
• P0171 [1] System too Lean (Bank 1)
• P0174 [1] System too Lean (Bank 2)
• P1151 [1] Fuel Restriction Indicator Circuit Malfunction
• P0732 [1] Gear 2 Incorrect ratio
• P0300 [2] Random/Multiple Cylinder Misfire Detected
• P2196 [1] O2 Sensor Signal Stuck Rich Bank 1 Sensor 1
• P2198 [1] O2 Sensor Signal Stuck Rich Bank 2 Sensor 1
• B1884 [1] PAD Warning Lamp Inoperative
• P2067 [1] Fuel Level Sensor "B" Circuit Low
• P0462 [1] Fuel Level Sensor Circuit Low Input