Once upon a time, August was a quiet month in Washington, when everyone went on vacation. Sure, there are plenty of vacations that will happen this coming month, but it seems that regulatory activity no longer takes a break. For example, August 1 is the due date for the filing with the FCC of license renewals for all radio stations (including translators and LPFM stations) in North and South Carolina, and the filing of associated EEO forms for all full power radio stations in those states. With the renewal filing comes the obligation that these stations start airing, on August 1 and August 16, their post-filing announcements informing the public about the submission of the license renewal applications. Radio stations in Maryland, Virginia, West Virginia and the District of Columbia, who filed their renewals on or before June 2, also need to keep running their post-filing announcements on these same dates. Radio stations in Florida, Puerto Rico and the Virgin Islands, who are in the next license renewal group with their renewal applications to be filed by October 1, need to start broadcasting their pre-filing announcements this month, also to run on the 1st and 16th of the month. See our post here on pre-filing announcements.

Commercial and noncommercial full power and Class A Television Stations and AM and FM radio stations in California, Illinois, North Carolina, South Carolina, and Wisconsin that are part of an employment unit with five or more full-time employees must place their annual EEO public inspection file reports in their online public file. Links to those reports should also be placed on the home pages of these station’s websites, if they have a website. The effectiveness of these EEO public file reports, and the EEO programs of which they are a part, are being reviewed by the FCC in a proceeding started by a Notice of Proposed Rulemaking about which we wrote here. Comments on this notice asking for suggestions about how to make the EEO rules more effective are due August 21, with reply comments due by September 5.
Continue Reading

Last year, as we wrote here, the FCC adopted a number of new rules regarding its emergency communications practices using the EAS system. At that time, soon after all the attention that had been given to the EAS alerts about the false Hawaii missile attack, the FCC adopted rules requiring stations to report to the FCC if they participated in an EAS alert about a fake emergency. Also, the FCC authorized EAS officials to conduct EAS tests using the real event codes for particular emergencies, but only after taking precautions to warn EAS-participating stations and the public that these tests were only tests, and not real emergencies. The effective dates of those new rules were put on hold pending review of the Office of Management and Budget under the Paperwork Reduction Act. According to a Federal Register publication this week, they have now been approved, and thus these rules are now in effect.

The FCC also approved a requirement for state emergency coordinators to file with the FCC in a new electronic database all Statewide EAS plans and any updates to those plans. The OMB also approved the data collection requirements of that rule but the rule will not become effective until one year after the FCC announces that it has created the electronic database to receive these updated plans. We recently noted that the FCC last month published links to statewide plans, and we urged state coordinating committees and participating broadcasters to review these plans to make sure that they have not become out of date with the passage of time. Given the upcoming new filing obligations, it would appear that this review is even more important.
Continue Reading

July is an important month for regulatory filings – even though it is one of those months with no FCC submissions tied to any license renewal dates. Instead, quarterly obligations arise this month, the most important of which will have an impact in the ongoing license renewal cycle that began in June (see last month’s update on regulatory dates, here).  Even though there are no renewal filing deadlines this month, radio stations in Maryland, Virginia, West Virginia and DC must continue their on-air post-filing announcements on the 1st and 16th of the month.  On these same days, pre-filing announcements must be run by radio stations in North and South Carolina, who file their renewals by August 1.  Stations in Florida and Puerto Rico, who file on October 1, should be prepared to start their pre-filing announcements on August 1.  See our article here on pre-filing announcements.

Perhaps the most important date this month is July 10, when all full power AM, FM, Class A TV and full power TV stations must place their quarterly issues/programs lists in their online public inspection files.  The issues/programs list should include details of important issues affecting a station’s community, and the station’s programming aired during April, May, and June that addressed those issues.  The list should include the time, date, duration and title of each program, along with a brief description of each program and how that program relates to a relevant community issue.  We have written many times about the importance of these lists and the fact that the FCC will likely be reviewing online public files for their existence and completeness during the license renewal cycle – and imposing fines on stations that do not have a complete set of these lists for the entire license renewal period (see, for instance, our articles here, here and here).  So be sure to get these important documents – the only official documents that the FCC requires to show how a station has met its overall obligation to serve the public interest – into your online public file by July 10. 
Continue Reading

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

