Masterthread Registration-Suche
- Starter*in bursche99
- Datum Start
ANZEIGE
16Right - Historical ACARS Search
If you're interested, we've listed a bunch of sources in post #6 in this thread, including the one where I found your flight.
Did you know that on DFLD and EANS you can also view flight tracks for a specific day, including flights that you cannot find using the airport search function?
Flight tracks
www.eans.net
Flugspuren
www.dfld.de
You have to tick the follwoing
I found here some flights with callsign AF74xxx, which I guess are your flights because I found them on EANS CDG and DLFD BSL.
Given that and that AF0748 stayed in BSL overnight (noticed that in FP winter 2014/2015) and went back to CDG on next morning as AF0741 then
2014-04-28 AF7748 CDG BSL 1850 2013 AT75 fakepcy should be (DLFD BSL 29.04.2014)
For 2014-04-18 AF7745 BSL CDG 1347 1510 AT75 fakepcy I'm not if for AF7744 is really the incoming flight for AF7745 when I see the times according to the timetable
Interesting, I never knew that since I'm still new to the site. Thank you for the tip!Did you know that on DFLD and EANS you can also view flight tracks for a specific day, including flights that you cannot find using the airport search function?
Flight tracks
Flugspuren
You have to tick the follwoing
Anhang anzeigen 328077
I found here some flights with callsign AF74xxx, which I guess are your flights because I found them on EANS CDG and DLFD BSL.
Given that and that AF0748 stayed in BSL overnight (noticed that in FP winter 2014/2015) and went back to CDG on next morning as AF0741 then
2014-04-28 AF7748 CDG BSL 1850 2013 AT75 fakepcy should be (DLFD BSL 29.04.2014)
Anhang anzeigen 328079
For 2014-04-18 AF7745 BSL CDG 1347 1510 AT75 fakepcy I'm not if for AF7744 is really the incoming flight for AF7745 when I see the times according to the timetable
based on Sascha's screenshot and the associated flight numbers, this could be a match, yet the layover in PMI seems quite long
AB9332 / HF9253 13:45 HAM to PMI ~16:00
AB9333 / HF9254 20:05 PMI to HAM
4 hours layover is long... though its March.
but it's too short to fit in additional flights.
found 2007-03-10 X39254 PMI HAM 2005 2250 fakepcy D-ABDM #8406
D-ABDM (A320 AB) 1009 20070310 AB9332 (HAM-PMI) [EDDH/HAM]
Zuletzt bearbeitet:
Hi @SaschaX99, what resources did you use for YVR flights in the early 2000s? I remember seeing you solve some on the other forum.
2000-08-04 AC0161 YYZ YVR ---- ---- fakepcy
2000-08-04 AC1545 YVR SEA ---- ---- fakepcy
Hoping to solve these too, thank you in advance.
2000-08-04 AC0161 YYZ YVR ---- ---- fakepcy
2000-08-04 AC1545 YVR SEA ---- ---- fakepcy
Hoping to solve these too, thank you in advance.
This one
you have to scroll to the bottom for other months.
T
1999-07-17 AC0869 LHR YYZ ---- ---- B762 fakepcy
I tried looking for its tail number, but only saw the ones for July 16 and 18.
Thank you, I actually used that earlier but they didn't have the YVR area in August 2000. There's another flight which is supposed to be easy to solve, but their flight fell on the only day ACARS wasn't recording...
1999-07-17 AC0869 LHR YYZ ---- ---- B762 fakepcy
I tried looking for its tail number, but only saw the ones for July 16 and 18.
T
Thank you, I actually used that earlier but they didn't have the YVR area in August 2000. There's another flight which is supposed to be easy to solve, but their flight fell on the only day ACARS wasn't recording...
1999-07-17 AC0869 LHR YYZ ---- ---- B762 fakepcy
I tried looking for its tail number, but only saw the ones for July 16 and 18.
Maybe this as outgoing flight?
ACARS Log for 16/7 from Wigan, NW England
C-GDSP AC0868 21:02:41 16 Jul 1999
Wait, that could be because AC868 was a morning flight according to FlightMemory entries from that time. AC869 also departs the next morning. Thank you!
found 1999-07-17 AC0869 LHR YYZ ---- ---- fakepcy C-GDSP #8413
confirmed by LHR-LGW 1999-07-acars\199907.htm (original file name is july1999.htm)
I'm surprised you didn't query this as first source)
868 inbound on 16 -> DSP
869 return 17 -> DSP
...
You have to tick the follwoingFlugspuren
Anhang anzeigen 328077
I found here some flights with callsign AF74xxx, which I guess are your flights because I found them on EANS CDG and DLFD BSL.
...
For 2014-04-18 AF7745 BSL CDG 1347 1510 AT75 fakepcy I'm not if for AF7744 is really the incoming flight for AF7745 when I see the times according to the timetable
I found these pairs (based on call sign, and filtered by type, ATR or Embraer) on both CDG and BSL:
F-GVZL AF741BC BSL 06:52:05 – 07:13:59 take off
F-GVZL AF741BC CDG 07:45:52 – 08:07:01 landing
F-GVZN AF331WG BSL 06:38:26 – 07:03:42 take off
F-GVZN AF331WG CDG 07:34:03 – 07:41:05 landing
F-GVZL AF742RY CDG 09:24:26 – 09:31:50 take off
F-GVZL AF742RY / 1000 BSL 10:03:41 – 10:25:07
F-GVZL AF743BC BSL 11:14:43 – 11:31:26 take off
F-GVZL AF743BC CDG 12:04:45 – 12:27:52 landing
D-AMGL AF744RY CDG 13:39:01 – 13:48:17 take off
D-AMGL AF744RY / 1000 RH1 BSL 14:06:13 – 14:28:29
1. F-GVZL came as AF742 and left as AF743
(CDG-BSL-CDG)2. D-AMGL came as AF744 from CDG to BSL
... and no sign of leaving 
3. the AF744 CDG BSL actual is delayed 14:06:13 – 14:28:29 arrival
yet it would still somewhat fit to the schedule of AF7745 BSL CDG 1347 15104. D-AMGL is Bae146 not AT72
Up until here, I conclude D-AMGL would be the inbound and thus return flight AF7745 @fakepcy is looking for
Now, what bothers me is that it left BSL 2,5 hours later as AF747
D-AMGL AF747BC BSL 16:54:01 – 17:02:55
D-AMGL AF747BC CDG 17:34:26 – 17:54:00 landing
thus the question is:
- does it arrive as 744 and leave only late as 747 ?
- or would it eventually rotate 2x on CDG-BSL as 744-745-746-747
Thank you, I actually got F-GVZL and F-GVZN but some tracks in Paris and Basel overlapped and I can't tell which flights they were. They also did ORY-MLH-ORY which confused me at first since BSL has other codes too. I'll try to deal with that again when I have time.I found these pairs (based on call sign, and filtered by type, ATR or Embraer) on both CDG and BSL:
F-GVZL AF741BC BSL 06:52:05 – 07:13:59 take off
F-GVZL AF741BC CDG 07:45:52 – 08:07:01 landing
F-GVZN AF331WG BSL 06:38:26 – 07:03:42 take off
F-GVZN AF331WG CDG 07:34:03 – 07:41:05 landing
F-GVZL AF742RY CDG 09:24:26 – 09:31:50 take off
F-GVZL AF742RY / 1000 BSL 10:03:41 – 10:25:07
F-GVZL AF743BC BSL 11:14:43 – 11:31:26 take off
F-GVZL AF743BC CDG 12:04:45 – 12:27:52 landing
D-AMGL AF744RY CDG 13:39:01 – 13:48:17 take off
D-AMGL AF744RY / 1000 RH1 BSL 14:06:13 – 14:28:29
1. F-GVZL came as AF742 and left as AF743
2. D-AMGL came as AF744 from CDG to BSL
3. the AF744 CDG BSL actual is delayed 14:06:13 – 14:28:29 arrival
4. D-AMGL is Bae146 not AT72
Up until here, I conclude D-AMGL would be the inbound and thus return flight AF7745 @fakepcy is looking for
Now, what bothers me is that it left BSL 2,5 hours later as AF747
D-AMGL AF747BC BSL 16:54:01 – 17:02:55
D-AMGL AF747BC CDG 17:34:26 – 17:54:00 landing
thus the question is:
- does it arrive as 744 and leave only late as 747 ?
- or would it eventually rotate 2x on CDG-BSL as 744-745-746-747
the more I dig for this flight, the more likely it seems to me -> 745 746 did not exist / fly on this day & season
AF741BC morning flight ~7:00
AF742RY moring flight ~9:00
AF743BC midday ~12
AF744RY midday flight ~ 14:00
AF747BC afternoon ~17:00
AF774NO evening flight ~20:00
I searched March, April and May data, not a single trace of .45 (same for flightmemory, shows Jan 14 and July 14 again)
And: all these regional aircrafts got tracked, we cannot even assume that track was missed due to small regional aircraft, the tracks go back and forth and are conclusive.
Zuletzt bearbeitet:
Here an excerpt from BSL 04.04.2014 which shows that the flights at least existed
Daily flight plan, Arrivals Friday 04/04/2014
17:20 PARIS-CDG AIR FRANCE AF7746 Landed 17:31
Daily flight plan, Departures Friday 04/04/2014
13:45 PARIS-CDG Departed 14:22
AIR FRANCE AF7745
KLM KL2305
AIR MAURIC MK9023
But when I see the timetable (winter 14/15) and compare the times with BSL 04.04.2014 then it seems that they change the aircrafts to CDG and ORY in BSL. Unfortunately this means that also my find for 28.04.2014 is not longer sure.