USCG Station Brunswick Using NET Frequency

I'm in the Brunswick area this morning hearing the Coast Guard Station using NET 118. I'm posting mobile, so I'll make a more detailed post later.

Mac McCormick III
KF4LMT

Sent from my Verizon Wireless BlackBerry

Military Monitoring Recap; August 2009

Hunter AAF
124.975 - Tower
279.575 - Tower
285.425 - Tower
121.800 - Ground
291.675 - Ground
126.200 - Base Ops
51.050 - Helicopter Common
309.000 - PMSV
406.1625 - Tower/Base Ops
406.7625 - POL
415.1625 - Trans Alert
67.975 - 1-3 AVN "VIPER OPS"
54.600 - 2-3 AVN "KNIGHTHAKW OPS"
51.375 - 3-17 CAV "LIGHTHORSE OPS"
245.175 - 3-17 CAV air-to-air
49.700 - 4-3 AVN "BRAWLER OPS"
30.300 - 4-3 AVN air-to-air
77.100 - 3rd AVN Bde; used by several units
77.725 - 224 MI Bn "SUNNY OPS"
345.000 - USCG Air Station Savanah Ops
157.175 - Marine VHF Ch. 83, Savannah Air MX Control
323.125 - Hunter AAF ATIS
127.525 - Hunter AAF ATIS (New)

ARMY 25287 (AH-64D, 1-3 AVN)
ARMY 25293 (AH-64D, 1-3 AVN)
ARMY 25295 (AH-64D, 1-3 AVN)
ARMY 25298 (AH-64D, 1-3 AVN)
ARMY 25300 (AH-64D, 1-3 AVN)
ARMY 25305 (AH-64D, 1-3 AVN)
ARMY 25330 (AH-64D, 1-3 AVN)
ARMY 35354 (AH-64D, 1-3 AVN)
ARMY 35359 (AH-64D, 1-3 AVN)
ARMY 35360 (AH-64D, 1-3 AVN)
ARMY 35377 (AH-64D, 1-3 AVN)
ARMY 35415 (AH-64D, 1-3 AVN)
ARMY 26555 (UH-60L, A/2-3 AVN)
ARMY 26556 (UH-60L, A/2-3 AVN)
ARMY 26558 (UH-60L, A/2-3 AVN)
ARMY 26594 (UH-60L, A/2-3 AVN)
ARMY 26596 (UH-60L, A/2-3 AVN)
ARMY 26795 (UH-60L, A/2-3 AVN)
RIVER ## (CH-47D, B/2-3 AVN)
ARMY 23938 (UH-60A, C/2-3 AVN)
ARMY 26501 (UH-60L, 4-3 AVN)
ARMY 26510 (UH-60L, 4-3 AVN)
ARMY 26513 (UH-60L, 4-3 AVN)
ARMY 26525 (UH-60L, 4-3 AVN)
ARMY 26542 (UH-60L, 4-3 AVN)
ARMY 26546 (UH-60L, 4-3 AVN)
ARMY 26585 (UH-60L, 4-3 AVN)
ARMY 26629 (UH-60L, 4-3 AVN)
ARMY 27039 (UH-60L, 4-3 AVN)
ARMY 27041 (UH-60L, 4-3 AVN)
ARMY 27064 (UH-60L, 4-3 AVN)
ARMY 27065 (UH-60L, 4-3 AVN)
ARMY 27066 (UH-60L, 4-3 AVN)
ARMY 00365 (OH-58D, 3-17 CAV)
ARMY 10330 (OH-58D, 3-17 CAV)
ARMY 10558 (OH-58D, 3-17 CAV)
ARMY 10561 (OH-58D, 3-17 CAV)
ARMY 20581 (OH-58D, 3-17 CAV)
ARMY 20590 (OH-58D, 3-17 CAV)
ARMY 20595 (OH-58D, 3-17 CAV)
ARMY 30981 (OH-58D, 3-17 CAV)
ARMY 26408 (MH-60L, 3-160 SOAR)
ARMY 26416 (MH-60L, 3-160 SOAR)
ARMY 26417 (MH-60L, 3-160 SOAR)
ARMY 03749 (MH-47G, 3-160 SOAR)
ARMY 03750 (MH-47G, 3-160 SOAR)
ARMY 03755 (MH-47G, 3-160 SOAR)
SUNNY ## (RC-12N, 224 MI Bn)
TESTHAWK ## (H-60, OLR)
TESTHOOK ## (H-47, OLR)
COAST GUARD 6510 (MH-65C, Savannah)
COAST GUARD 6542 (MH-65C, Savannah)
COAST GUARD 6545 (MH-65C, Savannah)
COAST GUARD 6565 (MH-65C, Savannah)
COAST GUARD 6604 (MH-65C, Savannah)
TEAL 37 (WC-130, 53rd WRS)
TEAL 80 (WC-130, 53rd WRS)
TEAL 85 (WC-130, 53rd WRS)


