London to Singapore — Flight Safety, FIRs Crossed, Airline Routing 2026
Great-circle ~5,900 nm · Scheduled block ~13 h direct · Last updated: May 2026
TL;DR
LHR–SIN is operated nonstop by British Airways and Singapore Airlines, with Qantas continuing the route on the Kangaroo backbone. Since February 2022 all three avoid Russian airspace. The replacement is the Caspian / Central Asia corridor: south-east across Turkey, through Azerbaijan or the Caspian, then Kazakhstan / Uzbekistan / Turkmenistan, India and the Bay of Bengal into Singapore. Block time is up roughly 30–60 minutes versus the pre-2022 Russia-routing baseline.
FIRs typically crossed
| ICAO | FIR | Notes |
|---|---|---|
| EGTT | London | Departure FIR. |
| EDUU / LKAA | Rhein / Praha | Central European upper, common transit. |
| LHCC / LRBB / LBSR | Budapest / Bucharest / Sofia | South-east Europe stack. |
| LTAA | Ankara (Turkey) | Workhorse transit. |
| UBBA | Baku (Azerbaijan) | Caspian crossing entry; see Baku bypass briefing. |
| UAAA | Almaty (Kazakhstan) | Central Asia core transit. |
| UTTR | Tashkent (Uzbekistan) | Alternative Central Asia transit. |
| VIDF / VABF | Delhi / Mumbai | Indian upper, southbound run. |
| VCCF / VOMF | Colombo / Chennai | Bay of Bengal transition. |
| WSJC | Singapore | Arrival FIR. Modern surveillance. |
Iran (OIIX) is bypassed by Western operators on this pair; either Caspian / Caucasus or Turkmenistan transit is preferred.
Pre-2022 vs current routing
Pre-2022, the standard LHR–SIN great-circle ran north-east via the Baltic, across European Russia and Siberia, into Mongolia or western China, then south through Hanoi or the Indochinese FIRs into Singapore. This trans-Siberian routing was efficient and short, and was the foundation of British Airways’ and Singapore Airlines’ pricing on the corridor.
From late February / early March 2022 Russian airspace closed to UK, EU and most allied operators. Singapore Airlines and Qantas independently withdrew from Russian transit for the same route. The replacement corridor runs south-east from London, through Turkey, across the Caspian basin (Azerbaijan or Caucasus transit), then into Central Asia (Kazakhstan and / or Uzbekistan / Turkmenistan), south through India and out across the Bay of Bengal into Singapore.
All flight paths on LHR–SIN are now at least a few hundred kilometres longer than the great-circle distance, and reported block-time deltas cluster around +30–60 minutes against 2019 baselines, depending on day-of-flight winds and exact corridor.
Operating carriers and their typical routings
777-300ER on the route. Caspian / Central Asia corridor; BA has publicly described flexing between north-of-Iran and south-of-Iran routings depending on the day’s NOTAM picture.
A380, 777-300ER and A350-900. Consistently uses the northern (Caspian / Central Asia) routing.
A380 on the European sector. Uses the same Central Asia corridor pattern as SQ; SIN remains the technical and operational fulcrum of the route.
Current airspace conditions on the corridor
The Caspian corridor and the wider Black Sea / South Caucasus area carry periodic GNSS interference and routing-flow constraints. See the Baku bypass briefing and Black Sea GPS spoofing.
Routings into Indian airspace are sensitive to Pakistan / India airspace status 2026 — primarily affecting carriers that previously transited Pakistan; LHR-SIN traffic is largely insulated but still feels secondary effects on flow.
UUUU / USSR-legacy upper FIRs remain closed to BA, SQ and QF. Detail in Russia West airspace.
Block-time and fuel impact
Public schedule samples from Cirium / OAG and crew rosters indicate block time on LHR-SIN is up by approximately 30–60 minutes versus the 2019 baseline, with westbound (winter) the worse side because of jet-stream interaction with the longer Central Asia track. The aircraft mix on the route — 777-300ER, A380, A350-900 — absorbs the extra fuel-uplift without payload issues except on the highest-demand westbound winter operations.
See why do airlines reroute for the cost-of-detour mechanics on long-haul.
Common diversion patterns
European-leg alternates: Frankfurt (EDDF), Munich (EDDM), Athens (LGAV), Istanbul (LTFM). Central Asia leg: Tbilisi (UGTB), Baku (UBBB), Tashkent (UTTT), Almaty (UAAA). Indian leg: Delhi (VIDP), Mumbai (VABB), Chennai (VOMM), Bengaluru (VOBL). Bay-of-Bengal and SE Asia: Colombo (VCBI), Kuala Lumpur (WMKK), Jakarta (WIII).
A350-900ULR, A380 and 777-300ER on this pair operate within standard wide-body ETOPS limits — the corridor is largely overland with short overwater segments. See ETOPS / EDTO explained for general background.
Sources and related
- Public ADS-B aggregations (Flightradar24, FlightAware) for corridor samples
- Cirium / OAG schedule data for block-time deltas
- OPSGROUP, EUROCONTROL bulletins for GNSS interference and conflict-zone status
- Airline route-network publications
Route-level data for your stack
Caspian and Central Asia corridor overlays, plus historical routing samples for LHR–SIN, are available via the FlySafe API.
FlySafe API →This page is editorial information based on publicly available routing, schedule and airspace data. It is not operational guidance, not a route plan, and not a substitute for ICAO / EASA / FAA / state-AIP publications, NOTAMs, or your operator’s dispatch and security teams.