Gatwick Airport: Easter travel chaos as crash closes part of M23

A single-vehicle crash on the M23 has snarled traffic near gatwick airport, closing the northbound carriageway between junction 10 in Crawley and junction 9. Emergency services, including Sussex Police and West Sussex Fire & Rescue Service, are at the scene and the road is expected to remain closed for several hours. The car, carrying two men and a woman, struck the central reservation and then a tree. Motorists were urged to avoid the area while collision investigators and traffic teams work to reopen the route.
What happened on the M23?
The incident took place in the early hours of the morning, with timings in local reports placing the collision at about 05: 30 GMT and descriptions noting it occurred just after 5am. Police have described the event as a serious single-vehicle collision in which a car travelling north came into collision with the central reservation and a tree. Emergency responders attended immediately and National Highways has officers at the scene assisting with traffic management.
A National Highways spokesperson said, “Due to the serious nature of the collision the road is expected to remain closed for several hours. ” Sussex Police confirmed officers are investigating and have asked anyone who witnessed the crash, or who has relevant dashcam footage, to come forward and help with enquiries. The closure directly affects movements toward gatwick airport, with the northbound carriageway between J10 (Crawley) and J9 (Gatwick Airport) remaining blocked while investigators work.
Gatwick Airport disruption ripples across local network
With the M23 northbound closed between junction 10 and junction 9, traffic built quickly and delays extended well beyond the immediate scene. By mid-morning delays of more than two hours had been recorded, and in parts the hold-ups reached roughly 150 minutes, with average speeds falling to around five miles per hour on stretches approaching the closure. Trapped traffic was turned around in stages back to junction 10, increasing congestion on feeder routes and local roads feeding the airport.
Local junctions and access roads experienced knock-on effects. Congestion reached back toward J10a at Copthorne Way and long delays were reported from Manor Royal in Crawley. Shorter but meaningful delays were recorded on the A23 Airport Way, adding friction for travellers trying to reach gatwick airport terminals and surrounding business areas. Authorities warned that the closure was likely to remain in place for several hours, creating peak disruption during a busy travel period.
Emergency response and investigation
West Sussex Fire & Rescue Service issued an early statement noting the northbound closure between Junction 10 for Crawley and Junction 9 for Gatwick and advising drivers to avoid the area. Firefighters joined the emergency response on the morning of the incident, and crews worked alongside police and highway teams to make the scene safe and support the investigation.
Sussex Police described the collision as serious and reiterated its appeal for witnesses and dashcam footage. Officers have asked the public to submit any relevant material, referencing the investigation as Operation Dorset, and stressed that the carriageway will remain closed while collision investigators and recovery teams complete their work. National Highways personnel have been present to manage diversions and reduce secondary incidents as traffic is turned around or held clear of the scene.
At this stage authorities are focused on scene safety, forensic examination of the collision site, and restoring traffic flow. The vehicle involved carried two men and a woman; no further details on their conditions were supplied in initial statements. Emergency services emphasised patience and cooperation from motorists while the closure remains in place.
How quickly gatwick airport and the wider M23 corridor will return to normal traffic conditions depends on the duration of the on-scene investigation and recovery operations — and on whether further congestion creates secondary delays that need active management?