Savannah IAP/CRTC
119.100 - Tower
257.800 - Tower
121.900 - Ground
348.600 - Ground
120.400 - Approach/Departure
353.775 - Approach/Departure
125.300 - Approach/Departure
371.875 - Approach/Departure
118.400 - Approach/Departure
307.225 - Approach/Departure
225.750 - 165th AW CP

DAWG ## (C-130H, 165th AW)
BLAZER 321/322 (T-45, Kingsville)
NAVY JR 151 (C-20, VR-48)
INTERIOR 18 (helicopter)
GULF TEST ## (Gulfstream Test)


Fort Stewart/Wright AAF
127.350 - Marne Radio
279.626 - Marne Radio
126.250 - Wright AAF Tower
269.275 - Wright AAF Tower
51.050 - Helicopter Common


MCAS Beaufort
328.425 - Approach/Departure
292.125 - Approach/Departure
281.800 - Base Ops
264.500 - PMSV
361.800 - VMFA-115 Base
335.950 - VMFA-115 Tac 1
225.675 - VMFA-115 Tac 2
253.100 - VMFA-122 Base
283.400 - VMFA-122 Tac 1
354.325 - VMFA-122 Tac 2
344.200 - VMFA(AW)-224 Base
250.300 - VMFA(AW)-224 Tac 1
258.900 - VMFA(AW)-224 Tac 2
313.800 - VMFA-251 Base
290.000 - VMFA-251 Tac 1
327.475 - VMFA-251 Tac 2
376.425 - VMFA-251 Tac 3
228.200 - VMFA-312 Base
301.950 - VMFA-312 Tac 1

BLADE 2# (F/A-18A+, VMFA-115)
NIKEL 3# (F/A-18C, VMFA-122)
BENGAL 4# (F/A-18D, VMFA-224)
TBOLT 5# (F/A-18C, VMFA-251)
CHECK 6# (F/A-18A+, VMFA-312)


Charleston AFB
306.925 - Charleston App/Dep
349.400 - Charleston AFB "PALMETTO OPS"
134.100 - Charleston AFB "PALMETTO OPS"
233.950 - PMSV
372.200 - PTD
314.450 - 437/315 AW air-to-air

LIFTR ## (C-17, 437/315 AW)
MOOSE ## (C-17, 437/315 AW)


Shaw AFB
252.100 - Shaw AFB SOF
311.200 - 55th FS "SHOOTER OPS"
141.675 - 55th FS air-to-air
141.900 - 55th FS air-to-air
142,400 - 55th FS air-to-air
320.525 - 79th FS "TIGER OPS"
138.150 - 79th FS air-to-air
139.925 - 79th FS air-to-air
141.550 - 79th FS air-to-air
141.700 - 79th FS air-to-air

COBRA (F-16C, 55th FS)
CONAN (F-16C, 55th FS)
HAMMER (F-16C, 55th FS)
HYDRA (F-16C, 55th FS)
GUNDOG (F-16C, 79 th FS)
HELLCAT (F-16C, 79th FS)
SLASH (F-16C, 79th FS)
SPITFIRE (F-16C, 79th FS)
TURBAN (F-16C, 79th FS)


McIntire JNGB
298.300 - 169th FW "SWAMP FOX OPS"
141.825 - 169th FW V14
143.625 - 169th FW V15
143.250 - 169th FW V16
141.925 - 169th FW V17
140.125 - 169th FW V18
138.025 - 169th FW air-to-air

MACE ## (F-16C, 169th FW)
VIPER ## (F-16C, 169th FW)
HEAT ## (F-16C, 169th FW)


Jacksonville IAP
251.250 - 125th FW Maintenance/Ops
273.900 - 125th FW SOF
234.800 - 125th FW Aux 6
253.700 - 125th FW Aux 7
314.200 - 125th FW Aux 8
343.000 - 125th FW Aux 9

