fullymatted.
Back to search
Pelican Parts

Fix the case and rebuild OR scrap the idea?

Add to repair workspace
Open repair workspace
Original source
5 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW

Discussion summary

YOUR RESEARCHFix the case and rebuild OR scrap the idea?

Leading reported evidence

Install took almost two months due

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

On the down side, it took some time (the process of just getting the Nickies installed took almost two months due to backlog), and was anything but cheap.

Original post Read captured discussion
Fix the case and rebuild OR scrap the idea?
Read full discussion summary

Leading evidence: 'Install took almost two months due' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Install took almost two months due' (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.

Read captured replies

1 matching discussions · 5 captured posts examined · 0 partial discussions

Frequently discussed actions (1)

These are separate views of the same evidence. Frequency alone does not establish a fix, and these counts must not be added together.

Install took almost two months due

No successful repair reported for this finding.

0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context
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

On the down side, it took some time (the process of just getting the Nickies installed took almost two months due to backlog), and was anything but cheap.

Original post Read captured discussion
Fix the case and rebuild OR scrap the idea?
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.

5 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: 20261027T013556Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources

POST 1 / ORIGINAL POSTEROriginal post

I tore down my M96 engine during this shutdown and found out the issue with the engine was a rod bolt that let go and sent the piston into the sleeve of the case. Or this was a classic D-chunk that went a little bit beyond normal. Is this case toast or can it be repaired (within reason) or should I just scrap the idea of being able to rebuild the engine? Thanks guys, Brian Video of the damage to the engine: https://youtu.be/h_2dEuj5efI

POST 2Original post

Quotes source post: 10846051

Depends upon your tolerance to financial distress. This engines are eminently repairable in the hands of the right machine shop. We have seen customer engines where parts from one cylinder ended up two cylinders over, and the engine is back on the road with a full set of Nickies, new rods, and aftermarket pistons; and is probably way more durable than when it left the factory. On the down side, it took some time (the process of just getting the Nickies installed took almost two months due to backlog), and was anything but cheap.

POST 4Original post

there is always that Porsche factory short block...

POST 5Original post

Quotes source post: 10866266

Porsche no longer offers many M96 engines, either as short blocks or complete; selling only bear cases at nearly $8K per. You can re sleeve the case with Nickies for less than that...............

This is a source reference. Confirm exact model applicability in the original material.