"takata recall" while dealer has told me air bag was completed, it was sold to me with an open entry or questionable completion. Upon driving the car I found it felt shaky & was told they would fix any problems however now that I have taken it in twice and it has stayed there over a week, and then taken home (without my approval) by service manager, when I still complained that it doesn't feel so stable and maybe we should call off the deal or trade for another car, I was told.."deal is done, the car is yours, we've spent $$ to fix things". my response was "whatever items done were items that should have been done pre-sale and were agreed to be done". the axle ended up being bad and something still feels like the car staggers however I got tired of complaining. I'm not entirely sure that I'm driving a safe car and that it was not in an accident. Not sure what to do as now I owe a loan & have been driving car. My main concern has always been safety. I brought all this to the table pre purchase. I brought car in again because it was shaky, struggling & staggering to go up hill, would not properly accelerate, and was having a burnt smell. What they found was bad axle and something with rotor (which was not caught on first time I brought in that it spent a week there). Car fax did not indicate accident but drivability seems questionable. I bought car 12/31/17, brought back in first week to complete the open items (one being the air bag issue) I brought all concerns up pre-purchase w/agreement they would take care of all. I brought it in & it remained about a week. Picked up 01/13/18. Had to bring in again 01/30/18 due to staggering & burnt smell. Picked up 2/02/18 & when I brought up that I think we should just trade car as I felt maybe I got burned, they said: Car is yours, you bought it (in a nutshell). I have all emails of concerns brought up. Just want to be sure.

- Daly City, CA, USA

Takata recall. The contact owns a 2009 Honda Civic hybrid. The contact received notification of NHTSA campaign number: 16V346000 (air bags). The parts to do the repair were unavailable. The contact stated that the manufacturer exceeded a reasonable amount of time for the recall repair. The contact called the dealer (bob howard Honda at 13201 N kelley ave, Oklahoma city, ok 73131, (405) 753-8700) where it was confirmed that the parts were not available for the recall remedy. The manufacturer was not notified of the issue. The contact had not experienced a failure. Parts distribution disconnect.

- Oklahoma City, OK, USA

Takata recall" airbag light on, took to Honda dealer. Diagnostic found multiple stored fault codes: 32-10 front passenger; 11-10 drivers airbag, inflator saved and cleared codes. Fault still in 31-10. System worked when simulator used, when simulator was removed fault returned in passenger side airbag. Recommended to replace passenger side seat airbag. Part $597; labor $140. Really? customer declined. Honda dealer says no that if car in collision, no airbags will deploy. Is this true? is this the subject of the recall" please advise.

- Pleasant Hill, CA, USA

Takata recall. The contact owns a 2009 Honda Civic hybrid. The contact received notification of NHTSA campaign number: 16V346000 (air bags). However, the part to do the recall repair was unavailable. The contact stated that the manufacturer exceeded a reasonable amount of time for the recall repair. The manufacturer was not aware of the issue. The contact had not experienced a failure. VIN tool confirms parts not available. Updated 01/25/2017

- Carson City, NV, USA

Entered the vehicle, closed the door, turned on the ignition, started connecting my phone to the phone charger and the side airbags (curtain airbags) deployed while the vehicle was in park. Vehicle was not involved in an accident nor had any damage on the body. I have filed a claim with the insurance company, geico and the vehicle is being towed to the closest Honda dealer to examine the data event recorder to review the computer for defects...updated 12/11/14 updated 06/2/2015...updated 12/29/15 Honda found the inadvertent deployment was caused by an anomaly on micro chip inside the SRS control unit, resulting in a false detection of impact and incorrect instruction for deployment. The anomaly on the micro chip had become contaminated by a foreign substance during the wafer production process. The crash sensors did not have any anomalies. Updated 1/22/2015

- Silver Spring, MD, USA