Thanks for the story, pro. Interesting drama, wonder if they'll drop the scrambling on anything on 131w? I'll have to scan it once in a while lol.
today is the day. D* and Comcrap both claim they will not be affected, I just want to make sure Lost airs without a hitch![]()
How odd is that, an Intelsat dish feeding an SES AMC satellite?
Over 62 feet19 meters is a BIG dish!
today is the day. D* and Comcrap both claim they will not be affected, I just want to make sure Lost airs without a hitch![]()
Hi,
I work at a satellite uplink teleport in the San Francisco area. I thought the forum might want some further info regarding the Galaxy 15 issue. We have two services on Anik F3 C-band. One is for rural telephony to Alaska, and the other is extending a computer LAN from the Japanese Ministry of Defense to the Japanese Disaster Relief Team working in Haiti.
Originally, it was thought that the Galaxy 15 satellite would create interference to these circuits as it drifted through 118.7°W (Anik F3 orbital slot). But now it is felt that we (in the SF area) won't be affected because the uplink "receive" beam to the Galaxy 15 satellite will have moved to the East of us by the time it reaches 118.7°W. That's not to mean that other teleports operating out of other areas in CONUS won't be affected.
Here are some notes from the mitigation plan:
- C Band payload remains active and will cause interference to other satellites as it drifts east through the arc from 133W.
- Orbital (manufacturer) expects satellite to trip off in August. Momentum build up will cause loss of earth lock ?August 23 (±20 days):
- Expected to lose earth lock then roll, deplete batteries and payload shut-off occurrence.
- Telesat (Anik F3 owner) will ensure collision avoidance using standard automated processes.
Thanks for the info.
Seems G15 is running reverse polarity for that slot. It is supposed to be odds on vertical. May be playing havoc with small dish FTA on adjacent sats.
Limited time offer