FCC Web Documents citing 76.1708

as compiled by hallikainen.com/FccRules on 2012 07 01

• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-01-2818A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-01-2818A1.txt
  • §§ 76.1700 (Records to be Maintained Locally By Cable System Operators), 76.1701 (Political File) and 76.1710 (Operator Interests in Video Programming). San Francisco, CA District Office (10/3/01). Mediacom, Excelsior Springs, MO. Kansas City, MO District Office (10/9/01). Charter Communications, Picayune, MS. New Orleans, LA District Office (10/11/01). Charter Communications, Columbia, MS. Other violations: 47 C.F.R. §§ 76.1701 (Political File) and 76.1708 (Principal Headend). New Orleans, LA District Office (10/12/01). Charter Communications VI LLC, St. Louis, MO. Dallas, TX District Office (10/17/01). AT&T Broadband and Internet Services, Tooele & Grantsville, UT (Physical System #008436). Denver, CO District Office (10/23/01). AT&T Broadband & Internet Services, Heber City and Midway, UT (Physical System #010042). Denver, CO District Office (10/23/01). AT&T Broadband & Internet Services,
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-01-2818A2.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-01-2818A2.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-01-2818A2.txt
  • §§ 76.1700 (Records to be Maintained Locally By Cable System Operators), 76.1701 (Political File) and 76.1710 (Operator Interests in Video Programming). San Francisco, CA District Office (10/3/01). Mediacom, Excelsior Springs, MO. Kansas City, MO District Office (10/9/01). Charter Communications, Picayune, MS. New Orleans, LA District Office (10/11/01). Charter Communications, Columbia, MS. Other violations: 47 C.F.R. §§ 76.1701 (Political File) and 76.1708 (Principal Headend). New Orleans, LA District Office (10/12/01). Charter Communications VI LLC, St. Louis, MO. Dallas, TX District Office (10/17/01). AT&T Broadband and Internet Services, Tooele & Grantsville, UT (Physical System #008436). Denver, CO District Office (10/23/01). AT&T Broadband & Internet Services, Heber City and Midway, UT (Physical System #010042). Denver, CO District Office (10/23/01). AT&T Broadband & Internet Services,
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-02-724A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-02-724A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-02-724A1.txt
  • Office (2/28/02). Public Radio, Inc., Holly Hill, FL. Tampa, FL District Office (2/28/02). 47 C.F.R. § 11.61 - Tests of EAS Procedures Charter Communications, Coos Bay, Oregon. Portland, OR Resident Agent Office (2/12/02). Service Electric Cable, Allentown, PA. Other violations: 47 C.F.R. §§ 17.4(g) (Posting of Antenna Structure Registration Number), 17.47 (Inspection of Antenna Structure Lights and Associated Control Equipment), 76.1708 (Principal Headend), 76.1709 (Availability of Signals) and 76.1711 (Emergency Alert System (EAS) Tests and Activation). Philadelphia, PA District Office (2/14/02). Urban Cableworks of Philadelphia, Philadelphia, PA. Philadelphia, PA District Office (2/14/02). Capstar TX Limited Partnership, WKCY, Harrisonburg, VA. Other violation: 47 C.F.R. § 73.1870 (Chief Operator). Columbia, MD District Office (2/26/02). Capstar TX Limited Partnership, WKCY-FM, Harrisonburg, VA. Other violation:
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-03-80A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-03-80A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-03-80A1.txt
  • 76.55(d) of the Commission's rules. First, Charter maintains that the distance between the Station and Charter's principal headend located in Jackson, Tennessee exceeds the statutorily mandated 35-mile limit for a qualified LPTV station. Charter asserts that its Jackson headend, which has served the cable communities since July 2001, was designated as its ``principal headend'' in accordance with Sections 76.5(pp) and 76.1708 of the Commission's rules. Charter asserts it collapsed its headends for legitimate business and engineering purposes, and not to avoid carrying WDYR. Second, Charter contends that WDYR does not broadcast ``programming that would address local news and informational needs'' as required by Section 76.55 of the Commission's rules because WDYR's programming is used by other Tri-State Christian TV, Inc. stations
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-11-1333A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-11-1333A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-11-1333A1.txt
  • 544, 544a, 545, 548, 549, 552, 554, 556, 558, 560, 561, 571, 572 and 573. Section Number and Title: 76.1700 Records to be maintained by cable system operators. 76.1701 Political file. 76.1702 Equal employment opportunity. 76.1703 Commercial records on children's programs. 76.1704 Proof-of-performance test data. 76.1705 Performance test (channels delivered). 76.1706 Signal leakage logs and repair records. 76.1707 Leased access. 76.1708 Principal headend. 76.1709 Availability of signals. 76.1710 Operator interests in video programming. 76.1711 Emergency alert system (EAS) tests and activation. 76.1712 Open video system (OVS) requests for carriage. 76.1713 Complaint resolution. 76.1714 FCC rules and regulations. 76.1715 Sponsorship identification. 76.1716 Subscriber records and public inspection file. SUBPART V-REPORTS AND FILINGS Brief Description: These rules require cable operators to file reports
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-249194A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-249194A1.pdf
  • are installed so that the monitoring and transmitting functions are available during the times the stations and systems are in operation. Additionally ... cable systems ...must determine the cause of any failure to receive the required tests or activations specified in §§ 11.61(a)(1) and (2). Appropriate entries must be made in the cable system record as specified in §§ 76.1700, 76.1708 and 76.1711 of this chapter ... indicating reasons why any tests were not received.'' The EAS encoder / decoder would not retain the current date and there was no entry in the cable system record stating when the problem was first noted. Also, the cable system record did not address absent EAS test receptions. Pursuant to Section 308(b) of the
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-260458A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-260458A1.pdf
  • are installed so that the monitoring and transmitting functions are available during the times the stations and systems are in operation. Additionally, ... cable systems ...must determine the cause of any failure to receive the required tests or activations specified in §§ 11.61(a)(1) and (2). Appropriate entries must be made in the cable system record as specified in §§ 76.1700, 76.1708 and 76.1711 of this chapter ... indicating reasons why any tests were not received.'' A review of the available EAS logs from August 30, 2004 through June 28, 2005 revealed that there were missing entries for received tests. There were numerous weeks which did not have an entry for a received test and those weeks which showed a received test
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-267571A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-267571A1.pdf
  • transmitting functions are available during the times the stations and systems are in operation. Additionally, broadcast stations and cable systems and wireless cable systems must determine the cause of any failure to receive the required tests or activations specified in Sec. 11.61(a)(1) and (a)(2). Appropriate entries must be made in the ... cable system record as specified in §§ 76.1700, 76.1708, and 76.1711 of this chapter ... indicating reasons why any tests were not received.'' At the time of inspection, the EAS equipment was operational, but there were missing entries of tests received from station KYKX and there were no entries in the log indicating the reasons why the tests were not received. Pursuant to Section 308(b) of the Communications Act
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-267572A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-267572A1.pdf
  • transmitting functions are available during the times the stations and systems are in operation. Additionally, broadcast stations and cable systems and wireless cable systems must determine the cause of any failure to receive the required tests or activations specified in Sec. 11.61(a)(1) and (a)(2). Appropriate entries must be made in the ... cable system record as specified in §§ 76.1700, 76.1708, and 76.1711 of this chapter ... indicating reasons why any tests were not received.'' At the time of inspection the EAS equipment was operational, but there were no log entries of test sent for the weeks of April 16-22, May 14-20, and June 11-17, 2006 and there were no entries in the log indicating the reasons why the tests were
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-284308A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-284308A1.pdf
  • Participant records as specified in §§ 11.35(a) and 11.54(b)(13). § 11.35(a) states ``EAS Participants must determine the cause of any failure to receive the required tests or activations specified in § 11.61(a)(1) and (a)(2). Appropriate entries indicating reasons why any tests were not received must be made in . . . cable system records as specified in Sec. Sec. 76.1700, 76.1708, and 76.1711 of this chapter.'' During the inspection, the agent observed that for the months of April and June 2008, there were no entries in the EAS logs nor any EAS printouts of Required Monthly Tests received from station WFAS, one of Cablevision's two monitoring sources. There were no log entries indicating the reasons why these tests were not received.
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-284310A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-284310A1.pdf
  • Participant records as specified in §§ 11.35(a) and 11.54(b)(13). § 11.35(a) states ``EAS Participants must determine the cause of any failure to receive the required tests or activations specified in § 11.61(a)(1) and (a)(2). Appropriate entries indicating reasons why any tests were not received must be made in . . . cable system records as specified in Sec. Sec. 76.1700, 76.1708, and 76.1711 of this chapter.'' During the inspection, the agent observed that for the months of April and June 2008, there were no entries in the EAS logs nor any EAS printouts of Required Monthly Tests received from station WFAS, one of Cablevision's two monitoring sources. There were no log entries indicating the reasons why these tests were not received.
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-296217A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-296217A1.pdf
  • monitoring and transmitting functions are available during the times the systems are in operation. Additionally, cable systems must determine the cause of any failure to receive the required tests or activations specified in § 11.61(a)(1) and (a)(2). Appropriate entries indicating reasons why any tests were not received must be made in the cable system records as specified in §§ 76.1700, 76.1708 and 76.1711. As the nation's emergency warning system, the Emergency Alert System is critical to public safety, and we recognize the vital role that cable systems play in ensuring its success. The Commission takes seriously any violations of the Rules implementing the EAS and expects full compliance from its regulatees. On October 5, 2009, an agent from the Houston Office
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-296218A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-296218A1.pdf
  • monitoring and transmitting functions are available during the times the systems are in operation. Additionally, cable systems must determine the cause of any failure to receive the required tests or activations specified in § 11.61(a)(1) and (a)(2). Appropriate entries indicating reasons why any tests were not received must be made in the cable system records as specified in §§ 76.1700, 76.1708 and 76.1711. As the nation's emergency warning system, the Emergency Alert System is critical to public safety, and we recognize the vital role that cable systems play in ensuring its success. The Commission takes seriously any violations of the Rules implementing the EAS and expects full compliance from its regulatees. On October 5 and 7, 2009, an agent from the
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-301926A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-301926A1.pdf
  • Globe, Arizona, and observed the following violations: a. 47 C.F.R. § 11.35(a): ``EAS Participants must determine the cause of any failure to receive the required tests or activations specified in Sections 11.61(a) (1) and (a) (2). Appropriate entries indicating reasons why any tests were not received must be made in the [...] cable system records as specified in Sec. 76.1700, 76.1708, and 76.1711 of this chapter.'' At the time of the inspection, the agent found that there were no entries in the station log indicating why tests had not been received from the primary local primary (LP-1) Emergency Management 158.940 MHz over the three months prior to the inspection. b. 47 C.F.R. § 11.61(a): ``EAS Participants shall conduct tests at regular
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-309310A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-309310A1.pdf
  • East Oregon Avenue, Philadelphia, Pennsylvania, and observed the following violation: 47 C.F.R. § 11.35(a): ``...EAS Participants must determine the cause of any failure to receive the required tests or activations specified in sections 11.61(a)(1) and (a)(2). Appropriate entries indicating reasons why any tests were not received must be made in the ... cable system records as specified in §§ 76.1700, 76.1708, and 76.1711 of this chapter.'' At the time of the inspection, there were no entries in Verizon's EAS logs indicating the reasons why the required weekly tests were not received from WMGK between July 4, 2011 and July 26, 2011, and between June 1, 2011 and June 22, 2011. As the nation's emergency warning system, the Emergency Alert System is
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-310620A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-310620A1.pdf
  • determine the cause of any failure to receive the required tests or activations specified in Sections 11.61(a)(1) and (a)(2). Appropriate entries indicating reasons why any tests were not received must be made in the broadcast station log as specified in Sections 73.1820 and 73.1840 of this chapter for all broadcast streams and cable system records as specified in Sections 76.1700, 76.1708, and 76.1711 of this chapter.'' At the time of the inspection, logs showed that only one source for EAS messages was being received. Logs also indicated that logging printer failures were preventing the maintenance of complete and legible logs for test and alerts both originated and received. As the nation's emergency warning system, the Emergency Alert System is critical to
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-311713A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-311713A1.pdf
  • available during the times the stations and systems are in operation. Additionally, EAS Participants must determine the cause of any failure to receive the required tests or activations specified in Sec. 11.61(a)(1) and (a)(2). Appropriate entries indicating reasons why any tests were not received must be made in the . . . cable system records as specified in Sections 76.1700, 76.1708, and 76.1711 of this chapter.'' At the time of the inspection, personnel were unable to demonstrate to agents that the EAS encoder and decoder were functional. 47 C.F.R. § 11.52(d): ``EAS Participants must monitor two EAS sources. The monitoring assignments of each broadcast station and cable system and wireless cable system are specified in the State EAS Plan and FCC
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-311714A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-311714A1.pdf
  • the three month period prior to the inspection. 47 C.F.R. § 11.35(a): ``EAS Participants must determine the cause of any failure to receive the required tests or activations specified in Sections 11.61(a)(1) and (a)(2). Appropriate entries indicating reasons why any tests were not received must be made in the . . . cable system records as specified in Sections 76.1700, 76.1708 and 76.1711 of this chapter.'' At the time of the inspection, there were no entries in CALNEVA's logs indicating why the required monthly tests (RMTs) had not been logged over the three months prior to the inspection. As the nation's emergency warning system, the Emergency Alert System is critical to public safety, and we recognize the vital role that cable
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-314316A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-314316A1.pdf
  • determine the cause of any failure to receive the required tests or activations specified in Sections 11.61(a)(1) and (a)(2). Appropriate entries indicating reasons why any tests were not received must be made in the broadcast station log as specified in §§ 73.1820 and 73.1840 of this chapter for all broadcast streams and cable system records as specified in §§ 76.1700, 76.1708, and 76.1711 of this chapter.'' At the time of the inspection, there were no entries in the station's EAS logs indicating that the internal clock of the station's EAS equipment had rolled back one month due to a power failure making it appear the station did not receive any EAS tests between May 24, 2011 and June 24, 2011. As
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-04-135A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-04-135A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-04-135A1.txt
  • operation. Additionally, broadcast stations and cable systems and wireless cable systems must determine the cause of any failure to receive the required tests or activations specified in §§ 11.61(a)(1) and (2). Appropriate entries must be made in the broadcast station log as specified in § 73.1820 and § 73.1840 of this chapter, cable system record as specified in §§ 76.1700, 76.1708, and 76.1711 of this chapter, BRS station records, indicating reasons why any tests were not received. * * * * * PART 15 - RADIO FREQUENCY DEVICES The authority citation for Part 15 continues to read as follows: AUTHORITY: 47 U.S.C. 154, 302(a), 303, 304, 336, and 544(a), unless otherwise noted. Section 15.205(a) is amended by deleting ``2655-2900 MHz'' and
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-05-191A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-05-191A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-05-191A1.txt
  • determine the cause of any failure to receive the required tests or activations specified in § 11.61(a)(1) and (a)(2). Appropriate entries indicating reasons why any tests were not received must be made in the broadcast station log as specified in §§ 73.1820 and 73.1840 of this chapter for all broadcast streams and cable system records as specified in §§ 76.1700, 76.1708, and 76.1711 of this chapter. All other EAS Participants must also keep records indicating reasons why any tests were not received and these records must be retained for two years, maintained at the EAS Participant's headquarters, and made available for public inspection upon reasonable request. (b) If the EAS Encoder or EAS Decoder becomes defective, the EAS Participant may operate
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-05-191A1_Erratum.doc
  • determine the cause of any failure to receive the required tests or activations specified in § 11.61(a)(1) and (a)(2). Appropriate entries indicating reasons why any tests were not received must be made in the broadcast station log as specified in §§ 73.1820 and 73.1840 of this chapter for all broadcast streams and cable system records as specified in §§ 76.1700, 76.1708, and 76.1711 of this chapter. All other EAS Participants must also keep records indicating reasons why any tests were not received and these records must be retained for two years, maintained at the EAS Participant's headquarters, and made available for public inspection upon reasonable request. (b) If the EAS Encoder or EAS Decoder becomes defective, the EAS Participant may operate
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-12-7A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-12-7A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-12-7A1.txt
  • EAS Participants must determine the cause of any failure to receive the required tests or activations specified in §11.61(a)(1) and (a)(2). Appropriate entries indicating reasons why any tests were not received must be made in the broadcast station log as specified in §§73.1820 and 73.1840 of this chapter for all broadcast streams and cable system records as specified in §§76.1700, 76.1708, and 76.1711 of this chapter. All other EAS Participants must also keep records indicating reasons why any tests were not received and these records must be retained for two years, maintained at the EAS Participant's headquarters, and made available for public inspection upon reasonable request. (b) If an EAS Encoder, EAS Decoder or Intermediary Device used as part of the
• http://transition.fcc.gov/eb/FieldNotices/2003/DOC-249194A1.html
  • the EAS are installed so that the monitoring and transmitting functions are available during the times the stations and systems are in operation. Additionally ... cable systems ...must determine the cause of any failure to receive the required tests or activations specified in 11.61(a)(1) and (2). Appropriate entries must be made in the cable system record as specified in 76.1700, 76.1708 and 76.1711 of this chapter ... indicating reasons why any tests were not received.'' The EAS encoder / decoder would not retain the current date and there was no entry in the cable system record stating when the problem was first noted. Also, the cable system record did not address absent EAS test receptions. 3. Pursuant to Section 308(b) of
• http://transition.fcc.gov/eb/FieldNotices/2003/DOC-260458A1.html
  • the EAS are installed so that the monitoring and transmitting functions are available during the times the stations and systems are in operation. Additionally, ... cable systems ...must determine the cause of any failure to receive the required tests or activations specified in 11.61(a)(1) and (2). Appropriate entries must be made in the cable system record as specified in 76.1700, 76.1708 and 76.1711 of this chapter ... indicating reasons why any tests were not received.'' A review of the available EAS logs from August 30, 2004 through June 28, 2005 revealed that there were missing entries for received tests. There were numerous weeks which did not have an entry for a received test and those weeks which showed a received test
• http://transition.fcc.gov/eb/FieldNotices/2003/DOC-267571A1.html
  • transmitting functions are available during the times the stations and systems are in operation. Additionally, broadcast stations and cable systems and wireless cable systems must determine the cause of any failure to receive the required tests or activations specified in Sec. 11.61(a)(1) and (a)(2). Appropriate entries must be made in the ... cable system record as specified in SS 76.1700, 76.1708, and 76.1711 of this chapter ... indicating reasons why any tests were not received." At the time of inspection, the EAS equipment was operational, but there were missing entries of tests received from station KYKX and there were no entries in the log indicating the reasons why the tests were not received. 3. Pursuant to Section 308(b) of the Communications
• http://transition.fcc.gov/eb/FieldNotices/2003/DOC-267572A1.html
  • transmitting functions are available during the times the stations and systems are in operation. Additionally, broadcast stations and cable systems and wireless cable systems must determine the cause of any failure to receive the required tests or activations specified in Sec. 11.61(a)(1) and (a)(2). Appropriate entries must be made in the ... cable system record as specified in SS 76.1700, 76.1708, and 76.1711 of this chapter ... indicating reasons why any tests were not received." At the time of inspection the EAS equipment was operational, but there were no log entries of test sent for the weeks of April 16-22, May 14-20, and June 11-17, 2006 and there were no entries in the log indicating the reasons why the tests were
• http://transition.fcc.gov/eb/FieldNotices/2003/DOC-284310A1.html
  • Participant records as specified in S:S: 11.35(a) and 11.54(b)(13). S: 11.35(a) states "EAS Participants must determine the cause of any failure to receive the required tests or activations specified in S: 11.61(a)(1) and (a)(2). Appropriate entries indicating reasons why any tests were not received must be made in . . . cable system records as specified in Sec. Sec. 76.1700, 76.1708, and 76.1711 of this chapter." During the inspection, the agent observed that for the months of April and June 2008, there were no entries in the EAS logs nor any EAS printouts of Required Monthly Tests received from station WFAS, one of Cablevision's two monitoring sources. There were no log entries indicating the reasons why these tests were not received.
• http://transition.fcc.gov/eb/FieldNotices/2003/DOC-296217A1.html
  • monitoring and transmitting functions are available during the times the systems are in operation. Additionally, cable systems must determine the cause of any failure to receive the required tests or activations specified in S: 11.61(a)(1) and (a)(2). Appropriate entries indicating reasons why any tests were not received must be made in the cable system records as specified in S:S: 76.1700, 76.1708 and 76.1711. As the nation's emergency warning system, the Emergency Alert System is critical to public safety, and we recognize the vital role that cable systems play in ensuring its success. The Commission takes seriously any violations of the Rules implementing the EAS and expects full compliance from its regulatees. On October 5, 2009, an agent from the Houston Office
• http://transition.fcc.gov/eb/FieldNotices/2003/DOC-296218A1.html
  • monitoring and transmitting functions are available during the times the systems are in operation. Additionally, cable systems must determine the cause of any failure to receive the required tests or activations specified in S: 11.61(a)(1) and (a)(2). Appropriate entries indicating reasons why any tests were not received must be made in the cable system records as specified in S:S: 76.1700, 76.1708 and 76.1711. As the nation's emergency warning system, the Emergency Alert System is critical to public safety, and we recognize the vital role that cable systems play in ensuring its success. The Commission takes seriously any violations of the Rules implementing the EAS and expects full compliance from its regulatees. On October 5 and 7, 2009, an agent from the
• http://transition.fcc.gov/eb/FieldNotices/2003/DOC-301926A1.html
  • Globe, Arizona, and observed the following violations: a. 47 C.F.R. S: 11.35(a): "EAS Participants must determine the cause of any failure to receive the required tests or activations specified in Sections 11.61(a) (1) and (a) (2). Appropriate entries indicating reasons why any tests were not received must be made in the [...] cable system records as specified in Sec. 76.1700, 76.1708, and 76.1711 of this chapter." At the time of the inspection, the agent found that there were no entries in the station log indicating why tests had not been received from the primary local primary (LP-1) Emergency Management 158.940 MHz over the three months prior to the inspection. b. 47 C.F.R. S: 11.61(a): "EAS Participants shall conduct tests at regular
• http://transition.fcc.gov/eb/FieldNotices/2003/DOC-309310A1.html
  • East Oregon Avenue, Philadelphia, Pennsylvania, and observed the following violation: 47 C.F.R. S: 11.35(a): "...EAS Participants must determine the cause of any failure to receive the required tests or activations specified in sections 11.61(a)(1) and (a)(2). Appropriate entries indicating reasons why any tests were not received must be made in the ... cable system records as specified in S:S: 76.1700, 76.1708, and 76.1711 of this chapter." At the time of the inspection, there were no entries in Verizon's EAS logs indicating the reasons why the required weekly tests were not received from WMGK between July 4, 2011 and July 26, 2011, and between June 1, 2011 and June 22, 2011. 3. As the nation's emergency warning system, the Emergency Alert System
• http://transition.fcc.gov/eb/FieldNotices/2003/DOC-310620A1.html
  • determine the cause of any failure to receive the required tests or activations specified in Sections 11.61(a)(1) and (a)(2). Appropriate entries indicating reasons why any tests were not received must be made in the broadcast station log as specified in Sections 73.1820 and 73.1840 of this chapter for all broadcast streams and cable system records as specified in Sections 76.1700, 76.1708, and 76.1711 of this chapter." At the time of the inspection, logs showed that only one source for EAS messages was being received. Logs also indicated that logging printer failures were preventing the maintenance of complete and legible logs for test and alerts both originated and received. 3. As the nation's emergency warning system, the Emergency Alert System is critical
• http://transition.fcc.gov/eb/FieldNotices/2003/DOC-311713A1.html
  • available during the times the stations and systems are in operation. Additionally, EAS Participants must determine the cause of any failure to receive the required tests or activations specified in Sec. 11.61(a)(1) and (a)(2). Appropriate entries indicating reasons why any tests were not received must be made in the . . . cable system records as specified in Sections 76.1700, 76.1708, and 76.1711 of this chapter." At the time of the inspection, personnel were unable to demonstrate to agents that the EAS encoder and decoder were functional. c. 47 C.F.R. S: 11.52(d): "EAS Participants must monitor two EAS sources. The monitoring assignments of each broadcast station and cable system and wireless cable system are specified in the State EAS Plan and
• http://transition.fcc.gov/eb/FieldNotices/2003/DOC-311714A1.html
  • three month period prior to the inspection. c. 47 C.F.R. S: 11.35(a): "EAS Participants must determine the cause of any failure to receive the required tests or activations specified in Sections 11.61(a)(1) and (a)(2). Appropriate entries indicating reasons why any tests were not received must be made in the . . . cable system records as specified in Sections 76.1700, 76.1708 and 76.1711 of this chapter." At the time of the inspection, there were no entries in CALNEVA's logs indicating why the required monthly tests (RMTs) had not been logged over the three months prior to the inspection. 3. As the nation's emergency warning system, the Emergency Alert System is critical to public safety, and we recognize the vital role that
• http://transition.fcc.gov/eb/Orders/2005/FCC-05-191A1.html
  • EAS Participants must determine the cause of any failure to receive the required tests or activations specified in 11.61(a)(1) and (a)(2). Appropriate entries indicating reasons why any tests were not received must be made in the broadcast station log as specified in 73.1820 and 73.1840 of this chapter for all broadcast streams and cable system records as specified in 76.1700, 76.1708, and 76.1711 of this chapter. All other EAS Participants must also keep records indicating reasons why any tests were not received and these records must be retained for two years, maintained at the EAS Participant's headquarters, and made available for public inspection upon reasonable request. (b) If the EAS Encoder or EAS Decoder becomes defective, the EAS Participant may operate
• http://transition.fcc.gov/eb/Public_Notices/DA-02-724A1.html
  • (2/28/02). * Public Radio, Inc., Holly Hill, FL. Tampa, FL District Office (2/28/02). * 47 C.F.R. 11.61 Tests of EAS Procedures * Charter Communications, Coos Bay, Oregon. Portland, OR Resident Agent Office (2/12/02). * Service Electric Cable, Allentown, PA. Other violations: 47 C.F.R. 17.4(g) (Posting of Antenna Structure Registration Number), 17.47 (Inspection of Antenna Structure Lights and Associated Control Equipment), 76.1708 (Principal Headend), 76.1709 (Availability of Signals) and 76.1711 (Emergency Alert System (EAS) Tests and Activation). Philadelphia, PA District Office (2/14/02). * Urban Cableworks of Philadelphia, Philadelphia, PA. Philadelphia, PA District Office (2/14/02). * Capstar TX Limited Partnership, WKCY, Harrisonburg, VA. Other violation: 47 C.F.R. 73.1870 (Chief Operator). Columbia, MD District Office (2/26/02). * Capstar TX Limited Partnership, WKCY-FM, Harrisonburg, VA.
• http://transition.fcc.gov/eb/Public_Notices/da012818.html http://transition.fcc.gov/eb/Public_Notices/da012818.pdf
  • (Records to be Maintained Locally By Cable System Operators), 76.1701 (Political File) and 76.1710 (Operator Interests in Video Programming). San Francisco, CA District Office (10/3/01). * Mediacom, Excelsior Springs, MO. Kansas City, MO District Office (10/9/01). * Charter Communications, Picayune, MS. New Orleans, LA District Office (10/11/01). * Charter Communications, Columbia, MS. Other violations: 47 C.F.R. 76.1701 (Political File) and 76.1708 (Principal Headend). New Orleans, LA District Office (10/12/01). * Charter Communications VI LLC, St. Louis, MO. Dallas, TX District Office (10/17/01). * AT&T Broadband and Internet Services, Tooele & Grantsville, UT (Physical System #008436). Denver, CO District Office (10/23/01). * AT&T Broadband & Internet Services, Heber City and Midway, UT (Physical System #010042). Denver, CO District Office (10/23/01). * AT&T
• http://www.fcc.gov/eb/FieldNotices/2003/DOC-249194A1.html
  • the EAS are installed so that the monitoring and transmitting functions are available during the times the stations and systems are in operation. Additionally ... cable systems ...must determine the cause of any failure to receive the required tests or activations specified in 11.61(a)(1) and (2). Appropriate entries must be made in the cable system record as specified in 76.1700, 76.1708 and 76.1711 of this chapter ... indicating reasons why any tests were not received.'' The EAS encoder / decoder would not retain the current date and there was no entry in the cable system record stating when the problem was first noted. Also, the cable system record did not address absent EAS test receptions. 3. Pursuant to Section 308(b) of
• http://www.fcc.gov/eb/FieldNotices/2003/DOC-260458A1.html
  • the EAS are installed so that the monitoring and transmitting functions are available during the times the stations and systems are in operation. Additionally, ... cable systems ...must determine the cause of any failure to receive the required tests or activations specified in 11.61(a)(1) and (2). Appropriate entries must be made in the cable system record as specified in 76.1700, 76.1708 and 76.1711 of this chapter ... indicating reasons why any tests were not received.'' A review of the available EAS logs from August 30, 2004 through June 28, 2005 revealed that there were missing entries for received tests. There were numerous weeks which did not have an entry for a received test and those weeks which showed a received test
• http://www.fcc.gov/eb/FieldNotices/2003/DOC-267571A1.html
  • transmitting functions are available during the times the stations and systems are in operation. Additionally, broadcast stations and cable systems and wireless cable systems must determine the cause of any failure to receive the required tests or activations specified in Sec. 11.61(a)(1) and (a)(2). Appropriate entries must be made in the ... cable system record as specified in SS 76.1700, 76.1708, and 76.1711 of this chapter ... indicating reasons why any tests were not received." At the time of inspection, the EAS equipment was operational, but there were missing entries of tests received from station KYKX and there were no entries in the log indicating the reasons why the tests were not received. 3. Pursuant to Section 308(b) of the Communications
• http://www.fcc.gov/eb/FieldNotices/2003/DOC-267572A1.html
  • transmitting functions are available during the times the stations and systems are in operation. Additionally, broadcast stations and cable systems and wireless cable systems must determine the cause of any failure to receive the required tests or activations specified in Sec. 11.61(a)(1) and (a)(2). Appropriate entries must be made in the ... cable system record as specified in SS 76.1700, 76.1708, and 76.1711 of this chapter ... indicating reasons why any tests were not received." At the time of inspection the EAS equipment was operational, but there were no log entries of test sent for the weeks of April 16-22, May 14-20, and June 11-17, 2006 and there were no entries in the log indicating the reasons why the tests were
• http://www.fcc.gov/eb/FieldNotices/2003/DOC-284308A1.html
  • Participant records as specified in S:S: 11.35(a) and 11.54(b)(13). S: 11.35(a) states "EAS Participants must determine the cause of any failure to receive the required tests or activations specified in S: 11.61(a)(1) and (a)(2). Appropriate entries indicating reasons why any tests were not received must be made in . . . cable system records as specified in Sec. Sec. 76.1700, 76.1708, and 76.1711 of this chapter." During the inspection, the agent observed that for the months of April and June 2008, there were no entries in the EAS logs nor any EAS printouts of Required Monthly Tests received from station WFAS, one of Cablevision's two monitoring sources. There were no log entries indicating the reasons why these tests were not received.
• http://www.fcc.gov/eb/FieldNotices/2003/DOC-284310A1.html
  • Participant records as specified in S:S: 11.35(a) and 11.54(b)(13). S: 11.35(a) states "EAS Participants must determine the cause of any failure to receive the required tests or activations specified in S: 11.61(a)(1) and (a)(2). Appropriate entries indicating reasons why any tests were not received must be made in . . . cable system records as specified in Sec. Sec. 76.1700, 76.1708, and 76.1711 of this chapter." During the inspection, the agent observed that for the months of April and June 2008, there were no entries in the EAS logs nor any EAS printouts of Required Monthly Tests received from station WFAS, one of Cablevision's two monitoring sources. There were no log entries indicating the reasons why these tests were not received.
• http://www.fcc.gov/eb/FieldNotices/2003/DOC-296217A1.html
  • monitoring and transmitting functions are available during the times the systems are in operation. Additionally, cable systems must determine the cause of any failure to receive the required tests or activations specified in S: 11.61(a)(1) and (a)(2). Appropriate entries indicating reasons why any tests were not received must be made in the cable system records as specified in S:S: 76.1700, 76.1708 and 76.1711. As the nation's emergency warning system, the Emergency Alert System is critical to public safety, and we recognize the vital role that cable systems play in ensuring its success. The Commission takes seriously any violations of the Rules implementing the EAS and expects full compliance from its regulatees. On October 5, 2009, an agent from the Houston Office
• http://www.fcc.gov/eb/FieldNotices/2003/DOC-296218A1.html
  • monitoring and transmitting functions are available during the times the systems are in operation. Additionally, cable systems must determine the cause of any failure to receive the required tests or activations specified in S: 11.61(a)(1) and (a)(2). Appropriate entries indicating reasons why any tests were not received must be made in the cable system records as specified in S:S: 76.1700, 76.1708 and 76.1711. As the nation's emergency warning system, the Emergency Alert System is critical to public safety, and we recognize the vital role that cable systems play in ensuring its success. The Commission takes seriously any violations of the Rules implementing the EAS and expects full compliance from its regulatees. On October 5 and 7, 2009, an agent from the
• http://www.fcc.gov/eb/FieldNotices/2003/DOC-301926A1.html
  • Globe, Arizona, and observed the following violations: a. 47 C.F.R. S: 11.35(a): "EAS Participants must determine the cause of any failure to receive the required tests or activations specified in Sections 11.61(a) (1) and (a) (2). Appropriate entries indicating reasons why any tests were not received must be made in the [...] cable system records as specified in Sec. 76.1700, 76.1708, and 76.1711 of this chapter." At the time of the inspection, the agent found that there were no entries in the station log indicating why tests had not been received from the primary local primary (LP-1) Emergency Management 158.940 MHz over the three months prior to the inspection. b. 47 C.F.R. S: 11.61(a): "EAS Participants shall conduct tests at regular
• http://www.fcc.gov/eb/FieldNotices/2003/DOC-309310A1.html
  • East Oregon Avenue, Philadelphia, Pennsylvania, and observed the following violation: 47 C.F.R. S: 11.35(a): "...EAS Participants must determine the cause of any failure to receive the required tests or activations specified in sections 11.61(a)(1) and (a)(2). Appropriate entries indicating reasons why any tests were not received must be made in the ... cable system records as specified in S:S: 76.1700, 76.1708, and 76.1711 of this chapter." At the time of the inspection, there were no entries in Verizon's EAS logs indicating the reasons why the required weekly tests were not received from WMGK between July 4, 2011 and July 26, 2011, and between June 1, 2011 and June 22, 2011. 3. As the nation's emergency warning system, the Emergency Alert System
• http://www.fcc.gov/eb/FieldNotices/2003/DOC-310620A1.html
  • determine the cause of any failure to receive the required tests or activations specified in Sections 11.61(a)(1) and (a)(2). Appropriate entries indicating reasons why any tests were not received must be made in the broadcast station log as specified in Sections 73.1820 and 73.1840 of this chapter for all broadcast streams and cable system records as specified in Sections 76.1700, 76.1708, and 76.1711 of this chapter." At the time of the inspection, logs showed that only one source for EAS messages was being received. Logs also indicated that logging printer failures were preventing the maintenance of complete and legible logs for test and alerts both originated and received. 3. As the nation's emergency warning system, the Emergency Alert System is critical
• http://www.fcc.gov/eb/FieldNotices/2003/DOC-311713A1.html
  • available during the times the stations and systems are in operation. Additionally, EAS Participants must determine the cause of any failure to receive the required tests or activations specified in Sec. 11.61(a)(1) and (a)(2). Appropriate entries indicating reasons why any tests were not received must be made in the . . . cable system records as specified in Sections 76.1700, 76.1708, and 76.1711 of this chapter." At the time of the inspection, personnel were unable to demonstrate to agents that the EAS encoder and decoder were functional. c. 47 C.F.R. S: 11.52(d): "EAS Participants must monitor two EAS sources. The monitoring assignments of each broadcast station and cable system and wireless cable system are specified in the State EAS Plan and
• http://www.fcc.gov/eb/FieldNotices/2003/DOC-311714A1.html
  • three month period prior to the inspection. c. 47 C.F.R. S: 11.35(a): "EAS Participants must determine the cause of any failure to receive the required tests or activations specified in Sections 11.61(a)(1) and (a)(2). Appropriate entries indicating reasons why any tests were not received must be made in the . . . cable system records as specified in Sections 76.1700, 76.1708 and 76.1711 of this chapter." At the time of the inspection, there were no entries in CALNEVA's logs indicating why the required monthly tests (RMTs) had not been logged over the three months prior to the inspection. 3. As the nation's emergency warning system, the Emergency Alert System is critical to public safety, and we recognize the vital role that
• http://www.fcc.gov/eb/FieldNotices/2003/DOC-314316A1.html
  • determine the cause of any failure to receive the required tests or activations specified in Sections 11.61(a)(1) and (a)(2). Appropriate entries indicating reasons why any tests were not received must be made in the broadcast station log as specified in S:S: 73.1820 and 73.1840 of this chapter for all broadcast streams and cable system records as specified in S:S: 76.1700, 76.1708, and 76.1711 of this chapter." At the time of the inspection, there were no entries in the station's EAS logs indicating that the internal clock of the station's EAS equipment had rolled back one month due to a power failure making it appear the station did not receive any EAS tests between May 24, 2011 and June 24, 2011. 3.
• http://www.fcc.gov/eb/Orders/2005/FCC-05-191A1.html
  • EAS Participants must determine the cause of any failure to receive the required tests or activations specified in 11.61(a)(1) and (a)(2). Appropriate entries indicating reasons why any tests were not received must be made in the broadcast station log as specified in 73.1820 and 73.1840 of this chapter for all broadcast streams and cable system records as specified in 76.1700, 76.1708, and 76.1711 of this chapter. All other EAS Participants must also keep records indicating reasons why any tests were not received and these records must be retained for two years, maintained at the EAS Participant's headquarters, and made available for public inspection upon reasonable request. (b) If the EAS Encoder or EAS Decoder becomes defective, the EAS Participant may operate
• http://www.fcc.gov/eb/Public_Notices/DA-02-724A1.html
  • (2/28/02). * Public Radio, Inc., Holly Hill, FL. Tampa, FL District Office (2/28/02). * 47 C.F.R. 11.61 Tests of EAS Procedures * Charter Communications, Coos Bay, Oregon. Portland, OR Resident Agent Office (2/12/02). * Service Electric Cable, Allentown, PA. Other violations: 47 C.F.R. 17.4(g) (Posting of Antenna Structure Registration Number), 17.47 (Inspection of Antenna Structure Lights and Associated Control Equipment), 76.1708 (Principal Headend), 76.1709 (Availability of Signals) and 76.1711 (Emergency Alert System (EAS) Tests and Activation). Philadelphia, PA District Office (2/14/02). * Urban Cableworks of Philadelphia, Philadelphia, PA. Philadelphia, PA District Office (2/14/02). * Capstar TX Limited Partnership, WKCY, Harrisonburg, VA. Other violation: 47 C.F.R. 73.1870 (Chief Operator). Columbia, MD District Office (2/26/02). * Capstar TX Limited Partnership, WKCY-FM, Harrisonburg, VA.
• http://www.fcc.gov/mb/engineering/76print.html
  • compatibility offer. [204]76.1622 Consumer education program on compatibility. Subpart U -- Documents to be Maintained for Inspection [205]76.1700 Records to be maintained by cable system operators. [206]76.1701 Political file. [207]76.1702 Equal employment opportunity. [208]76.1703 Commercial matter on children's programs. [209]76.1704 Proof of performance test data. [210]76.1705 Performance tests (channels delivered). [211]76.1706 Signal leakage logs and repair records. [212]76.1707 Leased access. [213]76.1708 Principal headend. [214]76.1709 Availability of signals. [215]76.1710 Operator interests in video programming. [216]76.1711 Emergency alert system (EAS) tests and activation. [217]76.1712 Open video system (OVS) requests for carriage. [218]76.1713 Complaint resolution. [219]76.1714 FCC rules and regulations. [220]76.1715 Sponsorship identification. [221]76.1716 Subscriber records and public inspection file. [222]76.1717 Compliance with technical standards. Subpart V -- Reports and Filings [223]76.1800 Additional reports
• http://www.fcc.gov/mb/engineering/part76.pdf
  • Regulations: 5/6/2011 http://ecfr.gpoaccess.gov/cgi/t/text/text-idx?c=ecfr&sid=a0b1c7045abd9e3f08f6d3233a640e58&rg... Subpart U-Documents to be Maintained for Inspection § 76.1700 Records to be maintained by cable system operators. § 76.1701 Political file. § 76.1702 Equal employment opportunity. § 76.1703 Commercial records on children's programs. § 76.1704 Proof-of-performance test data. § 76.1705 Performance tests (channels delivered). § 76.1706 Signal leakage logs and repair records. § 76.1707 Leased access. § 76.1708 Principal headend. § 76.1709 Availability of signals. § 76.1710 Operator interests in video programming. § 76.1711 Emergency alert system (EAS) tests and activation. § 76.1712 Open video system (OVS) requests for carriage. § 76.1713 Complaint resolution. § 76.1714 FCC rules and regulations. § 76.1715 Sponsorship identification. § 76.1716 Subscriber records and public inspection file. § 76.1717 Compliance with technical standards.