fullymatted.
Back to search
Planet-9

Flames out the exhaust!

Add to repair workspace
Open repair workspace
Original source
4 captured repliesPartial discussion capture · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW

Discussion summary

YOUR RESEARCHFlames out the exhaust!

Leading reported evidence

Check oil level and it reported it

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

Later as the car sat in the paddock he checked the oil level and it reported it to be OK.

Flames out the exhaust!
Read full discussion summary

Leading evidence: 'Check oil level and it reported it' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Check oil level and it reported it' (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 · 4 captured posts examined · 1 partial discussions

Compare 1 other evidence results

Replace air oil separator

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

I explained to him about the AOS issues, that perhaps it was a 1-time event, but if it recurred he may have to replace the AOS.

Flames out the exhaust!
Frequently discussed actions (2)

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

Check oil level and it reported it

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

Later as the car sat in the paddock he checked the oil level and it reported it to be OK.

Flames out the exhaust!

Replace air oil separator

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

I explained to him about the AOS issues, that perhaps it was a 1-time event, but if it recurred he may have to replace the AOS.

Flames out the exhaust!
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.

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

POST 1Original post

I was at a PCA DE at Gingerman Raceway this past weekend, where one of participants with a 2007 CS with 90K miles on clock had a bit of an "interesting" experience. First issue, which I assume was minor, was he had the notorious cloud of white smoke upon start-up for the 2nd or 3rd session of the day. I explained to him about the AOS issues, that perhaps it was a 1-time event, but if it recurred he may have to replace the AOS. Thankfully the problem did not recur. But what did happen was this: near the end of his next session coming down the front straight he heard a strange grinding noise and the oil low pressure indicator came on, so he coasted off track and killed the ignition. He sat for 10 seconds or so, and then tried to restart the engine, and a huge ball of flame came out the tail pipe. To those of us watching from the paddock area it looked like a flame thrower - a good 2 feet of flame I would guess. Needless to say he didn't try starting it any more and, was towed in. Later as the car sat in the paddock he checked the oil level and it reported it to be OK. Any idea as to what may have happened? Could the earlier issue of the white puff of smoke somehow been a factor, or was that merely coincidence? It seems to me that such a huge ball of flame would most likely be unburned gas, not oil. Could an injector have failed and started squirting gas into the cylinder at the wrong time, like on the exhaust stroke?

POST 2Original post

Just a pure WAG. Intermediate shaft packed it in. Oil pump and cams are driven off the IMS IIRC. It fails and low oil pressure. Try and start and valves are miss timed so open on ignition. Hence fireballs. I'd be curious to know what it really is if you ever find out.

POST 3Original post

I agree with Les. The "grinding noise and low oil pressure" are not good signs. Also if the intermediate shaft eats it and the valves get out of time, it's likely that the pistons have contacted (some of) the valves. I'd say that engine is probably done.

POST 4Original post

The ims can't get loose enough for the cams to jump timing without loudly proclaiming the failure immediately after the ball cage fails. See the pic attached. The stub in the flange has .020" clearance to the inside of the shaft n will support it while it makes bloody awful noises. The one pictured was driven 8 miles gently after this failure!!! It had 145,000 miles.

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