Heathrow and Gatwick are usually described by their route networks, which is the wrong end of the telescope if somebody is driving you to one of them. From a car, they are separated by roughly twenty miles of orbital motorway and by an entirely different relationship with the capital. One sits against London's western edge. The other sits well outside it, beyond the M25 altogether.
That distinction governs everything that follows: how long the run takes, which hours are treacherous, how much margin a sensible chauffeur builds in, and which airport is genuinely more convenient from your own address. Below is the road access to each, the timings we plan around, and the honest circumstances in which the airport that looks further away is the easier journey.
Where each airport actually sits
Heathrow occupies a wedge of west London between the M4 and the western arc of the M25, close enough to the city that suburbs press against its perimeter road. From Mayfair it is a run out along the A4 or the M4, and from most of the western Home Counties it is a short hop down a motorway junction or two. It feels like part of London because, functionally, it is.
Gatwick sits in West Sussex, at the end of a short spur off the M23, which in turn leaves the M25 at junction seven. From central London the journey is a genuine departure from the city: south across the river, out through the southern suburbs or round the orbital, then a clean motorway run through open country. Nothing about it feels metropolitan after the first fifteen minutes.
The roads in, and where they fail
The Heathrow approach has two personalities. Off-peak, the M4 delivers you in well under an hour from the West End and the whole thing is unremarkable. At peak, the same road becomes a queue, the A4 alternative through Hammersmith and Chiswick is no better, and the M25 between roughly junctions twelve and sixteen is among the least forgiving stretches of motorway in the country. Losing half an hour there is routine rather than exceptional.
Gatwick's own approach is easy: the M23 spur is short, purpose-built and rarely the problem. The risk lies further back. If the route uses the M25 anticlockwise, an incident anywhere between junctions ten and seven can add a great deal, and there is no meaningful parallel road. If it uses the A23 through Croydon and Purley instead, it is slower but more resilient, which is why we sometimes choose it deliberately on a bad morning.
Four terminals against two
At Heathrow the terminal is not a detail; it changes the last ten minutes of the drive and occasionally the whole route. Terminals two and three share the central area reached through the tunnel under the runways. Terminal five has its own approach from the western side, and terminal four is reached from the south. Arriving at the wrong one is expensive in time, and it happens most often when a booking says only Heathrow.
Gatwick's geography is simpler. Two terminals, north and south, sit close together and are linked by a shuttle, and the road layout signs them clearly on the way in. Getting the terminal wrong is still worth avoiding, but it is a smaller mistake and easier to recover from. For a nervous traveller or a very early departure, that simplicity has real value.
From central London, side by side
Set against each other on the points that decide a drive rather than a flight, the two airports separate quite cleanly.
- Distance from the West End: Heathrow is roughly half as far as Gatwick
- Typical drive: around 45 to 75 minutes to Heathrow, 70 to 100 to Gatwick
- Main approach: the M4 and A4 for Heathrow, the M23 spur for Gatwick
- Terminals: four in use at Heathrow, two at Gatwick, linked by a shuttle
- Peak weakness: Heathrow inherits London traffic, Gatwick inherits the M25
- From south London, Surrey, Sussex or Kent, Gatwick is usually quicker
- From west London, the Thames Valley or the M4 corridor, Heathrow wins easily
- After ten at night both improve sharply, Gatwick most of all
When Gatwick is the easier journey
If you live south of the river, the argument is largely settled before it starts. From Clapham, Dulwich, Croydon, Sevenoaks, Guildford or anywhere in Surrey and Sussex, Gatwick is reached without touching central London, and the drive is mostly on roads that flow. Heathrow from those addresses means crossing the city or committing to the western M25, both of which are unpredictable in a way the M23 is not.
It also wins on simplicity at difficult hours. A four in the morning collection for a Gatwick departure is a straightforward run down an empty motorway to an airport with two clearly signed terminals. The equivalent Heathrow run is quick too, but the terminal geometry is more demanding and the perimeter roads are busier at that hour with staff traffic and freight.
And it wins whenever the flight you actually want is there. Thirty extra minutes on the road is almost always a better trade than a connection, an earlier departure or a less convenient arrival time at the far end. We would rather drive you further to the right flight than have you rearrange your travel to shorten our journey.
Timing the run, whichever you choose
We plan backwards from your check-in rather than forwards from your door, then add margin sized to the hour and the road. A Heathrow departure at eight in the morning gets a far larger cushion than the same departure at eleven, because the difference between those two journeys can be forty minutes. For Gatwick we watch the M25 approach specifically, and will reroute through south London if the orbital looks poor.
Give us the terminal and the flight number when you book. The flight number lets us plan around the published schedule, so a departure brought forward or an arrival landing early does not catch anyone out, and it tells us which side of either airport to head for. Send it on WhatsApp or by email with your luggage count, and the vehicle recommendation and the timings follow from there.
