7 captured repliesPartial discussion capture · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHWeek of June 9 2023, evidently a bad week for 987s
Leading reported evidence
Replace stupid low number is exactly what they will offer
Performed · outcome unconfirmed
No successful repair reported for this finding.
0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that performed work without a confirmed outcome
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Performed · outcome unconfirmed
Unless something has changed a stupid low number is exactly what they will offer.
Week of June 9 2023, evidently a bad week for 987s
Read full discussion summary
Leading evidence: 'Replace stupid low number is exactly what they will offer' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Repair bills, upgrade receipts so we will have' (1 discussions). For that action, 0 discussions report a resolution and 0 report an unsuccessful attempt. No action has an explicit, attributable resolution report under the current rules. These are forum reports and suggestions, not a confirmed diagnosis.
Source reports, not a diagnosis or a success probability. Counts refer to discussions and can overlap.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that contain suggestions
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion · Original poster
Have full maintenance docs, repair bills, upgrade receipts so we will have to see how good an argument can be made.
Week of June 9 2023, evidently a bad week for 987s
Coverage and how to read this overview
Counts describe captured discussions, not unique people or a diagnosis. Author identities are not reliably stored. Exact duplicate evidence is counted once across matching discussions; one discussion counts at most once per action/state. Multiple repairs reported together remain a combination. Suggestions and failed attempts do not establish a fix. Matches cover whole discussions and can include related faults, model variants and incomplete threads.
7 eligible posts · 0 unverified posts · 1 discussions match the subject in their title or opening post.
Planet-9: 1 discussions
0 evidence records excluded for query context · 0 excluded by outcome qualification · 0 adjusted by outcome qualification.
0 acknowledgements have no verified action link; they do not establish a repair result.
Generation: 20261027T020439Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
Well just like
Apexhunter987
, two weeks ago was a really bad week for 987s. My 987 S, that I factory ordered and took delivery on Thanksgiving 2006, was totalled.
The story is really wild. Dropped the car off at a TiresPlus shop simply to have one tire pressure sensor replaced . Told them that it did not need programming but I did not tell them to not drive the car. ( Now you know where this is going)
Tech takes the car out for a spin to register the sensor and an idiot in a Telluride SUV decides to make a left turn into oncoming traffic. Result in the picture attached. (No one was hurt).
I found our several hours later when I called to see if my car was ready for pickup...
Never have had a car of mine totalled so I reached out to many. Had great advice especially from two very sympathetic Peachstate Porsche Club retired lawyer members. Have hired an appraiser who specializes in diminished value claims and, with evidence, argues for higher compensation on totalled vehicles. No doubt the Telluride's insurer (USAA) will offer some stupid low number. Have full maintenance docs, repair bills, upgrade receipts so we will have to see how good an argument can be made.
I really just kept the car for fun 3-4K miles per year. Wont be getting another Boxster until the EV verison comes out (2025?). Started looking at short term fun replacements and am leaning to a few years old 2-door Jeep Wrangler JL.
I'm beyond the anger, shock and numbness. Yes it's just a car, but it is and will be sorely missed.
Many years ago I was involved in an accident with a vehicle also insured with USAA. Unless something has changed a stupid low number is exactly what they will offer. I had to sue them and won more than I had originally asked plus attorney's fees. The downside was it took almost a year to settle. Best of luck
I'd ask that lawyer if there is any action you can take against the tire shop. I wouldn't let one drive my Ford. My cynical side says the tech wanted to drive a
Porsche
, there was no reason to do this, your
next
trip would have registered the sensor, in YOUR car.
