FCC Web Documents citing 11.31

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

• http://fjallfoss.fcc.gov/edocs_public/attachmatch/DA-08-1394A1.doc http://fjallfoss.fcc.gov/edocs_public/attachmatch/DA-08-1394A1.pdf
  • of record. FEDERAL COMMUNICATIONS COMMISSION Dennis P. Carlton Regional Director, South Central Region Enforcement Bureau 47 C.F.R. § 11.35(a). Notice of Apparent Liability for Forfeiture, NAL/Acct. No. 200732500006 (Enf. Bur., Dallas Office, October 23, 2007) (``NAL''). 47 U.S.C. § 503(b). 47 C.F.R. § 1.80. 47 U.S.C. § 503(b)(2)(E). 47 C.F.R. § 11.35(a). 47 C.F.R. §§ 11.35(a), (b). 47 C.F.R. § 11.31. Some EAS units can be programmed to print an out-of-date message for received tests prior to discarding them. However, there were no such messages in station KMZE's files. According to Omni's program logs, no weekly tests were transmitted between January 28 and February 17, 2008. Licensees are not informed of the exact time at which monthly EAS tests are sent.
• http://fjallfoss.fcc.gov/edocs_public/attachmatch/DA-08-1717A1.doc http://fjallfoss.fcc.gov/edocs_public/attachmatch/DA-08-1717A1.pdf
  • participating national EAS source (``EAS Participant'') unless the station affirmatively requests authority to not participate. 47 C.F.R. §§ 11.11 and 11.41. See 47 C.F.R. § 11.1 et. seq. The EAS protocol consists of four parts: Preamble and EAS Header Codes; two-tone audio Attention Signal (``EAS tone''); message; and Preamble and EAS End of Message (``EOM'') Codes. See 47 C.F.R. § 11.31(a). 47 C.F.R. §§ 11.32, 11.33. The functions of the EAS encoder and decoder may be combined into a single unit referred to as an Encoder/Decoder provided that the unit complies with all specifications in Part 11 of the Commission's Rules. See 47.C.F.R. § 11.34(c). 47 C.F.R. § 11.32(a). 47 C.F.R. § 11.32(a)(9)(v). 47 C.F.R. § 11.61(a). The Emergency Alert System
• http://fjallfoss.fcc.gov/edocs_public/attachmatch/DA-09-1958A1.doc http://fjallfoss.fcc.gov/edocs_public/attachmatch/DA-09-1958A1.pdf
  • Alabama 36467. FEDERAL COMMUNICATIONS COMMISSION Kathryn S. Berthot Chief, Spectrum Enforcement Division Enforcement Bureau File No. BRED-20040122AEE. The Commission granted Opp Educational Broadcasting Foundation a license renewal for station WJIF on January 31, 2007. The license expires on April 1, 2012. 47 C.F.R. §§ 11.35 and 11.61(a). 47 C.F. R. § 73.1015. 47 C.F.R. §§ 11.1 - 11.61. 47 C.F.R. §11.31. 47 C.F.R. §11.11(a). 47 C.F.R. § 11.61(a). See Letter from Kathryn S. Berthot, Chief, Spectrum Enforcement Division, Enforcement Bureau, Federal Communications Commission to Mr. Haywood F. Nawlin, Administrator, Opp Educational Broadcasting Foundation, Licensee of Radio Station WJIF (November 4, 2008). 47 C.F.R. § 73.1820. See Letter from Haywood F. Nawlins, WJIF Radio to Kathryn S. Berthot Chief, Spectrum Enforcement Division,
• http://fjallfoss.fcc.gov/edocs_public/attachmatch/DA-09-694A1.doc http://fjallfoss.fcc.gov/edocs_public/attachmatch/DA-09-694A1.pdf
  • March 27, 2009 PUBLIC SAFETY AND HOMELAND SECURITY BUREAU PROVIDES GUIDANCE REGARDING ``LIVE CODE'' TESTING OF THE EMERGENCY ALERT SYSTEM The Public Safety and Homeland Security Bureau reminds Commission-regulated entities that participate in the Emergency Alert System (EAS Participants) that tests of the EAS must conform to requirements set out in Part 11 of the Commission's Rules. In particular, section 11.31(c) provides that the EAS protocol, including any codes, ``must not be amended, extended or abridged without FCC authorization.'' The codes are specified in section 11.31(e), which lists the ``live'' event codes that are to be used for alerts in specific emergency situations, e.g., tornadoes, tsunamis, and other natural and weather-related emergencies. Section 11.31(e) also lists specific test codes that are
