StormCh🅰️serTodd's Avatar

StormCh🅰️serTodd

@stormchasertodd.bsky.social

Extreme weather videographer / sUAS pilot, Science, space, travel, Aurora, volcanoes, Investor in AST Spacemobile. Retired Cybersecurity Engineer. You've seen my storm video on all major networks. #JUSTICE #RESIST

486 Followers  |  571 Following  |  193 Posts  |  Joined: 12.11.2024  |  2.2243

Latest posts by stormchasertodd.bsky.social on Bluesky

Screenshot of FCC approval to launch FM-1 Satellite

Screenshot of FCC approval to launch FM-1 Satellite

🚀🚀🚀🚀🚀 $ASTS - FCC approves the launch of FM-1 Satellite! Let's do this!

11.07.2025 14:07 — 👍 29    🔁 3    💬 2    📌 1
Closeup picture of commercial fireworks exploding in the sky

Closeup picture of commercial fireworks exploding in the sky

It's been a long time since I took firework pics. Finally managed to get out and do it this year with my new Nikon Z8.

11.07.2025 14:58 — 👍 1    🔁 0    💬 0    📌 0
$ASTS another record high. Only one modest pullback this entire rally so far.

The move up has been very organized despite the steepness of the move. No sloppy buying or sloppy selling indicating any real capitulation from those on the sidelines rushing in with FOMO or from short sellers panic covering.

Compare it to last year's rally where it was similar price action leading up to the final blowoff top where we saw a substantial increase in volume coupled with sloppy buying and selling intraday.

TLDR: Reformed thinks higher

*NFA

$ASTS another record high. Only one modest pullback this entire rally so far. The move up has been very organized despite the steepness of the move. No sloppy buying or sloppy selling indicating any real capitulation from those on the sidelines rushing in with FOMO or from short sellers panic covering. Compare it to last year's rally where it was similar price action leading up to the final blowoff top where we saw a substantial increase in volume coupled with sloppy buying and selling intraday. TLDR: Reformed thinks higher *NFA

Quality $ASTS content from that other place. I agree with Reformed Trader's commentary that this run is orderly. This is not a blowoff moment. We are going higher.

18.06.2025 20:33 — 👍 6    🔁 1    💬 1    📌 0
Post image

Two nervous girls as the storm approaches Des Moines.

18.04.2025 03:37 — 👍 1    🔁 0    💬 0    📌 0

This *IS* good to see. I hope to see more resistance / complaints in the coming weeks from other entities.

08.04.2025 16:16 — 👍 5    🔁 0    💬 0    📌 0
Before the
FEDERAL COMMUNICATIONS COMMISSION
Washington, D.C. 20554
In the Matter of
Space Bureau and Wireless
Telecommunications Bureau Seek Comment
on Filings of SpaceX and T-Mobile
Requesting to Establish Supplemental
Coverage from Space
Application for Authority for Modification of
the SpaceX NGSO Satellite System to Add a
Direct to Cellular System
)
)
)
)
)
)
)
)
)
)
)
GN Docket No. 23-135; ICFS File Nos. SAT-
MOD-20230207-00021, SAT-AMD-20240322-
00061
Call Sign S3069
ECHOSTAR CORPORATION’S APPLICATION FOR REVIEW
EchoStar Corporation (“EchoStar”) respectfully seeks Commission review of the Space
Bureau’s decision to grant SpaceX’s waiver of the aggregate out-of-band interference limits for
supplemental coverage from space (“SCS”).1 Instead of finding that harmful interference would
be unlikely at the higher power levels proposed by SpaceX, the Bureau failed to make any
decision about the likelihood of harmful interference, granted the waiver, and put the burden on
EchoStar to protect itself. That decision was not reasoned, because the Bureau failed to show
that the Commission’s concerns underlying Section 25.202(k)(1) had changed, been eliminated,
or rendered unlikely. It was also erroneous because the plain text of the Communications Act
vests the Commission with the responsibility to “prevent interference” before it happens.2
Addressing interference after it already happens does not meet that mark.

Before the FEDERAL COMMUNICATIONS COMMISSION Washington, D.C. 20554 In the Matter of Space Bureau and Wireless Telecommunications Bureau Seek Comment on Filings of SpaceX and T-Mobile Requesting to Establish Supplemental Coverage from Space Application for Authority for Modification of the SpaceX NGSO Satellite System to Add a Direct to Cellular System ) ) ) ) ) ) ) ) ) ) ) GN Docket No. 23-135; ICFS File Nos. SAT- MOD-20230207-00021, SAT-AMD-20240322- 00061 Call Sign S3069 ECHOSTAR CORPORATION’S APPLICATION FOR REVIEW EchoStar Corporation (“EchoStar”) respectfully seeks Commission review of the Space Bureau’s decision to grant SpaceX’s waiver of the aggregate out-of-band interference limits for supplemental coverage from space (“SCS”).1 Instead of finding that harmful interference would be unlikely at the higher power levels proposed by SpaceX, the Bureau failed to make any decision about the likelihood of harmful interference, granted the waiver, and put the burden on EchoStar to protect itself. That decision was not reasoned, because the Bureau failed to show that the Commission’s concerns underlying Section 25.202(k)(1) had changed, been eliminated, or rendered unlikely. It was also erroneous because the plain text of the Communications Act vests the Commission with the responsibility to “prevent interference” before it happens.2 Addressing interference after it already happens does not meet that mark.

