expected:
09:45lt BARON71 C130
Peter
ETAR 20-2-2014
Forum rules
 | Mode S / SBS and radio logs, airfield specific, are allowed, but always state your source, mode S / SBS or air traffic conversations. These logs can be placed in the "day topic" so a separate Mode S / SBS radio log is not necessary |
-
jreijmer
- Scramble Addict
- Posts: 1028
- Joined: 02 Sep 2006, 10:25
- Type of spotter: F1
- Subscriber Scramble: Jeroen van Reijmersdal
- Location: Bemmel
Re: ETAR 20-2-2014
Looks like this is going to be a HC-130J.JetStar2 wrote:expected:
09:45lt BARON71 C130
Peter
BR,
Jeroen
-
Canon-Tim
- Scramble Junior
- Posts: 112
- Joined: 09 Nov 2013, 20:12
- Type of spotter: Radarspotter / Photographer
- Subscriber Scramble: yes
- Location: Ramstein, DE
Re: ETAR 20-2-2014
Thank you guys.
Cheers,
Tim
Cheers,
Tim
-
JetStar2
- Scramble Addict
- Posts: 1036
- Joined: 01 May 2004, 23:08
- Subscriber Scramble: JetStar2
- Location: Luxemburg
- Contact:
Re: ETAR 20-2-2014
BARON71 on its way, expected to land 09:30 local. It should leave again 17:05 local.
two C-17 arrivals:
09:33 RCH694
11:38 RCH241
Peter
two C-17 arrivals:
09:33 RCH694
11:38 RCH241
Peter
-
Canon-Tim
- Scramble Junior
- Posts: 112
- Joined: 09 Nov 2013, 20:12
- Type of spotter: Radarspotter / Photographer
- Subscriber Scramble: yes
- Location: Ramstein, DE
Re: ETAR 20-2-2014
Times provided are in local time. Since flights are logged via ADS-B actual time of departure and landing may differ by +-5min. Bold ones are the highlights of the day!
Movements 20.02.2014:
SOURCE: ADS-B Mode-S Beast
DEPARTURES:
06:24 97-0042 C-17A as "RCH 481"
11:16 70-0451 C-5A 433rd AW AFRC as "RCH 266"
11:09 08-8199 C-17A as "RCH 393"
12:51 83-0079 KC-10A 305th AMW as "RCH 781"
13:59 03-3122 C-17A as "RCH 180"
14:42 N85 CL-601 FAA as "FLC 85"
15:56 01-0189 C-17A as "RCH 954"
16:51 09-5708 HC-130J 79th RQS ACC as "BARON 71"
18:15 N918AX B772 Omni Air as "CMB 119"
20:38 N927AX B772 Omni Air as "CMB 559"
23:40 04-4129 C-17A as "RCH 536"
ARRIVALS:
09:03 09-5708 HC-130J 79th RQS ACC as "BARON 71"
09:12 03-3118 C-17A as "RCH 920"
09:25 03-3125 C-17A as "RCH 694"
10:42 01-0188 C-17A as "RCH 147"
11:30 69-0024 C5M 436th AW as "RCH 543"
11:36 95-0102 C-17A as "RCH 241"
12:13 N918AX B772 Omni Air as "CMB 119"
16:09 N85 CL-601 FAA as "FLC 85"
16:30 N927AX B772 Omni Air as "CMB 559"
18:09 N272WA MD11 World Airways as "CMB 1115"
18:40 06-6160 C-17A as "RCH 580"
19:11 08-8201 C-17A as "RCH 734"
19:28 97-0042 C-17A as "RCH 481"
LOCALS:
01:14 92-0375 C-20H as "FENDY 23"
06:30 07-8613 C-130J as "HKY 700"
08:01 08-8601 C-130J as "HKY 05"
08:52 06-8611 C-130J as "HKY 150"
10:16 84-0109 C-21A as "VALOR 21"
10:54 84-0081 C-21A as "SPAR 91"
16:08 84-0110 C-21A as "JALOP 32"
16:31 90-0300 C-20H as "FENDY 54"
Movements 20.02.2014:
SOURCE: ADS-B Mode-S Beast
DEPARTURES:
06:24 97-0042 C-17A as "RCH 481"
11:16 70-0451 C-5A 433rd AW AFRC as "RCH 266"
11:09 08-8199 C-17A as "RCH 393"
12:51 83-0079 KC-10A 305th AMW as "RCH 781"
13:59 03-3122 C-17A as "RCH 180"
14:42 N85 CL-601 FAA as "FLC 85"
15:56 01-0189 C-17A as "RCH 954"
16:51 09-5708 HC-130J 79th RQS ACC as "BARON 71"
18:15 N918AX B772 Omni Air as "CMB 119"
20:38 N927AX B772 Omni Air as "CMB 559"
23:40 04-4129 C-17A as "RCH 536"
ARRIVALS:
09:03 09-5708 HC-130J 79th RQS ACC as "BARON 71"
09:12 03-3118 C-17A as "RCH 920"
09:25 03-3125 C-17A as "RCH 694"
10:42 01-0188 C-17A as "RCH 147"
11:30 69-0024 C5M 436th AW as "RCH 543"
11:36 95-0102 C-17A as "RCH 241"
12:13 N918AX B772 Omni Air as "CMB 119"
16:09 N85 CL-601 FAA as "FLC 85"
16:30 N927AX B772 Omni Air as "CMB 559"
18:09 N272WA MD11 World Airways as "CMB 1115"
18:40 06-6160 C-17A as "RCH 580"
19:11 08-8201 C-17A as "RCH 734"
19:28 97-0042 C-17A as "RCH 481"
LOCALS:
01:14 92-0375 C-20H as "FENDY 23"
06:30 07-8613 C-130J as "HKY 700"
08:01 08-8601 C-130J as "HKY 05"
08:52 06-8611 C-130J as "HKY 150"
10:16 84-0109 C-21A as "VALOR 21"
10:54 84-0081 C-21A as "SPAR 91"
16:08 84-0110 C-21A as "JALOP 32"
16:31 90-0300 C-20H as "FENDY 54"
Last edited by Canon-Tim on 21 Feb 2014, 03:02, edited 3 times in total.
-
Eric van Lisdonk
- Scramble Master
- Posts: 2566
- Joined: 19 Mar 2004, 23:33
- Subscriber Scramble: Eric van Lisdonk
- Location: Ramstein and Gilze-Rijen Air Base
Re: ETAR 20-2-2014
Are you 100% sure that the Mildenhall KC-135 64-14830 landed in RS??
Re: ETAR 20-2-2014
He didn't land, as he landed egul around 12.35 our time.
So if he was down in RS, it could only be for a low approach, but also doubt that because of his mission.....
Oscar
So if he was down in RS, it could only be for a low approach, but also doubt that because of his mission.....
Oscar
-
Eric van Lisdonk
- Scramble Master
- Posts: 2566
- Joined: 19 Mar 2004, 23:33
- Subscriber Scramble: Eric van Lisdonk
- Location: Ramstein and Gilze-Rijen Air Base
Re: ETAR 20-2-2014
Exact Oscar that's why i ask.Oscar01 wrote:He didn't land, as he landed egul around 12.35 our time.
So if he was down in RS, it could only be for a low approach, but also doubt that because of his mission.....
Oscar
-
Canon-Tim
- Scramble Junior
- Posts: 112
- Joined: 09 Nov 2013, 20:12
- Type of spotter: Radarspotter / Photographer
- Subscriber Scramble: yes
- Location: Ramstein, DE
Re: ETAR 20-2-2014
Okay, thank you guys for the correction. Here is my original log. I see what happened, the KC-135 and a previous C-17 flight were mixed up in the log file. Don´t know why that happened, never happened before.
Hex Callsign Reg Type Route FAlt Lalt Fsqk Lsqk Date FTime Date LTime
AE07E5 RCH241 95-0102 C17 14000 1200 4731 4731 20.02.2014 10:23:43 20.02.2014 10:35:29
AE07C5 QID93 64-14830 K35R 7700 7700 5774 5774 20.02.2014 10:27:52 20.02.2014 10:27:52
AE07C5 RCH241 64-14830 K35R 3400 1500 5774 5774 20.02.2014 10:33:33 20.02.2014 10:34:54
This was logged with my box at live-mil-mode-s:
RCH241 64-14830 2014-02-20 10:26:43 KC-135R United States USAFE | 100ARW | 351ARS [EGUN] Ramstein, DE 5774 38000
QID93 64-14830 2014-02-20 10:26:43 KC-135R United States USAFE | 100ARW | 351ARS [EGUN] Ramstein, DE 5774 38000
Here it says the KC-135R was flying at an altitude of 38000ft but mixed up the callsigns as well.
Very strange...I think this was due to the fact that the hex IDs are almost identical. AE07E5 for the C-17 and AE07C5 for the KC-135R. Good to know that the logging software has issues with that.
Thank you again.
Tim
Hex Callsign Reg Type Route FAlt Lalt Fsqk Lsqk Date FTime Date LTime
AE07E5 RCH241 95-0102 C17 14000 1200 4731 4731 20.02.2014 10:23:43 20.02.2014 10:35:29
AE07C5 QID93 64-14830 K35R 7700 7700 5774 5774 20.02.2014 10:27:52 20.02.2014 10:27:52
AE07C5 RCH241 64-14830 K35R 3400 1500 5774 5774 20.02.2014 10:33:33 20.02.2014 10:34:54
This was logged with my box at live-mil-mode-s:
RCH241 64-14830 2014-02-20 10:26:43 KC-135R United States USAFE | 100ARW | 351ARS [EGUN] Ramstein, DE 5774 38000
QID93 64-14830 2014-02-20 10:26:43 KC-135R United States USAFE | 100ARW | 351ARS [EGUN] Ramstein, DE 5774 38000
Here it says the KC-135R was flying at an altitude of 38000ft but mixed up the callsigns as well.
Very strange...I think this was due to the fact that the hex IDs are almost identical. AE07E5 for the C-17 and AE07C5 for the KC-135R. Good to know that the logging software has issues with that.
Thank you again.
Tim
Re: ETAR 20-2-2014
Hello Canon-Tim,
Thank you for all the logs. Really appreciated, keep them comming.
One question, what was the hex-code of the HC-130 09-5708 ?
Thank you for all the logs. Really appreciated, keep them comming.
One question, what was the hex-code of the HC-130 09-5708 ?
-
Canon-Tim
- Scramble Junior
- Posts: 112
- Joined: 09 Nov 2013, 20:12
- Type of spotter: Radarspotter / Photographer
- Subscriber Scramble: yes
- Location: Ramstein, DE
Re: ETAR 20-2-2014
Hi there,cis wrote:Hello Canon-Tim,
Thank you for all the logs. Really appreciated, keep them comming.
One question, what was the hex-code of the HC-130 09-5708 ?
thank you very much I´ll try to do so
Unfortunately the HC-130J didn´t transmit any ADS-B data so I have no hex Code.
Cheers,
Tim