Quote:
Originally Posted by Petah78
My car with a build date of 04/22 still have the hyperflash problem so that is not resolved yet. As such, I doubt the QC hold in Jan/Feb was related. I have been reading more about this Jan/FEb QC hold, do you have more info about this?
|
Quote:
Originally Posted by Tcoat
The QC hold could have been just about anything. The most probable was that it was not to "repair" an issue but because they did not have all the parts to finish the vehicles at that time. There were thousands of vehicles waiting on QC hold and many more right this moment because they were waiting for needed parts.
|
Purely speculating: it's possible that the QC hold was in fact related and it was a stop production / stop sale order due to this discovered.
But after doing their bean counting they've decided the cost/risk is such that it's better for them to just sell the cars with the known manufacturing problem that might affect only a small % of a small total volume of cars produced, than to issue a recall and get bad PR.
Maybe they miscalculated ("My risk was calculated, but boy am I bad at math").
Or maybe they correctly guestimated that many of the early cars went to "enthusiasts" who are going to drive just hard enough to be able to deny warranty if needed; and the oil blockage/starvation is so much more likely to affect people who stay at the rev limiter for extended periods of time.
Also, a lot of early GR86s were automatics, and the AT doesn't like to go all the way to the rev limiter unless you're flooring it.
Quote:
Originally Posted by mycrors7
GR86's didnt start to touch America until January/February of 2022.
|
I know people who got their GR86's in December.
Quote:
Originally Posted by mycrors7
If it has to do with early production models, id expect early model BRZ's to have already had issues, which i havent heard of any
UNLESS subaru is sabotaging gr86's  |
You're assuming that all early cars had the same problem. It's possible that the earliest BRZs didn't have the problem, and then some robot got its calibration messed up, or they've "optimized" something incorrectly.