Masterthread Registration-Suche

[fakepcy]

ANZEIGE

yes i found following information:

Details
2009-01-05 9U0863 KIV FRA 0525 0700 ER-AXT
Routing: KIV-FRA
STD: 05.01.2009 03:25 UTC
STD: 05.01.2009 05:25 LT
Offblock: 05.01.2009 03:40 UTC
Offblock: 05.01.2009 05:40 LT
Takeoff: 05.01.2009 03:45 UTC
Takeoff: 05.01.2009 05:45 LT
STA: 05.01.2009 06:00 UTC
STA: 05.01.2009 07:00 LT
Touchdown: 05.01.2009 06:05 UTC
Touchdown: 05.01.2009 07:05 LT
Onblock: 05.01.2009 06:19 UTC
Onblock: 05.01.2009 07:19 LT
Registration: ERAXT
Subfleet: 322
Owner: 9U

-------------
2009-01-05 9U0864 FRA KIV 1500 1820 ER-AXT
Routing: FRA-KIV
STD: 05.01.2009 14:00 UTC
STD: 05.01.2009 15:00 LT
Offblock: 05.01.2009 15:11 UTC
Offblock: 05.01.2009 16:11 LT
Takeoff: 05.01.2009 15:35 UTC
Takeoff: 05.01.2009 16:35 LT
STA: 05.01.2009 16:20 UTC
STA: 05.01.2009 18:20 LT
Touchdown: 05.01.2009 17:29 UTC
Touchdown: 05.01.2009 19:29 LT
Onblock: 05.01.2009 17:34 UTC
Onblock: 05.01.2009 19:34 LT
Registration: ERAXT
Subfleet: 322
Owner: 9U

Oh, so ER-AXT stayed at FRA for 8 hours and did not fly elsewhere? Interesting. What about this flight?

2009-08-31 9U0863 KIV FRA 0505 0640 A320 fakepcy
2009-08-31 9U0864 FRA KIV 1500 1820 A320 fakepcy

They're asking for a KIV-LGW flight, and I'm thinking that the ground time at FRA is quite long to be able to do FRA-LGW-FRA.

 

[SaschaX99]

Whoa, where did you get this? I'm guessing it's now safe to eliminate S2-AFL.

There is a Mode-S group at groups.io

 

[zeus1309]

Oh, so ER-AXT stayed at FRA for 8 hours and did not fly elsewhere? Interesting. What about this flight?

2009-08-31 9U0863 KIV FRA 0505 0640 A320 fakepcy
2009-08-31 9U0864 FRA KIV 1500 1820 A320 fakepcy

They're asking for a KIV-LGW flight, and I'm thinking that the ground time at FRA is quite long to be able to do FRA-LGW-FRA.

2009-08-31 9U0863 KIV FRA 0505 0640 A320 fakepcy
Routing: KIV-FRA
STD: 31.08.2009 02:05 UTC
STD: 31.08.2009 05:05 LT
Offblock: 31.08.2009 01:56 UTC
Offblock: 31.08.2009 04:56 LT
Takeoff: 31.08.2009 02:01 UTC
Takeoff: 31.08.2009 05:01 LT
STA: 31.08.2009 04:40 UTC
STA: 31.08.2009 06:40 LT
Touchdown: 31.08.2009 04:17 UTC
Touchdown: 31.08.2009 06:17 LT
Onblock: 31.08.2009 04:27 UTC
Onblock: 31.08.2009 06:27 LT
Registration: ERAXT
Subfleet: 320
Owner: 9U

-------------
2009-08-31 9U0864 FRA KIV 1500 1820 A320 fakepcy
Routing: FRA-KIV
STD: 31.08.2009 13:00 UTC
STD: 31.08.2009 15:00 LT
Offblock: 31.08.2009 13:00 UTC
Offblock: 31.08.2009 15:00 LT
Takeoff: 31.08.2009 13:13 UTC
Takeoff: 31.08.2009 15:13 LT
STA: 31.08.2009 15:20 UTC
STA: 31.08.2009 18:20 LT
Touchdown: 31.08.2009 15:12 UTC
Touchdown: 31.08.2009 18:12 LT
Onblock: 31.08.2009 15:17 UTC
Onblock: 31.08.2009 18:17 LT
Registration: ERAXT
Subfleet: 320

 

