Word: fcc
(lookup in dictionary)
(lookup stats)
Dates: during 1940-1949
Sort By: most recent first
(reverse)
...desks of the network executives lay the neat briefs their lawyers had prepared for submission against FCC next week in a New York Federal court. They asked the court to annul the regulations issued last year by FCC and later suspended (TIME, May 12, Oct. 20). Gist of the networks' argument: "1) we are not monopolies; 2) but even if we were, FCC would not be entitled under law to determine the fact or to regulate against it." Last week's anti-trust suits looked at first like the Government's answer...
...nothing so simple. In Washington, FCC's Chairman James Lawrence Fly emphatically denied having anything to do with the suit, or even having known it was to be filed last week...
...Justice Department, filing of the suit was regarded as an almost inadvertent piece of routine. Prepared last summer, it had been pigeonholed while FCC's Fly and the networks reached a working understanding. Especially during the first three weeks of war, CBS and NBC were soothed by Chairman Fly's evident sympathy. Last week they blew up all over again...
...days before Japan attacked the U.S. an FCC monitor in Oregon heard a new and interesting short-wave signal: no message, just two-and three-letter calls. Promptly all monitoring stations in the U.S. began to listen for it. Directional measurements were taken in Texas, in Nebraska, in Georgia, in Massachusetts, in Maryland. Triangulations were worked out. By the time the transmitter began sending messages-in code-FCC knew about where it was. It was about in the German Embassy...
...Department restrained the FBI from moving in. The gumshoes, it was thought, might upset negotiations with Germany for safe exchange of diplomatic personnel. But when Germany's Hans Thomsen and friends departed to take a little rest in West Virginia, the transmitter stopped. To the Post-Dispatch story, FCC last week added two definitive points: 1) every message sent had been decoded; 2) the Embassy sender had been neatly jammed the moment it started sending messages...