Skip to content
FaultCrate

This is an open preview: every record can be read without an account.

← Back to the vehicle

Manufacturer communication 03-08-61-002B — 2003 GMC YUKON ・ Source reference 2004-10-01

Snap or popping noise from the front of the vehicle: slot the crossmember mounting holes

Reporter type: Manufacturer

Vehicles as recorded

What the manufacturer’s document says

03-08-61-002B ・ fault and correction ・ names this vehicle

Applies to

  • 2003-2005 Avalanche, Suburban, Tahoe, Silverado, Yukon/XL, Sierra, Escalade: a snap or popping noise from the front of the vehicle.

    the passage
    2003- 2005 Avalanche, Suburban, Tahoe, Silverado, Yukon/XL, Sierra, Escalade – Snap/Popping Noise from Front of Vehicle

Correction

Repair

  • Slot the left side mounting holes on the front crossmember.

    the passage
    Slot left side mounting holes on front crossmember per bulletin.

Caution

  • Do not replace the crossmember. The reference bulletin is 03-08-61-002B.

    the passage
    Don’t replace crossmember. 03-08-61-002B

What is needed

Parts and materials
Not stated
Labor time
Not stated
Special tools
Not stated
Scan tool
Not stated

Only what the technical documents state. "Not stated" does not mean not needed.

Compiled by reading the full text of the document; each point stands on the passage shown. Check the document itself, linked below, before working on a vehicle.

Stated content

  1. Communication summary

    トラックの問題 – 最初の一回で正しく直す 2003- 2005 Avalanche、Suburban、Tahoe、Silverado、Yukon/XL、Sierra、Escalade – 車両前部からのパキッ/ポンという音 技術情報に従い、フロントクロスメンバーの左側の取付穴を長穴に加工する。 クロスメンバーを交換しないこと。 03-08-61-002B Machine translation (unreviewed)

    Truck Issues – Fix It Right The First Time 2003- 2005 Avalanche, Suburban, Tahoe, Silverado, Yukon/XL, Sierra, Escalade – Snap/Popping Noise from Front of Vehicle Slot left side mounting holes on front crossmember per bulletin. Don’t replace crossmember. 03-08-61-002B
    Go to this passage in the original

Source

Source
GM TechLink
Source reference
2004-10-01
Received by source
2004-10-01
Incident date
Unknown

Open original text and sourceOpen the provider's page (external)