[SaschaX99]

Hi @zeus1309 do you have any other info on what ER-AXT did at FRA on January 5, 2009?

2009-01-05 9U0863 KIV FRA 0525 0700 ER-AXT
2009-01-05 9U0864 FRA KIV 1500 1820 ER-AXT

Someone is looking for info for a KIV-LHR flight that day, and the most likely stop, if there was, was at FRA. I'm thinking that FlightStats lacked info for FRA-LHR-FRA.

Here a timetable. Wayback shows the following so I guess it's from 08/2009

FILE ARCHIVED ON 00:00:41 Aug 11, 2009 AND RETRIEVED FROM THE INTERNET ARCHIVE ON 21:00:49 Apr 05, 2026.




and here from 01/2009 FILE ARCHIVED ON 18:19:29 Jan 29, 2009 AND RETRIEVED FROM THE

 

[SaschaX99]

@fakepcy and here also with STD and STA for sommer 2009 adn winter 2008/2009

 

[fakepcy]

@fakepcy and here also with STD and STA for sommer 2009 adn winter 2008/2009

Interesting because that would mean:

2009-01-06 9U0883 KIV CDG 1830 2040 ER-AXV
2009-01-06 9U0883 CDG STN 2130 2130 ER-AXV
2009-09-01 9U0883 KIV CDG 1740 1940 ER-AXV
2009-09-01 9U0883 CDG LGW 2050 2040 ER-AXV

They probably got the details wrong which explains why I wasn't able to find anything on the given dates.

 

[SaschaX99]

Interesting because that would mean:

2009-01-06 9U0883 KIV CDG 1830 2040 ER-AXV
2009-01-06 9U0883 CDG STN 2130 2130 ER-AXV
2009-09-01 9U0883 KIV CDG 1740 1940 ER-AXV
2009-09-01 9U0883 CDG LGW 2050 2040 ER-AXV

I think so because according to the timetable there was no flight to London on Mondays.

2009-01-06 9U0883 KIV CDG 1830 2040 ER-AXV
2009-01-06 9U0883 CDG STN 2130 2130 ER-AXV

SBS-1/3-receivers located ~100km around Amsterdam.

• 504D51 ER-AXV A320 2011-2015
• 504001 ER-AXV! A320 MLD883 2335-0010

2009-09-01 9U0883 KIV CDG 1740 1940 ER-AXV
2009-09-01 9U0883 CDG LGW 2050 2040 ER-AXV

SBS-1/3-receivers located ~100km around Amsterdam.
504D51 ER-AXV A320 MLD883 2324-2353

 

[fakepcy]

Whoa, where did you get this? I'm guessing it's now safe to eliminate S2-AFL.

S2-AFL
BG88 DAC-BKK 11:20-15:00
BG89 BKK-DAC 16:15-18:00

Schedules clash with:
BG97 DAC-DEL 15:00-17:20
BG98 DEL-DAC 18:20-21:15

For some reason, S2-AFL and S2-AFM had exceptionally poor/limited tracking in 2019 compared to the previous and next years.

This leaves @ChronicTraveller's options down to S2-AFM and S2-AHO.

@ChronicTraveller this might be solved if you remember what the nose looked like. In November 2019, S2-AFM had eyebrows, whereas S2-AHO had none but was named Meghdoot.

 

[fakepcy]

Interesting because that would mean:

2009-01-06 9U0883 KIV CDG 1830 2040 ER-AXV
2009-01-06 9U0883 CDG STN 2130 2130 ER-AXV
2009-09-01 9U0883 KIV CDG 1740 1940 ER-AXV
2009-09-01 9U0883 CDG LGW 2050 2040 ER-AXV

They probably got the details wrong which explains why I wasn't able to find anything on the given dates.

Requester clarified that they weren't trying to suggest they stayed on the same plane. They may have transferred to other flights onwards to LHR and LGW.

2009-01-05 ------ FRA LHR ---- ---- fakepcy
2009-08-31 ------ FRA LGW ---- ---- fakepcy

Also, does anyone know the whereabouts of ER-SFA and ER-SFB on August 31, 2009? I'm trying to eliminate in order to get these two:

