Emergency Communications

Subscribe to Emergency Communications via RSS

The FCC seems to be making another statement – releasing one decision upholding two very large fines against major cable programmers for improper use of EAS tones in ads for a movie, while just two days later releasing another decision approving a consent decree with a broadcaster imposing a penalty and monitoring conditions for using those tones in a radio show.  The first decision was by the full Commission.  It upheld a preliminary decision by its staff that we wrote about here, imposing fines of $1,120,000 against Viacom and $280,000 against ESPN.  The new case was against a Univision radio station in New York – agreeing in a consent decree to a $20,000 penalty.

The new case arose at a Spanish language station, where DJs in a comedy sketch on a morning radio show played the EAS tones repeatedly while joking about men who gain weight, and once even joking that playing the tone was illegal.  The FCC was alerted to the use of the tones by a radio listener who apparently was scanning the radio band, heard the tones and tried to determine what the emergency was – eventually figuring out that the alerts were not really part of an emergency at all.  The $20,000 penalty was combined with the FCC’s imposition of a requirement that the station prepare a compliance manual for its employees about the EAS system, conduct training programs, and report to the FCC about its compliance with the plan and the EAS rules for the next three years – including any EAS noncompliance at any of its stations.
Continue Reading More Big Penalties for Use of EAS Tones in Non-Emergency Programming

Perhaps Sunday’s anniversary of Pearl Harbor made the FCC want to make this week one which concentrated on emergency communications issues, or perhaps it is just a coincidence.  But the FCC has been active in the past 7 days dealing with emergency communications related items for broadcasters.  On Wednesday, it issued a consent decree by which a broadcaster agreed to a $46,000 fine for the use of EAS tones in a commercial message. This decision follows on the heels of an investigatory letter sent to a satellite radio programmer about the apparent use of a simulated EAS tone in a commercial message when, of course, there was no real emergency.   On Monday, there were two fines for non-operational EAS receivers and EAS recordkeeping failures.  At the end of last week, comments were filed in an FCC proceeding looking at the retransmission of EAS alerts in non-emergency situations, such as when a tone is included in programming on a station, and what can be done to avoid those alerts being sent throughout the system.  Comments are also due by the end of the month on suggested best practices on security for the EAS system, in light of the many issues that have arisen with the hacking of EAS receivers.  Here is a quick look at each of these issues.

The two most recent decisions highlight the severity with which the FCC is treating the use of EAS tones – real or simulated – in non-emergency programming.  We have written about past cases where the FCC has issued very substantial fines for the use of such tones in nonemergency situations, here and here.  In the decision released on Wednesday, the licensee of a Michigan radio station admitted to having broadcast ads for a storm-chasing tour which contained the EAS warning tones.  The National Weather Service received complaints, and in turn filed a complaint with the FCC.  The Consent Decree does not provide much more information, but to indicate that the commercial containing the EAS tones was broadcast on only a single day.  A $46,000 fine for a one-day violation demonstrates the gravity with which the FCC views these violations.  And it is a sense of importance that attaches not just to licensees, but to programmers as well.
Continue Reading A Week of Emergency Alert System Actions at the FCC – Fines Including One for $46,000 for EAS Tones in a Commercial, and Reviews of Best Practices for the System

Some quick items to update some of our recent articles.  The FCC has granted extensions of time to comment in two rulemaking proceedings, and released its tentative agenda for its next open meeting where it will adopt an initial order in the incentive auction proceeding.  That’s the proceeding that we most recently wrote about…

This blog usually covers legal and policy issues, not product reviews.  And this article will at least try to relate policy decisions to a product review, but mostly it’s to share a cool new feature on my phone.  To explain, I am one of those holdouts still using a Blackberry.  In dealing with new media clients, I almost feel like I have to make excuses for still using a Blackberry, but as an attorney who travels frequently and writes many emails from the road, the physical keyboard really makes a difference – at least to me.  I can at least say that I did upgrade to the Q10 last year – the Blackberry that has the physical keyboard, but also has a new faster operating system that relies much more on touch commands for everything but the actual typing.  This week, I received what I consider a gift from Blackberry, as I’m also a big radio fan.  While I listen to Internet radio and use digital music services, I also still really enjoy listening to over-the-air radio.  This week, my Blackberry Q10 received an upgrade to its operating system and, with that upgrade, the phone’s FM chip was activated.  Now, my ATT phone gets over-the-air radio – becoming the modern equivalent to the transistor radio – a radio in my pocket at all times.  Of course, being a lawyer, the whole question of activating FM chips in mobile phones brings up policy issues, as it has been in and out of many policy arguments over the last few years.

