WASHINGTON—The Federal Communications Commission should seek to minimize disruptions to TV viewers and FM radio listeners as it firms up how it will distribute the $1 billion additionally allocated by Congress to reimburse broadcasters for their channel relocation expenses, NAB said in comments filed Sept. 26 with the agency.
The comments, filed in reference to the FCC Notice of Proposed Rulemaking on reimbursement of repack-associated expenses to LPTV, TV Translator and FM radio stations, also pointed out the agency has no reason at the moment to think the additional funds won’t cover the expenses of “all eligible entities”
A key point in the filing centers on how Congress apportioned funding in its Reimbursement Expansion Act (REA), which passed in March. Of the $1 billion, Congress apportioned $600 million for FY 2018 and $400 million for FY 2019. The law caps FY 2018 spending at $600 million but does not restrict how the $400 million FY 2019 funds are allocated.
“At the outset, the plain language of the REA includes no limitations on how to allocate FY 2019 funds, in stark contrast to the express limitations for FY 2018 funds,” NAB said in the filing. The association told the commission that the language of the act “confirms that FY 2019 funds may supplement the funding levels made available in 2018.”
The NPRM sought comment on whether or not, and if so, how, reimbursement payments from FY 2019 funds should be prioritized. NAB urged the FCC only to prioritize funding if the facts prove doing so is needed. That will only become clear once FM and LPTV stations submit their cost estimates, NAB said.
“The Commission presently has no reason to believe that the $1 billion Congress appropriated will prove inadequate to reimburse all eligible entities for expenses associated with repacking and a limited basis, if any, for guessing where shortfalls are likely to arise. The Commission may have sufficient funds available to reimburse all eligible entities for expenses incurred during repacking, meaning that any prioritization at this point could prove unnecessary,” NAB said.
The FCC has a statutory deadline of Mach 23, 2019, to put in place rules for reimbursing FM and LPTV stations. Shortly after that, FM and LPTV stations will submit their estimates, and TV stations and MVPDs will have provided updated information on their repack expenses. Only then will the agency know if there won’t be adequate funds, how big the shortfall will be and how to prioritize payments, the association said. “Waiting to see whether prioritizing reimbursement will be necessary is the most reasonable approach,” the filing said.
However, if the commission insists on prioritizing payments, NAB offered its desired approach. First, allocate funds as soon as possible to make sure FM stations receive 80 percent of actual or estimated costs and that at least $50 million specified in FY2018 funds is allocated to FM stations; second, fully reimburse full-power and Class A TV stations being involuntarily repacked; third –if funds are available—fully reimburse FM radio stations impacted in the repack; and fourth, “use remaining funds to reimburse displaced LPTV stations and translators for any costs exceeding $150 million [which Congress set aside to cover their relocation expenses].”
(A separate filing this week from the National Translator Association places the estimated relocation expenses of LPTV and TV Translator stations at about $77 million.)
The filing is available online.
For a comprehensive list of TV Technology’s ATSC 3.0 coverage, see our ATSC3 silo.
Phil Kurz is a contributing editor to TV Tech. He has written about TV and video technology for more than 30 years and served as editor of three leading industry magazines. He earned a Bachelor of Journalism and a Master’s Degree in Journalism from the University of Missouri-Columbia School of Journalism.
Future US's leading brands bring the most important, up-to-date information right to your inbox
Thank you for signing up to TV Tech. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.