FANG (F-15, 125th FW)
SNAKE (F-15, 125th FW)
RATTLER (F-15, 125th FW)


Robins AFB/JSTARS
293.525 - 116th ACW "PEACHTREE OPS"
225.725 - JSTARS Discrete
228.050 - JSTARS Discrete
235.325 - JSTARS Discrete
276.075 - JSTARS Discrete
318.300 - JSTARS Discrete
328.025 - JSTARS Discrete
335.975 - JSTARS Discrete
341.750 - JSTARS Discrete
346.675 - JSTARS Discrete
355.250 - JSTARS Discrete
372.150 - JSTARS Discrete
395.150 - JSTARS Discrete

PEACH 2# (E-8C frontend, 12th ACCS)
NIGHTSTAR (E-8C backend, 12th ACCS)
PEACH 3# (E-8C frontend, 330th CTS)
STARGATE (E-8C backend, 330th CTS)
PEACH 6# (E-8C frontend, 16th ACCS)
STRIKESTAR (E-8C backend, 16th ACCS)
PEACH 8# (E-8C frontend, 128th ACCS)
ALLEYCAT (E-8C backend, 128th ACCS)

Ranges/Military Operating Areas
119.225 - Townsend Range
228.400 - Townsend Range
252.900 - Townsend Range
269.350 - Coastal MOAs
343.750 - Bulldog MOA
354.300 - Beefeater ECM Range (Poinsett)
264.700 - Poinsett Range

ADVANCE (JTAC, 15th ASOS)
BEEFEATER (ECM control at Bulldog/Beefeater Ranges)
STRIKER (JTAC at Townsend Range)


SEALORD (USN FACSFAC Jax)
120.950 - North Primary
284.500 - North Primary
267.500 - South Primary
133.950 - South Primary
313.700 - North Secondary
385.300 - W-157 Discrete
376.900 - W-157 Discrete
349.800 - W-157 Discrete
311.500 - BRISTOL Discrete
320.500 - BRISTOL Discrete


DOUBLESHOT (W-161/177)
127.725 - Primary
381.350 - Primary
258.400 - Discrete
279.725 - Discrete


Miscellaneous
BACKE ## (KC=135, 916 ARW)
CASINO (F-15E, 4th FW)
CHALICE (E-3 backend, 963rd ACCS)
DARKSTAR (E-3 backend, 965th ACCS)
DRAGNET (E-3 backend, 966th ACCS)
HOIST (KC-10, 305th AMW)
HUNTRESS (NORAD EADS)
MAD FOX ## (P-3C, VP-5)
NAVY CD 1## (T-45)
NAVY CD 2## (T-45)
NAVY LF ## (P-3C, VP-16)
NAVY LL ## (P-3C, VP-30)
OMEGA 70 (DOD Contract Tanker)
OTIS 24 (KC-130, VMGR-252)
PISTON 24 (KC-135, 6 AMW/927 ARW)
SENTRY 50 (E-3, 965th ACCS)
SENTRY 60 (E-3, 966th ACCS)
TEAL 73 (WC-130J, 53rd WRS)

364.200 - NORAD AICC
260.900 - NORAD Discrete
293.600 - NORAD Discrete
316.300 - NORAD Discrete
225.875 - AWACS Discrete
231.825 - AWACS Discrete
303.100 - AWACS Discrete
320.600 - AWACS Discrete
228.225 - Moody AFB "ANGEL OPS"
311.000 - ACC CP
300.625 - 4th FW air-to-air
360.500 - Aerial Refueling (OTIS/NIKEL/TBOLT)


ARTCC
256.900 - Jax Center
269.550 - Jax Center Columbia Low
277.400 - Jax Center Brunswick Low
281.550 - Jax Center Columbia Low
282.200 - Jax Center Jekyll Low
282.300 - Jax Center Alma High
285.650 - Jax Center Statesboro High
290.400 - Jax Center Waycross Low
319.200 - Jax Center Aiken High
322.500 - Jax Center Savannah Low
346.250 - Jax Center St. Augustine
351.700 - Jax Center Summerville High
363.200 - Jax Center Allendale Low
370.950 - Jax Center Georgetown High
379.100 - Jax Center Charleston Low

323.000 - Atlanta Center Macon

