SW Train - Details Taken

[Konzkripted123]

Hi all,

Went from station A to B. Accidentally didn't scan at A and when I got to B I had to give the officers all my details and explained that I did scan my oyster (unmanned station, gates open, didn't realise it didn't go through). I gave all my details to the officer and he called up someone to check my details. He then took me to the desk and made me pay for a full ticket, which he took and said he would rip up. He didn't mention anything about a fine and said my details have been recorded for life and not to do it again as I will go to court and be fined next time. He asked if this was my first offence, which is true.

Should I expect a letter in the post with a fine and court summons despite what he said?

I was stupid to not realise that it didn't go through and accept my mistake really worried now.

 

[Crossover]

You say the inspector made you purchase a full fare, the ticket from which he took and warned you not to do it again. If this was a first time offence and from your account, I get the feeling the inspector has given you the benefit of the doubt and in cooperating purchasing a new ticket, that will be the end of the matter. If it happens again, you may not be quite so fortunate

 

[Konzkripted123]

Hi, thanks for the reply. I was thinking that he had given me the benefit of the doubt but it was just playing on my mind! I hope that was the end of it, but if anyone has had the same experience and it did end there please let me know just to give me that final peace of mind.

 

[455driver]

I agree with Crossover, you were let off this time but your details were taken to be added to the database, if you make the same mistake (or any other one) this will be flagged up and you wont get the benefit of the doubt next time.

This isnt as bad as it sounds so there is no need to worry, just make sure your Oyster scans properly each time.

 

[maniacmartin]

1 beep + green light = Success
2 beeps + red light = Failure

 

[island]

Sounds like there will be no further action, just take extra care in the future.

 

[Monty]

I would like to add that it's unlikely your details have been "recorded for life on a database". IRCAS (the company SWT use to confirm names and addresses) use the electoral role and a note is only made if a passenger has been issued with a PFN, UFN or reported for Prosecution (MG11).

Your details will however remain in the inspectors notebook which he/she is required to hold for seven years.

 

[Pumbaa]

Not quite. Every time an enquiry is made about an individual, a log is created, even if it goes no further. Which is why you have to ring back to tell IRCAS that no further action was taken. If you do not ring back to advise of something being issued or no further action, the system will assume you let them off with a verbal warning, but they were still stopped for a ticket irregularity. This information is not available to Guards and Revenue staff, you will only be told of previous events that have resulted in something being issued. Prosecutions and back-office staff can see the whole shebang however, and is mainly used for deciding how to prosecute, if at all.

 

[TonyR]

1 beep + green light = Success
2 beeps + red light = Failure

Fine if you know the code but how is Joe Public supposed to know that? The TfL page on Touching in and out only says you might get a red light and the gates not open and attribute it to a clash with other cards in your wallet. But nothing about single or double beeps. In fact the only place its mentioned is about a single beep in how to use a contactless payment card.

 

[tsr]

1 beep + green light = Success
2 beeps + red light = Failure

Maybe a little off-topic, but... unfortunately, that system can be faulty. I have had two beeps + a "Board Tram" indication before when using a Tramlink validator. Luckily, although it transpired my Oyster didn't touch in correctly at all, revenue staff used discretion when I was checked and allowed me to touch in at the next stop. I don't doubt this error could also happen elsewhere if the bug hasn't been fixed, but it's hard to prove exactly what happened.