One million dollars is still a big fine, even though the FCC has been handing out fines for that amount, or more, many times in recent months. But fines rarely hit these levels for broadcasters. But, yesterday, the FCC issued such a fine – hitting iHeart Media with a $1 Million fine as part of a Consent Decree imposed for the inappropriate use of EAS tones in the Bobby Bones syndicated radio program. The program was being run on 82 stations across the country. According to the FCC’s order approving the Consent Decree and imposing the associated fine and compliance plan, the broadcast of those tones triggered EAS alerts across several states – principally at stations and cable systems that had not activated the ability of the EAS system to recognize the date of an alert (the program rebroadcast the FCC’s first national EAS test, a test that was conducted almost 3 years before the Bones broadcast).

As with many other recent cases where the FCC has imposed heavy fines on broadcasters and cable programmers for use of EAS tones in entertainment broadcasts (see our articles here, here, here, and here tracing the history of the FCC’s escalating penalties for this kind of violation over the last few years), the FCC sees these matters as threats to public health and safety, as the public could react adversely to these EAS alerts that were not tied to real emergencies (or be desensitized by repeated false alerts to the importance of real alerts). The FCC’s News Release announcing the adoption of the Consent Decree makes exactly this point – the misuse of EAS alerts are threats to the public safety.
Continue Reading FCC Fines iHeart Media $1,000,000 for Broadcasting EAS Alert Tones When there was No Emergency – What the Big Fine Says to Broadcasters

May is one of those months where there are no routine, recurring FCC regulatory filing deadlines – no EEO reports or Quarterly Issues Programs lists, no Children’s Television Programming Reports or noncommercial station ownership report deadlines. But, as with any month, that does not mean that there are no dates of concern for broadcasters – as there are certain compliance deadlines and other important dates of which broadcasters need to be aware in the upcoming month. Here is our summary of some of the dates that broadcasters should be watching in the upcoming month.

The only thing approaching a routine regulatory date of note is the obligation of TV stations in Delaware and Pennsylvania to air the third and fourth of their required six post-filing announcements of the filing of their renewal applications – the last of the renewal applications for either radio or TV that were filed in this renewal cycle. The next routine license renewal filing window will be when radio renewals being again in June of 2019 – with the filing of radio license renewals by stations in Maryland, Virginia, West Virginia and DC. However, as we have written before, EEO Mid-Term reports are due from larger radio station groups in these 3 states and in DC on June 1 of this year. So radio station employment units (commonly controlled station groups serving the same area and having at least one common employee) with 11 or more full-time (30 hours per week) employees should be preparing to file those reports on FCC Form 397 by June 1.
Continue Reading May Regulatory Dates for Broadcasters – Including EEO Mid-Term Reports, FM Auction, Emergency Communications Compliance, TV Market Modification Comments, Class A TV Digital Conversion Deadline and More

Last month, I did a seminar at the College Media Association about the FCC legal issues that college broadcasters need to think about – talking about required FCC filings, pubic file obligations, underwriting issues, and programming that can get the broadcaster into trouble. Slides from that presentation, which present only an outline of the more detailed discussion that we had during the session, are available here.

I mentioned during the session that the FCC decided two years ago that they would be somewhat lenient with student-run radio stations who are first-time violators of certain FCC rules. In a case that we wrote about here, the FCC said that the fines that are imposed on commercial broadcasters for rule violations like the failure to include quarterly issues programs lists in the public inspection file (fines which can exceed $10,000 when numerous such lists are missing from the public file), would be greatly reduced – to something on the order of $1000 – for student-run stations that are facing their first violation, and provided that the fine dealt principally with paperwork matters and was not one that affected public health or safety. In a decision released by the FCC last week, the limits of that leniency were made clear.
Continue Reading A Seminar on FCC Rules for College Broadcasters – And an FCC Case on the Limits on Leniency on Fines For Rule Violations By Noncommercial Broadcasters

The FCC two years ago adopted a rule requiring that television stations that provide emergency information visually (e.g. through open captions or crawls), outside of news programming, convert that emergency information into audio and run that audio on SAP channels (secondary audio programming channels – usually used for Spanish language translations of English-language programs). That

A flurry of fines against broadcasters have come out of the FCC in the last week.  These fines highlight the scrutiny under which owners of broadcast stations can find themselves should an FCC Field Office inspector knock on their door.  If the FCC pays a visit and finds a violation, a station is often looking at a fine even if it quickly takes corrective action.  Let’s look at some of these fines and the issues raised by each.

First, a Regional Director of the FCC’s Enforcement Bureau yesterday released a $17,000 Forfeiture Order (a notice of a fine) to a Michigan AM broadcaster for having a fence around its tower that had “separated” allowing unfettered access to the site and for missing quarterly issues programs lists in the public file.  The FCC refused to lower the fine, despite the licensee’s arguments that the quarterly issues programs lists were in fact at the station but there was “confusion” as to where they were at the time of the inspection, and its argument that it should not be responsible for the fencing issue as it did not itself own the real estate or the towers.
Continue Reading FCC Fines: $17,000 for Unsecure AM Tower Fence (Not Owning the Tower Site is No Excuse); $25,000 for Missing Quarterly Issues Programs Lists; $22,000 for Nonfunctioning EAS and Wrong Tower Coordinates

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