← New search

2009 Mercury Sable

Owner reports · Recalls · Investigations

Fewer warning signs than most model years

Owner complaints for the 2009 Mercury Sable are lower than the model-year median of 201.

About this comparison →

How this year compares

Owner complaints by model year

Other model years Selected year
Compare all Sable years →

Counts vary with age, sales and reporting. They are not failure rates.

What owners reported most

All reported categories

Tap a category to read its complaints. One report may name several components.

When problems were reported

Mileage at the reported incident

Limited mileage data: 19 of 20 reports include usable mileage. There isn’t enough coverage to show a useful chart.

NHTSA’s mileage field refers to the reported incident, not necessarily the filing date. This shows report counts, not the likelihood of a failure.

What to inspect

Issues worth paying extra attention to based on owner reports.

  • Engine. Review the 5 owner reports in this category and discuss these concerns during a pre-purchase inspection. Read reports →
  • Vehicle Speed Control. Review the 5 owner reports in this category and discuss these concerns during a pre-purchase inspection. Read reports →
  • Power Train. Review the 3 owner reports in this category and discuss these concerns during a pre-purchase inspection. Read reports →

NHTSA owner reports · September 18, 2026 snapshot.

2 crash reports0 fire reports2 injury reports

Vehicle Speed Control complaints

5 reports
Clear category filter
22,300 miles · Jul 23, 2014
Service BrakesVehicle Speed Control

TL* THE CONTACT OWNS A 2009 MERCURY SABLE. WHILE PULLING INTO A PARKING SPACE AT 2 MPH, THE VEHICLE ACCELERATED ON ITS OWN. THE FAILURES OCCURRED INTERMITTENTLY FOR THREE YEARS. THE DEALER WAS UNABLE TO DUPLICATE THE FAILURES. THE MANUFACTURER WAS NOTIFIED. THE VIN WAS UNAVAILABLE. THE APPROXIMATE FAILURE MILEAGE WAS 22,300. …

Read full complaint

TL* THE CONTACT OWNS A 2009 MERCURY SABLE. WHILE PULLING INTO A PARKING SPACE AT 2 MPH, THE VEHICLE ACCELERATED ON ITS OWN. THE FAILURES OCCURRED INTERMITTENTLY FOR THREE YEARS. THE DEALER WAS UNABLE TO DUPLICATE THE FAILURES. THE MANUFACTURER WAS NOTIFIED. THE VIN WAS UNAVAILABLE. THE APPROXIMATE FAILURE MILEAGE WAS 22,300. UPDATED 9/4/14*CN THE CONSUMER STATED WHEN AN INCIDENT WOULD OCCUR THE VEHICLE HAD NO BRAKES UNLESS PUT IN NUETRAL. THE ACCELERATION MAINTAINED THE CURRENT SPEED. FOR THE PAST 39 MONTHS THE OWNER HAD BEEN DRIVING WITH ONE HAND ON THE SHIFTING LEVER TO BE ABLE TO STOP. UPDATED 1/5/2014 *JS

NHTSA ODI #10615574

22,300 miles · Jul 23, 2014
Vehicle Speed Control

TL* THE CONTACT OWNS A 2009 MERCURY SABLE. WHILE PULLING INTO A PARKING SPACE AT 2 MPH, THE VEHICLE ACCELERATED ON ITS OWN. THE FAILURES OCCURRED INTERMITTENTLY FOR THREE YEARS. THE DEALER WAS UNABLE TO DUPLICATE THE FAILURES. THE MANUFACTURER WAS NOTIFIED. THE VIN WAS UNAVAILABLE. THE APPROXIMATE FAILURE MILEAGE WAS 22,300.

NHTSA ODI #10615571

37,565 miles · May 27, 2014
EngineVehicle Speed Control

IN CRUISE CONTROL--SPEED SET BETWEEN 37 & 39 MPH I ENGAGED BRAKES TO SLOW CAR--ENG STOPPED RUNNING --ALL LITES ON CONSOLE LIT..LOST PWR BRAKES AND STEERING. ALMOST HIT CAR COMING IN OPPOSITE DIRECTION. HAPPENED AGAIN IN APRIL, 2014 PLAZA LINCOLN CANNOT FIND PROBLEM--SCALES FORD CANNOT FIND PROBLEM--SEVERAL INDEPENDENT PROFE…