2009-08-31 2M0123 KIV BUD 0545 0610 SB20 fakepcy
2009-08-31 2M0133 KIV BUD 1615 1645 SB20 fakepcy

Don't add to the list.

I've seen pictures of them at airports like FRA and STR, but FlightStats doesn't give me anything when I try to decipher their flight numbers.

 

[zeus1309]

Requester clarified that they weren't trying to suggest they stayed on the same plane. They may have transferred to other flights onwards to LHR and LGW.

2009-01-05 ------ FRA LHR ---- ---- fakepcy
2009-08-31 ------ FRA LGW ---- ---- fakepcy

Also, does anyone know the whereabouts of ER-SFA and ER-SFB on August 31, 2009? I'm trying to eliminate in order to get these two:

2009-08-31 2M0123 KIV BUD 0545 0610 SB20 fakepcy
2009-08-31 2M0133 KIV BUD 1615 1645 SB20 fakepcy

Don't add to the list.

I've seen pictures of them at airports like FRA and STR, but FlightStats doesn't give me anything when I try to decipher their flight numbers.

all FRA-LHR on that day that i have.

Outbound	STD	Offblock	Destination	Position	Gate	Typ	Registration
LH 04722	07:30	08:11	LHR	V148	B60	A321	DAISB
BA 00901	07:45	08:40	LHR	D5	D5	A320	GEUUJ
LH 04724	08:25	09:05	LHR	V177	B60	B733	DABXN
LH 04726	10:05	11:59	LHR	V163	B60	A306	DAIAH
BA 00903	11:15	12:51	LHR	V109	D2	B763	GBNWA
LH 04728	12:30	14:25	LHR	A32	B61	A321	DAIRW
BA 00905	14:30	14:57	LHR	D4	D4	A320	GEUYC
LH 04732	15:15	15:52	LHR	V261	B61	B733	DABXN
LH 04736	16:15	16:57	LHR	V158	B30	A320	DAIQR
LH 04738	17:15	17:51	LHR	V148	B30	B735	DABIP
BA 00909	17:40	18:00	LHR	D1	D1	A320	GEUUW
LH 04742	20:10	20:32	LHR	V174	B30	A319	DAILS
BA 00913	20:35	20:56	LHR	D5	D5	A320	GEUUZ
LH 04744	21:20	22:43	LHR	A28	B30	A319	DAILU

For 31.08.2009 i cant help you. unfortunately for this day the file is missing

 

[SaschaX99]

Requester clarified that they weren't trying to suggest they stayed on the same plane. They may have transferred to other flights onwards to LHR and LGW.

2009-01-05 ------ FRA LHR ---- ---- fakepcy
2009-08-31 ------ FRA LGW ---- ---- fakepcy

Also, does anyone know the whereabouts of ER-SFA and ER-SFB on August 31, 2009? I'm trying to eliminate in order to get these two:

2009-08-31 2M0123 KIV BUD 0545 0610 SB20 fakepcy
2009-08-31 2M0133 KIV BUD 1615 1645 SB20 fakepcy

Don't add to the list.

I've seen pictures of them at airports like FRA and STR, but FlightStats doesn't give me anything when I try to decipher their flight numbers.

Here timetable KIV Airport 2009 (FILE ARCHIVED ON 02:51:27 Apr 10, 2009 )

When I look at the flight schedule, I see that the FRA flights operated by 9U were a codeshare with C9 (Cirrus Airlines) 9U863/C91150, and according to Wikipedia (the company was part of Team Lufthansa starting in 2000, became a Lufthansa partner after its dissolution in 2004, and offered codeshare flights in cooperation with Lufthansa, Swiss International Air Lines, and Air Moldova), then transferring at FRA and continuing on with LH makes sense

 

[Neo42]

@zeus1309

Könntest Du mir mit diesem Flug nochmal behilflich sein?

1998-07-08 LH0895 MUC HAJ ---- ---- Neo42

 

[zeus1309]

@zeus1309

Könntest Du mir mit diesem Flug nochmal behilflich sein?

1998-07-08 LH0895 MUC HAJ ---- ---- Neo42

aber immer doch