2
burden to the Commission, not EchoStar. Given all this, the waiver grant could not have
plausibly served the public interest. The Commission should reverse the Bureau.
QUESTION PRESENTED
In March 2024, the Commission adopted the SCS Order, which, among other things, set
an aggregate out-of-band of band interference limit for supplemental coverage from space
services.3 The Commission described that limit as “necessary” to protect wireless operators from
harmful interference, and proponents of weaker limits provided “no evidence” supporting their
claims.4 Despite that, less than a year later, the Space Bureau adopted the Waiver Order,
waiving this limit for SpaceX without deciding that harmful interference would be unlikely.5
Did this decision improperly conflict with the SCS Order, Section 303(f) of the Communications
Act, and the good cause standard for waivers in Section 1.3 of the Commission’s rules?6
BACKGROUND
The SCS Order crafted a regulatory framework for SCS service, including licensing and
service rules to prevent harmful interference. One of those rules is Section 25.202(k)(1), setting
the aggregate out-of-band interference limit for the service at -120 dBW/m2/MHz.7 The

2 burden to the Commission, not EchoStar. Given all this, the waiver grant could not have plausibly served the public interest. The Commission should reverse the Bureau. QUESTION PRESENTED In March 2024, the Commission adopted the SCS Order, which, among other things, set an aggregate out-of-band of band interference limit for supplemental coverage from space services.3 The Commission described that limit as “necessary” to protect wireless operators from harmful interference, and proponents of weaker limits provided “no evidence” supporting their claims.4 Despite that, less than a year later, the Space Bureau adopted the Waiver Order, waiving this limit for SpaceX without deciding that harmful interference would be unlikely.5 Did this decision improperly conflict with the SCS Order, Section 303(f) of the Communications Act, and the good cause standard for waivers in Section 1.3 of the Commission’s rules?6 BACKGROUND The SCS Order crafted a regulatory framework for SCS service, including licensing and service rules to prevent harmful interference. One of those rules is Section 25.202(k)(1), setting the aggregate out-of-band interference limit for the service at -120 dBW/m2/MHz.7 The

8
agency by the statute.”35 The Communications Act tasks the Commission with making “such
regulations not inconsistent with law as it may deem necessary to prevent interference between
stations[.]”36 The Commission’s SCS Order did that for SCS by adopting the aggregate out-of-
band interference limit in Section 25.202(k)(1) that was “necessary” to protect adjacent-band
wireless networks from harmful interference.37
Despite the Commission’s prior finding that out-of-band interference concerns warrant a
rule limiting aggregate emissions, the Bureau waived Section 25.202(k)(1) as requested by
SpaceX.38 In doing so, the Bureau failed to determine that the harmful interference concerns
described in the SCS Order that led to the adoption of Section 25.202(k)(1) had been eliminated.
Instead, all the Bureau said was that “SpaceX has provided engineering analyses in support of its
claim that harmful interference in adjacent bands is unlikely” and that “T-Mobile, an adjacent
band terrestrial operator . . . presents its own technical analyses in which it concludes that the
waiver poses a low likelihood of harmful interference.”39 That is as far as it went. The Bureau
never endorsed the conclusions of either analysis, nor did it reject the technical claims of AT&T,
Verizon, and EchoStar raised in the records for both the SCS Order and the Waiver Order.
AT&T demonstrated that it would suffer a devastating 18% reduction in throughput.40 But the
Waiver Order allowed SpaceX to operate at higher power levels regardless. This failure to rule

8 agency by the statute.”35 The Communications Act tasks the Commission with making “such regulations not inconsistent with law as it may deem necessary to prevent interference between stations[.]”36 The Commission’s SCS Order did that for SCS by adopting the aggregate out-of- band interference limit in Section 25.202(k)(1) that was “necessary” to protect adjacent-band wireless networks from harmful interference.37 Despite the Commission’s prior finding that out-of-band interference concerns warrant a rule limiting aggregate emissions, the Bureau waived Section 25.202(k)(1) as requested by SpaceX.38 In doing so, the Bureau failed to determine that the harmful interference concerns described in the SCS Order that led to the adoption of Section 25.202(k)(1) had been eliminated. Instead, all the Bureau said was that “SpaceX has provided engineering analyses in support of its claim that harmful interference in adjacent bands is unlikely” and that “T-Mobile, an adjacent band terrestrial operator . . . presents its own technical analyses in which it concludes that the waiver poses a low likelihood of harmful interference.”39 That is as far as it went. The Bureau never endorsed the conclusions of either analysis, nor did it reject the technical claims of AT&T, Verizon, and EchoStar raised in the records for both the SCS Order and the Waiver Order. AT&T demonstrated that it would suffer a devastating 18% reduction in throughput.40 But the Waiver Order allowed SpaceX to operate at higher power levels regardless. This failure to rule

