14 captured repliesPartial discussion capture · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCH987.2 DFI engine issues?
Reported or suspected cause
real and documented
Reported cause
No successful repair reported for this finding.
1
Identified cause
0
Suspected cause
0
Reported fixes
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 report identifying 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.
Reported cause
Obviously the IMS issue is real and documented, but in no way was it as bad as presented by some, the broad strokes used to paint the problem were border line dishonest.
Set me straight if i'm getting something wrong here
No successful repair reported for this finding.
0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context
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
This is the first time I read this and I have a strong feeling that this issue will be hyped to make new owners (new possible client base) nervous, while the perps hide behind the old rhetoric, "better be safe than sorry, send us your engine before it self destructs." Please, set me straight if I'm getting something wrong here.
Leading evidence: 'real and documented' (1 discussions report identifying this cause; no attributable repair resolution). Across 1 matching discussions, the most frequently mentioned possible cause is 'real and documented' (1 discussions; 1 report identifying it and 0 suggest it). The most frequently discussed action is 'Set me straight if i'm getting something wrong here' (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.
Set me straight if i'm getting something wrong here
Suggestion or failed attempt
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 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
This is the first time I read this and I have a strong feeling that this issue will be hyped to make new owners (new possible client base) nervous, while the perps hide behind the old rhetoric, "better be safe than sorry, send us your engine before it self destructs." Please, set me straight if I'm getting something wrong here.
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
now uses the 9a1 on every flat 6 powered production car from the base
These are separate views of the same evidence. Frequency alone does not establish a fix, and these counts must not be added together.
Set me straight if i'm getting something wrong here
No successful repair reported for this finding.
0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context
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
This is the first time I read this and I have a strong feeling that this issue will be hyped to make new owners (new possible client base) nervous, while the perps hide behind the old rhetoric, "better be safe than sorry, send us your engine before it self destructs." Please, set me straight if I'm getting something wrong here.
These are separate views of the same evidence. Frequency alone does not establish a fix, and these counts must not be added together.
real and documented
No successful repair reported for this finding.
1
Identified cause
0
Suspected cause
0
Reported fixes
Read evidence and context
Discussions that report identifying 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.
Reported cause
Obviously the IMS issue is real and documented, but in no way was it as bad as presented by some, the broad strokes used to paint the problem were border line dishonest.
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.
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: 20261026T124918Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
From the
986
forum with pics from Jake Ruby:
FRS DI issue - grass is not greener - 986 Forum - for Porsche Boxster Owners and Others
Has anyone heard of the kind of premature wear in the cylinder walls--or related issues--that was discussed with this particular 2012 CR?
Since I've got a 981S, I assumed most of the Porsche engine issues have been resolved with the introduction of the 9A1 motor..true?
Exactly. 'course some will blow this up to an inherent design flaw -- actually some already have on other boards but still offer "insurance" (for a tidy sum) to the scared... -- and have owners shaking in their boots over this.
Also, I wonder how the owner would have made out had he taken the car to the dealer? The car I think new enough to be covered under new car warranty.
Yep, I saw that and it seems reasonable on this particular car, however Jake went on:
"As we get evolve the 9a1 engines we have also found valve guide wear and other issues. We already have 3 years of development under our belts with the 9a1 DFI engines and the deficiencies are becoming more clear with each one. Others won't see these issues for 5-6 more years, more than likely."
Sounds like he thinks there are other issues with this motor; have there been any other reports? I haven't see a one...
Something's odd, guy has a car under warranty yet takes it to an independent and pays for it? Suddenly now the 9A1s are "troublesome," seems to me as the diminishing return on IMS equipped cars comes to the forefront, the 9A1 will be the new "scapegoat," the way I read these guys,
Porsche
is the only car company in the world that can't design and build engines, apparently
Porsche
engines require "help" from second hand shops to become reliable and functional. This is the first time I read this and I have a strong feeling that this issue will be hyped to make new owners (new possible client base) nervous, while the perps hide behind the old rhetoric, "better be safe than sorry, send us your engine before it self destructs." Please, set me straight if I'm getting something wrong here. Obviously the IMS issue is real and documented, but in no way was it as bad as presented by some, the broad strokes used to paint the problem were border line dishonest. I just hope we don't get a rash of 9A1-itis, no one has presented hard facts, who knows how case car was treated, at this point it's all speculation. I really hope this doesn't turn into a IMS-like scenario.
That's the guy who built my engine. People take their 9A1s to him so he can build them into 4.0L 9A1s. The issues are found when he disassembles the engine for rebuild.
Welcome to the Internet where any potential issue experienced by anyone becomes a design flaw and a cause of fear. I spent 7 yrs challenging people back on my 2006 cs engine and they still persist in spreading misinformation.
Good luck on establishing any sense of reality in this thread. Me, I'm going driving.
Agreed, I'm not saying Flat Six is unethical, in any way shape or form, in fact all I've read are good things, but why would you bypass your warranty and PAY for something that
Porsche
is responsible for and will pay? And like I asked, are these "issues" popping up on tracked cars, regular cars or being found as these cars are being modified? Again, most 9A1 engines are still under warranty, so why tear them down? Just honest questions.
Most of the pictures in this thread have been seen before. A Planet-9 member (I think "saildoc") is having his CR 3.4 motor punched out to 4.2 by Jake Raby.
The 9a1 has been out in the 987/
981
, 997/991 platforms since MY 2009. Essentially stock engines have been raced by privateers in Europe and the U.S. in a variety of venues including 24Hr races. The
Cayman
Interseries has tens of thousands of racing miles on these engines. I have not read of a single engine failure.
Porsche
now uses the 9a1 on every flat 6 powered production car from the base
981
to the 991 Turbo S and
GT3
.
If Mr Raby is correct, we should start to see trashed 9a1 engines starting to show up and with increasing regularity. If it is a design flaw, there is little anyone can do, including him. Until the engine carcasses start piling up, me thinks he's just stirring the pot.
I present to you the 991 GT3. They have reached a point where the engines are simply in need of replacement. Some cars have had 2-3+ engines in them... and we're talking 2015/2016 GT3s.
As someone stated, it would take years for the community to realize it, but the issues have come to roost.
How many 15-16 gt3's have engine replaced? - ******** Discussion Forums
(skip to page 101 for time's sake)