There were no warning indicators illuminated. The contact stated that the air bag and wires were not exposed. The contact stated that the dashboard was cracked above the passenger side air bag. I own this truck from day 1 and always had tinted window and use windshield sun shade.Īlso has two cracks on both side of the instrument panel on the drivers side wiitch leaving it more reason to deploy. Dash and airbag support system cracked in multiple areas. Two cracks appeared on dashboard near air bag. I expressed my concerns as a huge safety issue and obvious defect.

The approximate failure mileage was 75, My dash cracked straight line above and attached to airbag, wasn't there, next day it was, Nov 38, mi. Neither the dealer nor the manufacturer was notified. The contact was able to perform a diagnostic test and located dtc code: Was-B The vehicle was not repaired. The contact stated that the air bag warning sensor was replaced, but failed to remedy the vehicle. The contact stated that the service air bag warning indicator illuminated, which was a safety concern. I have found cracks in the dash directly connected to the support braces for the passenger side air bag, in case of deployment the shards of broken plastic can impale into an individual causing injury or death - Pittsburg, CA, USA. The failure mileage was approximately 85, Dashboard is cracked in multiple places, potentially representing a safety threat if the passenger air bag deploys. B0081 CHEVROLET - Passenger Presence System The vehicle was not diagnosed or repaired. The dealer and manufacturer were not contacted. The contact owns a Chevrolet Silverado When the vehicle was started, the air bag and service air bag indicators illuminated. The crack now is going to expand due to vibration and it could effect the drivers side airbag down the line. Share on Facebook Retweet this page Email this page. Don't waste your time wasting ours! If you are interested in advertising a for-profit service, contact us. So how do you find out what problems are occurring? Any duplicates or errors? It's not us.

Driver side deployment loop open