Topband
[Top] [All Lists]

Topband: How to File BPL Comments With the FCC

To: <topband@contesting.com>
Subject: Topband: How to File BPL Comments With the FCC
From: btippett at alum.mit.edu (Bill Tippett)
Date: Mon Aug 18 07:40:39 2003
K3KY wrote:
Note: As of 4 AM on Monday the 18th, the site is still
partially non-functional. It now 'accepts' my comments but
returns an error message when I click on the confirmation
bar on the next page. I will keep trying. I hope this site
is not still broken when the 20th rolls around!

         I just submitted my Reply Comment after 7 AM and it went through
fine with confirmation.  It is not unusual that they chose the weekend
for maintenance since all ECFS comments require some screening (virus,
spam, etc) before they are posted, which is normally on the day
following submission.  There is still plenty of time to post comments
before the end of the Reply Comment window on August 20.

         Please do remember that your comments should be entered using
the "Reply to Comments" description, and should reference an original
comment you are responding to.  Mike W4EF gave us a few samples here:

http://dayton.akorn.net/pipermail/topband/2003-August/017275.html

         In composing my letter, I also noted something which may be of
general interest to all.  Riley Hollingsworth has written 21 letters
to utility companies regarding interference complaints from amateurs
in the past 12 months alone:

<http://www.arrl.org/news/enforcement_logs/>http://www.arrl.org/news/enforcement_logs/
 


Just imagine what both the FCC and utility companies will face
with millions of SWL's, CB'ers and amateurs complaining...not
to mention commercial and government users of the HF spectrum!

         Another interesting fact I noticed was that several letters
were written by Riley to individuals regarding interference from
things like electric fencers, portable phones, etc.  If you have not
been able to resolve local interference problems due to part 15
devices, contacting the FCC appears to be a viable alternative,
but I would consider it only as a last resort.

                                 73,  Bill  W4ZV 

<Prev in Thread] Current Thread [Next in Thread>