Thursday Morning Mobile Monitoring

This morning, I had several errands to run and did some mobile MilCom monitoring while I was at it.

The F-15s from the 125th Fighter Wing at Jacksonville IAP were working offshore with the NORAD Eastern Air Defense Sector (callsign HUNTRESS). On 293.600, FANG flight was working NORAD vs. SNAKE flight on 316.300.

A JSTARS from Robins AFB, STARGATE, was on 328.025 training with simulated assets. There were long encrypted transmissions on 381.000 which were likely coming from the JSTARS as well.

I got to see a wonderful sight while out and about this morning as well. A C-5 departed Hunter AAF's Runway 10 and began a turn to the north. As it banked into it's turn, condensation streamed from the wings near the wing roots and formed a cloud over the center of the aircraft. What a great photo it would have made had I not been driving!

Mac McCormick III
KF4LMT

Monitoring the US Coast Guard – Sector Charleston and Station Tybee Transition to the RESCUE 21 System

This article was originally published in the September issue of "Groundwaves," the newsletter of the Coastal Amateur Radio Soceity.

US Coast Guard Sector Charleston and its subordinate unit US Coast Guard Station Tybee cover the Savannah area. The Sector Charleston area is in the process of transitioning their communications to the Coast Guard’s new Rescue 21 communications system. This raises two questions: what is Rescue 21 and what does this mean for the radio hobbyist? There are many hams that have programmed the Marine VHF frequencies into their 2-Meter radios to monitor the Coast Guard and knowing where to listen for the Coast Guard could enhance the capability of the ARES operator. First, we’ll learn a little bit about the Rescue 21 system and then we’ll explore what will change for the hobbyist that listens to the Coast Guard.

What is Rescue 21? Rescue 21 is the Coast Guard’s advanced direction-finding communications system. It is replacing the National Distress Response System which has been in service since the 1970’s. It provides an expanded frequency capacity which improves interoperability with other Department of Homeland Security agencies as well as other federal, state, and local agencies. This includes the capacity for using P25 digital technology and encryption capability in addition to the current Marine VHF frequencies.. The system will also allow the simultaneous monitoring of multiple VHF channels, enhanced clarity, and support of Digital Selective Calling (a system for transmitting GPS enabled distress messages). It will also close gaps in coastal coverage areas. Rescue 21 also incorporates an integrated direction finding system. Another interesting feature of the Rescue 21 System is that it provides portable, deployable towers and equipment for the restoration of communications in the aftermath of disasters such as Hurricanes Katrina, Gustav, and Ike. This will quickly allow the Coast Guard to re-establish their communications both within the agency, with other agencies, and with the public during an emergency or post-disaster.

A map of Rescue 21 coverage: Green areas indicate locations in which Rescue 21 is operational; the dots indicate tower locations and the circles indicate tower coverage. The blue areas indicate future Rescue 21 locations. (Diagram from the General Dynamics C4 Systems website)

A diagram of how the Rescue 21 system works utilizing multiple tower sites, and portable towers and equipment. Note the Disaster Recovery System (the deployable towers and equipment mentioned above) on the left hand side of the diagram.

What does this mean for the radio hobbyist? At this point, based on my monitoring experience, it means three things (Note that following applies to communications involving USCG Station Tybee and the MH-65s from USCG Air Station Savannah):

