Natakhtari Airfield
Open-knowledge reference entry
Natakhtari Airfield (ICAO: UGSA) is a domestic airport located in Natakhtari, Mtskheta-Mtianeti, Georgia. It serves as a secondary and domestic-only airfield for the Tbilisi metropolitan area at roughly 20 kilometres (12 mi) north of the city. It is privately owned and operated by the parent company of Vanilla Sky Airlines, Service Air. The airfield operates a bus link with Tbilisi in connection with scheduled flights.
General
Natakhtari Airfield is located about 9 kilometres (5.6 mi) north of Georgia's historic capital, Mtskheta, a popular tourist destination. Located in the Mukhrani Valley, it serves private flights and a number of small-scale charter and scheduled domestic flights by Vanilla Sky Airlines. Apart from providing a bus service with Tbilisi in connection with scheduled flights, the airfield is also easily accessible by car: it is located on the S3 highway to Russia and nearby S1 to the west of the country.
The airfield got a new concrete paved runway in mid-2011, and it was expanded with a restaurant and swimming pool on the property during this period to make it attractive for a family day out around the flight services the airfield provides. Sightseeing flights with a helicopter or a Cessna plane are also offered from the airport.
Since the end of 2010, flights have been operating between Natakhtari and Mestia, in the northwestern mountain region of Svanetia.
Begin with the source’s own compact description: “Natakhtari Airfield” is open-knowledge reference entry. The dossier treats that line as a proposition to test through Natakhtari, Airfield and Open-knowledge, not as a finished interpretation.
Why this record matters
The phrase “open-knowledge reference entry” supplies a clear boundary for inquiry. It also exposes the unanswered questions: who defined that boundary, when it became stable and which sources sit outside it.
Named sources, stable identifiers and responsible institutions provide the strongest route from overview to verifiable evidence. The source revision retrieved here is dated Jul 7, 2026. The linked authority identifier is Q24265446. Authority coordinates are 41.921, 44.714. 1 of 1 selected statements include explicit references; 0 carry qualifiers and 0 use preferred rank. The first chronological checks are 2011 and 2010.
Overview language is designed for orientation and should not be treated as a substitute for the evidence cited beneath it. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “Natakhtari Airfield”, its source revision and the description used here.
- Expand the search: follow Natakhtari Airfield primary sources, Natakhtari Airfield archive and Natakhtari research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Natakhtari Airfield”?
- Which institution is responsible for the underlying evidence?
- Which cited source is closest to the event, object or claim?
Search terms from this dossier
This entry incorporates text from “Natakhtari Airfield” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.