25.02.2022 Views

NG4 March/April 2022

Local business directory and community magazine

Local business directory and community magazine

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

new highway code rules for <strong>2022</strong><br />

Courtesy of Link Magazines<br />

The Highway Code has received a refresh, with<br />

a new set of rules coming into force from 29th<br />

January <strong>2022</strong>. As well as some 49 existing laws<br />

having been updated, new rules will be introduced.<br />

The changes are extensive and further information<br />

is available on the website link located at the<br />

bottom of this article. However, the key areas are<br />

summarised below.<br />

Hierarchy of road users<br />

Previously The Highway Code stated all road users<br />

should be considerate towards each other, applying<br />

this principle to pedestrians and drivers equally. It<br />

meant that equal responsibility was originally placed<br />

on all road users for assuring the safety of others.<br />

The new hierarchy places responsibility on road<br />

users who could do greatest harm to others, and it<br />

is with them that the greatest obligation to protect<br />

the most vulnerable on the road now lies. Top of<br />

the hierarchy are lorry drivers, cars, vans, buses and<br />

motorcycles. But it should be noted that cyclists,<br />

horse riders and horse-drawn carriage drivers have<br />

a greater responsibility to reduce the danger posed<br />

to pedestrians.<br />

Pedestrian priorities at junctions<br />

Prior to the rule change, road users would have given<br />

way to pedestrians who have started to cross the<br />

road into which they are turning.<br />

Under the new rules priority must be given to<br />

pedestrians who are waiting to cross the road, which<br />

means that if you are about to turn into a road and a<br />

pedestrian is waiting to cross, you should give way.<br />

New rule for drivers and motorcyclists at junctions<br />

The new rule states that when turning into or out of<br />

a junction, drivers should not cut across the path of<br />

any other road user, including cyclists, horse riders<br />

or horse-drawn vehicles, if doing so would cause the<br />

other road-user to slow down, stop or swerve.<br />

Safe passing distances<br />

An amendment to existing Rule 163 sets out safe<br />

passing distances for drivers when overtaking<br />

cyclists, motorcyclists, horse riders and those in<br />

horse-drawn carriages.<br />

Drivers must give at least a 1.5 metre space when<br />

overtaking a cyclist at speeds of up to 30mph. More<br />

space should be allowed when overtaking at speeds<br />

of more than 30mph. Rule 72 establishes the right<br />

for cyclists to ride in the centre of their lane, to<br />

ensure that they remain visible.<br />

When passing a pedestrian who is walking in the<br />

road, drivers should allow at least two metres of<br />

space and maintain a low speed.<br />

Rule 213 has also changed and now states that on<br />

narrow sections of roads, horse riders may ride in<br />

the centre of the lane and drivers should allow them<br />

to do so for their own safety, to ensure they can see<br />

and be seen. Drivers should pass a horse at least 2<br />

metres distance and at a slow speed.<br />

In all cases, drivers will now have to wait behind<br />

a motorcyclist, cyclist, horse rider, horse-drawn<br />

vehicle or pedestrian and not overtake if it is unsafe<br />

or not possible to meet these clearances. Extra<br />

care should be taken in poor weather, including high<br />

winds.<br />

For a more in-depth look at the new rules, visit:<br />

www.gov.uk/government/news/the-highway-<br />

code-8-changes-you-need-to-know-from-29-<br />

january-<strong>2022</strong><br />

72 Please mention ngmagazines when responding to adverts

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!