FCC Web Documents citing 11.33

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

• http://fjallfoss.fcc.gov/edocs_public/attachmatch/DA-08-1717A1.doc http://fjallfoss.fcc.gov/edocs_public/attachmatch/DA-08-1717A1.pdf
  • 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 2007 AM and FM Handbook
• http://fjallfoss.fcc.gov/edocs_public/attachmatch/DA-10-796A1.doc http://fjallfoss.fcc.gov/edocs_public/attachmatch/DA-10-796A1.pdf
  • that a copy of this Notice of Apparent Liability for Forfeiture shall be sent by Certified Mail, Return Receipt Requested, 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
• http://fjallfoss.fcc.gov/edocs_public/attachmatch/FCC-07-109A1.doc http://fjallfoss.fcc.gov/edocs_public/attachmatch/FCC-07-109A1.pdf
  • 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 this Order, once FEMA adopts the CAP protocol, we require existing EAS Participants to receive alert messages formatted to CAP, a standard alert message format that specifies data
• http://fjallfoss.fcc.gov/edocs_public/attachmatch/FCC-10-11A1.doc http://fjallfoss.fcc.gov/edocs_public/attachmatch/FCC-10-11A1.pdf
  • the President) to deliver specially-encoded messages to a broadcast station-based transmission network that, in turn, delivers the messages to individual broadcasters, cable operators, and other EAS Participants who maintain special encoding and decoding equipment that can receive the message for retransmission to other EAS Participants and to end users (broadcast listeners and cable and other service subscribers). Sections 11.32 and 11.33 of the Commission's rules set forth minimum requirements for these EAS encoders and decoders, respectively, the functions of which can be combined into a single unit that is commonly referred to as an Encoder/Decoder. The national EAS delivery/transmission system is commonly referred to as a ``daisy chain.'' At its initial level, it consists of various FEMA-designated radio broadcast stations -
• http://fjallfoss.fcc.gov/edocs_public/attachmatch/FCC-11-12A1.doc http://fjallfoss.fcc.gov/edocs_public/attachmatch/FCC-11-12A1.pdf
  • the President) to deliver specially-encoded messages to a broadcast station-based transmission network that, in turn, delivers the messages to individual broadcasters, cable operators, and other EAS Participants who maintain special encoding and decoding equipment that can receive the message for retransmission to other EAS Participants and to end users (broadcast listeners and cable and other service subscribers). Sections 11.32 and 11.33 of the Commission's rules set forth minimum requirements for these EAS encoders and decoders, respectively. The national EAS delivery/transmission system is commonly referred to as a ``daisy chain.'' At its initial level, it consists of various FEMA-designated radio broadcast stations - known as Primary Entry Point (PEP) stations - which are tasked with receiving and transmitting ``Presidential Level'' messages initiated
• http://fjallfoss.fcc.gov/edocs_public/attachmatch/FCC-11-82A1.doc http://fjallfoss.fcc.gov/edocs_public/attachmatch/FCC-11-82A1.pdf
  • and instead require EAS Participants to maintain within their facilities a copy of the current 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
• 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
  • 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 acceptable uses, these rules ensure the
• 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
  • 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 2007 AM and FM Handbook
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-10-372A2.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-10-372A2.txt
  • and this would bring additional problems to the implementation of these proposals asking for automatic cancellation in case of unresolved complaints. This raises even more concern 24 in cases where the complaint of harmful interference occurs towards the end of the four- month period. The matter of provisional recording of frequency assignments that received unfavourable finding under No. 11.32A or 11.33 is dealt with in Nos. 11.41, 11.41A and 11.421. In the November 2008 meeting of the SC-WP, the BR suggested that: "For complaint received beyond the four month period indicated in No. 11.41, it requests the administration responsible for the "incoming" assignment (i.e. the one recorded under No. 11.41) to eliminate the harmful interference immediately under No. 11.42. The matter
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-10-372A2_Rcd.pdf
  • and this would bring additional problems to the implementation of these proposals asking for automatic cancellation in case of unresolved complaints. This raises even more concern 2174 in cases where the complaint of harmful interference occurs towards the end of the four- month period. The matter of provisional recording of frequency assignments that received unfavourable finding under No. 11.32A or 11.33 is dealt with in Nos. 11.41,11.41A and 11.421. In the November 2008 meeting of the SC-WP, the BR suggested that: "For complaint received beyond the four month period indicated in No. 11.41, it requests the administration responsible for the "incoming" assignment (i.e. the one recorded under No.11.41) to eliminate the harmful interference immediately under No. 11.42. The matter is thereafter
