8 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHHe Should have been driving a Porsche! :)
Leading reported evidence
Use "land marks"
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 "land marks"' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, the most frequently mentioned possible cause is 'fastest ticket ever' (1 discussions; 0 report identifying it and 1 suggest it). The most frequently discussed action is 'Check watch' (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 suspect 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.
Suspected cause · Original poster
official records are kept, it was probably the fastest ticket ever
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 had to double-check my watch because in 27 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 · Original poster
motorcyclist hit the throttle and possibly set the informal record for
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
They do the timing method based off landmarks and use very very poor calculus for the distance cal.
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.
8 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: 20261027T035758Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
My wife emailed me the following story at work. Think she was sending me a subtle hint! LOL
I've already gotten one photo ticket and only had my MY99 996 3 months! (I live in the Wash/Metro area where photo tickets seem to abound!)
Subject: Minn. Trooper Writes 205 MPH Ticket....
Minn. Trooper Writes 205 Mph Ticket
WABASHA, Minn. (AP) - With a State Patrol airplane overhead, a
motorcyclist hit the throttle and possibly set the informal record for
the fastest speeding ticket in Minnesota history: 205 mph.
On Saturday afternoon, State Patrol pilot Al Loney was flying near
Wabasha, in southeastern Minnesota on the Wisconsin border, watching two
motorcyclists racing along U.S. Highway 61.
When one of the riders shot forward, Loney was ready with his stopwatch.
He clicked it once when the motorcycle reached a white marker on the
road and again a quarter-mile later. The watch read 4.39 seconds, which
Loney calculated to be 205 mph.
``I was in total disbelief,'' Loney told the St. Paul Pioneer Press for
Tuesday's editions. ``I had to double-check my watch because in 27 years
I'd never seen anything move that fast.''
Several law enforcement sources told the newspaper that, although no
official records are kept, it was probably the fastest ticket ever
written in the state.
After about three-quarters of a mile, the biker slowed to about 100 mph
and let the other cycle catch up. By then Loney had radioed ahead to
another state trooper, who pulled the two over soon afterward.
The State Patrol officer arrested the faster rider, 20-year-old
Stillwater resident Samuel Armstrong Tilley, for reckless driving,
driving without a motorcycle license - and driving 140 miles per hour
over the posted speed limit of 65 mph.
A search of speeding tickets written by state troopers, who patrol most
of the state's highways, between 1990 and February 2004 shows the next
fastest ticket was for 150 mph in 1994 in Lake of the Woods County.
Tilley did not return calls from the newspaper to his home Monday. A
working number for him could not immediately be found by The Associated
Press on Tuesday.
Only a handful of exotic sports cars can reach 200 mph, but many
high-performance motorcycles can top 175 mph. With minor modifications,
they can hit 200 mph. Tilley was riding a Honda 1000, Loney said.
Kathy Swanson of the state Office of Traffic Safety said unless Tilley
was wearing the kind of protective gear professional motorcycle racers
wear, he was courting death at 200 mph.
``I'm not entirely sure what would happen if you crashed at 200 miles
per hour,'' Swanson said. ``But it wouldn't be pretty, that's for
sure.''
undefined
This guy should have been driving a 911 tho....he might have even gotten off! Any thoughts?
Mdrob
=====================
MY99 996 (mine)
'01 BMW 325xi (mine)
'04 ML350 (herz)
3y/o daughter and 5 y/o son (Ourz)
I got a photo radar ticket from Macarthur Blvd about a month ago. You should post some pics of your 996! Much of my family is from MN (know Wabasha well) so everyone's been sending me this story via email!
The guy was clocked overhead by an airplane. A normally aspirated motorcycle will not hit 200mph. The police used "land marks". I think someone miscalculated.
Check out the below link for an explanation.
http://www.superbikeplanet.com/2004/Sep/040923z.htm
They also have a link to the actual ticket.
maybe you wife reads these boards too? This was discussed a couple days ago:
https://rennlist.com/forums/996-forum/159997-past-military-helps-in-today-speeding-tickets.html
Exacly my comment when I got the email from a friend about a week ago or so. They do the timing method based off landmarks and use very very poor calculus for the distance cal. - The only example I remember from my calculus class in high school. The fastest bike is that hiyabusa and it would get about there but that was only for the older one as the newer ones have the limiter now. I actually had a 100 and topped it out at 170. Incidently - motorcylce speedos are notorious for being greatly off at the higher speeds-
"Kathy Swanson of the state Office of Traffic Safety said unless Tilley
was wearing the kind of protective gear professional motorcycle racers
wear, he was courting death at 200 mph."
LOL! at 200mph "on the street" (totally different tha on the track) protective gear won't make much difference
(doesn't mean I don't use it, would never ride without leathers and helmet in the streets, and saved my butt on the track) but at 200mph you are pretty much done for in a public road if you fall.
And 205mph just like that? a Busa with a blower can get there in no time but around 170 is more like it in this case.