Police officer forced to dive for cover by suspected hare courser
Summarised from 2 outlets · Updated 18 Nov, 13:32 · Archive
A police sergeant near Micheldever had to run for safety as a vehicle sped towards him during a hare coursing operation.
A police officer was forced to dive for cover as a suspected hare courser sped past him near Micheldever on 20 October. Officers had been called to land near the village at around 2.30pm following reports of two 4x4s in a field and people hare coursing. Police approached the field through woodland off Laverstoke Lane and began searching the area on foot.
During the operation, a black Mercedes SUV without number plates reportedly made off at speed, and officers gave chase but the vehicle escaped. Sergeant Martyn Evans was later walking towards the road to regroup with a colleague when a grey Suzuki Grand Vitara headed in his direction at speed. Body-worn video footage shows the officer quickly running into the treeline for safety as the vehicle passes before leaving the area.
Police said those involved in hare coursing can be 'dangerous and unpredictable', with offenders known to drive at speed, off-road or on the wrong side of the road in attempts to evade officers. Anyone who witnesses hare coursing is urged not to approach those involved and instead call 999.
How it is being reported
- WATCH - Police officer forced to dive for cover as suspected hare courser speeds pastA police officer was forced to dive for cover as a suspected hare courser sped past him near Micheldever.Basingstoke Gazette · 18 Nov, 13:01
- WATCH - Police officer forced to dive for cover as suspected hare courser speeds pastA police officer was forced to dive for cover as a suspected hare courser sped past him near Micheldever.Romsey Advertiser · 17 Nov, 09:12
In this story: Micheldever · Laverstoke Lane · Sergeant Martyn Evans · Hampshire Police
This summary was written by AI from the headlines and standfirsts above, and states as fact only what at least two outlets report. How we use AI · Report a problem · Corrections log
Comments (0)