Articles Posted in Emergency Alert System

Published on:

Pillsbury’s communications lawyers have published FCC Enforcement Monitor monthly since 1999 to inform our clients of notable FCC enforcement actions against FCC license holders and others. This month’s issue includes:

  • Investigation Into Undisclosed Radio Station Owner With a History of Felonies Leads to Hearing Designation Order
  • FCC Settles With Alaskan Broadcaster After Disastrous Station Inspection
  • FCC Reinstates Licenses for Tennessee and Alabama Radio Stations, Then Immediately Threatens to Revoke Them

Continue reading →

Published on:

Last week, the Federal Emergency Management Agency (FEMA) formally notified the FCC that FEMA has scheduled the next nationwide test of the Emergency Alert System (EAS) for August 7, 2019 at 2:20 p.m. FEMA states that this year’s test will differ from the nationwide tests that have been conducted over the past several years in that it will be issued through the National Public Warning System, composed of FEMA-designated Primary Entry Point facilities, to test the readiness of the EAS to function in the absence of Internet connectivity.

Continue reading →

Published on:

Pillsbury’s communications lawyers have published FCC Enforcement Monitor monthly since 1999 to inform our clients of notable FCC enforcement actions against FCC license holders and others.  This month’s issue includes:

  • Oregon LPFM Station Warned Over Emergency Alert System Violations
  • Pennsylvania Man Accused of Interfering With Local Fire Department Operations
  • Earth Station Transmission Problems Lead to Warning Against Florida Wireless Licensee

This is Not a Test: Low Power FM Station Warned Over Emergency Alert Violations

The FCC’s Enforcement Bureau presented a Notice of Violation (“NOV”) to the licensee of a Portland, Oregon low-power FM radio station for a number of violations relating to the Emergency Alert System. The licensee is a local cultural community center that broadcasts Russian-language programming to the area’s Eastern European community.

The Emergency Alert System (“EAS”) is a nationwide warning system that allows authorized state and national public agencies to alert the public about urgent situations, including natural disasters and other incidents that require immediate attention.  The EAS is jointly operated by the FCC, the Federal Emergency Management Agency, and the National Oceanographic Atmospheric Administration.  Local radio stations make up a vital component of the system by monitoring authorized sources for alerts and rapidly relaying these emergency messages.  Such stations are referred to as “EAS participants.”  Each state is responsible for creating a state EAS plan, which includes designating in-state stations that other stations must constantly monitor for alerts.

Section 11.15 of the FCC’s Rules requires that a copy of the EAS Operating Handbook be located “at normal duty stations or EAS equipment locations when an operator is required to be on duty.”  Section 11 of the Rules also requires EAS participants to monitor two sources, which are specified in each state’s respective EAS plan.

In February 2019, Enforcement Bureau agents inspected the Portland station and discovered two violations of the EAS Rules.  According to the NOV, the station was unable to produce its copy of the EAS Operating Handbook.  The agents also discovered a monitoring error.  The most recent Oregon State Emergency Alert Plan required the station to monitor two specific Portland area FM stations.  During the inspection, the agents found the LPFM station had instead been monitoring a different station.

The licensee has 20 days to respond to the NOV.  In its response, it must provide: (1) an explanation of each violation; (2) a description of the licensee’s corrective actions; and (3) a timeline for completion of these actions.  The FCC will then consider the licensee’s responses and all relevant information to determine what, if any, enforcement action it will take against the licensee for the violations.

State Your Emergency: FCC Accuses Pennsylvania Man of Interfering With Safety Services

In a Notice of Unlicensed Operation and Notification of Harmful Interference (“Notice”), the FCC accused a man of using a two-way radio to cause harmful interference to a local emergency services operation by making unauthorized transmissions on a frequency reserved for public safety.

As we discussed last year, Chairman Pai has noted that protecting public safety and emergency response communications is of the utmost importance.  The Enforcement Bureau has recently responded aggressively to interference complaints from first responders and emergency service departments, including issuing multi-thousand dollar fines.

Section 301 of the Communications Act prohibits the transmission of radio signals without prior FCC authorization.  Section 90.20 of the Rules establishes the requirements for obtaining authorization to use public safety frequencies.  The FCC reserves certain bands for first responders as “public safety spectrum.” Unauthorized transmissions on such bands can pose a threat to first responders and the general public by interfering with local emergency service operations, including police, EMS, or in this case, the fire department.