First, a qualification must be made for international readers of this blog.  The question of an active FM chip in a mobile phone is an issue in the US, but not in many other countries of the world, where FM reception on mobile phones has been standard for many years.  In the US, that has not been the case.  While the chips are built into most phones, they are not activated.  Some suggest that the chips are not activated because the carriers want to encourage data usage through the use of online audio, but the carriers simply say that there is no consumer demand for the activation of the feature.  No matter what the reason, the chip has not been activated in most US phones, and thus policy issues from time to time arise as to whether it’s activation should be mandated or encouraged by government action.
Continue Reading Activating the FM Chip in Mobile Phones – As Blackberry Steps Up, a Policy and Product Review

With so much going on at the FCC and in connection with other topics that we consider, I’m sometimes late getting to all of the issues that arise, and sometimes never mention some of them.  But there is one interesting and important proceeding that the Commission has recently resuscitated and is worthy of mention – the proposal to mandate multilingual emergency alerts by broadcast stations – even when the station broadcasting in a language other than English is knocked off the air by some local emergency.  The proposal would require that all primary EAS stations broadcast national alerts in both English and Spanish, and that state EAS plans should designate stations to provide emergency information in other languages where there are significant populations that have a primary language other than English or Spanish.  Not only that, but English language stations in these areas are proposed to have to play a back-up role, ready to step in and provide emergency information in one of these languages should the primary station serving a particular non-English speaking population be forced off the air.  Comments on this proposal are due on April 28, and replies by May 12.

This is not a new proposal, having first been raised by MMTC (the Minority Media Telecommunications Council) in 2005 after there was a perceived failure to get information to minority populations in the area of Hurricane Katrina.  In recent filings, MMTC has suggested that broadcasters need to work together with local authorities to develop a plan that communicates each party’s responsibility based on likely contingencies. Specifically, MMTC stated, “Such a plan could be modeled after the current EAS structure that could include a ‘designated hitter’ approach to identify which stations would step in to broadcast multilingual information if the original non-English speaking station was knocked off air in the wake of a disaster.” What are the potential issues with such an approach? 
Continue Reading FCC Requests Comments on Proposal to Require Multilingual EAS Alerts – Comments Due April 28

The FCC has recently staked out a policy that the any use of EAS tones, or tones that sound like those alerts, outside of a real emergency, will lead to big fines.  Since the beginning of the year, the FCC has issued notices proposing fines totaling over $2.2 million against some of the biggest media companies in the country for such violations (see this decision proposing a $300,000 fine against Turner Broadcasting System Inc. for tones mimicking the EAS alerts that were included in a commercial transmitted nationwide in cable network programming, and this decision imposing cumulative fines of over $1.9 million on 3 cable network programmers for transmitting ads for the movie Olympus Has Fallen that included portions of the EAS alert tones).  Only days after the latter decision, a new warning about EAS tones or sound effects made to mimic those tones was sent out by the Southern California Broadcasters Association alerting broadcasters to a commercial for a charcoal briquettes company that seemingly contained such tones.  Given the strict liability that the FCC has been imposing for such commercials, watch for this recent ad and any other programming that might contain EAS tones or anything that sounds like them – and keep them off the air. 

With past warnings on this issue (see our article from November about another set of FCC fines for similar broadcasts,  and the release of an FCC press release warning media companies about the issue) and the recent large fines imposed on major media companies – both broadcast and cable – it is clear that all media companies need to be on the alert to monitor their broadcast material for the any content sounding like EAS alerts, and advertisers and program producers need to be aware that anything they produce that contains the alert tones is likely to cause problems at the FCC.  Note that these recent decisions imposed penalties on cable networks – so it is not just licensees who need to be vigilant.  In these decisions, the FCC has rejected any arguments that the media companies that transmitted the advertising containing the alert tones should be excused from liability as they did not themselves produce the ads.  So watch for these tones – even if they are packaged in someone else’s programming. 
Continue Reading Be on the Alert for EAS Tones in Non-Emergency Situations – Big FCC Fines for These Violations and Other EAS Issues

