M3 and M27 crashes cause traffic disruption in Hampshire
Summarised from 2 outlets · 8 reports · Updated 27 Sept, 17:42 · Archive
Crashes on the M3 and M27 motorways near Portsmouth have caused lane closures and delays.
Crashes on the M3 and M27 motorways have caused significant disruption to traffic. The M27 was closed following an incident involving a man on a bridge over the A27, who was taken to hospital with serious injuries. The M3 also experienced delays after a crash that resulted in lane closures.

How it is being reported
- Massive emergency response on A27 saw man fall from bridge after crash as road shut down - police updateDrivers suffered long delays during the incidentThe News, Portsmouth · 27 Sept, 13:38
- M27 shut by police and man taken to hospital with serious injuriesThe M27 was shut last night after police responded to a concern for welfare involving a man on a bridge over the A27.Southern Daily Echo · 27 Sept, 13:28
- Delays building after crash with lane closed on the M3 - LiveDrivers are being warned after a crash has caused delays on the M3.Southern Daily Echo · 27 Sept, 13:18
- All drivers need to know as M27 junction 10 closures continue next monthM27 motorists face closures at Junction 10 next month as work continues on the motorway.Southern Daily Echo · 27 Sept, 03:30
- M27 and A27 closed due to “serious“ multi-vehicle crashDrivers are facing long delaysThe News, Portsmouth · 26 Sept, 21:09
- M3 crash sees lane closed and delays for driversDrivers delayedThe News, Portsmouth · 26 Sept, 13:57
- Road closed after crash near A27 sees delays for driversDrivers are facing delays in the areaThe News, Portsmouth · 26 Sept, 11:48
- A27 weekend closure sees drivers warned of disruption for worksWork will keep the “important stretch safe and reliable”The News, Portsmouth · 26 Sept, 10:36
In this story: M3 · M27 · A27 · Portsmouth · Hampshire
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)