9
out harmful interference conflicts with the SCS Order’s technical reasons for adopting Section
25.202(k)(1).
The Bureau tried to cover this hole in its decisionmaking by conditioning SpaceX’s
authorization on a requirement to not cause harmful interference and to address any complaints
of harmful interference from adjacent band users.41 But this condition contravenes the
Communications Act’s mandate to make rules that “prevent interference between stations[.]”42
As the Supreme Court has held, the word “prevent” means “to render (an intended, possible, or
likely action or event) impractical or impossible by anticipatory action.”43 In other words,
“prevent” means to stop something before it happens. Accordingly, the Commission’s statutory
responsibility is to make rules that stop harmful interference at its inception, just like Section
25.202(k)(1) is supposed to do. But unlike an aggregate power limit, the condition in the Waiver
Order allows SpaceX and T-Mobile to interfere with adjacent band users like EchoStar up until
EchoStar detects and reports the interference. Because this non-anticipatory measure only kicks
in after EchoStar suffers from harmful interference, it does not satisfy the prevention required by
the plain text of the Communications Act.
In any event, the Bureau knows that it is immensely difficult for carriers to detect a
particular source of interference. In reality, the condition forces EchoStar to take up this burden
just to keep its basic rights as a licensee. Yet Congress placed the burden to prevent harmful
interference on the Commission and those causing it, not the victim operators.44

9 out harmful interference conflicts with the SCS Order’s technical reasons for adopting Section 25.202(k)(1). The Bureau tried to cover this hole in its decisionmaking by conditioning SpaceX’s authorization on a requirement to not cause harmful interference and to address any complaints of harmful interference from adjacent band users.41 But this condition contravenes the Communications Act’s mandate to make rules that “prevent interference between stations[.]”42 As the Supreme Court has held, the word “prevent” means “to render (an intended, possible, or likely action or event) impractical or impossible by anticipatory action.”43 In other words, “prevent” means to stop something before it happens. Accordingly, the Commission’s statutory responsibility is to make rules that stop harmful interference at its inception, just like Section 25.202(k)(1) is supposed to do. But unlike an aggregate power limit, the condition in the Waiver Order allows SpaceX and T-Mobile to interfere with adjacent band users like EchoStar up until EchoStar detects and reports the interference. Because this non-anticipatory measure only kicks in after EchoStar suffers from harmful interference, it does not satisfy the prevention required by the plain text of the Communications Act. In any event, the Bureau knows that it is immensely difficult for carriers to detect a particular source of interference. In reality, the condition forces EchoStar to take up this burden just to keep its basic rights as a licensee. Yet Congress placed the burden to prevent harmful interference on the Commission and those causing it, not the victim operators.44

Nice to see Echostar push back on the FCC's "arbitrary and capricious" decision to grant the SpaceX request for a waiver of the OOBE limit. $ASTS 🥊
www.fcc.gov/ecfs/documen...

08.04.2025 16:10 — 👍 25    🔁 9    💬 2    📌 0
1/ Ever wonder how a 199 square meter satellite 🛰️ could connect YOUR phone 📱 from space? @AST_SpaceMobile
's BlueBird is making 5G direct to device a reality—and $ASTS stock might just skyrocket 🚀 with it. Check this out! 👀

1/ Ever wonder how a 199 square meter satellite 🛰️ could connect YOUR phone 📱 from space? @AST_SpaceMobile 's BlueBird is making 5G direct to device a reality—and $ASTS stock might just skyrocket 🚀 with it. Check this out! 👀

2/ Millions of Americans can’t get a cellular signal 📶 in the vast rural landscape. @AST_SpaceMobile
’s game-changing D2D network is hitting AT&T and Verizon’s dead zones by early 2026. Is $ASTS the hidden gem 💎 investors are sleeping on? See for yourself! 👇

2/ Millions of Americans can’t get a cellular signal 📶 in the vast rural landscape. @AST_SpaceMobile ’s game-changing D2D network is hitting AT&T and Verizon’s dead zones by early 2026. Is $ASTS the hidden gem 💎 investors are sleeping on? See for yourself! 👇