The FCC is cracking down hard on television stations and cable companies who use EAS alerts – or even simulations of such alerts – in advertising, promotions, and programming.  In two orders released this week, the FCC imposed big penalties on video companies who used fake EAS alerts in commercial messages.  In one case, it fined a cable programmer (Turner Broadcasting) $25,000 for the use of a simulated EAS tone (not using the actual tone, but just a set of tones that sounded like the EAS alert) in a promotion for the Conan O’Brien program.  In a consent decree with a TV broadcaster, in exchange for a $39,000 voluntary payment to the FCC and the adoption by the station of a series of policies to avoid similar problems in the future, the Commission agreed to dismiss a complaint against a station that had used simulated EAS tones in a commercial for a local store.  These decisions were coupled with two other announcements to make the point that the FCC wanted to demonstrate the importance that it places on EAS and its lack of tolerance for any non-emergency use of anything sounding like the EAS tones that could possibly confuse the public.

At the same time as the two decisions were released, the FCC issued a press release emphasizing the importance of EAS and how such actions trivialized the alert system.  A Fact Sheet was also released, making four documents all emphasizing the importance of EAS, and the threat posed to real warnings by any sort of use of sounds that could be confused for the EAS alerts.  Where does the FCC get its authority to impose such fines?
Continue Reading Penalties of $39,000 and $25,000 Assessed For Video Programming Containing Fake EAS Messages

In 2011, the FCC conducted the first-ever nationwide test of the Emergency Alert System – commonly known as EAS (see our article here about the FCC’s report on the results of that test). While the system was originally created to convey Presidential alerts to the nation, it has never been used for that purpose and, until the nationwide test, it had never even been tested. Instead, EAS has most commonly been used for local emergencies like weather alerts and, in recent years, Amber Alerts for missing or abducted children. In the Public Notice released this week, the Commission asked for comments on a number of issues uncovered during the nationwide test, which in many ways illustrated how far the EAS system has evolved from its original purpose.

The issues on which comments are sought are principally technical issues of system design, such as whether the time codes in the EAS headers work the same on all EAS hardware, or whether these codes resulted in tests running at different times on different stations.  Apparently, some stations immediately broadcast the alert when received, and others delayed it until the time specified in the codes indicated that it should be run (3 minutes after the alert was sent out). The Commission also noted that there is no specific code in the standard alert codes for a nationwide alert. Similarly, there is no “location code” for a nationwide alert, as all of the location codes (which specify the geographic area where the alert is targeted), have been set up on a state-wide or more localized basis for the weather alerts and other similar localized emergencies for which the system is regularly used. These would all seem like easy things to fix – but are they?Continue Reading FCC Seeks Comments on Technical Details of Nationwide EAS Test – Preparing for the Next Test?

Almost a year and a half ago, the FCC held its first ever test of the EAS system designed to alert the country in the event of a nationwide emergency. On Friday, the FCC’s Public Safety and Homeland Security Bureau issued a report on the results of the test. While there have been many articles in the trade press reporting on some of the findings of the Bureau, few have focused on one footnote indicating that many EAS participants – including some broadcasters and cable systems – never bothered to file their reports as to the results of their participation in the tests. The Bureau notes that the identity of these broadcasters will be turned over the FCC’s Enforcement Bureau for further action – potentially fines for their failures to report on the results of the test (we warned that this might be a consequence of the failure to file a report of the results of the test in our article here).  Broadcasters should watch for further action from the Enforcement Bureau at some point in the future.

The Report indicated that approximately 83% of all broadcasters who reported to the FCC had received the test. However, the FCC received reports from only about 13,787 stations.  According to the FCC’s tabulation of the number of broadcast stations in the US, as released in another FCC report last week, there are approximately 15,256 radio stations and 1781 TV stations in the United States. This could mean that there are a substantial number of broadcast stations that did not report the results of the nationwide test. The Commission apparently did not try to determine if the results achieved by those nonresponsive stations were different than the results of those who reported to the FCC.  One might assume that these stations, which somehow missed all the warnings about the need to file with the FCC the results of the tests, probably also missed instructions about how to comply with the EAS rules and thus were probably less likely to have fully operating EAS systems. So there is concern that the report may even understate the shortcomings of the nationwide test.Continue Reading FCC Issues Report on Nationwide EAS Test And Refers to the Enforcement Bureau Stations That Did Not Submit the Results of the Test – Could Fines Follow?