Wed. Nov 6th, 2024
alert-–-appeal-to-identify-motorist-whose-reckless-driving-forced-ambulance-on-way-to-999-call-to-swerve-and-plough-into-a-ditchAlert – Appeal to identify motorist whose reckless driving forced ambulance on way to 999 call to swerve and plough into a ditch

This is the shocking moment an ambulance that was rushing to an emergency swerved off a road and crashed into a ditch after a motorist pulled out in front of it. 

The speeding ambulance had to turn suddenly to avoid the white car, flipping onto its side and causing £26,000 worth of damage. 

The driver of the white Ford does not appear to see the 999 response vehicle despite it’s blue lights being on.

Police said the crash caused a ‘considerable and potentially life-threatening delay’ in attending to a critical patient, with another ambulance having to be diverted.

No one was injured in the collision but there was thousands of pounds worth of damage caused to the ambulance, which will take over a month to be repaired. 

Hampshire Constabulary is trying to identify the driver who pulled out in front of the ambulance and did not stop at the scene.

Police are appealing for witnesses, especially those with dashcam footage, to assist their enquiries.

The traumatic incident happened at around 11.15pm on September 20 on the A339 near Alton, Hampshire. 

Hampshire and Isle of Wight Constabulary said: ‘The ambulance was not conveying any patients at the time, but was on a blue light run and this caused a considerable and potentially life-threatening delay in getting to that patient, who was attended to by another ambulance instead.

‘A small white car, possibly a Ford Fiesta or Focus, is seen on dash cam footage but did not stop at the scene.

‘We are continuing to investigate a number of lines of enquiry to identify this vehicle and its driver, and are now issuing this dash cam footage as part of our appeal.

‘If you are this driver, or know who they are, please contact us.

‘We would also like to speak to anyone with relevant dash cam or CCTV footage.’

error: Content is protected !!