The Enforcement Bureau began its investigation after being contacted by an eastern Pennsylvania county’s Emergency Management Association.  According to the complaint, harmful interference and unauthorized transmissions were occurring on 155.190 MHz, a frequency used for local fire department communications.  The Enforcement Bureau identified a local individual as the source of the interfering transmissions.

According to the Notice, the individual admitted to operating a VHF-UHF two-way radio at 155.190 MHz, despite not being authorized to operate on that frequency.

The individual was given 10 days to respond to the Notice.  In his response, the individual must explain the steps he is taking to avoid operating on unauthorized frequencies and causing harmful interference.  It will then be up to the FCC to determine whether further enforcement action, including fines or other sanctions, is appropriate. Continue reading →

Published on:

The Federal Emergency Management Agency (FEMA), in coordination with the FCC, announced this morning that the National Emergency Alert System (EAS) and Wireless Emergency Alerts (WEA) tests scheduled for this Thursday, September 20, have been postponed due to “ongoing response efforts to Hurricane Florence.”

Instead, the tests will be conducted on the previously announced backup date of October 3.  The Wireless Emergency Alerts test will commence at 2:18 p.m. EDT and the EAS test will commence at 2:20 p.m. EDT on that date.  FEMA has indicated that the purpose of the tests is to “assess the operational readiness of the infrastructure for distribution of a national message and determine whether improvements are needed.”

As we previously discussed on CommLawCenter, in preparation for the national test, all EAS Participants were required to file their Form 1 with the FCC by August 27, 2018.  They were then to file their Form 2 (day of test data) on September 20, 2018, with the final test report to be filed on Form 3 by November 5, 2018.

The Form 2 (and likely the Form 3) deadline will now shift to align with the new October 3 test date.  As of the publication of this post, the FCC had not yet announced new filing deadlines, but the Form 2 will likely be due on October 3, 2018, and since the FCC’s Rules require that EAS Participants “are required to file detailed post-test data 45 days following a nationwide EAS test,” the Form 3 deadline will most likely move to November 19, 2018.  Those are just predictions, however, and broadcasters and other EAS Participants should watch for a formal announcement from the FCC with the new filing deadlines.

[Editor’s Note: Subsequent to publication, the FCC did in fact release a Public Notice confirming the October 3 deadline for Form 2, and the November 19 deadline for Form 3.]

Published on:

The FCC and FEMA have established September 20, 2018 as the date for the next nationwide test of the Emergency Alert System (EAS).  The nationwide test is designed to study the effectiveness of the EAS and to monitor the performance of EAS participants.  The Wireless Emergency Alert (WEA) system will be tested immediately prior to the test of the EAS.  The FCC and FEMA have designated October 3, 2018 as the back-up date should circumstances prevent testing on September 20.

While the test itself is a month away, all EAS participants must file their Form One with the FCC by August 27, 2018 in preparation for the test.  To make this filing, EAS participants must log in to the EAS Test Reporting System using an FCC Username Account.  Those filers who do not already have an account can register for one in the FCC’s updated CORES system.  Once a username account is set up, it will need to be associated with a licensee’s FCC Registration Number (FRN) before the user can draft or file forms for that licensee’s station(s).  Many filers struggled to successfully register in past years, but those who participated in the annual test in 2017 should already be registered.

Form One requests information about a station’s transmitter location, EAS equipment, and the stations it is assigned to monitor.  For most EAS participants, this information will prefill from last year’s Form One (so be particularly careful reviewing it if your monitoring assignments, equipment, or something else has changed since last year).  Stations will also see an instruction to file a separate Form One for each encoder, decoder or combination unit.  Most broadcasters will likely have a combination unit and therefore only need to file a single Form One.  However, there may be situations where multiple filings are needed, for example where a cluster of co-owned radio stations share a studio but have to employ separate encoders and decoders to deal with stations in the group having different monitoring assignments.

As in the past, after the test is completed, participants must report the results of the test by filing Form Two, which requests abbreviated “day of test” data, and then Form Three, which collects more detailed data about the station’s performance.

