Person dies after being found on M5 motorway in Devon



[ad_1]

One person has died after being found on the M5 following an incident on the Devon motorway.

The emergency services closed the road in both directions after the incident that occurred around 12.25 pm today (September 28) between junctions 27 and 26 of the road heading north /

The locks remain in place with motorists caught in traffic saying dozens of police cars, fire trucks and paramedics are still in place.

In an update provided just before 2.50pm, Devon and Cornwall police confirmed that one person was killed after the incident which will keep the northbound M5 closed for much of the day.

A police spokesman said: “Police were called today at 12:25 pm to the M5 in Cullompton due to concerns for the well-being of a person on the northbound carriageway.

” A person was located on the road who had suffered serious injuries and his death has since been confirmed at the scene.

M5 traffic

” The road was initially closed in both directions, but lanes one and two of the southbound carriageway have since been reopened.

“Drivers heading north are asked to avoid the area and use alternate routes when possible, as the road is expected to remain closed for a considerable time.”

According to the Inrix traffic and surveillance service, traffic is queuing for five miles between junctions 27 and 26 as a result of the incident.

We have created a Facebook group dedicated to bringing you breaking news from across the county.

In this group, our Devon Live journalists will share the latest local stories.

If there’s anything we haven’t reported on, please post it in the group discussion and let us know.

To join our group, click here and click “join”.

‘A post on the website reads:’ Congestion on the A361 and A38 through Wellington.

“Traffic is also slow through Uffculme, Cullompton and Ottery St Mary as traffic detours. ”

The police investigation of the death has issued a call for witnesses.

Anyone with information should contact the police by calling 101 and quoting registry 313 of September 28.

For updates on the incident, click here.



[ad_2]