Source reference 10285540
Owner complaint — 2000 GMC YUKON
Vehicles as recorded
- 2000 GMC YUKON This vehicle's overview →
Stated content
Sentences whose label could not be settled automatically are shown as "Original text (unclassified)". They are left this way rather than risk a wrong category.
Vehicle information
2000年型GMC YUKONの所有者。 Machine translation (unreviewed)
TL*THE CONTACT OWNS A 2000 GMC YUKON.
Go to this passage in the originalOriginal text (unclassified)
彼は、自分の車両は 60,000 マイル (= 96,561 km)のときにリコール# 05V379000(サービスブレーキ、油圧:アンチロック)に従って修理されたと述べた。 Machine translation (unreviewed)
HE STATED THAT HIS VEHICLE WAS REPAIRED ACCORDING TO RECALL# 05V379000 (SERVICE BRAKES, HYDRAULIC: ANTI LOCK) AT 60,000 MILES.
Go to this passage in the originalObserved symptom
105,000マイル (= 168,981 km)で不正なアンチロックブレーキシステム(ABS)作動が開始された。 Machine translation (unreviewed)
AT 105,000 MILES HE BEGAN EXPERIENCING UNWANTED ANTI LOCK BRAKE SYSTEM (ABS) ACTIVATION.
Go to this passage in the originalOriginal text (unclassified)
車両は以前に修理済みだったため、彼は無償の対策を受ける資格がなかった。 Machine translation (unreviewed)
SINCE THE VEHICLE WAS PREVIOUSLY REPAIRED, HE WAS INELIGIBLE FOR A FREE REMEDY.
Go to this passage in the originalOriginal text (unclassified)
車両が修理された後も、故障は起き続けた。 Machine translation (unreviewed)
THE FAILURE CONTINUED TO OCCUR AFTER THE VEHICLE WAS REPAIRED.
Go to this passage in the originalVehicle information
不正作動が発生した走行距離は105,000マイル (= 168,981 km)。 Machine translation (unreviewed)
THE FAILURE MILEAGE WAS 105,000.
Go to this passage in the originalVehicle information
現在の走行距離は114,000マイル (= 183,465 km)。 Machine translation (unreviewed)
THE CURRENT MILEAGE WAS 114,000.
Go to this passage in the original
Not found in this report
The following items were not found in the original text. What is not stated is treated as unknown.
- Inspection
- Reported cause
- Work performed
- Outcome
Classification is automated. Check the original text for anything missed.
Source
- Source
- NHTSA ODI Complaints
- Source reference
- 10285540
- Received by source
- 2009-09-28
- Incident date
- 2009-07-01
Open original text and sourceOpen the provider's page (external)