3/ 3.0 BILLION people could soon be connected in the most remote locations on earth 🌎. @AST_SpaceMobile
's global connectivity is starting 🌐—and $ASTS could be your ticket 🎟️ to the next big thing in telecommunications. Don’t miss this! 🔥

3/ 3.0 BILLION people could soon be connected in the most remote locations on earth 🌎. @AST_SpaceMobile 's global connectivity is starting 🌐—and $ASTS could be your ticket 🎟️ to the next big thing in telecommunications. Don’t miss this! 🔥

Sharing some AMAZING $ASTS Infographics from @paul44250784.bsky.social! 🫡Please review and share with others!

08.04.2025 14:17 — 👍 10    🔁 4    💬 1    📌 0

So of course, less than a month after I decided to retire early so I could travel while I still had health and ability, I started having hip problems and can barely walk. MRI tomorrow. Trip to Amsterdam later this month has been canceled. UGH.

08.04.2025 14:27 — 👍 0    🔁 0    💬 1    📌 0
Post image 12.03.2025 19:21 — 👍 9568    🔁 3016    💬 254    📌 111

Today is the 60th anniversary of the Selma race riot known as "Bloody Sunday". I was in high school in the late 70's and it still pisses me off to this day that we were never taught about it.

07.03.2025 15:06 — 👍 2    🔁 0    💬 0    📌 0

Maybe Musk should spend more of his time paying attention to his SpaceX rockets and less time plotting to destroy our economy.

07.03.2025 13:21 — 👍 1    🔁 0    💬 0    📌 0

EXACTLY. And the dems seem to be just standing by and watching when we need voices SCREAMING about this! So frustrating..

03.03.2025 16:57 — 👍 0    🔁 0    💬 0    📌 0

on the bigger picture

03.03.2025 15:02 — 👍 32    🔁 6    💬 0    📌 0
Post image

When no other reply is accurate.

25.02.2025 18:10 — 👍 9997    🔁 1967    💬 610    📌 130

Snowstorms started hitting differently the year I went to the garage and there was a snow shovel hanging on the wall where my sled used to be.

12.02.2025 17:22 — 👍 2    🔁 0    💬 0    📌 0

I would seriously give my life savings ($328) to see Trump rolling his eyes at this half-time show!

10.02.2025 01:38 — 👍 2    🔁 0    💬 0    📌 0

Every time the Eagles score, Taylor Swift glares at Kelce and writes another song.

10.02.2025 01:17 — 👍 2    🔁 0    💬 0    📌 0

Update: One of the neighbor's dropped out tonight. Jerk.

10.02.2025 01:17 — 👍 1    🔁 0    💬 1    📌 0

NO PING FOR YOU!

08.02.2025 00:17 — 👍 0    🔁 0    💬 0    📌 0

We have an unspoken contest in our neighborhood who will be the last to crumble and shut 'em off. It's now February 7th, and there are four of us left. 5th one took his down last weekend. Seriously considering the permanent lights that you can change color with the seasons....

07.02.2025 23:09 — 👍 2    🔁 0    💬 1    📌 0

Awwww... Use it with Linux and thank me later.

07.02.2025 23:00 — 👍 0    🔁 0    💬 0    📌 0
A small firework shack outside a tiny volunteer fire department in South Dakota labeled "Gregory Ambulance and Fireworks"

A small firework shack outside a tiny volunteer fire department in South Dakota labeled "Gregory Ambulance and Fireworks"

I called this masterpiece "Conflict of Interest"

07.02.2025 22:58 — 👍 5    🔁 2    💬 0    📌 0

Yeah.... Those were the good ol' days

07.02.2025 22:50 — 👍 0    🔁 0    💬 0    📌 0
Post image

Ketchup On Walls Alert: HIGH

07.02.2025 19:50 — 👍 56406    🔁 9407    💬 2055    📌 635

I feel like a lot of them are complicit.

04.02.2025 19:04 — 👍 2    🔁 1    💬 0    📌 0

But our entire system of government is broken right now, so there will be no repercussions. What can "We the people who actually care" do about it? I feel so powerless.

04.02.2025 19:03 — 👍 0    🔁 0    💬 0    📌 0

True Fact: I am still using the CompuServe mouse pad that came with my 2400 Baud modem in 1986.

04.02.2025 19:00 — 👍 1    🔁 0    💬 1    📌 0

As we all know, encryption is a big deal in cybersecurity.
I shall henceforth refer to grinding my coffee beans as "Encrypting the Beans"

30.01.2025 19:19 — 👍 1    🔁 0    💬 0    📌 0

Awww... I just noticed some people from work are following me so now I can't complain about work. (maybe)
Lol next post will be about work.

30.01.2025 19:17 — 👍 1    🔁 0    💬 0    📌 0

Welcome to Iowa.

25.01.2025 03:51 — 👍 4    🔁 0    💬 0    📌 0

@stormchasertodd is following 20 prominent accounts