While many of us were trying to enjoy the holidays, the world of regulation kept right on moving, seemingly never taking time off.  So we thought that we ought to highlight some of the actions taken by the FCC in the last couple weeks and to also remind you of some of the upcoming January regulatory deadlines.

Before Christmas, we highlighted some of the regulatory dates for January – including the Quarterly Issues Programs Lists due to be placed in the online public file of all full-power stations by January 10.  Also on the list of dates in our post on January deadlines are the minimum SoundExchange fees due in January for most radio stations and other webcasters streaming programming on the Internet.  January also brings the deadline for Biennial Ownership Reports (postponed from their normal November 1 filing deadline).

In that summary of January regulatory dates, we had mentioned that the initial filing of the new Annual Children’s Television Programming Report would be due this month.  But, over the holiday week, the FCC extended that filing deadline for that report until March 30 to give broadcasters time to familiarize themselves with the new forms.  The FCC will be doing a webinar on the new form on January 23.  In addition, the FCC announced that many of the other changes in the children’s television rules that were awaiting review under the Paperwork Reduction Act had been approved and are now effective.  See our article here for more details.
Continue Reading

Several years ago, the FCC mandated that broadcasters utilize not only the traditional over-the-air “daisy-chain” broadcast EAS alerting system where emergency alerts are passed from one station to another but also utilize an Internet-based Common Alerting Protocol (“CAP”) system where warnings can be sent directly to stations (see, for example, our articles here and

The FCC on Monday released a Public Notice announcing that its next test of the Emergency Alert System (EAS) is scheduled for August 7 with a back-up date of August 21 (back-up dates being provided in the event that there are severe weather situations or other emergencies in early August which could increase the potential for public confusion on the originally scheduled date). This test will, unlike the last test we wrote about here, rely solely on the broadcast-based daisy chain where the test is initiated on certain broadcast primary stations, then rebroadcast by stations that monitor those primary stations, who then pass on the test to other stations that monitor these secondary stations and so on down the line to all the EAS participants. This test will not use the Internet-based IPAWS system used in other recent tests.

Thus, in the run-up to the August test, broadcasters should be sure that their EAS receivers are in working order and are tuned to receive the correct stations that they should be monitoring in order to receive alerts. Check your state EAS plan to make sure you know what stations you are to monitor. Make sure that you have been receiving and logging (in your station log) weekly and monthly tests as required by the FCC rules. If you have not been receiving these tests, that likely indicates problems either with your receivers or with the stations that you are monitoring – so find out the reasons for missing tests now and take any corrective actions (as you are required to by the rules). Check out all of your other EAS equipment to make sure that everything is working properly and prepare for the other paperwork obligations that arise because of the upcoming test.
Continue Reading

We wrote earlier this week about the upcoming EAS Nationwide Test and the need for broadcasters to make sure that their EAS equipment is operating in compliance with all FCC rules. The FCC itself has now released its own Public Notice detailing the many things that broadcasters need to check at their facilities before the