Read full complaint

IN CRUISE CONTROL--SPEED SET BETWEEN 37 & 39 MPH I ENGAGED BRAKES TO SLOW CAR--ENG STOPPED RUNNING --ALL LITES ON CONSOLE LIT..LOST PWR BRAKES AND STEERING. ALMOST HIT CAR COMING IN OPPOSITE DIRECTION. HAPPENED AGAIN IN APRIL, 2014 PLAZA LINCOLN CANNOT FIND PROBLEM--SCALES FORD CANNOT FIND PROBLEM--SEVERAL INDEPENDENT PROFESSIONAL MECHANICS CANNOT FIND PROBLEM--NO COMPUTERS WILL IDENTIFY PROBLEM--I'M AFRAID TO DRIVE CAR 32159,,I HAVE REPORTED THIS TO FORD MOTOR CO AND NTSB. NEED HELP --PLEASE *TR

NHTSA ODI #10594418

Mileage unknown · Oct 12, 2012
Vehicle Speed ControlCrashInjury

TL* THE CONTACT OWNS A 2009 MERCURY SABLE. THE CONTACT STATED THAT WHILE ENTERING A PARKING SPACE, THE RPMS INCREASED EXCESSIVELY AS THE VEHICLE SUDDENLY ACCELERATED, CAUSING THE CONTACT TO CRASH INTO A CURB AS THE VEHICLE WENT AIRBORNE. THE VEHICLE LANDED IN AN EMBANKMENT AND THEN STALLED. A PASSENGER SUSTAINED HEAD INJURIES AS…

Read full complaint

TL* THE CONTACT OWNS A 2009 MERCURY SABLE. THE CONTACT STATED THAT WHILE ENTERING A PARKING SPACE, THE RPMS INCREASED EXCESSIVELY AS THE VEHICLE SUDDENLY ACCELERATED, CAUSING THE CONTACT TO CRASH INTO A CURB AS THE VEHICLE WENT AIRBORNE. THE VEHICLE LANDED IN AN EMBANKMENT AND THEN STALLED. A PASSENGER SUSTAINED HEAD INJURIES AS A RESULT. THE VEHICLE HAD NOT YET BEEN DIAGNOSED FOR THE ACCELERATOR FAILURE. THE VEHICLE WAS REPAIRED FOR THE BODY DAMAGE. THE VIN WAS UNAVAILABLE. THE FAILURE MILEAGE WAS UNKNOWN.

NHTSA ODI #10479864

50,000 miles · Oct 11, 2012
Vehicle Speed ControlCrashInjury

TL* THE CONTACT OWNS A 2009 MERCURY SABLE. THE CONTACT STATED THAT WHILE ATTEMPTING TO PARK, THE VEHICLE SUDDENLY ACCELERATED, CRASHING INTO AND EMBANKMENT AND CONTINUING INTO A GOLF COURSE. THE CONTACT SUSTAINED LACERATIONS FROM THE CRASH. THE FRONT PASSENGER'S HEAD IMPACTED THE WINDSHIELD, RESULTING IN A CONTUSION. IN ADDITION…

Read full complaint

TL* THE CONTACT OWNS A 2009 MERCURY SABLE. THE CONTACT STATED THAT WHILE ATTEMPTING TO PARK, THE VEHICLE SUDDENLY ACCELERATED, CRASHING INTO AND EMBANKMENT AND CONTINUING INTO A GOLF COURSE. THE CONTACT SUSTAINED LACERATIONS FROM THE CRASH. THE FRONT PASSENGER'S HEAD IMPACTED THE WINDSHIELD, RESULTING IN A CONTUSION. IN ADDITION, THE PASSENGER SUSTAINED LACERATIONS AND BRUISES TO THE ARMS AND LEGS. A POLICE REPORT WAS FILED. THE VEHICLE WAS TAKEN TO THE DEALER. THE MANUFACTURER WAS NOT MADE AWARE OF THE FAILURE. THE VEHICLE WAS NOT REPAIRED. THE FAILURE AND CURRENT MILEAGE WAS 50,000.

NHTSA ODI #10479839

Official recalls

0

No recalls in this snapshot.

Model-level recall history does not show whether a particular VIN is affected or has received a repair. Check a VIN with NHTSA ↗

NHTSA investigations

0

No exact-year investigations in this snapshot.