• 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
  • that a copy of this Notice of Apparent Liability for Forfeiture shall be sent by Certified Mail, Return Receipt Requested, 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
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-11-447A2.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-11-447A2.txt
  • 2007 World Radiocommunication Conference (Document 4, Addendum 2, Section 3.1.3.3.4). 68 Proposal: ARTICLE 11 Notification and recording of frequency assignments1, 2, 3, 4, 5, 6, 7 (WRC-07) Section II ­ Examination of notices and recording of frequency assignments in the Master Register MOD USA/7/1 11.41A Should the assignments that were the basis of the unfavourable finding under Nos. 11.32A or 11.33 not be brought into use within the period specified in Nos. 11.24, 11.25 or 11.44, as appropriate, then the finding of the assignments resubmitted under No. 11.41 shall be reviewed accordingly. Should the coordination procedures specified in No.11.32 be completed with administration(s) whose assignments were the basis of the recording under No. 11.41with respect to assignments recorded under No. 11.41,
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-11-447A2_Rcd.pdf
  • 2007 World Radiocommunication Conference (Document 4, Addendum 2, Section 3.1.3.3.4). 3567 Proposal: ARTICLE 11 Notification and recording of frequency assignments1, 2, 3, 4, 5, 6, 7 (WRC-07) Section II ­ Examination of notices and recording of frequency assignments in the Master Register MOD USA/7/1 11.41A Should the assignments that were the basis of the unfavourable finding under Nos. 11.32A or 11.33 not be brought into use within the period specified in Nos. 11.24, 11.25 or 11.44,as appropriate, then the finding of the assignments resubmitted under No. 11.41 shall be reviewed accordingly. Should the coordination procedures specified in No.11.32 be completed with administration(s) whose assignments were the basis of the recording under No. 11.41with respect to assignments recorded under No. 11.41, then
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-11-447A3.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-11-447A3.txt
  • 2007 World Radiocommunication Conference (Document 4, Addendum 2, Section 3.1.3.3.4). 44 Proposal: ARTICLE 11 Notification and recording of frequency assignments1, 2, 3, 4, 5, 6, 7 (WRC-07) Section II ­ Examination of notices and recording of frequency assignments in the Master Register MOD USA/7/1 11.41A Should the assignments that were the basis of the unfavourable finding under Nos. 11.32A or 11.33 not be brought into use within the period specified in Nos. 11.24, 11.25 or 11.44as appropriate, then the finding of the assignments resubmitted under No. 11.41 shall be reviewed accordingly. Should the coordination procedures specified in No.11.32 be completed with administration(s) with respect to assignments recorded under No. 11.41, any conditions related to the initial recording under No. 11.41 shall
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-11-447A3_Rcd.pdf
  • 2007 World Radiocommunication Conference (Document 4, Addendum 2, Section 3.1.3.3.4). 3634 Proposal: ARTICLE 11 Notification and recording of frequency assignments1, 2, 3, 4, 5, 6, 7 (WRC-07) Section II ­ Examination of notices and recording of frequency assignments in the Master Register MOD USA/7/1 11.41A Should the assignments that were the basis of the unfavourable finding under Nos. 11.32A or 11.33 not be brought into use within the period specified in Nos. 11.24, 11.25 or 11.44as appropriate, then the finding of the assignments resubmitted under No. 11.41 shall be reviewed accordingly. Should the coordination procedures specified in No.11.32 be completed with administration(s) with respect to assignments recorded under No. 11.41, any conditions related to the initial recording under No. 11.41 shall
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-202154A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-202154A1.txt
  • Communications Ministry, Corona, NY. New York, NY Office (3/27/00). Apollo Transportation, Inc., Yonkers, NY. New York, NY (3/31/00). 47 (EAS) Rules) Cablevision of Massachusetts, Allston, MA. NOV also issued for violation of 47 C.F.R. §§ 11.21, and 11.61. New England District Office (3/10/00). Booth-Newsome Broadcasting, Inc., WKTE, King, North Carolina. NOV also issued for violation of 47 C.F.R. §§ 11.32, 11.33, 11.35, 11.52, 11.61, 73.49, 73.51, 73.1225, 73.1400 73.1350, 73.1560, 73.1590, 73.1870, and 73.3526. Norfolk, VA Office (3/13/00). KICO/AM1490 kHz, Hanson Broadcasting Co. San Diego, CA Office (3/27/00). First Assembly of God, Gainesville, FL. NOV also issued for violation of 47 C.F.R. § 11.52 and 11.61. Tampa, FL Office (3/28/00). KGBA/FM, 100.1 MHz, The Voice of International Christian. 16570 47 Key
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-202154A1_Erratum.pdf
  • Communications Ministry, Corona, NY. New York, NY Office (3/27/00). Apollo Transportation, Inc., Yonkers, NY. New York, NY (3/31/00). 47 (EAS) Rules) Cablevision of Massachusetts, Allston, MA. NOV also issued for violation of 47 C.F.R. §§ 11.21, and 11.61. New England District Office (3/10/00). Booth-Newsome Broadcasting, Inc., WKTE, King, North Carolina. NOV also issued for violation of 47 C.F.R. §§ 11.32, 11.33, 11.35, 11.52, 11.61, 73.49, 73.51, 73.1225, 73.1400 73.1350, 73.1560, 73.1590, 73.1870, and 73.3526. Norfolk, VA Office (3/13/00). KICO/AM1490 kHz, Hanson Broadcasting Co. San Diego, CA Office (3/27/00). First Assembly of God, Gainesville, FL. NOV also issued for violation of 47 C.F.R. § 11.52 and 11.61. Tampa, FL Office (3/28/00). KGBA/FM, 100.1 MHz, The Voice of International Christian. 16570 47 Key
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-255118A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-255118A1.txt
  • Unobserved Heterogeneity 5 Years Weibull Unobserved Heterogeneity 10 Years Year Subscribers (in millions) Year Subscribers (in millions) Year Subscribers (in millions) Year Subscribers (in millions) 1 0.33 1 3.51 1 3.24 1 5.36 2 0.49 2 5.21 2 4.80 2 7.94 3 0.67 3 7.04 3 6.48 3 10.74 4 0.86 4 8.99 4 8.28 4 13.71 5 1.08 5 11.33 5 10.43 5 17.27 6 13.95 6 21.27 7 16.84 7 25.67 8 19.50 8 29.72 9 22.74 9 34.66 10 24.08 10 36.72 Weibull No Unobserved Heterogeneity 5 Years Weibull No Unobserved Heterogeneity 10 Years Weibull Unobserved Heterogeneity 5 Years Weibull Unobserved Heterogeneity 10 Years Year Subscribers (in millions) Year Subscribers (in millions) Year Subscribers (in millions) Year Subscribers
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-262986A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-262986A1.txt
  • TELEPHONE COMPANY INC. 4.27 2.35 1.88 -2.19 411780 C HAVILAND TELEPHONE COMPANY INC. 33.92 -1.43 35.86 48.73 411781 C H & B COMMUNICATIONS INC. 5.14 -2.20 7.50 10.29 411782 C HOME TELEPHONE COMPANY INC. 4.62 -1.72 6.45 6.05 411785 C J. B. N. TELEPHONE COMPANY INC. -12.47 -1.45 -11.18 -19.90 411788 C KANOKLA TEL. ASSOC. INC.- KS 9.27 -1.69 11.15 11.33 411791 A LA HARPE TELEPHONE COMPANY INC. 13.66 6.55 6.67 21.35 411801 C MADISON TELEPHONE, LLC 6.55 -4.10 11.11 9.00 411807 C MOKAN DIAL, INC.- KS 2.70 2.09 0.60 -0.69 411808 C MOUNDRIDGE TEL. CO. -1.56 -3.53 2.04 -2.78 411809 C MUTUAL TELEPHONE COMPANY 5.82 1.39 4.36 5.85 411814 C PEOPLES TELECOMMUNICATIONS, LLC 20.19 -3.81 24.95 30.10 411817 C PIONEER
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-262986A13.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-262986A13.txt
  • Columbia DC 541,936 288,871 276,222 50.97 12.10 Verizon - Florida FL 1,266,671 908,536 438,109 34.59 30.93 BellSouth - Florida FL 3,554,132 2,585,779 1,161,751 32.69 28.15 Sprint - Florida FL 1,563,127 1,220,962 347,227 22.21 58.53 ALLTEL Georgia Communications GA 309,716 220,762 90,463 29.21 14.55 BellSouth - Georgia GA 3,875,863 2,696,938 1,332,536 34.38 12.77 Verizon - Hawaii HI 441,674 329,631 219,063 49.60 11.33 Verizon - NW - Idaho ID 106,856 76,612 37,073 34.69 35.63 Qwest - Idaho South ID 270,728 173,936 101,955 37.66 35.75 Qwest - Idaho North ID 21,594 14,907 8,417 38.98 30.83 Verizon - North - Contel Illinois IL 52,054 36,042 26,107 50.15 42.94 Verizon - South - Illinois IL 36,192 26,759 6,508 17.98 14.98 Verizon - North - Illinois IL
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-262986A5.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-262986A5.txt
  • TELEPHONE COMPANY INC. 4.27 2.35 1.88 -2.19 411780 C HAVILAND TELEPHONE COMPANY INC. 33.92 -1.43 35.86 48.73 411781 C H & B COMMUNICATIONS INC. 5.14 -2.20 7.50 10.29 411782 C HOME TELEPHONE COMPANY INC. 4.62 -1.72 6.45 6.05 411785 C J. B. N. TELEPHONE COMPANY INC. -12.47 -1.45 -11.18 -19.90 411788 C KANOKLA TEL. ASSOC. INC.- KS 9.27 -1.69 11.15 11.33 411791 A LA HARPE TELEPHONE COMPANY INC. 13.66 6.55 6.67 21.35 411801 C MADISON TELEPHONE, LLC 6.55 -4.10 11.11 9.00 411807 C MOKAN DIAL, INC.- KS 2.70 2.09 0.60 -0.69 411808 C MOUNDRIDGE TEL. CO. -1.56 -3.53 2.04 -2.78 411809 C MUTUAL TELEPHONE COMPANY 5.82 1.39 4.36 5.85 411814 C PEOPLES TELECOMMUNICATIONS, LLC 20.19 -3.81 24.95 30.10 411817 C PIONEER
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-265170A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-265170A1.txt
  • 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 606 5,412 11.20 Mississippi 298 6,309 4.72 202 3,529 5.72 Missouri 928 15,099 6.15 835 6,877 12.14 Montana 105 1,881 5.58
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-269251A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-269251A1.txt
  • 1,103,190 33.27 16.68 Sprint - Florida FL 1,538,812 1,212,030 332,374 21.60 8.56 ALLTEL Georgia Communications GA 282,589 199,057 85,264 30.17 39.46 BellSouth - Georgia GA 3,594,697 2,512,468 1,240,855 34.52 8.68 Verizon - Northwest - Idaho ID 86,405 62,317 31,092 35.98 (4.01) Qwest - Idaho South ID 228,224 149,941 84,279 36.93 31.60 Qwest - Idaho North ID 19,412 13,397 6,451 33.23 11.33 Verizon North - Contel/Illinois IL 40,278 25,259 25,988 64.52 25.17 Verizon South - Illinois IL 36,800 27,094 6,825 18.55 (0.02) Verizon North - Illinois IL 227,459 153,475 157,996 69.46 8.82 AT&T - Ameritech - Illinois Bell IL 2,212,686 1,606,189 809,019 36.56 10.49 Verizon North - Contel/Indiana IN 57,484 36,548 29,249 50.88 40.48 Verizon North - Indiana IN 316,677 202,984 179,681
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-269251A13.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-269251A13.txt
  • 1,103,190 33.27 16.68 Sprint - Florida FL 1,538,812 1,212,030 332,374 21.60 8.56 ALLTEL Georgia Communications GA 282,589 199,057 85,264 30.17 39.46 BellSouth - Georgia GA 3,594,697 2,512,468 1,240,855 34.52 8.68 Verizon - Northwest - Idaho ID 86,405 62,317 31,092 35.98 (4.01) Qwest - Idaho South ID 228,224 149,941 84,279 36.93 31.60 Qwest - Idaho North ID 19,412 13,397 6,451 33.23 11.33 Verizon North - Contel/Illinois IL 40,278 25,259 25,988 64.52 25.17 Verizon South - Illinois IL 36,800 27,094 6,825 18.55 (0.02) Verizon North - Illinois IL 227,459 153,475 157,996 69.46 8.82 AT&T - Ameritech - Illinois Bell IL 2,212,686 1,606,189 809,019 36.56 10.49 Verizon North - Contel/Indiana IN 57,484 36,548 29,249 50.88 40.48 Verizon North - Indiana IN 316,677 202,984 179,681
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-279226A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-279226A1.txt
  • MUTUAL TEL. CO. 24.28 0.99 23.07 56.29 341023 C GRIDLEY TEL. CO. 4.47 -2.54 7.19 696.13 341024 A HAMILTON COUNTY TELEPHONE CO-OP 12.36 -5.06 18.35 46.62 341025 C SHAWNEE TEL. CO. 13.24 -2.47 16.11 60.84 341026 C HARRISONVILLE TEL. CO. 0.15 -1.19 1.35 -6.54 341029 A HENRY COUNTY TEL. CO. 3.44 -1.82 5.35 13.22 341032 C HOME TEL. CO.-ST. JACOB 11.33 -1.06 12.51 13.85 341036 C VERIZON NORTH INC.-IL (CONTEL) 3.30 -4.67 8.37 0.00 341037 C ILLINOIS CONS. TEL. CO. -9.96 -4.72 -5.49 -43.32 341038 C FRONTIER COMM. OF ILLINOIS, INC. -13.74 -4.62 -9.57 0.00 341041 A KINSMAN MUTUAL TEL. CO. 24.89 1.19 23.42 56.87 341043 C LA HARPE TEL. CO. 2.90 -7.61 11.37 7.33 341045 C LEAF RIVER TEL. CO.
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-279226A5.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-279226A5.txt
  • MUTUAL TEL. CO. 24.28 0.99 23.07 56.29 341023 C GRIDLEY TEL. CO. 4.47 -2.54 7.19 696.13 341024 A HAMILTON COUNTY TELEPHONE CO-OP 12.36 -5.06 18.35 46.62 341025 C SHAWNEE TEL. CO. 13.24 -2.47 16.11 60.84 341026 C HARRISONVILLE TEL. CO. 0.15 -1.19 1.35 -6.54 341029 A HENRY COUNTY TEL. CO. 3.44 -1.82 5.35 13.22 341032 C HOME TEL. CO.-ST. JACOB 11.33 -1.06 12.51 13.85 341036 C VERIZON NORTH INC.-IL (CONTEL) 3.30 -4.67 8.37 0.00 341037 C ILLINOIS CONS. TEL. CO. -9.96 -4.72 -5.49 -43.32 341038 C FRONTIER COMM. OF ILLINOIS, INC. -13.74 -4.62 -9.57 0.00 341041 A KINSMAN MUTUAL TEL. CO. 24.89 1.19 23.42 56.87 341043 C LA HARPE TEL. CO. 2.90 -7.61 11.37 7.33 341045 C LEAF RIVER TEL. CO.
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-287688A1.pdf
  • RURAL TEL. COOP., INC. 23.71 -3.68 28.44 60.55 320815 C ROCHESTER TEL. CO., INC. 0.42 -3.65 4.22 4.90 320816 A S & W TEL. CO., INC. -2.86 -8.35 6.00 3.55 320818 C SMITHVILLE TEL. CO., INC. 14.12 -4.94 20.05 109.72 320819 C SOUTHEASTERN INDIANA RURAL TEL. COOP., INC. 12.65 -1.21 14.03 27.84 320825 C SUNMAN TELECOMMUNICATIONS CORPORATION 4.88 -1.57 6.56 11.33 320826 A SWAYZEE TEL. CO., INC. -3.34 -4.51 1.22 -15.30 320827 A SWEETSER RURAL TEL. CO., INC. 0.47 -3.16 3.75 15.64 320828 C FRONTIER COMM. OF THORNTOWN, INC. -12.21 -3.20 -9.31 0.00 320829 A TIPTON TEL. CO., INC. 3.27 -3.83 7.38 0.00 320830 A TRI-COUNTY TEL. CO., INC.-IN -2.95 -3.16 0.22 -18.29 320832 C UNITED TEL. CO. OF INDIANA, INC.
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-287688A13.pdf
  • of California - Shasta - California CA 114,023 81,052 32,971 28.92 14.25 Verizon - Northwest - West Coast California CA 8,472 6,075 2,622 30.95 11.59 Verizon California - GTE - California CA 1,472,545 1,044,382 829,991 56.36 19.69 AT&T - Pacific Telesis - Pacific Bell - California CA 3,637,748 2,712,831 1,207,485 33.19 19.48 Qwest - Colorado CO 1,959,772 1,461,217 538,705 27.49 11.33 AT&T - Southern New England Telephone CT 788,707 530,151 340,420 43.16 8.13 Verizon Delaware, LLC DE 390,603 280,833 119,881 30.69 (9.60) Verizon Washington, D.C. DC 340,578 211,973 153,436 45.05 30.82 Verizon Florida, LLC FL 1,477,833 1,130,990 415,071 28.09 (0.80) AT&T - BellSouth - Florida FL 2,012,177 1,549,308 865,636 43.02 29.63 Embarq - Florida FL 1,565,942 1,249,956 321,606 20.54 0.72 Windstream
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-287688A5.pdf
  • RURAL TEL. COOP., INC. 23.71 -3.68 28.44 60.55 320815 C ROCHESTER TEL. CO., INC. 0.42 -3.65 4.22 4.90 320816 A S & W TEL. CO., INC. -2.86 -8.35 6.00 3.55 320818 C SMITHVILLE TEL. CO., INC. 14.12 -4.94 20.05 109.72 320819 C SOUTHEASTERN INDIANA RURAL TEL. COOP., INC. 12.65 -1.21 14.03 27.84 320825 C SUNMAN TELECOMMUNICATIONS CORPORATION 4.88 -1.57 6.56 11.33 320826 A SWAYZEE TEL. CO., INC. -3.34 -4.51 1.22 -15.30 320827 A SWEETSER RURAL TEL. CO., INC. 0.47 -3.16 3.75 15.64 320828 C FRONTIER COMM. OF THORNTOWN, INC. -12.21 -3.20 -9.31 0.00 320829 A TIPTON TEL. CO., INC. 3.27 -3.83 7.38 0.00 320830 A TRI-COUNTY TEL. CO., INC.-IN -2.95 -3.16 0.22 -18.29 320832 C UNITED TEL. CO. OF INDIANA, INC.
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-01-269A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-01-269A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-01-269A1.txt
  • greatly. Although Z-Tel initially stated that various billing problems have not been fixed, it later clarified that much of its current billing disputes with Verizon are cumulative and span multiple billing periods other than the month in which Z-Tel filed the dispute. Thus, while Z-Tel reports disputing 36.51 percent of its total June bill from Verizon, it acknowledges that only 11.33 percent of its total June bill arose from errors that actually appeared on the June bill. To the extent that other competitive LECs report errors, these errors do not appear to reflect systemic wholesale billing problems that are likely to recur. WorldCom, for example, attributes the majority of its total billing disputes with Verizon for May and June to just
