Showing posts with label FCC. Show all posts
Showing posts with label FCC. Show all posts

Wednesday, December 19, 2012

US UHF Milsat Pirate Busted

Many of us who monitoring Milsat activity are well aware of the hijinks involving Brazilian (aka Portuguese speaking) pirates transmitting over our UHF milsats. Well one another one of them has been busted, and no he was not in South America, but right here in the United States, New Jersey and an Extra Class Amateur Radio Operator to boot.

So who is our winner of the "Bonehead of 2012 award?" Here is part of the story courtesy of the ARRL website:

FCC Finds New Jersey Ham Violated Communication Act, Reduces Forfeiture from $20,000 to $16,000

After unsuccessfully appealing to the FCC to cancel his $20,000 forfeiture, Joaquim Barbosa, N2KBJ, of Elizabeth, New Jersey was issued a Forfeiture Order stating that he must pay $16,000 for “willfully and repeatedly violating Section 301 of the Communications Act of 1934, as amended by operating a radio transmitting equipment on the frequency 296.550 MHz without Commission authorization.”

The FCC noted in the Forfeiture Order that based on the examination process involved in pursuing an amateur license, “amateur licensees are expected to have an understanding of radio operations and pertinent FCC regulations, including Part 97 of the FCC’s rules governing the Amateur Radio Service. Licensed amateur operators know that they are authorized to operate only on the frequencies listed in Section 97.301 of the rules, as designated by their operator class and license. Pursuant to the Table of Allocations, the 267-322 MHz band -- the band that Barbosa was operating in -- is allocated solely for federal government use, which we continue to believe Barbosa knew (or should have known) was not authorized for non-government use.”

Barbosa’s Amateur Radio license expired August 31, 2008, but his timely filed renewal application was listed as “Offlined for Enforcement Bureau Action” in the ULS. As such, Barbosa was legally allowed to operate while his case was undergoing the enforcement proceedings.

You can read the complete bizarre story on Barbosa and why he thought he could operate on a DoD Milsat uplink/downlink on the ARRL website at:
http://www.arrl.org/news/fcc-finds-new-jersey-ham-violated-communication-act-reduces-forfeiture-from-20-000-to-16-000

And what is 296.550 MHz? From my MilcomMP database:


296.5500 FLTSAT Charlie Navy Fleet Relay (25 kHz) Channel 04 Uplink
The downlink for this uplink is 255.550 MHz.

Here are a couple of the notes in this regard from my database about this 255.550 downlink/296.550 uplink

255.5500 Portuguese pirates music and comms (also noted using DStar digital comms)
255.5500 Portuguese milsat downlink pirates, whistling

So N2KBJ guess we won't be seeing you hand around the ham bands in the future. Just curious how is that Brazilian milsat license you got working out for you?

As old P.T. Barnum you to say, "There's a sucker born every minute" or you may better recognize it in your 296.550 MHz native tongue, " um otário a cada minuto nasce."

Monday, July 09, 2012

Executive order: Obama grabs communications

There is this report from the Canada Free Press by: Doug Hagmann & Joseph Hagmann

In the event you missed the Friday news dump, Barack Hussein Obama issued yet another executive order. Titled “Assignment of National Security and Emergency Preparedness Communications Functions,” it may be read in its entirety on the White House website here. At first blush, it appears that the order modernizes previous communications functionality, particularly as it relates to the continuity of governmental communication during wartime or national crisis as defined by Obama.

The text of the order itself consists of 2,205 words and seven-(7) sections and multiple subsections. The policy statement (section one) seems innocuous and actually beneficial to the continuity of communications within the U.S., until one begins to dissect the order and consider it in context with other Obama issued directives. Extensive analysis of this order, in tandem with other recent Obama orders and signed legislation, suggests a disconcerting pattern of potential overreach by Obama into the area of normal and customary commercial communication systems.

Based on our analysis of this order, it would appear that the implementation of emergency communications by Obama, using all forms of wired and wireless communication systems, is redirected through the Executive branch and could expand such takeover abilities beyond the limits of an actual act of war, national emergency, or other event impacting the national security of the U.S. The order also mandates that the Department of Homeland Security develops and submits such a plan to Obama within sixty-(60) days of this order (section 5.2(h)).

You can read the entire Executive Order at
http://www.whitehouse.gov/the-press-office/2012/07/06/executive-order-assignment-national-security-and-emergency-preparedness-

Wednesday, August 17, 2011

FCC ULS Ready to Accept Selected 8.33 kHz Spaced Licenses

Public Notice:
http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-11-1403A1.pdf

Third Report and Order referenced in Public Notice:
http://www.aerosupavionics.com/document/FCC-10-103A1.pdf

WIRELESS TELECOMMUNICATIONS BUREAU ANNOUNCES THAT UNIVERSAL LICENSING SYSTEM IS READY TO ACCEPT CERTAIN PART 87 AVIATION RADIO SERVICE APPLICATIONS

