← New search

2008 Suzuki Boulevard C50

Owner reports · Recalls · Investigations

Limited comparison data

There is not enough comparable history to draw a useful model-year comparison.

About this comparison →

How this year compares

Owner complaints by model year

Other model years Selected year
Compare all Boulevard C50 years →

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

What owners reported most

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: 3 of 3 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.

  • Electrical System. Review the 1 owner reports in this category and discuss these concerns during a pre-purchase inspection. Read reports →
  • Engine And Engine Cooling. Review the 1 owner reports in this category and discuss these concerns during a pre-purchase inspection. Read reports →
  • Power Train. Review the 1 owner reports in this category and discuss these concerns during a pre-purchase inspection. Read reports →

NHTSA owner reports · September 18, 2026 snapshot.

1 crash reports0 fire reports1 injury reports

What owners actually said

3 reports
2,200 miles · Sep 23, 2018
Electrical SystemVehicle Speed Control

SPEEDOMETER CABLE WAS FOUND CHAFFING AGAINST THE FRONT BRAKE ROTOR. THE RESULT CAUSED A SHORT ELECTRICAL SYSTEM FOR THE SPEED. MOTORCYCLE WOULD GIVE INACCURATE READING (150 MPH, WHEN DOING 30.) SPEEDOMETER CABLE NEEDS TO BE THICKER AND SECURED AWAY FROM THE FRONT ROTOR, OR HAVE A SHIELD AROUND IT TO COMPLETELY PREVENT IT FROM RU…

Read full complaint

SPEEDOMETER CABLE WAS FOUND CHAFFING AGAINST THE FRONT BRAKE ROTOR. THE RESULT CAUSED A SHORT ELECTRICAL SYSTEM FOR THE SPEED. MOTORCYCLE WOULD GIVE INACCURATE READING (150 MPH, WHEN DOING 30.) SPEEDOMETER CABLE NEEDS TO BE THICKER AND SECURED AWAY FROM THE FRONT ROTOR, OR HAVE A SHIELD AROUND IT TO COMPLETELY PREVENT IT FROM RUBBING AGAINST THE ROTOR.

NHTSA ODI #11130815

26,000 miles · Apr 23, 2014
Power Train

GEAR TEETH ON ATTACHMENT POINT OF DRIVE SHAFT AND FINAL DRIVE COUPLER STRIPPED OUT SHIFTING BETWEEN FIRST AND SECOND GEAR. REMOVAL OF OIL SEAL SHOWED THE WORN TEETH WITH NO LUBRICATION PRESENT. PART NOT LISTED AS USER SERVICEABLE. *TR

NHTSA ODI #10584518

21,373 miles · Oct 17, 2012
Engine And Engine CoolingCrashInjury

I WAS SLOWING DOWN FOR A TRUCK THAT WAS TURNING AHEAD OF US. SHORTLY AFTER INITIATING THE SLOWING DOWN, MY HANDLEBAR STARTED TO WOBBLE VIOLENTLY. I TRIED HARD TO CONTROL THE WOBBLE, BUT I COULDN'T AND THE BIKE AND I WENT DOWN. A RIDER WAS BEHIND ME NOTICED THAT MY REAR WHEEL LOCKED UP AND THE BIKE DIED. MY BIKE HAD LOUD PIPES AN…

Read full complaint

I WAS SLOWING DOWN FOR A TRUCK THAT WAS TURNING AHEAD OF US. SHORTLY AFTER INITIATING THE SLOWING DOWN, MY HANDLEBAR STARTED TO WOBBLE VIOLENTLY. I TRIED HARD TO CONTROL THE WOBBLE, BUT I COULDN'T AND THE BIKE AND I WENT DOWN. A RIDER WAS BEHIND ME NOTICED THAT MY REAR WHEEL LOCKED UP AND THE BIKE DIED. MY BIKE HAD LOUD PIPES AND HE SAID IT JUST WENT SILENT. MY FOOT WAS NOT ON THE REAR BRAKE WHEN THE TIRE LOCKED UP. I DIDN'T NOTICE INITIALLY THAT THE BIKE WASN'T RUNNING DURING THE MISHAP BECAUSE I WAS SO FOCUSED ON TRYING TO KEEP THE BIKE UPRIGHT. I DID NOTICE WHEN THE BIKE WAS SLIDING AWAY FROM ME THAT IT WAS SILENT, AND THEREFORE TURNED OFF. THE ENGINE KILL SWITCH WAS NOT ACCIDENTALLY HIT AND THERE WAS PLENTY OF GAS. THE BIKE SHOP THAT RECEIVED THE BIKE THINKS THERE IS EXCESSIVE LASH IN THE UPPER GEARS. THE BIKE WAS TOTALED AND I LEFT THE ACCIDENT WITH INJURIES. *TR

NHTSA ODI #10480853

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.