• http://fjallfoss.fcc.gov/edocs_public/attachmatch/DA-10-796A1.doc http://fjallfoss.fcc.gov/edocs_public/attachmatch/DA-10-796A1.pdf
  • and regular mail, to Telefutura Partnership of Douglas, at its address of record. FEDERAL COMMUNICATIONS COMMISSION William R. Zears, Jr. District Director San Diego Office Western Region Enforcement Bureau 47 C.F.R. § 11.35. 47 U.S.C. § 503(b). 47 C.F.R. § 11.33(a). The EAS decoder must at a minimum be capable of decoding the EAS protocol described in 47 C.F.R. § 11.31. Section 312(f)(1) of the Act, 47 U.S.C. § 312(f)(1), which applies to violations for which forfeitures are assessed under Section 503(b) of the Act, provides that ``[t]he term `willful', when used with reference to the commission or omission of any act, means the conscious and deliberate commission or omission of such act, irrespective of any intent to violate any provision
• http://fjallfoss.fcc.gov/edocs_public/attachmatch/FCC-07-109A1.doc http://fjallfoss.fcc.gov/edocs_public/attachmatch/FCC-07-109A1.pdf
  • public. Non-participating National (NN) sources have elected not to participate in the National level EAS and hold an authorization letter to that effect. They may transmit EAS State or Local Area messages. EAS Protocol. All EAS message originators (whether FEMA, NWS, or a state or local authority) currently must transmit messages using the EAS protocol and codes specified in section 11.31 of the Commission's rules. Dedicated equipment currently is required to initiate, receive, and retransmit EAS alerts, and must be installed by every EAS Participant. Sections 11.32 and 11.33 of the Commission's rules set forth minimum requirements for EAS encoders and decoders, respectively, the functions of which can be combined into a single unit referred to as an Encoder/Decoder (ENDEC). In
• http://fjallfoss.fcc.gov/edocs_public/attachmatch/FCC-10-11A1.doc http://fjallfoss.fcc.gov/edocs_public/attachmatch/FCC-10-11A1.pdf
  • systems, digital cable systems, wireless cables systems, Direct Broadcast Satellite (DBS) services, Satellite Digital Audio Radio Service (SDARS), and other participating entities. See 47 C.F.R. § 11.1. See 47 C.F.R. Part 11. See 47 C.F.R. § 11.21. All broadcast stations and cable systems have EAS designations that describe their functions within EAS. See 47 C.F.R. § 11.18. 47 C.F.R. § 11.31. 47 C.F.R. §§ 11.32, 11.33. 47 C.F.R. § 11.34(c). EAS equipment also provides a means to automatically interrupt regular programming and is capable of providing warnings in the primary language that is used by the station or cable system. See 47 C.F.R. §§ 11.33(a)(4), 11.51(k)(1), 11.54. See 47 C.F.R. § 11.54 (EAS operation during a national level emergency). See 47
• http://fjallfoss.fcc.gov/edocs_public/attachmatch/FCC-10-203A1.doc http://fjallfoss.fcc.gov/edocs_public/attachmatch/FCC-10-203A1.pdf
  • (footnotes omitted). AASHTO Letter at 3. AASHTO Comments at 7 (footnotes omitted). AASHTO Letter at 3. These requests did not appear in AASHTO's subsequent petition for rulemaking. The SAME transmissions concern National Weather Service severe weather alerts and warnings. They are equivalent to many of the ``Event codes'' used in the Commission's Emergency Alert System rules. See 47 C.F.R. § 11.31(e). . HIS Petition at 9. Id. at 10. Id. Id. at 4, quoting Commercial Mobile Alert System, PS Docket 07-287, Third Report and Order, 23 FCC Rcd 12561, 12563 ¶ 4 (2008). Id. at 4. Id. at 4-5. See, e.g., City of Santa Monica, CA; Florida's Turnpike Enterprise; Texas DOT; Utah DOT; City of Miramar, FL; Rhode Island DOT; Emanuel
• http://fjallfoss.fcc.gov/edocs_public/attachmatch/FCC-11-12A1.doc http://fjallfoss.fcc.gov/edocs_public/attachmatch/FCC-11-12A1.pdf
  • we do not adopt that code or any other location code here. Rather, we delegate authority to the Bureau to determine, in conjunction with FEMA and other EAS stakeholders, the specific location code or codes to be used for the first national EAS test and for subsequent tests. Required Relay of EAN in Conjunction with a National Location Code Section 11.31(c) of the Commission's rules requires that the header of all EAS alerts contain a code to indicate the location of the emergency. This location code is a 6 digit ASCII code that utilizes the five character numbers assigned to the various states, counties, cities and portions of counties. There is no national code as such, and the rule section notes
• http://fjallfoss.fcc.gov/edocs_public/attachmatch/FCC-11-82A1.doc http://fjallfoss.fcc.gov/edocs_public/attachmatch/FCC-11-82A1.pdf
  • FCC-filed and approved versions of the State and Local Area EAS Plans. Miscellaneous Part 11 Revisions Not Related to CAP: We seek comment on whether the Commission can delete some or all of the current provisions relating to the Attention Signal in sections 11.32(9) and 11.33(b) of the rules and instead apply the minimal standard currently set forth in section 11.31(a)(2) or whether we should delete the Attention Signal from the Part 11 rules altogether. We seek comment on whether the introduction of CAP to the existing technical framework of the EAS can improve access to emergency information to persons with disabilities. BACKGROUND Congress established the Commission for the purposes of, among other things, the national defense and the promotion of
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-01-2273A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-01-2273A1.txt
  • 73.1745 (Unauthorized Operation), 73.1870 (Chief Operator) and 73.3526 (Local Public Inspection File for Commercial Stations). Atlanta, GA District Office (8/9/01). Bartow Broadcasting Co., Inc. Other violations: 47 C.F.R. §§ 11.52 (EAS Code and Attention Signal Monitoring Requirements), 11.61(Tests of EAS Procedures), 73.49 (AM Transmission System Fencing Requirements) and 73.1840 (Retention of Logs). Tampa, FL District Office (8/22/01). 47 C.F.R. § 11.31 ­ EAS Protocol Agpal Broadcasting Inc., KPPT(AM/FM) Toledo, Oregon. Other violations: 47 C.F.R. § 73.3526 (Local Public Inspection File for Commercial Stations). Portland, OR Resident Agent Office (8/22/01). 47 C.F.R. § 11.35 ­ Equipment Operational Readiness Clarke Broadcasting Corporation, KVML/KZSQ, Sonora, CA. Other violations: 47 C.F.R. §§ 11.52 (EAS Code and Attention Signal Monitoring Requirements), 11.61 (Tests of EAS Procedures)
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-02-101A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-02-101A1.txt
  • agree cooperatively to achieve the level of protection for ARNS systems that is stated in considering c); h) that it may be appropriate for representatives of administrations operating ARNS systems to be involved in determinations made pursuant to considering g); resolves 1that, in order to protect ARNS systems, administrations shall ensure, without validation by the Bureau pursuant either to No. S11.31 or S9.35 of the Radio Regulations, that the aggregate pfd level produced by all space stations of all radionavigation-satellite service systems at the Earth's surface does not exceed the level, [­XXX dB(W/m2)] in any 1 MHz band for all angles of arrival; 2 that administrations operating or planning to operate in the 1 164-1 215 MHz frequency band RNSS systems
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-02-1415A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-02-1415A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-02-1415A1.txt
  • to achieve the level of protection for ARNS systems that is stated in considering c); h) that it may be appropriate for representatives of administrations operating ARNS systems to be involved in determinations made pursuant to considering g); resolves 1 that, in order to protect ARNS systems, administrations shall ensure, without validation by the Radiocommunication Bureau pursuant either to No. S11.31 or S9.35 of the Radio Regulations, that the equivalent pfd level produced by all space stations of all RNSS systems does not exceed the level, -121.5 dB(W/m2) in any 1 MHz band; 2 that administrations operating or planning to operate in the 1 164-1 215 MHz frequency band RNSS systems or networks for which complete coordination or notification information, as
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-02-1779A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-02-1779A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-02-1779A1.txt
  • April 2007; 2 that administrations should no longer notify any frequency assignments to stations of the fixed and mobile services in the reallocated bands. Assignments notified in these bands after x July 2003 shall bear a symbol to indicate that the finding will be examined by the Bureau as of 1 April 2007 in accordance with the provisions of No. 11.31; 3 that the Bureau shall undertake a continuing action to review the Master International Frequency Register with the help of administrations. In this respect, the Bureau shall periodically consult the administrations concerning the frequency assignments to links for which another satisfactory means of telecommunication exists, with a view to either downgrading assignments of class of operation A or deleting such
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-02-407A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-02-407A1.txt
  • agree cooperatively to achieve the level of protection for ARNS systems that is stated in considering c); h)that it may be appropriate for representatives of administrations operating ARNS systems to be involved in determinations made pursuant to considering g); resolves 1 that, in order to protect ARNS systems, administrations shall ensure, without validation by the Bureau pursuant either to No. S11.31 or S9.35 of the Radio Regulations, that the aggregate pfd level produced by all space stations of all radionavigation-satellite service systems at the Earth's surface does not exceed the level, [­116.6] dB(W/m2) in any 1 MHz band for all angles of arrival; 2 that administrations operating or planning to operate in the 1 164-1 215 MHz frequency band RNSS systems
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-05-1524A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-05-1524A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-05-1524A1.txt
  • B -- EQUIPMENT REQUIREMENTS Brief Description: These rules describe EAS protocol for emergency event codes and EAS equipment requirements. Need: Establishing quality and compatibility standards for EAS equipment will ensure technological interoperability and result in delivery of responsive, robust, and redundant emergency messaging. Legal Basis: 47 U.S.C. 151, 154 (i) and (o), 303(r), 544(g) and 606. Section Number and Title: 11.31 EAS Protocol. 11.32 EAS Encoder. 11.33 EAS Decoder. 11.34 Acceptability of the Equipment. 11.35 Equipment operational readiness. SUBPART C -- ORGANIZATION Brief Description: These rules describe participation standards and acceptable uses of EAS for all participating entities. The rules also set message priorities from the Presidential level down to the state and local levels. Need: By setting participation standards and
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-08-1394A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-08-1394A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-08-1394A1.txt
  • of record. FEDERAL COMMUNICATIONS COMMISSION Dennis P. Carlton Regional Director, South Central Region Enforcement Bureau 47 C.F.R. § 11.35(a). Notice of Apparent Liability for Forfeiture, NAL/Acct. No. 200732500006 (Enf. Bur., Dallas Office, October 23, 2007) (``NAL''). 47 U.S.C. § 503(b). 47 C.F.R. § 1.80. 47 U.S.C. § 503(b)(2)(E). 47 C.F.R. § 11.35(a). 47 C.F.R. §§ 11.35(a), (b). 47 C.F.R. § 11.31. Some EAS units can be programmed to print an out-of-date message for received tests prior to discarding them. However, there were no such messages in station KMZE's files. According to Omni's program logs, no weekly tests were transmitted between January 28 and February 17, 2008. Licensees are not informed of the exact time at which monthly EAS tests are sent.
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-08-1717A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-08-1717A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-08-1717A1.txt
  • participating national EAS source (``EAS Participant'') unless the station affirmatively requests authority to not participate. 47 C.F.R. §§ 11.11 and 11.41. See 47 C.F.R. § 11.1 et. seq. The EAS protocol consists of four parts: Preamble and EAS Header Codes; two-tone audio Attention Signal (``EAS tone''); message; and Preamble and EAS End of Message (``EOM'') Codes. See 47 C.F.R. § 11.31(a). 47 C.F.R. §§ 11.32, 11.33. The functions of the EAS encoder and decoder may be combined into a single unit referred to as an Encoder/Decoder provided that the unit complies with all specifications in Part 11 of the Commission's Rules. See 47.C.F.R. § 11.34(c). 47 C.F.R. § 11.32(a). 47 C.F.R. § 11.32(a)(9)(v). 47 C.F.R. § 11.61(a). The Emergency Alert System
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-09-1958A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-09-1958A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-09-1958A1.txt
  • Alabama 36467. FEDERAL COMMUNICATIONS COMMISSION Kathryn S. Berthot Chief, Spectrum Enforcement Division Enforcement Bureau File No. BRED-20040122AEE. The Commission granted Opp Educational Broadcasting Foundation a license renewal for station WJIF on January 31, 2007. The license expires on April 1, 2012. 47 C.F.R. §§ 11.35 and 11.61(a). 47 C.F. R. § 73.1015. 47 C.F.R. §§ 11.1 - 11.61. 47 C.F.R. §11.31. 47 C.F.R. §11.11(a). 47 C.F.R. § 11.61(a). See Letter from Kathryn S. Berthot, Chief, Spectrum Enforcement Division, Enforcement Bureau, Federal Communications Commission to Mr. Haywood F. Nawlin, Administrator, Opp Educational Broadcasting Foundation, Licensee of Radio Station WJIF (November 4, 2008). 47 C.F.R. § 73.1820. See Letter from Haywood F. Nawlins, WJIF Radio to Kathryn S. Berthot Chief, Spectrum Enforcement Division,
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-09-694A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-09-694A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-09-694A1.txt
  • March 27, 2009 PUBLIC SAFETY AND HOMELAND SECURITY BUREAU PROVIDES GUIDANCE REGARDING ``LIVE CODE'' TESTING OF THE EMERGENCY ALERT SYSTEM The Public Safety and Homeland Security Bureau reminds Commission-regulated entities that participate in the Emergency Alert System (EAS Participants) that tests of the EAS must conform to requirements set out in Part 11 of the Commission's Rules. In particular, section 11.31(c) provides that the EAS protocol, including any codes, ``must not be amended, extended or abridged without FCC authorization.'' The codes are specified in section 11.31(e), which lists the ``live'' event codes that are to be used for alerts in specific emergency situations, e.g., tornadoes, tsunamis, and other natural and weather-related emergencies. Section 11.31(e) also lists specific test codes that are
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-10-796A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-10-796A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-10-796A1.txt
  • and regular mail, to Telefutura Partnership of Douglas, at its address of record. FEDERAL COMMUNICATIONS COMMISSION William R. Zears, Jr. District Director San Diego Office Western Region Enforcement Bureau 47 C.F.R. § 11.35. 47 U.S.C. § 503(b). 47 C.F.R. § 11.33(a). The EAS decoder must at a minimum be capable of decoding the EAS protocol described in 47 C.F.R. § 11.31. Section 312(f)(1) of the Act, 47 U.S.C. § 312(f)(1), which applies to violations for which forfeitures are assessed under Section 503(b) of the Act, provides that ``[t]he term `willful', when used with reference to the commission or omission of any act, means the conscious and deliberate commission or omission of such act, irrespective of any intent to violate any provision
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-11-520A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-11-520A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-11-520A1.txt
  • subsequently notified systems, unless permitted by the terms of other coordination agreements. If negotiation with an objecting administration under Article 9 proves unsuccessful, the new system may not cause harmful interference to the previously registered system to which the objection pertained and will not be entitled to protection from interference caused by the other system. See ITU Radio Regulations, Article 11.31.1. In response to the French coordination request for the second-generation Globalstar system, the Commission notified the ANFR and the ITU's Radiocommunication Bureau on Oct. 22, 2010 that the U.S. administration would withhold consent pending coordination with respect to the Iridium system and certain other U.S.-licensed satellite systems. DISCO II Report and Order at ¶41. Id. Iridium Petition to Deny at
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-11-520A1_Rcd.pdf
  • interference from subsequently notified systems, unless permitted by the terms of other coordination agreements. If negotiation with an objecting administration under Article 9 proves unsuccessful, the new system may not cause harmful interference to the previously registered system to which the objection pertained and will not be entitled to protection from interference caused by the other system. 58SeeITU RadioRegulations, Article 11.31.1. In response to the French coordination request for the second- generation Globalstar system, the Commission notified the ANFR and the ITU's Radiocommunication Bureau on Oct. 22, 2010 that the U.S. administration would withhold consent pending coordination with respect to the Iridium system and certain other U.S.-licensed satellite systems. 59DISCO II Report and Order at ¶41. 60Id. 61Iridium Petition to Deny
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-262986A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-262986A1.txt
  • 13.18 6,025,621 8.01 Connecticut 570,023 24,320,736 42.67 9,259,201 16.24 15,061,535 26.42 Delaware 116,342 1,441,053 12.39 684,414 5.88 756,639 6.50 Dist. of Columbia 76,166 15,022,717 197.24 1,307,478 17.17 13,715,240 180.07 Florida 2,539,929 48,096,941 18.94 34,205,420 13.47 13,891,521 5.47 Georgia 1,496,012 77,682,726 51.93 60,457,782 40.41 17,224,944 11.51 Guam 31,992 4,552,769 142.31 3,386,956 105.87 1,165,813 36.44 Hawaii 183,829 3,976,714 21.63 1,897,403 10.32 2,079,310 11.31 Idaho 248,515 4,699,919 18.91 2,976,609 11.98 1,723,310 6.93 Illinois 2,084,187 72,354,829 34.72 40,823,362 19.59 31,531,467 15.13 Indiana 1,003,875 25,512,350 25.41 12,600,151 12.55 12,912,198 12.86 Iowa 482,210 11,026,942 22.87 8,727,428 18.10 2,299,514 4.77 Kansas 470,957 15,237,844 32.36 9,988,834 21.21 5,249,010 11.15 Kentucky 660,782 34,589,141 52.35 16,382,727 24.79 18,206,413 27.55 Louisiana 730,464 53,889,332 73.77 34,820,345 47.67 19,068,986 26.11 Maine 204,337 8,183,013 40.05
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-262986A6.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-262986A6.txt
  • 13.18 6,025,621 8.01 Connecticut 570,023 24,320,736 42.67 9,259,201 16.24 15,061,535 26.42 Delaware 116,342 1,441,053 12.39 684,414 5.88 756,639 6.50 Dist. of Columbia 76,166 15,022,717 197.24 1,307,478 17.17 13,715,240 180.07 Florida 2,539,929 48,096,941 18.94 34,205,420 13.47 13,891,521 5.47 Georgia 1,496,012 77,682,726 51.93 60,457,782 40.41 17,224,944 11.51 Guam 31,992 4,552,769 142.31 3,386,956 105.87 1,165,813 36.44 Hawaii 183,829 3,976,714 21.63 1,897,403 10.32 2,079,310 11.31 Idaho 248,515 4,699,919 18.91 2,976,609 11.98 1,723,310 6.93 Illinois 2,084,187 72,354,829 34.72 40,823,362 19.59 31,531,467 15.13 Indiana 1,003,875 25,512,350 25.41 12,600,151 12.55 12,912,198 12.86 Iowa 482,210 11,026,942 22.87 8,727,428 18.10 2,299,514 4.77 Kansas 470,957 15,237,844 32.36 9,988,834 21.21 5,249,010 11.15 Kentucky 660,782 34,589,141 52.35 16,382,727 24.79 18,206,413 27.55 Louisiana 730,464 53,889,332 73.77 34,820,345 47.67 19,068,986 26.11 Maine 204,337 8,183,013 40.05
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-265170A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-265170A1.txt
  • 178 830 21.45 District of Columbia 146 3,962 3.69 286 1,100 26.00 Florida 2,853 41,725 6.84 3,606 20,782 17.35 Georgia 855 22,184 3.85 1,210 10,286 11.76 Guam 0 0 NM 0 0 NM Hawaii 54 3,042 1.78 171 1,313 13.02 Idaho 111 2,901 3.83 156 1,515 10.30 Illinois 4,376 35,105 12.47 2,512 15,798 15.90 Indiana 885 14,332 6.17 802 7,092 11.31 Iowa 187 4,297 4.35 353 3,336 10.58 Kansas 343 7,831 4.38 349 2,897 12.05 Kentucky 336 9,735 3.45 549 4,846 11.33 Louisiana 535 11,461 4.67 823 5,492 14.99 Maine 254 2,167 11.72 211 1,269 16.63 Maryland 1,302 16,734 7.78 1,225 5,670 21.60 Massachusetts 2,240 26,355 8.50 1,490 7,314 20.37 Michigan 1,993 26,557 7.50 1,692 13,006 13.01 Minnesota 675 13,155 5.13
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-277675A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-277675A1.pdf
  • assessed under Section 503(b) of the Act, provides that ``[t]he term 'repeated', when used with reference to the commission or omission of any act, means the commission or omission of such act more than once or, if such commission or omission is continuous, for more than one day.'' 47 C.F.R. § 11.35(a). 47 C.F.R. §§ 11.35(a), (b). 47 C.F.R. § 11.31. Some EAS units can be programmed to print an out-of-date message for received tests prior to discarding them. However, there were no such messages in station KMZE's files. 12 FCC Rcd 17087 (1997), recon. denied, 15 FCC Rcd 303 (1999); 47 C.F.R. §1.80. 47 U.S.C. § 503(b)(2)(E). 47 U.S.C. § 503(b), 47 C.F.R. §§ 0.111, 0.311, 0.314, 1.80, 11.35(a). 8
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-277877A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-277877A1.pdf
  • assessed under Section 503(b) of the Act, provides that ``[t]he term 'repeated', when used with reference to the commission or omission of any act, means the commission or omission of such act more than once or, if such commission or omission is continuous, for more than one day.'' 47 C.F.R. § 11.35(a). 47 C.F.R. §§ 11.35(a), (b). 47 C.F.R. § 11.31. Some EAS units can be programmed to print an out-of-date message for received tests prior to discarding them. However, there were no such messages in station KMZE's files. 12 FCC Rcd 17087 (1997), recon. denied, 15 FCC Rcd 303 (1999); 47 C.F.R. §1.80. 47 U.S.C. § 503(b)(2)(E). 47 U.S.C. § 503(b), 47 C.F.R. §§ 0.111, 0.311, 0.314, 1.80, 11.35(a). 8
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-279226A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-279226A1.txt
  • TEL. COOP., INC. D/B/A CCRTC 15.79 -2.99 19.36 INFINITE 320756 A CRAIGVILLE TEL. CO., INC. 2.15 -2.26 4.51 9.04 320759 C DAVIESS-MARTIN CTY. RURAL TEL. DBA RTC COMM. 12.92 -4.90 18.74 35.15 320771 A GEETINGSVILLE TEL. CO., INC. -9.18 -25.77 22.35 68.58 320772 C VERIZON NORTH INC.-IN 3.84 -4.58 8.82 0.00 320775 C HANCOCK RURAL TEL. CORP. DBA HANCOCK TELECOM 11.31 -1.27 12.74 32.00 320776 C COMM. CORP. OF INDIANA 1.56 -1.75 3.37 1.46 320777 A HOME TEL. CO. OF PITTSBORO, INC. -2.30 -1.59 -0.72 0.00 320778 A HOME TEL. CO., INC. -2.38 -4.42 2.14 -33.29 320779 C VERIZON NORTH INC.-IN (CONTEL) -1.80 -3.60 1.86 0.00 320783 C LIGONIER TEL. CO. 19.98 -5.88 27.47 59.43 320788 C MERCHANTS & FARMERS TEL.
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-279226A5.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-279226A5.txt
  • TEL. COOP., INC. D/B/A CCRTC 15.79 -2.99 19.36 INFINITE 320756 A CRAIGVILLE TEL. CO., INC. 2.15 -2.26 4.51 9.04 320759 C DAVIESS-MARTIN CTY. RURAL TEL. DBA RTC COMM. 12.92 -4.90 18.74 35.15 320771 A GEETINGSVILLE TEL. CO., INC. -9.18 -25.77 22.35 68.58 320772 C VERIZON NORTH INC.-IN 3.84 -4.58 8.82 0.00 320775 C HANCOCK RURAL TEL. CORP. DBA HANCOCK TELECOM 11.31 -1.27 12.74 32.00 320776 C COMM. CORP. OF INDIANA 1.56 -1.75 3.37 1.46 320777 A HOME TEL. CO. OF PITTSBORO, INC. -2.30 -1.59 -0.72 0.00 320778 A HOME TEL. CO., INC. -2.38 -4.42 2.14 -33.29 320779 C VERIZON NORTH INC.-IN (CONTEL) -1.80 -3.60 1.86 0.00 320783 C LIGONIER TEL. CO. 19.98 -5.88 27.47 59.43 320788 C MERCHANTS & FARMERS TEL.
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-287688A1.pdf
  • MIDWEST-KENDALL, LLC -12.83 -7.00 -6.26 0.00 330925 A BAYLAND TEL, INC. 4.36 -1.62 6.08 0.00 330930 A GRANTLAND TELECOM, INC. -2.48 -2.37 -0.11 -18.76 330931 C CENTURYTEL OF SOUTHERN WISCONSIN, LLC -6.31 -4.90 -1.48 0.00 330934 C CENTURYTEL OF THE MIDWEST-WI/PLATTEVILLE -11.29 -2.01 -9.47 0.00 330936 C INDIANHEAD TEL. CO. -6.98 -2.22 -4.88 -31.91 330937 C PRICE COUNTY TEL. CO. 11.31 -2.98 14.73 0.00 330938 A NORTHEAST TEL. CO. 3.02 -2.64 5.82 INFINITE 330940 C RHINELANDER TEL CO LLC DBA FRONTIER RIB LAKE 0.16 -2.61 2.84 0.00 330941 C RHINELANDER TEL CO LLC(RIB LAKE) DBA FRONTIER -10.56 -3.81 -7.01 0.00 330942 C RICHLAND-GRANT TEL. COOP., INC. 3.89 -2.70 6.77 8.76 330943 A RIVERSIDE TELECOM, INC. 1.42 -2.27 3.78 19.49 330944 A
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-287688A5.pdf
  • MIDWEST-KENDALL, LLC -12.83 -7.00 -6.26 0.00 330925 A BAYLAND TEL, INC. 4.36 -1.62 6.08 0.00 330930 A GRANTLAND TELECOM, INC. -2.48 -2.37 -0.11 -18.76 330931 C CENTURYTEL OF SOUTHERN WISCONSIN, LLC -6.31 -4.90 -1.48 0.00 330934 C CENTURYTEL OF THE MIDWEST-WI/PLATTEVILLE -11.29 -2.01 -9.47 0.00 330936 C INDIANHEAD TEL. CO. -6.98 -2.22 -4.88 -31.91 330937 C PRICE COUNTY TEL. CO. 11.31 -2.98 14.73 0.00 330938 A NORTHEAST TEL. CO. 3.02 -2.64 5.82 INFINITE 330940 C RHINELANDER TEL CO LLC DBA FRONTIER RIB LAKE 0.16 -2.61 2.84 0.00 330941 C RHINELANDER TEL CO LLC(RIB LAKE) DBA FRONTIER -10.56 -3.81 -7.01 0.00 330942 C RICHLAND-GRANT TEL. COOP., INC. 3.89 -2.70 6.77 8.76 330943 A RIVERSIDE TELECOM, INC. 1.42 -2.27 3.78 19.49 330944 A
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-295442A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-295442A1.txt
  • 0.73 -19.27 -49.04 351125 A CENTRAL SCOTT TEL. 6.29 -1.29 7.67 122.09 351126 A CENTURYTEL OF CHESTER, INC. -25.02 -6.35 -19.93 -52.18 351127 C FRONTIER COMMUNICATIONS OF IOWA, INC. -4.62 -4.76 0.14 0.00 351129 C CITIZENS MUTUAL TELEPHONE COOPERATIVE 21.84 -3.67 26.48 58.06 351130 A CLARENCE TEL. CO., INC. -2.10 -4.24 2.24 -27.29 351132 C CLEAR LAKE INDP. TEL. CO. 11.31 -6.89 19.55 49.15 351133 A C-M-L TEL. COOP. ASSN. -19.53 -2.20 -17.72 -49.92 351134 C COLO TEL. CO. -1.75 -5.64 4.12 -2.56 3 - 159 Table 3.32 ILEC High-Cost Loop Support Data Percentage Changes from 2006 to 2007 by Study Area Study Area Code Type Study Area Name Unseparated High Cost Loop Unseparated Number NTS Revenue Support Payment NTS Revenue
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-295442A5.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-295442A5.txt
  • 0.73 -19.27 -49.04 351125 A CENTRAL SCOTT TEL. 6.29 -1.29 7.67 122.09 351126 A CENTURYTEL OF CHESTER, INC. -25.02 -6.35 -19.93 -52.18 351127 C FRONTIER COMMUNICATIONS OF IOWA, INC. -4.62 -4.76 0.14 0.00 351129 C CITIZENS MUTUAL TELEPHONE COOPERATIVE 21.84 -3.67 26.48 58.06 351130 A CLARENCE TEL. CO., INC. -2.10 -4.24 2.24 -27.29 351132 C CLEAR LAKE INDP. TEL. CO. 11.31 -6.89 19.55 49.15 351133 A C-M-L TEL. COOP. ASSN. -19.53 -2.20 -17.72 -49.92 351134 C COLO TEL. CO. -1.75 -5.64 4.12 -2.56 3 - 159 Table 3.32 ILEC High-Cost Loop Support Data Percentage Changes from 2006 to 2007 by Study Area Study Area Code Type Study Area Name Unseparated High Cost Loop Unseparated Number NTS Revenue Support Payment NTS Revenue
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-303886A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-303886A1.txt
  • GLACIER STATE -6.11 -6.75 0.69 -23.63 613011 C INTERIOR TEL CO INC -11.53 -7.19 -4.67 -20.78 613011A C INTERIOR TEL CO INC -5.53 -14.21 10.12 2.12 613012 C ACS-AK JUNEAU -10.34 -8.39 -2.13 0.00 613013 C KETCHIKAN PUBLIC UT 3.91 -5.64 10.12 6.97 613015 C MATANUSKA TEL ASSOC -5.63 -7.85 2.41 -15.16 613016 C MUKLUK TEL CO INC 3.18 -7.31 11.31 6.47 613016A C MUKLUK TEL CO INC -5.29 -13.70 9.75 0.00 613017 C ALASKA TEL CO 1.76 -1.53 3.34 -5.84 613017A C ALASKA TEL CO 1.04 -1.70 2.79 0.00 613018 C NUSHAGAK ELEC & TEL 8.93 -2.08 11.25 12.05 613019 C OTZ TEL COOPERATIVE -0.81 -12.57 13.45 6.28 613020 C ACS-N SITKA -8.68 -4.10 -4.78 -94.56 613022 C ACS-AK GREATLAND
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-303886A5.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-303886A5.txt
  • GLACIER STATE -6.11 -6.75 0.69 -23.63 613011 C INTERIOR TEL CO INC -11.53 -7.19 -4.67 -20.78 613011A C INTERIOR TEL CO INC -5.53 -14.21 10.12 2.12 613012 C ACS-AK JUNEAU -10.34 -8.39 -2.13 0.00 613013 C KETCHIKAN PUBLIC UT 3.91 -5.64 10.12 6.97 613015 C MATANUSKA TEL ASSOC -5.63 -7.85 2.41 -15.16 613016 C MUKLUK TEL CO INC 3.18 -7.31 11.31 6.47 613016A C MUKLUK TEL CO INC -5.29 -13.70 9.75 0.00 613017 C ALASKA TEL CO 1.76 -1.53 3.34 -5.84 613017A C ALASKA TEL CO 1.04 -1.70 2.79 0.00 613018 C NUSHAGAK ELEC & TEL 8.93 -2.08 11.25 12.05 613019 C OTZ TEL COOPERATIVE -0.81 -12.57 13.45 6.28 613020 C ACS-N SITKA -8.68 -4.10 -4.78 -94.56 613022 C ACS-AK GREATLAND
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-311775A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-311775A1.txt
  • 1.17 8.59 10.93 7.09 3.49 1.74 8.84 12.33 7.16 3.24 1.62 8.78 12.03 California 6.60 3.42 1.71 8.31 11.74 8.03 3.50 1.75 9.78 13.28 6.61 3.43 1.71 8.32 11.75 Colorado 8.21 3.49 1.75 9.96 13.46 8.25 3.50 1.75 10.00 13.50 8.21 3.49 1.75 9.96 13.46 Connecticut 7.48 1.18 0.59 8.07 9.25 7.48 3.50 1.75 9.23 12.73 7.48 2.55 1.28 8.76 11.31 Delaware 8.13 0.00 0.00 8.13 8.13 8.13 3.50 1.75 9.88 13.38 8.13 3.23 1.61 9.74 12.97 District of Columbia 5.59 3.50 1.75 7.34 10.84 5.59 3.47 1.73 7.32 10.79 5.59 3.48 1.74 7.33 10.80 Florida 8.19 3.50 1.75 9.94 13.44 8.19 3.50 1.75 9.94 13.44 8.19 3.50 1.75 9.94 13.44 Georgia 8.25 3.38 1.69 9.94 13.32 8.25 3.50 1.75 10.00
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-00-418A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-00-418A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-00-418A1.txt
  • other spectrum is available. DIRECTV Comments at 4-7. Northpoint maintains that its technology requires deployment in the 12.2-12.7 GHz band because it was designed specifically to use existing commercially available consumer and transmission equipment in that band. Northpoint Reply Comments at i-iv, 1-2. Compliance with the ``validation'' limits will be checked by the ITU/BR under Radio Regulation No. S9.35 and S11.31. See also Section 3.1.2.4.6 of the CPM Report. ITU-R Recommendation BO.1503 provides the specification for the software that the BR/ITU would use to verify that a NGSO network meets the EPFD limits. NPRM at ¶ 58. DIRECTV insists that the Commission ensure that any EPFDdown limits adopted fully protect the examples of future BSS links contained in the ITU database,
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-01-88A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-01-88A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-01-88A1.txt
  • emergency warnings. As a result, we are requesting specific cost information below and will evaluate that information carefully. EAS Codes Event Codes. Event codes are three-letter codes used in the transmission of EAS messages that identify the nature of the event or emergency that is causing the EAS activation. A list of authorized event codes is set forth in Section 11.31(e) of the Rules. This list includes codes for national EAS events and tests, which broadcasters and cable systems are required to receive and transmit, and codes for state and local EAS events, which broadcasters and cable systems voluntarily participating in state and local area EAS plans may transmit on an optional basis. NWS requests a number of modifications to the
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-02-27A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-02-27A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-02-27A1.txt
  • , infra. , supra, the band 7100-7300 kHz is allocated to the broadcasting service on an exclusive basis in ITU Regions 1 and 3. "Assignments notified in these bands after 1 April 1992 shall bear a symbol to indicate that the finding will be examined by the Bureau as of 1 April 2007 in accordance with the provisions of No. S11.31." See ITU Radio Regulations, Resolution 21 (Rev.WRC-95), which is entitled "Implementation of changes in frequency allocations between 5900 kHz and 19020 kHz." See WARC-92 Final Acts, international footnotes 521A, 521B, 521C, 528A, 529B, and 534A (later renumbered as S5.134, S5.135 (later deleted), S5.136, S5.143, S5.146, and S5.151); and Resolution No. 21. For example, international footnote S5.146 reads as follows: "The
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-02-64A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-02-64A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-02-64A1.txt
  • period during which both existing and revised codes could be used is not a viable option. Particularly in view of the cost and safety concerns cited above, we are unwilling to revise any existing event codes without being able to afford broadcast stations and cable systems an adequate period of time to ease the transition. b. New Event Codes Section 11.31(e) of the Rules lists the authorized three-letter event codes for national EAS events and tests, which broadcasters and cable systems are required to receive and transmit, and for state and local EAS events, which broadcasters and cable systems voluntarily participating in state and local area EAS plans may transmit on an optional basis. We sought comment in the NPRM on