Filing Deadlines:

  • Form One must be filed on or before August 27, 2018.
  • Form Two (“day of test” data) must be filed by 11:59 PM (EDT) on September 20, 2018.
  • Form Three must be filed on or before November 5, 2018.

Additional Requirements

To prepare for the test, the FCC recommends that EAS participants review the EAS Operating Handbook and be sure that it is available at normal duty positions or EAS equipment locations, and is otherwise readily accessible to employees responsible for managing EAS actions.

Participants should also use this time to ensure their facilities are in a state of “operational readiness.”  Operators should confirm that their EAS equipment has any necessary software and firmware upgrades and that it is capable of receiving the various test codes.  If not automatic, operators must also manually set their EAS equipment to the “official time” as established by the National Institute of Standards and Technology.  Each of these issues has been a significant cause of stations being unable to receive or transmit past tests.

Finally, the person filing for each station should verify that they have the right username, password, and licensee FRN in advance of the filing deadline.  Experience from the the past two national tests revealed that many stations were caught off guard not by the test itself, but by their inability to access the ETRS to make required filings, often because of confusion surrounding how to log in.

Summer break notwithstanding, this is one test that broadcasters should study for ahead of time.

Published on:

Pillsbury’s communications lawyers have published FCC Enforcement Monitor monthly since 1999 to inform our clients of notable FCC enforcement actions against FCC license holders and others.  This month’s special issue takes a look at the government’s renewed efforts to scuttle Pirate Radio operations.

Since the government first began regulating the airwaves, it has struggled to eliminate unlicensed radio operators.  In its latest effort, the FCC is taking a hardline approach to this illegal behavior and is partnering with local and federal law enforcement, as well as Congress, to accomplish the task. While Chairman Pai has made clear that pirate radio prosecutions are once again a priority at the FCC, it is Commissioner O’Rielly who has been the most vocal on this front, calling for more aggressive action against unauthorized operators.  The continued prevalence of pirate radio operations has been chalked up to several factors, including insufficient enforcement mechanisms and resources, the procedural difficulties in tracking down unregulated parties, and lackadaisical enforcement until recently. Regulators and broadcast industry leaders have also expressed frustration with the whack-a-mole nature of pirate radio enforcement—shutting down one operation only to have another pop up nearby.

Real Consequences

Congress has also begun to take an interest in the issue, with the House Subcommittee on Communications and Technology holding a hearing last week discussing the subject.  One of the witnesses was David Donovan, president of the New York State Broadcasters Association.  In his testimony, he listed numerous risks that unlicensed operations present to the public, including failure to adhere to Emergency Alert System rules and RF emissions limits (which can be critically important where a pirate’s antenna is mounted on a residential structure).  Pirate operators also create interference to other communications systems, including those used for public safety operations, while causing financial harm to legitimate broadcast stations by diverting advertising revenue and listeners from authorized stations.

Despite these harms, pirate operations continue to spread.  This past month, the FCC issued a Notice of Unlicensed Operation (“NOUO”) to a New Jersey individual after the FCC received complaints from the Federal Aviation Administration (“FAA”) that an FM station’s broadcasts were causing harmful interference to aeronautical communications operating on air-to-ground frequencies.  FCC agents tracked the errant transmissions to the individual’s residence and confirmed that he was transmitting without authorization.

Days later, the FCC issued an NOUO to another New Jersey resident who was transmitting unlicensed broadcasts from a neighborhood near Newark Airport.  Once again, FCC agents were able to determine the source of the signal and found that the property owner was not licensed to broadcast on the frequency in question.

Continue reading →

Published on:

Yesterday’s enactment of the Consolidated Appropriations Act, 2018 (feel free to read it, it’s only 2,232 pages) was welcomed by broadcasters. If you’ve been following the trade press, you’ll know that’s largely because it not only added a billion dollars to the FCC’s fund for reimbursing broadcasters displaced by the spectrum repack, but for the first time made FM, LPTV and TV Translator stations eligible for repack reimbursement funds.

Continue reading →

Published on:

Earlier this week, the FCC and FEMA released a final reminder that this year’s nationwide test of the Emergency Alert System will occur today, September 27, 2017 at 2:20 PM Eastern Time.  The test will be transmitted in both English and Spanish and broadcasters will choose which one to air in their communities.

