Components - Details | |
---|---|
NHTSA Complaint Number: 006118732 | Incident Date: Oct, 31 2006 |
Consumer's City: ARLINGTON | Consumer's State: MA |
Vehicle Transmission Type: MAN | Manufacturers Name: BMW of North America, LLC |
Model Name: R1200 GS | Model Year: 2005 |
Vehicle Involved in a Crash: No | Component's Description: Service brakes, hydraulic |
Vehicle Involved in a Fire: No | Persons Injured: 0 |
Vehicle's VIN#: | Date added to File: May, 23 2021 |
Date Complaint Received: Sep, 08 2007 | Complaint Type: IVOQ |
Incident Reported To Police: No | Purchase Date: - |
Was Original Owner: Yes | Anti-lock Brakes: Yes |
Number of Cylinders: 2 | Date of Manufacturer: - |
Was Vehicle Towed: - | Description of the Complaints: Rear brake pads wear out prematurely, typically in 6000 miles, as opposed to typical pad life which is ~18-24000 miles. no symptoms were noted previous to the brake pads wearing out. when rear brake pads wear out, there is loss of rear braking ability. this did not cause an accident for me, but could easily catch a rider by surprise and cause a crash as a result of loss of rear brake. bmw claims that this is normal for these bikes, and therefore nothing was done to fix the actual problem, aside from having the owner pay and have new brake pads installed. the problem seems to be caused by the linked brake system employed on the r12gs / abs model. with this system, using the front brake also causes the rear brakes to be actuated. somehow the system in at least some cases causes the breaking force applied to front and rear brakes to be biased to use the rear brake very heavily. a symptom of the problem is that the rear brake rotor is very hot (indicating that the rear brake has been actuated) even when neither brake levers have been employed by the rider. this problem has happened very often. at least to me once, personally. i've also read many many firsthand stories about this problem on various web forums such as advrider.com, ukgser.com and bmwmoa.org. i am unsure of the exact time that this occurred to me but can find records to pinpoint the exact date. *jb |