TAIS CRS Web Service User Manual
Contents |
Preface
TAIS CRS Web Services (TCWS) is a standard interface implementing the most important functions of TAIS CRS (legacy name Sirena-2.3). A similar product is available for TAIS DCS (legacy name Regina). At the moment, the following features of TAIS CRS are supported:
- Search Availability
The interface can be used for various purposes, for example:
- implementation of various booking and ticketing processes
- automation of inventory management operations
- business intelligence
TCWS Basics. Test and Production Systems. WSDL and Endpoints
TCWS is a SOAP server. Access to Test (Integration) and Production Systems is provided to each customer. You will receive URLs (“WebServiceURL” in the examples below), and possibly Login + Password for http authentication (depending on security level agreed on). At the moment, TAIS doesn’t employ WS Security.
Once having access to Test or Production System, you can readily request WSDL. Such request follows the standard pattern:
WebServiceURL/sigws/Action/SIRENA.ReqRootElement/SIRENA.ResRootElement?WSDL
where:
WebServiceURL – customer-specific part of WSDL address
Action – operation name
ReqRootElement – name of request root element (the one immediately following the <soapenv:Body> tag)
ResRootElement – name of response root element (the one immediately following the <soapenv:Body> tag)
For example:
https://sigtest.tais.ru/sigws/SciGetPNR/SIRENA.SCILOCATOR/SIRENA.SCIPNR?WSDL
or
http://109.73.1.66:23002/cgi/sirena23.cgi/sigws/SciGetPNR/SIRENA.SCILOCATOR/SIRENA.SCIPNR?WSDL
Below is a table of supported operations and the related root elements.
# |
Action |
ReqRootElement |
ResRootElement |
Comment |
1 |
SciGetAvailabiltiy |
SCIAVLQRY |
SCIAVLRPL |
OW or RT availability search for a city pair |
WSDL advises the endpoint location and provides the essential information regarding the request and response format. The endpoint address is constructed as follows:
WebServiceURL/sigws/Action.wsdl
Following the examples above, the endpoint addresses would be:
https://sigtest.tais.ru/sigws/SciGetPNR.wsdl
or
http://109.73.1.66:23002/cgi/sirena23.cgi/sigws/SciGetPNR.wsdl
A sample request sent to the first endpoint of the above might look as follows:
<soapenv:Header/>
<soapenv:Body>
<sir:SIRENA.SCILOCATOR>
<!--Zero or more repetitions:-->
<sir:LOCATOR>
<sir:LOCATOR>E1IWNI</sir:LOCATOR>
</sir:LOCATOR>
</sir:SIRENA.SCILOCATOR>
</soapenv:Body>
</soapenv:Envelope>
Understanding Format Descriptions in this Document
What you will find below is mainly description of xml requests and responses. As TCWS is virtually attribute-free, it will be mainly description of elements. The description always begins with the root element and then either lists the immediate child elements either by reference (E1_2) or complete explanation. In either case, the list of child elements looks as follows:
Name |
Type |
ST |
RP |
Comment |
AVLQRY |
n/a |
M |
1 |
See below E1_2) |
where:
Name – element name
Type – element data type (in xsd terms)
ST – element status (M – mandatory, O – optional)
RP – maximum number of repetitions (blank – unlimited)
Comment – for elements that do have child elements, this will show reference to element’s own description (like in the example above, where AVLQRY has child elements). For elements that don’t have child elements, complete description is provided, for example:
Name |
Type |
ST |
RP |
Comment |
DEPPOINT |
string |
M |
1 |
Departure city or airport code. Use IATA or STC (TCH) code. Specifying part of the name (Russian or English) is also allowed. |
As this document is aimed at both Cyrillic and English users, code sets in both languages are provided where applicable as follows:
Flight Type:
C |
E |
Explanation |
Н |
N |
only Non-stop flights |
П |
D |
only Direct flights |
where:
C – Cyrillic Code
E – English Code
Availability Search (SciGetAvailability)
Overview
SciGetAvailabiltiy returns flight availability for the specified search criteria.
The minimum set of the required data in the request includes Departure Point, Arrival Point, Departure Date. You can add other preferences as needed.
The response will contain schedule and availability data for all flights matching the filters. In addition, it will provide comprehensive reference data (full names and other details) on all Carriers, Equipment Types and Points present in the response.
WSDL
WSDL for SciGetAvailability is as follows:
WebServiceURL/sigws/SciGetAvailability/SIRENA.SCIAVLQRY/SIRENA.SCIAVLRPL?WSDL
Format
Request
E1_1) SIRENA.SCIAVAILQRY: The root element.
Attributes: none
Elements:
Name |
Type |
ST |
RP |
Comment |
AVLQRY |
n/a |
M |
1 |
See below E1_2) |
E1_2) AVLQRY: Group of search criteria.
Attributes: none
Elements:
Name |
Type |
ST |
RP |
Comment | ||||||||||||||||||||||||||||||||||||||||||
DEPPOINT |
string |
M |
1 |
Departure city or airport code. Use IATA or STC (TCH) code. Specifying part of the name (Russian or English) is also allowed. | ||||||||||||||||||||||||||||||||||||||||||
ARRPOINT |
string |
M |
1 |
Arrival city or airport code. Use IATA or STC (TCH) code. Specifying part of the name (Russian or English) is also allowed. | ||||||||||||||||||||||||||||||||||||||||||
ROUTETYPE |
string |
O |
1 |
Journey type: OW – one-way RT – round-trip | ||||||||||||||||||||||||||||||||||||||||||
DATEOUT |
dateTime |
M |
1 |
Departure date for outbound flight | ||||||||||||||||||||||||||||||||||||||||||
DATEBACK |
dateTime |
O |
1 |
Departure date for return flight. Use only if ROUTETYPE=’RT’ | ||||||||||||||||||||||||||||||||||||||||||
NODAYS |
short |
O |
1 |
Number of days to perform the search for. If specified, the search will be done for the range [DATEOUT; DATEOUT+NODAYS]. The same applies to DATEBACK | ||||||||||||||||||||||||||||||||||||||||||
NOSEATS |
short |
O |
1 |
Number of seats. Flights / RBD with availability less than NOSEATS will be excluded from the response | ||||||||||||||||||||||||||||||||||||||||||
TIMEOUTMIN TIMEOUTMAX |
long |
O |
1 |
Departure time range for outbound flight. Provide range limits as numbers of seconds after 00:00 of DATEOUT | ||||||||||||||||||||||||||||||||||||||||||
TIMEBACKMIN TIMEBACKMAX |
long |
O |
1 |
Departure time range for return flight. Provide range limits as numbers of seconds after 00:00 of DATEBACK | ||||||||||||||||||||||||||||||||||||||||||
AK |
string |
O |
1 |
Carrier code. Use IATA or STC (TCH) code. | ||||||||||||||||||||||||||||||||||||||||||
SERVCLASS |
string |
O |
1 |
Service class code: П/Б/Э F/C/Y (only for English users!) | ||||||||||||||||||||||||||||||||||||||||||
DIRECTONLY |
short |
O |
1 |
obsolete | ||||||||||||||||||||||||||||||||||||||||||
FLAGS |
string |
O |
1 |
Additional preferences (modifiers of СМ/AD entry in TAIS CRS). Provide as many modifiers as needed without separators (e.g., ‘NO’). Please note that in the explanation below both Cyrillic (C) and English (E) codes are provided. Cyrillic codes are available to all users. English codes are available only to English users!
|
Response
E1_21) SCIAVLRPL: The root element.
Attributes: none
Elements:
Name |
Type |
ST |
RP |
Comment |
AVLQRY |
n/a |
M |
1 |
See below E1_22) |
COMPANYLKP |
n/a |
M |
|
Carrier reference data. For explanation, please refer to the relevant sciWhat section (TBA) |
FLIGHT |
n/a |
M |
|
See below E1_23) |
FLIGHTAVL |
n/a |
M |
|
See below E1_24) |
PLANETYPELKP |
n/a |
M |
|
Equipment Type reference data. For explanation, please refer to the relevant sciWhat section (TBA) |
TOWN |
n/a |
M |
|
Point reference data. For explanation, please refer to the relevant sciWhat section (TBA) |
E1_22) AVLQRY: Information on usage of external (in relation to TAIS CRS) availability sources.
Attributes: none
Elements:
Name |
Type |
ST |
RP |
Comment |
RSSLINKDOWN |
short |
M |
1 |
Gallileo RSS link availability flag 0 – link available 1 – link down
|
E1_23) FLIGHT: Schedule and general data for a flight.
Attributes: none.
Elements:
Please note that code sets used in the response will depend on your language settings. For Cyrillic users, STC (TCH) Cyrillic codes will be used if available. If not, IATA codes will be used. For English users, the response will always show IATA codes.
Name |
Type |
ST |
RP |
Comment | ||||||||||||
ORDERNO |
short |
M |
1 |
First part of the unique FLIGHT element reference within the response. The complete reference consists of ORDERNO and POSINROUTE. When a connection (two or more connecting flights) is returned in the response, all flights of the connection have the same ORDERNO but different POSINROUTE (see below). | ||||||||||||
POSINROUTE |
short |
M |
1 |
Second part of the unique FLIGHT element reference within the response. The complete reference consists of ORDERNO and POSINROUTE. When a connection (two or more connecting flights) is returned in the response, all flights of the connection have the same ORDERNO but different POSINROUTE (see below). POSINOUTE numbering begins with 1. For direct flights, this element value is always 0. | ||||||||||||
AK |
string |
M |
1 |
Marketing carrier code | ||||||||||||
OAK |
string |
O |
1 |
Operating carrier code (for code-share flights only) | ||||||||||||
FLIGHTNO |
string |
M |
1 |
Flight number | ||||||||||||
DEPDATE |
date |
M |
1 |
Departure date | ||||||||||||
TOS |
string |
O |
1 |
Type of service:
| ||||||||||||
PLANETYPE |
string |
M |
|
Equipment type | ||||||||||||
DEPARPT |
string |
M |
|
Departure airport code | ||||||||||||
DEPTERM |
string |
O |
|
Departure terminal code | ||||||||||||
ARRARPT |
string |
M |
|
Arrival airport code | ||||||||||||
ARRTERM |
string |
O |
|
Arrival terminal code | ||||||||||||
DEPTIME |
long |
M |
|
Departure time. Number of seconds after 00:00:00 of DEPDATE | ||||||||||||
ARRTIME |
long |
M |
|
Arrival time. Number of seconds after 00:00:00 of DEPDATE | ||||||||||||
CHECKINTIME |
long |
M |
|
Check-in start time. Number of seconds after 00:00:00 of DEPDATE | ||||||||||||
DEPTIMEGMT |
long |
M |
|
Departure time in GMT/UTC. Number of seconds after 00:00:00 of DEPDATE. Can be negative. | ||||||||||||
ARRTIMEGMT |
long |
M |
|
Arrival time in GMT/UTC. Number of seconds after 00:00:00 of DEPDATE. Can be negative. | ||||||||||||
NOSTOPS |
short |
O |
|
Number of intermediate stops. This is used only for flights with the same flight number and one or several scheduled landings in the route. Not to be confused with connections, which consist of different flight numbers and therefore are shown as separate FLIGHT elements. | ||||||||||||
MEAL |
string |
O |
1 |
Currently not used | ||||||||||||
INVGRD INVORG |
string string |
O |
1 |
Code of the flight inventory system (e.g., MUC1A). Normally blank for TAIS-hosted airline projects. | ||||||||||||
ACCESSLEVEL |
short |
M |
1 |
Flight inventory access level (for booking): 0 – unavailable 1 – standard (teletype) 2 – interactive 3 – local TAIS CRS host | ||||||||||||
LINKSTATUS |
short |
M |
1 |
Flight availability source link status: 0 – no link 1 – link down 2 – link up 3 – local TAIS CRS host | ||||||||||||
AVLSOURCE |
short |
M |
1 |
Availability source type: 0 – no availability data 1– Segment AVS (offline data based on processing of teletype Availability Status Messages which tell that seats are available but don’t tell how many) 2– Numeric AVS (offline data based on processing of teletype Availability Status Messages which tell how available but don’t tell how many) 3 – cached real-time data from airline host 4 – real-time data from airline host |
E1_24) FLIGHTAVL: Availability data for one booking class (RBD).
Attributes: none.
Elements:
Please note that code sets used in the response will depend on your language settings. For Cyrillic users, STC (TCH) Cyrillic codes will be used if available. If not, IATA codes will be used. For English users, the response will always show IATA codes.
Name |
Type |
ST |
RP |
Comment |
ORDERNO |
short |
M |
1 |
First part of the unique reference to the FLIGHT element within the response.
|
POSINROUTE |
short |
M |
1 |
Second part of the unique reference to the FLIGHT element within the response
|
RBD |
string |
M |
1 |
Booking class |
SERVCLASS |
string |
M |
1 |
Service class |
NOSEATS |
string |
M |
1 |
Seat availability 1-9 – no less than the number of seats shown 0 – no seats, waitlist open R – on request С – no seats, waitlist open X – flight/class canceled |
Examples
Request
<soapenv:Header/>
<soapenv:Body>
<sir:SIRENA.SCIAVLQRY>
<!--Zero or more repetitions:-->
<sir:AVLQRY>
<sir:AK>KK</sir:AK>
<sir:ARRPOINT>IST</sir:ARRPOINT>
<sir:DATEOUT>2013-11-01T00:00:00</sir:DATEOUT>
<sir:DEPPOINT>ADA</sir:DEPPOINT>
</sir:AVLQRY>
</sir:SIRENA.SCIAVLQRY>
</soapenv:Body>
</soapenv:Envelope>
Response
<soapenv:Header/>
<soapenv:Body>
<nssig:SCIAVLRPL>
<nssig:AVLQRY>
<nssig:RSSLINKDOWN>0</nssig:RSSLINKDOWN>
</nssig:AVLQRY>
<nssig:COMPANYLKP>
<nssig:AK>KK</nssig:AK>
<nssig:CRTCODE/>
<nssig:IATACODE>KK</nssig:IATACODE>
<nssig:NAME>ATLASJET</nssig:NAME>
<nssig:NAMEENG>ATLASJET</nssig:NAMEENG>
<nssig:PAXCODE>610</nssig:PAXCODE>
<nssig:USECARRIERIATACODE>1</nssig:USECARRIERIATACODE>
<nssig:USERBDIATACODE>1</nssig:USERBDIATACODE>
</nssig:COMPANYLKP>
<nssig:FLIGHT>
<nssig:ORDERNO>0</nssig:ORDERNO>
<nssig:POSINROUTE>0</nssig:POSINROUTE>
<nssig:ACCESSLEVEL>3</nssig:ACCESSLEVEL>
<nssig:AK>KK</nssig:AK>
<nssig:ARRARPT>IST</nssig:ARRARPT>
<nssig:ARRTERM/>
<nssig:ARRTIME>38100</nssig:ARRTIME>
<nssig:ARRTIMEGMT>30900</nssig:ARRTIMEGMT>
<nssig:AVLSOURCE>4</nssig:AVLSOURCE>
<nssig:CHECKINTIME>27300</nssig:CHECKINTIME>
<nssig:DEPARPT>ADA</nssig:DEPARPT>
<nssig:DEPDATE>2013-11-01T00:00:00.0Z</nssig:DEPDATE>
<nssig:DEPTERM/>
<nssig:DEPTIME>32700</nssig:DEPTIME>
<nssig:DEPTIMEGMT>25500</nssig:DEPTIMEGMT>
<nssig:FLIGHTNO>31</nssig:FLIGHTNO>
<nssig:INVGRD/>
<nssig:INVORG/>
<nssig:LINKSTATUS>3</nssig:LINKSTATUS>
<nssig:MEAL/>
<nssig:NOSTOPS>0</nssig:NOSTOPS>
<nssig:OAK/>
<nssig:PLANETYPE>320</nssig:PLANETYPE>
<nssig:ROUTETHERE>1</nssig:ROUTETHERE>
<nssig:TOS/>
</nssig:FLIGHT>
<nssig:FLIGHT>
<nssig:ORDERNO>1</nssig:ORDERNO>
<nssig:POSINROUTE>0</nssig:POSINROUTE>
<nssig:ACCESSLEVEL>3</nssig:ACCESSLEVEL>
<nssig:AK>KK</nssig:AK>
<nssig:ARRARPT>IST</nssig:ARRARPT>
<nssig:ARRTERM/>
<nssig:ARRTIME>81300</nssig:ARRTIME>
<nssig:ARRTIMEGMT>74100</nssig:ARRTIMEGMT>
<nssig:AVLSOURCE>4</nssig:AVLSOURCE>
<nssig:CHECKINTIME>69900</nssig:CHECKINTIME>
<nssig:DEPARPT>ADA</nssig:DEPARPT>
<nssig:DEPDATE>2013-11-01T00:00:00.0Z</nssig:DEPDATE>
<nssig:DEPTERM/>
<nssig:DEPTIME>75300</nssig:DEPTIME>
<nssig:DEPTIMEGMT>68100</nssig:DEPTIMEGMT>
<nssig:FLIGHTNO>35</nssig:FLIGHTNO>
<nssig:INVGRD/>
<nssig:INVORG/>
<nssig:LINKSTATUS>3</nssig:LINKSTATUS>
<nssig:MEAL/>
<nssig:NOSTOPS>0</nssig:NOSTOPS>
<nssig:OAK/>
<nssig:PLANETYPE>320</nssig:PLANETYPE>
<nssig:ROUTETHERE>1</nssig:ROUTETHERE>
<nssig:TOS/>
</nssig:FLIGHT>
<nssig:FLIGHTAVL>
<nssig:ORDERNO>0</nssig:ORDERNO>
<nssig:POSINROUTE>0</nssig:POSINROUTE>
<nssig:RBD>C</nssig:RBD>
<nssig:NOSEATS>2</nssig:NOSEATS>
<nssig:SERVCLASS>C</nssig:SERVCLASS>
</nssig:FLIGHTAVL>
<nssig:FLIGHTAVL>
<nssig:ORDERNO>0</nssig:ORDERNO>
<nssig:POSINROUTE>0</nssig:POSINROUTE>
<nssig:RBD>D</nssig:RBD>
<nssig:NOSEATS>2</nssig:NOSEATS>
<nssig:SERVCLASS>C</nssig:SERVCLASS>
</nssig:FLIGHTAVL>
<nssig:FLIGHTAVL>
<nssig:ORDERNO>0</nssig:ORDERNO>
<nssig:POSINROUTE>0</nssig:POSINROUTE>
<nssig:RBD>Y</nssig:RBD>
<nssig:NOSEATS>9</nssig:NOSEATS>
<nssig:SERVCLASS>Y</nssig:SERVCLASS>
</nssig:FLIGHTAVL>
<nssig:FLIGHTAVL>
<nssig:ORDERNO>0</nssig:ORDERNO>
<nssig:POSINROUTE>0</nssig:POSINROUTE>
<nssig:RBD>H</nssig:RBD>
<nssig:NOSEATS>9</nssig:NOSEATS>
<nssig:SERVCLASS>Y</nssig:SERVCLASS>
</nssig:FLIGHTAVL>
<nssig:FLIGHTAVL>
<nssig:ORDERNO>0</nssig:ORDERNO>
<nssig:POSINROUTE>0</nssig:POSINROUTE>
<nssig:RBD>L</nssig:RBD>
<nssig:NOSEATS>9</nssig:NOSEATS>
<nssig:SERVCLASS>Y</nssig:SERVCLASS>
</nssig:FLIGHTAVL>
<nssig:FLIGHTAVL>
<nssig:ORDERNO>0</nssig:ORDERNO>
<nssig:POSINROUTE>0</nssig:POSINROUTE>
<nssig:RBD>N</nssig:RBD>
<nssig:NOSEATS>9</nssig:NOSEATS>
<nssig:SERVCLASS>Y</nssig:SERVCLASS>
</nssig:FLIGHTAVL>
<nssig:FLIGHTAVL>
<nssig:ORDERNO>0</nssig:ORDERNO>
<nssig:POSINROUTE>0</nssig:POSINROUTE>
<nssig:RBD>G</nssig:RBD>
<nssig:NOSEATS>9</nssig:NOSEATS>
<nssig:SERVCLASS>Y</nssig:SERVCLASS>
</nssig:FLIGHTAVL>
<nssig:FLIGHTAVL>
<nssig:ORDERNO>0</nssig:ORDERNO>
<nssig:POSINROUTE>0</nssig:POSINROUTE>
<nssig:RBD>Q</nssig:RBD>
<nssig:NOSEATS>9</nssig:NOSEATS>
<nssig:SERVCLASS>Y</nssig:SERVCLASS>
</nssig:FLIGHTAVL>
<nssig:FLIGHTAVL>
<nssig:ORDERNO>0</nssig:ORDERNO>
<nssig:POSINROUTE>0</nssig:POSINROUTE>
<nssig:RBD>V</nssig:RBD>
<nssig:NOSEATS>9</nssig:NOSEATS>
<nssig:SERVCLASS>Y</nssig:SERVCLASS>
</nssig:FLIGHTAVL>
<nssig:FLIGHTAVL>
<nssig:ORDERNO>1</nssig:ORDERNO>
<nssig:POSINROUTE>0</nssig:POSINROUTE>
<nssig:RBD>C</nssig:RBD>
<nssig:NOSEATS>2</nssig:NOSEATS>
<nssig:SERVCLASS>C</nssig:SERVCLASS>
</nssig:FLIGHTAVL>
<nssig:FLIGHTAVL>
<nssig:ORDERNO>1</nssig:ORDERNO>
<nssig:POSINROUTE>0</nssig:POSINROUTE>
<nssig:RBD>D</nssig:RBD>
<nssig:NOSEATS>2</nssig:NOSEATS>
<nssig:SERVCLASS>C</nssig:SERVCLASS>
</nssig:FLIGHTAVL>
<nssig:FLIGHTAVL>
<nssig:ORDERNO>1</nssig:ORDERNO>
<nssig:POSINROUTE>0</nssig:POSINROUTE>
<nssig:RBD>Y</nssig:RBD>
<nssig:NOSEATS>9</nssig:NOSEATS>
<nssig:SERVCLASS>Y</nssig:SERVCLASS>
</nssig:FLIGHTAVL>
<nssig:FLIGHTAVL>
<nssig:ORDERNO>1</nssig:ORDERNO>
<nssig:POSINROUTE>0</nssig:POSINROUTE>
<nssig:RBD>H</nssig:RBD>
<nssig:NOSEATS>9</nssig:NOSEATS>
<nssig:SERVCLASS>Y</nssig:SERVCLASS>
</nssig:FLIGHTAVL>
<nssig:FLIGHTAVL>
<nssig:ORDERNO>1</nssig:ORDERNO>
<nssig:POSINROUTE>0</nssig:POSINROUTE>
<nssig:RBD>L</nssig:RBD>
<nssig:NOSEATS>9</nssig:NOSEATS>
<nssig:SERVCLASS>Y</nssig:SERVCLASS>
</nssig:FLIGHTAVL>
<nssig:FLIGHTAVL>
<nssig:ORDERNO>1</nssig:ORDERNO>
<nssig:POSINROUTE>0</nssig:POSINROUTE>
<nssig:RBD>N</nssig:RBD>
<nssig:NOSEATS>9</nssig:NOSEATS>
<nssig:SERVCLASS>Y</nssig:SERVCLASS>
</nssig:FLIGHTAVL>
<nssig:FLIGHTAVL>
<nssig:ORDERNO>1</nssig:ORDERNO>
<nssig:POSINROUTE>0</nssig:POSINROUTE>
<nssig:RBD>G</nssig:RBD>
<nssig:NOSEATS>9</nssig:NOSEATS>
<nssig:SERVCLASS>Y</nssig:SERVCLASS>
</nssig:FLIGHTAVL>
<nssig:FLIGHTAVL>
<nssig:ORDERNO>1</nssig:ORDERNO>
<nssig:POSINROUTE>0</nssig:POSINROUTE>
<nssig:RBD>Q</nssig:RBD>
<nssig:NOSEATS>9</nssig:NOSEATS>
<nssig:SERVCLASS>Y</nssig:SERVCLASS>
</nssig:FLIGHTAVL>
<nssig:FLIGHTAVL>
<nssig:ORDERNO>1</nssig:ORDERNO>
<nssig:POSINROUTE>0</nssig:POSINROUTE>
<nssig:RBD>V</nssig:RBD>
<nssig:NOSEATS>9</nssig:NOSEATS>
<nssig:SERVCLASS>Y</nssig:SERVCLASS>
</nssig:FLIGHTAVL>
<nssig:PLANETYPELKP>
<nssig:PLANETYPE>320</nssig:PLANETYPE>
<nssig:CRTCODE/>
<nssig:IATACODE>320</nssig:IATACODE>
<nssig:NAME>AIRBUS A320</nssig:NAME>
<nssig:NAMEENG>AIRBUS A320</nssig:NAMEENG>
<nssig:SHORTNAME>AIRBUS A320</nssig:SHORTNAME>
<nssig:SHORTNAMEENGL>AIRBUS A320</nssig:SHORTNAMEENGL>
</nssig:PLANETYPELKP>
<nssig:TOWNLKP>
<nssig:GRD>ADA</nssig:GRD>
<nssig:ARPTNAME>ADA</nssig:ARPTNAME>
<nssig:ARPTNAMEENGL>ADA</nssig:ARPTNAMEENGL>
<nssig:CITYNAME>ADANA</nssig:CITYNAME>
<nssig:CITYNAMEENGL>ADANA</nssig:CITYNAMEENGL>
<nssig:COUNTRY>TR</nssig:COUNTRY>
<nssig:CRTCODE/>
<nssig:IATACODE>ADA</nssig:IATACODE>
<nssig:IGNOREDST>0</nssig:IGNOREDST>
<nssig:LOCATEDIN>ADA</nssig:LOCATEDIN>
<nssig:PTYPE>CA</nssig:PTYPE>
<nssig:REGION/>
<nssig:TIMEZONE>TR</nssig:TIMEZONE>
</nssig:TOWNLKP>
<nssig:TOWNLKP>
<nssig:GRD>IST</nssig:GRD>
<nssig:ARPTNAME>ATATURK</nssig:ARPTNAME>
<nssig:ARPTNAMEENGL>ATATURK</nssig:ARPTNAMEENGL>
<nssig:CITYNAME>ISTANBUL</nssig:CITYNAME>
<nssig:CITYNAMEENGL>ISTANBUL</nssig:CITYNAMEENGL>
<nssig:COUNTRY>TR</nssig:COUNTRY>
<nssig:CRTCODE/>
<nssig:IATACODE>IST</nssig:IATACODE>
<nssig:IGNOREDST>0</nssig:IGNOREDST>
<nssig:LOCATEDIN>IST</nssig:LOCATEDIN>
<nssig:PTYPE>CA</nssig:PTYPE>
<nssig:REGION/>
<nssig:TIMEZONE>TR</nssig:TIMEZONE>
</nssig:TOWNLKP>
</nssig:SCIAVLRPL>
</soapenv:Body>
</soapenv:Envelope>