Free Traffic Legal Advice
Live cases legal advice => Speeding and other criminal offences => Topic started by: MichaelH on April 10, 2025, 11:35:35 am
-
And also I acknowledge that I may have misinterpreted the time on the image, although to me as it happened so fast it probably wasn’t far off that time.
-
Yes I have contacted national highways and are awaiting response to activated time of the red x, although lady on phone did confirm that the smart sign in question was the start of the warning of lane closure, and yes there were many vehicles infront and behind. You would assume common sense would prevail in this case, I’m sure I’m not the first nor will I be the last to fall foul of this given that the gantry is meters before the turn off for the m60. And ppl wishing to leave the motorway would have already been in the inside lane.
-
If you have a dashcam now would be an ideal time so save the footage as that would certainly help your case if the events are as you described.
-
There appears to be a lot of traffic in that closed lane along with the OP. Now whether that backs up that the gantry had just changed or not I don't know.
You could contact National Highways to get a log of when the x was first displayed
Is probably a decent approach to begin with.
-
The OP claims "the red X activated literally as I was driving past it as the time says on the ticket was 0.35s." Which seems to suggest that the red X appeared as he was passing BECAUSE the time says 0.35s, and applying such logic as suits his case, rather than saying "I didn't see it illuminated as I approached." What did his own eyes tell him about whether it was illuminated or not as he approached? Or was he not paying attention?
-
I recall the actual data is on the top of the images, unfortunately OP has submitted a screenshot so it's unreadable.
OP - if you go back onto where you got that picture, right click the picture, you may be able to "Open in new tab" or "Save Image As". You may also be able to click it and enlarge it, then save that image, and submit it onto a post.
-
Time Int(secs) on your HADECS3 data relates to the time between the two camera flashes. It's short for "Time interval"
Cameras are triggered 200m distance apart and this is a secondary check for speed only - as if the timing on the flash was wrong it would also calculate the wrong speed.
It does not relate to how long the sign has been displayed.
For a red X they don't need the speed to prosecute, just evidence that you passed under it which they seem to have. Image 4 with the two red lines overlaid.
You could contact National Highways to get a log of when the x was first displayed.
My understanding is type approval is still 60 seconds after display until enforcement & that applies to red X too.
-
How do you arrive at that conclusion?
-
So basically 1-2s prior to that picture there was no red x on that lane.
-
Mabye this helps
[attachment deleted by admin]
-
We don't charge extra for white space to make your post more accessible.
as the time says on the ticket was 0.35s
Depending on what it actually says, this could be very important. Or not.
-
I received a NIP from Manchester police regarding a lance closure on the m62 which it alleged I drove through, they have pictures of me passing the red x sign, what the pictures don’t show however is that the smart motorway gantry is almost exactly at the junction to Turn off to access m60, the red X activated literally as I was driving past it as the time says on the ticket was 0.35s with 5 cars infront and 3 behind travelling at 30 mph in the left lane indicating to leave the motorway, which I did and have a full journey log to prove this, is this unfair because to me it seem ridiculous to be charged for this when I was already leaving the lane with the x and the time from the very first x was exactly the time of me passing the gantry, there were no other warnings of any sort that there was a lane closure. Any advise would be great thank you. Also I side note, this happened at junction 18, and the ticket showed that the cause of the red x was at junction 20.