ANZEIGE
Effective May 15, 2017
HONOLULU ↔ KONA | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Zuletzt bearbeitet:
Masterthread Registration-Suche
- Starter*in bursche99
- Datum Start
ANZEIGE
Effective May 15, 2017
Interesting how you managed to find that since Island Air has been long gone
Via Wayback Machine, I assumed that you already work with it.Interesting how you managed to find that since Island Air has been long gone
Hi all,
I was just alerted by FlyerTalk PM from @fakepcy that there are quite a few possible solutions waiting on my confirmation. My apologies, I've been through a difficult past few months, with my business partner in rehab for a coke habit (not the kind you drink
) and other issues limiting my time available for stuff like this.
I took a quick look through the thread and see there's a lot of different stuff out there that I should look at. Thanks to all who have put the effort in, I had assumed most of these were impossible; this is such a great community!
Most of these are flights where I have been helping friends track down this info, so I'll need some time to comb through everything and trace it back; in some cases, I'll need to go back to the person to try to resolve conflicts. Some are easy - anything WN will be my friend Tim; the Island Air one was definitely my friend Scott (as for how an ATR and a Dash 8 got confused on that one, you can blame FlightStats, not a FOTSG who didn't recognize the aircraft; the aircraft type that I threw in my request was just whatever FlightStats was showing as the type, which I'm sure many of us know is usually correct, but not always accurate) - but some are more difficult, e.g. a lot of the AC regional ones could be Tim, or Scott, or Lawrence, or Andrea, or a couple of them are even mine...
I'll try to come back on these in a reasonable timeframe, and thanks again!
Adam
I was just alerted by FlyerTalk PM from @fakepcy that there are quite a few possible solutions waiting on my confirmation. My apologies, I've been through a difficult past few months, with my business partner in rehab for a coke habit (not the kind you drink
) and other issues limiting my time available for stuff like this.I took a quick look through the thread and see there's a lot of different stuff out there that I should look at. Thanks to all who have put the effort in, I had assumed most of these were impossible; this is such a great community!
Most of these are flights where I have been helping friends track down this info, so I'll need some time to comb through everything and trace it back; in some cases, I'll need to go back to the person to try to resolve conflicts. Some are easy - anything WN will be my friend Tim; the Island Air one was definitely my friend Scott (as for how an ATR and a Dash 8 got confused on that one, you can blame FlightStats, not a FOTSG who didn't recognize the aircraft
; the aircraft type that I threw in my request was just whatever FlightStats was showing as the type, which I'm sure many of us know is usually correct, but not always accurate) - but some are more difficult, e.g. a lot of the AC regional ones could be Tim, or Scott, or Lawrence, or Andrea, or a couple of them are even mine...I'll try to come back on these in a reasonable timeframe, and thanks again!
Adam
@bursche99 Mal wieder eine Cross-Forenanfrage für die Flughäfen. Brauchen in die offenen Liste nicht mit aufgenommen werden
2007-06-02 X30332 STR TXL 0715 0825 737-800 SaschaX99
2007-06-07 X30335 TXL STR 1710 1825 737-800 SaschaX99
2007-11-04 LX1168 ZRH STR 1130 1215 Avro RJ100 SaschaX99
Danke
2007-06-02 X30332 STR TXL 0715 0825 737-800 SaschaX99
2007-06-07 X30335 TXL STR 1710 1825 737-800 SaschaX99
Danke
Zuletzt bearbeitet:
Good to hear that you're back and on your way to solving the past challenges.Hi all,
I was just alerted by FlyerTalk PM from @fakepcy that there are quite a few possible solutions waiting on my confirmation. My apologies, I've been through a difficult past few months, with my business partner in rehab for a coke habit (not the kind you drink
I took a quick look through the thread and see there's a lot of different stuff out there that I should look at. Thanks to all who have put the effort in, I had assumed most of these were impossible; this is such a great community!
Most of these are flights where I have been helping friends track down this info, so I'll need some time to comb through everything and trace it back; in some cases, I'll need to go back to the person to try to resolve conflicts. Some are easy - anything WN will be my friend Tim; the Island Air one was definitely my friend Scott (as for how an ATR and a Dash 8 got confused on that one, you can blame FlightStats, not a FOTSG who didn't recognize the aircraft
I'll try to come back on these in a reasonable timeframe, and thanks again!
Adam
And thank you for the praise.
We've been able to solve quite a few issues, and thanks to @fakepcy, even some that I thought would burn into the list like screen burn-in.
2016-06-14 3M0068 FLL MCO 0650 0804 SF34 Zachgriff N442XJ (most likely)
2016-06-13
3M59 TPA-FLL 19:59-21:15 Gate C8 ARR N442XJ
2016-06-14
3M68 FLL-MCO 06:50-08:04 Gate C8 DEP Gate 36 ARR
There was N347AG (3M73 MCO-FLL) which also arrived at Gate C8 at 22:14. Luckily, its activity on June 14 was recorded and its flights overlapped with my reconstruction of 3M68's next flights with the help of gate numbers (good thing it's 2016, so those were well-recorded).
N347AG: 3M114 FLL-GGT 12:12-13:26
N442XJ Reconstruction: 3M113 MCO-RSW 12:00-13:00
FULL 2016-06-14 RECONSTRUCTION:
3M68 FLL-MCO 06:50-08:04 Gate C8 DEP Gate 36 ARR
3M68 MCO-TLH 08:40-09:58 Gate 36 DEP
3M69 TLH-MCO 10:23-11:40 Gate A4 DEP Gate 36 ARR
3M113 MCO-RSW 12:00-13:00 Gate 36 DEP Gate D9A ARR
3M53 RSW-EYW 13:40-14:30 Gate D9A DEP
3M53 EYW-RSW 15:00-15:51 Gate 4 DEP Gate D9A ARR
3M52 RSW-MCO 16:29-17:30 Gate D9A DEP Gate 36 ARR
3M60 MCO-EYW 18:05-19:29 Gate 36 DEP
N442XJ wasn't recorded that day and with it being the only choice left, it made sense.
To further confirm my findings, 3M59 and 3M73 were the only flights that would spend the night at FLL because the next ones, 3M128 EYW-FLL and 3M122 EYW-FLL, were canceled and continued onto EYW, respectively.
2016-06-13
3M59 TPA-FLL 19:59-21:15 Gate C8 ARR N442XJ
2016-06-14
3M68 FLL-MCO 06:50-08:04 Gate C8 DEP Gate 36 ARR
There was N347AG (3M73 MCO-FLL) which also arrived at Gate C8 at 22:14. Luckily, its activity on June 14 was recorded and its flights overlapped with my reconstruction of 3M68's next flights with the help of gate numbers (good thing it's 2016, so those were well-recorded).
N347AG: 3M114 FLL-GGT 12:12-13:26
N442XJ Reconstruction: 3M113 MCO-RSW 12:00-13:00
FULL 2016-06-14 RECONSTRUCTION:
3M68 FLL-MCO 06:50-08:04 Gate C8 DEP Gate 36 ARR
3M68 MCO-TLH 08:40-09:58 Gate 36 DEP
3M69 TLH-MCO 10:23-11:40 Gate A4 DEP Gate 36 ARR
3M113 MCO-RSW 12:00-13:00 Gate 36 DEP Gate D9A ARR
3M53 RSW-EYW 13:40-14:30 Gate D9A DEP
3M53 EYW-RSW 15:00-15:51 Gate 4 DEP Gate D9A ARR
3M52 RSW-MCO 16:29-17:30 Gate D9A DEP Gate 36 ARR
3M60 MCO-EYW 18:05-19:29 Gate 36 DEP
N442XJ wasn't recorded that day and with it being the only choice left, it made sense.
To further confirm my findings, 3M59 and 3M73 were the only flights that would spend the night at FLL because the next ones, 3M128 EYW-FLL and 3M122 EYW-FLL, were canceled and continued onto EYW, respectively.
Zuletzt bearbeitet:
I’m going to have to go through these things in batches... These were mostly easy to just confirm when I went back and checked.
I snipped out the bits from a couple of the posts I replied to here about flights on 2010-01-31 that I'll have to reply to later, those ones were much more complex.
I actually looked in to this one ages ago. It seems what has happened here is that after AC (or its lessor) sold the aircraft, the new owner has requested that FlightAware block it. And even though this owner didn’t control the aircraft at the time of this flight, when FlightAware blocks the registration, it does this for all time - every flight the aircraft has ever taken.
Since this was the only one with this problem (although I think this may have subsequently happened to at least one more AC 320, so this problem may get worse over time)I think we can consider this solved through the magic of elimination.
(This problem may also impact other airlines and other specific aircraft, unfortunately, underlying yet again the fact that this data may not be available to us forever)
Excellent, thank you, solved
This is conclusive, C-FPDN solved.
Thanks, solved
Great, thanks! I had already ruled out C-FGWJ (or at least noted the inbound wasn’t dispositive and it may have been something else) in #6650. This one is solved.
Great, thanks, solved
This one is mine, so this is particularly great news, thank you I searched all sorts of things and even tried to find this one by elimination. Was there a new source that became available?
I snipped out the bits from a couple of the posts I replied to here about flights on 2010-01-31 that I'll have to reply to later, those ones were much more complex.
Maybe you have found it already by yourself.
AC481 (ACA481) Air Canada Flugtracking und Flugverlaufsdaten 12.01.2016 (CYUL-CYYZ) - FlightAware
Track Air Canada (AC) #481 flight from Aéroport Int'l Pierre-Elliott-Trudeau de Montréal to Torontode.flightaware.com
What i find noticeable is this comment:
Luftfahrzeugkennzeichen
Are you the operator? Purchase FlightAware Global to see tail number and more.
I have tried all A320 regs according to Airfleets and all without result, except this one:
C-FPDN - Unknown Owner (Canada)
Das Flugzeug (C-FPDN) steht auf Wunsch des Besitzers nicht für öffentliches Tracking zur Verfügung.
Das ist mein Flugzeug! Wie kann ich mein Flugzeug auf FlightAware verfolgen?
So maybe this the reg for this flight
I actually looked in to this one ages ago. It seems what has happened here is that after AC (or its lessor) sold the aircraft, the new owner has requested that FlightAware block it. And even though this owner didn’t control the aircraft at the time of this flight, when FlightAware blocks the registration, it does this for all time - every flight the aircraft has ever taken.
Since this was the only one with this problem (although I think this may have subsequently happened to at least one more AC 320, so this problem may get worse over time)I think we can consider this solved through the magic of elimination.
(This problem may also impact other airlines and other specific aircraft, unfortunately, underlying yet again the fact that this data may not be available to us forever
)Excellent, thank you, solved
This is conclusive, C-FPDN solved.
Thanks, solved
Great, thanks! I had already ruled out C-FGWJ (or at least noted the inbound wasn’t dispositive and it may have been something else) in #6650. This one is solved.
Great, thanks, solved
This one is mine, so this is particularly great news, thank you
I searched all sorts of things and even tried to find this one by elimination. Was there a new source that became available?I checked other 3M flights and realized that ALL of them, even those that are closely spaced, used Gate C8 at FLL and Gate 36 at MCO. I believe it's impossible for that to happen in real life which now makes me doubtful of my findings. I'll leave this as a guess for now.
Zuletzt bearbeitet:
Good thing the owner forgot that VariFlight exists because it managed to record C-FPDN for AC481, thus confirming it.I actually looked in to this one ages ago. It seems what has happened here is that after AC (or its lessor) sold the aircraft, the new owner has requested that FlightAware block it. And even though this owner didn’t control the aircraft at the time of this flight, when FlightAware blocks the registration, it does this for all time - every flight the aircraft has ever taken.
Since this was the only one with this problem (although I think this may have subsequently happened to at least one more AC 320, so this problem may get worse over time)I think we can consider this solved through the magic of elimination.
(This problem may also impact other airlines and other specific aircraft, unfortunately, underlying yet again the fact that this data may not be available to us forever
With that logic, can these two be solved in the same manner? The dates are too old to be confirmed on VariFlight. If that's the case, then AC405 would be C-FTJP. Surprisingly, there was no "Unknown Owner" message for C-FPDN.
As for AC408, no A319s gave that message, but C-FTJP did despite being an A320. Could it be that the flight was actually flown by an A320 or the owner thing isn't always reliable, which would mean that the AC481 case was a coincidence?
Zuletzt bearbeitet:
I think this is a useful piece of information, but may not always be reliable. I’m not sure everyone realizes that FlightAware doesn’t use the entire URL - the destination airport is irrelevant. You have to enter something, but even if it’s wrong, the URL will still work. When you have all the flight info, it’s not a big deal, because you can just double check things. But when it’s blocked, it can potentially be impossible to resolve.
For example, this is a flight I took:
AC2058 (ACA2058) Air Canada Flight Tracking and History 28-Jul-2014 (CYYZ-KDCA) - FlightAware
Track Air Canada (AC) #2058 flight from Toronto Pearson Int'l to Reagan National
flightaware.com
When I was first getting my registrations, I was just inputting each AC E90 registration one after the other. When it returned a result, I noted the registration and moved on:
C-FEKD Flight Tracking and History 28-Jul-2014 (CYYZ-KDCA) - FlightAware
Track C-FEKD flight from Toronto Pearson Int'l to Newark Liberty Intl
www.flightaware.com
But you may notice, the flight I wanted was to DCA, when in fact C-FEKD operated a YYZ-EWR flight that just happened to depart at the same time! Since FlightAware ignores the destination airport code in the URL, even though I had KDCA in the URL, it still popped up the result page for me, and I just wasn’t paying attention.
Somehow I later realized my mistake and went back and found the right one:
C-FGLW Flight Tracking and History 28-Jul-2014 (CYYZ-KDCA) - FlightAware
Track C-FGLW flight from Toronto Pearson Int'l to Reagan National
flightaware.com
This might present a problem when you have multiple aircraft that are blocked and an airport where that airline operates a number of departures, such as AC at YYZ, because FlightAware does consider the origin. So if the aircraft departed from a different airport at the same time as the flight you’re looking for, it should still return an error. But if you had two aircraft depart the same airport, and both are blocked, both would return the blocked message. You therefore wouldn’t be able to verify whether C-FEKD had operated a flight to EWR or to DCA.
So it has to be used carefully, I think. For an outstation or one where that airline had few flights or few aircraft of the type, possibly quite reliable. For a big carrier, common aircraft type, from one of their hubs... much bigger risk of incorrect data.
As for whether it can solve those other flights, let me add that to the queue of things to check here
Re the 319 vs 320 issue, my confidence in the type is always somewhat limited with AC. FlightAware and FlightStats are not always correct for that, so if I pulled 320 as the type, it’s quite possible it’s a 319, or vice versa. It’s probably correct over 80% of the time, maybe even over 90% of the time, but sometimes even when it has the exact registration, it still stores the type incorrectly. Something which continues to this day, by the way.
Confirmed, thank you
Solved.
@Adam Smith
2007-05-26 WS0136 YVR YEG 1000 1223 736 Adam Smith
Nachdem @HannoverEDDV DLFD/EANS mit seinem Suchtrick die Seite wohl überfordert hat und sie nicht mehr aufzurufen ist
,ein wenig Spekulatius:
Im Mai 2007 gab es wohl folgende Rotation WS0015-WS0136-WS0199-WS0198
[...]
Für den 26.05. habe für die WS0199/0198 bei Ladysmith Acars folgende Reg gefunden (Zeituntschied da Ladysmith in den Reports in local Zeit zeigt)
1401 20070526 C-GBWS B736 34288 WS0198 # (YXX-YEG)
1306 20070526 C-GBWS B736 34288 WS0199 # \n(YEG-YXX)
This is quite the dataset... Seems very strong. The flights all operated on time that day, so I see no reason to deviate from the extremely consistent operating pattern. Is there anything I’m missing that would make this not be the answer?
Thank you, solved.
Correct that 8112 was the outbound from IAH. I thought I had posted about this one upthread, but I’ve narrowed this down, through process of elimination, to one of the following aircraft:
- C-FCJZ
- C-FJJZ
- C-FKJZ
- C-FTJZ
2015-01-12 AC8406 YLW YYC 1000 1159 CRJ Adam Smith (op by QK) C-GKEW
alle CRJ200 ausprobiert von JZA
QK8406 (JZA8406) Jazz Flight Tracking and History 12-Jan-2015 (CYLW-CYYC) - FlightAware
Track Jazz (QK) #8406 flight from Kelowna Int'l to Calgary Int'l
und dann für eine Reg (C-GKEW) die bekannte "nicht öffentliches Tracking" Meldung bekommen
https://www.flightaware.com/live/flight/CGKEW/history/20150112/1804Z/CYLW/CYYC
Was ich finden konnte, war das die Reg in YYC zur geplanten Ankunftszeit getrackt wurde
C05F8F -------- C-GKEW CRJ2 29125 3350 12/01/2015 11:37:13
SBS-1 Log from CALGARY, AB, CANADA (CYYC) beginning 12/01/2015. Times
are LOCAL.
I’ll have to take a look at this one in more detail.
Good thing I didn’t do all that work to double-check the @SaschaX99 had done upthread (which was correct anyway), I think we can call this one solved.
Although it seems that both of you missed that the inbound AC234 was also one of the requested flights, so we’ve managed to solve both
found 2010-01-31 AC0234 YVR YEG 0829 1054 319 Adam Smith C-FZUH
Thanks, confirmed
Apologies, that’s a typo on my part
Thank you. This one is not correct though. Inbound was WS476 YYZ-YUL. 654 likely went to YYZ as 661. I say this based both on timing (WS wouldn’t likely have an aircraft sitting 3 hours at YUL) as well as FlightStats having stored the arrival/departure gates for a few of these flights.
Same thing here, inbound would have been 476 from YYZ. Although I suspect it should have originally been 478, which was cancelled, and thus likely switched to 476, which caused the 1-hour departure delay for 655.
So in either case, if you have info on WS476, that should solve it. I’ve checked acarsd.org on the Wayback Machine and it didn’t have either. If not, this one remains open.
Great detective work
Agreed.
Zuletzt bearbeitet:
I actually looked in to this one ages ago. It seems what has happened here is that after AC (or its lessor) sold the aircraft, the new owner has requested that FlightAware block it. And even though this owner didn’t control the aircraft at the time of this flight, when FlightAware blocks the registration, it does this for all time - every flight the aircraft has ever taken.
Since this was the only one with this problem (although I think this may have subsequently happened to at least one more AC 320, so this problem may get worse over time)I think we can consider this solved through the magic of elimination.
(This problem may also impact other airlines and other specific aircraft, unfortunately, underlying yet again the fact that this data may not be available to us forever
Good thing the owner forgot that VariFlight exists because it managed to record C-FPDN for AC481, thus confirming it.
To make it easier for @bursche99, both entries are related to
found 2016-01-12 AC0481 YUL YYZ 0553 0756 Adam Smith C-FPDN #6934
found 2008-12-07 WS0502 YYJ YYC 1745 2002 736 Adam Smith C-GWSK #6670This one is mine, so this is particularly great news, thank you
C-GWSK; B736 34287 \nWestJet WS0502 (YYJ-YYC-YWG) 1803 20081207
No, not a new source, just overlooked several times when searching through the old Yahoo Acars files
No, there is no missing information, but rather that we are waiting for approval from the requester for solutions based on previous routings.
After ok from Adam Smith it's solved
found 2007-05-26 WS0136 YVR YEG 1000 1223 736 Adam Smith (see #6921) C-GBWS
Zuletzt bearbeitet:
Thank you, this is great, I know what a lot of work these BTS reconstructions are (having done a few myself). Confirmed.
Solved
This one is solved too. I think you did attempt some reconstructions at the busier airports later (I'm trying to go through these chronologically), so we'll see how those went
Concur.
Agreed! I had actually tried to figure this one out myself a while ago based solely on the BTS data, and I was left with way too many possibilities - other aircraft that departed or arrived, internationally, or went for maintenance or whatever. Awesome that you found this gate info, otherwise I'm not sure it would have been solved
@zachgriff
Found 2016-06-14 3M0068 FLL MCO 0650 0804 SF34 Zachgriff N442XJ
2016-06-13
3M59 TPA-FLL 19:59-21:15 N442XJ
2016-06-14
3M68 FLL-MCO 06:50-08:04
3M68 MCO-TLH 08:40-09:58
3M69 TLH-MCO 10:23-11:40
3M75 MCO-EYW 12:30-13:54 N442XJ
It turns out that I mistyped N442XJ as N422XJ which explains why I never found flight data on June 14. Now that I know N442XJ's whereabouts on that day, I pieced them together using departures/arrivals at the respective airports and they linked back to 3M68! There was an 11:16 arrival at MCO which I thought might affect its credibility, but thankfully it was recorded as N413XJ. The next MCO arrival after 3M69 would be 3M76 from EYW at 12:27 which was flown by N350AG. TLH had a few movements, and 3M69 was the next one after 3M68.
Zuletzt bearbeitet:
I’m going to tackle some of these out of order since I can make a call one way or the other on some of them much more easily than others.
I’m heading out of town tomorrow for a few days and my travel laptop suffered a dead motherboard the other day, so I may not have the ability to follow up on more of these until next week. We’ll see. But I do appreciate everyone’s assistance and I’ll try to respond to the others soon
This certainly feels plausible, although there are some other arrivals that could make sense as the inbound, I’m not sure this is certain. Rotations weren’t necessarily consistent things like YYZ-YYC-YVR. It could have been YUL-YYC-YVR or YOW-YYC-YVR. FlightStats might say those were operated by E90 or 320, but that’s just not super reliable. Especially the older flights.
I was pleasantly surprised that it has the gate for 225, but FlightStats has no gate for 1159, not for the other possible inbounds either, so that doesn’t solve anything for us.
For the moment, I think this is possible, and maybe the most likely, but I’m not sure it’s solved.
Very logical (this one plus the follow-up - not quoting them in full just to save space, confirmed.
It’s maybe not 100% that the same aircraft would have operated both legs, but I think it’s close enough to say this is solved.
These are all confirmed except the 7782. I apologize, the 7782 that was missing was actually on the 12th, not the 11th.
You asked in a different post whether it was a milk run, I presume in relation to the person taking the flights rather than the flights themselves... Air Canada used to run a contest once or twice a year where you could earn a ton of points for flying to/from certain destinations, which they always set based on where their load factors were looking a little bit light and they wanted to bump up traffic a bit. Typically the top 10 finishers would earn 1 million Aeroplan points each. So a few people would figure out highly efficient routings and then just go fly for days on end to rack up big scores in the contest. Hence all these repetitive YYG-YHZ-YQM-YHZ-YQM-YYG and so on. And two of the people I’ve been helping out with this were consistently among those top 20 finishers, so they did a lot of these things
As I noted in an earlier post, I’m not sure about the blocked URL as 100% reliable, but with the added bonus of Variflight, I don’t think we need to worry about that and can call these solved.
Agreed, thanks
Okay, so, the famous KOA-HNL... Since it prompted so much discussion in the last day or so, I figured I should try to clear this one up
I had my friend dig up the original booking, he was definitely on WP87. The times I previously provided don’t match the times in FlightStats for WP85, so I think this is a case of FlightRadar24 recorded the times incorrectly (or he did if he entered it manually rather than having MyFR24 populate it for him), and I just assumed that what was in the spreadsheet he sent me was correct (I was helping him with hundreds of flights, so scrubbing every single data point would have been a crazy amount of work).
I see for WP87 it’s either N944WP or N945WP? I don’t think I saw any details that I should look at to try to figure out which?
I’m heading out of town tomorrow for a few days and my travel laptop suffered a dead motherboard the other day, so I may not have the ability to follow up on more of these until next week. We’ll see. But I do appreciate everyone’s assistance and I’ll try to respond to the others soon
This certainly feels plausible, although there are some other arrivals that could make sense as the inbound, I’m not sure this is certain. Rotations weren’t necessarily consistent things like YYZ-YYC-YVR. It could have been YUL-YYC-YVR or YOW-YYC-YVR. FlightStats might say those were operated by E90 or 320, but that’s just not super reliable. Especially the older flights.
I was pleasantly surprised that it has the gate for 225, but FlightStats has no gate for 1159, not for the other possible inbounds either, so that doesn’t solve anything for us.
For the moment, I think this is possible, and maybe the most likely, but I’m not sure it’s solved.
Very logical (this one plus the follow-up - not quoting them in full just to save space, confirmed.
It’s maybe not 100% that the same aircraft would have operated both legs, but I think it’s close enough to say this is solved.
These are all confirmed except the 7782. I apologize, the 7782 that was missing was actually on the 12th, not the 11th.
You asked in a different post whether it was a milk run, I presume in relation to the person taking the flights rather than the flights themselves... Air Canada used to run a contest once or twice a year where you could earn a ton of points for flying to/from certain destinations, which they always set based on where their load factors were looking a little bit light and they wanted to bump up traffic a bit. Typically the top 10 finishers would earn 1 million Aeroplan points each. So a few people would figure out highly efficient routings and then just go fly for days on end to rack up big scores in the contest. Hence all these repetitive YYG-YHZ-YQM-YHZ-YQM-YYG and so on. And two of the people I’ve been helping out with this were consistently among those top 20 finishers, so they did a lot of these things
As I noted in an earlier post, I’m not sure about the blocked URL as 100% reliable, but with the added bonus of Variflight, I don’t think we need to worry about that and can call these solved.
Agreed, thanks
Okay, so, the famous KOA-HNL... Since it prompted so much discussion in the last day or so, I figured I should try to clear this one up
I had my friend dig up the original booking, he was definitely on WP87. The times I previously provided don’t match the times in FlightStats for WP85, so I think this is a case of FlightRadar24 recorded the times incorrectly (or he did if he entered it manually rather than having MyFR24 populate it for him), and I just assumed that what was in the spreadsheet he sent me was correct (I was helping him with hundreds of flights, so scrubbing every single data point would have been a crazy amount of work).
I see for WP87 it’s either N944WP or N945WP? I don’t think I saw any details that I should look at to try to figure out which?
Found 2018-06-12 AC7782 YQX YYT 0530 0618 BEH Adam Smith C-GTMB
To test how reliable the unknown owner case is for C-FTJP which could solve AC405, I got some of its known flights in 2014. Notice how the unique message for the tail number part is present.Good thing the owner forgot that VariFlight exists because it managed to record C-FPDN for AC481, thus confirming it.
With that logic, can these two be solved in the same manner? The dates are too old to be confirmed on VariFlight. If that's the case, then AC405 would be C-FTJP. Surprisingly, there was no "Unknown Owner" message for C-FPDN.
As for AC408, no A319s gave that message, but C-FTJP did despite being an A320. Could it be that the flight was actually flown by an A320 or the owner thing isn't always reliable, which would mean that the AC481 case was a coincidence?
AC1202 (ACA1202) Air Canada Flight Tracking and History 10-Feb-2014 (CYYZ-KTPA) - FlightAware
Track Air Canada (AC) #1202 flight from Toronto Pearson Int'l to Tampa Intl
www.flightaware.com
AC550 (ACA550) Air Canada Flight Tracking and History 11-Feb-2014 (CYVR-KLAX) - FlightAware
Track Air Canada (AC) #550 flight from Vancouver Int'l to Los Angeles Intl
www.flightaware.com
AC792 (ACA792) Air Canada Flight Tracking and History 04-Jun-2014 (KLAX-CYYZ) - FlightAware
Track Air Canada (AC) #792 flight from Los Angeles Intl to Toronto Pearson Int'l
www.flightaware.com
AC792 - Air Canada - Flight history - Flightradar24
AC792 - Air Canada - Flight history
web.archive.org
They were the only two ATRs left at the time of flight which simplifies things when identifying which flights were flown by an ATR. Had he taken the flight past July 2017, then N945WP would've been the only choice
FLIGHT RECONSTRUCTION:
2017-05-31
WP262 HNL-KOA 06:25-07:21 Gate 76 DEP
WP263 KOA-HNL 07:46-08:43 Gate 72 ARR
WP82 HNL-KOA 09:20-10:17 Gate 72 DEP
WP83 KOA-HNL 10:39-11:35 Gate 72 ARR
WP117 HNL-LIH 12:06-12:56 Gate 72 DEP
WP118 LIH-HNL 13:21-14:03 Gate 72 ARR
WP86 HNL-KOA 14:40-15:37 Gate 72 DEP
WP87 KOA-HNL 16:02-16:57 Gate 72 ARR
WP446 HNL-OGG 17:27-18:15 Gate 72 DEP
WP447 OGG-HNL 18:40-19:23 Gate 72 ARR
WP90 HNL-KOA 19:56-20:55 Gate 72 DEP
WP91 KOA-HNL 21:20-22:20
N944WP:
2017-05-30
WP82 HNL-KOA 09:20-10:17 Gate 73 DEP N944WP
WP83 KOA-HNL 10:39-11:35 Gate 72 ARR
WP117 HNL-LIH 12:06-12:56 Gate 72 DEP
WP118 LIH-HNL 13:16-13:44 Gate 72 ARR
WP86 HNL-KOA 14:40-15:37 Gate 72 DEP
WP87 KOA-HNL 16:02-16:57 Gate 72 ARR
WP446 HNL-OGG 17:27-18:15 Gate 72 DEP
WP447 OGG-HNL 18:40-19:23 Gate 72 ARR
WP90 HNL-KOA 19:56-20:55 Gate 72 DEP
WP91 KOA-HNL 21:20-22:20
2017-06-01
WP115 HNL-LIH 09:22-10:12 Gate 72 DEP
WP116 LIH-HNL 10:39-11:21 Gate 72 ARR
WP84 HNL-LIH 12:55-13:55 Gate 72 DEP N944WP
WP85 LIH-HNL 14:20-15:15 Gate 72 ARR
WP440 HNL-OGG 15:52-16:42 Gate 72 DEP
WP88 HNL-KOA 18:16-19:15 Gate 72 ARR
N945WP:
2017-05-30
WP262 HNL-KOA 06:25-07:21 Gate 76 DEP
WP263 KOA-HNL 07:46-08:43 Gate 72 ARR
WP82 HNL-KOA 09:20-10:17 Gate 72 DEP
WP83 KOA-HNL 10:39-11:35 Gate 72 ARR
WP428 HNL-OGG 12:58-13:50 Gate 72 DEP
WP425 OGG-HNL 14:15-14:59 Gate 72 ARR
WP119 HNL-LIH 15:36-16:27 Gate 72 DEP
WP120 LIH-HNL 16:52-17:33 Gate 72 ARR
WP123 HNL-LIH 18:03-18:50 Gate 72 DEP
WP124 LIH-HNL 19:15-19:56 Gate 74 ARR
WP448 HNL-OGG 20:26-21:14 Gate 74 DEP
WP449 OGG-HNL 21:39-22:22
Unfortunately, VariFlight gave no data for either aircraft on May 31. Had at least one of them been tracked that day, this would've been solved instantly because it's just a matter of elimination. It doesn't help that the arrival gate numbers for the final flight of the day were always unknown. Perhaps your friend has spotted an ATR earlier or later that day because I could use it to identify the flight it was taking to eliminate it.
Zuletzt bearbeitet:
Successfully Found@bursche99 Mal wieder eine Cross-Forenanfrage für die Flughäfen. Brauchen in die offenen Liste nicht mit aufgenommen werden
2007-06-02 X30332 STR TXL 0715 0825 737-800 SaschaX99
2007-06-07 X30335 TXL STR 1710 1825 737-800 SaschaX99
2007-11-04 LX1168 ZRH STR 1130 1215 Avro RJ100 SaschaX99
Danke
2007-11-04 LX1168 ZRH STR 1130 1215 Avro RJ100 SaschaX99
Flight: LX 1168
Flight Date: 04.11.2007 UTC
Route: ZRH-STR
Callsign: SWR116F
AC Owner: LX
Registration: HBIXW
AC Type: AR1
STD: 04.11.2007 11:30 UTC
STA: 04.11.2007 12:15 UTC
Offblock: 04.11.2007 11:39 UTC
Onblock: 04.11.2007 12:18 UTC
Takeoff: 04.11.2007 11:44 UTC
Touchdown: 04.11.2007 12:11 UTC
Arrival Position: 017
Arrival Runway: 07
I do have a small amount of hesitation about some of the matches at the WN hubs (although I haven't been through them in detail yet), but with the gate info, this one is clear, agreed.
@Adam Smith
Is it safe to say that:
2014-02-15 AC0405 YUL YYZ 0859 1013 320 Adam Smith C-FTJP
2014-02-17 AC0408 YYZ YUL 1059 1217 319 Adam Smith C-FTJP
AC405 has a very high chance, while AC408 is probable because I checked other AC flights in 2014 and compared the listed equipment to the actual one used. Some listed an A319 but actually used an A320, and no A319 regs gave me an "Unknown Owner (Canada)" alert. Only C-FTJP, an A320, did.
We've seen how the C-GKEW and C-FPDN assumptions turned out to be true upon verification on VariFlight, not to mention how C-FPDN did not give the "Unknown Owner (Canada)" alert when inputting it for AC405 in 2014 but it did for AC481 in 2016. Since VariFlight doesn't go back to early 2014, C-FTJP is the best bet. The chances of C-FTJP being used for both flights are very low but never zero.
On a side note, I have a feeling the owner blocked the reg after the crash landing at YHZ.
UPDATE:
https://www.flightaware.com/live/flight/ACA609/history/20140808/1150Z/CYHZ/CYYZ
This is from an unrelated request, and what I noticed that is if you replace it with C-FTJP, you'll only get the standard message and not the unknown owner one.
And then I got ahold of C-FTJP's flight on that same day: 2014/08/08 19:12;ACA610;ACA610;-;C-FTJP;C03326;Air Canada;A320
www.flightaware.com
Look at the Tail Number message on the side and also see what happens when you replace the callsign with C-FTJP
What I can conclude from here is that the unknown owner message appears only if the blocked aircraft flew that flight.
Is it safe to say that:
2014-02-15 AC0405 YUL YYZ 0859 1013 320 Adam Smith C-FTJP
2014-02-17 AC0408 YYZ YUL 1059 1217 319 Adam Smith C-FTJP
AC405 has a very high chance, while AC408 is probable because I checked other AC flights in 2014 and compared the listed equipment to the actual one used. Some listed an A319 but actually used an A320, and no A319 regs gave me an "Unknown Owner (Canada)" alert. Only C-FTJP, an A320, did.
We've seen how the C-GKEW and C-FPDN assumptions turned out to be true upon verification on VariFlight, not to mention how C-FPDN did not give the "Unknown Owner (Canada)" alert when inputting it for AC405 in 2014 but it did for AC481 in 2016. Since VariFlight doesn't go back to early 2014, C-FTJP is the best bet. The chances of C-FTJP being used for both flights are very low but never zero.
On a side note, I have a feeling the owner blocked the reg after the crash landing at YHZ.
UPDATE:
https://www.flightaware.com/live/flight/ACA609/history/20140808/1150Z/CYHZ/CYYZ
This is from an unrelated request, and what I noticed that is if you replace it with C-FTJP, you'll only get the standard message and not the unknown owner one.
And then I got ahold of C-FTJP's flight on that same day: 2014/08/08 19:12;ACA610;ACA610;-;C-FTJP;C03326;Air Canada;A320
AC610 (ACA610) Air Canada Flight Tracking and History 08-Aug-2014 (CYYZ-CYHZ) - FlightAware
Track Air Canada (AC) #610 flight from Toronto Pearson Int'l to Halifax Int'l
www.flightaware.com
Look at the Tail Number message on the side and also see what happens when you replace the callsign with C-FTJP
What I can conclude from here is that the unknown owner message appears only if the blocked aircraft flew that flight.
Zuletzt bearbeitet:
@Der BWLer
2007-09-05 AB3785 OPO PMI 1615 1900 A320 Der BWLer / spotter.lars (ATD 1700, ATA 1945) D-ABDK?
Habe folgendes in den ACARS Logs gefunden:
D-ABDK (A320 AB) 1044 20070905 AB9332 (HAM-PMI) [EDDH/HAM]
20070905;2120;22052;D-ABDK;AB9333 AB029Q;A320 AB PMI-HAM;Jena
Der Flug AB9332 (planmäßig 11:20-14:00) passt sehr gut zu AB3784 PMI-OPO mit STA/STD 14:50-15:30 und AB9333 ist laut Flugstatistik normalerweise 20:00-22:45 geflogen, das passt ebenfalls zur STA/STD von AB3785.
Alle anderen Air Berlin/LTU-A320 konnte ich außerdem durch ACARS-Einträge ausschließen.
Allerdings wurde AB3785 laut Flugstatistik auch manchmal mit Niki-Flugzeugen durchgeführt, die ich nicht alle in den ACARS Logs gefunden habe.
Falls das aber ausgeschlossen werden könnte, dürfte es wohl D-ABDK gewesen sein.
2007-09-05 AB3785 OPO PMI 1615 1900 A320 Der BWLer / spotter.lars (ATD 1700, ATA 1945) D-ABDK?
Habe folgendes in den ACARS Logs gefunden:
D-ABDK (A320 AB) 1044 20070905 AB9332 (HAM-PMI) [EDDH/HAM]
20070905;2120;22052;D-ABDK;AB9333 AB029Q;A320 AB PMI-HAM;Jena
Der Flug AB9332 (planmäßig 11:20-14:00) passt sehr gut zu AB3784 PMI-OPO mit STA/STD 14:50-15:30 und AB9333 ist laut Flugstatistik normalerweise 20:00-22:45 geflogen, das passt ebenfalls zur STA/STD von AB3785.
Alle anderen Air Berlin/LTU-A320 konnte ich außerdem durch ACARS-Einträge ausschließen.
Allerdings wurde AB3785 laut Flugstatistik auch manchmal mit Niki-Flugzeugen durchgeführt, die ich nicht alle in den ACARS Logs gefunden habe.
Falls das aber ausgeschlossen werden könnte, dürfte es wohl D-ABDK gewesen sein.