[TVARC] "Florida State Parks On-the-Air" (FLSPOTA) - April 6-7, 2019

[Anthony Hackenberg]

 Hi Members of TVARC's Mailing List,

Is anybody planning to participate in this weekend's "Florida State Parks
On-the-Air" (FLSPOTA) event?  It's held the first full weekend in April.
So, in 2019, it will be held on April 6 & April 7, 2019, in these two,
separate sessions of eight (8) hours each:

UTC: 1400Z-2200Z, Saturday Apr 6 AND 1400Z-2200Z, Sunday Apr 7, 2019
EDT: 1000 -1800 ,    Saturday Apr 6 AND 1000 -1800 ,   Sunday Apr 7, 2019

You can participate as an *"activator"* (one person, or a team, going to a
Florida State Park and operating from it).  I am thinking about activating
"Lake Griffin State Park" (State Park ID#: GRF; POTA ID#: KFF-1889) for a
couple of reasons.  First, it's location (at 3089 US Highway 441/27
Fruitland Park, FL 34731) is close to The Villages.  Second, I've never
visited this park before.  Third, and most importantly, nobody has "staked
their claim" as an activator for this park.

You can also participate as a *"chaser"* (remain at your home QTH and
contact other stations operating at parks around the State).  Of course,
propagation does not favor in-state chasers (i.e. Florida-to-Florida
contacts can be difficult).

Unfortunately, FLSPOTA's first session on Saturday, April 6, conflicts with
TVARC's "Radio Rodeo" event.  On the other hand, the extra activity on the
HF bands generated by the FLSPOTA event may give a boost to our club's
radio operations at Brown

For more details/information about this annual event, check out these
references:

http://flspota.org;
http://flspota.org/rules; &
https://www.contestcalendar.com/contestdetails.php?ref=612

So, is anybody planning to activate a Florida State Park for this
event/contest?  Is anybody forming an activation team?  Would anybody be
interested in forming a small team to activate a park?

73,

Tony/K4QR
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.qth.net/pipermail/tvarc/attachments/20190404/32a378cb/attachment-0001.html>