1. You will hear less on the Marine VHF frequencies. Station Tybee has been communicating with its surface assets on federal VHF frequencies that are used by the Rescue 21 system. Some communications with USCG surface assets are still on Marine VHF Ch. 21 (157.050 MHz) and currently all communications with USCG Auxiliary assets and aviation assets remain on Marine VHF frequencies. A list of these frequencies will follow at the end of this article.
2. You will hear an increased amount of P25 digital voice communications with the Rescue 21 system. You will also hear an increased amount of encrypted traffic. Almost all of the transmission I’ve heard from Station Tybee on their new operating channel have been digital encrypted. On the other hand, almost all of the transmissions from the surface assets have been digital in the clear.
3. Because the Rescue 21 system uses both frequencies in the Federal VHF range and digital voice technology, you may have to get some new radio equipment if you want to listen to the Coast Guard. Not all scanners will receive the Federal VHF frequency range (16# - 17# MHz) and many will not receive the P25 digital voice mode. Almost all VHF/UHF Amateur Radio equipment is not P25 digital capable (I believe that Alinco makes some that are capable and it should be noted that the Icom D-Star protocol and P25 are not compatible). Radios like the Radio Shack Pro-96, Pro-106, Pro-197, Uniden BC396 and BC996, and GRE PR-500 and PR-600 are radios that can monitor the unencrypted digital transmissions.

In addition to the common Marine VHF frequencies that are used by the US Coast Guard, you will need to monitor some new frequencies for the Rescue 21 system. Station Tybee has been utilizing Net 113 as the operating channel in recent weeks. The channels are designated with NET 1# and 1## numbers. The frequencies are identical for each 1#/1## combination; the two digit designator indicates analog voice use and the three digit number created by the addition of a one at the beginning indicates digital voice use.

Rescue 21 “NET” Channels
NET 01/101 - 139.9750
NET 02/102 - 140.4750
NET 03/103 - 140.7250
NET 04/104 - 141.6125
NET 05/105 - 150.7250
NET 06/106 - 141.5500
NET 07/107 - 150.3000
NET 08/108 - 162.0500
NET 09/109 - 162.1250
NET 10/110 - 162.2500
NET 11/111 - 162.3250
NET 12/112 - 163.0500
NET 13/113 - 163.1375
NET 14/114 - 164.3000
NET 15/115 - 164.3125
NET 16/116 - 164.5500
NET 17/117 - 164.5625
NET 18/118 - 164.9000
NET 19/119 - 164.9125
NET 20/120 - 165.2625
NET 21/121 - 165.3125
NET 22/122 - 165.3250
NET 23/123 - 165.3375
NET 24/124 - 166.1875
NET 25/125 - 167.9000
NET 26/126 - 168.8625
NET 27/127 - 171.2375
NET 28/128 - 172.3125

One of Rescue 21’s calling cards is Interoperability. This is achieved through the addition of two more sets of frequencies: the VHF Federal Law Enforcement interoperability channels and the VHF Incident Response channels. Both sets are common interoperability frequencies that other federal, state, and local agencies have access to. The Law Enforcement frequencies are designated with “LE” and the Incident Response frequencies are designated with “IR.” LE-1 through LE-5 are duplex channels, LE Alpha and LE-6 through LE-9 are simplex channels. IR-1 through IR-4 are duplex channels, IR-5 through IR-9 are simplex channels (You can look them up in the NIFOG, link below for input frequencies). Station Tybee has been heard using LE-A in recent months.

VHF Law Enforcement (LE)
LE-A - 167.0875 (simplex)

LE-1 - 167.0875

LE-2 - 167.2500

LE-3 - 167.7500

LE-4 - 167.1125

LE-5 - 168.4625

LE-6 - 167.2500 (simplex)

LE-7 - 167.7500 (simplex)

LE-8 - 168.1125 (simplex)

LE-9 - 168.4625 (simplex)

VHF Incident Response (IR)

IR-1 - 170.0125

IR-2 - 170.4125

IR-3 - 170.6875

IR-4 - 173.0375

IR-5 - 169.5375 (simplex) - Calling

IR-6 - 170.0125 (simplex)

IR-7 - 170.4125 (simplex)

IR-8 - 170.6875 (simplex)

IR-9 - 173.0375 (simplex)


Sources:
General Dynamics C4 Systems Website
http://www.gdc4s.com/content/detail.cfm?item=816a4a1c-1316-4879-adff-430e9f7972fa

The Monitoring Times “MT Fed Files” Blog by Chris Parris
http://mt-fedfiles.blogspot.com/2009_05_31_archive.html

USCG Rescue 21 Website and Rescue 21 Fact Sheet
http://www.uscg.mil/hq/cg9/rescue21/
http://www.uscg.mil/hq/cg9/programs/pdf/r21factsheet.pdf

US Department of Homeland Security National Interoperability Field Operations Guide (NIFOG)
http://www.dhhs.state.nc.us/dhsr/EMS/pdf/NIFOG.pdf

Changes Coming in October

Beginning in October, I'll begin working in the Brunswick area. While my permanent residence will remain in Savannah, I'll be staying in Brunswick roughly five days out of each week. Such changes have both their negative and positive aspects. While I won't be able to monitor the smorgasboard of great communications in the Savannah area as much as I do now, a door to monitoring a new area has been opened.

October will lead me to expand the coverage area of this blog to the Brunswick area. There are plenty of things to monitor in Brunswick and I expect to cover them in this blog. Glynn County and Brunswick have an 800 MHz TRS and I'll be learning that system and becoming accustomed to how their agencies operate. Brunswick will put me closer to the military offshore operations closer to Jacksonville that I can't hear well here at home. A short trip down the road is NSB Kings Bay and just a bit farther down the road is Jacksonville.

Material from the Savannah area no doubt will be reduced, but look for material from the Brunswick and Jacksonville area to be added. The mobile monitoring post should see a lot of use; I don't plan on being any less "radio active."

Mac McCormick III
KF4LMT

Monitoring the Shuttle Discovery Launch

I had fun monitoring the Space Shuttle Discovery Launch last night. While the scrubs and delays disappointed many, they did allow me to be able to monitor the launch. I was working the 7-3 shift all week and wasn't able to stay up to listen until last night!

A number of us utilized the Internet and amateur radio to monitor and watch last night's launch, enhancing the experience. I started off the evening by getting updated on developments with Al Stern in Satellite Beach via instant message. After Al got me up to speed, I coordinated monitoring efforts with Dan - KF4MND, Robert - KJ4HAL, and Guy, K4GTM via various IM and social networking applications. Being out of range of the VHF and UHF traffic we mostly were keeping up with the launch via NASA TV and the Booster Recovery Net on 7.833 USB. Not long after, Kevin - KW4B made his way out to Tybee Island to watch the launch; several of us talked to Kevin on the 146.700 repeater as Guy tried to patch in NASA audio via Echolink. For some unknown reason that attempt was unsuccessful, but later Dan was able to transmit audio from NASA TV into the 147.330 repeater, which Kevin was better able to hear from Tybee Island.

Once it was close to launch time, I pushed audio from the shuttle air-to-ground frequency, 259.700, to my UStream feed (linked on this blog), posting it on the Scan Savannah group and passing it on to the others I was monitoring with last night. I received good, strong signals from Discovery last night on 259.700; it picked up at the "2 Engine Moron" call and ended with the "Press to MECO" call.

Mac McCormick III
KF4LMT

Suggested Frequency Move for the Savannah Simplex Net

I would like to suggest moving the weekly simplex net off of 146.520. I understand the reasoning behind conducting the net there, but there is also a very good argument for not holding it on 146.520. I understand the initial reasoning for holding the net on 146.520, it is probably the most monitored simplex frequency on 2 Meters; holding it there would possibly generate more check-ins from those monitoring the frequency. This is admirable but it also goes against the logic behind the use of 146.520.

146.520 is the National FM Voice Calling Frequency. A calling frequency is supposed to be used for initial contact, with extended communications moved off to another frequency. Conducting a net on the calling frequency is therefore contrary to the band plan; it prevents the use of the frequency for it’s intended purpose.

Once again, I understand that the argument is that a net moved off 146.520 would not have as many check-ins because it would not be as “visible.” I offer two opposing arguments:

1. As long as the net has been running, we have an established base of participants. Essentially the same operators check into the net each week. If you run announcements over a month period on both the club nets, the simplex net, and the ARES net it should provide plenty of heads-up on a frequency change.

2. One could argue that conducting the net on 146.520 could attract hams traveling through the area. You could attempt to attract transients monitoring 146.520 by making an announcement on 146.520 about the net prior to the beginning of the net (a proper use of the calling frequency).

So what frequency do we use? SERA lists the following simplex frequencies that do not offer a conflict with repeater inputs: 146.535, 146.550, 146.565, 146.580, 146.595, 147.510, 147.525, 147.540, 147.555, 147.570, and 147.585.

From that list above, I would suggest two frequencies: 146.550 and 147.555. Both have a history of use in this area as a common simplex frequency for 146.550 and 147.550 saw long use a previous simplex net frequency in Savannah. Of the two, I would suggest 146.550 for the simple reason that it Is closer to 146.520 and would be easier to stumble across during a search.

We have to find a balance between generating activity and respecting the band plan. At this point, are we really generating any additional activity by conducting the net on 146.520. This is nothing personal, so I hope no one takes it that way. It’s just a suggestion on my part to allow us to operate more in accordance with the 2 Meter band plan. Any decision to move or not to move the net will have no effect on my participation in the net.

Mac McCormick III
KF4LMT