Hello,
I’m checking flights for QATAR 8408 to occur in 18th May, I was expection 2 flights for that that.
One from DOH to ALA and another from ALA to HKG.
FlightAware only detects one flight from DOH to HKG.
Other flight trackers shows that information, as you can check by this printscreen:
Why this is happening? How can I treat these cases?
Thanks.
If a flight has multiple legs endpoints like FindFlight can be used to identify potential linked individual flights between multiple airports by providing an origin and destination.
Hi @dogrock.
This is the response from FlightInfoStatus fregarding 18th May.
{
"ident": "QTR8408",
"faFlightID": "QTR8408-1557984391-airline-0441",
"airline": "QTR",
"airline_iata": "QR",
"flightnumber": "8408",
"tailnumber": "A7-BGA",
"type": "Form_Airline",
"blocked": false,
"diverted": false,
"cancelled": false,
"origin": {
"code": "OTHH",
"city": "Doha",
"alternate_ident": "DOH",
"airport_name": "Hamad Int'l"
},
"destination": {
"code": "VHHH",
"city": "Hong Kong",
"alternate_ident": "HKG",
"airport_name": "Hong Kong Int'l"
},
"filed_ete": 27600,
"filed_airspeed_kts": 444,
"distance_filed": 3913,
"filed_departure_time": {
"epoch": 1558202400,
"tz": "+03",
"dow": "Saturday",
"time": "21:00",
"date": "05/18/2019",
"localtime": 1558213200
},
"estimated_departure_time": {
"epoch": 1558202601,
"tz": "+03",
"dow": "Saturday",
"time": "21:03",
"date": "05/18/2019",
"localtime": 1558213401
},
"actual_departure_time": {
"epoch": 1558202601,
"tz": "+03",
"dow": "Saturday",
"time": "21:03",
"date": "05/18/2019",
"localtime": 1558213401
},
"departure_delay": -480,
"filed_arrival_time": {
"epoch": 1558230000,
"tz": "HKT",
"dow": "Sunday",
"time": "09:40",
"date": "05/19/2019",
"localtime": 1558258800
},
"estimated_arrival_time": {
"epoch": 1558229520,
"tz": "HKT",
"dow": "Sunday",
"time": "09:32",
"date": "05/19/2019",
"localtime": 1558258320
},
"actual_arrival_time": {
"epoch": 1558229107,
"tz": "HKT",
"dow": "Sunday",
"time": "09:25",
"date": "05/19/2019",
"localtime": 1558257907
},
"arrival_delay": -1493,
"status": "Arrived / Gate Arrival",
"progress_percent": 100,
"aircrafttype": "B744",
"full_aircrafttype": "B744",
"adhoc": false
},
Is there any property that indicates my that this flight has any possible leg? Cause I’m requesting only FlightInfoStatus in my application. I don’t want to duplicate requests just to find if the given flight has any leg…
Thanks.
Can anyone help me clarifying my question?
A flight returned in FlightInfoStatus is a single leg.
In the case of a flight that actually has a stop in the middle (such as the DOH to ALA and then ALA to HKG example) there will be two distinct flights each with their own flight number. This is where FindFlight can be helpful. By searching for onestop flights between DOH and HKG it will return sets of paired flights that could match.
Alternately, nonstop from DOH to ALA can be searched to return flights that operate on that segment.
That said it looks like QTR8408 is normally only associated with the nonstop DOH to HKG route. I can’t speak for other trackers placing it on a onestop route via ALA.
Hi @dogrock,
Thanks again for your support.
I stiil have doubts on this question:
because the flight I’ve mentioned had the same flight number. It operated as QTR8408. So this case confused me and I still don’t get it and how to check if a Flight has possible legs or not, without firstly, for each flight, check another API method “FindFlight” 
Can anyone assist?
Thanks
Hello again,
Can any Flightware staff assist on my last question?
I dind’t get it what @dogrock, because, I’m talking about a flight with a same flight number, for same day: QTR8408.
Also, do I have to request via FindFlight method, firstly every flight , to check if it has any possible legs?
Do I have any other alternative to avoid doing , for most flights, unnecessary requests?
Thanks
It looks like both variants (direct and two-leg) of QTR8408 are being tracked and are now showing up in FlightXML and in the web view.
https://flightaware.com/live/flight/QTR8404/history
It looks like schedules for the DOH-ALA route were not well published until July, but is now well tracked.
The ALA-HKG route is normally tracked as position-only and doesn’t appear to be acknowledged as ticketed/scheduled flight in QTR’s public booking system. The in progress ALA-HKG flight will not normally appear in XML results until after completion unless position-only flights are enabled on your account.
@dogrock thank you.
Now it’s way better since I don’t have to ask Find Flight to find possible two leg flights.