<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
<title>tower light outage - Broadcast Law Blog</title>
<link>http://www.broadcastlawblog.com/articles/tower-issues/</link>
<description></description>
<language>en-us</language>
<copyright>Copyright 2013</copyright>
<lastBuildDate>Wed, 08 May 2013 09:04:08 -0500</lastBuildDate>
<pubDate>Wed, 08 May 2013 14:17:49 -0500</pubDate>
<generator>http://www.movabletype.org/?v=3.34</generator>
<docs>http://blogs.law.harvard.edu/tech/rss</docs> 

<item>
<title>FCC Fines Up to $25,000 for Tower Issues Including Lighting and Painting Issues, Inadequate Fencing, Tower Registration in Wrong Name and No Posted ASRN</title>
<description><![CDATA[<p>Failing to <strong>properly maintain a communications tower </strong>can be expensive, as a number of FCC decisions released in the last few days demonstrate.&nbsp;In several decisions reached in the last week, the Commission faulted tower owners for all sorts of problems &ndash; tower lights being out without letting the FAA know, faded paint, missing fencing around an AM tower, tower registrations that had not been updated after a sale, and the failure to post the tower <strong>Antenna Survey Registration Number (&ldquo;ASRN&rdquo;) </strong>at the base of the tower so that the FCC could identify the tower owner.&nbsp;These cases provide a survey of the many issues that tower owners can have &ndash; ones that can bring big FCC fines.</p>
<p>In <a href="http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-13-984A1.pdf"><font color="#0563c1">the case with the largest proposed fine</font></a> - $25,000 &ndash; the FCC faulted a tower owner for having a tower with <strong>faded paint and no posted ASRN </strong>that was visible at the base of the tower.&nbsp;In addition, the <strong>FCC tower registration had not been updated to reflect the name of the current tower owner </strong>&ndash; even though the owner had bought the tower 10 years before.&nbsp;After an FCC inspection identifying the issues, the licensee promised that they would be remedied.&nbsp;But, according to the decision, two more inspections were made by FCC inspectors within 15 months of the first inspection, and the problems all remained.&nbsp;The failure to correct the errors after being repeatedly warned brought about a $10,000&nbsp;increase in the fine from what would be normally warrant a penalty of approximately $15,000.&nbsp;Clearly, if the FCC tells you something is wrong &ndash; fix it, or face increased liability for the problems.&nbsp;The FCC does not like to be ignored.</p>]]><![CDATA[<p>A $7000 fine was imposed on a tower owner in <a href="http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-13-982A1.pdf"><font color="#0563c1">another case</font></a>, where the FCC found&nbsp;three AM towers, two without fences at all, and one with fences in bad condition that allowed easy access to the tower. While the owner claimed that there was a local flood that <strong>damaged the fences</strong>, the FCC said that there was no evidence at the site of any recent flood, and even if a flood had damaged the one fence, it didn&rsquo;t see how the fences around the other two towers would have entirely disappeared. The FCC also rejected arguments that the site was not accessible to the public as there was a steep cliff on one side of the towers, and water on the other.&nbsp;The FCC noted that, while these obstructions were on the sides of the towers, the FCC inspector had no trouble driving up to the towers from the front. Plus, even if there was a gate blocking that access (as claimed by the owner, but not found by the FCC inspector), the fact that the site could be accessed by boat made is sufficiently accessible that a fence should surround areas of high RF radiation.</p>
<p>Another $<a href="http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-13-971A1.pdf"><font color="#0563c1">7000 fine was proposed for another AM licensee</font></a> where the FCC found the <strong>fence&nbsp;around the transmission tower&nbsp;to have fallen in one section</strong>. Even though the licensee claimed that it had been damaged and temporarily repaired about 3 months before, as the temporary repairs had not lasted, the FCC did not excuse the violation. The FCC also rejected an argument that a larger perimeter fence obviated the need for the fence around the base of the tower. Had that outer fence secured the property, that might have been sufficient, but the FCC found the outer fence to have an unlocked, open gate, and at least one section of that fence had also had fallen, allowing easy access.</p>
<p>In a <a href="http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-13-1005A1.pdf"><font color="#0563c1">fourth decision</font></a>, the FCC fined a tower owner <strong>$10,000 for having the top light out on its tower</strong>, and <strong>not promptly notifying the FAA of the light being out</strong>. The FCC rules require that the FAA be notified whenever lights are out for more than 30 minutes. Here, the FCC found the lights out in mid-August, notified the owner of the issue, which the owner repaired at the end of September. But, according to the decision, the FAA was not notified about the issue until after the repairs had been made.</p>
<p>Four decisions and almost $50,000 in fines. Tower issues are among the issues of most concern to the FCC, given the potential for personal injury and the threats to public safety. These issues are not new - we <a href="http://www.broadcastlawblog.com/2013/03/articles/fcc-fines/14000-fcc-fine-for-tower-violations-obstruction-light-out-no-faa-notification-and-failure-to-update-antenna-survey-registration-to-report-new-owner/#more">wrote about a number of similar decisions just a few months ago</a>.&nbsp; Keep those tower sites fenced, lights lit, towers painted and identified, and their ownership properly registered or face big fines from the FCC.</p>]]></description>
<link>http://www.broadcastlawblog.com/2013/05/articles/tower-issues/fcc-fines-up-to-25000-for-tower-issues-including-lighting-and-painting-issues-inadequate-fencing-tower-registration-in-wrong-name-and-no-posted-asrn/</link>
<guid isPermaLink="false">http://www.broadcastlawblog.com/2013/05/articles/tower-issues/fcc-fines-up-to-25000-for-tower-issues-including-lighting-and-painting-issues-inadequate-fencing-tower-registration-in-wrong-name-and-no-posted-asrn/</guid>
<category>FCC Fines</category><category>Tower Issues</category><category>antenna structure registration</category><category>tower fencing requirements</category><category>tower light outage</category><category>tower painting</category>
<pubDate>Wed, 08 May 2013 09:04:08 -0500</pubDate>
<dc:creator>David Oxenford</dc:creator>

