Change in historic flights

dbfvmarketingbi · June 24, 2020, 4:18pm

Hi,

when retriving data twice bei flightnumber, I get for the same day differnt results for same flightnumber and departure day.

Eg.: DLH1035 querried on 15.06.2020 21:05:55 FRA local time and 22.06.2020 21:07:02 FRA local time
with the first querry we got flights

FromCode	ToCode	FlightNumber	STD
LFPG	EDDF	DLH1035	17.06.2020 16:00
LFPG	EDDF	DLH1035	12.06.2020 15:50
LFPG	EDDF	DLH1035	09.06.2020 15:50

for the latter we got:

FromCode	ToCode	FlightNumber	STD
LFPG	EDDF	DLH1035	17.06.2020 15:50
LFPG	EDDF	CLH1035	16.06.2020 15:50
LFPG	EDDF	DLH1035	15.06.2020 15:50
LFPG	EDDF	CLH1035	14.06.2020 15:50
LFPG	EDDF	CLH1035	13.06.2020 15:50
LFPG	EDDF	CLH1035	12.06.2020 16:00
LFPG	EDDF	DLH1035	12.06.2020 15:50
LFPG	EDDF	CLH1035	11.06.2020 15:50

the querry at 2020-06-15 did not report eg. flight on 2020-06-14
but the querry at 2020-06-22 did report it.

Is there a time of querry when to be sure, that all flights flown will be in database?

Example Code:
FlightXML2b flightxml = new FlightXML2b();
ArrayOfFlightInfoStatusStruct fis = flightxml.FlightInfoStatus(“DLH1035”, 15, 1);

best regards
Olaf

dogrock · June 25, 2020, 8:17pm

It looks like this was the result of automatic codeshare matching performed by the API. Schedule data indicated that once a week Lufthansa Cityline (CLH) would operate the Lufthansa mainline (DLH) flight staring on June 20th. After that date the codeshare to CLH was automatically returned by the API. This revealed old, but already existing, flights that match the codeshare lookup.

dbfvmarketingbi · June 26, 2020, 7:10am

We assume, that flight DLH1035 actually took place at 2020-06-14, since it was bookable up to that day. Our question is, it was not reported in the querry on 2020-06-15 but it was reported with the querry at 2020-06-22

Actually this flight is in my opinion not a codeshare, it is never published to the custumer as a CLH flight. I assume that CLH is aircraft owner, since CLH (Lufthansa Cityline) is a 100% subsidiary of DLH (Lufthansa Airlines)

This was just one example. We experienced an increase in number of flights by 10%.

dbfvmarketingbi · November 27, 2020, 1:14pm

FlightXML2b flightxml = new FlightXML2b();
ArrayOfFlightInfoStatusStruct fis = flightxml.FlightInfoStatus(“DLH1035”, 15, 1);

We did querry twice first on 15th of June and than sencond as 22nd of June. The first querry resulted in two historic flights, which are should have taken place at nineth and twelveth of June. The same querry seven days later showed an additional flight on eleventh of June and also an different operational carrier (Lufthansa City Line)

dogrock · November 30, 2020, 10:16pm

This is a limitation on how the automatic codeshare lookup is performed. Flight DLH1035 was occasionally operated under the City Line name (CLH1035). When the codeshare was active a search for DLH1035 would return both DLH1035 and CLH1035 results.

Whether or not a codeshare may be active can be anticipated by using AirlineFlightSchedules. When looking up a flight it will return multiple results that refer back to a common “actual_ident” that as the operating carrier in the codeshare relationship. The related entries will have the same origin/destination/departure time. However, this specific arrangement hasn’t occurred since June.