Details
1998-07-08 LH0895 MUC HAJ ---- ---- Neo42
Routing: MUC-HAJ
STD: 08.07.1998 15:45 UTC
STD: 08.07.1998 17:45 LT
Offblock: 08.07.1998 15:42 UTC
Offblock: 08.07.1998 17:42 LT
Takeoff: 08.07.1998 15:57 UTC
Takeoff: 08.07.1998 17:57 LT
STA: 08.07.1998 16:55 UTC
STA: 08.07.1998 18:55 LT
Touchdown: 08.07.1998 16:50 UTC
Touchdown: 08.07.1998 18:50 LT
Onblock: 08.07.1998 16:54 UTC
Onblock: 08.07.1998 18:54 LT
Registration: DAIQA
Subfleet: 320
Owner: LH
Departure Gate: A16
Departure Position: 102
Arrival Gate: A03
Arrival Position: A03

-------------



Lines
found 1998-07-08 LH0895 MUC HAJ ---- ---- Neo42 DAIQA #8713

 

[gotflyer]

I will post the ones that have to be reopened one by one for a better overview. @bursche99

1997-06-17 EWR ARN 22:00 12:20 @gotflyer (Probably SK)

I will post the ones that have to be reopened one by one for a better overview. @bursche99

1996-06-24 EWR ARN 22:00 12:20 gotflyer (Probably SK)

I will post the ones that have to be reopened one by one for a better overview. @bursche99

2000-01-03 SK0903 ARN EWR @gotflyer

disappointing to lose these three, but incorrect data is worse than no data

 

[fakepcy]

Any luck with these flights? No need to add them to the list since I'm just checking something.

2010-10-06 PG0273 BKK HKT 1355 1520 A320 fakepcy
2011-03-29 MH0715 KUL DPS 0850 1150 A333 fakepcy
2011-04-11 MH0714 DPS KUL 1250 1550 A333 fakepcy
2011-05-20 MH0786 KUL HKT 0930 0945 B734 fakepcy
2011-05-27 MH0791 HKT KUL 1805 2030 B734 fakepcy
2011-09-11 PG0274 HKT BKK 1610 1735 A320 fakepcy
2011-09-11 EK0373 BKK DXB 2120 0030 B77W fakepcy

 

[SaschaX99]

disappointing to lose these three, but incorrect data is worse than no data

I'm still sorry about that.

Maybe I found a solution for

1997-06-17 EWR ARN 22:00 12:20 @gotflyer (Probably SK)

The problem with the flights was that, for the return flights, I can no longer be sure whether they were tracked in Europe or the U.S. However, this doesn’t make a difference for the outbound flights, since they depart and arrive on the same day.

Assuming that, the following would apply to the flight:


outgoing flights
flug 17 18
SAS901 KDO ---
SAS903 RCH RCG
SAS907 RCG RCK
SAS911 RCK RCI
SAS937 --- ---
SAS941 RCL RCH

incoming flights
flug 17 18
SAS904 RCH RCG
SAS908 RCG RCK
SAS912 RCK RCH


SK907/908 FBU-EWR-FBU
SK903/904 ARN-EWR-ARN
SK911/912 CPH-EWR-CPH


17.06. SK903 RCH 18.06. RCG
17.06. SK907 RCG 18.06. RCK
17.06. SK911 RCK 18.06. RCI

SK903 was on 17 June RCH, which departed on 18 June as SK941 CPH-ORD, confirming Zeus’s theory that the return flights were tracked in Europe, as according to Atlantic Overflight, SK912 on 18 June was the RCH, meaning it was also in CPH on that day to fly SK941.

SK907 was on 17 June RCG, which departed on 18 June as SK903 ARN-EWR, which supports Zeus’s theory that the return flights were tracked in Europe, as according to Atlantic Overflight, SK904 was the RCG on 18 June, meaning it was also in ARN on that day to fly SK903.

Could you check if this makes sense for you because then we have as solution LN-RCG

 

[SaschaX99]

Unfortunately, I realized that the flight paths from the Atlantic Overflights source were likely not always tracked in Maine, USA, which is why none of the solutions for flights from the US to Europe are 100% certain. I'm so sorry for this.

I will post the ones that have to be reopened one by one for a better overview. @bursche99

1996-06-24 EWR ARN 22:00 12:20 gotflyer (Probably SK)