</item>
<item>
<title>$11,000 Fine for Broadcast Station Tower Light Outage - FCC Emphasizes the Responsibility of Licensee To Maintain Lights if Tower Owner Does Not</title>
<description><![CDATA[<p>Fines for broadcast station tower owners who fail to maintain the required lighting on their tower are not unusual.&nbsp;But in <a href="http://transition.fcc.gov/Daily_Releases/Daily_Business/2013/db0425/FCC-13-56A1.pdf">a decision last week</a>, the FCC made clear that, <strong>even if the licensee of a broadcast station is not the tower owner, it still has the responsibility for dealing with tower lights that are out, even if the tower owner does not</strong>.&nbsp;The failure of the licensee to maintain the tower lights, and other related issues, resulted in an $11,000 fine issued by the FCC.</p>
<p>The case was unusual in that the broadcast licensee, and the company from which it bought the station, were arguing over who owned the tower &ndash; not contending that the each owned the tower, but instead each pointing to the other as the one with the responsibility for the maintenance of the tower.&nbsp;The former owner of the station maintained ownership of the underlying land, but claimed that the tower was conveyed to the new station owner.&nbsp;The licensee claimed that the tower was still owned by the former owner, and that former owner should be responsible for the tower lights.&nbsp;The FCC reviewed the contract between the two parties, seemed to conclude that the licensee had in fact acquired the tower, but said that the&nbsp;final determination&nbsp;on that issue was one&nbsp;for local courts, not the&nbsp;FCC.&nbsp; But even if the licensee did not own the tower, it still had the responsibility for the tower as licensees have the responsibility to insure that the tower lighting requirements in their licenses are met.&nbsp;This obligation is set out in Section 17.6 of the Commission's rules and in various policy statements.&nbsp; Thus, no matter who owned the tower, the licensee was still subject to the fine for the lights not being operational.</p>]]><![CDATA[<p>As set forth in this decision, if the lights go out, the FAA must be notified of the outage, which was not done here. And attempts to fix the problem must be made. Here, while there was the dispute over the ownership of the tower, the FCC found that the licensee made no attempts to fix the issue or notify the FAA or the FCC, even though it appeared to have control over the tower &ndash; whether or not it actually owned it.</p>
<p>Clearly, licensees need to take note. If the required lights are out on their towers, and the owner of the tower refuses to take the required actions, the licensee must step in and do what it needed to be in compliance or, on top of any other liability that may attach, the FCC is liable to take action. <strong>Section 17.6 of the FCC's rules </strong>requires that the licensee notify the tower owner if the licensee believes that painting or lighting requirements are not being met.&nbsp; If such a step does not result in a resolution of the problem, the licensee must notify the FCC and take such steps as it can to get the tower into complaince.&nbsp; Such an eventuality should also be taken into account in any tower lease agreement, requiring that the owner do what is necessary, but noting that the licensee can act (and perhaps set off costs against its lease obligations) if the owner does not do what it required. Something to think about if you are operating a broadcast station from a tower that you do not own.</p>]]></description>
<link>http://www.broadcastlawblog.com/2013/04/articles/fcc-fines/11000-fine-for-broadcast-station-tower-light-outage-fcc-emphasizes-the-responsibility-of-licensee-to-maintain-lights-if-tower-owner-does-not/</link>
<guid isPermaLink="false">http://www.broadcastlawblog.com/2013/04/articles/fcc-fines/11000-fine-for-broadcast-station-tower-light-outage-fcc-emphasizes-the-responsibility-of-licensee-to-maintain-lights-if-tower-owner-does-not/</guid>
<category>FCC Fines</category><category>Tower Issues</category><category>responsibility for tower maintenance</category><category>tower lease agreement</category><category>tower light outage</category>
<pubDate>Mon, 29 Apr 2013 10:19:27 -0500</pubDate>
<dc:creator>David Oxenford</dc:creator>

</item>
<item>
<title>Monitor Required Tower Lighting - FCC Proposes $17,000 Fine for Violations</title>
<description><![CDATA[<p>Communications&nbsp;<strong>towers that are not lit as required often bring big fines </strong>from the FCC.&nbsp; In two decisions released today, the Commission followed that precedent. &nbsp;In <a href="http://transition.fcc.gov/Daily_Releases/Daily_Business/2012/db0404/DA-12-535A1.pdf">one case, the FCC proposed a&nbsp;fine of $17,000 to&nbsp;a tower owner</a> after repeated promises to fix lights that were out did not result in any resolution of the issue after 2 years (problems which, according to the FCC decision, were first brought to the tower owner's attention by the FCC).&nbsp; The FCC's order also said that the tower owner stated that its protocol was to examine the status of the tower lights quarterly, even though the FCC's rules (Section 17.47(a)) require that there be a direct visual check, or a check of an authorized monitoring system, every 24 hours.&nbsp; The owner was also required to report to the FCC, within 30 days, stating&nbsp;that that the required lights were back on or with a specific timetable for doing so.&nbsp;</p>
<p>In a <a href="http://transition.fcc.gov/Daily_Releases/Daily_Business/2012/db0404/DA-12-533A1.pdf">second&nbsp;case</a>, the FCC proposed a&nbsp;fine&nbsp;to&nbsp;the same company for&nbsp;$15,000 for perceived issues at another tower, and indicated that they thought that there might be a systematic problem with the company's practices - ordering the company to report to the FCC on the compliance status of all of its towers.&nbsp; These decisions are indicative of how seriously the FCC considers its tower lighting and monitoring rules, given their potential impact on public safety.&nbsp; So remember to check your tower lights daily,&nbsp;report outages to the FAA when they occur, and promptly fix any problems that may exist.&nbsp;</p>]]></description>
<link>http://www.broadcastlawblog.com/2012/04/articles/tower-issues/monitor-required-tower-lighting-fcc-proposes-17000-fine-for-violations/</link>
<guid isPermaLink="false">http://www.broadcastlawblog.com/2012/04/articles/tower-issues/monitor-required-tower-lighting-fcc-proposes-17000-fine-for-violations/</guid>
<category>FCC Fines</category><category>Tower Issues</category><category>tower light outage</category><category>tower lighting requirements</category>
<pubDate>Thu, 05 Apr 2012 14:28:46 -0500</pubDate>
<dc:creator>David Oxenford</dc:creator>

</item>
<item>
<title>A Host of FCC Fines of Over $20,000 for Technical and Tower Issues - And a Presentation on How to Avoid FCC Problems to the Kansas Broadcasters</title>
<description><![CDATA[<p>Last week, I did a presentation on the issues facing broadcasters at&nbsp;the <strong>Kansas Association of Broadcasters</strong> annual convention (a copy of the slides from my presentation is available <a href="http://www.dwt.com/portalresource/10-11_OxenfordKansasCon">here</a>).&nbsp; I spoke about some of the day-to-day issues that can get broadcasters into trouble, as well as some of the big policy issues that broadcasters need to consider.&nbsp; My presentation was preceded by a session conducted by the agent in charge of the Kansas City field office of the FCC, who emphasized the many issues that the field agents discover at broadcast stations that can lead to fines.&nbsp; In the week since I returned from Kansas, it seems like the FCC has wanted to demonstrate the examples given by their agent, as there have been a large number of fines demonstrating the breadth of technical issues that broadcasters can face.&nbsp;&nbsp;Fines (or &quot;forfeitures&quot;, as the FCC calls them) were issued or proposed&nbsp;for issues ranging from faded tower paint, tower light outages, EAS problems, operations with excess power, and the ubiquitous (and very costly) public file violations.&nbsp; Fines of up to $25,000 were issued for these violations - demonstrating how important it is not to overlook the day-to-day compliance matters highlighted in my presentation.</p>
<p>The largest of these fines was for $25,000.&nbsp; <a href="http://transition.fcc.gov/Daily_Releases/Daily_Business/2011/db1102/DA-11-1822A1.pdf">This fine </a>was imposed on a station for failing to have operational <strong>EAS equipment</strong>, not having an <strong>enclosed&nbsp;fence around the antenna site</strong>, and a <strong>missing public file</strong>.&nbsp; The fine was originally proposed in a <strong>Notice of Apparent Liability </strong>(the first step in imposing an FCC&nbsp;fine, when the FCC spells out the&nbsp;apparent violation and the fine proposed, and the licensee is given time to respond to the allegations), released&nbsp;in July (see our post <a href="http://www.broadcastlawblog.com/2011/07/articles/fcc-fines/25000-fine-for-unlocked-tower-fence-and-missing-eas-receiver-and-public-file/">here</a>).&nbsp; The licensee failed to respond to the Notice of Apparent Liability, thus the fine is now being officially imposed.</p>]]><![CDATA[<p>In <a href="http://transition.fcc.gov/Daily_Releases/Daily_Business/2011/db1101/DA-11-1825A1.pdf">another case</a>, a tower owner was fined $3750 for failing to have operating lights on a tower, and failing to notify the FAA that the lights were not working.&nbsp; The fine was imposed even though the tower no longer had any communications antennas mounted on it,&nbsp;the tower was scheduled for demolition, and the owners were elderly and in poor health.&nbsp; The FCC reminded tower owners that they must observe all lighting requirements even if no licensees were using the tower for as long as the tower is standing.&nbsp; A $10,000 fine was proposed in <a href="http://transition.fcc.gov/Daily_Releases/Daily_Business/2011/db1101/DA-11-1828A1.pdf">another case&nbsp;</a>for a North Carolina station that did not have operating tower lights, and did not have a system in place to monitor the lights.&nbsp; In both cases, the FAA was apparently not notified immediately upon the tower lights failing.</p>
<p>These tower owners were not the only tower owners to get into trouble.&nbsp; The Commission <a href="http://transition.fcc.gov/Daily_Releases/Daily_Business/2011/db1031/DA-11-1802A1.pdf">issued a Notice of Apparent Liability </a>for $20,000 to another&nbsp;tower owner in Atlantic City NJ who had&nbsp;a tower that had faded paint, lights that were not operational, and an open gate in the fence surrounding the base of the tower.&nbsp; The FCC inspected the tower several times, notified the owner of the issues, and was promised that the lights would be fixed by a given date.&nbsp; But, upon revisiting the site well after the promised date, the lights were still out and the paint was still faded. Thus, the fine was upped from the&nbsp;$17,000 that would be suggested by the FCC's schedule of routine amounts for fines, to the announced amount of $20,000.&nbsp; Obviously, if you make a promise to the FCC that you are going to fix a problem, keep it.</p>
<p>But keeping track of who owns a tower is also important, as a $3000 fine was proposed for a tower owner in California.&nbsp; The FCC visited the tower, and contacted the owner listed in the FCC&nbsp;tower registration records (when registering, tower owners are given an <strong>Antenna Structure Registration </strong>of ASR number).&nbsp; That owner&nbsp;told the Commission that the tower had been sold years before - with the Buyer apparently never bothering to update the tower registration at the FCC. &nbsp;As we have <a href="http://www.broadcastlawblog.com/2011/06/articles/tower-issues/buy-a-station-recently-make-sure-your-tower-registration-is-updated-fcc-fines-broadcaster-3000-for-not-doing-so/">warned before</a>, the <strong>FCC&nbsp;tower registration is not automatically updated when the&nbsp;sale of a broadcast station is approved by the FCC</strong>.&nbsp; A buyer must proactively go to the FCC and file a separate form&nbsp;to change the owner in the FCC tower registration database.&nbsp; If you don't update the tower registration, and a problem arises at your site where the FCC needs to find the tower owner, you may be looking at a&nbsp;fine.</p>
<p>While operating your tower in compliance with the rules is important, so is <strong>operating at the right power</strong>.&nbsp; Fines for overpower operations, especially on AM stations that have to switch power levels or directional patterns at sundown, seem common, including fines of $4000&nbsp;in cases reported <a href="http://transition.fcc.gov/Daily_Releases/Daily_Business/2011/db1025/DA-11-1779A1.pdf">here</a> and <a href="http://transition.fcc.gov/Daily_Releases/Daily_Business/2011/db1020/DA-11-1737A1.pdf">here</a>.&nbsp; Especially at this time of year, on Friday nights with high school football games going on after dark, and sundown coming earlier and earlier, stations may be inclined to cheat.&nbsp; But if you get caught, you are looking at fines - and you have built in enforcers in competing stations who don't want you to get the competitive advantage of an overpower operation.</p>
<p>Moving a station without approval can also be costly - as shown by the <a href="http://transition.fcc.gov/Daily_Releases/Daily_Business/2011/db1024/DA-11-1755A1.pdf">case here</a>.&nbsp; The Commission is proposing a $22,000 fine for a station operating from a site not authorized in its license (even small moves require FCC approval), and not having an operating EAS system or a complete public file.&nbsp;</p>
<p>This host of fines demonstrates that the FCC is very serious about the technical operations of broadcast stations.&nbsp; Seemingly little issues can result in big fines - so pay attention to details and save yourself a few dollars.&nbsp;</p>]]></description>
<link>http://www.broadcastlawblog.com/2011/11/articles/fcc-fines/a-host-of-fcc-fines-of-over-20000-for-technical-and-tower-issues-and-a-presentation-on-how-to-avoid-fcc-problems-to-the-kansas-broadcasters/</link>
<guid isPermaLink="false">http://www.broadcastlawblog.com/2011/11/articles/fcc-fines/a-host-of-fcc-fines-of-over-20000-for-technical-and-tower-issues-and-a-presentation-on-how-to-avoid-fcc-problems-to-the-kansas-broadcasters/</guid>
<category>FCC Fines</category><category>Kansas Association of broadcasters</category><category>Tower Issues</category><category>antenna structure registration</category><category>notice of apparent liability</category><category>tower fencing requirements</category><category>tower light outage</category><category>tower lighting requirements</category><category>tower painting</category><category>tower registration</category>
<pubDate>Fri, 04 Nov 2011 10:01:32 -0500</pubDate>
<dc:creator>David Oxenford</dc:creator>

</item>
<item>
<title>How Much Will Tower Lighting and Painting Issues Cost You in FCC Fines?  $10,000 According to Recent Case</title>
<description><![CDATA[<p><strong>FCC tower lighting and marking violations </strong>are among those treated most seriously by the FCC, given their potential for tragedy should there be an incident with an aircraft due to improper tower maintenance.&nbsp; Today, in two Notices of Apparent liability, the FCC proposed fines against&nbsp;tower owners for such violations. &nbsp;In <a href="http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-11-263A1.pdf">one case</a>, where the lights were apparently not functioning and the FAA had not been notified of the outage as required, the proposed fine is $10,000.&nbsp; In that case, the FCC cited the owner for failing&nbsp;to observe the&nbsp;lighting and painting requirements, and&nbsp;not observing the tower to determine if the lights were operational, and not having an&nbsp;automatic monitoring system to check on those lights (see our post <a href="http://www.broadcastlawblog.com/2010/11/articles/tower-issues/fcc-decisions-making-the-life-of-a-tower-owner-easier-easing-approval-for-automatic-monitoring-and-making-clear-that-rf-radiation-standards-are-not-arbitrary/">here</a> about how the FCC allows such systems to, in many cases, substitute for routine visual monitoring).&nbsp;&nbsp;In a <a href="http://www.fcc.gov/Daily_Releases/Daily_Business/2011/db0214/DA-11-264A1.pdf">second case</a>, where the issue was only with the painting of the tower, the fine was $4000.&nbsp; In either case, these fines are significant, and serve as a reminder to tower owners to observe the mandatory tower painting and lighting requirements attached to their communications tower.&nbsp; Remember, FCC fines pale in comparison to potential liability if the failure to observe the marking requirements lead to some more serious incident.&nbsp;</p>]]></description>
<link>http://www.broadcastlawblog.com/2011/02/articles/tower-issues/how-much-will-tower-lighting-and-painting-issues-cost-you-in-fcc-fines-10000-according-to-recent-case/</link>
<guid isPermaLink="false">http://www.broadcastlawblog.com/2011/02/articles/tower-issues/how-much-will-tower-lighting-and-painting-issues-cost-you-in-fcc-fines-10000-according-to-recent-case/</guid>
<category>FCC Fines</category><category>Tower Issues</category><category>automatic monitoring of towers</category><category>tower light outage</category><category>tower lighting requirements</category><category>tower lights</category><category>tower painting</category>
<pubDate>Mon, 14 Feb 2011 14:02:37 -0500</pubDate>
<dc:creator>David Oxenford</dc:creator>

</item>
<item>
<title>FCC Fines for No EAS Equipment, Unreported Tower Light Outage, and No Posting of ASR</title>
<description><![CDATA[<p>In two separate Orders today, the FCC&nbsp;issued monetary forfeitures against a cable operator for failure to install <strong>Emergency Alert System (EAS)&nbsp;equipment </strong>and for&nbsp;<strong>various tower violations</strong>.&nbsp; These same violations could have been cited against a broadcaster, so these cases are instructive to both broadcasters and cable operators.&nbsp; The FCC issued monetary forfeitures of <a href="http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-10-633A1.pdf">$20,000 </a>and <a href="http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-10-632A1.pdf">$18,000 </a>against two Texas&nbsp;cable systems owned by the same company.&nbsp; In both cases, the cable operator <strong>failed to install EAS equipment</strong>, <strong>failed to notify the FAA&nbsp;of a tower&nbsp;lighting outage</strong> and<strong> failed to&nbsp;exhibit red obstruction tower lighting from sunset to sunrise</strong>.&nbsp;&nbsp;&nbsp;The higher fine related to a system's <strong>failure to display a tower's&nbsp;Antenna Structure Registration (ASR) number </strong>&quot;in a conspicuous place so that it is readily visible near the base of the antenna structure.&quot;&nbsp;&nbsp;</p>
<p>These same requirements apply equally to broadcast stations that have their own towers.&nbsp;&nbsp;&nbsp;While most broadcasters&nbsp;are aware&nbsp;of the requirement to maintain working EAS&nbsp;equipment, many may not know that&nbsp; FCC&nbsp;rules require a tower's&nbsp;ASR to be conspicuously displayed at the base of the tower.&nbsp;&nbsp;To be compliant, the ASR&nbsp;must be displayed on a&nbsp;weather-resistant surface and of sufficient size to be easily seen at the base of the tower.</p>]]><![CDATA[<p>Similarly, if tower lighting is required, FCC&nbsp;rules require that any outage be reported &quot;immediately&quot;&nbsp;to the FAA&nbsp;if it cannot be fixed within 30 minutes.&nbsp; Red obstruction lighting is required to be operational from sunset to sunrise, while high and medium intensity obstruction lighting is required to be operational 24 hours a day.</p>
<p>These are important issues to which both&nbsp;broadcasters and cable operators need to stay alert to avoid big fines like those imposed here.&nbsp; As they potentially involve matters of public safety, the FCC is not likely to be forgiving in the event of violations.&nbsp;&nbsp;&nbsp;</p>]]></description>
<link>http://www.broadcastlawblog.com/2010/04/articles/fcc-fines/fcc-fines-for-no-eas-equipment-unreported-tower-light-outage-and-no-posting-of-asr/</link>
<guid isPermaLink="false">http://www.broadcastlawblog.com/2010/04/articles/fcc-fines/fcc-fines-for-no-eas-equipment-unreported-tower-light-outage-and-no-posting-of-asr/</guid>
<category>ASR posting</category><category>EAS receivers</category><category>Emergency Communications</category><category>FAA hazard lighting</category><category>FCC Fines</category><category>Tower Issues</category><category>antenna structure registration</category><category>obstruction lights</category><category>reporting outage of tower lights to FAA</category><category>tower light outage</category>
<pubDate>Fri, 16 Apr 2010 11:40:42 -0500</pubDate>
<dc:creator>David Silverman</dc:creator>

</item>
<item>
<title>Tower Lights Out for Even One Day? - Pay A Fine, Says the FCC</title>
<description><![CDATA[<p>In a <a href="http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-10-90A1.pdf">recent decision</a>, the FCC's Enforcement Bureau&nbsp;ruled that a tower owner should pay a fine for&nbsp;a single day where the <strong>required tower lights&nbsp;were not operational</strong>, and where no <strong>required monitoring of the tower</strong> to discover such outage was taking place.&nbsp; On top of the penalty for the non-working lights, the FCC also fined the owner for the <strong>failure to report a change in ownership of the tower</strong>.&nbsp; The total fine in the case was $4000 (reduced from an initial fine of $13,000 because of the tower owner's past record of compliance).</p>
<p>As with any FCC fine, while the fine was for one day of tower light outage, there was more to the story.&nbsp; The FCC inspected the tower after receiving a complaint stating that the lights were out on a day that was almost&nbsp;a month before the inspection - indicating that the outage may have been in place for far longer than the one day revealed by the FCC inspection.&nbsp; The tower owner admitted that the person who was supposed to conduct the <strong>required daily inspection </strong>of the tower lights had moved from the area in which the tower was located, and the owner did not know&nbsp;exactly when that occurred.&nbsp; The owner did not get someone new to do the inspection until after the FCC inspection.&nbsp;&nbsp;And the tower had no automatic monitoring system to&nbsp;determine if the lights were in fact operational.&nbsp; With these admissions, it seemed clear that there was the potential that there had been a problem for a long time,&nbsp;so perhaps the fine was not unexpected, even though the lights were&nbsp;fixed within hours of the FCC report of the problem, as the issue was a&nbsp;simple one that the tower&nbsp;owner&nbsp;blamed on a careless repair person who had recently visited the site.</p>]]><![CDATA[<p>In addition, the original complaint indicated that the complainant could not reach the owner listed on the tower registration to notify them of the outage.&nbsp; After the FCC inspection, it became clear that this&nbsp;was because the ownership had changed, and the FCC had not been notified.&nbsp; Had the <strong>FCC tower registration</strong> information been timely updated&nbsp;when the ownership change occurred, the fine for the unreported change in ownership would not have been issued, and the fine for the light outage might also have been avoided if the owner had been able to respond to the private party's notification instead of having to wait for the FCC to get involved.</p>
<p>As we have <a href="http://www.broadcastlawblog.com/2008/12/articles/tower-issues/fcc-fines-tower-owner-for-failure-to-monitor-lighting-when-automatic-monitoring-equipment-did-not-give-notice-of-problem/">written before</a>, the FCC takes tower issues very seriously, because of the potential threat to safety posed by improperly lit towers.&nbsp; Tower owners need to take this issue very seriously themselves, not only because of the threat of FCC fines, but because of the potential exposure to civil liability&nbsp;should there be an aeronautical accident when the lights are out.&nbsp; If there are lighting problems, they need to be fixed immediately.&nbsp; If they cannot, the FAA needs to be notified so that it can alert airmen to the potential hazard.&nbsp; So inspect those towers regularly, and make sure that issues are promptly reported and corrected when they arise.&nbsp;</p>]]></description>
<link>http://www.broadcastlawblog.com/2010/01/articles/tower-issues/tower-lights-out-for-even-one-day-pay-a-fine-says-the-fcc/</link>
<guid isPermaLink="false">http://www.broadcastlawblog.com/2010/01/articles/tower-issues/tower-lights-out-for-even-one-day-pay-a-fine-says-the-fcc/</guid>
<category>FAA hazard lighting</category><category>FCC Fines</category><category>FCC tower lighting requirements</category><category>FCC tower lighting rules</category><category>FCC tower registration</category><category>Tower Issues</category><category>broadcasting&quot;</category><category>of</category><category>ownership</category><category>tower </category><category>tower light outage</category>
<pubDate>Wed, 20 Jan 2010 22:46:57 -0500</pubDate>
<dc:creator>David Oxenford</dc:creator>

</item>


</channel>
</rss>