Very slow traffic was reported on the A27 Westbound after a crash involving a moped and a car. The incident was being covered as live updates, giving drivers on that stretch a traffic warning rather than a full road-closure notice.
A27 Westbound traffic
The report placed the disruption on the westbound side of the A27, where traffic was moving at a much slower pace than normal after the crash. For drivers already on that route, the practical effect was simple: expect delays and a slower journey while the road remained affected.
The Argus reported the incident as it developed. That live format matters because it shows the traffic issue was active at the time of publication, not a past delay cleared from the road network.
Moped and car crash
The crash involved a moped and a car, but the brief update did not add police detail, injury information, or any road-status explanation beyond the slow traffic report. That leaves the traffic impact as the only firm public detail attached to the incident in the available update.
For anyone heading westbound, the useful readout is the same: the A27 was affected immediately after the crash, and the disruption was serious enough to be described as very slow traffic. No further instructions or diversion information were included in the update, so drivers had to rely on live conditions rather than a fuller incident summary.
Live update report
The live-update note gives readers one clear operational point: the A27 Westbound was still experiencing slow traffic when the report was posted. If you were planning to use that route, the safest assumption from the available information was to allow extra time and check the road again before setting out.
Because the update did not include a clearance time, the question for drivers was not what caused the delay — that part was already identified — but how long the westbound disruption would continue. Until a further road update appears, the incident should be treated as an active slowdown on the A27.
