Trans-Ulgii

active
IATA: QU ICAO: UTN Callsign: TRANS-ULGII Country: Mongolia
Stub Profile (5 of 6 facts) As of 2026-10-08

Not yet researched. This carrier record is currently catalogued from seed civil aviation registry data. Full historical verification and lineage tracking remain pending.

Key Facts: Trans-Ulgii

  • Trans-Ulgii was established in Mongolia.
  • The carrier currently holds active operating status.
  • Aviation authorities assigned IATA code QU and ICAO code UTN.
  • Air traffic control utilized the radio callsign TRANS-ULGII.
  • Observed registry airframe records document 1 aircraft.
  • Operates a scheduled route network connecting 3 catalogued commercial destinations.

Carrier Identity & Specifications

Legal / Trading Name Trans-Ulgii
Operating Status active Source: observed_fleet_gt_zero
Country of Registry Mongolia
IATA Two-Letter Code QU
ICAO Three-Letter Code UTN
Telephony Callsign TRANS-ULGII

Observed Fleet Data

Observed registry records account for 1 aircraft as of 2026-10-08.

Route Network & Served Destinations

Scheduled flight network and destination directory for Trans-Ulgii.

3 Destinations
3 Airports Served
2 Countries Reached
2 Direct Flight Pairs
1+ Primary Bases / Hubs
IEV to VKO LWO to VKO Kiev Zhuliany International Airport (IEV / UKKK) Kiev, Ukraine Lviv International Airport (LWO / UKLL) Lvov, Ukraine Vnukovo International Airport (VKO / UUWW) Moscow, Russia
Primary Hub / Base Airport
Served Destination Airport
Direct Flight Route

All Served Airports & Cities (3)

Filter destinations by airport name, three-letter IATA code, city, or destination country.

Code Airport Name City / Region Country Coordinates
IEV UKKK
Kiev Zhuliany International Airport Kiev Ukraine 50.40N, 30.45E
LWO UKLL
Lviv International Airport Lvov Ukraine 49.81N, 23.96E
VKO UUWW
Vnukovo International Airport Moscow Russia 55.59N, 37.26E

Data Provenance & Audit Trail

  • Seed Source: Civil aviation registry baseline (OpenFlights / ICAO / Wikidata CC0).
  • Observed Fleet: Observation logs as of 2026-10-08.
  • Operational Status: Audited under rule pipeline (observed_fleet_gt_zero).
  • Last Pipeline Build: 2026-10-08.