Kingston Pedestrian Zone PCN Appeal Refused: Lesson

Hook — when “it just turned 4 o’clock” still isn’t safe

Most drivers have had that moment: you’re approaching a restriction you know well, you glance at the dashboard clock, and you make a quick judgement call. If it’s 16:00, you’re good. If it’s 15:59, you’re not. Simple, right?

A Kingston upon Thames case about Latchmere Road shows why it isn’t that simple. The driver genuinely believed the restriction had ended because his car clock ticked over to 16:00. The council’s CCTV timestamp suggested he entered a few minutes earlier. He argued it was close enough to be de minimis (too trivial to enforce), and that the council hadn’t proved its camera time was “atomic clock” accurate.

The tribunal refused the appeal — not because the driver wasn’t believable, but because the legal question turned out to be what “until 4.00 pm” actually means.

The case — what happened on Latchmere Road

Authority: Royal Borough of Kingston upon Thames Contravention: Fail comply restriction vehicles entering pedestrian zone (a moving traffic restriction) Location: Latchmere Road (a timed restriction / “pedestrian zone” style prohibition) Outcome: Appeal refused

The driver (the Appellant) was heading to collect his son on 24 June. He knew the Latchmere Road restriction and says he carefully watched his in-car clock as he approached.

He told the adjudicator that as he neared the restriction, he saw the time change from 15:59 to 16:00 and then proceeded, believing the restriction had ended.

The council issued a Penalty Charge Notice (PCN) alleging the vehicle entered at around 15:56. The council’s CCTV footage showed a timestamp of 15:56:31 as the vehicle entered the restricted street.

The key point: the signs on street stated the restriction operated Monday–Friday, 2.30 pm – 4.00 pm.

The arguments — what the driver said vs what the council said

The driver’s case (in plain English)

The Appellant’s argument was built around three common-sense points many drivers will recognise:

1. He relied on his car clock, which he actively keeps accurate.

He explained he has a “00” button that lets him quickly set the clock to the exact hour. He even described how he syncs it using the BBC Radio 4 time pips.

1. If there’s a dispute about the time, why believe the council’s equipment over his?

He asked why the council’s timestamp should automatically be preferred, particularly as the authority hadn’t produced proof that its CCTV/ANPR system is synchronised to an atomic clock or otherwise independently verified.

1. Even if he was technically early, it was only by a few minutes — surely that’s too trivial?

In written submissions he relied on the de minimis principle: if the council’s time was right, he was allegedly within the restriction by about 3 minutes and 28 seconds, and he argued that should be treated as too minor to justify a penalty.

The council’s case

The authority’s position was essentially:

• The vehicle entered during the restricted period (as evidenced by CCTV).
• Its camera systems are “maintained regularly” and the timestamps are “extremely accurate and up to date”.

Notably, the adjudicator recorded that the council did not provide supporting evidence to prove the accuracy of the camera clock (for example calibration logs, maintenance records, or a syncing protocol). That might sound significant — but it wasn’t the decisive issue in this case.

The decision — refused, even though the driver was credible

The adjudicator refused the appeal. Two findings drove the outcome:

1. The restriction ran “up to and including 16:00”.

The adjudicator looked not only at the sign but also at the underlying legal instrument creating the restriction — the Kingston upon Thames (Moving Traffic Restrictions) Order 2024 and its map schedule. From these, the adjudicator concluded the prohibition applied until 16:00 inclusive.

1. Therefore, the timing dispute didn’t matter.

Even if the driver’s car clock had just turned 16:00, the adjudicator’s view was that 16:00 is still within the operating hours, not safely outside them.

The adjudicator also made an important human point: the driver came across as honest and careful, and the adjudicator accepted his account as true — but that amounts to mitigation, and mitigation is not a legal ground that allows an adjudicator to cancel a PCN.

The legal reasoning — the key points, explained plainly

1) Signs matter — but the Traffic Order is the legal backbone

In moving traffic cases, councils don’t just “invent” a restriction with a sign. The restriction must be backed by a Traffic Management Order (or in London, often a moving traffic order made under London-specific legislation).

Here, Kingston provided:

• The Moving Traffic Restrictions Order 2024, and
• A map schedule stating:

“All vehicles prohibited… Mon–Fri, 14:30–16:00”.