• 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
  • stations; Low-power TV (LPTV) stations; cable systems; wireless cable systems which may consist of Broadband Radio Service (BRS), or Educational Broadband Service (EBS) stations; and other entities and industries operating on an organized basis during emergencies at the National, State and local levels. It requires that at a minimum all participants use a common EAS protocol, as defined in § 11.31, to send and receive emergency alerts in accordance with the effective dates in the following tables: Wireless Cable Systems (BRS/EBS Stations) [A. Wireless cable systems serving fewer than 5,000 subscribers from a single transmission site must either provide the National level EAS message on all programmed channels--including the required testing--by October 1, 2002, or comply with the following EAS requirements.
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-04-189A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-04-189A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-04-189A1.txt
  • at 12 (May 16, 2003) (PPW May 2003 Report). The Commission has encouraged the monitoring of NWS transmissions. See First Report and Order, 10 FCC Rcd at 1810-11. All EAS decoders are able to directly monitor and decode NWS SAME codes with the addition of any ordinary weather radio receiver and off-the-shelf connections to the EAS decoder. 47 C.F.R. § 11.31(c). All broadcast stations and cable systems have EAS designations that describe their functions within EAS. See 47 C.F.R. § 11.18. 47 C.F.R. § 11.14. 47 C.F.R. §§ 11.21, 11.52(d). The broadcast stations and cable systems must monitor at least two EAS sources to reduce the likelihood of a single point of failure preventing an EAS message from propagating through the
• 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
  • potentially life-saving information under such circumstances. Accordingly, we seek comment on whether our rules should be amended to require EAS participants to transmit EAS messages issued by the governor(s) of the state(s) in which they provide service. We further ask whether, if such a requirement were adopted, we should also adopt an additional originator code for state governors in section 11.31(d) of our rules. We also seek comment on how we can best work with the states to help implement the EAS rules we adopt today as well as to develop the next generation of alert and warning systems. In particular, we note that there is a vital connection between state and local alert and warning and Federal efforts to mitigate
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-05-191A1_Erratum.doc
  • potentially life-saving information under such circumstances. Accordingly, we seek comment on whether our rules should be amended to require EAS participants to transmit EAS messages issued by the governor(s) of the state(s) in which they provide service. We further ask whether, if such a requirement were adopted, we should also adopt an additional originator code for state governors in section 11.31(d) of our rules. We also seek comment on how we can best work with the states to help implement the EAS rules we adopt today as well as to develop the next generation of alert and warning systems. In particular, we note that there is a vital connection between state and local alert and warning and Federal efforts to mitigate
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-07-109A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-07-109A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-07-109A1.txt
  • public. Non-participating National (NN) sources have elected not to participate in the National level EAS and hold an authorization letter to that effect. They may transmit EAS State or Local Area messages. EAS Protocol. All EAS message originators (whether FEMA, NWS, or a state or local authority) currently must transmit messages using the EAS protocol and codes specified in section 11.31 of the Commission's rules. Dedicated equipment currently is required to initiate, receive, and retransmit EAS alerts, and must be installed by every EAS Participant. Sections 11.32 and 11.33 of the Commission's rules set forth minimum requirements for EAS encoders and decoders, respectively, the functions of which can be combined into a single unit referred to as an Encoder/Decoder (ENDEC). In
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-09-2A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-09-2A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-09-2A1.txt
  • include, but are not limited to, specific details regarding the areas that will be affected by the emergency, evacuation orders, detailed descriptions of areas to be evacuated, specific evacuation routes, approved shelters or the way to take shelter in one's home, instructions on how to secure personal property, road closures, and how to obtain relief assistance.'' See 47 C.F.R. §§ 11.31(e), 11.44(a). See also, Amendment of Part 11 of the Commission's Rules Regarding the Emergency Alert System, EB Docket No. 01-66, Report and Order, 17 FCC Rcd 4055, 4065-66, ¶¶ 19, 20 (2002). See NAB/MSTV Reply Comments at 2-3. Id. As discussed below, we conclude that limited sponsorship announcements are permitted as part of nightlight programming. See, infra, Section II, E,
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-10-11A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-10-11A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-10-11A1.txt
  • systems, digital cable systems, wireless cables systems, Direct Broadcast Satellite (DBS) services, Satellite Digital Audio Radio Service (SDARS), and other participating entities. See 47 C.F.R. § 11.1. See 47 C.F.R. Part 11. See 47 C.F.R. § 11.21. All broadcast stations and cable systems have EAS designations that describe their functions within EAS. See 47 C.F.R. § 11.18. 47 C.F.R. § 11.31. 47 C.F.R. §§ 11.32, 11.33. 47 C.F.R. § 11.34(c). EAS equipment also provides a means to automatically interrupt regular programming and is capable of providing warnings in the primary language that is used by the station or cable system. See 47 C.F.R. §§ 11.33(a)(4), 11.51(k)(1), 11.54. See 47 C.F.R. § 11.54 (EAS operation during a national level emergency). See 47
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-10-203A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-10-203A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-10-203A1.txt
  • (footnotes omitted). AASHTO Letter at 3. AASHTO Comments at 7 (footnotes omitted). AASHTO Letter at 3. These requests did not appear in AASHTO's subsequent petition for rulemaking. The SAME transmissions concern National Weather Service severe weather alerts and warnings. They are equivalent to many of the ``Event codes'' used in the Commission's Emergency Alert System rules. See 47 C.F.R. § 11.31(e). . HIS Petition at 9. Id. at 10. Id. Id. at 4, quoting Commercial Mobile Alert System, PS Docket 07-287, Third Report and Order, 23 FCC Rcd 12561, 12563 ¶ 4 (2008). Id. at 4. Id. at 4-5. See, e.g., City of Santa Monica, CA; Florida's Turnpike Enterprise; Texas DOT; Utah DOT; City of Miramar, FL; Rhode Island DOT; Emanuel
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-11-12A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-11-12A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-11-12A1.txt
  • we do not adopt that code or any other location code here. Rather, we delegate authority to the Bureau to determine, in conjunction with FEMA and other EAS stakeholders, the specific location code or codes to be used for the first national EAS test and for subsequent tests. Required Relay of EAN in Conjunction with a National Location Code Section 11.31(c) of the Commission's rules requires that the header of all EAS alerts contain a code to indicate the location of the emergency. This location code is a 6 digit ASCII code that utilizes the five character numbers assigned to the various states, counties, cities and portions of counties. There is no national code as such, and the rule section notes
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-11-136A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-11-136A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-11-136A1.txt
  • Relief, ET Docket No. 04-296, Second Report and Order and Further Notice of Proposed Rulemaking, 22 FCC Rcd 13275, 13280-83, paras. 11-14 (2007) (Second Report and Order). See Third FNPRM, 26 FCC Rcd 8149, 8152-53, para. 3. See Memorandum, Presidential Communications with the General Public During Periods of National Emergency, The White House (Sept. 15, 1995). See 47 C.F.R. § 11.31. Under this protocol, an EAS alert uses a four-part message: (1) preamble and EAS header codes (these codes contain information regarding the identity of the sender, the type of emergency, its location, and the valid time period of the alert); (2) audio attention signal; (3) message; and (4) preamble and ``end of message'' (EOM) codes. See id. § 11.31(a). Although
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-11-82A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-11-82A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-11-82A1.txt
  • FCC-filed and approved versions of the State and Local Area EAS Plans. Miscellaneous Part 11 Revisions Not Related to CAP: We seek comment on whether the Commission can delete some or all of the current provisions relating to the Attention Signal in sections 11.32(9) and 11.33(b) of the rules and instead apply the minimal standard currently set forth in section 11.31(a)(2) or whether we should delete the Attention Signal from the Part 11 rules altogether. We seek comment on whether the introduction of CAP to the existing technical framework of the EAS can improve access to emergency information to persons with disabilities. BACKGROUND Congress established the Commission for the purposes of, among other things, the national defense and the promotion of
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-12-41A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-12-41A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-12-41A1.txt
  • v. 1.2 USA Integrated Public Alert and Warning System Profile Version 1.0 (Oct. 13, 2009), into EAS alert messages that comply with the EAS Protocol, such that the Preamble and EAS Header Codes, audio Attention Signal, audio message, and Preamble and EAS End of Message (EOM) Codes of such messages are rendered equivalent to the EAS Protocol (set forth in §11.31), in accordance with the technical specifications governing such conversion process set forth in the EAS-CAP Industry Group's (ECIG) Recommendations for a CAP EAS Implementation Guide, Version 1.0 (May 17, 2010) (except that any and all specifications set forth therein related to gubernatorial ``must carry'' shall not be followed, and that EAS Participants may adhere to the specifications related to text-to-speech
• 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
  • are set forth in section 11.32. In the Third FNPRM, we sought comment on several CAP-related proposals involving these requirements that were raised by CSRIC and parties responding to the Part 11 Public Notice. Section 11.32(a). Section 11.32(a) specifies the minimum requirements for encoders. This section requires that encoders be capable of encoding the EAS Protocol set forth in section 11.31, providing the EAS code transmission requirements described in section 11.51, and meeting various other specifications. In the Third FNPRM, we explained that CSRIC had recommended that the Commission ``[m]odify [the] EAS encoder minimum requirement'' so that ``EAS encoder[s] [are] capable of [r]endering a fully CAP compliant message.'' To the extent that CSRIC was proposing that EAS encoders be required to
• http://transition.fcc.gov/Bureaus/Engineering_Technology/Orders/2000/fcc00418.doc http://transition.fcc.gov/Bureaus/Engineering_Technology/Orders/2000/fcc00418.pdf http://transition.fcc.gov/Bureaus/Engineering_Technology/Orders/2000/fcc00418.txt
  • other spectrum is available. DIRECTV Comments at 4-7. Northpoint maintains that its technology requires deployment in the 12.2-12.7 GHz band because it was designed specifically to use existing commercially available consumer and transmission equipment in that band. Northpoint Reply Comments at i-iv, 1-2. Compliance with the ``validation'' limits will be checked by the ITU/BR under Radio Regulation No. S9.35 and S11.31. See also Section 3.1.2.4.6 of the CPM Report. ITU-R Recommendation BO.1503 provides the specification for the software that the BR/ITU would use to verify that a NGSO network meets the EPFD limits. NPRM at ¶ 58. DIRECTV insists that the Commission ensure that any EPFDdown limits adopted fully protect the examples of future BSS links contained in the ITU database,
• http://transition.fcc.gov/Bureaus/Mass_Media/Orders/2000/fcc00019.doc http://transition.fcc.gov/Bureaus/Mass_Media/Orders/2000/fcc00019.pdf
  • to safety will last, and the originator of the alert message. Id. at ¶ 2, n. 4. National level EAS messages and EAS tests must be forwarded to the public upon receipt. EAS participants transmit state and local messages on a voluntary basis. Id. at ¶ 2. Specifically, EAS equipment must be able to perform the functions described in sections 11.31, 11.32, 11.33, 11.51, 11.52, and 11.61 of our rules. Class D noncommercial educational FM and LPTV stations are not required to install or operate encoders as defined in section 11.32, to have equipment capable of generating the EAS codes and Attention Signal specified in section 11.31, or to perform certain parts of EAS tests. Accordingly, we amend section 11.11(b) to
• http://transition.fcc.gov/eb/FieldNotices/2003/DOC-277675A1.html
  • assessed under Section 503(b) of the Act, provides that "[t]he term 'repeated', when used with reference to the commission or omission of any act, means the commission or omission of such act more than once or, if such commission or omission is continuous, for more than one day." 47 C.F.R. S: 11.35(a). 47 C.F.R. S:S: 11.35(a), (b). 47 C.F.R. S: 11.31. Some EAS units can be programmed to print an out-of-date message for received tests prior to discarding them. However, there were no such messages in station KMZE's files. 12 FCC Rcd 17087 (1997), recon. denied, 15 FCC Rcd 303 (1999); 47 C.F.R. S:1.80. 47 U.S.C. S: 503(b)(2)(E). 47 U.S.C. S: 503(b), 47 C.F.R. S:S: 0.111, 0.311, 0.314, 1.80, 11.35(a). 8
• http://transition.fcc.gov/eb/FieldNotices/2003/DOC-277877A1.html
  • assessed under Section 503(b) of the Act, provides that "[t]he term 'repeated', when used with reference to the commission or omission of any act, means the commission or omission of such act more than once or, if such commission or omission is continuous, for more than one day." 47 C.F.R. S: 11.35(a). 47 C.F.R. S:S: 11.35(a), (b). 47 C.F.R. S: 11.31. Some EAS units can be programmed to print an out-of-date message for received tests prior to discarding them. However, there were no such messages in station KMZE's files. 12 FCC Rcd 17087 (1997), recon. denied, 15 FCC Rcd 303 (1999); 47 C.F.R. S:1.80. 47 U.S.C. S: 503(b)(2)(E). 47 U.S.C. S: 503(b), 47 C.F.R. S:S: 0.111, 0.311, 0.314, 1.80, 11.35(a). 8
• http://transition.fcc.gov/eb/Orders/2001/fcc01088.doc http://transition.fcc.gov/eb/Orders/2001/fcc01088.html
  • emergency warnings. As a result, we are requesting specific cost information below and will evaluate that information carefully. EAS Codes Event Codes. Event codes are three-letter codes used in the transmission of EAS messages that identify the nature of the event or emergency that is causing the EAS activation. A list of authorized event codes is set forth in Section 11.31(e) of the Rules. This list includes codes for national EAS events and tests, which broadcasters and cable systems are required to receive and transmit, and codes for state and local EAS events, which broadcasters and cable systems voluntarily participating in state and local area EAS plans may transmit on an optional basis. NWS requests a number of modifications to the
• http://transition.fcc.gov/eb/Orders/2002/FCC-02-64A1.html
  • during which both existing and revised codes could be used is not a viable option. Particularly in view of the cost and safety concerns cited above, we are unwilling to revise any existing event codes without being able to afford broadcast stations and cable systems an adequate period of time to ease the transition. b. New Event Codes 11. Section 11.31(e) of the Rules lists the authorized three-letter event codes for national EAS events and tests, which broadcasters and cable systems are required to receive and transmit, and for state and local EAS events, which broadcasters and cable systems voluntarily participating in state and local area EAS plans may transmit on an optional basis.24 We sought comment in the NPRM on
• http://transition.fcc.gov/eb/Orders/2004/FCC-04-189A1.html
  • (May 16, 2003) (PPW May 2003 Report). 28 The Commission has encouraged the monitoring of NWS transmissions. See First Report and Order, 10 FCC Rcd at 1810- 11. All EAS decoders are able to directly monitor and decode NWS SAME codes with the addition of any ordinary weather radio receiver and off-the-shelf connections to the EAS decoder. 29 47 C.F.R. 11.31(c). 30 All broadcast stations and cable systems have EAS designations that describe their functions within EAS. See 47 C.F.R. 11.18. 31 47 C.F.R. 11.14. 32 47 C.F.R. 11.21, 11.52(d). The broadcast stations and cable systems must monitor at least two EAS sources to reduce the likelihood of a single point of failure preventing an EAS message from propagating through the
• http://transition.fcc.gov/eb/Orders/2005/FCC-05-191A1.html
  • potentially life-saving information under such circumstances. Accordingly, we seek comment on whether our rules should be amended to require EAS participants to transmit EAS messages issued by the governor(s) of the state(s) in which they provide service. We further ask whether, if such a requirement were adopted, we should also adopt an additional originator code for state governors in section 11.31(d) of our rules. We also seek comment on how we can best work with the states to help implement the EAS rules we adopt today as well as to develop the next generation of alert and warning systems. In particular, we note that there is a vital connection between state and local alert and warning and Federal efforts to mitigate
• http://transition.fcc.gov/eb/Orders/2008/DA-08-1394A1.html
  • of record. FEDERAL COMMUNICATIONS COMMISSION Dennis P. Carlton Regional Director, South Central Region Enforcement Bureau 47 C.F.R. S: 11.35(a). Notice of Apparent Liability for Forfeiture, NAL/Acct. No. 200732500006 (Enf. Bur., Dallas Office, October 23, 2007) ("NAL"). 47 U.S.C. S: 503(b). 47 C.F.R. S: 1.80. 47 U.S.C. S: 503(b)(2)(E). 47 C.F.R. S: 11.35(a). 47 C.F.R. S:S: 11.35(a), (b). 47 C.F.R. S: 11.31. Some EAS units can be programmed to print an out-of-date message for received tests prior to discarding them. However, there were no such messages in station KMZE's files. According to Omni's program logs, no weekly tests were transmitted between January 28 and February 17, 2008. Licensees are not informed of the exact time at which monthly EAS tests are sent.
• http://transition.fcc.gov/eb/Orders/2008/DA-08-1717A1.html
  • participating national EAS source ("EAS Participant") unless the station affirmatively requests authority to not participate. 47 C.F.R. S:S: 11.11 and 11.41. See 47 C.F.R. S: 11.1 et. seq. The EAS protocol consists of four parts: Preamble and EAS Header Codes; two-tone audio Attention Signal ("EAS tone"); message; and Preamble and EAS End of Message ("EOM") Codes. See 47 C.F.R. S: 11.31(a). 47 C.F.R. S:S: 11.32, 11.33. The functions of the EAS encoder and decoder may be combined into a single unit referred to as an Encoder/Decoder provided that the unit complies with all specifications in Part 11 of the Commission's Rules. See 47.C.F.R. S: 11.34(c). 47 C.F.R. S: 11.32(a). 47 C.F.R. S: 11.32(a)(9)(v). 47 C.F.R. S: 11.61(a). The Emergency Alert System
• http://transition.fcc.gov/eb/Orders/2009/DA-09-1958A1.html
  • Alabama 36467. FEDERAL COMMUNICATIONS COMMISSION Kathryn S. Berthot Chief, Spectrum Enforcement Division Enforcement Bureau File No. BRED-20040122AEE. The Commission granted Opp Educational Broadcasting Foundation a license renewal for station WJIF on January 31, 2007. The license expires on April 1, 2012. 47 C.F.R. S:S: 11.35 and 11.61(a). 47 C.F. R. S: 73.1015. 47 C.F.R. S:S: 11.1 - 11.61. 47 C.F.R. S:11.31. 47 C.F.R. S:11.11(a). 47 C.F.R. S: 11.61(a). See Letter from Kathryn S. Berthot, Chief, Spectrum Enforcement Division, Enforcement Bureau, Federal Communications Commission to Mr. Haywood F. Nawlin, Administrator, Opp Educational Broadcasting Foundation, Licensee of Radio Station WJIF (November 4, 2008). 47 C.F.R. S: 73.1820. See Letter from Haywood F. Nawlins, WJIF Radio to Kathryn S. Berthot Chief, Spectrum Enforcement Division,
• http://transition.fcc.gov/eb/Orders/2010/DA-10-796A1.html
  • and regular mail, to Telefutura Partnership of Douglas, at its address of record. FEDERAL COMMUNICATIONS COMMISSION William R. Zears, Jr. District Director San Diego Office Western Region Enforcement Bureau 47 C.F.R. S: 11.35. 47 U.S.C. S: 503(b). 47 C.F.R. S: 11.33(a). The EAS decoder must at a minimum be capable of decoding the EAS protocol described in 47 C.F.R. S: 11.31. Section 312(f)(1) of the Act, 47 U.S.C. S: 312(f)(1), which applies to violations for which forfeitures are assessed under Section 503(b) of the Act, provides that "[t]he term `willful', when used with reference to the commission or omission of any act, means the conscious and deliberate commission or omission of such act, irrespective of any intent to violate any provision
• http://transition.fcc.gov/eb/Public_Notices/da012273.html http://transition.fcc.gov/eb/Public_Notices/da012273.pdf
  • 73.1745 (Unauthorized Operation), 73.1870 (Chief Operator) and 73.3526 (Local Public Inspection File for Commercial Stations). Atlanta, GA District Office (8/9/01). * Bartow Broadcasting Co., Inc. Other violations: 47 C.F.R. 11.52 (EAS Code and Attention Signal Monitoring Requirements), 11.61(Tests of EAS Procedures), 73.49 (AM Transmission System Fencing Requirements) and 73.1840 (Retention of Logs). Tampa, FL District Office (8/22/01). * 47 C.F.R. 11.31 EAS Protocol * Agpal Broadcasting Inc., KPPT(AM/FM) Toledo, Oregon. Other violations: 47 C.F.R. 73.3526 (Local Public Inspection File for Commercial Stations). Portland, OR Resident Agent Office (8/22/01). * 47 C.F.R. 11.35 Equipment Operational Readiness * Clarke Broadcasting Corporation, KVML/KZSQ, Sonora, CA. Other violations: 47 C.F.R. 11.52 (EAS Code and Attention Signal Monitoring Requirements), 11.61 (Tests of EAS Procedures) and 73.1820
• http://transition.fcc.gov/eb/bc-chklsts/EB18LPFM06_2008.pdf
  • at their normal duty stations, can be alerted immediately when EAS messages are received. Only one EAS decoder is required for combined facilities operating from one common location, such as a co-owned and co-located AM and FM studio. All decoder devices are to be certified by the Commission in accordance with Part 2 Subpart J of the Commission's rules. [See 11.31, 11.33, 11.34, 11.35 and 11.52] 27. CERTIFIED EQUIPMENT: Does the station use only certified EAS equipment at each location utilized for EAS monitoring? [See 11.34] 28. EQUIPMENT STATUS: Is the required EAS decoding/receiving equipment currently installed and in operational condition? [See 11.35] 29. INSTANTANEOUS ALERT RECEPTION: For manually operated EAS decoding equipment, is the decoder installed in a way that
• http://transition.fcc.gov/pshs/docs/services/eas/Second.pdf
  • systems; wireless cable systems which may consist of Multipoint Distribution Service (MDS), Multichannel Multipoint Distribution Service (MMDS), or Instructional Television Fixed Service (ITFS) stations; and other entities and industries operating on an organized basis during emergencies at the National, State and local levels. It requires that at a minimum all participants use a common EAS protocol, as defined in § 11.31, to send and receive emergency alerts in accordance with the effective dates in the following tables: 2 TIMETABLE BROADCAST STATIONS REQUIREMENT AM & FM TV FM CLASS D LPTV1 Two-tone encoder2,3 Y Y N N Two-tone decoder4,5 Y Y Y Y EAS decoder Y 1/1/97 Y 1/1/97 Y 1/1/97 Y 1/1/97 EAS encoder Y 1/1/97 Y 1/1/97 N N Audio
• http://wireless.fcc.gov/auctions/53/releases/fc000418.pdf http://wireless.fcc.gov/auctions/53/releases/fc000418.txt
  • BSS systems will be able to take into account the NGSO FSS interference environment.368 173. In the following sub-sections, we discuss particular issues with respect to NGSO FSS operations in the 12.2-12.7 GHz band, such as single-entry EPFDdown limits, verification of compliance 364 Compliance with the "validation" limits will be checked by the ITU/BR under Radio Regulation No. S9.35 and S11.31. See also Section 3.1.2.4.6 of the CPM Report. 365 ITU-R Recommendation BO.1503 provides the specification for the software that the BR/ITU would use to verify that a NGSO network meets the EPFD limits. 366 NPRM at ¶ 58. 367 DIRECTV insists that the Commission ensure that any EPFDdown limits adopted fully protect the examples of future BSS links contained in
• http://www.fcc.gov/Bureaus/Common_Carrier/Reports/FCC-State_Link/IAD/ref99.pdf
  • 12.61 8.78% Idaho 20.45 11.24 3.03% Illinois 15.78 13.11 0.63% Indiana 20.20 12.70 3.04% Iowa 11.56 9.12 5.98% Kansas 11.29 7.53 5.40% Kentucky 17.46 10.84 8.36% Louisiana 28.66 15.09 5.42% Maine 16.93 10.42 5.21% Maryland 9.00 6.00 0.18% Massachusetts 23.28 12.21 0.06% Michigan 14.19 8.22 1.82% Minnesota 17.69 11.09 12.79% Mississippi 23.06 14.18 6.08% Missouri 12.98 7.71 15.57% Montana 22.72 11.31 15.60% Nebraska 19.15 11.95 9.00% Nevada 14.71 10.57 9.33% New Hampshire 18.47 8.61 2.46% New Jersey 15.50 7.80 3.17% New Mexico 21.06 13.76 3.85% New York 18.84 9.73 1.11% North Carolina 27.19 11.86 7.73% North Dakota 15.02 11.09 14.68% Ohio 25.48 15.96 0.34% Oklahoma 18.88 12.44 7.65% Oregon 16.78 10.76 4.42% Pennsylvania 18.78 10.73 4.09% South Carolina 23.02 11.76 15.42%
• http://www.fcc.gov/Bureaus/Common_Carrier/Reports/FCC-State_Link/IAD/ror02.pdf
  • 22.13 10.65 23Concord Telephone Co. 16.51 11.78 44.49 14.69 181.82 14.67 14.90 24El Paso Telephone Co. 17.75 9.82 88.57 12.06 14.01 12.20 25Farmers Telephone Cooperative, Inc 11.48 11.78 14.97 7.07 10.08 8.86 26Fort Bend Telephone Co. dba TXU Communications 12.38 12.65 15.54 13.01 4.70 11.01 27Fort Mill Telephone Company 13.80 11.92 21.93 3.91 49.78 18.83 28Gallatin River Communications, LLC 13.64 11.31 9.58 24.56 15.09 22.17 29Gulf Telephone Company 13.31 11.39 15.73 11.68 17.13 15.16 30Hargray Telephone Company 9.23 14.30 6.94 (0.03) 9.25 5.09 31Home Telephone Company, Inc 9.63 11.77 14.97 (0.21) 6.17 0.91 32Horry Telephone Cooperative, Inc 10.83 11.80 14.90 9.39 6.68 7.77 33Illinois Consolidated Telephone Company 23.60 9.37 10.77 6.80 30.67 23.49 34Lancaster Telephone Company 8.97 12.10 (1.64) 8.74 1.23
• http://www.fcc.gov/Bureaus/Common_Carrier/Reports/FCC-State_Link/IAD/ror96.pdf
  • 42.02 20.11 77GTE NORTH INCORPORATED - NEBRASKA 13.29 11.94 10.94 17.75 (19.21) 10.37 15.73 78GTE NORTHWEST INCORPORATED - ID/MT 12.08 11.95 1.96 14.46 (4.99) 12.90 13.60 79GTE NORTHWEST INCORPORATED - WA/OR/CA(WC) 12.19 11.96 3.35 14.88 (54.03) 12.97 14.12 80GTE NORTH INCORPORATED - OHIO 9.96 11.95 9.21 9.13 (54.24) 3.98 7.63 81GTE NORTH INCORPORATED - PENNSYLVANIA 10.44 11.95 7.32 8.95 (106.79) 11.31 9.29 82GTE SOUTH INCORPORATED - ALABAMA 12.40 11.96 9.29 14.53 112.46 10.61 13.60 83GTE SOUTH INCORPORATED - GEORGIA 11.29 11.97 13.47 10.32 (22.75) 8.35 9.58 84GTE SOUTH INCORPORATED - KENTUCKY 11.88 11.95 10.48 12.56 (45.07) 12.24 12.13 85GTE SOUTH INCORPORATED - NORTH CAROLINA 12.89 11.96 16.35 11.78 20.52 18.06 12.52 86GTE SOUTH INCORPORATED - SOUTH CAROLINA 8.93 11.96 6.88 8.16
• http://www.fcc.gov/Bureaus/Common_Carrier/Reports/FCC-State_Link/IAD/ror97.pdf
  • 15.23 11.64 9.94 14.55 2,078.04 34.52 22.02 18CHILLICOTHE TELEPHONE COMPANY, THE 3.66 11.25 (2.97) 11.83 10.43 11.54 19CONCORD TELEPHONE CO. 14.50 11.72 11.06 24.04 21.54 22.99 20FORT MILL TELEPHONE COMPANY 1/ 16.45 12.13 22.48 39.64 33.33 37.20 21HOME TELEPHONE COMPANY 1/ 16.98 11.61 21.13 19.84 66.33 25.86 22HORRY TELEPHONE CO. 13.48 11.60 1.86 8.64 26.30 17.13 23ILLINOIS CONSOLIDATED TELEPHONE COMPANY 11.31 12.18 12.97 13.05 7.16 9.07 24LANCASTER TELEPHONE COMPANY 1/ 12.08 12.33 15.81 9.48 15.38 10.73 25LUFKIN-CONROE TELEPHONE EXCHANGE 12.07 10.23 8.44 17.57 30.96 24.74 26PUERTO RICO TELEPHONE COMPANY 11.89 11.60 14.32 12.98 (239.32) 12.82 12.26 27ROCK HILL TELEPHONE COMPANY 1/ 13.83 12.31 15.58 19.88 2.30 16.25 28ROSEVILLE TELEPHONE COMPANY 11.19 11.60 11.59 9.21 (1,481.71) 11.74 10.33 29TELEPHONE UTILITIES EXCHANGE CARRIER
• http://www.fcc.gov/Bureaus/Common_Carrier/Reports/FCC-State_Link/Monitor/mr03-3.pdf
  • 361445 C CENTURYTEL OF MINNESOTA, INC. 3.32 0.50 2.81 1.79 361448 A OSAKIS TELEPHONE COMPANY 15.32 2.50 12.51 INFINITE 361450 A PARK REGION MUTUAL TEL. CO. 18.00 5.58 11.77 74.37 361451 C PAUL BUNYAN RURAL TEL. COOP. 37.52 4.91 31.08 134.05 361453 C PEOPLES TELEPHONE COMPANY - MN 2.49 2.54 -0.04 0.07 361454 C PINE ISLAND TELEPHONE COMPANY 13.27 1.76 11.31 48.81 361456 C UNITED TELEPHONE CO OF MINN 1.01 2.71 -1.65 0.00 361472 A REDWOOD COUNTY TEL. CO. 19.37 7.04 11.51 70.37 361474 A ROTHSAY TELEPHONE COMPANY INC. 6.56 -6.31 13.74 53.60 361475 A RUNESTONE TEL. ASSN. 9.85 -1.10 11.07 41.41 361476 A SACRED HEART TEL. CO. 7.58 -3.00 10.91 36.27 361479 A SCOTT RICE TEL. CO. DBA INTEGRA TELECOM
• http://www.fcc.gov/Bureaus/Common_Carrier/Reports/FCC-State_Link/Monitor/mr04-3.pdf
  • 3.73 6.23 482255 3-RIVERS TEL. COOPERATIVE INC. 2.72 0.65 2.06 0.66 482257 C TRIANGLE TEL. COOPERATIVE ASSN. INC. 24.64 0.38 24.16 79.28 483308 C BLACKFOOT TELEPHONE COOPERATIVE, INC. - CFT (CLARK FORK) -5.56 2.42 -7.79 -12.01 483310 C CENTRAL MONTANA COMMUNICATIONS, INC. 5.95 -0.54 6.53 8.48 484322 C CITIZENS TEL CO OF MT DBA FRONTIER COMM OF MT -11.43 -0.13 -11.31 -33.86 485104 C QWEST CORPORATION - MT -0.01 -2.99 3.07 0.00 NEBRASKA Total -0.92 -4.70 3.97 9.03 371128 C CITIZENS TEL CO OF NE DBA FRONTIER COMM OF NE -5.45 -6.73 1.37 0.00 371516 C ARAPAHOE TELEPHONE COMPANY 3.05 5.51 -2.33 -2.33 371517 C ARLINGTON TELEPHONE COMPANY 4.77 -1.11 5.94 7.03 371518 C ELSIE COMMUNICATIONS, INC. 5.35 -3.57 9.25 6.15
• http://www.fcc.gov/Bureaus/Common_Carrier/Reports/FCC-State_Link/Monitor/mr98-9.pdf
  • Percentage of Customers Dissatisfied Company AmeritechBell AtlanticBellSouth NYNEX Pacific SBC US West GTE Overall:Residential 2.9 2.25 6.28 3.83 3.99 7.12 8.67 3.07 Small Business 2.36 5.96 12.1 3.74 5.39 6.72 12.38 5.97 Large Business 10.86 9.18 3.92 20.24 6.21 8.21 8 1.51 Installations: Residential 4.13 8.66 5.19 14.13 3.10 5.83 5.33 7.31 Small Business 8.20 6.48 3.47 20.53 4.54 6.89 11.31 13.39 Large Business 9.38 11.36 NA 23.42 7.42 11.21 23.00 0.74 Repairs:Residential 9.55 20.69 8.72 27.33 7.41 8.44 10.50 13.43 Small Business 10.88 9.20 4.32 23.37 7.61 6.57 12.80 14.11 Large Business 11.83 13.17 NA 30.07 7.93 7.94 22.00 1.61 Business Office: Residential 5.94 11.17 5.21 18.90 2.07 7.15 2.17 1.88 Small Business 6.02 5.22 2.31 15.86 4.02 6.64 3.56
• http://www.fcc.gov/Bureaus/Common_Carrier/Reports/FCC-State_Link/Monitor/mrs01-0.pdf
  • 4.05 35.68 361357 C BLACKDUCK TEL. CO. 7.60 11.89 -3.83 -14.15 361358 A BLUE EARTH VALLEY TEL. CO. 1.55 4.65 -2.96 -100.00 361362 A BRIDGEWATER TEL. CO. 18.65 9.66 8.20 0.00 361365 A CALLAWAY TEL. CO. 15.39 2.55 12.53 72.61 361367 C FRONTIER COMM. OF MINNESOTA, INC. -5.52 3.06 -8.33 0.00 361370 C CLARA CITY TEL. EXCH. CO. 11.37 0.06 11.31 54.45 361372 A CLEMENTS TEL. CO. 4.18 2.36 1.78 4.46 3 - 201 Table 3.28 High-Cost Loop Fund Percentage Changes from 1998 to 1999 by Study Area Unseparated Universal Study Unseparated Number NTS Revenue Service Fund Area NTS Revenue of Requirement Payments in Code Type Study Area Name Requirement Loops per Loop Later Year* MINNESOTA (CONT.) 361373 A CONSOLIDATED TEL.
• http://www.fcc.gov/Bureaus/Common_Carrier/Reports/FCC-State_Link/Monitor/mrs02-0.pdf
  • 9.38 65.79 220386 C STANDARD TEL. CO. 9.39 3.49 5.70 23.77 220387 A FRONTIER COMM. OF GEORGIA, INC. 6.95 5.06 1.80 0.00 220389 A TRENTON TEL. CO. 12.76 7.66 4.73 0.00 220392 C WAVERLY HALL TEL. CO., INC. -6.65 6.51 -12.36 -20.93 220394 C WILKES TEL. & ELECTRIC CO. 7.66 1.21 6.37 90.69 220395 A ACCUCOMM TELECOMMUNICATIONS, INC. 15.40 3.68 11.31 INFINITE 223036 C GEORGIA ALLTEL TELECOM 4.79 3.78 0.97 20.30 223037 C ALLTEL GEORGIA COMMUNICATIONS CORP. 7.72 4.34 3.23 38.72 225192 C SOUTHERN BELL-GA 1.53 0.89 0.64 0.00 TOTAL: GUAM -6.67 -4.18 -2.60 0.00 663800 C GUAM TELEPHONE AUTHORITY -6.67 -4.18 -2.60 0.00 TOTAL: HAWAII -0.27 0.15 -0.42 131.80 623021 C SANDWICH ISLES COMMUNICATIONS, INC. 127.28 79.73 26.46 131.80 623100
• http://www.fcc.gov/Bureaus/Engineering_Technology/Orders/2000/fcc00418.doc http://www.fcc.gov/Bureaus/Engineering_Technology/Orders/2000/fcc00418.pdf http://www.fcc.gov/Bureaus/Engineering_Technology/Orders/2000/fcc00418.txt
  • other spectrum is available. DIRECTV Comments at 4-7. Northpoint maintains that its technology requires deployment in the 12.2-12.7 GHz band because it was designed specifically to use existing commercially available consumer and transmission equipment in that band. Northpoint Reply Comments at i-iv, 1-2. Compliance with the ``validation'' limits will be checked by the ITU/BR under Radio Regulation No. S9.35 and S11.31. See also Section 3.1.2.4.6 of the CPM Report. ITU-R Recommendation BO.1503 provides the specification for the software that the BR/ITU would use to verify that a NGSO network meets the EPFD limits. NPRM at ¶ 58. DIRECTV insists that the Commission ensure that any EPFDdown limits adopted fully protect the examples of future BSS links contained in the ITU database,
• http://www.fcc.gov/Bureaus/Mass_Media/Orders/2000/fc00019a.doc
  • systems; wireless cable systems which may consist of Multipoint Distribution Service (MDS), Multichannel Multipoint Distribution Service (MMDS), or Instructional Television Fixed Service (ITFS) stations; and other entities and industries operating on an organized basis during emergencies at the National, State and local levels. It requires that at a minimum all participants use a common EAS protocol, as defined in § 11.31, to send and receive emergency alerts in accordance with the effective dates in the following tables: A new column is inserted into the ``Timetable - Broadcast Stations'' table in §11.11 as follows: Requirement AM & FM TV FM Class D LPTV LPFM * * * * * * * * * * * * * * * N Y Y
• http://www.fcc.gov/Bureaus/Mass_Media/Orders/2000/fcc00019.doc http://www.fcc.gov/Bureaus/Mass_Media/Orders/2000/fcc00019.pdf http://www.fcc.gov/Bureaus/Mass_Media/Orders/2000/fcc00019.txt
  • to safety will last, and the originator of the alert message. Id. at ¶ 2, n. 4. National level EAS messages and EAS tests must be forwarded to the public upon receipt. EAS participants transmit state and local messages on a voluntary basis. Id. at ¶ 2. Specifically, EAS equipment must be able to perform the functions described in sections 11.31, 11.32, 11.33, 11.51, 11.52, and 11.61 of our rules. Class D noncommercial educational FM and LPTV stations are not required to install or operate encoders as defined in section 11.32, to have equipment capable of generating the EAS codes and Attention Signal specified in section 11.31, or to perform certain parts of EAS tests. Accordingly, we amend section 11.11(b) to
• http://www.fcc.gov/eb/FieldNotices/2003/DOC-277675A1.html
  • assessed under Section 503(b) of the Act, provides that "[t]he term 'repeated', when used with reference to the commission or omission of any act, means the commission or omission of such act more than once or, if such commission or omission is continuous, for more than one day." 47 C.F.R. S: 11.35(a). 47 C.F.R. S:S: 11.35(a), (b). 47 C.F.R. S: 11.31. Some EAS units can be programmed to print an out-of-date message for received tests prior to discarding them. However, there were no such messages in station KMZE's files. 12 FCC Rcd 17087 (1997), recon. denied, 15 FCC Rcd 303 (1999); 47 C.F.R. S:1.80. 47 U.S.C. S: 503(b)(2)(E). 47 U.S.C. S: 503(b), 47 C.F.R. S:S: 0.111, 0.311, 0.314, 1.80, 11.35(a). 8
• http://www.fcc.gov/eb/FieldNotices/2003/DOC-277877A1.html
  • assessed under Section 503(b) of the Act, provides that "[t]he term 'repeated', when used with reference to the commission or omission of any act, means the commission or omission of such act more than once or, if such commission or omission is continuous, for more than one day." 47 C.F.R. S: 11.35(a). 47 C.F.R. S:S: 11.35(a), (b). 47 C.F.R. S: 11.31. Some EAS units can be programmed to print an out-of-date message for received tests prior to discarding them. However, there were no such messages in station KMZE's files. 12 FCC Rcd 17087 (1997), recon. denied, 15 FCC Rcd 303 (1999); 47 C.F.R. S:1.80. 47 U.S.C. S: 503(b)(2)(E). 47 U.S.C. S: 503(b), 47 C.F.R. S:S: 0.111, 0.311, 0.314, 1.80, 11.35(a). 8
• http://www.fcc.gov/eb/Orders/2001/fcc01088.doc http://www.fcc.gov/eb/Orders/2001/fcc01088.html
  • emergency warnings. As a result, we are requesting specific cost information below and will evaluate that information carefully. EAS Codes Event Codes. Event codes are three-letter codes used in the transmission of EAS messages that identify the nature of the event or emergency that is causing the EAS activation. A list of authorized event codes is set forth in Section 11.31(e) of the Rules. This list includes codes for national EAS events and tests, which broadcasters and cable systems are required to receive and transmit, and codes for state and local EAS events, which broadcasters and cable systems voluntarily participating in state and local area EAS plans may transmit on an optional basis. NWS requests a number of modifications to the
• http://www.fcc.gov/eb/Orders/2002/FCC-02-64A1.html
  • during which both existing and revised codes could be used is not a viable option. Particularly in view of the cost and safety concerns cited above, we are unwilling to revise any existing event codes without being able to afford broadcast stations and cable systems an adequate period of time to ease the transition. b. New Event Codes 11. Section 11.31(e) of the Rules lists the authorized three-letter event codes for national EAS events and tests, which broadcasters and cable systems are required to receive and transmit, and for state and local EAS events, which broadcasters and cable systems voluntarily participating in state and local area EAS plans may transmit on an optional basis.24 We sought comment in the NPRM on
• http://www.fcc.gov/eb/Orders/2004/FCC-04-189A1.html
  • (May 16, 2003) (PPW May 2003 Report). 28 The Commission has encouraged the monitoring of NWS transmissions. See First Report and Order, 10 FCC Rcd at 1810- 11. All EAS decoders are able to directly monitor and decode NWS SAME codes with the addition of any ordinary weather radio receiver and off-the-shelf connections to the EAS decoder. 29 47 C.F.R. 11.31(c). 30 All broadcast stations and cable systems have EAS designations that describe their functions within EAS. See 47 C.F.R. 11.18. 31 47 C.F.R. 11.14. 32 47 C.F.R. 11.21, 11.52(d). The broadcast stations and cable systems must monitor at least two EAS sources to reduce the likelihood of a single point of failure preventing an EAS message from propagating through the
• http://www.fcc.gov/eb/Orders/2005/FCC-05-191A1.html
  • potentially life-saving information under such circumstances. Accordingly, we seek comment on whether our rules should be amended to require EAS participants to transmit EAS messages issued by the governor(s) of the state(s) in which they provide service. We further ask whether, if such a requirement were adopted, we should also adopt an additional originator code for state governors in section 11.31(d) of our rules. We also seek comment on how we can best work with the states to help implement the EAS rules we adopt today as well as to develop the next generation of alert and warning systems. In particular, we note that there is a vital connection between state and local alert and warning and Federal efforts to mitigate
• http://www.fcc.gov/eb/Orders/2008/DA-08-1394A1.html
  • of record. FEDERAL COMMUNICATIONS COMMISSION Dennis P. Carlton Regional Director, South Central Region Enforcement Bureau 47 C.F.R. S: 11.35(a). Notice of Apparent Liability for Forfeiture, NAL/Acct. No. 200732500006 (Enf. Bur., Dallas Office, October 23, 2007) ("NAL"). 47 U.S.C. S: 503(b). 47 C.F.R. S: 1.80. 47 U.S.C. S: 503(b)(2)(E). 47 C.F.R. S: 11.35(a). 47 C.F.R. S:S: 11.35(a), (b). 47 C.F.R. S: 11.31. Some EAS units can be programmed to print an out-of-date message for received tests prior to discarding them. However, there were no such messages in station KMZE's files. According to Omni's program logs, no weekly tests were transmitted between January 28 and February 17, 2008. Licensees are not informed of the exact time at which monthly EAS tests are sent.
• http://www.fcc.gov/eb/Orders/2008/DA-08-1717A1.html
  • participating national EAS source ("EAS Participant") unless the station affirmatively requests authority to not participate. 47 C.F.R. S:S: 11.11 and 11.41. See 47 C.F.R. S: 11.1 et. seq. The EAS protocol consists of four parts: Preamble and EAS Header Codes; two-tone audio Attention Signal ("EAS tone"); message; and Preamble and EAS End of Message ("EOM") Codes. See 47 C.F.R. S: 11.31(a). 47 C.F.R. S:S: 11.32, 11.33. The functions of the EAS encoder and decoder may be combined into a single unit referred to as an Encoder/Decoder provided that the unit complies with all specifications in Part 11 of the Commission's Rules. See 47.C.F.R. S: 11.34(c). 47 C.F.R. S: 11.32(a). 47 C.F.R. S: 11.32(a)(9)(v). 47 C.F.R. S: 11.61(a). The Emergency Alert System
• http://www.fcc.gov/eb/Public_Notices/da012273.html http://www.fcc.gov/eb/Public_Notices/da012273.pdf
  • 73.1745 (Unauthorized Operation), 73.1870 (Chief Operator) and 73.3526 (Local Public Inspection File for Commercial Stations). Atlanta, GA District Office (8/9/01). * Bartow Broadcasting Co., Inc. Other violations: 47 C.F.R. 11.52 (EAS Code and Attention Signal Monitoring Requirements), 11.61(Tests of EAS Procedures), 73.49 (AM Transmission System Fencing Requirements) and 73.1840 (Retention of Logs). Tampa, FL District Office (8/22/01). * 47 C.F.R. 11.31 EAS Protocol * Agpal Broadcasting Inc., KPPT(AM/FM) Toledo, Oregon. Other violations: 47 C.F.R. 73.3526 (Local Public Inspection File for Commercial Stations). Portland, OR Resident Agent Office (8/22/01). * 47 C.F.R. 11.35 Equipment Operational Readiness * Clarke Broadcasting Corporation, KVML/KZSQ, Sonora, CA. Other violations: 47 C.F.R. 11.52 (EAS Code and Attention Signal Monitoring Requirements), 11.61 (Tests of EAS Procedures) and 73.1820
• http://www.fcc.gov/pshs/docs/services/eas/Second.pdf
  • systems; wireless cable systems which may consist of Multipoint Distribution Service (MDS), Multichannel Multipoint Distribution Service (MMDS), or Instructional Television Fixed Service (ITFS) stations; and other entities and industries operating on an organized basis during emergencies at the National, State and local levels. It requires that at a minimum all participants use a common EAS protocol, as defined in § 11.31, to send and receive emergency alerts in accordance with the effective dates in the following tables: 2 TIMETABLE BROADCAST STATIONS REQUIREMENT AM & FM TV FM CLASS D LPTV1 Two-tone encoder2,3 Y Y N N Two-tone decoder4,5 Y Y Y Y EAS decoder Y 1/1/97 Y 1/1/97 Y 1/1/97 Y 1/1/97 EAS encoder Y 1/1/97 Y 1/1/97 N N Audio
• http://www.fcc.gov/transaction/arch-nextel/nextel_reply040201.pdf
  • TD Marketing Research, Inc."Nextel New Customer Welcome Survey" Third Quarter 2000, p. 44. *' These exit interviews were conducted in November 2000.(p. 16 of internal Nextel presentation, dated December 15,200O). 3o Bauman and Siwek Affidavit, pp. 15-17. 12 Southern Lint discounts the dispatch features provided by cellular and PCS providers because they are limited to 30 users on a one-to-many ca11.31Not only is 30 a large number-with 30 or more users, it would be very possible to set up a private system-but the vast majority of Nextel calls are one-to-one.Strategis reports that only 2% of Nextel's calls are one-to-many.32Presumably only a minute number of those calls involve more than 30 users at a time. As a result, cellular and PCS providers
• http://www.fcc.gov/transaction/nextel-motorola/nextel_exparte032901.pdf
  • New Customer Welcome Survey" Third Quarter 2000, p. 44. 2g These exit interviews were conducted in November 2000.(p. 16 of internal Nextel presentation, dated December 15, 2000). 3o Bauman and Siwek Affidavit, pp. 15-17. 12 I ' 7 Southern Lint discounts the dispatch features provided by cellular and PCS providers because they are limited to 30 users on a one-to-many ca11.31 Not only is 30 a large number-with 30 or more users, it would be very possible to set up a private system-but the vast majority of Nextel calls are one-to-one. Strategis reports that only 2% of Nextel's calls are one-to-many.32Presumably only a minute number of those calls involve more than 30 users at a time. As a result, cellular and