27 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCH100@100k
Reported or suspected cause
deer
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.
Leading evidence: 'deer' (1 discussions report identifying this cause; no attributable repair resolution). Across 1 matching discussions, the most frequently mentioned possible cause is 'deer' (1 discussions; 1 report identifying it and 0 suggest it). The most frequently discussed action is 'Replace planned' (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 · Original poster
I had planned on hitting 100k during the day, but a last minute, 400 mile trip changed everything.
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 · Original poster
Tested the camera for better exposure, set the cruise @ 99,999, do a test run and yes hit the trip @ 99,990.
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
When I was about to cross 40,000 I reset the trip odo when it got to 39,600 so both would read 400...
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
Tested the camera for better exposure, set the cruise @ 99,999, do a test run and yes hit the trip @ 99,990.
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.
27 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.
1 acknowledgements have no verified action link; they do not establish a repair result.
Outcome without a verified action link
Insurance totaled the car, I bought it back, fixed it for $300 and drove it for another 30k.
Recently took a 400 mile trip and hit the century mark. Had to make it memorable. It almost was 5 minutes later when coyote crossed my path.
Anyway-I knew I had to have proof of 100k with this crowd.
Unfortunately it was in the dark so the pic is not as crisp as I would of liked -
It was one of those "in restrospect", I should of....
Tested the camera for better exposure, set the cruise @ 99,999, do a test run and yes hit the trip @ 99,990. I had planned on hitting 100k during the day, but a last minute, 400 mile trip changed everything.
Trying to maintain an exact speed was harder than expected, plus I knew my window of opportunity was just over 30 secs.
I feel like such a wimp. I'm only just about to hit 50,000 so my photo would be at a paltry 50MPH.
When I was about to cross 40,000 I reset the trip odo when it got to 39,600 so both would read 400... at the same time. But I forgot.
Tried again before 45,000 and reset the trip odo when I got to 44,550.
Still no luck. I always reset the trip odo when I fill up, and in a microsecond of senior moment, reset the trip odo with about a 100 miles to go to 45,000. THIS time I am going to pay attention!
Hopefully
I had a 108mph at 108000 pic - somehow I deleted it, guess after thinking about it wasnt too special...
also have this... but speed is wrong (there was just NO WAY it was gonna happen at that point - traffic )
not to distract from the OP's moment - sorry
Thanks guys!
I'm planning to hit 200k with this car. It is a semi-DD and has many planned trips.
I was just figuring, if this became a ritual every 10k, at 170k, I'd have 21 sec to get a good pic vs 36 sec @ 100.
Stray animals were more on my mind. Far more damage, plus not much you can do but hit the brakes and pray. I hit a deer years ago with an Audi. Not alot of damage, but crapped all over the side of the car.
Pretty sure it was the deer. It was not the dramatic, crush the front of the car and come through the windshield type of hit. I was going ~75 on a banked curve on the interstate. The small doe came up an embankment and hit the front passenger fender area. I wasn't sure I hit something at first. First depression in the road and I heard the tire scrape the fender and knew something was wrong. Insurance totaled the car, I bought it back, fixed it for $300 and drove it for another 30k.
What a great thread 15psi. I don't know if my MY99 will ever hit 100k miles, but wed am heading up to the White Mtns. I did 106 mph (I think my speedo is 5 mph high) shortly before Lincoln...at 48,643 mi.
