Where Irkutsk’s flights went in the days around the reported hospital death
A review of public flight histories documents connections across Russia and Asia between 26 September and 1 October. The records establish travel routes; evidence linking a passenger to the incident remains missing.
Minimum counts from the records obtained. Coverage on 26 September is especially limited. This is an incomplete reconstruction, not a census of every flight or a count of exposed people.
Flights departing Irkutsk connected the region with domestic hubs and overseas destinations in the days surrounding a woman’s reported fatal illness in nearby Shelekhov. An Irkutsk Live review identified 160 departures to 33 airports in 7 countries during a six-day review window.
Those connections help define where officials might need to make enquiries if a travel link is established. None of the incident sources reviewed for this feature identifies the woman, an infected traveller or a named contact as a passenger on any of the flights listed here. The records contain aircraft movements, not passenger health histories.
The timeline has an unresolved endpoint
The Insider’s 2 October report, citing the independent outlet People of Baikal, said the woman spent three days in hospital and died overnight on 1–2 October. It also reported an earlier laboratory incident. That account is attributed reporting; it does not supply a verified time of death or establish the laboratory allegation, the pneumonic form of illness, or a chain of transmission. Calling her “patient zero” would imply knowledge of the first infection that the available evidence does not provide.
For a reproducible comparison, this analysis covers actual departures from 00:00 on 26 September to just before 00:00 on 2 October 2026, Irkutsk local time. The start is an editorial research boundary, not an established start of infectiousness. Without a precise death time, late departures on 1 October cannot reliably be placed before or after her death; departures early on 2 October are outside this dataset.
The district administration’s 2 October statement described a suspected especially dangerous infection without naming the disease. It said identified contacts were under medical observation, without symptoms and with negative laboratory tests at that time. Contacts under observation are not confirmed cases.
What the flight records establish
Russian destinations account for 126 of the 160 movements documented. Moscow’s Domodedovo and Sheremetyevo airports together received 31 recorded departures, while Novosibirsk accounted for 29. Krasnoyarsk, St Petersburg and destinations across the Russian Far East also appear. These are counts within the retrieved records, so they cannot establish each route’s share of all airport traffic.
The international network spans China, Mongolia, Thailand, Vietnam, Uzbekistan and Kyrgyzstan. Beijing appears as two separate airport destinations, Capital (PEK) and Daxing (PKX), with 11 documented departures between them. The records also establish flights to Guangzhou, Harbin, Sanya and Shanghai; Bangkok and Phuket; Ulaanbaatar; Tashkent and Namangan; Osh; and Cam Ranh, which serves the Nha Trang area.
A city served by two airports is counted once in the location total and twice in the airport total. Talakan is an oil-field airport destination rather than a city. The locations in this investigation describe the places served by the flights, without assigning disease status to them.
Each entry below is supported by at least one public history showing an actual departure from Irkutsk and a landed status. The source links identify the flight histories used, and the downloadable record list preserves the departure dates and times reviewed. The number beside each route reflects only records obtained for this investigation.
Explore all 33 documented routes Dates, flight numbers and sources
| Destination | Recorded departures | Flight histories |
|---|---|---|
| Blagoveshchensk BQS · Russia | 130 Sept | IO177 |
| Chita HTA · Russia | 527 Sept, 28 Sept, 30 Sept, 1 Oct | IO105IO109IO311IO317 |
| Kazan KZN · Russia | 129 Sept | N4744 |
| Khabarovsk KHV · Russia | 627 Sept, 28 Sept, 29 Sept, 30 Sept, 1 Oct | HZ5653HZ5655IO107 |
| Krasnoyarsk KJA · Russia | 1127 Sept, 28 Sept, 29 Sept, 30 Sept, 1 Oct | FV6678FV6686FV6868FV6882SU6868SU6882 |
| Mirny MJZ · Russia | 528 Sept, 29 Sept, 30 Sept, 1 Oct | 6R572IO9587 |
| Moscow DME · Russia | 1427 Sept, 28 Sept, 29 Sept, 30 Sept, 1 Oct | S73018S73022U6106 |
| Moscow SVO · Russia | 1726 Sept, 27 Sept, 28 Sept, 29 Sept, 30 Sept, 1 Oct | SU1441SU1443SU1445SU1447SU1563SU1623 |
| Novosibirsk OVB · Russia | 2926 Sept, 27 Sept, 28 Sept, 29 Sept, 30 Sept, 1 Oct | S75226S75228S75230S75232S75234S75236 |
| Omsk OMS · Russia | 129 Sept | S76451 |
| Petropavlovsk-Kamchatsky PKC · Russia | 227 Sept, 30 Sept | S76411 |
| Samara KUF · Russia | 128 Sept | IO465 |
| St Petersburg LED · Russia | 727 Sept, 28 Sept, 29 Sept, 30 Sept, 1 Oct | S76409SU2933 |
| Talakan oil field TLK · Russia | 627 Sept, 28 Sept, 29 Sept, 30 Sept, 1 Oct | IO410IO417IO9415 |
| Tomsk TOF · Russia | 11 Oct | UT158 |
| Ufa UFA · Russia | 228 Sept, 1 Oct | S76419 |
| Ulan-Ude UUD · Russia | 226 Sept, 1 Oct | IO117IO315 |
| Vladivostok VVO · Russia | 527 Sept, 28 Sept, 29 Sept, 30 Sept | S76403U6365 |
| Yakutsk YKS · Russia | 427 Sept, 28 Sept, 30 Sept, 1 Oct | S76401 |
| Yekaterinburg SVX · Russia | 627 Sept, 28 Sept, 30 Sept | S76415U6366 |
| Beijing PEK · China | 626 Sept, 27 Sept, 28 Sept, 29 Sept, 30 Sept, 1 Oct | CA870 |
| Beijing PKX · China | 527 Sept, 28 Sept, 29 Sept, 30 Sept, 1 Oct | S76311 |
| Guangzhou CAN · China | 226 Sept, 30 Sept | S76319 |
| Harbin HRB · China | 128 Sept | IO891 |
| Sanya SYX · China | 227 Sept, 29 Sept | SU866 |
| Shanghai PVG · China | 228 Sept, 30 Sept | S76325 |
| Osh OSS · Kyrgyzstan | 130 Sept | S76327 |
| Ulaanbaatar UBN · Mongolia | 227 Sept, 1 Oct | IO230IO232 |
| Bangkok BKK · Thailand | 627 Sept, 28 Sept, 29 Sept, 1 Oct | S76305S76309S76317SU658 |
| Phuket HKT · Thailand | 227 Sept, 30 Sept | SU660 |
| Namangan NMA · Uzbekistan | 130 Sept | HY9822 |
| Tashkent TAS · Uzbekistan | 328 Sept, 29 Sept, 1 Oct | HY9674U62719 |
| Nha Trang / Cam Ranh CXR · Vietnam | 128 Sept | SU840 |
What these connections cannot tell us
Airport destinations cannot establish that a patient or contact travelled, that an infectious person boarded an aircraft, or that anyone at the destination was exposed. The flight data also cannot show passengers’ onward journeys. We have therefore drawn direct documented connections only, without adding speculative connections through major hubs or estimating passenger numbers from aircraft capacity.
A meaningful assessment would require a confirmed diagnosis, a clinical timeline, an identified exposure and a travel history tied to a particular flight. The public evidence reviewed here does not supply that chain. A busy route is not, by itself, evidence of a higher disease risk.
How we researched this feature and where coverage falls short
We used the airport’s published destination and flight-number listings to identify candidate services, then examined public flight histories. A current timetable was a search aid only: scheduled services were never counted as operated flights. Histories and medical sources were reviewed on 3 October 2026.
For the graphic and totals, we retained only records with Irkutsk (IKT) as origin, an actual departure within the stated window and a landed status. Flightradar24 timestamps were converted from UTC to UTC+8. Duplicate flight IDs were removed. Unknown outcomes, scheduled-only entries, cancellations and diversions were excluded from these completed-route totals. Exclusion means insufficient evidence for this graphic, not that no flight took place.
We checked 149 candidate flight-number histories. Public lookback periods are limited and smaller regional services often lacked actual movement data. An initial rate limit was resolved by slowing the review, but we could not obtain a complete airport movement register. Other departures and destinations may therefore be missing, especially on 26 September and during the uncertain overnight death interval. These limitations prevent us from describing the graphic as every outbound flight up to the moment of death.
The downloadable evidence file records coverage and exclusions. Airport coordinates come from OurAirports; geographic outlines from Natural Earth. Both geographic datasets are public domain. Connecting arcs are illustrative. The historical feature has its own fixed research date; the incident summary and news feed elsewhere on this site update separately.
Cities and destinations to watch for official follow-up
The destinations below are an editorial list for following health-authority statements, airline notices and any later confirmed travel links. Listing a place does not designate it as exposed, infected or at elevated risk. No evidence reviewed for this feature establishes spread along these routes.
Russia
Blagoveshchensk · Chita · Kazan · Khabarovsk · Krasnoyarsk · Mirny · Moscow · Novosibirsk · Omsk · Petropavlovsk-Kamchatsky · Samara · St Petersburg · Talakan oil field · Tomsk · Ufa · Ulan-Ude · Vladivostok · Yakutsk · Yekaterinburg
China
Beijing · Guangzhou · Harbin · Sanya · Shanghai
Kyrgyzstan
Osh
Mongolia
Ulaanbaatar
Thailand
Bangkok · Phuket
Uzbekistan
Namangan · Tashkent
Vietnam
Nha Trang / Cam Ranh
Watch for a named flight and date linked by a public health authority to a confirmed case or a contact investigation. Until then, the route list supports further reporting, not travel restrictions or a forecast of disease spread. An unlisted destination may simply lack usable public flight records.