1415 Greyhawk3 checking in with zny on 307
Tinear they are on range now but didn't catch callsign 1501
Tinear they are on range now but didn't catch callsign 1501
Last edited:
Sticky Thread for MilAir
- Thread starter TinEar
- Start date
- Status
n3bxv
Member
TinEar said:
Updated the 113th Wing Wiki as well. Do you have a good freq for V-9??
TinEar said:
Updated the 177th Fighter Wing Wiki as well.
I should start having a little more non-work time to do more work on the Wiki and do a little more scanning in the next couple of weeks, I hope!
Last edited:
TinEar
Member
Thanks Chuck for doing that updating. Will be glad to see you back home to help with this MilAir activity. No, not only don't I have a good freq for the DC-ANG's V-9, I consider the standard list we all have for V-9 through V-17 as tentative and probably no good either.
1845: There is a pair of fighters working Bollen Range on «237.2»
1850: Fighter activity on «141.725» and it's the same guys working Bollen. Since that tac freq doesn't fit for MD/DC/VA/NJ-ANG units, I think we can safely label it as A-10s from the PA-ANG at Willow Grove.
1852: Evac 71474 calling Andrews on «141.5» - obviously a mistake. He then tries «141.55» and gets no reply so finally goes to «378.1» where he reports 30 minutes out, needs parking, has 4 Space A pax to offload, needs a Payloader and airstairs and transportation for the pax. He wants to do a quick turnaround and is inquiring about the upcoming ramp freeze.
1859: Fighters on Bollen «237.2» mention heading for Slate Run at 11,000 feet and over on their «141.725» freq they are talking about refueling.
1900: Fighter on Bollen calls BALKY range controller for count on BDUs used. I think he used callsign CADE for himself. If so, that confirms PA-ANG. «237.2»
1901: Yes, confirmed CADE 1 and 2 are the callsigns of the fighters at Bollen. He says rather than refueling, they are going to RTB because of a stuck BDU. «237.2»
1902: CADE wants BALKY to call Pittsburgh or Ohio or wherever the tanker is from to let him know they won't be refueling. I think that reference earlier to going to Slate Run was in reference to going to the Duke MOA for refueling before they decided to cancel it. At 1903, CADE signs off the freq. «237.2»
If that tanker was indeed from Pittsburgh, there will be a STEEL KC-135 flying around the area. He's all yours Dave.
1905: Navy 017 off Andrews «118.4»
1906: JOSA 488 to SAM Command on «141.55» home station C-21, tail #40076, arriving Andrews in 25 minutes, done with their mission upon landing, no pax or cargo to download, wants crew bus for 2 to meet them in 9 row where they'll park.
1907: CADE 1/2 with ZNY-North Mountain on «338.3» leaving 15,000 for 13,000. They are also still chatting on «141.725» I never hear the PA-ANG using channel references to be able to log them like we have the other units.
1909: CRAB 52 (C-130J MD-ANG Martin State) with Martin State Tower on «121.3» for landing...they're 6 miles northwest of the airfield at this time.
1911: CADE 1/2 descending to ?3,000? feet «338.3»
1912: UGLY flight of two (A-10 PA-ANG Willow Grove) now heading for the Bollen Range. Talking with BALKY on «237.2» Meanwhile, over on «141.725» one of the CADEs asks, "Is that our guys over there going to the range?"
1915: The CADEs don't know which of them has the hung BDU. All they know is that they asked how many impacted at the range and they have that number versus the number they knew they carried and thought they fired. «141.725»
NOTE: Remember, we had a couple of Willow Grove A-10s deploy into Martin State this afternoon using their travelling callsign - SANDY.
1920: Evac 71474 landing with Andrews Tower on «118.4»
1922: UGLY flight attacking targets at the Bollen Range. This might just be a flight of three A-10s, rather than two.
Unable to find a tac freq for the UGLY flight...have two scanners searching...one covering the 138-144 range and the other 138 extended to 149.
1935: Have some fighters on tac freq «143.025» Not sure yet if it's the UGLY flight.
1937: Have someone working HUNTRESS on «364.2» No ID heard yet.
1938: Fighters on «143.025» talking about landing on runway 24 visual. Runways at Willow Grove are 15/33. Hmmmm.
1940: The aircraft with HUNTRESS on «364.2» is REACH 111.
1941: Fighters on «143.025» telling Ebonics jokes (and they're not even funny)...sounds like just two of them though and the UGLY flight was three. Between that and the runway 24 mention, it doesn't appear to be the UGLY tac freq.
Have the 143.025 freq on the webcast for now. Lots of chat from these guys.
1949: Fighters on «143.025» still chatting - profanely - and are very loud and clear at this time.
1953: The «143.025» guys just mentioned calling Atlantic Aviation.
http://www.atlanticaviation.com/
1955: REACH 9017 to Dover Command Post on «349.4» reports 20 minutes out, A-2, no offload.
2009: Tanker interplane freq «139.875» active.
2037: Tanker interplane still busy with chat from time to time «139.875» (IDed as TEAM 45 and 46 from another source working up around Albany NY for refueling activity)
2042: DC KC-135 tanker about to land at Andrews. He's with LIBERATOR on squadron freq «351.2» reports A-1
2044: Army 053 landing Andrews «118.4»
2056: JOSA 611, after calling SAM Command several times, finally makes contact on «378.1» reports arriving at Andrews at 0215Z, A-1, is a C-21 with tail #40077, will be mission complete upon arriving, has 2 Duty Pax to offload - an A-4 plus 1, needs crew transportation to pick them up in 9 row.
2102: DC 02 (female) (KC-135 756th ARS Andrews) to LIBERATOR on «351.2» asking if the ramp freeze is getting ready to go into effect or is being lifted. Reply from ground not heard so don't know the answer.
Thanks Dave...that also confirms my statement of three UGLYs. It also confirms what CADE said about the tanker being from Pittsburgh or Ohio. Since it's TAZZ, that's a KC-135R from the OH-ANG at Rickenbacker ANGB. I wonder if that Willow Grove unit has a tac freq out of the common range like the DC-ANG does at 127.275 or something around that?
Dave, you hit it just right...they do sound like a couple of young punks. Was that you tuned into my webcast while I had them on? I noticed someone sign off as soon as I went back to regular scan.
Come to think of it (took long enough!), there's a runway 24 at Patuxent River also.
Jack, yeah, it could be almost any type plane - either fighters low enough to not be breathing oxygen or tankers or almost any transport type.
1845: There is a pair of fighters working Bollen Range on «237.2»
1850: Fighter activity on «141.725» and it's the same guys working Bollen. Since that tac freq doesn't fit for MD/DC/VA/NJ-ANG units, I think we can safely label it as A-10s from the PA-ANG at Willow Grove.
1852: Evac 71474 calling Andrews on «141.5» - obviously a mistake. He then tries «141.55» and gets no reply so finally goes to «378.1» where he reports 30 minutes out, needs parking, has 4 Space A pax to offload, needs a Payloader and airstairs and transportation for the pax. He wants to do a quick turnaround and is inquiring about the upcoming ramp freeze.
1859: Fighters on Bollen «237.2» mention heading for Slate Run at 11,000 feet and over on their «141.725» freq they are talking about refueling.
1900: Fighter on Bollen calls BALKY range controller for count on BDUs used. I think he used callsign CADE for himself. If so, that confirms PA-ANG. «237.2»
1901: Yes, confirmed CADE 1 and 2 are the callsigns of the fighters at Bollen. He says rather than refueling, they are going to RTB because of a stuck BDU. «237.2»
1902: CADE wants BALKY to call Pittsburgh or Ohio or wherever the tanker is from to let him know they won't be refueling. I think that reference earlier to going to Slate Run was in reference to going to the Duke MOA for refueling before they decided to cancel it. At 1903, CADE signs off the freq. «237.2»
If that tanker was indeed from Pittsburgh, there will be a STEEL KC-135 flying around the area. He's all yours Dave.
1905: Navy 017 off Andrews «118.4»
1906: JOSA 488 to SAM Command on «141.55» home station C-21, tail #40076, arriving Andrews in 25 minutes, done with their mission upon landing, no pax or cargo to download, wants crew bus for 2 to meet them in 9 row where they'll park.
1907: CADE 1/2 with ZNY-North Mountain on «338.3» leaving 15,000 for 13,000. They are also still chatting on «141.725» I never hear the PA-ANG using channel references to be able to log them like we have the other units.
1909: CRAB 52 (C-130J MD-ANG Martin State) with Martin State Tower on «121.3» for landing...they're 6 miles northwest of the airfield at this time.
1911: CADE 1/2 descending to ?3,000? feet «338.3»
1912: UGLY flight of two (A-10 PA-ANG Willow Grove) now heading for the Bollen Range. Talking with BALKY on «237.2» Meanwhile, over on «141.725» one of the CADEs asks, "Is that our guys over there going to the range?"
1915: The CADEs don't know which of them has the hung BDU. All they know is that they asked how many impacted at the range and they have that number versus the number they knew they carried and thought they fired. «141.725»
NOTE: Remember, we had a couple of Willow Grove A-10s deploy into Martin State this afternoon using their travelling callsign - SANDY.
1920: Evac 71474 landing with Andrews Tower on «118.4»
1922: UGLY flight attacking targets at the Bollen Range. This might just be a flight of three A-10s, rather than two.
Unable to find a tac freq for the UGLY flight...have two scanners searching...one covering the 138-144 range and the other 138 extended to 149.
1935: Have some fighters on tac freq «143.025» Not sure yet if it's the UGLY flight.
1937: Have someone working HUNTRESS on «364.2» No ID heard yet.
1938: Fighters on «143.025» talking about landing on runway 24 visual. Runways at Willow Grove are 15/33. Hmmmm.
1940: The aircraft with HUNTRESS on «364.2» is REACH 111.
1941: Fighters on «143.025» telling Ebonics jokes (and they're not even funny)...sounds like just two of them though and the UGLY flight was three. Between that and the runway 24 mention, it doesn't appear to be the UGLY tac freq.
Have the 143.025 freq on the webcast for now. Lots of chat from these guys.
1949: Fighters on «143.025» still chatting - profanely - and are very loud and clear at this time.
1953: The «143.025» guys just mentioned calling Atlantic Aviation.
http://www.atlanticaviation.com/
1955: REACH 9017 to Dover Command Post on «349.4» reports 20 minutes out, A-2, no offload.
2009: Tanker interplane freq «139.875» active.
2037: Tanker interplane still busy with chat from time to time «139.875» (IDed as TEAM 45 and 46 from another source working up around Albany NY for refueling activity)
2042: DC KC-135 tanker about to land at Andrews. He's with LIBERATOR on squadron freq «351.2» reports A-1
2044: Army 053 landing Andrews «118.4»
2056: JOSA 611, after calling SAM Command several times, finally makes contact on «378.1» reports arriving at Andrews at 0215Z, A-1, is a C-21 with tail #40077, will be mission complete upon arriving, has 2 Duty Pax to offload - an A-4 plus 1, needs crew transportation to pick them up in 9 row.
2102: DC 02 (female) (KC-135 756th ARS Andrews) to LIBERATOR on «351.2» asking if the ramp freeze is getting ready to go into effect or is being lifted. Reply from ground not heard so don't know the answer.
Thanks Dave...that also confirms my statement of three UGLYs. It also confirms what CADE said about the tanker being from Pittsburgh or Ohio. Since it's TAZZ, that's a KC-135R from the OH-ANG at Rickenbacker ANGB. I wonder if that Willow Grove unit has a tac freq out of the common range like the DC-ANG does at 127.275 or something around that?
Dave, you hit it just right...they do sound like a couple of young punks. Was that you tuned into my webcast while I had them on? I noticed someone sign off as soon as I went back to regular scan.
Come to think of it (took long enough!), there's a runway 24 at Patuxent River also.
Jack, yeah, it could be almost any type plane - either fighters low enough to not be breathing oxygen or tankers or almost any transport type.
Last edited:
TinEar,
Ugly 1, 2, and 3 were refuelling up at the Duke with Taz 72 on 301.60. They finished up at about 1855 and exited the airspace, they mentioned going to R-5802 (Bollen). They told Taz 72 that a Cade flight was probably a few minutes out, I never heard them come in...now I know why, thanks a million! Ugly gave only the last 3 digits of each aircrafts tail number as follows: Ugly 1 (658), Ugly 2 (170), and Ugly 3 (981). I only had my PRO-2052 with the telescopic antenna that came with the scanner and I heard them on 338.30 with NY Center until they mentioned they were about 40 Miles from the range, not bad I think.
I tried to get them on the VHF Tac Freqs as well while they were up here, but didn't have any luck either. My 2052 does not go into AM mode on that Freq range, but if they would have popped up, I would have at least heard something, although not perfectly clear.
Yessir, definately from Ohio. Sluff 63 was about 6 minutes behind Taz 72 and transitioned through the airspace. Both are, of course, from Ohio.
I thought along those lines of the lower Tac Freq so I scanned a few times from 126.0 to 135.0 then from 135.0 up to 150.0. Unfortunately, I didn't get any hits though.
"I never hear the PA-ANG using channel references to be able to log them like we have the other units." - Ugly 1 sad "Push 17" and that was the 338.30 Freq.
Those two sound like a couple of punks...I heard the Atlantic Aviation Reference, Teterboro has a Runway 24 I believe. That's one of Atlantic Aviation's FBOs.
Yeah, I was listening to your webcast, that's a pretty nice setup you have there. Good Show!
I searched the scramble.nl database and the Serials Must Be: 78-0658, 79-0170, and 81-0981.
Dave
Ugly 1, 2, and 3 were refuelling up at the Duke with Taz 72 on 301.60. They finished up at about 1855 and exited the airspace, they mentioned going to R-5802 (Bollen). They told Taz 72 that a Cade flight was probably a few minutes out, I never heard them come in...now I know why, thanks a million! Ugly gave only the last 3 digits of each aircrafts tail number as follows: Ugly 1 (658), Ugly 2 (170), and Ugly 3 (981). I only had my PRO-2052 with the telescopic antenna that came with the scanner and I heard them on 338.30 with NY Center until they mentioned they were about 40 Miles from the range, not bad I think.
I tried to get them on the VHF Tac Freqs as well while they were up here, but didn't have any luck either. My 2052 does not go into AM mode on that Freq range, but if they would have popped up, I would have at least heard something, although not perfectly clear.
Yessir, definately from Ohio. Sluff 63 was about 6 minutes behind Taz 72 and transitioned through the airspace. Both are, of course, from Ohio.
I thought along those lines of the lower Tac Freq so I scanned a few times from 126.0 to 135.0 then from 135.0 up to 150.0. Unfortunately, I didn't get any hits though.
"I never hear the PA-ANG using channel references to be able to log them like we have the other units." - Ugly 1 sad "Push 17" and that was the 338.30 Freq.
Those two sound like a couple of punks...I heard the Atlantic Aviation Reference, Teterboro has a Runway 24 I believe. That's one of Atlantic Aviation's FBOs.
Yeah, I was listening to your webcast, that's a pretty nice setup you have there. Good Show!
I searched the scramble.nl database and the Serials Must Be: 78-0658, 79-0170, and 81-0981.
Dave
Last edited:
TinEar
Member
The Defense Department plans to accelerate retirement of key Air Force aircraft, including nearly half the B-52 bomber force and the full U-2 spy plane and F-117 stealth fighter fleets, in a bid to save $2.6 billion and boost spending for the services' prized F-22A fighter aircraft program.
http://www.military.com/features/0,15240,84991,00.html?ESRC=airforce-a.nl
From the same story......
In addition to these decrements, the Air Force plans to slash its fleet of C-21 jets from 76 to 38 aircraft. C-21s are used to ferry Pentagon executives, cargo and execute medical missions.
There goes half the traffic into Andrews.
2233: OPEC 49 (KC-10A, McGuire AFB NJ) with McGuire Command Post on «319.4» arriving at McGuire in 20 minutes, no writeups. Several minutes later he is given parking spot F-2.
http://www.military.com/features/0,15240,84991,00.html?ESRC=airforce-a.nl
From the same story......
In addition to these decrements, the Air Force plans to slash its fleet of C-21 jets from 76 to 38 aircraft. C-21s are used to ferry Pentagon executives, cargo and execute medical missions.
There goes half the traffic into Andrews.
2233: OPEC 49 (KC-10A, McGuire AFB NJ) with McGuire Command Post on «319.4» arriving at McGuire in 20 minutes, no writeups. Several minutes later he is given parking spot F-2.
Last edited:
TinEar
Member
Mid 40s temps and overcast with some earlier rain this morning has held MilAir flights to a minimum today. No fighters heard at all and just the usual transport activity.
Late in the 1000 hour had a PAT 988 call Davison Metro for a weather forecast on «139.4» He wanted it because his in-flight weather reports had not indicated clouds and rain for this area. Over the course of the morning have been off and on comms on the tanker interplane freq «139.875» No IDs heard - just chat. About 1140 they are talking about how bad the weather is at their base and one says he's just going to stay up until it clears up. He has 80,000 pounds of fuel so that won't be a problem. And about 1130 there was a KING 15 going into Andrews using «141.55» that said he was weather diverted. The weather diversions around the east coast are for low ceilings and ground fog. He wants 20,000 pounds of fuel when he lands. His tail # was 64-14853 which confirms him as a C-130. The KING callsign should make him from either Duke or Hurlburt Airfields in Florida.
About 1315 had a COBRA 40 with ZDC-Calvert on «281.4» coming into the area and heading for Andrews. He mentioned contacting Navy Ops at Andrews. A few minutes later he was cleared off Center and was heard with Andrews Ground on «275.8»
At 1326, there was an Army 10301 on «141.55» saying he was turning back to Andrews. He didn't mention the reason for this. Anyway, he had an R-3 on board and objected to parking on 10 row when he landed because that was too far away. Everyone knows the important guys get closer to the terminal. Ground relented and gave him 4 row and the pilot said he needed about 500 gallons of gas upon landing. Sorry pal, gas trucks don't go to 4 row. Well, where do I go for fuel? Fuel truck goes to 3 row. Good...I'll park on 3 row. Later at 1342 heard on «118.4» landing. The End.
1336: AERO 21 (F-16 NJ-ANG Atlantic City) with ZDC-Casanova on «282.2». Push 362.3. I set up on «362.3» and hear him mention something about GUARD DOG and the flight being AERO 21 and 22. I don't know who belongs to this freq.
1347: Have AERO 21 & 22 with HUNTRESS on «260.9» setting up the CAP with a "bullseye of Thurmont" according to flight leader. He's looking for TANKER 20. AERO 21 has a terrible transmitter that's has very weak modulation. 22 has a great signal. They also say the north end of the CAP is okay but the farther south they go, the worse it gets. He wants to know if they can set up at 19,000. This is kind of unusual since when the NJ-ANG takes the CAP, they use the COSMIC callsign rather than the normal squadron callsigns.
1354: AERO 21 again asking HUNTRESS about TANKER 20. «260.9»
1355: AERO 21 goes back to that «362.3» freq and calls Washington Center several times without getting a reply. I don't have that freq listed for Washington Center. anyway, he goes back to «260.9» to confirm the freq should be 362.3 where I guess he's told it is and then back to 362.3 he goes to call Center several more times without reply.
1357: AERO 22 tries calling Washington Center several times on «362.3» He has no better luck that 21 had. No reply.
1356: OMAHA 1 calling THOR on the HUNTRESS «260.9» freq.
1357-59: AERO 21 tries calling Washington Center on GUARD DOG freq «288.35» also with no reply. He goes back to «260.9» to say they were given the 362.3 freq but have no contact and does HUNTRESS have another one. I can't hear the ground station during this CAP so don't know what reply he was given. He then comes up and says push 247.7.
1400: VA-ANG F-16s on tac «141.875»
1401: AERO 21 calling Washington Center on «247.7» and doesn't seem to make contactwith Washington Center there either and is then given 296.7 to try.
1402: AERO 21 tries «296.7» for Washington Center...still no reply. So then it's push 362.3.
1402: AERO 21 on «362.3» with nothing again.
1403: AERO 21 now calling GUARD DOG on «362.3» He's apparently told to go to 288.35
1403: TANKER 20 comes up with HUNTRESS on «260.9»
1405: AERO 21 to GUARD DOG on «288.35» where he makes contact and asks permission to leave the CAP for aerial refueling with TANKER 20
1408: AERO 21 goes to ZDC-Hagerstown on «227.125» to setup refueling with TANKER 21. (He calls him 21 but earlier it was 20)
1409: AERO 21 using boom freq «320.6» for refueling.
These are not NJ-ANG fighters. They are F-15s and much of the terminology during freq changes was consistent with F-15s such as "prime" and "aux."
AERO 21's tail number is EG 8-0011
AERO 22's tail number is EG 00-8507
They ID to the tanker as being from the 60th Fighter Squadron. (I earlier thought I heard 16th but it's definitely 60th.)
The final word should be the EG on the tail which should make them from the 33rd Fighter Wing at Eglin AFB Florida.
1417: The AERO 21 F-15 is finishing up his refueling with TANKER 20 on boom freq «320.6»
1422: AERO 22 going in to refuel with TANKER 21 on «320.6»
1423: Have a couple of KC-135 tankers from the 756th at Andrews on squadron freq «351.2» They are DC51 who is 30 minutes out and A-2 and DC52 (I think) who is 15 minutes out and A-1.
1425: Have a pair of NJ-ANG F-16s on tac «138.875» (I hope their callsign isn't AERO)
1428: AERO 22 finishes refueling on «320.6»
We have three Washington Center freqs that were provided to the CAP fighters by HUNTRESS which were:
247.7...296.7...362.3
None of those three are listed for Washington Center and we're going to have to do some work to find out just what they might be.
1430: The NJ F-16s are heading down this way, obviously to the Pax River Range to do their work. This is a two ship flight. «138.875» Still no callsign heard from them.
1431: Have a BICEP 11 (F-16 NJ-ANG) working «138.125» And then it's..."BICEPs push 138.05" He did not give a V channel reference. They go to «138.05» Sounds like a flight of two.
1435: While on «138.05» BICEP flight leader says to push V-15 and they come up where expected on «138.425» When they were still on 138.05 they tried calling WARHAWK but got no reply.
1437: BICEP goes to «138.125» with SOF to say they couldn't make contact on 138.05 and does SOF have a backup. He then says, "BICEP push 138.3."
1438: BICEPs call KINGPIN (SOF call) and then WARHAWK on «138.3» and finally have contact.
1438: Meanwhile the AERO 21/22 CAP flight is still in place and doing their thing. «260.9»
1442: BICEP contacts range controller - GIANT HAND - with flight info, ordnance, type aircraft (two F16C+) and says they have 25 minutes of playtime. «138.3»
1443: VA-ANG tac «142.175» active
1457: Finally got a callsign from the NJ pair using tac «138.875» and, of course, it's AERO 21/22 - just the same as the AERO 21/22 working the CAP with HUNTRESS. I stress they are different flights. These guys are F-16s and the ones in the CAP are F-15s. What are the odds of this happening?
1459: BICEP 11 flight now with KINGPIN (SOF) on «138.3» They mention using freq 256.5 which is a Pax River freq.
1515: The BICEP flight on «138.3» is still up but having difficulty with their mission because of the weather...the AERO F-16 flight is still on «138.875» basically on a photo mission. The AERO F-15 flight is still in the CAP over Thurmont under direction of HUNTRESS on «260.9» They've been very, very quiet since they finished refueling shortly after coming on station.
1528: AERO 22 from the CAP is going to the tanker to refuel. «260.9» He makes the switch to boom freq «320.6» and reports nose cold to TANKER 20.
1529: BICEP 11 flight with Pax on «256.5» reports they're going to RTB and wants a Washington Center freq...they get 256.8
1530: BICEP 11 with ZDC-Cape Charles on «256.8» to start his trip home. reports direct Atlantic City. Push U-7
1530: It appears the AERO F-16 flight from Atlantic City has also headed for home.
1532: BICEP 11 with ZDC-Casino on «285.4» direct Atlantic City. They continue to use «138.3» for tac as they head for home. The wingman is sent to get the ATIS and do the SOF report.
1535: AERO 22 from the CAP is cleared onto the boom by TANKER 20. «320.6»
I wonder if this Eglin AFB CAP flight will have replacements from Eglin and if they're actually flying all the way up the coast or if they've deployed somewhere closer such as to Langley. This pair came aboard just before 1400 so they might be on station until about 1800 if they follow the normal shifts.
1537: BICEP push 6 as they say goodbye to the Center on «285.4» and so they report in to Atlantic City Approach on «327.125» as expected for final approach into the runway at Atlantic City.
Conued below...character limit...had to move that whole discussion of the AERO 22 fuel door problem down below also.
Late in the 1000 hour had a PAT 988 call Davison Metro for a weather forecast on «139.4» He wanted it because his in-flight weather reports had not indicated clouds and rain for this area. Over the course of the morning have been off and on comms on the tanker interplane freq «139.875» No IDs heard - just chat. About 1140 they are talking about how bad the weather is at their base and one says he's just going to stay up until it clears up. He has 80,000 pounds of fuel so that won't be a problem. And about 1130 there was a KING 15 going into Andrews using «141.55» that said he was weather diverted. The weather diversions around the east coast are for low ceilings and ground fog. He wants 20,000 pounds of fuel when he lands. His tail # was 64-14853 which confirms him as a C-130. The KING callsign should make him from either Duke or Hurlburt Airfields in Florida.
About 1315 had a COBRA 40 with ZDC-Calvert on «281.4» coming into the area and heading for Andrews. He mentioned contacting Navy Ops at Andrews. A few minutes later he was cleared off Center and was heard with Andrews Ground on «275.8»
At 1326, there was an Army 10301 on «141.55» saying he was turning back to Andrews. He didn't mention the reason for this. Anyway, he had an R-3 on board and objected to parking on 10 row when he landed because that was too far away. Everyone knows the important guys get closer to the terminal. Ground relented and gave him 4 row and the pilot said he needed about 500 gallons of gas upon landing. Sorry pal, gas trucks don't go to 4 row. Well, where do I go for fuel? Fuel truck goes to 3 row. Good...I'll park on 3 row. Later at 1342 heard on «118.4» landing. The End.
1336: AERO 21 (F-16 NJ-ANG Atlantic City) with ZDC-Casanova on «282.2». Push 362.3. I set up on «362.3» and hear him mention something about GUARD DOG and the flight being AERO 21 and 22. I don't know who belongs to this freq.
1347: Have AERO 21 & 22 with HUNTRESS on «260.9» setting up the CAP with a "bullseye of Thurmont" according to flight leader. He's looking for TANKER 20. AERO 21 has a terrible transmitter that's has very weak modulation. 22 has a great signal. They also say the north end of the CAP is okay but the farther south they go, the worse it gets. He wants to know if they can set up at 19,000. This is kind of unusual since when the NJ-ANG takes the CAP, they use the COSMIC callsign rather than the normal squadron callsigns.
1354: AERO 21 again asking HUNTRESS about TANKER 20. «260.9»
1355: AERO 21 goes back to that «362.3» freq and calls Washington Center several times without getting a reply. I don't have that freq listed for Washington Center. anyway, he goes back to «260.9» to confirm the freq should be 362.3 where I guess he's told it is and then back to 362.3 he goes to call Center several more times without reply.
1357: AERO 22 tries calling Washington Center several times on «362.3» He has no better luck that 21 had. No reply.
1356: OMAHA 1 calling THOR on the HUNTRESS «260.9» freq.
1357-59: AERO 21 tries calling Washington Center on GUARD DOG freq «288.35» also with no reply. He goes back to «260.9» to say they were given the 362.3 freq but have no contact and does HUNTRESS have another one. I can't hear the ground station during this CAP so don't know what reply he was given. He then comes up and says push 247.7.
1400: VA-ANG F-16s on tac «141.875»
1401: AERO 21 calling Washington Center on «247.7» and doesn't seem to make contactwith Washington Center there either and is then given 296.7 to try.
1402: AERO 21 tries «296.7» for Washington Center...still no reply. So then it's push 362.3.
1402: AERO 21 on «362.3» with nothing again.
1403: AERO 21 now calling GUARD DOG on «362.3» He's apparently told to go to 288.35
1403: TANKER 20 comes up with HUNTRESS on «260.9»
1405: AERO 21 to GUARD DOG on «288.35» where he makes contact and asks permission to leave the CAP for aerial refueling with TANKER 20
1408: AERO 21 goes to ZDC-Hagerstown on «227.125» to setup refueling with TANKER 21. (He calls him 21 but earlier it was 20)
1409: AERO 21 using boom freq «320.6» for refueling.
These are not NJ-ANG fighters. They are F-15s and much of the terminology during freq changes was consistent with F-15s such as "prime" and "aux."
AERO 21's tail number is EG 8-0011
AERO 22's tail number is EG 00-8507
They ID to the tanker as being from the 60th Fighter Squadron. (I earlier thought I heard 16th but it's definitely 60th.)
The final word should be the EG on the tail which should make them from the 33rd Fighter Wing at Eglin AFB Florida.
1417: The AERO 21 F-15 is finishing up his refueling with TANKER 20 on boom freq «320.6»
1422: AERO 22 going in to refuel with TANKER 21 on «320.6»
1423: Have a couple of KC-135 tankers from the 756th at Andrews on squadron freq «351.2» They are DC51 who is 30 minutes out and A-2 and DC52 (I think) who is 15 minutes out and A-1.
1425: Have a pair of NJ-ANG F-16s on tac «138.875» (I hope their callsign isn't AERO)
1428: AERO 22 finishes refueling on «320.6»
We have three Washington Center freqs that were provided to the CAP fighters by HUNTRESS which were:
247.7...296.7...362.3
None of those three are listed for Washington Center and we're going to have to do some work to find out just what they might be.
1430: The NJ F-16s are heading down this way, obviously to the Pax River Range to do their work. This is a two ship flight. «138.875» Still no callsign heard from them.
1431: Have a BICEP 11 (F-16 NJ-ANG) working «138.125» And then it's..."BICEPs push 138.05" He did not give a V channel reference. They go to «138.05» Sounds like a flight of two.
1435: While on «138.05» BICEP flight leader says to push V-15 and they come up where expected on «138.425» When they were still on 138.05 they tried calling WARHAWK but got no reply.
1437: BICEP goes to «138.125» with SOF to say they couldn't make contact on 138.05 and does SOF have a backup. He then says, "BICEP push 138.3."
1438: BICEPs call KINGPIN (SOF call) and then WARHAWK on «138.3» and finally have contact.
1438: Meanwhile the AERO 21/22 CAP flight is still in place and doing their thing. «260.9»
1442: BICEP contacts range controller - GIANT HAND - with flight info, ordnance, type aircraft (two F16C+) and says they have 25 minutes of playtime. «138.3»
1443: VA-ANG tac «142.175» active
1457: Finally got a callsign from the NJ pair using tac «138.875» and, of course, it's AERO 21/22 - just the same as the AERO 21/22 working the CAP with HUNTRESS. I stress they are different flights. These guys are F-16s and the ones in the CAP are F-15s. What are the odds of this happening?
1459: BICEP 11 flight now with KINGPIN (SOF) on «138.3» They mention using freq 256.5 which is a Pax River freq.
1515: The BICEP flight on «138.3» is still up but having difficulty with their mission because of the weather...the AERO F-16 flight is still on «138.875» basically on a photo mission. The AERO F-15 flight is still in the CAP over Thurmont under direction of HUNTRESS on «260.9» They've been very, very quiet since they finished refueling shortly after coming on station.
1528: AERO 22 from the CAP is going to the tanker to refuel. «260.9» He makes the switch to boom freq «320.6» and reports nose cold to TANKER 20.
1529: BICEP 11 flight with Pax on «256.5» reports they're going to RTB and wants a Washington Center freq...they get 256.8
1530: BICEP 11 with ZDC-Cape Charles on «256.8» to start his trip home. reports direct Atlantic City. Push U-7
1530: It appears the AERO F-16 flight from Atlantic City has also headed for home.
1532: BICEP 11 with ZDC-Casino on «285.4» direct Atlantic City. They continue to use «138.3» for tac as they head for home. The wingman is sent to get the ATIS and do the SOF report.
1535: AERO 22 from the CAP is cleared onto the boom by TANKER 20. «320.6»
I wonder if this Eglin AFB CAP flight will have replacements from Eglin and if they're actually flying all the way up the coast or if they've deployed somewhere closer such as to Langley. This pair came aboard just before 1400 so they might be on station until about 1800 if they follow the normal shifts.
1537: BICEP push 6 as they say goodbye to the Center on «285.4» and so they report in to Atlantic City Approach on «327.125» as expected for final approach into the runway at Atlantic City.
Conued below...character limit...had to move that whole discussion of the AERO 22 fuel door problem down below also.
Last edited:
freqhopping
Member
I just tuned into the CAP and heard that "Aero-22" lost the door to his refueling boom. 
I mapped the coordinates. The location is NW of Potomac, MD in the area of Deep Glenn Dr and S. Glen Rd.
I mapped the coordinates. The location is NW of Potomac, MD in the area of Deep Glenn Dr and S. Glen Rd.
Last edited:
TinEar
Member
Good job freqhopping on mapping where the door fell. Wonder if it did any damage?
1539: TANKER 20 reports he was showing no flow which confuses AERO 22 since he says his tanks are full. AERO 21 reminds him that they tanker shows "no flow" when his tanks are full. AERO 22 reported during the refueling that his refueling door blew off. He goes back to primary «260.9» to report his fact. AERO 21 then goes to boom freq to ask the tanker if that's true. 22 confirms it's true because he can see it missing. 21 asks the tanker if the boom sustained any damage. The tanker says he doesn't know because 22 just dropped down and took off after refueling. The tanker asks if 21 will come up to the tanker and take a look. He won't but asks the tanker for the coordinates of the dropped object. 22 jumps in and says he marked it as 3902N-077130W at 2038Z.
22 confirms both external tanks are feeding and the door switch is in the closed position. This conversation was taking place across both 260.9 and 320.6. 21 says he's going to go up to 22 and do a batttle damage assessment and then he'll go to the tanker to take a look. 21 and 22 head for each other so this can take place. AERO 21 reports it was a 12 inch by 6 inch by 2 inch deep piece of metal. 21 then goes back to the tanker to ask if he saw the door fly off. Tanker confirms he saw it but couldn't tell for sure if it hit the plane at all...he just saw it break off and head upward.
At 1547, the two fighters are together and 21 tells 22 to open and close the remaining portion of the door. 21 tells him he may have some issues but should be able to continue refueling and continue the mission. The tanker wants 21 to come to the tanker to make sure the boom is okay. 21 relents and says he'll go to the boom now to get gas. 21 tells HUNTRESS he's going to the tanker and wants the BRA for him. He gets it and sets off on his way. We'll soon know if the boom sustained any damage and if the mission can continue.
AERO 21 goes up to the tanker and ask for the tanker's description of how it happened and he proceeds to tell him. Anyway, AERO 21 reports that everything looks good on the boom and he begins moving up to make contact with it. This should confirm the mission can continue and if 22 has trouble when he needs to refuel, I imagine there are plenty of close by places he can land to refuel if necessary.
Oh-oh....no fuel flow happening between the tanker and the fighter. 21 is backing off and reconnecting to try again. Nope....tanker reports they weren't getting a good connection at all and that gas was spurting out of the fighter's recepticle. Not a good sign for the future of the mission. Apparently, the tanker sustained damage too.
They just made contact to try yet again. They are giving up...the tanker says his system checks good but he can't refuel the F-15...he's just going to have to make other arrangements. AERO 21 says his system checks good also and wants to know if he wants to try again. The tanker tells him he's not supposed to come back to him after receiving that problem according to regs. He can try the other aircraft which is what they're going to try but he cannot go back to the same aircraft after a failure like that. AERO 21 tells HUNTRESS about the problem and says they either need to get another tanker up there or he has 1 hour before he has to divert to Langley.
At 1603, AERO 21 checks with the tanker again to get the coordinates of where the metal door broke off and dropped. Tanker 20 gives it him which agrees with what is somewhere in the report above.
1605 TANKER 20 tells AERO 21 he rechecked the books and they agree that he can no longer try to refuel 21 after the delayed disconnect they experienced. He can take AERO 22 but not 21. He apologizes but that's what the book says. 21 then goes to HUNTRESS to see if they can get another tanker or should he go into Langley preferably when he runs out of fuel. HUNTRESS wants to know if 22 can refuel and 21 tells him he's currently getting on the boom and he'll let HUNTRESS know.
At 1607, AERO 22 makes contact with the boom and has a problem...he's going to back off and try again since it might have just been an operator problem...he backs away and then is cleared into the tanker a second time. 1609 and contact made again between TANKER 20 and AERO 22...we shall see.
At 1611, AERO 22 reports he's full...so at least that was successful. We'll have to see what HUNTRESS decides to do about a replacement tanker. 21 goes back yet again to check with tanker and tanker confirms what he said earlier -- he will not give 21 gas. He also says he'd be better to get another F-15 up there because even if they scrambled another tanker, he might still not be able to be refueled. He goes back to HUNTRESS to whine where HUNTRESS tells him to try again. 21 says the tanker has already told him three times NO.
1614: AERO 21 asks HUNTRESS if he's going to get someone up or another Eglin jet and wants to make sure the Langley weather is good when he has to recover there in about 45 minutes when he'll be out of fuel.
Have had Raven Ops talking to aircraft on the ground on «347.2» over the past 10 minutes or so which may indicate an A-10 flight getting ready to happen.
At 1616 AERO 21 tells 22 to make sure he's full of fuel before starting back to Eglin because there's bad weather there...he mentions the possibility of having to go back to Maxwell, Tindall, Robins or Pensacola. I guess this tells us these F-15s are coming to the CAP directly from Eglin and are not deployed closer.
1624: AERO 21 tells 22 that in 45 minutes he'll be leaving and that 22 will have the cap by himself for an hour and 15 minutes by himself and to make sure to top off with fuel before leaving for home at Eglin in case weather forces him to divert to another base. Doing the math, means this pair was scheduled to have the CAP until about 1820-1830 local. I guess it's decided that AERO 21 will go into Langley when he does leave.
1629: AERO 21 mentions in chat with HUNTRESS on «260.9» that the next Eglin flight won't be here by the time he has to leave. This at least confirms that the replacements will be from Eglin and not some other closer unit. I wonder, with the withdrawal of F-15s from Langley, if Eglin is going to be the prime CAP worker bees in the future.
1638: AERO 21 tells 22 that if for any reason he can't top off his gas tanks when it's time, he's to divert into Langley too. 22 acknowledges. «260.9»
1638: A-10s are up from Martin State and working with Raven Ops on «347.2»
Got to get out of here....END OF REPORT...for now.
1539: TANKER 20 reports he was showing no flow which confuses AERO 22 since he says his tanks are full. AERO 21 reminds him that they tanker shows "no flow" when his tanks are full. AERO 22 reported during the refueling that his refueling door blew off. He goes back to primary «260.9» to report his fact. AERO 21 then goes to boom freq to ask the tanker if that's true. 22 confirms it's true because he can see it missing. 21 asks the tanker if the boom sustained any damage. The tanker says he doesn't know because 22 just dropped down and took off after refueling. The tanker asks if 21 will come up to the tanker and take a look. He won't but asks the tanker for the coordinates of the dropped object. 22 jumps in and says he marked it as 3902N-077130W at 2038Z.
22 confirms both external tanks are feeding and the door switch is in the closed position. This conversation was taking place across both 260.9 and 320.6. 21 says he's going to go up to 22 and do a batttle damage assessment and then he'll go to the tanker to take a look. 21 and 22 head for each other so this can take place. AERO 21 reports it was a 12 inch by 6 inch by 2 inch deep piece of metal. 21 then goes back to the tanker to ask if he saw the door fly off. Tanker confirms he saw it but couldn't tell for sure if it hit the plane at all...he just saw it break off and head upward.
At 1547, the two fighters are together and 21 tells 22 to open and close the remaining portion of the door. 21 tells him he may have some issues but should be able to continue refueling and continue the mission. The tanker wants 21 to come to the tanker to make sure the boom is okay. 21 relents and says he'll go to the boom now to get gas. 21 tells HUNTRESS he's going to the tanker and wants the BRA for him. He gets it and sets off on his way. We'll soon know if the boom sustained any damage and if the mission can continue.
AERO 21 goes up to the tanker and ask for the tanker's description of how it happened and he proceeds to tell him. Anyway, AERO 21 reports that everything looks good on the boom and he begins moving up to make contact with it. This should confirm the mission can continue and if 22 has trouble when he needs to refuel, I imagine there are plenty of close by places he can land to refuel if necessary.
Oh-oh....no fuel flow happening between the tanker and the fighter. 21 is backing off and reconnecting to try again. Nope....tanker reports they weren't getting a good connection at all and that gas was spurting out of the fighter's recepticle. Not a good sign for the future of the mission. Apparently, the tanker sustained damage too.
They just made contact to try yet again. They are giving up...the tanker says his system checks good but he can't refuel the F-15...he's just going to have to make other arrangements. AERO 21 says his system checks good also and wants to know if he wants to try again. The tanker tells him he's not supposed to come back to him after receiving that problem according to regs. He can try the other aircraft which is what they're going to try but he cannot go back to the same aircraft after a failure like that. AERO 21 tells HUNTRESS about the problem and says they either need to get another tanker up there or he has 1 hour before he has to divert to Langley.
At 1603, AERO 21 checks with the tanker again to get the coordinates of where the metal door broke off and dropped. Tanker 20 gives it him which agrees with what is somewhere in the report above.
1605 TANKER 20 tells AERO 21 he rechecked the books and they agree that he can no longer try to refuel 21 after the delayed disconnect they experienced. He can take AERO 22 but not 21. He apologizes but that's what the book says. 21 then goes to HUNTRESS to see if they can get another tanker or should he go into Langley preferably when he runs out of fuel. HUNTRESS wants to know if 22 can refuel and 21 tells him he's currently getting on the boom and he'll let HUNTRESS know.
At 1607, AERO 22 makes contact with the boom and has a problem...he's going to back off and try again since it might have just been an operator problem...he backs away and then is cleared into the tanker a second time. 1609 and contact made again between TANKER 20 and AERO 22...we shall see.
At 1611, AERO 22 reports he's full...so at least that was successful. We'll have to see what HUNTRESS decides to do about a replacement tanker. 21 goes back yet again to check with tanker and tanker confirms what he said earlier -- he will not give 21 gas. He also says he'd be better to get another F-15 up there because even if they scrambled another tanker, he might still not be able to be refueled. He goes back to HUNTRESS to whine where HUNTRESS tells him to try again. 21 says the tanker has already told him three times NO.
1614: AERO 21 asks HUNTRESS if he's going to get someone up or another Eglin jet and wants to make sure the Langley weather is good when he has to recover there in about 45 minutes when he'll be out of fuel.
Have had Raven Ops talking to aircraft on the ground on «347.2» over the past 10 minutes or so which may indicate an A-10 flight getting ready to happen.
At 1616 AERO 21 tells 22 to make sure he's full of fuel before starting back to Eglin because there's bad weather there...he mentions the possibility of having to go back to Maxwell, Tindall, Robins or Pensacola. I guess this tells us these F-15s are coming to the CAP directly from Eglin and are not deployed closer.
1624: AERO 21 tells 22 that in 45 minutes he'll be leaving and that 22 will have the cap by himself for an hour and 15 minutes by himself and to make sure to top off with fuel before leaving for home at Eglin in case weather forces him to divert to another base. Doing the math, means this pair was scheduled to have the CAP until about 1820-1830 local. I guess it's decided that AERO 21 will go into Langley when he does leave.
1629: AERO 21 mentions in chat with HUNTRESS on «260.9» that the next Eglin flight won't be here by the time he has to leave. This at least confirms that the replacements will be from Eglin and not some other closer unit. I wonder, with the withdrawal of F-15s from Langley, if Eglin is going to be the prime CAP worker bees in the future.
1638: AERO 21 tells 22 that if for any reason he can't top off his gas tanks when it's time, he's to divert into Langley too. 22 acknowledges. «260.9»
1638: A-10s are up from Martin State and working with Raven Ops on «347.2»
Got to get out of here....END OF REPORT...for now.
Last edited:
Caught KING 15 C-130 as well for wx divert.Have that tail aircraft as a HC-130P 347th RQW.
Could be from Patrick AFB in Florida or maybe Moody AFB Georgia as well.
For those ZDC freqs the only one I have and hear on regularly is that 362.300 which is normally
a DC CAP freq.The others are new to me as well.
Good id on those AERO F-15's,caught a pp to Eglin 60th FS as well.
The Fighting Crows is their squad name.
http://www.globalsecurity.org/military/agency/usaf/60fs.htm
Mark
Could be from Patrick AFB in Florida or maybe Moody AFB Georgia as well.
For those ZDC freqs the only one I have and hear on regularly is that 362.300 which is normally
a DC CAP freq.The others are new to me as well.
Good id on those AERO F-15's,caught a pp to Eglin 60th FS as well.
The Fighting Crows is their squad name.
http://www.globalsecurity.org/military/agency/usaf/60fs.htm
Mark
TinEar
Member
Back after doing a quick written critique of a graduate student's term paper. (It was pretty damn good, although written from a mushy headed liberal perspective. Aren't they all?)
OKay, so AERO 21 heads for Langley at about 1715 after giving 22 a good old boy pep talk about doing what HUNTRESS says, make sure you're topped off before leaving the CAP, watch out for storms around the Carolinas, etc. In general, he talked to him like he was a little kid on the first day of school
At 1727, AERO 23/24 show up with HUNTRESS on «260.9» Then, at 1738, 23 and 24 head for TANKER 20. He tells them that he refueled his primary receiver - without mentioning who that might have been - and says he's low and can't give them as much as they may want but TANKER 21 would be along soon. AERO 22 pops in here and wants to make sure 20 has enough gas to top him off and 20 confirms he does.
By 1747, both replacements F-15s have been given enough gas to get them into CAP duty and 22 is going in for his share. TANKER 21 is on the way according to 20. Primary CAP freq is still «260.9» and boom freq is still «320.6» However, I never did find a chat freq for the first pair. I just heard 23/24 mention 8 AUX for which I think is their chat freq so perhaps I can find it. If Eglin is going to be the regulars for the CAP in the future, we need to find all their tac freqs the way we did with Langley.
1749: TANKER 20 wants to know how much fuel AERO 22 needs to top off and is told 4,000 which doesn't seem to be a problem. «320.6»
1752: AERO 23 is telling 22 that there are some pretty severe thunderstorms around the Carolinas that he'll have to go around on his way home. «260.9»
<Break....damn, that pizza was good>
1909: AERO 23 calls HUNTRESS on «260.9» to ask if they have the capability to call Andrews and ask them to answer a call on 378.1. If he really wanted to call on 378.1, he's made a mistake because a couple of minutes later he's heard calling on the V, rather than U, freq of «141.55» His modulation is extremely low on that freq which is why he may not be being answered.
1914: Tanker interplane freq «139.875» active with chat
1914: REACH 943 calling Dover Command Post on «349.4»
1915: AERO 23 to GUARD DOG on «288.35» to ask for a radio check.
1916: AERO 23 heard on «342.5» (Didn't run across the freq in time to hear who he was calling. I don't have this freq listed for anyone.) Apparently though, he got no reply here either.
1918: AERO 23/24 give fuel remainders...24 reports "tanks dry" - referring to his wing tanks. «260.9»
1921: REACH 943 to Dover CP on «349.4» to report arriving in 20 minutes, A-1, ID as a C-17, no pax, 4 pallets to offload, wants info on the upload. Will need 110,000 pounds of fuel and crew transportation.
1922: BOLAR 44 (C-5) reports airborne from Dover at 20 after the hour «349.4»
1924: REACH 943 having trouble with followup questions from Dover...one reply is that he'll land with 50K of fuel on board. «349.4» They eventually get it all straight.
1930: AERO 23 calls Andrews on «378.1» Gets no reply
1932: AERO 23/24 both give a PIREP...23 says he's in the weather over the whole CAP but it's a thin deck. «260.9»
1939: AERO 23 tells 24 to push 8 AUX «260.9» Wild scramble now to find their chat freq.
1940: Got it! First Eglin tac freq for the new list. Their 8 AUX is «369.15» They mention thinking about heading for the tanker soon. (I guess TANKER 21 had to come on station while I was away.) To change back to primary CAP freq, it's push 10 AUX.
1943: AERO 24 tells HUNTRESS he's heading for the tanker...states his weapons are safe. «260.9» 24 then tells 23 he'll be off the prime
1945: AERO 24 calls TANKER 21 to clear into the tanker...reports nose cold. TANKER 21 is a female boom op. «320.6»
1948: As AERO 24 pulls up to the tanker, the boom op is suddenly a male. (Change of operators? Sex change operation?) «320.6» At 1949, 24 makes reports contact with the boom and gas starts flowing. In chat, 24 tells the tanker his crew will be on station until about 9 local time. The tanker asks if they'll fly out of Andrews. 24 responds that they may in the future if they keep doing this activity but the decision is way above his pay grade. The tanker also asks why Langley isn't doing the CAP - too busy? 24 answers that they just needed something to do since they had no other mission. He adds that they did a lot of this stuff over New Orleans after Katrina. 24 disconnects after taking 12,000 pounds at 1954...breaking to the right. The best info often comes from unplanned chat - and most of the security lapses.
1955: AERO 24 reports to HUNTRESS that he's returning to the CAP «260.9»
1959: AERO 23 tells HUNTRESS he'll be off prime for a minute «260.9» and goes to TANKER 21 for a radio check on «320.6»
2003: AERO 23 is at the tanker for refueling «320.6» He asks the tanker to turn down the "director" lights. TANKER 21 agrees he can do that.
2006: AERO 23 is full after taking 12,800 pounds of fuel. «320.6»
2013: AERO 23 with Andrews Command Post on «378.1» asking for a phone patch to DNS 651-XXXX. Apparently, it didn't work because he said he'd try again later.
2018: AERO 23 back to Andrews for another phone patch. Andrews wanted him to go to a Victor freq (probably 141.55) but 23 said he's unable to do Victor.
2020: AERO 23, on «260.9» says to push 8 AUX and they go to tac «369.15» where 23 tells 24 how he can see the Pentagon in relation to the Andrews circle and the Reagan circle. Short and sweet and back to 10 AUX.
2032: AERO 23/24 both declare timber sweet on their DATALINK and 24 sees 23 in the net but 23 doesn't see 24. He's trying to figure out why. «260.9»
2040: AERO 23 to Andrews again on «378.1» for a phone patch...five calls, no reply.
2042: AERO 23 gets a reply...wants a phone patch to 571-213-XXXX. «378.1» (That 571 area code is in northern Virginia so he's not calling home.)
2043: AERO 23 tells 24 to stay in the northern part of the CAP and he'd orbit the south (no doubt so he's closer to Andrews for his phone patch) «260.9»
2044: AERO 23 tells Andrews he'll try again later. He also tells Andrews to check his radio because he's only 10 miles away and everyone else hears him except Andrews «378.1»
2052: TANKER 21 to HUNTRESS asking when his replacement is due on station. «260.9» I think he then said he shows 0215Z as the time he's due
2058: AERO 23/24 give fuel remainders...23 with 16.1 (16,100 pounds) and 24 with 14.5 (14,500 pounds) «260.9
Continued below if necessary...approaching character count limits
Thanks freqhopping.
From there in Loudon County you're right in the middle of the track they run so, yeah, they should be overhead your house from time to time during their run.
Yes, I have a map showing the Thurmont CAP. One of these days I'll figure out how to scan just that portion of the map and then get it turned right to reproduce on here. One of my computer guru friends might stop by here one day and I'll think about it and have them do it for me. The overall map is rather large but the part containing the CAP portion should fit on the scanner.
Jack, I can always hear the ground station on the 141.55 Command Post freq but only rarely on 378.1. I also hear the HUNTRESS controller very well when it's the one at Andrews no matter which freq they use.
OKay, so AERO 21 heads for Langley at about 1715 after giving 22 a good old boy pep talk about doing what HUNTRESS says, make sure you're topped off before leaving the CAP, watch out for storms around the Carolinas, etc. In general, he talked to him like he was a little kid on the first day of school
At 1727, AERO 23/24 show up with HUNTRESS on «260.9» Then, at 1738, 23 and 24 head for TANKER 20. He tells them that he refueled his primary receiver - without mentioning who that might have been - and says he's low and can't give them as much as they may want but TANKER 21 would be along soon. AERO 22 pops in here and wants to make sure 20 has enough gas to top him off and 20 confirms he does.
By 1747, both replacements F-15s have been given enough gas to get them into CAP duty and 22 is going in for his share. TANKER 21 is on the way according to 20. Primary CAP freq is still «260.9» and boom freq is still «320.6» However, I never did find a chat freq for the first pair. I just heard 23/24 mention 8 AUX for which I think is their chat freq so perhaps I can find it. If Eglin is going to be the regulars for the CAP in the future, we need to find all their tac freqs the way we did with Langley.
1749: TANKER 20 wants to know how much fuel AERO 22 needs to top off and is told 4,000 which doesn't seem to be a problem. «320.6»
1752: AERO 23 is telling 22 that there are some pretty severe thunderstorms around the Carolinas that he'll have to go around on his way home. «260.9»
<Break....damn, that pizza was good>
1909: AERO 23 calls HUNTRESS on «260.9» to ask if they have the capability to call Andrews and ask them to answer a call on 378.1. If he really wanted to call on 378.1, he's made a mistake because a couple of minutes later he's heard calling on the V, rather than U, freq of «141.55» His modulation is extremely low on that freq which is why he may not be being answered.
1914: Tanker interplane freq «139.875» active with chat
1914: REACH 943 calling Dover Command Post on «349.4»
1915: AERO 23 to GUARD DOG on «288.35» to ask for a radio check.
1916: AERO 23 heard on «342.5» (Didn't run across the freq in time to hear who he was calling. I don't have this freq listed for anyone.) Apparently though, he got no reply here either.
1918: AERO 23/24 give fuel remainders...24 reports "tanks dry" - referring to his wing tanks. «260.9»
1921: REACH 943 to Dover CP on «349.4» to report arriving in 20 minutes, A-1, ID as a C-17, no pax, 4 pallets to offload, wants info on the upload. Will need 110,000 pounds of fuel and crew transportation.
1922: BOLAR 44 (C-5) reports airborne from Dover at 20 after the hour «349.4»
1924: REACH 943 having trouble with followup questions from Dover...one reply is that he'll land with 50K of fuel on board. «349.4» They eventually get it all straight.
1930: AERO 23 calls Andrews on «378.1» Gets no reply
1932: AERO 23/24 both give a PIREP...23 says he's in the weather over the whole CAP but it's a thin deck. «260.9»
1939: AERO 23 tells 24 to push 8 AUX «260.9» Wild scramble now to find their chat freq.
1940: Got it! First Eglin tac freq for the new list. Their 8 AUX is «369.15» They mention thinking about heading for the tanker soon. (I guess TANKER 21 had to come on station while I was away.) To change back to primary CAP freq, it's push 10 AUX.
1943: AERO 24 tells HUNTRESS he's heading for the tanker...states his weapons are safe. «260.9» 24 then tells 23 he'll be off the prime
1945: AERO 24 calls TANKER 21 to clear into the tanker...reports nose cold. TANKER 21 is a female boom op. «320.6»
1948: As AERO 24 pulls up to the tanker, the boom op is suddenly a male. (Change of operators? Sex change operation?) «320.6» At 1949, 24 makes reports contact with the boom and gas starts flowing. In chat, 24 tells the tanker his crew will be on station until about 9 local time. The tanker asks if they'll fly out of Andrews. 24 responds that they may in the future if they keep doing this activity but the decision is way above his pay grade. The tanker also asks why Langley isn't doing the CAP - too busy? 24 answers that they just needed something to do since they had no other mission. He adds that they did a lot of this stuff over New Orleans after Katrina. 24 disconnects after taking 12,000 pounds at 1954...breaking to the right. The best info often comes from unplanned chat - and most of the security lapses.
1955: AERO 24 reports to HUNTRESS that he's returning to the CAP «260.9»
1959: AERO 23 tells HUNTRESS he'll be off prime for a minute «260.9» and goes to TANKER 21 for a radio check on «320.6»
2003: AERO 23 is at the tanker for refueling «320.6» He asks the tanker to turn down the "director" lights. TANKER 21 agrees he can do that.
2006: AERO 23 is full after taking 12,800 pounds of fuel. «320.6»
2013: AERO 23 with Andrews Command Post on «378.1» asking for a phone patch to DNS 651-XXXX. Apparently, it didn't work because he said he'd try again later.
2018: AERO 23 back to Andrews for another phone patch. Andrews wanted him to go to a Victor freq (probably 141.55) but 23 said he's unable to do Victor.
2020: AERO 23, on «260.9» says to push 8 AUX and they go to tac «369.15» where 23 tells 24 how he can see the Pentagon in relation to the Andrews circle and the Reagan circle. Short and sweet and back to 10 AUX.
2032: AERO 23/24 both declare timber sweet on their DATALINK and 24 sees 23 in the net but 23 doesn't see 24. He's trying to figure out why. «260.9»
2040: AERO 23 to Andrews again on «378.1» for a phone patch...five calls, no reply.
2042: AERO 23 gets a reply...wants a phone patch to 571-213-XXXX. «378.1» (That 571 area code is in northern Virginia so he's not calling home.)
2043: AERO 23 tells 24 to stay in the northern part of the CAP and he'd orbit the south (no doubt so he's closer to Andrews for his phone patch) «260.9»
2044: AERO 23 tells Andrews he'll try again later. He also tells Andrews to check his radio because he's only 10 miles away and everyone else hears him except Andrews «378.1»
2052: TANKER 21 to HUNTRESS asking when his replacement is due on station. «260.9» I think he then said he shows 0215Z as the time he's due
2058: AERO 23/24 give fuel remainders...23 with 16.1 (16,100 pounds) and 24 with 14.5 (14,500 pounds) «260.9
Continued below if necessary...approaching character count limits
Thanks freqhopping.
From there in Loudon County you're right in the middle of the track they run so, yeah, they should be overhead your house from time to time during their run.
Yes, I have a map showing the Thurmont CAP. One of these days I'll figure out how to scan just that portion of the map and then get it turned right to reproduce on here. One of my computer guru friends might stop by here one day and I'll think about it and have them do it for me. The overall map is rather large but the part containing the CAP portion should fit on the scanner.
Jack, I can always hear the ground station on the 141.55 Command Post freq but only rarely on 378.1. I also hear the HUNTRESS controller very well when it's the one at Andrews no matter which freq they use.
Last edited:
freqhopping
Member
I've got CROW-21 currently on 322.45 (ZDC Sector 36 Raleigh) at around 40,000ft. He switched over from 354.1 (ZDC Sector 38 - "Tar River")
I have CROW as an Eglin F-15 callsign.
He is fading out. It sounded like he said something about direct to Atlanta.
At 2014 AERO-23 must by right above me, because I can hear him very loud and clear with just the rubber ducky on my Icom R10.
TinEar, was it you that mentioned having a map showing the track? I'd like to see it.
There are so many planes flying around here it's hard to know what's what when I stick my head out the window to listen. But just now (2024) I was able to hear what sounded more like a fighter than commericial, that and I couldn't see it due to cloud cover. I can usually see everything in and out of Dulles or inbound to DCA unless the cloud cover is really low.
Had some quick hits on 344.6 (USAF WX) and 386.8 (Andrews Navy Dispatch). Finally around 2100 some real comms on 344.6. No callsign heard, asking for 0230Z weather reports for NXX Willow Grove and NRI McGuire.
At 2126 I had some quick hits on 377.2 (ZDC Sector 52 - "Tech"). Reports being at 40,000ft.
Then at 2129, it is AERO-25. He would like to descend to 23,000 when at about 40 miles out so he can enter the CAP at 23,000.
2136- They push from 377.2 to 351.9 (ZDC Sector 32 - "Gordonsville") and then hear AERO-24 checking out and switching to 284.7 (ZDC Sector 60 - "Montebello")
I have CROW as an Eglin F-15 callsign.
He is fading out. It sounded like he said something about direct to Atlanta.
At 2014 AERO-23 must by right above me, because I can hear him very loud and clear with just the rubber ducky on my Icom R10.
TinEar, was it you that mentioned having a map showing the track? I'd like to see it.
There are so many planes flying around here it's hard to know what's what when I stick my head out the window to listen. But just now (2024) I was able to hear what sounded more like a fighter than commericial, that and I couldn't see it due to cloud cover. I can usually see everything in and out of Dulles or inbound to DCA unless the cloud cover is really low.
Had some quick hits on 344.6 (USAF WX) and 386.8 (Andrews Navy Dispatch). Finally around 2100 some real comms on 344.6. No callsign heard, asking for 0230Z weather reports for NXX Willow Grove and NRI McGuire.
At 2126 I had some quick hits on 377.2 (ZDC Sector 52 - "Tech"). Reports being at 40,000ft.
Then at 2129, it is AERO-25. He would like to descend to 23,000 when at about 40 miles out so he can enter the CAP at 23,000.
2136- They push from 377.2 to 351.9 (ZDC Sector 32 - "Gordonsville") and then hear AERO-24 checking out and switching to 284.7 (ZDC Sector 60 - "Montebello")
Last edited:
TinEar
Member
2109: AERO 25/26 are on the way to the CAP and are about 45 minutes out according to 24. 23 suggests that 24 go to the tanker and get filled «260.9»
2110: AERO 24 switches to «320.6», the boom freq and makes contact with TANKER 21. 21 tells him to come on in. 24 says he'll need about 8K.
2114: AERO 24 is given permission to contact the boom...a few seconds later reports contact.. «320.6» 21 asks 24 if he knows how much fuel 25/26 will need when they get here. 24 doesn't know but reports they'll be here in about 40 minutes.
Ka-ching!!!! TANKER 21 asks AERO 24 if they'll be here all weekend and 24 replies at least until Sunday night...also that they'll be here next weekend and maybe the weekend after that.
2117: AERO 24 disconnects...he took 9,000 pounds. «320.6»
2118: AERO 24 returning to CAP «260.9»
2119: TANKER 21 asking HUNTRESS if he thinks they will have to give any gas to 25 and 26 when they get here.
2120: AERO 23 with TANKER 21...3 miles off his tail, nose cold...going to topoff also. «320.6»
2123: TANKER 21 clears AERO 23 to contact the boom «320.6»...38 seconds later they announce contact.
This is a long shift for these pilots from Eglin. The round trip has to be about 4 hours plus 4 hours on station. That's a long time to be strapped in and cooped up in one of those tiny cockpits
2128: AERO 23 off the boom...he took 10,000 pounds. TANKER 21 wishes him a good flight home. «320.6»
2030: TANKER 21 with HUNTRESS on «260.9» and it's the female speaking from 21 again. First we've heard her since they came on station.
2131: AERO 25 and 26 on the AUX freq chatting «369.15» They are weak and still distant but that'll change soon.
2132: TANKER 22 checking in with HUNTRESS on «260.9»
2133: 23 and 24 go to «369.15» about changing to Andrews for that phone patch. He wants to find out what happened to the earlier AERO 21 that had to go to Langley. AERO 23 and 25 then chat on the 8 AUX freq.
2133: TANKER 21 goes to GUARD DOG on «135.525» and ZDC-Swann «134.5» for clearances back home. He's getting clearances as far as Boston so he might just be from Pease AFB NH.
2136: AERO 25 clears through ZDC-Gordonsville on «351.9» and then to 10 AUX on «260.9» where he checks his flight in with HUNTRESS.
2137: AERO 25 with ZDC-Montebello on «284.7» descending to CAP altitude. Passing 27 for 26(000)...then cleared to 25(000), heading 054....couple minutes later cleared down to 23,000
2143: AERO 23/24 with PIREP on 8 AUX 369.15 and immediately back to 10 AUX
2145: AERO 25 with GUARD DOG on «288.35» for altitude block assignment
2147: AERO 25 says they'll stay in the south until the TANKER 22 arrives. «260.9»
2150: AERO 25 asks 23 if he's BFC (I'm not going to spell that one out). 23 replies, "Sometimes." «260.9»
2151: AERO 26 gets his Mode 3 assignment from GUARD DOG on «288.35»
2153: AERO 25 and 26 do an Alpha check of their DATALINK...both show the same BRA which indicates they're both timber sweet.
2154: ZDC-Swann «134.5/360.7» advises AERO flight that TANKER 22 is entering the CAP. He also asks TANKER 22 for his origination and is given BGR which is Bangor Maine, making him a KC-135R.
2156: AERO 25 calling TANKER 23...then corrects it to TANKER 22...no reply «320.6»
2157: TANKER 22 is given the boom freq assignment of 320.6 while on «260.9»
2157: TANKER 22 going to flight level 240 for his refueling activity. «260.9»
Man, there are AEROs and TANKERs all over the place...with HUNTRESS, boom freqs, GUARD DOG, chat channel, ZDC freqs.
2159: TANKER 22 reports to GUARD DOG that he's in the CAP at this time at altitude block 22-24000 «135.525»
Continued below....maybe.
2110: AERO 24 switches to «320.6», the boom freq and makes contact with TANKER 21. 21 tells him to come on in. 24 says he'll need about 8K.
2114: AERO 24 is given permission to contact the boom...a few seconds later reports contact.. «320.6» 21 asks 24 if he knows how much fuel 25/26 will need when they get here. 24 doesn't know but reports they'll be here in about 40 minutes.
Ka-ching!!!! TANKER 21 asks AERO 24 if they'll be here all weekend and 24 replies at least until Sunday night...also that they'll be here next weekend and maybe the weekend after that.
2117: AERO 24 disconnects...he took 9,000 pounds. «320.6»
2118: AERO 24 returning to CAP «260.9»
2119: TANKER 21 asking HUNTRESS if he thinks they will have to give any gas to 25 and 26 when they get here.
2120: AERO 23 with TANKER 21...3 miles off his tail, nose cold...going to topoff also. «320.6»
2123: TANKER 21 clears AERO 23 to contact the boom «320.6»...38 seconds later they announce contact.
This is a long shift for these pilots from Eglin. The round trip has to be about 4 hours plus 4 hours on station. That's a long time to be strapped in and cooped up in one of those tiny cockpits
2128: AERO 23 off the boom...he took 10,000 pounds. TANKER 21 wishes him a good flight home. «320.6»
2030: TANKER 21 with HUNTRESS on «260.9» and it's the female speaking from 21 again. First we've heard her since they came on station.
2131: AERO 25 and 26 on the AUX freq chatting «369.15» They are weak and still distant but that'll change soon.
2132: TANKER 22 checking in with HUNTRESS on «260.9»
2133: 23 and 24 go to «369.15» about changing to Andrews for that phone patch. He wants to find out what happened to the earlier AERO 21 that had to go to Langley. AERO 23 and 25 then chat on the 8 AUX freq.
2133: TANKER 21 goes to GUARD DOG on «135.525» and ZDC-Swann «134.5» for clearances back home. He's getting clearances as far as Boston so he might just be from Pease AFB NH.
2136: AERO 25 clears through ZDC-Gordonsville on «351.9» and then to 10 AUX on «260.9» where he checks his flight in with HUNTRESS.
2137: AERO 25 with ZDC-Montebello on «284.7» descending to CAP altitude. Passing 27 for 26(000)...then cleared to 25(000), heading 054....couple minutes later cleared down to 23,000
2143: AERO 23/24 with PIREP on 8 AUX 369.15 and immediately back to 10 AUX
2145: AERO 25 with GUARD DOG on «288.35» for altitude block assignment
2147: AERO 25 says they'll stay in the south until the TANKER 22 arrives. «260.9»
2150: AERO 25 asks 23 if he's BFC (I'm not going to spell that one out). 23 replies, "Sometimes." «260.9»
2151: AERO 26 gets his Mode 3 assignment from GUARD DOG on «288.35»
2153: AERO 25 and 26 do an Alpha check of their DATALINK...both show the same BRA which indicates they're both timber sweet.
2154: ZDC-Swann «134.5/360.7» advises AERO flight that TANKER 22 is entering the CAP. He also asks TANKER 22 for his origination and is given BGR which is Bangor Maine, making him a KC-135R.
2156: AERO 25 calling TANKER 23...then corrects it to TANKER 22...no reply «320.6»
2157: TANKER 22 is given the boom freq assignment of 320.6 while on «260.9»
2157: TANKER 22 going to flight level 240 for his refueling activity. «260.9»
Man, there are AEROs and TANKERs all over the place...with HUNTRESS, boom freqs, GUARD DOG, chat channel, ZDC freqs.
2159: TANKER 22 reports to GUARD DOG that he's in the CAP at this time at altitude block 22-24000 «135.525»
Continued below....maybe.
Last edited:
ka3jjz
Wiki Admin Emeritus
Jack it sounds like you might have an overloading problem; intermod is one big symptom. Do you know what it is that is causing you grief? A pager, taxi system, FM station, ect? There are a couple of folks on the VHF UHF Military Monitoring wiki that sells filters for such things. Par Electronics is among the best known but there are others. It might be worth investigating.
I live in the same region as TinEar (in fact, if I am any judge, he's only right across town from me). I' limited to indoor antennas, but I can hear a/c calling into 141.55 and 378.1 no problem. I'll bet Tin can indeed hear the replies. 73s Mike
I live in the same region as TinEar (in fact, if I am any judge, he's only right across town from me). I' limited to indoor antennas, but I can hear a/c calling into 141.55 and 378.1 no problem. I'll bet Tin can indeed hear the replies. 73s Mike
Mike,
The intermod is coming from pagers on 152 or 153 mhz.I have a filter from par electronics it works real good but I think I am just too close to alot of towers (TV Hill 10 miles ) and others ...plus I am using a Log periodic directional antenna so that doesn't help any.I am seriously thinking about bagging the LPD and possibly putting up a discone again.
Jack
The intermod is coming from pagers on 152 or 153 mhz.I have a filter from par electronics it works real good but I think I am just too close to alot of towers (TV Hill 10 miles ) and others ...plus I am using a Log periodic directional antenna so that doesn't help any.I am seriously thinking about bagging the LPD and possibly putting up a discone again.
Jack
TinEar
Member
Jack, I don't get any intermod on the 141.55 freq as long as I use my BC785 to copy it. When I try my PRO-2042, it gets wiped out by intermod on the VHF freqs which is why I only use that radio for UHF.
2202: AERO 25 and TANKER 22 settle their altitudes for refueling and 25 tells 22 that he's now the commander and that 23 is going home. «260.9» 22 is going to be at FL240 and will try to get down to FL230 when they refuel. 25 assigns 26 to FL230 so he can be in place for refueling soon.
2204: AERO 23 says to HUNTRESS he doesn't need fuel as long as 25 and 26 don't take too long refueling. He explains that they must leave the CAP within 15 minutes to be able to leave without refueling first. «260.9»
2205: AERO 23/24 go to 8 AUX to check fuel remainders. 24 says his speed is about 275 and has 16,600 pounds left in his tanks. «369.15»
2207: AERO 25 and TANKER 22 make contact on boom freq «320.6» for refuleing and 22 clears him in to contact the boom. Meanwhile, back on «260.9» 23 reminds 25 to hurry up with that refueling because they have to scoot because of the gas remainders.
2213: AERO 25 tells 23 they're about done topping off so 23 says he's RTB «260.9»
2214: 25 tells the tanker he's got enough for now and 22 reports disconnect. 25 says he'll get more after 26 has refueled. 25 going down to 21,000 «320.6»
2215: AERO 23 tells HUNTRESS he's RTBing and switches to 8 AUX «260.9»
2215: An AERO 21 suddenly appears with HUNTRESS and asks the whereabouts of 23. Don't know if that's a mistake or could 21 possibly have come back from his earlier trip to Langley when he couldn't refuel?
2217: AERO 23 and 24 give fuel remainders over on 8 AUX...23 has 16.6 remaining and 24 has 15.3. «369.15»
NOTE: All thes Eglin AFB F-15s have used common frequency designators - unlike the HARASS bunch from Langley. Today, they've all used 8 AUX for chat freq 369.15 and 10 AUX for CAP primary 260.9
2220: AERO 26 finishes refueling and disconnects from the boom and heads down to 22,000. «320.6»
2220: AERO 26 reports back to the CAP «260.9»
2222: AERO 26 reports timber sour. «260.9» 25 asks HUNTRESS for the status of the net.
2223: AERO 23 with ZDC-Montebello on «284.7» at FL230 as his flight heads south.
2228: AERO 25 and 26 both reporting timber sour now. 25 also gives a PIREP indicating they're socked in and operating IFC at this time with negative icing. «260.9»
2230: Very weak chat from AERO 23/24 on «369.15» This will no doubt be the last I hear from them.
2233: Both AEROs still reporting timber sour. I wonder if they are having the same problem the HARASS flights always have. They are working Zulu time and when the date rolls over, they always seem to lose the net on their DATALINK. This flight is no exception. «260.9»
2243: AERO 25/26 tell HUNTRESS both are timber sour...still. «260.9»
2246: The AEROs go to 8 AUX «369.15» to suggest a possible fix...a new time hack in case they are more than six seconds apart. They then go back to HUNTRESS on «260.9» to suggest this brilliant strategy. (Wanna take bets?)
2254: AERO 25/26 back to 8 AUX to discuss the problem with the net. «369.15» Yet another suggestion for a fix. They report wx good in the south part of the CAP so 25 tells 26 if he's having trouble bouncing around up in the north, he can come down to the south to take a break. (Bet you never thought of that problem, huh?) Back to 10 AUX they go.
2258: Back to 8 AUX for more chat for reasons why their last suggestion won't work. «369.15» Back to 10 AUX
2310: AERO 25/26 back to 8 AUX for more chat about settings as they continue to attempt fixes for the DATALINK. «369.15» They also mention that night flying all counts as instrument flight time in the Air Force. How nice. Back to 10 AUX they go.
2315: AERO 25 tells HUNTRESS the cloud decks are starting to break up at this time...he also tells him that his DATALINK is timber sweet but that he only sees himself in the net. (Well, how could it be timber sweet under those conditions? If he can't also see his wingman and the tanker and the bullseye it sure ain't sweet.) «260.9»
2331: 25/26 back to 8 AUX with more setting changes for the DATALINK. 25 mentions this is the last time they're going to change the settings. «369.15» Back to 10 AUX with HUNTRESS on «260.9»
2350: AERO 25 has both himself and 26 in the net but 26 only has himself showing. 25 wants BRA to the tanker. AERO 25 heading for TANKER 22 «260.9» (Is TANKER 22 still awake? Did he take a go-pill?)
2353: AERO 25 in half mile trail with the tanker «320.6» 22 clears him in.
0001: AERO 25 gets the "no flow" shout from TANKER 22 indicating he's full. 25 breaks contact with the boom and heads back to the CAP. «320.6»
And that's where I'll leave it for the night. Next change should be around 0115.
END OF REPORT.
2202: AERO 25 and TANKER 22 settle their altitudes for refueling and 25 tells 22 that he's now the commander and that 23 is going home. «260.9» 22 is going to be at FL240 and will try to get down to FL230 when they refuel. 25 assigns 26 to FL230 so he can be in place for refueling soon.
2204: AERO 23 says to HUNTRESS he doesn't need fuel as long as 25 and 26 don't take too long refueling. He explains that they must leave the CAP within 15 minutes to be able to leave without refueling first. «260.9»
2205: AERO 23/24 go to 8 AUX to check fuel remainders. 24 says his speed is about 275 and has 16,600 pounds left in his tanks. «369.15»
2207: AERO 25 and TANKER 22 make contact on boom freq «320.6» for refuleing and 22 clears him in to contact the boom. Meanwhile, back on «260.9» 23 reminds 25 to hurry up with that refueling because they have to scoot because of the gas remainders.
2213: AERO 25 tells 23 they're about done topping off so 23 says he's RTB «260.9»
2214: 25 tells the tanker he's got enough for now and 22 reports disconnect. 25 says he'll get more after 26 has refueled. 25 going down to 21,000 «320.6»
2215: AERO 23 tells HUNTRESS he's RTBing and switches to 8 AUX «260.9»
2215: An AERO 21 suddenly appears with HUNTRESS and asks the whereabouts of 23. Don't know if that's a mistake or could 21 possibly have come back from his earlier trip to Langley when he couldn't refuel?
2217: AERO 23 and 24 give fuel remainders over on 8 AUX...23 has 16.6 remaining and 24 has 15.3. «369.15»
NOTE: All thes Eglin AFB F-15s have used common frequency designators - unlike the HARASS bunch from Langley. Today, they've all used 8 AUX for chat freq 369.15 and 10 AUX for CAP primary 260.9
2220: AERO 26 finishes refueling and disconnects from the boom and heads down to 22,000. «320.6»
2220: AERO 26 reports back to the CAP «260.9»
2222: AERO 26 reports timber sour. «260.9» 25 asks HUNTRESS for the status of the net.
2223: AERO 23 with ZDC-Montebello on «284.7» at FL230 as his flight heads south.
2228: AERO 25 and 26 both reporting timber sour now. 25 also gives a PIREP indicating they're socked in and operating IFC at this time with negative icing. «260.9»
2230: Very weak chat from AERO 23/24 on «369.15» This will no doubt be the last I hear from them.
2233: Both AEROs still reporting timber sour. I wonder if they are having the same problem the HARASS flights always have. They are working Zulu time and when the date rolls over, they always seem to lose the net on their DATALINK. This flight is no exception. «260.9»
2243: AERO 25/26 tell HUNTRESS both are timber sour...still. «260.9»
2246: The AEROs go to 8 AUX «369.15» to suggest a possible fix...a new time hack in case they are more than six seconds apart. They then go back to HUNTRESS on «260.9» to suggest this brilliant strategy. (Wanna take bets?)
2254: AERO 25/26 back to 8 AUX to discuss the problem with the net. «369.15» Yet another suggestion for a fix. They report wx good in the south part of the CAP so 25 tells 26 if he's having trouble bouncing around up in the north, he can come down to the south to take a break. (Bet you never thought of that problem, huh?) Back to 10 AUX they go.
2258: Back to 8 AUX for more chat for reasons why their last suggestion won't work. «369.15» Back to 10 AUX
2310: AERO 25/26 back to 8 AUX for more chat about settings as they continue to attempt fixes for the DATALINK. «369.15» They also mention that night flying all counts as instrument flight time in the Air Force. How nice. Back to 10 AUX they go.
2315: AERO 25 tells HUNTRESS the cloud decks are starting to break up at this time...he also tells him that his DATALINK is timber sweet but that he only sees himself in the net. (Well, how could it be timber sweet under those conditions? If he can't also see his wingman and the tanker and the bullseye it sure ain't sweet.) «260.9»
2331: 25/26 back to 8 AUX with more setting changes for the DATALINK. 25 mentions this is the last time they're going to change the settings. «369.15» Back to 10 AUX with HUNTRESS on «260.9»
2350: AERO 25 has both himself and 26 in the net but 26 only has himself showing. 25 wants BRA to the tanker. AERO 25 heading for TANKER 22 «260.9» (Is TANKER 22 still awake? Did he take a go-pill?)
2353: AERO 25 in half mile trail with the tanker «320.6» 22 clears him in.
0001: AERO 25 gets the "no flow" shout from TANKER 22 indicating he's full. 25 breaks contact with the boom and heads back to the CAP. «320.6»
And that's where I'll leave it for the night. Next change should be around 0115.
END OF REPORT.
Last edited:
TIN I still can't find a A/A freq for these AERO guys! Thought I heard a hit around 226-227 MHZ range but nothing else heard.
Will try VHF search just in case..
Mark
Will try VHF search just in case..
Mark
TinEar
Member
Mark, I logged the A/A chat freq in bold type a couple of hours ago when I found it. It's 369.15 and being called 8 AUX. See the log at 1940 (and about 40 entries after that time where I logged it....lol.)
Alan
Alan
Last edited:
DPD1
Member
- Joined
- Jul 24, 2005
- Messages
- 1,994
JackTV said:
Try taking the antenna down, take it apart, and polish the whole thing... Especially any points where metal parts need to make electrical contact. Then use an electrical corrosion inhibitor between any two parts that need to make electrical contact... There's stuff called Ox-Gard or Noalox, that you can get at home stores. You just smear a little of that stuff on any contact point before you put it together and leave it on.
Corrosion building up between contact points is often what starts the intermod. Can't guarantee that will fix it, but it might.
Dave
http://www.DPDProductions.com
- Custom Scanner, MURS, GMRS, & Ham Antennas -
- Status
