Du verwendest einen veralteten Browser. Es ist möglich, dass diese oder andere Websites nicht korrekt angezeigt werden. Du solltest ein Upgrade durchführen oder ein alternativer Browser verwenden.
Ich habe Kontakt mit HAJ hinbekommen - erste positive Ergebnisse
HAJ airport meinte:
Für den Flug AF 5491 vom 12.07.2011 kann ich Ihnen zu mindestens mitteilen, dass dieser mit der Registration FHBXI (E170) durchgeführt wurde!
Da wir unser aktuelles Abrechnungssystem erst im Juni 2010 eingeführt haben und wir leider auch keinen Zugriff mehr auf das Altsystem haben.
I found a couple more gaps in my records that you all might be able to help me with; I can't recall whether these flights were on F100 or F70 aircraft:
2004-03-06 KL1601(?) AMS FCO 0905 jelliott4
2004-03-13 KL1618(?) MXP AMS 0630 jelliott4
I found a couple more gaps in my records that you all might be able to help me with; I can't recall whether these flights were on F100 or F70 aircraft:
2004-03-06 KL1601(?) AMS FCO 0905 jelliott4
2004-03-13 KL1618(?) MXP AMS 0630 jelliott4
Oh hmm, interesting; I distinctly remember a 3-2 seating configuration with KLM branding (these being the only two KLM flights I've ever taken), but maybe I'm only remembering the 2004-03-06 flight.
Oh hmm, interesting; I distinctly remember a 3-2 seating configuration with KLM branding (these being the only two KLM flights I've ever taken), but maybe I'm only remembering the 2004-03-06 flight.
I have already searched the old ACARSd archive and the newly reconstructed ACARSd database, including FZ0791/FDB791 and FZ0792/FDB792, without finding either registration.
I understand that some Libhomeradar records may contain the aircraft contact even where the commercial flight number or routing was not populated.
@euul — I saw that you have some of the old Libhomeradar data saved locally. If possible, could you please check these two dates?
If the direct flight-number search gives no result, could you also check flydubai / FDB / A6-Fxx contacts around the relevant times?
If anything is found, I would really appreciate the original Libhomeradar row if possible — timestamp, callsign, flight number, routing, registration, Mode-S hex and aircraft type.
Lines
found 2012-06-30 LH0991 AMS FRA zoki91 (D-AILU currently supported by an exact-day ACARS rotation; looking for independent/direct confirmation) DAILU #9260
found 2012-06-30 LH1116 FRA MAD zoki91 DAILU #9260
Lines
found 2012-06-30 LH0991 AMS FRA zoki91 (D-AILU currently supported by an exact-day ACARS rotation; looking for independent/direct confirmation) DAILU #9260
found 2012-06-30 LH1116 FRA MAD zoki91 DAILU #9260
Beitrag automatisch zusammengeführt:
typo 2012-07-11 OS0369 BCN VIE zoki91
should be
typo 2012-07-11 OS0396 BCN VIE zoki91
Details
2012-07-11 OS0396 BCN VIE zoki91
Routing: BCN-VIE
STD: 11.07.2012 04:40 UTC
STD: 11.07.2012 06:40 LT
Offblock: 11.07.2012 04:33 UTC
Offblock: 11.07.2012 06:33 LT
Takeoff: 11.07.2012 04:53 UTC
Takeoff: 11.07.2012 06:53 LT
STA: 11.07.2012 07:05 UTC
STA: 11.07.2012 09:05 LT
Touchdown: 11.07.2012 06:41 UTC
Touchdown: 11.07.2012 08:41 LT
Onblock: 11.07.2012 06:47 UTC
Onblock: 11.07.2012 08:47 LT
Registration: OELNS
Subfleet: 738
Owner: VO
-------------
Lines
found 2012-07-11 OS0396 BCN VIE zoki91 OELNS #9260
Thank you very much for taking the time to check these for me, I really appreciate it!
The detailed information for LH991, LH1116 and OS396 is extremely helpful, and thank you also for correcting my mistake with OS369 → OS396. That correction is especially valuable because I’m trying to rebuild my old flight history as accurately as possible for my personal Flighty records.
It’s also great to see LH991 and LH1116 both showing D-AILU, which fits the same-aircraft rotation perfectly.
Thanks again for your help and for checking the details so carefully!
I have already searched the old ACARSd archive and the newly reconstructed ACARSd database, including FZ0791/FDB791 and FZ0792/FDB792, without finding either registration.
I understand that some Libhomeradar records may contain the aircraft contact even where the commercial flight number or routing was not populated.
@euul — I saw that you have some of the old Libhomeradar data saved locally. If possible, could you please check these two dates?
If the direct flight-number search gives no result, could you also check flydubai / FDB / A6-Fxx contacts around the relevant times?
If anything is found, I would really appreciate the original Libhomeradar row if possible — timestamp, callsign, flight number, routing, registration, Mode-S hex and aircraft type.
found 2004-06-11 — QF93 — MEL → LAX VH-OEG
VH-OEG (B74ER [QFA] - QF) 0855 20040611 QF0093
if Traveling into past
Southern California Acars Log
Location: Baldwin Park, CA
proposal
2004-06-30 — QF108 — JFK → LAX
VH-OJK (B744 [QFA] - 25 QF) 0027 20040630 QF0108 (JFK-LAX)
Southern California Acars Log
Location: Baldwin Park, CA
Thank you very much for the help, Sascha, and also for pointing out how the open-request list is maintained.
I understand now. I’ve gone back and cleaned up my original posts, struck through the flights that have already been solved, and removed the duplicated open requests from my later post. I’ve left only the genuinely new 2004 Qantas flights there.
And thank you for finding VH-VQV, EC-ICS, EC-LML, TC-JRN, VH-VXU, VH-OGJ and VH-OGG. The underlying rows are extremely useful for my records.
Really appreciate you taking the time to check all of these and helping me get the thread organised properly as well.
found 2004-06-11 — QF93 — MEL → LAX VH-OEG
VH-OEG (B74ER [QFA] - QF) 0855 20040611 QF0093
if Traveling into past
Southern California Acars Log
Location: Baldwin Park, CA
proposal
2004-06-30 — QF108 — JFK → LAX
VH-OJK (B744 [QFA] - 25 QF) 0027 20040630 QF0108 (JFK-LAX)
Southern California Acars Log
Location: Baldwin Park, CA
Thank you very much, Sascha, this is really helpful.
QF93 = VH-OEG looks excellent, especially with the exact-date Southern California ACARS entry.
For QF108, I noticed you marked VH-OJK as a proposal. Because QF108 operated JFK–LAX and then continued onward, I believe, is there any way to confirm whether the 00:27 ACARS record on 30 June belongs to the QF108 that departed JFK on 30 June, rather than the previous day’s rotation continuing after midnight?
I’m just trying to be very careful with the service date before I mark that one as confirmed.
And if you happen to find anything for QF107 on 16 June or QF94 on 30 June, I’d be very grateful.
For QF108, I noticed you marked VH-OJK as a proposal. Because QF108 operated JFK–LAX and then continued onward, I believe, is there any way to confirm whether the 00:27 ACARS record on 30 June belongs to the QF108 that departed JFK on 30 June, rather than the previous day’s rotation continuing after midnight?
Thank you very much for the help, Sascha, and also for pointing out how the open-request list is maintained.
I understand now. I’ve gone back and cleaned up my original posts, struck through the flights that have already been solved, and removed the duplicated open requests from my later post. I’ve left only the genuinely new 2004 Qantas flights there.
And thank you for finding VH-VQV, EC-ICS, EC-LML, TC-JRN, VH-VXU, VH-OGJ and VH-OGG. The underlying rows are extremely useful for my records.
Really appreciate you taking the time to check all of these and helping me get the thread organised properly as well.
Qantas used to provide tail numbers if you ask them on Facebook, even going back to 1992, but they stopped doing so a few months ago. I used that time to solve almost all outstanding QF requests, so you kinda missed out on the fun.
However, I think you should try asking them and see if they changed. Maybe it was just a matter of which agent was handling that account and not some new data retention policy. Please let us know.
found 2012-08-23 TK1006 SKP-IST 20:40-23:05 B738 TC-JFG #9271
2012/08/23 19:00;THY2HJ;THY2HJ;-;TC-JFG;4BA8C7;Turkish Airlines;B738
THY2HJ seen @ 2012-08-23 20:56 CET on route from SKP to IST
THY5CG seen @ 2012-08-23 18:50 CET on route from IST to SKP
Thank you very much again, Sascha, this is really helpful.
I’ve now marked TK1006 as solved with TC-JFG, since the THY2HJ route observation closes the gap I was worried about.
And thank you for finding QF856 = VH-TJI as well, that exact historical record is perfect for what I’m trying to keep with my Flighty history.
Regarding JQ509 on 9 January 2014, you’ve raised a good point. I’m going back through my old records now to double-check whether the date is correct or whether I may have the wrong Jetstar flight number for that SYD → MEL trip.
I won’t mark that one solved until I’ve verified the date/flight-number combination.
Thanks again for checking these so carefully. I really appreciate it!
For QF108, I noticed you marked VH-OJK as a proposal. Because QF108 operated JFK–LAX and then continued onward, I believe, is there any way to confirm whether the 00:27 ACARS record on 30 June belongs to the QF108 that departed JFK on 30 June, rather than the previous day’s rotation continuing after midnight?
I’m just trying to be very careful with the service date before I mark that one as confirmed.
not correct
2004-06-30 — QF108 — JFK → LAX
VH-OJK (B744 [QFA] - 25 QF) 0027 20040630 QF0108 (JFK-LAX)
Southern California Acars Log
Location: Baldwin Park, CA
When I check the timetable, it looks to me like the routing was entered incorrectly, as it looks more like the LAX-SYD flight from 29,06,2004, which departed a little bit delayed.
