FCC Web Documents citing 11.44

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

• http://fjallfoss.fcc.gov/edocs_public/attachmatch/FCC-07-109A1.doc http://fjallfoss.fcc.gov/edocs_public/attachmatch/FCC-07-109A1.pdf
  • Commission's EAS rules are intended to ensure that national activation of EAS would enable the President to communicate with the American public within ten minutes from any location at any time. These messages must take priority over any other messages and preempt other messages in progress. First Report and Order, 20 FCC Rcd at 18628, ¶ 8; 47 C.F.R. § 11.44(a). (August 30, 2006). (March 6, 2007). The seven NWR frequencies (MHz) are: 162.400, 162.425, 162.450, 162.475, 162.500, 162.525, and 162.550. Id. The digital protocol is known as Specific Area Message Encoding (SAME). See The Emergency Alert System (EAS): An Assessment, Partnership for Public Warning Report 2004-1, at 18. See id. at 7. In some localities, emergency managers can originate EAS
• http://fjallfoss.fcc.gov/edocs_public/attachmatch/FCC-10-11A1.doc http://fjallfoss.fcc.gov/edocs_public/attachmatch/FCC-10-11A1.pdf
  • public within ten minutes from any location at any time. These messages must take priority over any other messages and preempt other messages in progress. Review of the Emergency Alert System, EB Docket No. 04-296, First Report and Order and Further Notice of Proposed Rulemaking, 20 FCC Rcd 18625, 18628, ¶ 8 (2005) (First Report and Order); 47 C.F.R. § 11.44(a). A more detailed overview of the history of EAS is set out in the first Notice of Proposed Rulemaking in this docket. See Review of the Emergency Alert System, EB Docket No. 04-296, Notice of Proposed Rulemaking, 19 FCC Rcd 15775, 15776-77, ¶¶ 6-8 (2004 NPRM). FEMA acts as Executive Agent for the development, operation, and maintenance of the national-level
• http://fjallfoss.fcc.gov/edocs_public/attachmatch/FCC-11-12A1.doc http://fjallfoss.fcc.gov/edocs_public/attachmatch/FCC-11-12A1.pdf
  • public within ten minutes from any location at any time. These messages must take priority over any other messages and preempt other messages in progress. Review of the Emergency Alert System, EB Docket No. 04-296, First Report and Order and Further Notice of Proposed Rulemaking, 20 FCC Rcd 18625, 18628, ¶ 8 (2005) (First Report and Order); 47 C.F.R. § 11.44(a). A more detailed overview of the history of EAS is set out in the first Notice of Proposed Rulemaking in this docket. See Review of the Emergency Alert System, EB Docket No. 04-296, Notice of Proposed Rulemaking, 19 FCC Rcd 15775, 15776-77, ¶¶ 6-8 (2004 NPRM). FEMA acts as Executive Agent for the development, operation, and maintenance of the national-level
