10 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHFuel return lines
Leading reported evidence
Use redline
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.
Leading evidence: 'Use redline' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Test drive was great' (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 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 · Original poster
I got the car back together last night and a test drive was great.
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.
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 · Original poster
I got them in using some white lithium grease as recommended in the Pelican article.
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.
10 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: 20261027T184158Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
It is an 2002. There is not a good how to on this.
From the Pelican how-to, if I skip the fuel line removal, then proceed with unclipping the wire harness, and fuel rail bolts, I should be good to unclip the injectors and pull the rail off? Then the injectors out of the block?
I take it I don't want to release the quick disconnect or muck around with removing the fuel rails from the car?
Ok. Left side out, new injectors back on the rails, but i can not get them back in the block. Any hints?
Am i going to ruin the new injectors by greasing the ports?
Normal process is to use a lube on the o-rings,,
most Hydro shops, and auto supply houses sell it.
IIRC its available through Jegs/Summit as well.
A good assembly lube works too, I use Redline..
Thanks everyone. I got them in using some white lithium grease as recommended in the Pelican article. That article says to insert the injectors first, then put the rails on, but I found it impossible to get the retaining clips back on that way. I put the injectors on the rails, put the clips on, and then re-inserted the whole assembly back into the block.
I got the car back together last night and a test drive was great. The old injectors were very brittle. I am surprised that I didn't have any serious problems before. I replaced them as the car has 100K miles on it, and it seemed time.
Plus, of course, shortly after the Flat6 video came out, most vendors raised the prices on injectors.
This is a source reference. Confirm exact model applicability in the original material.