By this Public Notice, the Wireless Telecommunications Bureau (Bureau) announces that the Universal Licensing System (ULS) is now ready to accept applications for
new or modified aeronautical enroute and flight test stations for authorization to operate with 8.33 kilohertz channel spacing, and applications to assign or transfer aircraft station licenses. These changes were made to implement rules adopted by the Commission in the Third Report and Order in WT Docket No. 01-289.

8.33 Kilohertz Channel Spacing. In the Third Report and Order, the Commission amended its Part 87 rules to permit aeronautical enroute and flight test stations to
use 8.33 kilohertz channel spacing, in order to migrate voluntarily from 25 kilohertz channel spacing.

It concluded that the permissive introduction of 8.33 kilohertz channel spacing in the aeronautical enroute service would provide the aviation industry with the ability to greatly enhance spectrum efficiency and alleviate congestion, while avoiding the imposition of the significant compliance burdens that could result from a mandatory narrowbanding transition. It also concluded that narrowbanding would benefit flight test stations, which likewise face increasing frequency congestion in U.S. airspace. The Commission directed the Bureau to issue a public notice to alert applicants when the Bureau was ready to begin accepting applications for 8.33 kilohertz channel spacing.

The necessary modifications to ULS have been implemented. Aeronautical enroute stations (station class code FA) and flight test stations (station class code FAT) may now apply for VHF channels with 8.33 kilohertz spacing. Specifically, applications may be filed for the following aeronautical enroute frequencies in the 128.825-132.000 MHz and 136.500-137.000 MHz bands: the end frequencies, frequencies within those bands separated from the end frequencies by a multiple of 25 kilohertz
("channels with 25 kilohertz spacing"), and interstitial frequencies separated by 8.33 kilohertz from channels with 25 kilohertz spacing ("channels with 8.33 kilohertz
spacing"). Flight test stations may apply for the VHF frequencies listed in Section 87.303 of the Commission's Rules,3 and frequencies in the 123.125-123.575 MHz band separated by 8.33 kilohertz from the VHF frequencies listed in Section 87.303. The authorized bandwidth for channels with 8.33 kilohertz channel spacing is 8.33 kilohertz; for channels with 25 kilohertz channel spacing, applicants may request an
authorized bandwidth of either 8.33 kilohertz or 25 kilohertz.

Saturday, June 11, 2011

First National EAS Test to be Conducted in November

Rear Admiral James Barnett, Jr., Chief, Public Safety and Homeland Security Bureau, FCC, announced that the National Emergency Alert System (EAS) Test will take place November 9, 2011, at 2pm ET. The announcement was made during a regularly scheduled FCC Meeting on June 9.

"With the date of the National EAS Test now set, broadcast stations will now be able to make their plans to participate. SBE will continue to provide information to our members to assist in their preparation," said SBE President, Vinny Lopez, CEV, CBNT.

The duration may last up to three-and-a-half minutes. The alert enables the president to break into regular broadcasts and address the American public during emergencies.

Similar to local EAS tests that are already conducted frequently, the nationwide test will include broadcast radio and TV stations, cable networks, satellite radio and television services and wireline video service providers across the US, Puerto Rico, the U.S. Virgin Islands and American Samoa. The nation and its territories are divided into 550 EAS areas.

On November 9 those carriers will transmit the message audio message: "This is a test." The audio message will be the same for both radio and television. All will be required to participate. The test is intended to identify and work the bugs out of the system.

"A national test of our Emergency Alert System, with the vital communications support and involvement of participants, is a step towards ensuring that the alert and warning community is prepared to deliver critical information that can help save lives and protect property," said Damon Penn, FEMA's Assistant Administrator of National Continuity Programs. "Because there has never been an activation of the Emergency Alert System on a national level, FEMA views this test as an excellent opportunity to assess the readiness and effectiveness of the current system. It is important to remember that this is not a pass or fail test, but a chance to establish a baseline for making incremental improvements to the Emergency Alert
System with ongoing and future testing. It is also important to remember that the Emergency Alert System is one of many tools in our communications toolbox, and we will continue to work on additional channels that can be a lifeline of information for people during an emergency."

A limited-area test was done in Alaska in January of 2010, with 104 radio stations and 26 TV stations participating. There were points of failure involving audio levels and improperly functioning encoders and decoders. That the hardware is not configured to a single standard complicates matters.

EAS participants are also under the September deadline to implement the Common Alerting Protocol (CAP) data format that will standardize the alerts issued by various federal agencies. The protocol is said to be much more complex than regular EAS transmission, and the FCC may extend that deadline. After the first test in November, weekly or monthly tests are likely to become routine, according to the FCC.

Sunday, September 12, 2010

Nine years later: Towers of Babble

From the The Virginian-Pilot, September 11, 2010
http://hamptonroads.com/2010/09/nine-years-later-towers-babble

A network that allows public safety agencies to communicate with each other remains one of the most elusive and pressing recommendations from the 9/11 Commission. Nine years after America was attacked, there's no guarantee that such a system will ever come into existence.

As The New York Times reported this week, squabbling over who will control a prime slice of broadband spectrum has left plans for a nationwide system literally up in the air.

The Federal Communications Commission has been pushing an approach that would have commercial companies buy and control the airwaves and build fourth-generation wireless networks on it. During emergencies, police and fire and emergency personnel would get control of the network, effectively taking over the airwaves to coordinate interagency communication.

Those public safety groups, however, insist such a network is unlikely to have the capacity needed during an emergency, meaning it could fail under heavy use and put lives at risk. They want exclusive control of the entire section of the spectrum, and they're lobbying Congress for it.
It has been six years since the 9/11 Commission issued its massive report, which included recommendations to improve the response to catastrophes on the scale of the terrorist attacks of Sept. 11, 2001.

That makes the prolonged delay over divvying up broadband spectrum and developing a nationwide interoperable communication system all the more frustrating, particularly for commission members. Two years ago, after an FCC auction failed to draw sufficient commercial bids, the commission's vice chairman told The Washington Post: "I've lost patience... The slowness of this just indicates a lack of urgency and a lack of concern about human survival and human life if a disaster strikes."

The unhurried pace is indeed disappointing, especially given the urgency of the problem. During the attacks on the World Trade Center in New York nine years ago, first responders found themselves - for a variety of reasons - unable to communicate with each other. People died as a result.

There has been some progress that will help in future emergencies.

Today, many police and fire departments, including those in South Hampton Roads, use plain English on their radios instead of arbitrary, agency-specific codes.

They have developed interoperable regional systems and standard operating procedures to communicate during emergencies, and they've held joint training to prepare for hurricanes, plane crashes and other disasters.

Such changes have helped communities become better prepared, but each would be more valuable if they were part of a system that permits local, state and federal agencies from Virginia to Oregon to communicate and coordinate in a large-scale emergency.

Officials have said construction of the network could take as much as a decade. That means if Congress has any intention of seeing the system in place before the 20th anniversary of 9/11, it must act now to settle the debate over access to the broadband spectrum.

Wednesday, October 21, 2009

Comments Sought for Draft Channel Naming Standards

Here is the APCO pdf document with a complete list of interop freqs and the proposed new desigs. This is a must download for active public safety scanner monitors.
http://apcointl.org/new/commcenter911/documents/APCO-NPSTC-ANS-1-104-1DraftPRC.pdf

APCO NPSTC
2009 Oct 20

Alexandria, Va. - The Association of Public-Safety Communications Officials (APCO) International and the National Public Safety Telecommunications Council (NPSTC) released for comments a candidate American National Standard (ANS) to ensure national consistency of interoperability on related radio channels. The proposed Standard Channel Nomenclature for Public Safety Interoperability Channels provides a standardized naming format for each Federal Communications Commission (FCC) designated Interoperability Channel in Public Safety Radio Services.

“The public safety community uses 700 MHz spectrum allocated by the FCC that is replete with interoperability channels,” APCO International Executive Director George Rice said. “It is necessary to develop and employ a common set of channel names. It is crucial that all responders to an incident know which channel to tune their radios to, as well as the band and primary use for the channel.”

NPSTC Chair Ralph A. Haller said that he was pleased to see such a positive step forward in interoperability saying, “Common interoperability channel names will help to assure that any organization responding to an emergency will be able to establish contact immediately when arriving on scene. Although the specific channel names were initially controversial, the proposed standard represents the collective efforts of public safety agencies across the country to reach consensus. NPSTC is pleased to have been instrumental in this process."

The issue of common channel naming has been on the forefront since the mid-1980s and was again highlighted during the terrorist attacks on September 11, 2001 and Hurricane Katrina. In 2006, NPSTC reviewed and updated the Standard Channel Nomenclature recommended in the 700 MHz National Coordination Committee’s Final Report. This new protocol has been widely adopted across the country in the intervening period, and requests to the federal government resulted in finalizing standard names for similar channels in federal agency spectrum earlier this year.

APCO International is the recognized American National Standards Institute (ANSI)-accredited Standards Developer for public safety communications standards and was selected to facilitate the most recent version of the Standard Channel Nomenclature document through the ANSI standardization process, moving one step closer to completion of National Emergency Communications Plan milestone 3.1.33.

There is a 45-day public review and comment period for this standard that ends on November 30. The Candidate ANS can be downloaded at http://apcointl.org/new/commcenter911/ansi-activity.php . To submit comments or questions prior to the deadline, e-mail standards@apco911.org .