• http://fjallfoss.fcc.gov/edocs_public/attachmatch/FCC-11-82A1.doc http://fjallfoss.fcc.gov/edocs_public/attachmatch/FCC-11-82A1.pdf
  • and related Part 11 rule sections so that EAS Participants process EANs like any other EAS message, only on a mandatory and priority basis. We also seek comment on whether the Commission should: eliminate the Emergency Action Termination event code and replace it where necessary with the End Of Message code in the Part 11 rules; delete sections 11.16, 11.42, 11.44, and 11.54(a), (b)(1)-(8), (10), (12), and 11.54(c) of the rules; and eliminate the EAS Operating Handbook 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
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-00-1358A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-00-1358A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-00-1358A1.txt
  • characteristics (strapping table and noise/gamma table). This information was deemed as unnecessary in view of the coordination arc trigger and the separate analyses of uplink and downlink noise temperature increases rather than a combined analysis of total system noise temperature increase. All the foregoing provisions are effective from 3 June 2000. Requirement to notify WRC-2000 also adopted a new provision (S11.44.1) effective 1 January 2002 that requires the frequency assignments for a satellite network whose Advance Publication Information (API) was received on or after 22 November 1997 to be notified within seven years from the date of receipt of the API. For those networks whose APIs were received prior to 22 November 1997, the corresponding period is nine years from the
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-00-2796A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-00-2796A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-00-2796A1.txt
  • 5. 525 F.2d 630 (D.C. Cir.), cert. denied, 425 U.S. 992 (1976). Id. at 642. 47 C.F.R. § 25.145(f). See also Ka-band Third Report and Order, 12 FCC Rcd at 22334-35 ¶ 61 & n.77. The exact date is nine years after the date of ITU publication of the Advanced Publication Information for each orbit location. See ITU Radio Regulations S11.44, as modified by Final Acts of the 2000 World Radiocommunication Conference, Istanbul (2000). Thus, the ITU Radio Regulations require that the satellite at 67° W.L. be brought into use by June 25, 2005, and the satellite at 126.5° E.L. be brought into use by July 23, 2005. See Ka-band Third Report and Order, 12 FCC Rcd at 22335-39 ¶¶ 63-72.
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-00-2796A1_Erratum.doc
  • 5. 525 F.2d 630 (D.C. Cir.), cert. denied, 425 U.S. 992 (1976). Id. at 642. 47 C.F.R. § 25.145(f). See also Ka-band Third Report and Order, 12 FCC Rcd at 22334-35 ¶ 61 & n.77. The exact date is nine years after the date of ITU publication of the Advanced Publication Information for each orbit location. See ITU Radio Regulations S11.44, as modified by Final Acts of the 2000 World Radiocommunication Conference, Istanbul (2000). Thus, the ITU Radio Regulations require that the satellite at 67° W.L. be brought into use by June 25, 2005, and the satellite at 126.5° E.L. be brought into use by July 23, 2005. See Ka-band Third Report and Order, 12 FCC Rcd at 22335-39 ¶¶ 63-72.
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-01-1686A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-01-1686A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-01-1686A1.txt
  • be brought into use by July 2, 2005; and the satellite at 103° E.L. must be brought into use by July 16, 2005. With regard to the 131° W.L. orbital location, ITU Radio Regulations require that the satellite be "brought-into-use" (BIU) no later than five years from the date the ITU publishes the advance publication information. (ITU Radio Regulations Article S11.44). The ITU may extend the BIU date by two years under the conditions specified in ITU Radio Regulations Articles S11.44B through S11.44I (launch failure; launch delays due to circumstances outside the control of the administration or operator; delays caused by modifications of satellite design necessary to reach coordination agreements; problems in meeting the satellite design specifications; delays in reaching coordination
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-01-1687A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-01-1687A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-01-1687A1.txt
  • FSS Rules Order, 12 FCC Rcd at 22334-35 ¶ 61 & n.77 (1997). ITU Radio Regulations require that the satellite at 111° W.L. be brought into use by March 9, 2003. ITU Radio Regulations require that the satellite be ``brought-into-use'' (``BIU'') no later than five years from the date the ITU publishes the advance publication information. (ITU Radio Regulations Article S11.44). The ITU may extend the BIU date by two years under the conditions specified in ITU Radio Regulations Articles S11.44B through S11.44I (launch failure; launch delays due to circumstances outside the control of the administration or operator; delays caused by modifications of satellite design necessary to reach coordination agreements; problems in meeting the satellite design specifications; delays in reaching coordination
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-01-1688A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-01-1688A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-01-1688A1.txt
  • be brought into use by July 16, 2005, and the satellite at 151.5° E.L. must be brought into use by July 23, 2005. With regard to the 129° W.L. and 51° W.L. orbital locations, ITU Radio Regulations require that the satellites be "brought-into-use" (BIU) no later than five years after ITU receipt of advance publication information (ITU Radio Regulations Article S11.44). The ITU may extend the BIU date by two years under the conditions specified in ITU Radio Regulations Articles S11.44B through S11.44I (launch failure; launch delays due to circumstances outside the control of the administration or operator; delays caused by modifications of satellite design necessary to reach coordination agreements; problems in meeting the satellite design specifications; delays in reaching coordination
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-01-1691A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-01-1691A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-01-1691A1.txt
  • be brought into use by July 23, 2005; and the satellites at 72.7° E.L and 166° E.L. must be brought into use by July 30, 2005. With regard to the 133° W.L. orbital location, ITU Radio Regulations require that the satellite be ``brought-into-use'' (BIU) no later than five years after ITU receipt of advance publication information. (ITU Radio Regulations Article S11.44). The ITU may extend the BIU date by two years under the conditions specified in ITU Radio Regulations Articles S11.44B through S11.44I (launch failure; launch delays due to circumstances outside the control of the administration or operator; delays caused by modifications of satellite design necessary to reach coordination agreements; problems in meeting the satellite design specifications; delays in reaching coordination
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-01-1692A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-01-1692A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-01-1692A1.txt
  • 28° E.L. must be brought into use by July 2, 2005, and the satellite at 107.5° E.L. must be brought into use by July 16, 2005. With regard to the 107° W.L. orbital location, ITU Radio Regulations require that the satellite be "brought-into-use" (BIU) no later than five years after ITU receipt of advance publication information (ITU Radio Regulations Article S11.44). The ITU may extend the BIU date by two years under the conditions specified in ITU Radio Regulations Articles S11.44B through S11.44I (launch failure; launch delays due to circumstances outside the control of the administration or operator; delays caused by modifications of satellite design necessary to reach coordination agreements; problems in meeting the satellite design specifications; delays in reaching coordination
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-01-1694A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-01-1694A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-01-1694A1.txt
  • 15° E.L. must be brought into use by March 9, 2003; and the satellite at 116.5° E.L. must be brought into use by July 16, 2005. With regard to the 15° E.L. orbital location, ITU Radio Regulations require that the satellite be "brought-into-use" (BIU) no later than five years after ITU receipt of advance publication information. (ITU Radio Regulations Article S11.44). The ITU may extend the BIU date by two years under the conditions specified in ITU Radio Regulations Articles S11.44B through S11.44I (launch failure; launch delays due to circumstances outside the control of the administration or operator; delays caused by modifications of satellite design necessary to reach coordination agreements; problems in meeting the satellite design specifications; delays in reaching coordination
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-01-221A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-01-221A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-01-221A1.txt
  • be exceeded by up to 3 dB for no more than 5% of the time. 47 C.F.R. § 25.145(f). See also Third Report and Order at ¶ 61 and fn. 77. The exact date is nine years after the date the ITU publishes the Advanced Publication Information for the concerned frequency assignment at each orbit location. See ITU Radio Regulations S.11.44, as modified by Final Acts of the 2000 World Radiocommunication Conference, Istanbul (2000). Thus, the ITU Radio Regulations require that: the USA satellite network advanced published at 97° W.L. be brought into use by June 25, 2005; the USA satellite network advanced published at 21.5° W.L. be brought into use by July 9, 2005; the USA satellite network advanced published
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-01-222A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-01-222A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-01-222A1.txt
  • Rules and Policies for Local Multipoint Distribution Service and for Fixed Satellite Services, CC Docket No. 92-297, Third Report and Order, 12 FCC Rcd 22310, 22334-35 ¶ 61 & n.77 (1997). The exact date is nine years after the date the ITU publishes the Advanced Publication Information for the concerned frequency assignment at each orbit location. See ITU Radio Regulations S.11.44, as modified by Final Acts of the 2000 World Radiocommunication Conference, Istanbul (2000). Thus, the ITU Radio Regulations require that: the USA satellite advanced published at 91° W.L. be brought into use by June 25, 2005; the USA satellite advanced published at 87° W.L. be brought into use by June 25, 2005; the USA satellite advanced published at 77° W.L.
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-01-222A1_Erratum.doc
  • Rules and Policies for Local Multipoint Distribution Service and for Fixed Satellite Services, CC Docket No. 92-297, Third Report and Order, 12 FCC Rcd 22310, 22334-35 ¶ 61 & n.77 (1997). The exact date is nine years after the date the ITU publishes the Advanced Publication Information for the concerned frequency assignment at each orbit location. See ITU Radio Regulations S.11.44, as modified by Final Acts of the 2000 World Radiocommunication Conference, Istanbul (2000). Thus, the ITU Radio Regulations require that: the USA satellite advanced published at 91° W.L. be brought into use by June 25, 2005; the USA satellite advanced published at 87° W.L. be brought into use by June 25, 2005; the USA satellite advanced published at 77° W.L.
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-01-223A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-01-223A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-01-223A1.txt
  • Rules and Policies for Local Multipoint Distribution Service and for Fixed Satellite Services, CC Docket No. 92-297, Third Report and Order, 12 FCC Rcd 22310, 22334-35 ¶ 61 & n.77 (1997). The exact date is nine years after the date the ITU publishes the Advanced Publication Information for the concerned frequency assignment at each orbit location. See ITU Radio Regulations S.11.44, as modified by Final Acts of the 2000 World Radiocommunication Conference, Istanbul (2000). Thus, the ITU Radio Regulations require that the satellite at 115° W.L. be brought into use by June 25, 2005; the satellite at 93° W.L. be brought into use by June 25, 2005; and the satellite at 105.5° E.L. be brought into use by July 16, 2005.
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-01-224A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-01-224A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-01-224A1.txt
  • Rules and Policies for Local Multipoint Distribution Service and for Fixed Satellite Services, CC Docket No. 92-297, Third Report and Order, 12 FCC Rcd 22310, 22334-35 ¶ 61 & n.77 (1997). The exact date is nine years after the date the ITU publishes the Advanced Publication Information for the concerned frequency assignment at each orbit location. See ITU Radio Regulations S.11.44, as modified by Final Acts of the 2000 World Radiocommunication Conference, Istanbul (2000). Thus, the ITU Radio Regulations require that: the USA satellite advanced published at 121° W.L. be brought into use by June 25, 2005; and the USA satellite advanced published at 83° W.L. be brought into use by June 25, 2005. Indeed, EchoStar has represented it has made
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-01-226A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-01-226A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-01-226A1.txt
  • Rules and Policies for Local Multipoint Distribution Service and for Fixed Satellite Services, CC Docket No. 92-297, Third Report and Order, 12 FCC Rcd 22310, 22334-35 ¶ 61 & n.77 (1997). The exact date is nine years after the date the ITU publishes the Advanced Publication Information for the concerned frequency assignment at each orbit location. See ITU Radio Regulations S.11.44, as modified by Final Acts of the 2000 World Radiocommunication Conference, Istanbul (2000). Thus, the ITU Radio Regulations require that: the USA satellite network advanced published at 101° W.L. be brought into use by June 25, 2005; the USA satellite network advanced published at 99° W.L. be brought into use by June 25, 2005; the USA satellite network advanced published
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-01-227A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-01-227A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-01-227A1.txt
  • 89° W.L. Modification at 2. ISL Modification Applications at 5 n.11. According to Loral Corp.'s annual status report, Orion F7 is the Ka-band satellite planned to operate at the 89° W.L. orbit location. See Loral Space & Communications Ltd. Annual Status Report for the year ending May 31, 2000, redacted version at 16 (June 30, 2000). See ITU Radio Regulation S11.44. Norris Satellite Communications, Inc., Order, 11 FCC Rcd 5402 (Int'l Bur. 1996). See Norris Satellite Communications, Inc. Petition for Reconsideration in the Matter of Comm, Inc. and Orion Network Systems, Inc., File Nos. 163/164/165/166-SAT-P/LA-95, 201 SAT-MISC-95; 195/196/197-SAT-P/LA-95, 205-SAT-AMEND-95 (filed June 9, 1997); see also Opposition to Petition for Reconsideration of Orion Network Systems, Inc. (filed June 24, 1997). Norris Satellite
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-01-228A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-01-228A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-01-228A1.txt
  • Frequency Band, to Establish Rules and Policies for Local Multipoint Distribution Service and for Fixed Satellite Services, CC Docket No. 92-297, Third Report and Order, 12 FCC Rcd 22310, 22334-35 ¶ 61 & n.77 (1997). The exact date is nine years after the date of ITU publication of the Advanced Publication Information for each orbit location. See ITU Radio Regulations S.11.44, as modified by Final Acts of the 2000 World Radiocommunication Conference, Istanbul (2000). Thus, the ITU Radio Regulations require that: the satellite licensed at 36°E.L. be brought into use by July 2, 2005; the satellite licensed at 40°E.L. be brought into use by July 2, 2005; the satellite licensed at 48° E.L. be brought into use by July 2, 2005;
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-01-229A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-01-229A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-01-229A1.txt
  • GHz Frequency Band, to Establish Rules and Policies for Local Multipoint Distribution Service and for Fixed Satellite Services, CC Docket No. 92-297, Third Report and Order, 12 FCC Rcd 22310, 22334-35 ¶ 61 & n.77 (1997). This date is nine years after the date the ITU published the Advanced Publication Information for the concerned frequency assignments. See ITU Radio Regulations S.11.44, as modified by Final Acts of the 2000 World Radiocommunication Conference, Istanbul (2000). Federal Communications Commission DA 01-229 Federal Communications Commission DA 01-229 Ã Ä � (R) Ä Å (R) Ä Å F @& @& „Ð @& @& Óÿÿÿ � Ðÿÿÿ Ñÿÿÿ „Ð „0ý „0ý „0ý „0ý „0ý „0ý „0ý „`ú „0ý 1 ''
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-01-231A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-01-231A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-01-231A1.txt
  • Rules and Policies for Local Multipoint Distribution Service and for Fixed Satellite Services, CC Docket No. 92-297, Third Report and Order, 12 FCC Rcd 22310, 22334-35 ¶ 61 & n.77 (1997). The exact date is nine years after the date the ITU publishes the Advanced Publication Information for the concerned frequency assignment at each orbit location. See ITU Radio Regulations S.11.44, as modified by Final Acts of the 2000 World Radiocommunication Conference, Istanbul (2000). Thus, the ITU Radio Regulations require that: the USA satellite advanced published at 109.2° W.L. be brought into use by June 25, 2005; and the USA satellite advanced published at 73° W.L. be brought into use by October 7, 2006. See Annual Statement from David M. Brown,
• 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
  • local levels. Need: By setting participation standards and acceptable uses, these rules ensure the integrity of EAS for the Presidential message priority in the event of a national emergency. Legal Basis: 47 U.S.C. 151, 154 (i) and (o), 303(r), 544(g) and 606. Section Number and Title: 11.41 Participation in EAS. 11.42 Participation by communications common carriers. 11.43 National level participation. 11.44 EAS message priorities. 11.45 Prohibition of false or deceptive EAS transmissions. 11.46 EAS public service announcements. 11.47 Optional use of other communications methods and systems. SUBPART D - EMERGENCY OPERATIONS Brief Description: These rules describe procedures for monitoring key EAS sources. Once EAS has been activated, these rules set operation and transmission guidelines for national, state, and local level messaging.
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-05-1774A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-05-1774A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-05-1774A1.txt
  • (number of networks) Number of administrations Period of survey Due diligence received by 31.12.2002 (number of networks) Due diligence published by 31.12.2002 (number of networks) Cancellation by 31.12.2002 (number of networks) Non-planned services 1574 Over 45 2DBIU ( 30.06.03 878 878 152* Planned services 179** 32 DBIU < 01.06.03 42 42 2 * All satellite networks cancelled under provision No. 11.44 of the Radio Regulations (frequency assignment not brought into use within the regulatory time-frame). ** 108 reminders have been sent in accordance with resolves 4 and Paragraph 10 of Annex 1 to Resolution 49. 111 Special Sections (AP30/E, AP30A/E) were published to modify the date of bringing into use. 5. WRC-03 suppressed Nos. 11.44B, C, D, E, F, G, H,
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-06-2013A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-06-2013A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-06-2013A1.txt
  • in Section II of Article 9 below, where applicable, send to the Bureau a general description of the network or system for advance publication in the International Frequency Information Circular (BR IFIC) not earlier than seven years and preferably not later than two years before the planned date of bringing into use of the network or system (see also No. 11.44). The characteristics to be provided for this purpose are listed in Appendix 4. The coordination or notification information may also be communicated to the Bureau at the same time.; Where coordination information is required by Section II of Article 9, the coordination information it shall be considered as having been received by the Bureau upon its actual date of receipt
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-06-960A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-06-960A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-06-960A1.txt
  • the end of WRC-03, shall not be brought into use before the end of WRC-07no submissions for GSO BSS networks and non-GSO BSS satellite networks or systems in the frequency band 620-790 MHz under Articles 9 or 11 of the Radio Regulations involving digital transmission shall be accepted; 54 that the notified date of bringing into use referred in Nos. 11.44 and 11.48 for GSO BSS networks and non-GSO BSS satellite networks or systems in this frequency band for which the Bureau receives notification prior to 5 July 2003 shall be extended by the length of the period from the date of receipt by the Bureau of the complete advanced publication information to the end of WRC-07;5 that the BSS systems
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-07-3470A6.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-07-3470A6.txt
  • Markets with HHI in Range Variable Mean for All Stations0 HHI < 1,000 [1] 1,000 HHI < 2,000 [2] 2,000 HHI < 3,000 [3] 3,000 HHI < 4,000 [4] 4,000 HHI [5] All Format 101 Count 14.94 23.94 16.23 11.80 9.93 6.29 -17.66 - Format 101 HHI 0.10 0.07 0.09 0.11 0.12 0.20 0.13 + Format 20 Count 10.70 14.53 11.44 9.36 8.17 5.86 -8.67 - Format 20 HHI 0.14 0.11 0.13 0.14 0.16 0.22 0.11 + Format 11 Count 8.04 9.56 8.54 7.50 6.63 5.00 -4.56 - Format 11 HHI 0.17 0.16 0.16 0.18 0.19 0.25 0.10 + Number of Stations 24.20 47.68 26.00 16.85 13.00 8.57 -39.11 - FM Only Format 101 Count 10.35 15.50 11.24 8.64 7.03 4.29
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-08-946A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-08-946A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-08-946A1.txt
  • carrier for emissions 26M9G7W, 17M9G7W, 16M9D7W, 16M9G7W, 8M43D7W, 8M43G7W, 7M34G7W, 8M43D7W, 8M43G7W, and 7M34G7W, respectively. Based on this information, and by subtracting the antenna gain (47.2 dBi listed in response to item E41 of Schedule B) from the e.i.r.p. density, we calculate the power density at the input of the antenna flange as -13.48, -11.71, -11.46, -11.46, -8.44, -8.44, -7.84, -11.44, -11.44, and -10.84 dBW/4kHz, respectively. This value exceeds the -14.0 dBW/4kHz power density limit for two-degree compliant earth stations contained in Section 25.212(c) of the Commission's rules, 47 C.F.R. § 25.212(c). Thus, NHK cannot use an ALSAT designation for these emissions and must specifically list all satellites that the earth station intends to communicate with when using these emissions. Third,
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-09-1994A2.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-09-1994A2.txt
  • BACKGROUND:WRC-07consideredthereportofITUstudiesinresponsetoResolution951 (WRC-03)onmethodstoimprovetheinternationalspectrumregulatoryframework.Thisreport identifiedanumberofoptionsforaddressingtheevolutionofradioapplications,systemsand technologieswhichincludethefollowing: Option1:keepingthecurrentservicedefinitionsandnotintroducinganychangestothelTU RadioRegulations(RR)withrespecttothisagendaitem; Option 2:reviewingandpossiblyrevisingthecurrentservicedefinitionsoraddingoneormore newservicestothelistofservicedefinitions,eachoneencompassingseveraloftheexistingones; Option 3:introducinganewprovisionintheRRenablingsubstitutionbetweenassignmentsof specificservices; Option4:introducingcompositeservicesintheTableofFrequencyAllocations. WRC-07alsoadoptedarevisedversionofResolution951,callingforurgentstudiesinorderto developasappropriate,newconceptsandproceduresforenhancingtheRadioRegulationsto meetthedemandsofcurrent,emergingandfutureradioapplications,whiletakingintoaccount existingservicesandusage. Inparticular,itcallsforstudiesaimedat:a)evaluatingoptionsfor enhancingspectrummanagementsolutionsforincreasedflexibilityinmeetingnewdemands;b) developingapplicableconceptsandproceduresincludingsharingstudiesonaband-by-bandbasis tosupporttheseoptions;c)preparingrelevanttechnicalandregulatorysolutionsforconsideration andappropriateactionatWRC-l1. DISCUSSION:TheUnitedStatesrecognizestheimportanceofaspectrumregulatoryframework thatallowsflexiblespectrumuse,totheextentpracticable,soastoallowfortheevolutionof servicesandtechnologies,takingintoaccountexistingservicesandusage.Accordingly,the UnitedStateshas,consistentlyadopteddomesticservicerulestoaccommodateemerging technologies,or,invariousinstances,soughtchangesintheITURadioRegulationsinorderto accommodateneworevolvingsystems.Theseapproacheshaveallowedthetimelydeploymentof newtechnologies.Ineithercase,suchchangeshavebeensoughtaftercarefulevaluation,ona case-by-casebasis,ofthenewservice'srequirements,andtheirabilitytoco-existwithotherco- frequencysystems. U.S.VIEW:TheUnitedStatesisoftheviewthatsupportforproposalsforenhancingthe internationalregulatoryframeworkinspecificsituationsshouldbeevaluatedusingtheguidelines setforthinAnnex 2ofRes.951(WRC-07).TheUnitedStatesisalsooftheviewthatstudies shouldbeconductedonafrequencybandbyfrequencybandbasisconsistentwiththeguidelines 30 inthisAnnex.TheUnitedStatesmayconsidersupportingproposalsunderAgendaItem1.2ona casebycasebasis,takingintoaccounttheguidelinesintheAnnexestoResolution951.The UnitedStatesdoesnotsupportlarge-scalemodificationstotheinternationalregulatory frameworksinceitbelievesthatthecurrentregulatoryframework,includingtheWRCprocess,is sufficientlyflexibletoaccommodatenewtechnologies. 31 DOCUMENTWAC/042(Ol.09.09) UnitedStatesofAmerica DRAFTPROPOSALSFORTHEWORKOFTHECONFERENCE WRC-11AgendaItem7: toconsiderpossiblechangesinresponsetoResolution86(Rev. Marrakesh,2002)ofthePlenipotentiaryConference:"Advancepublication,coordination, notificationandrecordingproceduresforfrequencyassignmentspertainingtosatellite networks",inaccordancewithResolution86(Rev.WRC-07) Backgroundinformation:Accesstothegeostationaryorbit(GSa)hasbecomeincreasingly difficultovertheyears,inlargepartduetodifficultiesinfullycoordinatingneworbitalpositions andapplyingtherelevantprovisionsoftheRadioRegulations.Ashighlightedatthemostrecent ITURadiocommunicationsBureau(BR)workshoponefficientuseofthespectrum/orbitresource andinITUadministrativecircularCRl301,ithasbeennotedthatsomeunusedfrequencyand GSa resourcesremainrecordedintheMasterInternationalFrequencyRegister,whichservesto worsenthisproblem.Assuch,improvingtransparencyintoactualusageoffrequencyandGSa resourcescouldhelptoimprovethissituation. Fornon-plannedsatellitebands,No.11.44oftheRadioRegulations(RR)requiresthatthe notifieddateofbringingintouseofanyassignmenttoaspacestationofasatellitenetworkshall notbelaterthansevenyearsfollowingthedateofreceiptoftherelevantcompleteinformation underRRNo.9.1or9.2,asappropriate.Additionally,thisprovisionstatesthatanyfrequency assignmentnotbroughtintousewithintherequiredperiodshallbecancelledbytheBR.When thenotifieddateofbringingintouseoffrequencyassignmentsisearlierthanthedateof submissionoftheNotificationrequest,theNotificationrequestitselfisconsideredbytheBRas confirmationthatthefrequencyassignmentshavebeenbroughtintouse.Furthermore,RRNo. 11.47clarifiestherequirementforadministrationstoinformtheBRoffrequenciesassignments broughtintouseforthecaseofassignmentsbeingNotifiedbeforebeingbroughtintouse. Therefore,itcanbeconsideredthattherearetwoseparaterequirements.Underthefirst,theBR mustreceivetheNotificationinformationforfrequencyassignmentsinanetworkbytheendof theregulatorylifetimeofthesatellitenetworkfiling,whereasunderthesecondtheBRmusthave beeninformedthatthefrequencyassignmentshaveactuallybeenbroughtintousebyadate certain. Thepotentialdifficultywiththecurrentprocessisthatitcanresultinuncertaintyfor administrationsastothestatusoffrequencyassignmentsforseveralreasons.Forexample,while administrationscanexaminetheSRSdatabasefordetailspertainingtonotifiedfrequency assignmentsthathavebeensubmittedtotheBR(PartI-S),orexaminedbytheBRandfoundto beinconformitywiththeRadioRegulations(PartII-S),theycannotreadilydeterminewhetheror notadministrationshaveinformedtheBRthatfrequencyassignmentshavebeenbroughtintouse, andifsothedateonwhichtheywerebroughtintouse.Thiscanresultinuncertaintyfor administrationsastotheprovisionalordefinitivestatusoffrequencyassignmentsintheMIFR,or whetheranadministrationhasmissedthedeadlineunderRRNo.11.44entirelyanditissimplya matteroftimebeforetheprovisionallynotifiedfrequencyassignmentsaresuppressed. Additionally,thereiscurrentlynospecificrequirementtoinformtheBRwithinaspecifiedtime limitthatfrequencyassignmentshaveactuallybeenbroughtintouse.Assuch,assignmentscan bebroughtintouseonagivendateandtheNotificationinformationfortheseassignmentscanbe 32 submittedtotheBRatanylaterdate,providedthatthedateofthatsubmissionisearlierthanthe endofthetimelimitfornotifyingthenetwork. Theuncertaintyassociatedwithfrequencyassignmentsandsatellitenetworksactuallybrought intousecanbeaddressedbyrequiringadministrationstoinformtheBRwithinaspecifiedtime periodthatfrequencyassignmentsassociatedwithasatellitenetworkhaveactuallybeenbrought intouseandbyhavingtheBRmakeinformationreceivedfromadministrationsregardingsuch bringingintousepubliclyavailable.TheBRhasestablished,onatrialbasis,twowebpagesfor providingsuchinformation:http://www.itu.int/ITU-Rlspace/snIllistinuse/fornon-plannedbands andhttp://www.itu.int/ITU-Rlspace/snIllistinuseplan/forplannedbands.TheBRshouldbe instructedtocontinuetobuildthelistofnetworkscontainedonthesepagesandtomakethese pagespermanent.Inaddition,itwouldalsobeusefulif,onthissamewebpage,ahyperlinkwere includedtotheResolution49informationassociatedwiththebringingintouseofthefrequency assignmentsinquestion. Inadditiontotheuncertaintyassociatedwithfrequencyassignmentsandsatellitenetworks actuallybroughtintouse,therecanalsobeuncertaintyassociatedwiththeAnnex2dataof Resolution49.ThisisduetothefactthatResolution49callsfordatatobesubmittedasearlyas possiblebeforetheendoftheregulatorylifetimeofthefiling,orasearlyaspossiblebefore satellitelaunchand,foravarietyofreasons,itispossibleforcertainofthesedataelementsto changeaftersuchinitialsubmissionofthedata.Suchchangesaddtotheuncertaintyassociated withtheGSaresourcesactuallybeingusedbyadministrations. InordertoaddresstheuncertaintiesassociatedwithResolution49data,itisproposedtomodify thisResolution.TheproposedchangesentailrequiringsubmissionofResolution49dataonly aftertheBRhasbeeninformedthatfrequencyassignmentshavebeenbroughtintouse.Inthis way,theResolution49datawouldbecomedefinitiveastherewillbecertaintyassociatedwiththe datacalledforinAnnex2oftheResolution(i.e.launchdate,launchprovider,nameofsatellite, frequencybandsonthesatellite,etc.). Proposal: USA/xxiI MOD Theuncertaintyassociatedwithfrequencyassignmentsandsatellitenetworksactuallybrought intousecouldbeaddressedasfollows: 11.44
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-10-372A2.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-10-372A2.txt
  • use. In this way, the Resolution 49 data would become definitive as there will be certainty associated with the data called for the Resolution (i.e. launch date, launch provider, name of satellite, frequency bands on the satellite, etc.). Proposal: USA/xx/1 MOD The uncertainty associated with frequency assignments and satellite networks actually brought into use could be addressed as follows: 20 11.44.1 In the case of space station frequency assignments that are brought into use prior to the completion of the coordination process, and for which the Resolution 49 (Rev.WRC-1203)* data have been submitted to the Bureau, the assignment shall continue to be taken into consideration for a maximum period of seven years from the date of receipt of the relevant information
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-10-372A2_Rcd.pdf
  • use. In this way, the Resolution 49 data would become definitive as there will be certainty associated with the data called for the Resolution (i.e. launch date, launch provider, name of satellite, frequency bands on the satellite, etc.). Proposal: USA/xx/1 MOD The uncertainty associated with frequency assignments and satellite networks actually brought into use could be addressed as follows: 20 11.44.1 In the case of space station frequency assignments that are brought into use prior to the completion of the coordination process, and for which the Resolution 49 (Rev.WRC-1203)*data have been submitted to the Bureau, the assignment shall continue to be taken into consideration for a maximum period of seven years from the date of receipt of the relevant information under
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-10-372A3.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-10-372A3.txt
  • the recent ITU Radiocommunication Bureau Workshop on the Efficient Use of the Spectrum/Orbit Resource, and in ITU-R Circular Letter CR/301, some unused frequency and orbital resources remain recorded in the Master International Frequency Register, aggravating the problem. Improving the transparency of the processes for notification and bringing into use could help to improve this situation. For non-planned satellite bands, No. 11.44 of the Radio Regulations (RR) requires that "the notified date of bringing into use of any assignment to a space station of a satellite network shall not be later than seven years following the date of receipt...of the relevant complete information under RR No. 9.1 or 9.2, as appropriate." Additionally, this provision states that "any frequency assignment not brought into
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-10-372A3_Rcd.pdf
  • the recent ITU Radiocommunication Bureau Workshop on the Efficient Use of the Spectrum/Orbit Resource, and in ITU-R Circular Letter CR/301, some unused frequency and orbital resources remain recorded in the Master International Frequency Register, aggravating the problem. Improving the transparency of the processes for notification and bringing into use could help to improve this situation. For non-planned satellite bands, No. 11.44 of the Radio Regulations (RR) requires that "the notified date of bringing into use of any assignment to a space station of a satellite network shall not be later than seven years following the date of receipt...of the relevant complete information under RR No. 9.1 or 9.2, as appropriate." Additionally, this provision states that "any frequency assignment not brought into
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-11-447A2.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-11-447A2.txt
  • 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 any conditions related to the initial recording of assignments under No. 11.41 shall be
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-11-447A2_Rcd.pdf
  • 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 any conditions related to the initial recording of assignments under No. 11.41 shall be removed.
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-11-447A3.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-11-447A3.txt
  • 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 be removed. Reasons: The proposed modification to No. 11.41A will ensure that the BR consider
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-11-447A3_Rcd.pdf
  • 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 be removed. Reasons: The proposed modification to No. 11.41A will ensure that the BR consider
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-11-712A2.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-11-712A2.txt
  • highlighted in the text below are proposed changes to the NTIA proposals contained in Document IWG-4/093 addressing No. 11.49 and No. 13.6 of the Radio Regulations. In both cases, the proposed changes aim at clarification of the text and its alignment with the definition of bringing into use being proposed in Document IWG-4/110rev3 through the introduction of a new No. 11.44J. No. 11.49 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.49 Where Whenever the use of a recorded assignment to a space station is suspended for a period not exceeding eighteen months, the notifying administration
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-11-712A2_Rcd.pdf
  • highlighted in the text below are proposed changes to the NTIA proposals contained in Document IWG-4/093 addressing No. 11.49 and No. 13.6 of the Radio Regulations. In both cases, the proposed changes aim at clarification of the text and its alignment with the definition of bringing into use being proposed in Document IWG-4/110rev3 through the introduction of a new No. 11.44J. No.11.49 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.49 WhereWheneverthe use of a recorded assignment to a space station is suspended for a period not exceeding eighteen months, the notifying administration shall, as soon
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-215526A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-215526A1.txt
  • Islands - GTMC) 24/ 2.53 7.49 15.49 21.17 34.45 29.24 1.87 GTE New York (New York Contel) 25/ 9.90 8.60 12.10 GSTC - North (East North Contel) 25/ 10.36 10.15 15.51 Sprint 43 Central Telephone of Nevada 26/ 12.44 14.23 18.90 20.46 20.42 17.07 17.79 21.15 19.29 44 Sprint - Florida 20.05 26.14 27.17 27.38 Central Telephone of Florida 26/ 11.44 14.66 15.93 17.16 17.85 United Telephone Co. of Florida 13.00 12.27 14.44 17.63 19.28 19.79 45 Sprint Local Telephone Cos. - Eastern (NJ & PA) 11.71 12.32 13.98 16.12 14.87 17.42 17.36 14.59 20.87 25.62 46 Sprint Local Telephone Cos. - Midwest (MO, KS, MN, NE, WY, TX) 19.97 19.66 17.69 18.88 Central Telephone of Texas 26/ 14.94 16.19 18.39
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-278628A10.pdf
  • nacional, las instalaciones de todos los participantes en el EAS tienen que reservarse exclusivamente para la difusión de los mensajes presidenciales. Primero Los mensajes presidenciales tienen prioridad sobre cualquier otro mensaje Segundo Mensajes del área local Tercero Mensajes estatales Cuarto Mensajes del Centro de Información Nacional (NIC) 7 Transmita los mensajes de emergencia tan pronto como estén disponibles (47 C.F.R. §11.44) 13 Transmita este anuncio Interrumpimos nuestra transmisión a solicitud de la Casa Blanca. Este es el Sistema de Alerta de Emergencia. Todas las transmisiones normales han cesado durante esta emergencia. Este es (nombre del sistema). Este sistema continuará proveyendo noticias, informaciones oficiales e instrucciones para el área de (nombre del área local del EAS). Si usted no se encuentra en
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-278628A11.pdf
  • nacional, las instalaciones de todos los participantes en el EAS tienen que reservarse exclusivamente para la difusión de los mensajes presidenciales. Primero Los mensajes presidenciales tienen prioridad sobre cualquier otro mensaje Segundo Mensajes del área local Tercero Mensajes estatales Cuarto Mensajes del Centro de Información Nacional (NIC) 7 Transmita los mensajes de emergencia tan pronto como estén disponibles (47 C.F.R. §11.44) 12 Transmita este anuncio Interrumpimos nuestra transmisión a solicitud de la Casa Blanca. Este es el Sistema de Alerta de Emergencia. Todas las transmisiones normales han cesado durante esta emergencia. Este es (nombre del proveedor de satélite). Esta red de satélite continuará proveyendo noticias, informaciones oficiales e instrucciones para el área de (nombre del área local del EAS). Los proveedores
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-278628A2.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-278628A2.txt
  • priorities for EAS messages are: During a national emergency, the facilities of all EAS participants must be reserved exclusively for distribution of Presidential Messages. First Presidential messages take priority over any other message Second Local Area messages Third State messages Fourth National Information Center (NIC) messages 7 Transmit emergency messages as soon as they are available (Participating Systems) (47 C.F.R. §11.44) 14 Broadcast this Announcement We interrupt our programming at the request of the White House. This is the Emergency Alert System. All normal programming has been discontinued during this emergency. This is (cable system name). This cable system will continue furnishing news, official information and instructions for the (EAS Local Area name) area. If you are not in (EAS Local
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-278628A3.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-278628A3.txt
  • priorities for EAS messages are: During a national emergency, the facilities of all EAS participants must be reserved exclusively for distribution of Presidential Messages. First Presidential messages take priority over any other message Second Local Area messages Third State messages Fourth National Information Center (NIC) messages 7 Transmit emergency messages as soon as they are available (Participating Stations) (47 C.F.R. §11.44) 13 Broadcast this Announcement We interrupt our programming at the request of the White House. This is the Emergency Alert System. All normal programming has been discontinued during this emergency. This is (station call name). This station will continue furnishing news, official information and instructions for the (EAS Local Area name) area. If you are not in (EAS Local Area
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-278628A4.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-278628A4.txt
  • 11 The priorities for EAS messages are: During a national emergency, the facilities of all EAS participants must be reserved exclusively for distribution of Presidential Messages. First Presidential messages take priority over any other message Second Local Area messages Third State messages Fourth National Information Center (NIC) messages 7 Transmit emergency messages as soon as they are available (47 C.F.R. §11.44) 12 Broadcast this Announcement We interrupt our programming at the request of the White House. This is the Emergency Alert System. All normal programming has been discontinued during this emergency. This is (satellite provider name). This satellite network will continue furnishing news, official information and instructions for the (EAS Local Area name) area. Providers may opt to tune to a
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-278628A5.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-278628A5.txt
  • 12 The priorities for EAS messages are: During a national emergency, the facilities of all EAS participants must be reserved exclusively for distribution of Presidential Messages. First Presidential messages take priority over any other message Second Local Area messages Third State messages Fourth National Information Center (NIC) messages 7 Transmit emergency messages as soon as they are available (47 C.F.R. §11.44) (Participating Stations) 13 Broadcast this Announcement We interrupt our programming at the request of the White House. This is the Emergency Alert System. All normal programming has been discontinued during this emergency. This is (station call name). This station will continue furnishing news, official information and instructions for the (EAS Local Area name) area. If you are not in (EAS
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-278628A6.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-278628A6.txt
  • 12 The priorities for EAS messages are: During a national emergency, the facilities of all EAS participants must be reserved exclusively for distribution of Presidential Messages. First Presidential messages take priority over any other message Second Local Area messages Third State messages Fourth National Information Center (NIC) messages 7 Transmit emergency messages as soon as they are available (47 C.F.R. §11.44) 13 Broadcast this Announcement We interrupt our programming at the request of the White House. This is the Emergency Alert System. All normal programming has been discontinued during this emergency. This is [system name]. This system will continue furnishing news, official information and instructions for the (EAS Local Area name) area. If you are not in [EAS Local Area name]
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-278628A7.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-278628A7.txt
  • nacional, las instalaciones de todos los participantes en el EAS tienen que reservarse exclusivamente para la difusión de los mensajes presidenciales. Primero Los mensajes presidenciales tienen prioridad sobre cualquier otro mensaje Segundo Mensajes del área local Tercero Mensajes estatales Cuarto Mensajes del Centro de Información Nacional (NIC) 7 Transmita los mensajes de emergencia tan pronto como estén disponibles (47 C.F.R. §11.44) (Estaciones participantes) 13 Transmita este anuncio Interrumpimos nuestra transmisión a solicitud de la Casa Blanca. Este es el Sistema de Alerta de Emergencia. Todas las transmisiones normales han cesado durante esta emergencia. Esta es (nombre identificación de la estación). Esta estación continuará proveyendo noticias, informaciones oficiales e instrucciones para el área de (nombre del área local del EAS). Si usted
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-278628A8.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-278628A8.txt
  • nacional, las instalaciones de todos los participantes en el EAS tienen que reservarse exclusivamente para la difusión de los mensajes presidenciales. Primero Los mensajes presidenciales tienen prioridad sobre cualquier otro mensaje Segundo Mensajes del área local Tercero Mensajes estatales Cuarto Mensajes del Centro de Información Nacional (NIC) 7 Transmita los mensajes de emergencia tan pronto como estén disponibles (47 C.F.R. §11.44) (Estaciones participantes) 13 Transmita este anuncio Interrumpimos nuestra transmisión a solicitud de la Casa Blanca. Este es el Sistema de Alerta de Emergencia. Todas las transmisiones normales han cesado durante esta emergencia. Esta es (nombre identificación de la estación). Esta estación continuará proveyendo noticias, informaciones oficiales e instrucciones para el área de (nombre del área local del EAS). Si usted
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-278628A9.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-278628A9.txt
  • nacional, las instalaciones de todos los participantes en el EAS tienen que reservarse exclusivamente para la difusión de los mensajes presidenciales. Primero Los mensajes presidenciales tienen prioridad sobre cualquier otro mensaje Segundo Mensajes del área local Tercero Mensajes estatales Cuarto Mensajes del Centro de Información Nacional (NIC) 7 Transmita los mensajes de emergencia tan pronto como estén disponibles (47 C.F.R. §11.44) (Sistemas participantes) 14 Transmita este anuncio Interrumpimos nuestra transmisión a solicitud de la Casa Blanca. Este es el Sistema de Alerta de Emergencia. Todas las transmisiones normales han cesado durante esta emergencia. Esta es (nombre del sistema de cable). Este sistema de cable continuará proveyendo noticias, informaciones oficiales e instrucciones para el área de (nombre del área local del EAS).
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-279226A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-279226A1.txt
  • 3.66 -1.24 441163 C VALOR TELECOMM OF TX, LP-TX#1 DBA WINDSTREAM -4.34 -0.74 -3.62 -83.87 442038 A BLOSSOM TELEPHONE COMPANY -0.08 -3.96 4.04 4.85 442039 C BIG BEND TELEPHONE COMPANY INC. 16.15 -2.86 19.57 19.90 442040 C BRAZORIA TEL. CO. 4.08 -4.53 9.02 9.27 442041 C BRAZOS TELEPHONE COOPERATIVE INC. -2.48 -2.06 -0.43 -11.23 442043 A NORTH TEXAS TELEPHONE COMPANY 11.44 -3.91 15.97 45.82 442046 C CAP ROCK TELEPHONE COOPERATIVE, INC. 11.69 -0.72 12.50 31.75 442052 C CENTRAL TEXAS TELEPHONE CO-OP. INC. 0.25 -2.58 2.90 0.04 442057 C COLEMAN COUNTY TELEPHONE CO-OP. INC. 14.76 -8.92 26.00 28.18 442059 C COLORADO VALLEY TELEPHONE CO-OP. INC. -1.44 -2.03 0.60 -3.85 442060 C COMANCHE COUNTY TEL COMPANY INC. -6.14 -4.45 -1.77 -21.78 442061 C
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-279226A5.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-279226A5.txt
  • 3.66 -1.24 441163 C VALOR TELECOMM OF TX, LP-TX#1 DBA WINDSTREAM -4.34 -0.74 -3.62 -83.87 442038 A BLOSSOM TELEPHONE COMPANY -0.08 -3.96 4.04 4.85 442039 C BIG BEND TELEPHONE COMPANY INC. 16.15 -2.86 19.57 19.90 442040 C BRAZORIA TEL. CO. 4.08 -4.53 9.02 9.27 442041 C BRAZOS TELEPHONE COOPERATIVE INC. -2.48 -2.06 -0.43 -11.23 442043 A NORTH TEXAS TELEPHONE COMPANY 11.44 -3.91 15.97 45.82 442046 C CAP ROCK TELEPHONE COOPERATIVE, INC. 11.69 -0.72 12.50 31.75 442052 C CENTRAL TEXAS TELEPHONE CO-OP. INC. 0.25 -2.58 2.90 0.04 442057 C COLEMAN COUNTY TELEPHONE CO-OP. INC. 14.76 -8.92 26.00 28.18 442059 C COLORADO VALLEY TELEPHONE CO-OP. INC. -1.44 -2.03 0.60 -3.85 442060 C COMANCHE COUNTY TEL COMPANY INC. -6.14 -4.45 -1.77 -21.78 442061 C
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-287688A1.pdf
  • 310726 C SHIAWASSEE TEL. CO. -5.05 -3.51 -1.59 -19.21 310728 C SPRINGPORT TEL. CO. -8.92 -4.83 -4.30 -18.01 310732 C UPPER PENINSULA TEL. CO. -9.04 -4.80 -4.45 -14.94 310734 C WALDRON TEL. CO. -9.95 -2.12 -8.01 -19.62 310735 A WESTPHALIA TEL. CO. 3.16 1.90 1.24 -9.60 310737 C WINN TEL. CO. 3.86 -3.61 7.76 9.31 310738 C WOLVERINE TEL. CO. -11.44 -4.05 -7.70 -100.00 313033 C VERIZON NORTH INC.-MI (ALLTEL) -0.24 -5.10 5.12 0.00 315090 C MICHIGAN BELL TEL. CO. -0.09 -8.68 9.40 0.00 TOTAL MINNESOTA -8.54 -5.49 -3.23 1.53 361123 C CITIZENS TEL CO OF MN, LLC DBA FRONTIER MN -7.68 -2.83 -4.99 0.00 361337 A>CWINNEBAGO COOP. TEL. ASSN.-MN 36.83 -3.12 41.23 85.77 361346 C ACE TEL. ASSN.-MN 25.82 -2.93
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-287688A5.pdf
  • 310726 C SHIAWASSEE TEL. CO. -5.05 -3.51 -1.59 -19.21 310728 C SPRINGPORT TEL. CO. -8.92 -4.83 -4.30 -18.01 310732 C UPPER PENINSULA TEL. CO. -9.04 -4.80 -4.45 -14.94 310734 C WALDRON TEL. CO. -9.95 -2.12 -8.01 -19.62 310735 A WESTPHALIA TEL. CO. 3.16 1.90 1.24 -9.60 310737 C WINN TEL. CO. 3.86 -3.61 7.76 9.31 310738 C WOLVERINE TEL. CO. -11.44 -4.05 -7.70 -100.00 313033 C VERIZON NORTH INC.-MI (ALLTEL) -0.24 -5.10 5.12 0.00 315090 C MICHIGAN BELL TEL. CO. -0.09 -8.68 9.40 0.00 TOTAL MINNESOTA -8.54 -5.49 -3.23 1.53 361123 C CITIZENS TEL CO OF MN, LLC DBA FRONTIER MN -7.68 -2.83 -4.99 0.00 361337 A>CWINNEBAGO COOP. TEL. ASSN.-MN 36.83 -3.12 41.23 85.77 361346 C ACE TEL. ASSN.-MN 25.82 -2.93
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-295442A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-295442A1.txt
  • 260415 C PEOPLES RURAL TEL. COOP. CORP. 9.87 -1.94 12.05 18.50 260417 A SALEM TEL. CO. 6.03 -2.75 9.03 INFINITE 260418 C SOUTH CENTRAL RURAL TEL. COOP. CORP., INC. -0.96 -0.74 -0.22 -9.59 260419 A THACKER/GRIGSBY TEL. CO., INC. 1.08 -3.67 4.93 -5.91 260421 C WEST KY. RURAL TEL. COOP. CORP., INC. 4.03 -5.07 9.59 8.66 265061 C CINCINNATI BELL-KY -11.44 -12.57 1.28 0.00 265182 C SOUTH CENTRAL BELL-KY -10.09 -9.11 -1.08 -100.00 269690 C WINDSTREAM KENTUCKY EAST, INC.-LEXINGTON -7.42 -5.49 -2.04 0.00 269691 C WINDSTREAM KENTUCKY EAST, INC.-LONDON -4.93 -4.08 -0.88 0.00 LOUISIANA TOTAL -8.38 -5.36 -3.19 -8.19 270423 C CENTURYTEL OF CENTRAL LA, LLC -5.28 -5.93 0.68 -11.95 270424 C CENTURYTEL OF SOUTHEAST LOUISIANA, LLC -9.82 -11.89 2.35 -16.52
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-295442A5.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-295442A5.txt
  • 260415 C PEOPLES RURAL TEL. COOP. CORP. 9.87 -1.94 12.05 18.50 260417 A SALEM TEL. CO. 6.03 -2.75 9.03 INFINITE 260418 C SOUTH CENTRAL RURAL TEL. COOP. CORP., INC. -0.96 -0.74 -0.22 -9.59 260419 A THACKER/GRIGSBY TEL. CO., INC. 1.08 -3.67 4.93 -5.91 260421 C WEST KY. RURAL TEL. COOP. CORP., INC. 4.03 -5.07 9.59 8.66 265061 C CINCINNATI BELL-KY -11.44 -12.57 1.28 0.00 265182 C SOUTH CENTRAL BELL-KY -10.09 -9.11 -1.08 -100.00 269690 C WINDSTREAM KENTUCKY EAST, INC.-LEXINGTON -7.42 -5.49 -2.04 0.00 269691 C WINDSTREAM KENTUCKY EAST, INC.-LONDON -4.93 -4.08 -0.88 0.00 LOUISIANA TOTAL -8.38 -5.36 -3.19 -8.19 270423 C CENTURYTEL OF CENTRAL LA, LLC -5.28 -5.93 0.68 -11.95 270424 C CENTURYTEL OF SOUTHEAST LOUISIANA, LLC -9.82 -11.89 2.35 -16.52
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-303886A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-303886A1.txt
  • -4.46 -9.39 5.44 0.00 150122 C FRONTIER-SENECA GORH -10.84 -7.19 -3.93 0.00 150125 A STATE TEL CO -8.79 -5.15 -3.85 0.00 150128 C FRONTIER-SYLVAN LAKE -11.41 -14.22 3.27 -100.00 150129 C TOWNSHIP TEL CO 2.12 -9.13 12.37 16.98 150131 C TRUMANSBURG TEL CO. -0.50 -9.81 10.31 6.89 150133 C VERNON TEL CO 0.41 -9.98 11.55 0.00 150135 C WARWICK VALLEY-NY -11.44 -9.95 -1.65 0.00 154532 C CITIZENS-FRONTIER-NY -5.20 -6.60 1.49 0.00 154533 C CITIZENS-FRONTIER-NY -3.97 -6.94 3.19 0.00 154534 C CITIZENS-FRONTIER-NY -4.12 -6.41 2.45 0.00 155130 C VERIZON NEW YORK 5.94 -11.45 19.64 0.00 TOTAL NORTH CAROLINA -4.38 -8.78 4.82 3.28 230468 C ATLANTIC MEMBERSHIP -6.90 -3.02 -4.01 0.00 230469 C BARNARDSVILLE TEL CO -5.70 -8.04 2.54 -17.30 230470 C CAROLINA
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-303886A5.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-303886A5.txt
  • -4.46 -9.39 5.44 0.00 150122 C FRONTIER-SENECA GORH -10.84 -7.19 -3.93 0.00 150125 A STATE TEL CO -8.79 -5.15 -3.85 0.00 150128 C FRONTIER-SYLVAN LAKE -11.41 -14.22 3.27 -100.00 150129 C TOWNSHIP TEL CO 2.12 -9.13 12.37 16.98 150131 C TRUMANSBURG TEL CO. -0.50 -9.81 10.31 6.89 150133 C VERNON TEL CO 0.41 -9.98 11.55 0.00 150135 C WARWICK VALLEY-NY -11.44 -9.95 -1.65 0.00 154532 C CITIZENS-FRONTIER-NY -5.20 -6.60 1.49 0.00 154533 C CITIZENS-FRONTIER-NY -3.97 -6.94 3.19 0.00 154534 C CITIZENS-FRONTIER-NY -4.12 -6.41 2.45 0.00 155130 C VERIZON NEW YORK 5.94 -11.45 19.64 0.00 TOTAL NORTH CAROLINA -4.38 -8.78 4.82 3.28 230468 C ATLANTIC MEMBERSHIP -6.90 -3.02 -4.01 0.00 230469 C BARNARDSVILLE TEL CO -5.70 -8.04 2.54 -17.30 230470 C CAROLINA
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-01-134A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-01-134A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-01-134A1.txt
  • Rules for the Mobile Satellite Service in the 2 GHz Band, 15 FCC Rcd 16127 (2000) (2 GHz Report and Order) at ¶ 106. The critical design review is the stage in the space station implementation process at which the design and development phase ends, and the manufacturing phase begins. See 47 C.F.R. §§ 25.161, 25.163. See ITU RR Art. S11.44. We plan to undertake an investigation of milestones issues by the end of this year, in a separate, broader proceeding not limited to this NGSO FSS service. See generally Streamlining the Commission's Rules and Regulations for Satellite Applications and Licensing Procedures, Report and Order, 11 FCC Rcd 21581 (1996) (Part 25 Streamlining Order). See 47 C.F.R. § 25.210(l) (1) and
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-02-123A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-02-123A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-02-123A1.txt
  • terms will apply to all space station and earth station licenses granted after the effective date of the rule change, April 18, 2002. 67 Fed. Reg. 12485 (March 19, 2002). The critical design review is the stage in the space station implementation process at which the design and development phase ends, and the manufacturing phase begins. See ITU RR Art. S11.44. Generally, ITU Radio Regulations require that the satellite be "brought-into-use" (BIU) no later than five years from the date the ITU publishes the advance publication information. ITU Radio Regulations Article S11.44. The ITU may extend the BIU date by two years under the conditions specified in ITU Radio Regulations Articles S11.44B through S11.44I (launch failure; launch delays due to circumstances
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-02-331A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-02-331A1.txt
  • + Port Combinations/>=10 circuits/Dispatch/FL (days) 10.00 5.06 11.41 4.20 10.61 5.36 11.32 3.37 11.16 3.33 1,4,5 B.2.1.3.2.2Loop + Port Combinations/>=10 circuits/Non-Dispatch/FL (days) 3.38 0.44 7.04 7.00 3.10 4.11 2.67 6.50 3.89 1,2,3,4 B.2.1.3.2.4Loop + Port Combinations/>=10 circuits/Dispatch In/FL (days) 4.98 1.00 8.77 7.00 3.81 6.00 4.27 6.50 5.95 1,2,3,4 B.2.1.4.1.1Combo Other/<10 circuits/Dispatch/FL (days) 4.72 11.97 5.79 11.57 6.31 12.09 5.38 11.44 5.92 12.21 B.2.1.6.3.1UNE ISDN/<6 circuits/Dispatch/FL (days) 11.88 10.70 13.80 10.02 14.88 9.92 13.64 10.69 13.15 10.62 B.2.1.6.4.1UNE ISDN/6-13 circuits/Dispatch/FL (days) 12.00 12.00 11.00 3 B.2.1.7.3.1Line Sharing/<6 circuits/Dispatch/FL (days) 3.77 6.30 2.80 4.87 2.75 6.69 2.58 3.45 2.73 3.54 B.2.1.7.3.2Line Sharing/<6 circuits/Non- Dispatch/FL (days) 3.49 3.81 2.32 3.77 2.33 3.65 2.20 2.16 2.38 2.20 B.2.1.8.1.12W Analog Loop Design/<10 circuits/Dispatch/FL (days) 4.03
• 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
  • 11.51(k)(1) of this part, must transmit the header codes, Attention Signal, sign-off announcement and EOM code after receiving the appropriate EAS header codes for a national emergency. (3) After completing the above transmission procedures, key EAS and Participating National sources must transmit a common emergency message until receipt of the Emergency Action Termination Message. Message priorities are specified in § 11.44 of this part. If LP or SR sources of a Local Area cannot provide an emergency message feed, any source in the Local Area may elect to provide a message feed. This should be done in an organized manner as designated in State and Local Area EAS Plans. (4) The Standby Script shall be used until emergency messages are available.
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-03-137A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-03-137A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-03-137A1.txt
  • 03-102. Id. at ¶ 164. Id. at ¶ 167-172. Id. at ¶ 168. The amount of this bond is subject to detailed consideration in a further notice of proposed rulemaking. The critical design review is the stage in the space station implementation process at which the design and development phase ends, and the manufacturing phase begins. See ITU RR Art. S11.44. Generally, ITU Radio Regulations require that the satellite be "brought-into-use" (BIU) no later than five years from the date the ITU publishes the advance publication information. ITU Radio Regulations Article S11.44. The ITU may extend the BIU date by two years under the conditions specified in ITU Radio Regulations Articles S11.44B through S11.44I (launch failure; launch delays due to circumstances
• 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
  • and Further Notice of Proposed Rulemaking, 7 FCC Rcd 6903 (1992); Amendment of Part 73, Subpart G, of the Commission's Rules Regarding the Emergency Broadcast System, Notice of Inquiry and Notice of Proposed Rulemaking, 6 FCC Rcd 6739 (1991); Inquiry into Possible Technical Improvements in the Emergency Broadcasting System, Notice of Inquiry, 6 FCC Rcd 4264 (1991). 47 C.F.R. § 11.44. 47 C.F.R. § 11.1. See, e.g., NOAA News Release, Homeland Security Uses NOAA All-Hazards Network For Alerts And Warnings (June 17, 2004); CEA News Release, CEA Welcomes DHS and NOAA Public Alert Memorandum of Agreement (June 17, 2004); see also Pennsylvania Emergency Alert System State EAS Plan (2004). Providing for Emergency Control Over Certain Government and Non-Government Stations Engaged in
• 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
  • which have facilities in place may, without charge, connect an originating source from the nearest exchange to a selected Test Center and then to any EAS Participant. Independent stations will not be connected during the test unless authorized by the FCC. Upon test termination, EAS Participants shall be restored to their original configurations. * * * * * Amend § 11.44 by revising paragraph (d) to read as follows: § 11.44 EAS message priorities. * * * * * (d) During a national emergency, the facilities of all EAS Participants must be reserved exclusively for distribution of Presidential Messages. NIC messages received from national networks which are not broadcast at the time of original transmission must be recorded locally by LP
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-05-191A1_Erratum.doc
  • which have facilities in place may, without charge, connect an originating source from the nearest exchange to a selected Test Center and then to any EAS Participant. Independent stations will not be connected during the test unless authorized by the FCC. Upon test termination, EAS Participants shall be restored to their original configurations. * * * * * Amend § 11.44 by revising paragraph (d) to read as follows: § 11.44 EAS message priorities. * * * * * (d) During a national emergency, the facilities of all EAS Participants must be reserved exclusively for distribution of Presidential Messages. NIC messages received from national networks which are not broadcast at the time of original transmission must be recorded locally by LP
• 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
  • Commission's EAS rules are intended to ensure that national activation of EAS would enable the President to communicate with the American public within ten minutes from any location at any time. These messages must take priority over any other messages and preempt other messages in progress. First Report and Order, 20 FCC Rcd at 18628, ¶ 8; 47 C.F.R. § 11.44(a). (August 30, 2006). (March 6, 2007). The seven NWR frequencies (MHz) are: 162.400, 162.425, 162.450, 162.475, 162.500, 162.525, and 162.550. Id. The digital protocol is known as Specific Area Message Encoding (SAME). See The Emergency Alert System (EAS): An Assessment, Partnership for Public Warning Report 2004-1, at 18. See id. at 7. In some localities, emergency managers can originate EAS
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-07-33A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-07-33A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-07-33A1.txt
  • may be made jointly for both stations for periods of such simultaneous operations. See 47 C.F.R. § 73.1201(c)(2). PIC Comments at 36-37. PIC Reply Comments at 16. iBiquity Comments at 26. SBAs Comments at 16. See Second Periodic Review of the Commission's Rules and Policies Affecting the Conversion to Digital Television, 19 FCC Rcd 18279, 18354 (2004). 47 C.F.R. §§ 11.44, 11.54. 47 C.F.R. §§ 11.1, 11.55. See 47 C.F.R. § 73.1250. Emergency situations in which the broadcasting of information is considered as furthering the safety of life and property include, but are not limited to the following: tornadoes, hurricanes, floods, tidal waves, earthquakes, icing conditions, heavy snows, widespread fires, discharge of toxic gasses, widespread power failures, industrial explosions, civil disorders
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-07-76A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-07-76A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-07-76A1.txt
  • the Radio Regulations require ITU member nations to bring their proposed satellite systems into use within seven years of the date the nation informs the ITU of its intent to construct and operate the satellite system. Failure to meet the bringing-into-use date causes the member nation to lose its priority relative to other member nations' proposed satellite systems. See No. 11.44 of the ITU Radio Regulations. Thus, an efficient licensing method that does not require further proceedings will facilitate each licensee's ability to obtain date priority at the ITU. EchoStar Comments at 17. See First Space Station Licensing Reform Order, 18 FCC Rcd at 10800-04, paras. 99-107. Intelsat Comments at 3, n. 7. EchoStar Comments at 18. DIRECTV Reply Comments at
• 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
  • 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, 3.
• 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
  • public within ten minutes from any location at any time. These messages must take priority over any other messages and preempt other messages in progress. Review of the Emergency Alert System, EB Docket No. 04-296, First Report and Order and Further Notice of Proposed Rulemaking, 20 FCC Rcd 18625, 18628, ¶ 8 (2005) (First Report and Order); 47 C.F.R. § 11.44(a). A more detailed overview of the history of EAS is set out in the first Notice of Proposed Rulemaking in this docket. See Review of the Emergency Alert System, EB Docket No. 04-296, Notice of Proposed Rulemaking, 19 FCC Rcd 15775, 15776-77, ¶¶ 6-8 (2004 NPRM). FEMA acts as Executive Agent for the development, operation, and maintenance of the national-level
• 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
  • public within ten minutes from any location at any time. These messages must take priority over any other messages and preempt other messages in progress. Review of the Emergency Alert System, EB Docket No. 04-296, First Report and Order and Further Notice of Proposed Rulemaking, 20 FCC Rcd 18625, 18628, ¶ 8 (2005) (First Report and Order); 47 C.F.R. § 11.44(a). A more detailed overview of the history of EAS is set out in the first Notice of Proposed Rulemaking in this docket. See Review of the Emergency Alert System, EB Docket No. 04-296, Notice of Proposed Rulemaking, 19 FCC Rcd 15775, 15776-77, ¶¶ 6-8 (2004 NPRM). FEMA acts as Executive Agent for the development, operation, and maintenance of the national-level
• 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 related Part 11 rule sections so that EAS Participants process EANs like any other EAS message, only on a mandatory and priority basis. We also seek comment on whether the Commission should: eliminate the Emergency Action Termination event code and replace it where necessary with the End Of Message code in the Part 11 rules; delete sections 11.16, 11.42, 11.44, and 11.54(a), (b)(1)-(8), (10), (12), and 11.54(c) of the rules; and eliminate the EAS Operating Handbook 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
• 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
  • terminated. This process is described in section 11.54, which specifies the actions an EAS Participant must take upon receiving an EAN. Under these provisions, the EAN commences a ``National Level emergency'' condition, during which EAS Participants must discontinue regular programming, make certain announcements set forth in the EAS Operating Handbook, and broadcast a ``common emergency message,'' as prioritized under section 11.44. EAS Participants are required to follow this process until receipt of the EAT. In the Third FNPRM, we sought comment on whether the procedures set forth in section 11.54 for processing EATs and EANs are problematic and technically impractical for automated operation. We explained that the framework for manually processing EANs described in section 11.54 was derived from the former
• http://transition.fcc.gov/eb/Orders/2002/FCC-02-64A1.html
  • under 11.51(k)(1) of this part, must transmit the header codes, Attention Signal, sign-off announcement and EOM code after receiving the appropriate EAS header codes for a national emergency. (3) After completing the above transmission procedures, key EAS and Participating National sources must transmit a common emergency message until receipt of the Emergency Action Termination Message. Message priorities are specified in 11.44 of this part. If LP or SR sources of a Local Area cannot provide an emergency message feed, any source in the Local Area may elect to provide a message feed. This should be done in an organized manner as designated in State and Local Area EAS Plans. (4) The Standby Script shall be used until emergency messages are available.
• http://transition.fcc.gov/eb/Orders/2004/FCC-04-189A1.html
  • and Further Notice of Proposed Rulemaking, 7 FCC Rcd 6903 (1992); Amendment of Part 73, Subpart G, of the Commission's Rules Regarding the Emergency Broadcast System, Notice of Inquiry and Notice of Proposed Rulemaking, 6 FCC Rcd 6739 (1991); Inquiry into Possible Technical Improvements in the Emergency Broadcasting System, Notice of Inquiry, 6 FCC Rcd 4264 (1991). 2 47 C.F.R. 11.44. 3 47 C.F.R. 11.1. 4 See, e.g., NOAA News Release, Homeland Security Uses NOAA All- Hazards Network For Alerts And Warnings (June 17, 2004); CEA News Release, CEA Welcomes DHS and NOAA Public Alert Memorandum of Agreement (June 17, 2004); see also Pennsylvania Emergency Alert System State EAS Plan (2004). 5 Providing for Emergency Control Over Certain Government and Non-Government
• http://transition.fcc.gov/eb/Orders/2005/FCC-05-191A1.html
  • which have facilities in place may, without charge, connect an originating source from the nearest exchange to a selected Test Center and then to any EAS Participant. Independent stations will not be connected during the test unless authorized by the FCC. Upon test termination, EAS Participants shall be restored to their original configurations. * * * * * 14. Amend 11.44 by revising paragraph (d) to read as follows: 11.44 EAS message priorities. * * * * * (d) During a national emergency, the facilities of all EAS Participants must be reserved exclusively for distribution of Presidential Messages. NIC messages received from national networks which are not broadcast at the time of original transmission must be recorded locally by LP sources
• http://www.fcc.gov/Bureaus/Common_Carrier/Orders/2002/fcc02331.pdf
  • + Port Combinations/>=10 circuits/Dispatch/FL (days) 10.00 5.06 11.41 4.20 10.61 5.36 11.32 3.37 11.16 3.33 1,4,5 B.2.1.3.2.2Loop + Port Combinations/>=10 circuits/Non-Dispatch/FL (days) 3.38 0.44 7.04 7.00 3.10 4.11 2.67 6.50 3.89 1,2,3,4 B.2.1.3.2.4Loop + Port Combinations/>=10 circuits/Dispatch In/FL (days) 4.98 1.00 8.77 7.00 3.81 6.00 4.27 6.50 5.95 1,2,3,4 B.2.1.4.1.1Combo Other/<10 circuits/Dispatch/FL (days) 4.72 11.97 5.79 11.57 6.31 12.09 5.38 11.44 5.92 12.21 B.2.1.6.3.1UNE ISDN/<6 circuits/Dispatch/FL (days) 11.88 10.70 13.80 10.02 14.88 9.92 13.64 10.69 13.15 10.62 B.2.1.6.4.1UNE ISDN/6-13 circuits/Dispatch/FL (days) 12.00 12.00 11.00 3 B.2.1.7.3.1Line Sharing/<6 circuits/Dispatch/FL (days) 3.77 6.30 2.80 4.87 2.75 6.69 2.58 3.45 2.73 3.54 B.2.1.7.3.2Line Sharing/<6 circuits/Non- Dispatch/FL (days) 3.49 3.81 2.32 3.77 2.33 3.65 2.20 2.16 2.38 2.20 B.2.1.8.1.12W Analog Loop Design/<10 circuits/Dispatch/FL (days) 4.03
• http://www.fcc.gov/Bureaus/Common_Carrier/Reports/FCC-State_Link/IAD/ror00.pdf
  • Rate of Return Summary January 1, 1999 - December 31, 2000 Summary of Reports Filed September 30, 2001 Switched Traffic Sensitive Common Special End Local Name of Company Interstate Line Access Office Information Transport Total National Exchange Carrier Association 11.81% 11.44% 11.48% - - - 12.34% 1ACS of Anchorage 17.09 11.35 12.94 27.10 91.77 37.05 30.26 2ALLTEL Alabama, Inc. 10.68 11.44 45.10 4.76 10.43 6.09 3ALLTEL Arkansas, Inc. 10.30 11.44 13.34 5.56 6.08 5.94 4ALLTEL Carolina, Inc. 10.56 11.44 8.32 9.05 8.95 8.89 5ALLTEL Florida, Inc. 11.17 11.44 11.66 10.53 8.90 9.64 6ALLTEL Georgia Properties 12.38 14.15 8.66 9.82 7.82 8.86 7ALLTEL Kentucky, Inc. 10.93 11.44 9.87 11.08 6.81 10.18 8ALLTEL Mississippi, Inc. 10.56 11.44 21.09 5.69 10.43 6.78 9ALLTEL Missouri,
• http://www.fcc.gov/Bureaus/Common_Carrier/Reports/FCC-State_Link/IAD/ror96.pdf
  • OF THE SOUTH-NC 8.87 12.44 2.27 7.87 14.88 8.19 8.00 92GENERAL TELEPHONE CO. OF THE SOUTH-SC 10.04 12.44 4.42 7.50 69.12 11.82 8.33 93GENERAL TELEPHONE CO. OF THE SOUTH-TN 13.87 12.45 7.74 15.43 (57.26) 21.71 17.48 94GENERAL TELEPHONE CO. OF THE SOUTH-VA 17.20 12.45 44.47 11.34 (259.63) 30.31 17.64 95GENERAL TELEPHONE CO. OF THE SOUTH-WV 11.23 12.45 6.18 10.68 (39.75) 11.44 10.90 96GREAT PLAINS COMMUNICATIONS, INC. 12.01 11.68 10.04 - - - 13.21 97GRIDLEY TELEPHONE COMPANY 16.05 12.37 17.42 21.85 - 13.70 19.95 98GTE MTO INC. - ILLINOIS 11.80 12.45 18.82 12.43 (41.08) 5.58 10.16 99GTE MTO INC. - INDIANA 13.11 12.45 23.11 9.62 (41.10) 15.69 11.39 100GTE MTO INC. - IOWA 14.32 12.45 8.99 17.54 (71.93) 20.91 18.47 101GTE MTO
• http://www.fcc.gov/Bureaus/Common_Carrier/Reports/FCC-State_Link/IAD/ror97.pdf
  • ONLY - COWZ) 17/ 14.86 GTE WEST (WEST CONTEL) 17/ 17.26 13.81 10.51 54 MICRONESIAN TELECOMMUNICATIONS CORP. 18/ 20.06 15.49 7.49 2.53 GTE NEW YORK (NEW YORK CONTEL) 19/ 12.10 8.60 9.90 GSTC - NORTH (EAST NORTH CONTEL) 19/ 15.51 10.15 10.36 SPRINT 55 SPRINT LOCAL TELEPHONE COMPANIES - FLORIDA 20.05 CENTRAL TELEPHONE OF FLORIDA 20/ 17.85 17.16 15.93 14.66 11.44 UNITED TELEPHONE CO. OF FLORIDA 19.79 19.28 17.63 14.44 12.27 13.00 56 CENTRAL TELEPHONE OF ILLINOIS 20/ 18.92 18.40 19.55 18.87 10.18 11.54 57 CENTRAL TELEPHONE OF NEVADA 20/ 17.07 20.42 20.46 18.90 14.23 12.44 58 CENTRAL TELEPHONE OF NORTH CAROLINA 20/ 16.55 15.75 15.36 14.19 11.97 11.29 59 CENTRAL TELEPHONE OF TEXAS 20/ 43.40 21.58 21.81 18.39 16.19 14.94
• http://www.fcc.gov/Bureaus/Common_Carrier/Reports/FCC-State_Link/IAD/ror98.pdf
  • CORP. (N. MARIANA IS. - GTMC)17/ 33.06 21.17 15.49 7.49 2.53 GTE NEW YORK (NEW YORK CONTEL) 18/ 12.10 8.60 9.90 GSTC - NORTH (EAST NORTH CONTEL) 18/ 15.51 10.15 10.36 SPRINT 56 CENTRAL TELEPHONE OF NEVADA 19/ 17.79 17.07 20.42 20.46 18.90 14.23 12.44 57 SPRINT - FLORIDA 26.14 20.05 CENTRAL TELEPHONE OF FLORIDA 19/ 17.85 17.16 15.93 14.66 11.44 UNITED TELEPHONE CO. OF FLORIDA 19.79 19.28 17.63 14.44 12.27 13.00 58 SPRINT LOCAL TELEPHONE COS. - EASTERN (NJ & PA) 14.59 17.36 17.42 14.87 16.12 13.98 12.32 11.71 59 SPRINT LOCAL TELEPHONE COS. - MIDWEST (MO,KS,MN,NE,WY,TX) 19.63 19.97 CENTRAL TELEPHONE OF TEXAS 19/ 21.58 21.81 18.39 16.19 14.94 UNITED TELEPHONE - MIDWEST (MO,KS,MN,NE,WY,TX) 21.52 19.64 17.44 13.92 15.35 14.57
• http://www.fcc.gov/Bureaus/Common_Carrier/Reports/FCC-State_Link/IAD/ror99.pdf
  • - GTMC) 21/ 28.53 34.45 21.17 15.49 7.49 2.53 GTE New York (New York Contel) 22/ 12.10 8.60 9.90 GSTC - North (East North Contel) 22/ 15.51 10.15 10.36 Sprint 55 Central Telephone of Nevada 23/ 21.40 17.79 17.07 20.42 20.46 18.90 14.23 12.44 56 Sprint - Florida 27.25 26.14 20.05 Central Telephone of Florida 23/ 17.85 17.16 15.93 14.66 11.44 United Telephone Co. of Florida 19.79 19.28 17.63 14.44 12.27 13.00 57 Sprint Local Telephone Cos. - Eastern (NJ & PA) 20.88 14.59 17.36 17.42 14.87 16.12 13.98 12.32 11.71 58 Sprint Local Telephone Cos. - Midwest (MO,KS,MN,NE,WY,TX) 17.83 19.66 19.97 Central Telephone of Texas 23/ 21.58 21.81 18.39 16.19 14.94 United Telephone - Midwest (MO,KS,MN,NE,WY,TX) 21.52 19.64 17.44 13.92
• http://www.fcc.gov/Bureaus/Common_Carrier/Reports/FCC-State_Link/IAD/trend100.pdf
  • (N. Mariana Is. - GTMC) 21/ 33.06 21.17 15.49 7.49 2.53 GTE New York (New York Contel) 22/ 12.10 8.60 9.90 GSTC - North (East North Contel) 22/ 15.51 10.15 10.36 Sprint 56 Central Telephone of Nevada 23/ 17.79 17.07 20.42 20.46 18.90 14.23 12.44 57 Sprint - Florida 26.14 20.05 Central Telephone of Florida 23/ 17.85 17.16 15.93 14.66 11.44 United Telephone Co. of Florida 19.79 19.28 17.63 14.44 12.27 13.00 58 Sprint Local Telephone Cos. - Eastern (NJ & PA) 14.59 17.36 17.42 14.87 16.12 13.98 12.32 11.71 59 Sprint Local Telephone Cos. - Midwest (MO,KS,MN,NE,WY,TX) 19.63 19.97 Central Telephone of Texas 23/ 21.58 21.81 18.39 16.19 14.94 United Telephone - Midwest (MO,KS,MN,NE,WY,TX) 21.52 19.64 17.44 13.92 15.35 14.57
• http://www.fcc.gov/Bureaus/Common_Carrier/Reports/FCC-State_Link/IAD/trend199.pdf
  • ONLY - COWZ) 17/ 14.86 GTE WEST (WEST CONTEL) 17/ 17.26 13.81 10.51 54 MICRONESIAN TELECOMMUNICATIONS CORP. 18/ 20.06 15.49 7.49 2.53 GTE NEW YORK (NEW YORK CONTEL) 19/ 12.10 8.60 9.90 GSTC - NORTH (EAST NORTH CONTEL) 19/ 15.51 10.15 10.36 SPRINT 55 SPRINT LOCAL TELEPHONE COMPANIES - FLORIDA 20.05 CENTRAL TELEPHONE OF FLORIDA 20/ 17.85 17.16 15.93 14.66 11.44 UNITED TELEPHONE CO. OF FLORIDA 19.79 19.28 17.63 14.44 12.27 13.00 56 CENTRAL TELEPHONE OF ILLINOIS 20/ 18.92 18.40 19.55 18.87 10.18 11.54 57 CENTRAL TELEPHONE OF NEVADA 20/ 17.07 20.42 20.46 18.90 14.23 12.44 58 CENTRAL TELEPHONE OF NORTH CAROLINA 20/ 16.55 15.75 15.36 14.19 11.97 11.29 59 CENTRAL TELEPHONE OF TEXAS 20/ 43.40 21.58 21.81 18.39 16.19 14.94
• http://www.fcc.gov/Bureaus/Common_Carrier/Reports/FCC-State_Link/IAD/trend200.pdf
  • - GTMC) 21/ 28.53 34.45 21.17 15.49 7.49 2.53 GTE New York (New York Contel) 22/ 12.10 8.60 9.90 GSTC - North (East North Contel) 22/ 15.51 10.15 10.36 Sprint 55 Central Telephone of Nevada 23/ 21.40 17.79 17.07 20.42 20.46 18.90 14.23 12.44 56 Sprint - Florida 27.25 26.14 20.05 Central Telephone of Florida 23/ 17.85 17.16 15.93 14.66 11.44 United Telephone Co. of Florida 19.79 19.28 17.63 14.44 12.27 13.00 57 Sprint Local Telephone Cos. - Eastern (NJ & PA) 20.88 14.59 17.36 17.42 14.87 16.12 13.98 12.32 11.71 58 Sprint Local Telephone Cos. - Midwest (MO,KS,MN,NE,WY,TX) 17.83 19.66 19.97 Central Telephone of Texas 23/ 21.58 21.81 18.39 16.19 14.94 United Telephone - Midwest (MO,KS,MN,NE,WY,TX) 21.52 19.64 17.44 13.92
• http://www.fcc.gov/Bureaus/Common_Carrier/Reports/FCC-State_Link/IAD/trend298.pdf
  • ONLY - COWZ) 17/ 14.86 GTE WEST (WEST CONTEL) 17/ 17.26 13.81 10.51 54 MICRONESIAN TELECOMMUNICATIONS CORP. 18/ 20.06 15.49 7.49 2.53 GTE NEW YORK (NEW YORK CONTEL) 19/ 12.10 8.60 9.90 GSTC - NORTH (EAST NORTH CONTEL) 19/ 15.51 10.15 10.36 SPRINT 55 SPRINT LOCAL TELEPHONE COMPANIES - FLORIDA 20.05 CENTRAL TELEPHONE OF FLORIDA 20/ 17.85 17.16 15.93 14.66 11.44 UNITED TELEPHONE CO. OF FLORIDA 19.79 19.28 17.63 14.44 12.27 13.00 56 CENTRAL TELEPHONE OF ILLINOIS 20/ 18.92 18.40 19.55 18.87 10.18 11.54 57 CENTRAL TELEPHONE OF NEVADA 20/ 17.07 20.42 20.46 18.90 14.23 12.44 58 CENTRAL TELEPHONE OF NORTH CAROLINA 20/ 16.55 15.75 15.36 14.19 11.97 11.29 59 CENTRAL TELEPHONE OF TEXAS 20/ 43.40 21.58 21.81 18.39 16.19 14.94
• http://www.fcc.gov/Bureaus/Common_Carrier/Reports/FCC-State_Link/IAD/trend299.pdf
  • (N. Mariana Is. - GTMC) 21/ 33.06 21.17 15.49 7.49 2.53 GTE New York (New York Contel) 22/ 12.10 8.60 9.90 GSTC - North (East North Contel) 22/ 15.51 10.15 10.36 Sprint 56 Central Telephone of Nevada 23/ 17.79 17.07 20.42 20.46 18.90 14.23 12.44 57 Sprint - Florida 26.14 20.05 Central Telephone of Florida 23/ 17.85 17.16 15.93 14.66 11.44 United Telephone Co. of Florida 19.79 19.28 17.63 14.44 12.27 13.00 58 Sprint Local Telephone Cos. - Eastern (NJ & PA) 14.59 17.36 17.42 14.87 16.12 13.98 12.32 11.71 59 Sprint Local Telephone Cos. - Midwest (MO,KS,MN,NE,WY,TX) 19.63 19.97 Central Telephone of Texas 23/ 21.58 21.81 18.39 16.19 14.94 United Telephone - Midwest (MO,KS,MN,NE,WY,TX) 21.52 19.64 17.44 13.92 15.35 14.57
• http://www.fcc.gov/Bureaus/Common_Carrier/Reports/FCC-State_Link/IAD/trend801.pdf
  • Islands - GTMC) 24/ 2.53 7.49 15.49 21.17 34.45 29.24 1.87 GTE New York (New York Contel) 25/ 9.90 8.60 12.10 GSTC - North (East North Contel) 25/ 10.36 10.15 15.51 Sprint 43 Central Telephone of Nevada 26/ 12.44 14.23 18.90 20.46 20.42 17.07 17.79 21.15 19.29 44 Sprint - Florida 20.05 26.14 27.17 27.38 Central Telephone of Florida 26/ 11.44 14.66 15.93 17.16 17.85 United Telephone Co. of Florida 13.00 12.27 14.44 17.63 19.28 19.79 45 Sprint Local Telephone Cos. - Eastern (NJ & PA) 11.71 12.32 13.98 16.12 14.87 17.42 17.36 14.59 20.87 25.62 46 Sprint Local Telephone Cos. - Midwest (MO, KS, MN, NE, WY, TX) 19.97 19.66 17.69 18.88 Central Telephone of Texas 26/ 14.94 16.19 18.39
• http://www.fcc.gov/Bureaus/Common_Carrier/Reports/FCC-State_Link/Monitor/mr03-3.pdf
  • TOTAL: NORTHERN MARIANA ISLANDS -20.15 2.53 -22.12 -66.58 653700 C MICRONESIAN TELECOMMUNICATIONS CORPORATION -20.15 2.53 -22.12 -66.58 TOTAL: OHIO 1.31 0.74 0.57 13.01 300585 A ARCADIA TEL. CO. 14.63 1.97 12.42 82.99 300586 A THE ARTHUR MUTUAL TEL. CO. 14.32 1.02 13.17 222.61 300588 A AYERSVILLE TEL. CO. 13.27 -0.16 13.45 158.43 300589 A BASCOM MUTUAL TEL. CO. 19.81 7.52 11.44 69.06 300590 A BENTON RIDGE TEL. CO. 9.14 2.58 6.40 17.04 300591 A BUCKLAND TELEPHONE COMPANY 8.62 -4.12 13.28 80.33 300594 A THE CHAMPAIGN TEL. CO. 9.31 0.58 8.68 0.00 300597 C CHILLICOTHE TEL. CO. 8.04 -0.80 8.92 15.74 300598 C MCCLURE TEL. CO. 46.47 0.39 45.91 97.45 300604 A COLUMBUS GROVE TEL. CO. 12.52 -1.53 14.26 INFINITE 300606 A
• http://www.fcc.gov/Bureaus/Common_Carrier/Reports/FCC-State_Link/Monitor/mr04-3.pdf
  • 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 BLOOMER TEL. CO. 3.18 -4.40 7.93 0.00 330851 A BONDUEL TEL. CO. 11.74 1.76 9.81 0.00 330855 C BRUCE TEL. CO., INC. 0.13 -0.16 0.29 -11.44 330856 A BURLINGTON BRIGHTON & WHEATLAND TEL. 13.30 4.44 8.49 0.00 330857 C CENTURYTEL OF THE MIDWEST-WI/CASCO 6.76 0.80 5.91 15.18 330859 C CENTRAL STATE TEL. CO. 1.62 0.37 1.25 -4.54 330860 C CHEQUAMEGON COMMUNICATIONS COOPERATIVE, INC. -1.53 0.75 -2.26 -21.61 330861 A CHIBARDUN TEL. COOP., INC. 9.95 -0.47 10.48 62.86 330863 A CITIZENS TEL. COOP., INC.-WI 11.19 1.58 9.46
• http://www.fcc.gov/Bureaus/Common_Carrier/Reports/FCC-State_Link/Monitor/mrs01-0.pdf
  • 462202 C ROGGEN TELEPHONE COOPERATIVE CO. -3.57 7.64 -10.41 -9.04 462203 C THE RYE TELEPHONE CO. INC. 18.18 12.12 5.40 20.90 462204 C COLUMBINE ACQ CORP DBA COLUMBINE TELECOM CO 11.19 8.14 2.82 11.83 462206 A STONEHAM COOPERATIVE TEL. CO. -3.62 -1.27 -2.38 -8.95 462207 C STRASBURG TEL. CO. 0.88 9.68 -8.02 -11.38 462208 C CENTURYTEL OF COLORADO, INC. 12.93 11.44 1.34 12.53 462209 C WIGGINS TEL. ASSOC. 13.60 3.88 9.35 41.32 462210 A WILLARD TEL. CO. -5.69 -4.55 -1.20 -8.98 465102 C U S WEST, INC. - CO 4.50 3.78 0.69 -58.05 TOTAL: CONNECTICUT 6.64 10.11 -3.15 0.00 132454 A THE WOODBURY TEL. CO. 21.53 5.51 15.19 0.00 135200 C SOUTHERN NEW ENGLAND TEL. 6.47 10.16 -3.34 0.00 TOTAL: DELAWARE
• http://www.fcc.gov/Bureaus/Common_Carrier/Reports/FCC-State_Link/Monitor/mrs02-0.pdf
  • MAINE (NEW ENGLAND) -6.18 0.92 -7.03 0.00 TOTAL: MARYLAND 2.30 2.39 -0.09 INFINITE 180216 C ARMSTRONG TEL. CO. OF MD 23.04 12.03 9.82 INFINITE 185030 C VERIZON MARYLAND INC. (C & P) 2.24 2.38 -0.13 0.00 TOTAL: MASSACHUSETTS -14.21 -1.21 -13.16 214.18 110036 C GRANBY TEL. & TELE. CO.-MA 19.68 3.20 15.97 198.48 110037 C RICHMOND TEL. CO. 15.96 4.06 11.44 297.23 115112 C VERIZON NEW ENGLAND INC. - MASS. (NEW ENGLAND) -14.26 -1.21 -13.21 0.00 TOTAL: MICHIGAN -5.17 -0.81 -4.40 12.31 310669 A ALLENDALE TEL. CO. 10.05 8.23 1.68 0.00 310671 C CENTURY TEL. MIDWEST, INC. 2.25 2.30 -0.06 6.02 310672 C COMM. CORP. OF MICHIGAN 3.83 4.09 -0.24 13.65 310675 A BARAGA TEL. CO. 11.20 -1.34 12.71 INFINITE 310676
• http://www.fcc.gov/eb/Orders/2002/FCC-02-64A1.html
  • under 11.51(k)(1) of this part, must transmit the header codes, Attention Signal, sign-off announcement and EOM code after receiving the appropriate EAS header codes for a national emergency. (3) After completing the above transmission procedures, key EAS and Participating National sources must transmit a common emergency message until receipt of the Emergency Action Termination Message. Message priorities are specified in 11.44 of this part. If LP or SR sources of a Local Area cannot provide an emergency message feed, any source in the Local Area may elect to provide a message feed. This should be done in an organized manner as designated in State and Local Area EAS Plans. (4) The Standby Script shall be used until emergency messages are available.
• http://www.fcc.gov/eb/Orders/2004/FCC-04-189A1.html
  • and Further Notice of Proposed Rulemaking, 7 FCC Rcd 6903 (1992); Amendment of Part 73, Subpart G, of the Commission's Rules Regarding the Emergency Broadcast System, Notice of Inquiry and Notice of Proposed Rulemaking, 6 FCC Rcd 6739 (1991); Inquiry into Possible Technical Improvements in the Emergency Broadcasting System, Notice of Inquiry, 6 FCC Rcd 4264 (1991). 2 47 C.F.R. 11.44. 3 47 C.F.R. 11.1. 4 See, e.g., NOAA News Release, Homeland Security Uses NOAA All- Hazards Network For Alerts And Warnings (June 17, 2004); CEA News Release, CEA Welcomes DHS and NOAA Public Alert Memorandum of Agreement (June 17, 2004); see also Pennsylvania Emergency Alert System State EAS Plan (2004). 5 Providing for Emergency Control Over Certain Government and Non-Government
• http://www.fcc.gov/eb/Orders/2005/FCC-05-191A1.html
  • which have facilities in place may, without charge, connect an originating source from the nearest exchange to a selected Test Center and then to any EAS Participant. Independent stations will not be connected during the test unless authorized by the FCC. Upon test termination, EAS Participants shall be restored to their original configurations. * * * * * 14. Amend 11.44 by revising paragraph (d) to read as follows: 11.44 EAS message priorities. * * * * * (d) During a national emergency, the facilities of all EAS Participants must be reserved exclusively for distribution of Presidential Messages. NIC messages received from national networks which are not broadcast at the time of original transmission must be recorded locally by LP sources
• http://www.fcc.gov/transaction/echostar-directv/nrtc_petdeny061702.pdf
  • *The Licensee may apply to the International Telecommunication Union (ITU) - through the FCC -- for an extension of this date. In order to receive an extension, the Licensee must make a showing of various due diligence requirements. The lTU may extend the Bring Into Use date by two years under the conditions specified in ITU Radio Regulations Articles 8 11.44B through 811.441. 6S A "-" symbol is inserted in those instances where the FCC has not established a milestone date. ~21~ Certificate of Service I HEREBY CERTIFY that on this 17th day of June, 2002, a true and correct copy of the foregoing Petition to Deny of the National Rural Telecommunications Cooperative in the Matter of Application of VisionS tar