• 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
  • after station processing to attain the required modulation level. According to SBE, this situation is ``adverse to acceptable engineering practice.'' We agree with SBE and propose to amend Section 11.51(f) of the Rules to permit a minimum modulation level of 50%. We invite comment on this proposal. Compatibility of EAS Equipment with NWR-SAME System NWS requests that we amend Section 11.33(a)(4) and (a)(5) of the Rules to permit EAS decoders to display or log receipt of only those event codes and accompanying location codes for which the decoder is programmed for mandatory receipt and those optionally set by the device user. Section 11.33(a)(4) and (a)(5) requires EAS decoders to display messages from any valid EAS header codes received. Therefore, EAS participants
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-02-331A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-02-331A1.txt
  • (days) 10.00 8.00 11.41 6.50 10.61 7.00 11.32 6.00 11.16 5.67 1,2,3,4,5 B.2.1.9.1.12W Analog Loop Non-Design/<10 circuits/Dispatch/FL (days) 4.01 3.64 4.81 3.73 5.31 4.29 4.54 3.75 5.01 3.76 B.2.1.9.1.42W Analog Loop Non-Design/<10 circuits/Dispatch In/FL (days) 1.61 3.33 1.53 3.11 1.59 3.64 1.52 3.50 1.89 4.22 4,5 B.2.1.9.2.12W Analog Loop Non-Design/>=10 circuits/Dispatch/FL (days) 9.03 4.55 9.89 6.14 10.18 8.08 11.42 7.92 11.33 5.90 B.2.1.11.1.42W Analog Loop w/INP Non- Design/<10 circuits/Dispatch In/FL (days) 1.61 1.53 1.59 4.00 1.52 1.89 3 B - 25 Metric Metric Name [SQM Number] May June July August September Number and Disaggregation BST CLEC BST CLEC BST CLEC BST CLEC BST CLEC Notes Federal Communications Commission FCC 02-331 Florida Performance Metric Data B.2.1.12.1.12W Analog Loop w/LNP Design/<10 circuits/Dispatch/FL (days)