outgoing flights
Flug 24 25
SAS903 RCG RCK
SAS907 RCK KDL
SAS911 KDL RCI
SAS913 --- RCH


Incoming flighs
Flug 24 25
SAS904 RCG RCK
SAS908 RCK KDL
SAS912 RCH RCG
SAS914 RCE ---

disappointing to lose these three, but incorrect data is worse than no data

When I use the same logic as in #8716 then the reg should be LN-RCK.

 

[SaschaX99]

So diesen hab ich mir auch nochmal angeschaut und er ist definitiv falsch

1997-03-07 DL0140 JFK-BRU 1925 L1011 cityman N754DL #4653

Die N754DL ist DL0124 ATL-BRU am 07.031997 und DL0125 BRU-ATL am 08.03.1997 geflogen.

Für die Kombi DL0140/141 ist leider nichts zu finden und ATL und JFK waren auch die einzigen US Flüge von DL.

 

[gotflyer]

I'm still sorry about that.

Absolutely no need for that, you all have solved so many flights for me, I'm eternally grateful.

outgoing flights
flight 17 18
SAS901 KDO ---
SAS903 RCH RCG
SAS907 RCG RCK
SAS911 RCK RCI
SAS937 ---- ---
SAS941 RCL RCH

incoming flights
flight 17 18
SAS904 RCH RCG
SAS908 RCG RCK
SAS912 RCK RCH


SK907/908 FBU-EWR-FBU
SK903/904 ARN-EWR-ARN
SK911/912 CPH-EWR-CPH


17.06. SK903 RCH 18.06. RCG
17.06. SK907 RCG 18.06. RCK
17.06. SK911 RCK 18.06. RCI

SK903 was on 17 June RCH, which departed on 18 June as SK941 CPH-ORD, confirming Zeus’s theory that the return was traveled in Europe, as according to Atlantic Overflight, SK912 on 18 June was the RCH, it was also in CPH that on day to fly SK941.

SK907 was on 17 June RCG, which departed on 18 June as SK903 ARN-E whichWR, supports Zeus’s theory that the return was traveled in Europe, as according to Atlantic Overflight, SK904 was the RCG on 18 June meaning, it was in that that on day to fly SK903.

I'm going to restate what you wrote above by registration, just to make sure I'm understanding.

LN-RCH:

1997-06-17 SK0903 ARN - EWR
1997-06-17 SK0912 EWR - CPH (arriving CPH 1997-06-18)
1997-06-18 SK0941 CPH - ORD

LN-RCG:

1997-06-17 SK0907 FBU - EWR
1997-06-17 SK0904 EWR - ARN (arriving ARN 1997-06-18)
1997-06-18 SK0903 ARN - EWR

LN-RCK:

1997-06-17 SK0911 CPH - EWR
1997-06-17 SK0908 EWR - FBU (arriving FBU 1997-06-18)
1997-06-18 SK0907 FBU - EWR

Could you check if this makes sense for you because we have as solution LN-RCG

So if I understood it correctly, and my restating above is what you meant then I agree that this can be considered solved.

 

[SaschaX99]

Absolutely no need for that, you all have solved so many flights for me, I'm eternally grateful.



I'm going to restate what you wrote above by registration, just to make sure I'm understanding.

LN-RCH:

1997-06-17 SK0903 ARN - EWR
1997-06-17 SK0912 EWR - CPH (arriving CPH 1997-06-18)
1997-06-18 SK0941 CPH - ORD

LN-RCG:

1997-06-17 SK0907 FBU - EWR
1997-06-17 SK0904 EWR - ARN (arriving ARN 1997-06-18)
1997-06-18 SK0903 ARN - EWR

LN-RCK:

1997-06-17 SK0911 CPH - EWR
1997-06-17 SK0908 EWR - FBU (arriving FBU 1997-06-18)
1997-06-18 SK0907 FBU - EWR



So if I understood it correctly, and my restating above is what you meant then I agree that this can be considered solved.

I’d say yes, because regardless of whether the tracking was done in Europe or the US, westbound flights are almost always tracked on the same day (unless the flight departs very late in the evening).

Assuming the above is correct, the records for the flights from Scandinavia to the USA on the 17th and 18th are therefore correct. Furthermore, on the 18th, the aircraft were not back at their departure airport from the 17th.

