9 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHConfirmation of replacement engine?
Leading reported evidence
Replace before the at program
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
Lot's of problems with the early 3.4 litre engines, lots got replaced before the AT program.
Leading evidence: 'Replace before the at program' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Replace before the at program' (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 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
Instead of the production tear letter, it has AT in the series and can be used for a number of model years.
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
Could have been replaced with a wrecked donor car motor
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.
9 eligible posts · 0 unverified posts · 1 discussions match the subject in their title or opening post.
Pelican Parts: 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: 20261027T075545Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
My 1999 996 has a build date of 3/98. However, the engine is stamped with M96/0166X15601, indicating a 1999 manufacturing date for the engine.
The VIN analysis that I purchased from Stuttcars says the engine code should be M96/0166W08070. Can I take this, along with the above date discrepancy, as confirmation of a replacement engine?
If so, what am I to make of this? I thought all engines replaced under the auspices of an official recall or Porsche-approved replacement plan are stamped with an AT in the engine code.
Any analysis from the experienced crew here is appreciated.
Thanks. I'm thinking the scenario was something like that.
If it was a replacement engine installed "officially", so to speak, it would have the AT in the engine code, right?
The AT engines are the style with the non-serviceable IMS bearing, meaning that they are the same as the early 997’s. If the failure to the original engine came sooner than the development of the next gen engine, that could also explain the number discrepancy. Or, as explained in the earlier post, it could have been out of warranty and the owner may have purchased a used engine.
Ah, interesting. Thanks for the replies. I didn't realize the AT-stamped engines came later.
This is all very interesting, and I'm going to see if I can tell when the engine was replaced.
It is part of the engine serial number by the oil sump. If you look up engine numbers for a 996, you will find the series of number and letter designations for each year of production. Instead of the production tear letter, it has AT in the series and can be used for a number of model years.
This is a source reference. Confirm exact model applicability in the original material.