• 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
  • with SBE that it is important that EAS decoders have the capability to store and forward EAS messages or to automatically pass through EAS messages. Accordingly, we will not relax the certification requirements for EAS decoders. In order to receive FCC certification, EAS decoders will be required to satisfy all of the existing requirements for decoders set forth in Section 11.33 of the Rules. Small cable systems which opt to install decoder-only units will not be able to originate EAS messages or generate RWTs. However, these small cable systems will still be able to pass through EAS messages and accomplish Required Weekly Testing by forwarding a received RWT. Thus, we do not believe that permitting small cable systems to install decoder-only
• 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
  • called an ENDEC unit. EAS equipment sends and receives messages using a precise format referred to as the EAS digital protocol. An emergency activation of EAS uses a four part message: (1) preamble and EAS header codes; (2) audio attention signal; (3) message; and (4) preamble and EAS end of message codes. See 47 C.F.R. § 11.31(a). 47 C.F.R. §§ 11.33(a)(4), 11.51(k)(1), 11.54. 47 C.F.R. § 11.31(c). 47 C.F.R. § 11.31(a)(3)(i). MSRC was formed following the events of September 11, 2001, to study, develop, and report on Best Practices designed to ensure the continued operations and security of media facilities in times of a national emergency. See FCC News Release, FCC Announces Creation of Media Security & Reliability Council; Tribune Company
• 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
  • common studio or control point if there is no hub station) and rebroadcast 100% of the programming of the hub station (or common studio or control point) may satisfy the requirements of this part through the use of a single set of EAS equipment at the hub station (or common studio or control point) which complies with §§ 11.32 and 11.33. * * * * * (e) Organizations using other communications systems or technologies such as low earth orbit satellite systems, paging, computer networks, etc. may join the EAS on a voluntary basis by contacting the FCC. Organizations that choose to voluntarily participate must comply with the requirements of this part. Revise § 11.13 to read as follows: § 11.13 Emergency
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-05-191A1_Erratum.doc
  • common studio or control point if there is no hub station) and rebroadcast 100% of the programming of the hub station (or common studio or control point) may satisfy the requirements of this part through the use of a single set of EAS equipment at the hub station (or common studio or control point) which complies with §§ 11.32 and 11.33. * * * * * (e) Organizations using other communications systems or technologies such as low earth orbit satellite systems, paging, computer networks, etc. may join the EAS on a voluntary basis by contacting the FCC. Organizations that choose to voluntarily participate must comply with the requirements of this part. Revise § 11.13 to read as follows: § 11.13 Emergency
• 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
  • 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 this Order, once FEMA adopts the CAP protocol, we require existing EAS Participants to receive alert messages formatted to CAP, a standard alert message format that specifies data
• 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
  • the President) to deliver specially-encoded messages to a broadcast station-based transmission network that, in turn, delivers the messages to individual broadcasters, cable operators, and other EAS Participants who maintain special encoding and decoding equipment that can receive the message for retransmission to other EAS Participants and to end users (broadcast listeners and cable and other service subscribers). Sections 11.32 and 11.33 of the Commission's rules set forth minimum requirements for these EAS encoders and decoders, respectively, the functions of which can be combined into a single unit that is commonly referred to as an Encoder/Decoder. The national EAS delivery/transmission system is commonly referred to as a ``daisy chain.'' At its initial level, it consists of various FEMA-designated radio broadcast stations -
• 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
  • the President) to deliver specially-encoded messages to a broadcast station-based transmission network that, in turn, delivers the messages to individual broadcasters, cable operators, and other EAS Participants who maintain special encoding and decoding equipment that can receive the message for retransmission to other EAS Participants and to end users (broadcast listeners and cable and other service subscribers). Sections 11.32 and 11.33 of the Commission's rules set forth minimum requirements for these EAS encoders and decoders, respectively. The national EAS delivery/transmission system is commonly referred to as a ``daisy chain.'' At its initial level, it consists of various FEMA-designated radio broadcast stations - known as Primary Entry Point (PEP) stations - which are tasked with receiving and transmitting ``Presidential Level'' messages initiated