The agencies had reserved October 4th as a backup date for the test in the event that an emergency was ongoing that could lead to confusion around the test.  They decided not to fall back on that option despite Hurricanes Harvey, Irma and Maria recently causing much destruction.  They did, however, acknowledge the disruption those events caused by giving broadcasters in the affected areas additional time to meet their various filing obligations connected to the national EAS test.

Stations unaffected by the hurricanes must file a Form 2, the day-of-test reporting form, via the FCC’s Emergency Test Reporting System by 11:59 PM Eastern Time tonight (September 27).  Stations are allowed to make any corrections to their earlier-filed Form 1 submissions by that time as well.  More detailed information on a station’s performance during the test, including any issues encountered, must be submitted electronically on Form 3 no later than November 13, 2017.

As noted above, broadcasters in hurricane-affected areas (Florida, Puerto Rico and the U.S. Virgin Islands, as well as portions of Alabama, Georgia, Louisiana, and Texas) have more flexibility, and may make corrections to their Form 1, and file Form 2, as late as November 13, the national deadline for filing Form 3.

Unrelated to those Form 1, 2 and 3 filings, stations are also required to report to their State Emergency Communications Committee by November 6, 2017 any steps they have taken to distribute EAS content in languages other than English to their non-English speaking audiences.  While the FCC has not mandated the precise information to be reported, it has suggested that stations provide:

  • a description of the steps taken to make EAS content available to speakers of other languages;
  • a description of any plans made to do so in the future, along with an explanation of why or why not; and
  • any additional information that would be useful to the FCC, such as state-wide demographic information regarding languages spoken and resources used or needed to originate EAS content in languages other than English.

The State Emergency Communications Committees are then required to report this information to the FCC within six months.

This is the third nationwide EAS test, and as you would hope, each test seems to go better than the last one as bugs in the alerting chain and equipment are discovered and fixed.  While some might view it as contradictory, the twin hopes of everyone involved in today’s test is that we will eventually have a perfectly functioning national alerting system, and that it will never be needed.

Published on:

The FCC and FEMA have established September 27, 2017 as the date for the next nationwide test of the Emergency Alert System (EAS). Like last year’s test, all EAS participants must file Form 1 a month before the test.  The Form 1 has been modified, however, requiring information that was not requested previously.  In addition, the FCC’s Emergency Test Reporting System (ETRS) has been revamped so that prior log in codes do not work and the system’s functionality is now unfamiliar to prior users.  As a result, while the Form 1 is technically due next Monday, August 28th, anyone who has not yet started the filing process should begin immediately and aim to finish the process this week.

Abandoning the ETRS log in system from the prior test, the ETRS now relies on log in information from an entirely separate FCC database, the Commission Registration System (CORES). Therefore, the first step in filing the Form 1 in the ETRS is the rather unintuitive step of establishing an FCC Username and Password in the CORES.  While this step might be simple enough in and of itself, it is important to understand that the CORES system confers control of the licensee’s Federal Registration Number (FRN) on the first person to lay claim to it.

Many broadcasters only know the FRN as the number they have to frantically search for every September when paying their Annual Regulatory Fees. But the FRN and password are increasingly used as the log in for many of the FCC’s other filing systems such as the new Licensing Management System that TV stations use for most application filings, the Universal Licensing System which is the licensing system for stations’ wireless facilities like broadcast auxiliaries and business radios, the International Bureau’s filing system for stations’ earth station facilities, and even an alternate log in for the new Online Public Inspection File.  Therefore, every station owner should establish a CORES Username and Password or have their lawyer do so on their behalf, and then claim the role of “Admin” of their FRN, even if someone else will be making their ETRS filings.

Once the licensee has claimed the Admin role for the station’s FRN, the person making the ETRS filings for the station must establish a CORES Username and Password for themselves and request that the FRN Admin associate the licensee’s FRN with their account. Only once all those steps are complete will the person making the ETRS filings be able to even draft the Form 1.

To reach the Form 1, filers should log into the ETRS using their own CORES Username and Password. A message may appear at the top of the page upon logging in saying that no FRNs are associated with the account.  If you think you have in fact associated the FRN with the account, proceed with drafting the Form 1, as the FRN may appear in the pull down menu despite that message.