The adjudicator used these documents to interpret the restriction and confirm its lawful hours.

Plain English: the sign tells drivers what to do; the Order is the rulebook that makes it enforceable.

2) “2.30 – 4.00 pm” is treated as including 4.00 pm, not stopping just before it

This is the crux. Many drivers read “2.30–4.00” as “you can go at 4.00”. The adjudicator took the opposite view: the restriction applies up to and including 16:00.

That’s why the “my clock just turned 4” argument didn’t win. In this tribunal’s interpretation, 16:00:00 is still inside the restriction and only 16:00:01 and beyond is safely outside (and even that assumes the system records seconds in a way that favours you).

This may feel counter-intuitive, but it reflects a common tribunal approach: when an order states an operating period ending at a stated time, that end time is usually treated as part of the restricted period unless the order clearly states otherwise.

Practical translation: if the sign says “until 4.00 pm”, treat 4.00 pm as still restricted.

3) The council’s lack of proof about CCTV accuracy didn’t help — because it wasn’t necessary

The driver pushed a reasonable challenge: “show me your clock is accurate”. The adjudicator even noted the council had not provided evidence supporting its claim of accuracy.

In many cases, that could be fertile ground — especially if:

• the alleged contravention time is right on the boundary, and
• the boundary point determines guilt or innocence.

But here, once the adjudicator decided 16:00 counts as restricted, the argument about whether the entry time was 15:56 or 16:00 became largely academic: either way it falls within the restricted window (on the adjudicator’s interpretation).

Plain English: you can be right about the camera clock being unproven, and still lose if the “end time” point is legally against you.

4) De minimis is not a “grace period” for moving traffic restrictions

The driver argued the alleged breach was only a few minutes and should be treated as trivial.

Tribunals can apply de minimis in appropriate cases, but it is not a guaranteed “margin of error” and it’s not the same as a statutory grace period (which is a concept more associated with certain parking situations, not camera-enforced moving traffic bans).

In a timed “no motor vehicles” restriction, being early is usually being early, even if by seconds. Some adjudicators may show flexibility in very unusual circumstances, but you should not assume they will.

Plain English: there’s no reliable “close enough” defence with these restrictions.

5) Mitigation can be compelling — but adjudicators generally can’t act on it

The adjudicator said the Appellant was credible and accepted his evidence about clock-setting. That matters, but only up to a point.

A tribunal adjudicator’s job is to decide whether:

• the contravention occurred, and
• a statutory ground of appeal is made out (for example, the contravention didn’t occur, the signage was inadequate, the vehicle was taken without consent, procedural impropriety, and so on).

Mitigation (fairness, honest mistake, rushing to collect a child, relying on a clock you reasonably thought was accurate) is typically something only the council can take into account via discretion.

Plain English: the tribunal isn’t a “fairness court”; it’s there to decide if the PCN is legally enforceable.

Lessons for drivers — practical takeaways

1) Treat the end time as “still restricted”

If a sign says 2.30 pm – 4.00 pm, assume the restriction applies right up to and including 4.00 pm. The safe approach is to wait until after 4.00 pm has clearly passed.

2) Don’t rely on your car clock for boundary decisions

Even a carefully set car clock can drift, and you may not know whether it’s ahead or behind. If you’re arriving near the cut-off:

• wait a minute or two, or
• take an alternative route.

3) Camera timestamp challenges need to be outcome-changing

Questioning the accuracy of the council’s CCTV time can be a smart line of defence — but it only helps if proving a time discrepancy would mean you were outside the restriction. If the restriction is interpreted as including the boundary time, the clock dispute may not move the needle.

4) De minimis is not a dependable safety net

A few minutes (or seconds) inside a timed restriction is still likely to be enforced. Don’t plan on “they’ll let it go” — especially in camera-enforced pedestrian zones and school streets.

5) Mitigation is for the council, not the tribunal

If your case is essentially “I made an understandable mistake”, focus your efforts early on asking the council to exercise discretion with a clear, polite explanation and any supporting context. By the time you’re at tribunal, the adjudicator may simply have no power to help on that basis.

Key takeaway — one memorable lesson

When a restriction ends at 4.00 pm, assume you can’t enter at 4.00 pm — only after it.