November is perhaps the month with the lightest schedule of routine FCC regulatory filing obligations – with no requirements for EEO Public File Reports, Quarterly Issues Programs or Children’s Television Reports. Nor are there other routine obligations that come up in the course of any year, though during November of 2019, broadcasters will be preparing for next year’s December 1 Biennial Ownership Report deadline. So does that mean that there are no dates of interest this month for broadcasters? As always, there are always a few dates of which you need to keep track.

The one November date applicable to all broadcasters is the requirement for the filing of ETRS Form Three, which gives a detailed analysis of the results of the nationwide EAS test conducted on October 3. Stations should have filed Form Two on the day of the test reporting whether or not the test was received. They now need to follow up with the more detailed Form Three report by November 19. See our article here for more information.
Continue Reading

While September is one of those months with neither EEO reports nor Quarterly Issues Programs or Children’s Television Reports, that does not mean that there are no regulatory matters of importance to broadcasters. Quite the contrary – as there are many deadlines to which broadcasters should be paying attention. The one regulatory obligation that in recent years has come to regularly fall in September is the requirement for commercial broadcasters to pay their regulatory fees – the fees that they pay to the US Treasury to reimburse the government for the costs of the FCC’s operations. We don’t know the specific window for filing those fees yet, nor do we know the exact amount of the fees. But we do know that the FCC will require that the fees be paid before the October 1 start of the next fiscal year, so be on the alert for the announcement of the filing deadline which should be released any day now.

September 20 brings the next Nationwide Test of the EAS system, and the obligations to submit information about that test to the FCC. As we have written before (here and here), the first of those forms, ETRS Form One, providing basic information about each station’s EAS status is due today, August 27. Form Two is due the day of the test – reporting as to whether or not the alert was received and transmitted. More detailed information about a station’s participation in the test is due by November 5 with the filing of ETRS Form Three. Also on the EAS front, comments are due by September 10 on the FCC’s proposal to require stations to report on any false or inaccurate EAS reports originated from their stations. See our articles here and here.
Continue Reading

The last month has been one where there has been lots of activity dealing with EAS. The FCC announced that it will be conducting a Nationwide EAS Test on September 20, 2018. The FCC has been conducting these Nationwide tests routinely over the last few years (see, for instance, our articles here and here on past tests). This test will include wireless carriers as well as broadcasters. To be prepared for this test, the FCC reminded EAS participants to file their updated ETRS Form One by August 27 (see our article here), and to be prepared to file the post-test Forms Two (filed on the day of the test) and Three (due by November 5) to report on the results of the test at their stations.

At its July meeting (as we briefly noted here), the FCC adopted an Order making some changes to the EAS rules, as well as asking further questions in an included Further Notice of Proposed Rulemaking. The changes included:

  • New rules allowing “live code testing” – using actual EAS alert tones in practice alerts, but only after providing lots of publicity that the tones are being used only as part of a test
  • Allowing the use of the EAS attention signal in PSAs and other informational announcements from FEMA and other public interest organizations – but only where simulated tones developed by FEMA are used, as these simulated tones will not trigger other station’s EAS alerts, and only where the tones used are specifically identified as not being a real notice of an emergency.

Use of the alert tones like this have been approved in the past by the FCC, but only by use of a waiver process. The FCC actions allow for more testing and more public information without having to request FCC approval for each such use.
Continue Reading

The FCC recently released a Public Notice reminding all EAS participants that they need to file ETRS Form One by August 27, 2018. This form needs to be filed by all radio and TV stations, including LPFM and LPTV stations (unless those LPTV stations simply act as a translator for another station). While the