Information about the station’s transmitter location, EAS equipment, and stations monitored will prefill from the Form 1 filed for the last nationwide test. This year, stations must also provide the location of their EAS receivers.  The FCC is requesting this information to be able to map where signals are received and sent so that it can better understand any communications breakdowns.  Also new this year, stations will see an instruction to file a separate Form 1 for each encoder, decoder or combination unit.  It is likely that most broadcasters have a combination unit and therefore only need to file one Form 1.  However, there may be situations where multiple filings are needed, for example where a cluster of co-owned radio stations share a studio but have to employ separate encoders and decoders to deal with stations in the group having different monitoring assignments.

So if you were procrastinating before filing the Form 1, or tried and were stymied by the FCC’s updated filing system, it’s time to get moving. Monday’s deadline is coming fast.

Published on:

Pillsbury’s communications lawyers have published FCC Enforcement Monitor monthly since 1999 to inform our clients of notable FCC enforcement actions against FCC license holders and others.  This month’s issue includes:

Headlines:

  • FCC Proposes $66,000 Fine Against Alaska Noncommercial FM Station for EAS and Other Violations
  • Man Faces $120 Million Fine for “Massive” Robocall Operation
  • FCC Proposes $1,500 Fine Against South Carolina AM Station for Late-Filed License Renewal

Alaska Noncommercial FM Station Faces $66,000 Fine for EAS and Other Violations

The FCC proposed a $66,000 fine against an Alaska noncommercial FM station for a number of violations, including actions that the FCC says “undermine the effectiveness of the Emergency Alert System (EAS).”

Section 11.15 of the FCC’s Rules requires that a copy of the EAS Operating Handbook be located “at normal duty stations or EAS equipment locations when an operator is required to be on duty.” In addition, Section 11.35(a) of the Rules states that EAS participants are responsible for ensuring that EAS equipment, such as encoders and decoders, are installed such that “monitoring and transmitting functions are available during the times the stations and system are in operation.” Also, Section 11.52(d)(1) requires EAS participants to monitor two EAS sources.

A June 2013 FCC inspection of the station’s main studio revealed several violations of the FCC’s EAS Rules. Specifically, the FCC agent found that the station (1) did not have an EAS Handbook; (2) did not have properly operating EAS equipment (because the programming and identification of the station’s EAS device was for another station); and (3) was only monitoring one EAS source.

In addition, the agent found numerous violations of the FCC’s other broadcast rules, including: (1) failure to post a valid license as required by Section 73.1230; (2) failure to maintain a public inspection file as required by Section 73.3527; (3) failure to retain the logs required by Section 73.1840; (4) failure to maintain a main studio staff under Section 73.1125(a); (5) inability to produce documentation designating a chief operator as required by Section 73.1870; and (6) failure to ensure that the station was operating in accordance with the terms of the station authorization or within variances permitted under the FCC’s technical rules, as required by Section 73.1400.

The FCC subsequently issued a Notice of Violation (“NOV”) to the station in August 2013. When the FCC did not receive a response from the station within the 20-day deadline specified in the NOV, the FCC sent a Warning Letter to the station in September 2013, and issued two additional NOVs in November 2013 and April 2016 directing the station “to provide information concerning the apparent violations described in the August 2013 NOV.” Despite signing a receipt for the April 2016 NOV, the station again failed to respond.

The base fine amounts for the apparent EAS violations, broadcast violations, and failures to respond to the NOVs total $11,000, $23,000, and $16,000 respectively. The FCC may adjust a fine upward or downward after taking into account the particular facts of each case. Here, citing the station’s failure to respond to FCC documents of four occasions, the FCC concluded that a 100 percent upward adjustment of the base fine for the failures to respond, or an additional $16,000, was warranted. As a result, the FCC proposed a total fine against the station of $66,000.

FCC Proposes $120 Million Fine for Caller ID Spoofing Operation

A Florida man’s spoofing campaign has earned him a proposed $120 million fine. The man apparently caused the display of misleading or inaccurate caller ID information (“spoofing”) on millions of calls to perpetrate an illegal robocalling campaign.

The Truth in Caller ID Act of 2009, as codified in Section 227(e) of the Communications Act and Section 64.1604 of the FCC’s Rules, prohibits any person from knowingly causing, directly or indirectly, any caller ID service to transmit or display misleading or inaccurate caller ID information with the intent to defraud, cause harm, or wrongfully obtain anything of value. Continue reading →