A lot of the nasty-grams are posted, but I'm starting to wonder the same
thing.  It might have been in ARRL letter or something like that.

Mike
WM4B

From: Repeater-Builder@yahoogroups.com
[mailto:repeater-buil...@yahoogroups.com] On Behalf Of Randy Brumback
Sent: Sunday, April 12, 2009 2:56 PM
To: Repeater-Builder@yahoogroups.com
Subject: RE: [Repeater-Builder] Repeater ID Enforcement




Mike, I am sitting here wondering if a nasty-gram would be considered
“enforcement”? If they are two different things then looking in the
enforcement section might not be the right place.
Randy
 
From: Repeater-Builder@yahoogroups.com
[mailto:repeater-buil...@yahoogroups.com] On Behalf Of Mike Besemer (WM4B)
Sent: Sunday, April 12, 2009 10:51 AM
To: Repeater-Builder@yahoogroups.com
Subject: RE: [Repeater-Builder] Repeater ID Enforcement
 




Been looking… just haven’t hit paydirt yet!
 
73,
 
Mike
WM4B
 
From: Repeater-Builder@yahoogroups.com
[mailto:repeater-buil...@yahoogroups.com] On Behalf Of Mike Mullarkey
Sent: Sunday, April 12, 2009 9:59 AM
To: Repeater-Builder@yahoogroups.com
Subject: RE: [Repeater-Builder] Repeater ID Enforcement
 





Go to the www.fcc.gov web page and search there. They are bound by law to
post all nasty grams there and are available for the public to view.
 
Hope this helps.
 
Mike
 
________________________________________
From: Repeater-Builder@yahoogroups.com
[mailto:repeater-buil...@yahoogroups.com] On Behalf Of Mike Besemer (WM4B)
Sent: Sunday, April 12, 2009 7:10 AM
To: Repeater-Builder@yahoogroups.com
Subject: [Repeater-Builder] Repeater ID Enforcement
 






I know we’re not supposed to discuss FCC rules on this forum, so I hope this
isn’t across the line.
I’m trying to find a Rileygram citing a repeater owner because his repeater
ID’d at 10-minute intervals without user input (beaconing).
Does anybody happen to have a copy or know where it’s posted?  I’ve been
going through the Amateur Enforcement Actions on the FCC page, but haven’t
come across it yet… and am hoping not to have to dig too far!
73,
Mike
WM4B



Reply via email to