• 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
  • and instead require EAS Participants to maintain within their facilities a copy of the current 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
• 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
  • obligations to receive and convert CAP-formatted messages into the SAME format without having to replace its existing EAS equipment and sought comment on whether we should permit EAS Participants to meet their CAP-related obligations by deploying such intermediary devices. We further sought comment on whether we should subject intermediary devices to some or all of the requirements of sections 11.32, 11.33, 11.51, and 11.52 of the Commission's rules. We also sought comment on whether intermediary devices can be modified via software or firmware to accommodate future changes to CAP, the SAME protocol, or changes to other Part 11 requirements and whether intermediary devices provide a cost-effective and efficient method for EAS Participants to meet the CAP-related obligations. We asked whether EAS
• http://transition.fcc.gov/Bureaus/Common_Carrier/Orders/2001/fcc01269.doc http://transition.fcc.gov/Bureaus/Common_Carrier/Orders/2001/fcc01269.pdf http://transition.fcc.gov/Bureaus/Common_Carrier/Orders/2001/fcc01269.txt
  • greatly. Although Z-Tel initially stated that various billing problems have not been fixed, it later clarified that much of its current billing disputes with Verizon are cumulative and span multiple billing periods other than the month in which Z-Tel filed the dispute. Thus, while Z-Tel reports disputing 36.51 percent of its total June bill from Verizon, it acknowledges that only 11.33 percent of its total June bill arose from errors that actually appeared on the June bill. To the extent that other competitive LECs report errors, these errors do not appear to reflect systemic wholesale billing problems that are likely to recur. WorldCom, for example, attributes the majority of its total billing disputes with Verizon for May and June to just
• http://transition.fcc.gov/Bureaus/Mass_Media/Orders/2000/fcc00019.doc http://transition.fcc.gov/Bureaus/Mass_Media/Orders/2000/fcc00019.pdf
  • 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 provide that
• http://transition.fcc.gov/eb/Orders/2001/fcc01088.doc http://transition.fcc.gov/eb/Orders/2001/fcc01088.html
  • after station processing to attain the required modulation level. According to SBE, this situation is ``adverse to acceptable engineering practice.'' We agree with SBE and propose to amend Section 11.51(f) of the Rules to permit a minimum modulation level of 50%. We invite comment on this proposal. Compatibility of EAS Equipment with NWR-SAME System NWS requests that we amend Section 11.33(a)(4) and (a)(5) of the Rules to permit EAS decoders to display or log receipt of only those event codes and accompanying location codes for which the decoder is programmed for mandatory receipt and those optionally set by the device user. Section 11.33(a)(4) and (a)(5) requires EAS decoders to display messages from any valid EAS header codes received. Therefore, EAS participants
• http://transition.fcc.gov/eb/Orders/2002/FCC-02-64A1.html
  • with SBE that it is important that EAS decoders have the capability to store and forward EAS messages or to automatically pass through EAS messages.165 Accordingly, we will not relax the certification requirements for EAS decoders. In order to receive FCC certification, EAS decoders will be required to satisfy all of the existing requirements for decoders set forth in Section 11.33 of the Rules.166 Small cable systems which opt to install decoder-only units will not be able to originate EAS messages or generate RWTs. However, these small cable systems will still be able to pass through EAS messages and accomplish Required Weekly Testing by forwarding a received RWT. Thus, we do not believe that permitting small cable systems to install decoder-only
• http://transition.fcc.gov/eb/Orders/2004/FCC-04-189A1.html
  • often called an ENDEC unit. EAS equipment sends and receives messages using a precise format referred to as the EAS digital protocol. An emergency activation of EAS uses a four part message: (1) preamble and EAS header codes; (2) audio attention signal; (3) message; and (4) preamble and EAS end of message codes. See 47 C.F.R. 11.31(a). 37 47 C.F.R. 11.33(a)(4), 11.51(k)(1), 11.54. 38 47 C.F.R. 11.31(c). 39 47 C.F.R. 11.31(a)(3)(i). 40 MSRC was formed following the events of September 11, 2001, to study, develop, and report on Best Practices designed to ensure the continued operations and security of media facilities in times of a national emergency. See FCC News Release, FCC Announces Creation of Media Security & Reliability Council; Tribune
• http://transition.fcc.gov/eb/Orders/2005/FCC-05-191A1.html
  • (or common studio or control point if there is no hub station) and rebroadcast 100% of the programming of the hub station (or common studio or control point) may satisfy the requirements of this part through the use of a single set of EAS equipment at the hub station (or common studio or control point) which complies with 11.32 and 11.33. * * * * * (e) Organizations using other communications systems or technologies such as low earth orbit satellite systems, paging, computer networks, etc. may join the EAS on a voluntary basis by contacting the FCC. Organizations that choose to voluntarily participate must comply with the requirements of this part. 4. Revise 11.13 to read as follows: 11.13 Emergency Action
• http://transition.fcc.gov/eb/Orders/2008/DA-08-1717A1.html
  • 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 2007 AM and FM Handbook
• http://transition.fcc.gov/eb/Orders/2010/DA-10-796A1.html
  • that a copy of this Notice of Apparent Liability for Forfeiture shall be sent by Certified Mail, Return Receipt Requested, 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
