14 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHCoil Over Install - Other bits to add?
Leading reported evidence
Replace (components and driving skills)
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
I think I need some seat time on a track to really determine what needs to be changed (components AND driving skills).
Leading evidence: 'Replace (components and driving skills)' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, the most frequently mentioned possible cause is 'alignment and/or me' (1 discussions; 0 report identifying it and 1 suggest it). The most frequently discussed action is 'Replace (components and driving skills)' (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 suspect a cause
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.
Suspected cause
I don't want to just throw hardware at it ( and $$) if the problem is alignment and/or me.
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 suspect a cause
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.
Suspected cause
The front end gets a little squirrelly when I'm on it in a turn so I suspect the conservative alignment to save tires (per PO) or worn/failed components are contributing.
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
You may have to change your line and apex to do it but that will be a good thing.
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
My my plan is to drop an inch, replace shocks and put in stiffer roll bars.
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.
Suspected cause
The front end gets a little squirrelly when I'm on it in a turn so I suspect the conservative alignment to save tires (per PO) or worn/failed components are contributing.
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.
14 eligible posts · 0 unverified posts · 1 discussions match the subject in their title or opening post.
Rennlist: 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: 20261026T112012Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
I'm looking at installing coil overs as my OEM suspension has 71k on it. It has H&R Lowering springs and ROW 30 suspension currently.
While I'm at this, is there anything else I should add such as adjustable toe-steer kit, etc? This car is 90% street with limited autocross and possibly a bit of track time in its future. However, I do drive pretty aggressively on the street.
Sorry, missed this. It will all depend on how far you lower it. If you stay within an inch or so of stock ride height and a street alignment you should be fine for now.
Extanker, what is the issue with coilovers on a DD? Too harsh of a ride? I am looking to take an inch or so out of ride height for a DD with 2-3 DE per year but don't want to compromise ride and have to invest in more hardware to correct geometry.
good question.
You can't make a generic statement like "don't go coilovers." I have coilovers on my BMW X5.
presumably he means the ride will be too harsh, but that really depends on spring rate, appropriate shock settings, alignment, ride height, etc.
As for coilovers affecting the alignment.....I'm not as well versed on the 996, but as slakker said I BELIEVE you can stay within stock alignment if you don't lower more than an inch (but I could be wrong)
Great question. I cannot imagine any coilover giving a harsher ride than the M030 suspension. My 996 is my DD and I am also planning to convert to coilovers - mainly for the track, but I expect more compliance on the street.
fyi, I don't think 71k miles is cause by itself to go from springs to full coilovers. My mechanic has a 996 and obviously works on them; his guidance was that Porsche suspensions tend to be very durable & replacing my shocks now would be purely elective given their behavior & how they look (no leaks, noise & great performance).
If and when you move forward keep us updated as it could help me when the time comes.
A street biased coilover like the bilstein pss9 or h&r street performance can provide a good ride on the street ( even a bit better than mo30 due to better rebound damping) and excellent track day performance .
If you slam it down you'll need adjustable drop links , but if about an inch lower than stock you might be fine with the stock ones .
You'll want to make sure all your bushes are in excellent shape and you could consider a set of bigger swaybars like eibach or h&r .
I did all this and my car had less than 40k on it , I found one shock was leaking and a couple bushes needed doing . Age not just miles degrades suspension systems.
The front end gets a little squirrelly when I'm on it in a turn so I suspect the conservative alignment to save tires (per PO) or worn/failed components are contributing.
My my plan is to drop an inch, replace shocks and put in stiffer roll bars. This is my daily so I don't want a stiff ride but the side to side transitions need to be stiffened up. Dampening seems spot on to me. I don't see the need to adjust ride height so thinking lowering springs are what I need. The wild card here is which will ride better. Oh, I will be doing occasional DE's but only for fun not comp. I really need to go ride in example cars it sounds like.
Focus on unwinding the wheel as you are adding power. You may have to change your line and apex to do it but that will be a good thing. Even with stock shocks that shouldn't make the front end squirrelly. But adding power with wheel lock on definitely will.
I think I need some seat time on a track to really determine what needs to be changed (components AND driving skills). I don't want to just throw hardware at it ( and $$) if the problem is alignment and/or me.
Smart thinking. Focus on the basic track stuff like X51 baffle, hi-temp brake fluid and racing brake pads. From there, I would recommend a set of scrub wheels and some NT01 or R888 tires. With this setup you can have a crazy amount of fun in these cars.
This is a source reference. Confirm exact model applicability in the original material.
