We found the following complaints for MERCURY SABLE (2004)
Read complaints for MERCURY SABLE (2004)
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.
Side impact on a 2004 sable. No airbags deployed. Driver sustained severe injuries including scapula fracture and pneumothorax, pneumomediastinum and subcuaneous air tracking, along with head wounds/lacerations. Patient required icu and multiple ct scans along with x-rays. Passenger airbag also did not deploy causing injury to passenger from seat belt and bounce-back from hitting the door secondary to airbag failure to deploy.
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.
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?
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!
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.
2004 mercury sableheadlights go out and immediately come back on.this has happened four times,in complete darkness, each time in a cold vehicle in the morning within 3 miles of home.three of these events occurred in relation to stopping, starting , or turning at stop sign. One event occurred at highway speed on straight hardtop road. Vehicle is under warranty and has been tested by the dealership where it was purchased and they were unable to find a mechanical or electrical cause.
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.
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.
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.
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.
While driving to work, i smelled burning plastic.i rolled up the window thinking it was another vehicle.a few minutes later i noticed an odd melting look on the rear windshield, and a stronger burning plastic smell.immediately i turned off the rear defrost, and cracked the window to let the fumes escape.approximately a mile later (while driving 70 mph) the rear windshield exploded.the glass initially stayed intact, but prior to me driving to the closest dealership (3 miles from that point), the shards began falling into the back seat of the vehicle.i am grateful there was no one in the back seat.
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.
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.
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!
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?
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.
I have a 2004 sable and the brake lights will not go off.i've tried changing the fuse to no avail.after researching, it seems that the 2000-2003 ford taurus and mercury sables had recalls for faulty brake light switches.it appears that this is still a problem in the 2004 model!
I have a 2004 sable and the brake lights will not go off.i've tried changing the fuse to no avail.after researching, it seems that the 2000-2003 ford taurus and mercury sables had recalls for faulty brake light switches.it appears that this is still a problem in the 2004 model!
2004 mercury sableheadlights go out and immediately come back on.this has happened four times,in complete darkness, each time in a cold vehicle in the morning within 3 miles of home.three of these events occurred in relation to stopping, starting , or turning at stop sign. One event occurred at highway speed on straight hardtop road. Vehicle is under warranty and has been tested by the dealership where it was purchased and they were unable to find a mechanical or electrical cause.
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.
Dt*: the contact stated the vehicle failed to start on the first 4 to 5 attempts. Later while traveling at 70 mph, the vehicle lost all power, stalling the engine. The vehicle was towed to the service dealer for repair. The service technician determined the vehicle would have needed to be in an accident to cause the inertia switch to be tripped. The switch was reset and the vehicle was restarted. The manufacturer was alerted.updated 8/16/2006 - there had been no accident.
This complaint concerns a 2004 mercury sable stationwagon.it was purchased 5 days before the incident.i was driving in rural poway on august 3, 2004.i apparently drove over a pebble or something - i heard a "thunk" under the car.almost immediately the car lost power, and came to a complete stop a few feet later.apparently the problem was that the fuel line and/or fuel pump were injured.and most of a tankful of gas spewed out into the road.i managed to get out of the car safely, this time.no one hit the car, this time.no fire resulted from all of that gasoline, this time.but i'm bothered by two things: 1)is the fuel line, and/or fuel pump, so exposed and so fragile that a pebble will cause mayhem in the system?2)is there any way to get a more gradual stopping of the car, so as to get further out of traffic than i was able to?this, as i see it, is bad engineering.i should add, in case you are wondering - i'm not a ditzy teenager.i'm a 54 year old woman, and up to now a pretty good driver.
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.
Without warning i experienced a loss of power with my 2004 mercury sable. After driving my car approximately 46 miles (i live 47 miles from job) i came to a stop sign and when i went to proceed through the stop sign, i was not able to do so. I had lost forward and reverse gears and the car would not move. There were no warning signs. No slipping, no banging, no grinding or any other noises that almost always are associated with transmission failure. I had the car towed to a transmission shop (aamco of mineola, ny) and the transmission was replaced. I never in all my 32 years of driving had a transmission fail in the manner that this transmission did. I also truly felt it was a torque converter or input shaft failure but i am not a mechanic (i do have a good knowledge of how a car and it's components work) and just decided to get the transmission fixed. I did not think much about this until i received a notice that my ford freestar is involved in a recall (11s25/nhtsa recall 12v-006) which described the same failure. It just so happens that it is also a model year 2004 and is equipped with the same model transmission (ax4s). I am now very confident that the transmission's torque converter failed just as it is described in the recall for my ford freestar. I believe that there is a design problem with the splines in the torque converter when it is manufactured and a possible failure of the input shaft (which the torque converter spins on).
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.
The contact owns a 2004 mercury sable. The contact stated that while driving approximately 65 mph, the vehicle stalled without warning. The vehicle was towed to a local mechanic where a diagnostic was performed, which located the failure at the transmission. The transmission was replaced. The manufacturer was made aware of the failure. The failure and the current mileage was 58,000.
The contact owns a 2004 mercury sable. The contact stated while driving 8 mph the vehicle suddenly stopped and it would not accelerate or move. The contact mentioned that no warning lamps illuminated. The vehicle was taken to the dealer who diagnosed that the transmission was defective and needed to be replaced. The manufacturer was not made aware of the failure. The vehicle was not repaired. The failure and current mileage was 59,000.
The contact owns a 2004 mercury sable. The contact stated that while driving 65 mph, the vehicle stopped accelerating. The contact was able to safely coast to a stop. The vehicle was then towed to an independent repair shop and the contact was informed that the transmission needed to be replaced. The vehicle was in the process of being repaired. The manufacturer was not made aware of the failure. The failure mileage was 155,000.
2004 mercury sable ls premium with dohc v-6 automatic engine. Bad slippage occurs when reverse is engaged with the transmission being warm. Only occurs when the transmission is warm. Mileage is currently at 61,000. Vehicle was purchased in 2007 with 48,000 miles with full factory warranty. I notified ford.mercury. Because the car is now out of warranty, they wont do a fix ... Only under the full cost of rebuilding or replacing the transmission.
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.
My complaint is for a 2004 mercury sable sl prem wagon with a 4f50n transmission.it has approx 18500 miles. While driving close to home, the dash 'transmission' light came on, but almost instantly went off.i called the dealer, who i use for maintenance and repair. They advised it might have been a fluke or nothing, to see what happened next time.the next day i backed the car out of my driveway,no light came on.i started to drive,the hill, the light came on and immediately the car stopped moving forward.we had it towed to the dealer and have been told the transmission is bad, that it must be replaced at a cost to us of over $3,000.this transmission failed withoutexpectation and suddenly.if this had happened in traffic, i could have had a serious accident.vehicle is at the dealer. This seems to fit in with the problems indicated in nhtsa action no. Ea09016.
While driving home at 11pm on september 2, 2006 my car stopped moving as i was making a left-hand turn. The engine was running, the electrical system was in order; the car simply would not move. Luckily, i was able to coast across the road and stop the car in a safe location. As i live in a rural area, the road was empty or i could have been seriously injured. I walked to a nearby bar where i called aaa to come and tow the car. I had the car towed to my home, then after my husband determined it was a serious problem, we had the car towed to the dealership where we purchased it the previous march. The mechanic determined that the transmission was shot and needed to be completely replaced! i was shocked as i had serviced the transmission as recommended at 35,000 and the vehicle only had 52,000 on it.
While the consumer wasparking the vehicle, it inadvertently went into reverse and subsequently the consumer vrashed into the garage.
Vehicle jumps forward about 3 feet when it is started. Occasionally, the same problem occurs when idling.
The contact owns a 2004 mercury sable. The contact stated that the internal steel cable of the front passenger seat belt fractured and resulted in the seat belt becoming inoperable. The vehicle was taken to an authorized dealer for inspection but was not repaired. The failure mileage was approximately 107,000.
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.
Side impact on a 2004 sable. No airbags deployed. Driver sustained severe injuries including scapula fracture and pneumothorax, pneumomediastinum and subcuaneous air tracking, along with head wounds/lacerations. Patient required icu and multiple ct scans along with x-rays. Passenger airbag also did not deploy causing injury to passenger from seat belt and bounce-back from hitting the door secondary to airbag failure to deploy.
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).
Dt*:the contact stated while driving 35 mph the vehicle was hit from behind.when the vehicle was hit, the driver seat fell backwards and bent to the left side.the occupant was wearing a seatbelt and was injured receiving compression fractures in the spine.the vehicle was towed to a local body shop which determined the vehicle was totaled.
Dt*:the contact stated while driving 35 mph the vehicle was hit from behind.when the vehicle was hit, the driver seat fell backwards and bent to the left side.the occupant was wearing a seatbelt and was injured receiving compression fractures in the spine.the vehicle was towed to a local body shop which determined the vehicle was totaled.
Dt: consumer's vehicle was rear ended.wife was in passenger seat, and the seat back broke of bucketon left of seat, causing wife toturn slightly toward the driver.
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.
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.
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).
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.
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 offit 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.
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.
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.
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!
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?
My husband is currently leasing a 2004 mercury sable.we've had it since february of 2008, and it's almost paid off.we've noticed the rotors are warped and are causing the car to shake when the brakes are pressed to come to a stop.it does it everytime and it has done it since the second week of april 2010.no parts have been replaced, but when we test drove it before we bought it, it didn't do that at all.
Over the last few years i have had the problem of when braking the car speeds up and i would have to slame the brakes on so i would not rear end the person in front of me.i kept thinking it was something i did but after seeing report today i sure it was nothing i did. Glad to see that the 2004 sable was now added. Will be callinf ford today....
2004 mercury sable front brake rotors were warped.***no answer required***. *mrthe consumer request a written response to a letter he submitted to nhtsa on august 30, 2005.
While driving to work, i smelled burning plastic.i rolled up the window thinking it was another vehicle.a few minutes later i noticed an odd melting look on the rear windshield, and a stronger burning plastic smell.immediately i turned off the rear defrost, and cracked the window to let the fumes escape.approximately a mile later (while driving 70 mph) the rear windshield exploded.the glass initially stayed intact, but prior to me driving to the closest dealership (3 miles from that point), the shards began falling into the back seat of the vehicle.i am grateful there was no one in the back seat.
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.
The problem started with the smell of something burning coming through the air vents. This happens only on ocassion and when then vehicle slows down or is stoped. I recently have seen smoke coming from the vents with the smell. And more recently smoke coming from under the hood. Upon investigation i could not see any burning or smoke. The dealer so far has not been able to find the problem i'm afraid it may lead to a car fire or health problems from the polluted air entering the vehicle
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.
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.
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.
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 offit 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.
I noticed that the car did not decelerate when i removed my foot from the gas pedal. When i braked, the engine continued to race. I put the car in neutral and i could hear the engine race even faster. At the light i kept it in neutral and gave it gas while braked. Then it went back to normal idle speed. It has done this several times since that first incident. Previous to that first incident, i noticed that the cruise control no longer worked.
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.
Throttle got stuck and car continued to accelerate on its own and now its a constant problem every time i drive the car i can get it to stop momentarily by quickly applying pressure to the gas pedal where it will stop accelerating for a moment but once the rpms drop as low as they are going to go it starts accelerating all over again when in park it revs out at up to 5000 rpmsi know you are already aware of this problem in the 05 & 06 models but i haven't seen anything about 04's also everything i've researched says its the cruise control cable being disconnected which was the first thing i checked and mine is still connected.
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.
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.
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.
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.
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.
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.
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.
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.
The contact owns a 2004 mercury sable. The contact stated that while approaching a stop sign at 50 mph, she heard an abnormal pop. The engine rpm's increased to 4000 while the contact was applying extreme pressure to the brakes. The contact coasted off the roadway and shut off the vehicle. Once restarted, the vehicle abnormally accelerated to 50 mph.the contact stated that the accelerator pedal was not being depressed. The vehicle was taken to the dealer where they advised her that the cruise control cable was fractured and caused the throttle to become jammed. The vehicle was repaired by having the cruise control cable disconnected. The failure mileage was approximately 61,000. Updated 3/2/12
The contact owns a 2004 mercury sable.the cowl on the windshield has become warped and is failing.the failure allows water to leak into the vehicle.the weather caused the failure and the cowl has been previously replaced twice.the dealer stated that the contact would have to pay for any future repairs.the failure mileage was 25,000 and current mileage was 27,000.
Read more