• http://transition.fcc.gov/eb/Public_Notices/da002136.doc http://transition.fcc.gov/eb/Public_Notices/da002136.html
  • Irving, TX. Dallas, TX District Office (8/18/00). Atlanta Gas Light Company, Atlanta, GA. Other violations: 47 C.F.R. §§ 90.233 (Base/Mobile Non-Voice Operations) and 90.403 (General Operating Requirements). Atlanta, GA District Office (8/29/00). 47 C.F.R. Part 11 - Emergency Alert System 47 C.F.R. § 11.15 - EAS Operating Handbook Cherokee Broadcasting Company, Inc. Other violations: 47 C.F.R. §§ 11.32 (EAS Encoder), 11.33 (EAS Decoder), 11.35 (Equipment Operational Readiness), 11.52 (EAS Code and Attention Signal Monitoring Requirements), 11.61 (Tests of EAS Procedures), 17.4 (Antenna Structure Registration), 17.50 (Cleaning and Repainting), and 73.1230 (Posting of Station License). Norfolk, VA Resident Agent Office (8/01/00). AT&T Broadband, Des Moines, IA. Other violations: 47 C.F.R. §§ 11.52 (EAS Code and Attention Signal Monitoring Requirements), 11.54 (EAS Operation
• http://transition.fcc.gov/eb/Public_Notices/da00813.doc http://transition.fcc.gov/eb/Public_Notices/da00813.html
  • New York, NY Office (3/31/00). 47 C.F.R. Part 11 (Emergency Alert System (EAS) Rules) 47 C.F.R. § 11.15 (EAS Operating Handbook) Cablevision of Massachusetts, Allston, MA. NOV also issued for violation of 47 C.F.R. §§ 11.21, and 11.61. New England District Office (3/10/00). Booth-Newsome Broadcasting, Inc., WKTE, King, North Carolina. NOV also issued for violation of 47 C.F.R. §§ 11.32, 11.33, 11.35, 11.52, 11.61, 73.49, 73.51, 73.1225, 73.1400 73.1350, 73.1560, 73.1590, 73.1870, and 73.3526. Norfolk, VA Office (3/13/00). KICO/AM 1490 kHz, Hanson Broadcasting Co. San Diego, CA Office (3/27/00). First Assembly of God, Gainesville, FL. NOV also issued for violation of 47 C.F.R. § 11.52 and 11.61. Tampa, FL Office (3/28/00). KGBA/FM, 100.1 MHz, The Voice of International Christian. San Diego,
• http://transition.fcc.gov/eb/bc-chklsts/EB18LPFM06_2008.pdf
  • 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 enables
• http://transition.fcc.gov/pshs/docs/services/eas/Second.pdf
  • and co- located with a combined studio or control facility (such as an AM and FM licensed to the same entity and at the same location or a cable headend serving more than one system) may comply with the EAS monitoring requirements contained in this section for the combined station or system with one EAS Decoder. The requirements of § 11.33 must be met by the combined facility. (d) Broadcast stations and cable systems and wireless cable systems 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 Mapbook. They are developed in accordance with FCC monitoring priorities. (1) If the required EAS
• http://www.fcc.gov/Bureaus/Common_Carrier/Orders/2001/fcc01269.doc http://www.fcc.gov/Bureaus/Common_Carrier/Orders/2001/fcc01269.pdf http://www.fcc.gov/Bureaus/Common_Carrier/Orders/2001/fcc01269.txt
  • greatly. Although Z-Tel initially stated that various billing problems have not been fixed, it later clarified that much of its current billing disputes with Verizon are cumulative and span multiple billing periods other than the month in which Z-Tel filed the dispute. Thus, while Z-Tel reports disputing 36.51 percent of its total June bill from Verizon, it acknowledges that only 11.33 percent of its total June bill arose from errors that actually appeared on the June bill. To the extent that other competitive LECs report errors, these errors do not appear to reflect systemic wholesale billing problems that are likely to recur. WorldCom, for example, attributes the majority of its total billing disputes with Verizon for May and June to just
• http://www.fcc.gov/Bureaus/Common_Carrier/Orders/2002/fcc02331.pdf
  • (days) 10.00 8.00 11.41 6.50 10.61 7.00 11.32 6.00 11.16 5.67 1,2,3,4,5 B.2.1.9.1.12W Analog Loop Non-Design/<10 circuits/Dispatch/FL (days) 4.01 3.64 4.81 3.73 5.31 4.29 4.54 3.75 5.01 3.76 B.2.1.9.1.42W Analog Loop Non-Design/<10 circuits/Dispatch In/FL (days) 1.61 3.33 1.53 3.11 1.59 3.64 1.52 3.50 1.89 4.22 4,5 B.2.1.9.2.12W Analog Loop Non-Design/>=10 circuits/Dispatch/FL (days) 9.03 4.55 9.89 6.14 10.18 8.08 11.42 7.92 11.33 5.90 B.2.1.11.1.42W Analog Loop w/INP Non- Design/<10 circuits/Dispatch In/FL (days) 1.61 1.53 1.59 4.00 1.52 1.89 3 B - 25 Metric Metric Name [SQM Number] May June July August September Number and Disaggregation BST CLEC BST CLEC BST CLEC BST CLEC BST CLEC Notes Federal Communications Commission FCC 02-331 Florida Performance Metric Data B.2.1.12.1.12W Analog Loop w/LNP Design/<10 circuits/Dispatch/FL (days)
• http://www.fcc.gov/Bureaus/Common_Carrier/Reports/FCC-State_Link/IAD/ref03.pdf
  • 50.28 14.07 Illinois Rock Island SBC 20.97 10.75 50.28 14.07 Indiana Indianapolis SBC 20.36 8.75 47.00 0.00 Indiana Terre Haute Verizon 24.80 15.95 60.06 30.03 Iowa Fort Dodge Frontier 18.81 9.32 13.57 6.78 Kentucky Louisville BellSouth 28.22 14.00 44.52 22.26 Louisiana Baton Rouge BellSouth 23.18 14.17 44.28 22.14 Louisiana New Orleans BellSouth 21.74 13.62 42.23 21.12 Maine Portland Verizon 26.09 11.33 46.99 10.50 Maryland Baltimore Verizon 27.34 7.45 48.00 0.00 Massachusetts Boston Verizon 25.71 7.95 14.18 0.00 Massachusetts Hyannis Verizon 25.71 7.95 14.18 0.00 Massachusetts Springfield Verizon 25.71 8.47 14.18 0.00 Michigan Detroit SBC 27.59 15.50 46.62 0.00 Michigan Grand Rapids SBC 24.97 17.28 44.52 0.00 Michigan Saginaw SBC 28.16 14.42 44.52 0.00 Minnesota Detroit Lakes Qwest 21.76 6.25 19.54 9.78
• http://www.fcc.gov/Bureaus/Common_Carrier/Reports/FCC-State_Link/IAD/ref97.pdf
  • 8.95 8.95 9.95 10.95 11.14 11.14 12.04 12.04 15.13 16.25 17.91 20.35 20.35 Springfield 10.05 10.05 11.05 12.05 12.78 12.20 13.10 13.10 16.07 17.19 19.10 20.35 20.35 MI Detroit 10.65 11.86 12.86 14.08 14.68 13.23 14.59 14.35 14.33 14.48 14.50 14.50 14.46 Grand Rapids 9.72 10.84 11.84 13.28 13.66 12.21 13.57 13.33 13.31 13.46 13.46 13.48 13.95 Saginaw 9.26 10.33 11.33 12.55 13.15 11.70 13.06 12.82 12.80 12.95 12.97 12.97 12.93 MN Detroit Lakes 10.72 10.72 14.98 16.19 16.58 15.80 16.51 16.51 16.51 16.51 16.51 16.51 16.51 Minneapolis 11.66 11.66 16.20 17.20 17.76 16.76 17.66 17.66 17.66 17.66 18.08 18.08 18.08 MS Pascagoula 17.25 17.25 18.25 21.25 20.85 20.85 21.75 21.75 21.75 21.75 21.75 21.75 21.75 MO Kansas City 9.55 11.60
• http://www.fcc.gov/Bureaus/Common_Carrier/Reports/FCC-State_Link/IAD/ror96.pdf
  • (71.91) 19.03 16.67 14SOUTHERN BELL TELEPHONE & TELEGRAPH CO.-FL 13.85 11.99 13.03 14.86 12.58 25.77 19.23 15SOUTHERN BELL TELEPHONE & TELEGRAPH CO.-GA 12.64 11.94 11.45 13.18 (54.71) 18.66 15.00 16NEW ENGLAND TELEPHONE AND TELEGRAPH CO. 12.54 11.57 11.52 19.46 (26.02) 10.62 13.81 17NEW YORK TELEPHONE 11.46 11.14 13.49 11.10 39.43 9.89 10.74 18PACIFIC BELL 11.51 11.76 11.04 12.47 36.68 9.94 11.33 19SOUTHWESTERN BELL TELEPHONE-TOTAL COMPANY 12.73 11.89 11.34 10.13 7.86 20.59 15.15 20SOUTHWESTERN BELL TELEPHONE-KANSAS SWITCHED - - - 12.36 (13.33) 23.48 19.09 21MOUNTAIN STATE TELEPHONE AND TELEGRAPH COMPANY 12.00 11.88 17.48 12.35 3.70 8.78 10.39 22NORTHWESTERN BELL TELEPHONE COMPANY 11.86 12.18 12.02 10.14 18.20 12.19 11.37 23PACIFIC NORTHWEST BELL TELEPHONE COMPANY 14.57 12.20 13.38 13.57 27.92 23.32 18.58 24ALLTEL ILLINOIS,
• http://www.fcc.gov/Bureaus/Common_Carrier/Reports/FCC-State_Link/IAD/ror99.pdf
  • Katie Rangos as of May 22, 2000. SWITCHED TRAFFIC SENSITIVE COMMON SPECIAL END LOCAL NAME OF COMPANY INTERSTATE LINE ACCESS OFFICE INFORMATION TRANSPORT TOTAL NATIONAL EXCHANGE CARRIER ASSOCIATION 12.94% 12.68% 15.53% - - - 12.93% 1ALLTEL ALABAMA, INC. 9.47 11.50 11.61 2.03 15.36 4.38 2ALLTEL ARKANSAS, INC. 9.88 11.50 11.49 4.69 5.03 4.96 3ALLTEL CAROLINA, INC. 10.93 11.50 5.13 11.70 11.33 11.98 4ALLTEL FLORIDA, INC. 11.44 11.50 10.18 10.34 12.95 11.78 5ALLTEL GEORGIA PROPERTIES 11.87 11.84 11.78 11.85 11.91 11.99 6ALLTEL KENTUCKY, INC. 11.46 11.50 10.41 11.24 12.19 11.52 7ALLTEL MISSISSIPPI, INC. 10.36 11.50 11.30 4.63 10.62 5.98 8ALLTEL MISSOURI, INC. 11.58 11.50 11.34 11.20 12.52 11.99 9ALLTEL NEW YORK, INC. 10.80 11.50 8.06 8.87 13.50 10.41 10ALLTEL OKLAHOMA PROPERTIES 11.69
• http://www.fcc.gov/Bureaus/Common_Carrier/Reports/FCC-State_Link/Monitor/mr04-3.pdf
  • INFINITE 204338 C CITIZENS TEL CO OF WVA DBA FRONTIER COMM 10.79 4.35 6.17 15.28 204339 C CITIZENS TEL CO OF WVA DBA FRONTIER COMM 0.23 -0.65 0.89 -7.34 205050 C VERIZON WEST VIRGINIA INC. -3.80 -1.90 -1.93 0.00 WISCONSIN Total -2.51 -4.63 2.22 12.04 330841 C CENTURYTEL OF THE MIDWEST-WI/CENCOM 3.85 1.58 2.24 -3.43 330842 A AMERY TELCOM, INC. 11.33 1.53 9.64 0.00 330843 A AMHERST TEL. CO. 9.69 -1.87 11.79 INFINITE 330844 C BADGER TELECOM, INC. -1.86 -0.04 -1.82 -19.13 330846 A BALDWIN TELCOM., INC. 10.69 0.10 10.58 0.00 330847 A BELMONT TEL. CO. 11.07 1.20 9.76 46.42 330848 A BERGEN TEL. CO. 1.48 3.15 -1.62 -7.36 330849 A BLACK EARTH TEL. CO. 10.99 -0.12 11.13 333.88 330850 A
• http://www.fcc.gov/Bureaus/Common_Carrier/Reports/FCC-State_Link/Monitor/mrs01-0.pdf
  • -2.28 532384 C MONITOR COOPERATIVE TELEPHONE CO 4.19 4.81 -0.59 0.63 532385 C MONROE TELEPHONE COMPANY 5.14 0.30 4.82 10.60 532386 A MT. ANGEL TELEPHONE COMPANY 3.25 1.86 1.37 0.00 532387 C NEHALEM TELEPHONE AND TELEGRAPH 8.30 5.24 2.91 0.00 532388 C NORTH STATE TELEPHONE COMPANY - OR 5.55 3.29 2.19 8.36 532389 C OREGON TELEPHONE CORPORATION 5.58 1.22 4.31 11.33 532390 C OREGON-IDAHO UTILITIES, INC. -6.34 -4.03 -2.41 -6.95 532391 A PEOPLES TELEPHONE CO. - OR -2.57 -0.19 -2.38 0.00 532392 C PINE TELEPHONE SYSTEM INC. - OR 7.34 7.84 -0.46 6.02 532393 C PIONEER TELEPHONE COOPERATIVE 11.85 2.12 9.53 26.08 532396 A ST. PAUL COOP. TEL. ASSN. 14.00 5.92 7.63 64.28 532397 C SCIO MUTUAL TEL. ASSOCIATION 7.80 1.68
• http://www.fcc.gov/Bureaus/Common_Carrier/Reports/FCC-State_Link/Monitor/mrs02-0.pdf
  • 6.22 9.37 658.21 361348 A WILDERNESS VALLEY TELEPHONE COMPANY, INC. -8.90 4.55 -12.86 -21.58 361350 C ARVIG TEL. CO. 10.10 4.62 5.24 33.05 361353 A CITY OF BARNESVILLE TEL. CO. 17.41 7.06 9.66 2,261.61 361356 A BENTON COOP. TEL. CO. 16.09 6.83 8.67 190.78 361357 C BLACKDUCK TEL. CO. 15.84 3.82 11.58 170.60 361358 A BLUE EARTH VALLEY TEL. CO. 11.33 0.80 10.44 768.30 361362 A BRIDGEWATER TEL. CO. 11.14 9.46 1.54 0.00 361365 A CALLAWAY TEL. CO. 21.10 3.55 16.96 146.05 361367 C FRONTIER COMM. OF MINNESOTA, INC. 39.85 1.42 37.90 0.00 361370 C CLARA CITY TEL. EXCH. CO. 30.46 5.00 24.25 201.87 361372 A CLEMENTS TEL. CO. 9.06 1.84 7.09 45.61 361373 A CONSOLIDATED TEL. CO.-MN 15.90 6.21 9.12
• http://www.fcc.gov/Bureaus/Enforcement/Orders/2000/da000814.doc
  • New York, NY Office (3/31/00). 47 C.F.R. Part 11 (Emergency Alert System (EAS) Rules) 47 C.F.R. § 11.15 (EAS Operating Handbook) Cablevision of Massachusetts, Allston, MA. NOV also issued for violation of 47 C.F.R. §§ 11.21, and 11.61. New England District Office (3/10/00). Booth-Newsome Broadcasting, Inc., WKTE, King, North Carolina. NOV also issued for violation of 47 C.F.R. §§ 11.32, 11.33, 11.35, 11.52, 11.61, 73.49, 73.51, 73.1225, 73.1400 73.1350, 73.1560, 73.1590, 73.1870, and 73.3526. Norfolk, VA Office (3/13/00). KICO/AM 1490 kHz, Hanson Broadcasting Co. San Diego, CA Office (3/27/00). First Assembly of God, Gainesville, FL. NOV also issued for violation of 47 C.F.R. § 11.52 and 11.61. Tampa, FL Office (3/28/00). KGBA/FM, 100.1 MHz, The Voice of International Christian. San Diego,
• http://www.fcc.gov/Bureaus/Enforcement/Public_Notices/2000/da000813.doc
  • New York, NY Office (3/31/00). 47 C.F.R. Part 11 (Emergency Alert System (EAS) Rules) 47 C.F.R. § 11.15 (EAS Operating Handbook) Cablevision of Massachusetts, Allston, MA. NOV also issued for violation of 47 C.F.R. §§ 11.21, and 11.61. New England District Office (3/10/00). Booth-Newsome Broadcasting, Inc., WKTE, King, North Carolina. NOV also issued for violation of 47 C.F.R. §§ 11.32, 11.33, 11.35, 11.52, 11.61, 73.49, 73.51, 73.1225, 73.1400 73.1350, 73.1560, 73.1590, 73.1870, and 73.3526. Norfolk, VA Office (3/13/00). KICO/AM 1490 kHz, Hanson Broadcasting Co. San Diego, CA Office (3/27/00). First Assembly of God, Gainesville, FL. NOV also issued for violation of 47 C.F.R. § 11.52 and 11.61. Tampa, FL Office (3/28/00). KGBA/FM, 100.1 MHz, The Voice of International Christian. San Diego,
• http://www.fcc.gov/Bureaus/Enforcement/Public_Notices/2000/da002136.doc
  • Irving, TX. Dallas, TX District Office (8/18/00). Atlanta Gas Light Company, Atlanta, GA. Other violations: 47 C.F.R. §§ 90.233 (Base/Mobile Non-Voice Operations) and 90.403 (General Operating Requirements). Atlanta, GA District Office (8/29/00). 47 C.F.R. Part 11 - Emergency Alert System 47 C.F.R. § 11.15 - EAS Operating Handbook Cherokee Broadcasting Company, Inc. Other violations: 47 C.F.R. §§ 11.32 (EAS Encoder), 11.33 (EAS Decoder), 11.35 (Equipment Operational Readiness), 11.52 (EAS Code and Attention Signal Monitoring Requirements), 11.61 (Tests of EAS Procedures), 17.4 (Antenna Structure Registration), 17.50 (Cleaning and Repainting), and 73.1230 (Posting of Station License). Norfolk, VA Resident Agent Office (8/01/00). AT&T Broadband, Des Moines, IA. Other violations: 47 C.F.R. §§ 11.52 (EAS Code and Attention Signal Monitoring Requirements), 11.54 (EAS Operation
• 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
  • 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 provide that
• http://www.fcc.gov/eb/Orders/2001/fcc01088.doc http://www.fcc.gov/eb/Orders/2001/fcc01088.html
  • after station processing to attain the required modulation level. According to SBE, this situation is ``adverse to acceptable engineering practice.'' We agree with SBE and propose to amend Section 11.51(f) of the Rules to permit a minimum modulation level of 50%. We invite comment on this proposal. Compatibility of EAS Equipment with NWR-SAME System NWS requests that we amend Section 11.33(a)(4) and (a)(5) of the Rules to permit EAS decoders to display or log receipt of only those event codes and accompanying location codes for which the decoder is programmed for mandatory receipt and those optionally set by the device user. Section 11.33(a)(4) and (a)(5) requires EAS decoders to display messages from any valid EAS header codes received. Therefore, EAS participants
• http://www.fcc.gov/eb/Orders/2002/FCC-02-64A1.html
  • with SBE that it is important that EAS decoders have the capability to store and forward EAS messages or to automatically pass through EAS messages.165 Accordingly, we will not relax the certification requirements for EAS decoders. In order to receive FCC certification, EAS decoders will be required to satisfy all of the existing requirements for decoders set forth in Section 11.33 of the Rules.166 Small cable systems which opt to install decoder-only units will not be able to originate EAS messages or generate RWTs. However, these small cable systems will still be able to pass through EAS messages and accomplish Required Weekly Testing by forwarding a received RWT. Thus, we do not believe that permitting small cable systems to install decoder-only
• http://www.fcc.gov/eb/Orders/2004/FCC-04-189A1.html
  • often called an ENDEC unit. EAS equipment sends and receives messages using a precise format referred to as the EAS digital protocol. An emergency activation of EAS uses a four part message: (1) preamble and EAS header codes; (2) audio attention signal; (3) message; and (4) preamble and EAS end of message codes. See 47 C.F.R. 11.31(a). 37 47 C.F.R. 11.33(a)(4), 11.51(k)(1), 11.54. 38 47 C.F.R. 11.31(c). 39 47 C.F.R. 11.31(a)(3)(i). 40 MSRC was formed following the events of September 11, 2001, to study, develop, and report on Best Practices designed to ensure the continued operations and security of media facilities in times of a national emergency. See FCC News Release, FCC Announces Creation of Media Security & Reliability Council; Tribune
• http://www.fcc.gov/eb/Orders/2005/FCC-05-191A1.html
  • (or common studio or control point if there is no hub station) and rebroadcast 100% of the programming of the hub station (or common studio or control point) may satisfy the requirements of this part through the use of a single set of EAS equipment at the hub station (or common studio or control point) which complies with 11.32 and 11.33. * * * * * (e) Organizations using other communications systems or technologies such as low earth orbit satellite systems, paging, computer networks, etc. may join the EAS on a voluntary basis by contacting the FCC. Organizations that choose to voluntarily participate must comply with the requirements of this part. 4. Revise 11.13 to read as follows: 11.13 Emergency Action
• http://www.fcc.gov/eb/Orders/2008/DA-08-1717A1.html
  • 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 2007 AM and FM Handbook
• http://www.fcc.gov/eb/Public_Notices/da002136.doc http://www.fcc.gov/eb/Public_Notices/da002136.html
  • Irving, TX. Dallas, TX District Office (8/18/00). Atlanta Gas Light Company, Atlanta, GA. Other violations: 47 C.F.R. §§ 90.233 (Base/Mobile Non-Voice Operations) and 90.403 (General Operating Requirements). Atlanta, GA District Office (8/29/00). 47 C.F.R. Part 11 - Emergency Alert System 47 C.F.R. § 11.15 - EAS Operating Handbook Cherokee Broadcasting Company, Inc. Other violations: 47 C.F.R. §§ 11.32 (EAS Encoder), 11.33 (EAS Decoder), 11.35 (Equipment Operational Readiness), 11.52 (EAS Code and Attention Signal Monitoring Requirements), 11.61 (Tests of EAS Procedures), 17.4 (Antenna Structure Registration), 17.50 (Cleaning and Repainting), and 73.1230 (Posting of Station License). Norfolk, VA Resident Agent Office (8/01/00). AT&T Broadband, Des Moines, IA. Other violations: 47 C.F.R. §§ 11.52 (EAS Code and Attention Signal Monitoring Requirements), 11.54 (EAS Operation
• http://www.fcc.gov/eb/Public_Notices/da00813.doc http://www.fcc.gov/eb/Public_Notices/da00813.html
  • New York, NY Office (3/31/00). 47 C.F.R. Part 11 (Emergency Alert System (EAS) Rules) 47 C.F.R. § 11.15 (EAS Operating Handbook) Cablevision of Massachusetts, Allston, MA. NOV also issued for violation of 47 C.F.R. §§ 11.21, and 11.61. New England District Office (3/10/00). Booth-Newsome Broadcasting, Inc., WKTE, King, North Carolina. NOV also issued for violation of 47 C.F.R. §§ 11.32, 11.33, 11.35, 11.52, 11.61, 73.49, 73.51, 73.1225, 73.1400 73.1350, 73.1560, 73.1590, 73.1870, and 73.3526. Norfolk, VA Office (3/13/00). KICO/AM 1490 kHz, Hanson Broadcasting Co. San Diego, CA Office (3/27/00). First Assembly of God, Gainesville, FL. NOV also issued for violation of 47 C.F.R. § 11.52 and 11.61. Tampa, FL Office (3/28/00). KGBA/FM, 100.1 MHz, The Voice of International Christian. San Diego,
• http://www.fcc.gov/pshs/docs/services/eas/Second.pdf
  • and co- located with a combined studio or control facility (such as an AM and FM licensed to the same entity and at the same location or a cable headend serving more than one system) may comply with the EAS monitoring requirements contained in this section for the combined station or system with one EAS Decoder. The requirements of § 11.33 must be met by the combined facility. (d) Broadcast stations and cable systems and wireless cable systems 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 Mapbook. They are developed in accordance with FCC monitoring priorities. (1) If the required EAS