So, unless there were transfer flights between the Scandinavian airports, LN-RCG should be correct.

 

[marco1]

1994-03-26 AB---- NUE LPA 0500 0845 B734 marco1 (D-ABAB,-C,-D,-E,-F,-G, see #8341)
1994-04-09 AB---- LPA NUE 1520 2050 B734 marco1 (evtl. AB0911, D-ABAB,-C,-D,-E,-F,-G, see #8341)

Durch die Daten von @zeus1309 kann ich zumindest schon mal gut eingrenzen auf 2 bzw. 3 der 6 möglichen:
1994-03-26 AB0910 NUE LPA 0500 0845 B734 marco1 --> D-ABAB,-D,-F
1994-04-09 AB0911 LPA NUE 1520 2050 B734 marco1 --> D-ABAC,-F
Meine spanische BER911 Bordkarte ist nun auch relativ sicher hier zuzuordnen.

1994-08-25 AB0902 NUE IBZ 0525 ---- B734 marco1 (D-ABAB,-C,-D,-E,-F,-G, see #8359)
1994-09-08 AB0903 IBZ NUE 0805 ---- B734 marco1 (D-ABAB,-C,-D,-E,-F,-G, see #8342)

Hier war nicht viel zu holen, da die Maschine wohl direkt nach NUE zurückflog und keinen Berlin Bezug hatte und nicht in den Daten erscheint.
Nur jeweils eine der 6 Maschinen kann ausgeschlossen werden:
1994-08-25 AB0902 NUE IBZ 0525 ---- B734 marco1 -->D-ABAB,-C,-D,-E,-G
1994-09-08 AB0903 IBZ NUE 0805 ---- B734 marco1 -->D-ABAB,-C,-D,-F,-G


@zeus1309
ich würde mich noch über das Air Berlin Datenpaket vom Aug&Sept. 1992 freuen (D-ABAB, -AC, -AD),
sowie von der Germania im Aug&Sept. 1996 (D-AGE* + D-ABWA) falls da überhaupt was vorhanden ist...

 

[ChronicTraveller]

@ChronicTraveller this might be solved if you remember what the nose looked like. In November 2019, S2-AFM had eyebrows, whereas S2-AHO had none but was named Meghdoot.

Unfortunately, I don't see any mention in my notes, nor recall either eyebrows or if it had a name.

However, not sure if this is coincidence or not. I do have in my notes that when we landed at DAC, the plane stopped on the tarmac to let out 3 VIPs into waiting cars. I just did a web search on 'Megdhoot', and it is a name used in India for their VIP jet. Biman seemed less certain--but it stated they their use newer planes for VIPs. AHO was a newer 737; AFM is older.

So I wouldn't call it conclusive, but points to AHO/Meghdoot maybe? And if anybody is wondering 'meghdoot' means 'cloud messenger' in Sanskrit.

 

[fakepcy]

Unfortunately, I don't see any mention in my notes, nor recall either eyebrows or if it had a name.

However, not sure if this is coincidence or not. I do have in my notes that when we landed at DAC, the plane stopped on the tarmac to let out 3 VIPs into waiting cars. I just did a web search on 'Megdhoot', and it is a name used in India for their VIP jet. Biman seemed less certain--but it stated they their use newer planes for VIPs. AHO was a newer 737; AFM is older.

So I wouldn't call it conclusive, but points to AHO/Meghdoot maybe? And if anybody is wondering 'meghdoot' means 'cloud messenger' in Sanskrit.

S2-AHO
2019-11-14
BG87 KUL-DAC 03:00-04:45
BG417 DAC-CGP 12:00-12:45
BG418 CGP-DAC 13:30-14:15
BG97 DAC-DEL 15:00-17:20
BG98 DEL-DAC 18:20-21:15

2019-11-15
??
BG69 DAC-KTM 14:30-15:45

I hate how the 45-minute ground time at DAC and the VIP thing make sense, but the lack of data, especially from S2-AFM, messes up my brain.

 

[gotflyer]

So, unless there were transfer flights between the Scandinavian airports, LN-RCG should be correct.

Agreed, with the exception of broken aircraft I cannot imagine they would do repositioning flights from e.g. ARN to CPH.

1996-06-24 EWR ARN 22:00 12:20 gotflyer (Probably SK)

outgoing flights
Flug 24 25
SAS903 RCG RCK
SAS907 RCK KDL
SAS911 KDL RCI
SAS913 --- RCH


Incoming flighs
Flug 24 25
SAS904 RCG RCK
SAS908 RCK KDL
SAS912 RCH RCG
SAS914 RCE ---

With just this I can't get things to quite line up, just rewriting this as I did above ordering it by registration I get this:

LN-RCG:

1996-06-24 SK0903 ARN - EWR
1996-06-24 SK0904 EWR - ARN (arriving ARN on 1997-06-25)
<what happened here>
1996-06-25 SK0912 EWR - CPH (arriving CPH on 1997-06-26)

LN-RCK:

1996-06-24 SK0907 FBU - EWR
1996-06-24 SK0908 EWR - FBU (arriving FBU on 1997-06-25)
<what happened here>
1996-06-25 SK0903 ARN - EWR
1996-06-25 SK0904 EWR - ARN (arriving ARN on 1997-06-25)

LN-RCH:

1996-06-24 SK0912 EWR - CPH (arriving CPH on 1997-06-25)
1996-06-25 SK0913 CPH - EWR


OY-KDL:

1996-06-24 SK0911 CPH - EWR
<what happened here>
1996-06-25 SK0907 FBU - EWR
1996-06-25 SK0908 EWR - FBU (arriving FBU on 1997-06-26)

LN-RCI:

1996-06-25 SK0911 CPH - EWR

LN-RCE:

1996-06-24 SK0914 EWR - CPH (arriving CPH on 1997-06-25)

Assuming that we are only certain about westbound flights, I then looked to see how we could possible make it work out (highlights in orange).


LN-RCG:

1996-06-24 SK0903 ARN - EWR

LN-RCK:

1996-06-24 SK0907 FBU - EWR
1996-06-24 SK0904 EWR - ARN (arriving ARN on 1997-06-25)
1996-06-25 SK0903 ARN - EWR

LN-RCH:

1996-06-25 SK0913 CPH - EWR

OY-KDL:

1996-06-24 SK0911 CPH - EWR
1996-06-24 SK0908 EWR - FBU (arriving FBU on 1997-06-25)
1996-06-25 SK0907 FBU - EWR

LN-RCI:

1996-06-25 SK0911 CPH - EWR

This leaves the following as unresolved, I've just left them associated with the flight numbers you indicated, I am not sure I can confidently confirm them with the information I currently have.

LN-RCG:
1996-06-25 SK0912 EWR - CPH (arriving CPH on 1997-06-26)

LN-RCH:
1996-06-24 SK0912 EWR - CPH (arriving CPH on 1997-06-25)

LN-RCK:
1996-06-25 SK0904 EWR - ARN (arriving ARN on 1997-06-26)

OY-KDL:
1996-06-25 SK0908 EWR - FBU (arriving FBU on 1997-06-26)

LN-RCE:
1996-06-24 SK0914 EWR - CPH (arriving CPH on 1997-06-25)

When I use the same logic as in #8716 then the reg should be LN-RCK.

Yes this seems to be the case, even though it took me a while to get there.

 

[SaschaX99]

Agreed, with the exception of broken aircraft I cannot imagine they would do repositioning flights from e.g. ARN to CPH.



With just this I can't get things to quite line up, just rewriting this as I did above ordering it by registration I get this:

LN-RCG:

1996-06-24 SK0903 ARN - EWR
1996-06-24 SK0904 EWR - ARN (arriving ARN on 1997-06-25)
<what happened here>
1996-06-25 SK0912 EWR - CPH (arriving CPH on 1997-06-26)

LN-RCK:

1996-06-24 SK0907 FBU - EWR
1996-06-24 SK0908 EWR - FBU (arriving FBU on 1997-06-25)
<what happened here>
1996-06-25 SK0903 ARN - EWR
1996-06-25 SK0904 EWR - ARN (arriving ARN on 1997-06-25)

LN-RCH:

1996-06-24 SK0912 EWR - CPH (arriving CPH on 1997-06-25)
1996-06-25 SK0913 CPH - EWR


OY-KDL:

1996-06-24 SK0911 CPH - EWR
<what happened here>
1996-06-25 SK0907 FBU - EWR
1996-06-25 SK0908 EWR - FBU (arriving FBU on 1997-06-26)

LN-RCI:

1996-06-25 SK0911 CPH - EWR

LN-RCE:

1996-06-24 SK0914 EWR - CPH (arriving CPH on 1997-06-25)

Assuming that we are only certain about westbound flights, I then looked to see how we could possible make it work out (highlights in orange).


LN-RCG:

1996-06-24 SK0903 ARN - EWR

LN-RCK:

1996-06-24 SK0907 FBU - EWR
1996-06-24 SK0904 EWR - ARN (arriving ARN on 1997-06-25)
1996-06-25 SK0903 ARN - EWR

LN-RCH:

1996-06-25 SK0913 CPH - EWR

OY-KDL:

1996-06-24 SK0911 CPH - EWR
1996-06-24 SK0908 EWR - FBU (arriving FBU on 1997-06-25)
1996-06-25 SK0907 FBU - EWR

LN-RCI:

1996-06-25 SK0911 CPH - EWR

This leaves the following as unresolved, I've just left them associated with the flight numbers you indicated, I am not sure I can confidently confirm them with the information I currently have.

LN-RCG:
1996-06-25 SK0912 EWR - CPH (arriving CPH on 1997-06-26)

LN-RCH:
1996-06-24 SK0912 EWR - CPH (arriving CPH on 1997-06-25)

LN-RCK:
1996-06-25 SK0904 EWR - ARN (arriving ARN on 1997-06-26)

OY-KDL:
1996-06-25 SK0908 EWR - FBU (arriving FBU on 1997-06-26)

LN-RCE:
1996-06-24 SK0914 EWR - CPH (arriving CPH on 1997-06-25)



Yes this seems to be the case, even though it took me a while to get there.

Maybe the following can answer the unresolved.

All westbound flights 06/1996

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

SAS903

RCI

RCI

RCI

RCG

RCH

RCG

RCG

RCH

RCH

RCK

RCG

RCK

RCK

RCI

RCG

RCK

RCI

RCG

RCI

RCI

RCH

RCH

RCK

RCG

RCK

KDL

RCK

RCG

RCI

RCI

SAS907

RCG

RCG

RCG

RCH

RCI

RCI

RCH

RCK

RCG

RCH

RCK

RCG

RCI

RCG

RCK

RCI

RCG

RCH

RCH

RCG

RCI

RCG

RCG

RCK

KDL

RCK

RCI

RCI

RCK

RCK

SAS911

KDL

KDH

RCH

RCI

RCG

RCH

RCK

RCG

RCK

RCG

RCI

RCI

DOC

RCK

RCI

RCG

RCH

RCI

RCH

RCG

RCK

RCH

KDL

RCI

RCI

RCG

RCK

RCG

RCD

SAS913

RCE

RCK

KDN

RCE

RCH

RCH

RCE

KDN

RCK

KDL

KDN

RCE

RCH

DOC

KDN

KDM

All eastbound flights 06/1996

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

SAS904

RCI

RCI

RCI

RCG

RCH

RCG

RCG

RCH

RCH

RCK

RCG

RCK

RCG

RCI

RCG

RCK

RCI

RCG

RCI

RCI

RCH

RCH

RCK

RCG

RCK

KDL

RCK

RCG

RCI

RCI

SAS908

RCG

RCG

RCG

RCH

RCI

RCI

RCH

RCK

RCG

RCH

RCK

RCG

RCI

RCG

RCK

RCI

RCG

RCH

RCH

RCI

RCG

RCG

RCK

KDL

RCK

RCI

RCI

RCK

RCK

SAS912

KDO

KDL

KDH

RCI

RCG

RCH

RCI

RCG

RCK

RCG

RCH

RCI

RCK

DOC

RCI

RCG

RCK

RCI

RCG

RCH

RCG

RCI

RCH

RCH

RCG

RCI

KDL

RCK

RCG

RCG

SAS914

RCE

RCK

KDN

RCE

RCH

RCH

RCE

KDN

RCK

KDL

KDN

RCE

RCH

DOC

KDN