Echostar 16 Launch - November 20 2012

The design of the E-16 appears to be a lot like the Ciel-2 satellite in that 16 of the 32 TP frequencies can be used for spotbeams. Also the filing appears to imply that E-15 is not for sure moving from 61.5 W or E-12 for that matter. It also should be noted that Dish wants to swap TPs 1 and 2 with TPs 23 and 24 which Dish only has temporary authority to use. This TP swap might be the reason for the early filing because E-16 is designed to use TPs 23 and 24 for spotbeams which are needed more than CONUS beams for the EA. E-16 provides a spotbeam for Puerto Rico and it will be interesting how many TPs will be useable for it.
 
Spacecraft weight: 3228 KG
Fuel: 3030 KG
Lifted Weight: 6258 KG

Construction Completion : 6/12/2012
Estimated Launch Begin Date: 7/1/2012
Estimated Launch End Date: 8/1/2012
Estimated In-Service: 9/15/2012
 
Echostar 16 61.5W Conus Plus & Spot Beam Footprints

The 72 beam footprints for E16 have been uploaded and are available at:

Satelliteguys Satmaps

Geographic names have been added each beam to help identify location when searching for beams in your area.

The 64 bit version of Internet Explorer does not support the Google Earth Plug In required to view the embeds.
 
Will this add to Dish's fleet, or just replace one like Echostar XIV did? (Western Arc could use one more bird.)

Replacing the old rainbow bird acquired from voom. It didn't really have spotbeams setup for use like Dish network needed. This should allow them to pull the conus locals off 77w and put them on spotbeams like they should be.
 
Maps look great but it would be interesting to know how many TP frequencies are assigned to each spotbeam. I guess the west coast spotbeams are for backup but counting them, there is probably at least 20 of the 71 that are spotbeams for Western Arc cities. In regards to 77W, I wouldn't be surprised if locals remain there even after E-16 is deployed because I believe Dish will still need bandwidth for locals on the EA even after E-16 is deployed and it doesn't appear that QuetzSat-1 is truly CONUS for the entire EA.
 
Last edited:
This should allow them to pull the conus locals off 77w and put them on spotbeams like they should be.
:(

In regards to 77W, I wouldn't be surprised if locals remain there even after E-16 is deployed because I believe Dish will still need bandwidth for locals on the EA even after E-16 is deployed and it doesn't appear that QuetzSat-1 is truly CONUS for the entire EA.
:popcorn
 
Maps look great but it would be interesting to know how many TP frequencies are assigned to each spotbeam..

You may find what you need in the tech report.

Tech Report

You can copy the transponder table to an excel file and then manipulate it.
Sometimes, it's easier than building a database query for those items.
 
Last edited:
You may find what you need in the tech report.

Tech Report

You can copy the transponder table to an excel file and then manipulate it.
Sometimes, it's easier than building a database query for those items.

Thanks for the Tech Report. I've started sorting out the TPs for each spotbeam. Folks in Puerto Rico should be happy because there are 5 TP frequencies for the Puerto Rico spotbeam. Interesting there are 6 for Bermuda and some for Mexico/Mexico City and Cuba. As mentioned previously, there are a substantial number of spotbeams for Western Arc cities but I have to believe these are for backup.
 
rocatman said:
Thanks for the Tech Report. I've started sorting out the TPs for each spotbeam. Folks in Puerto Rico should be happy because there are 5 TP frequencies for the Puerto Rico spotbeam. Interesting there are 6 for Bermuda and some for Mexico/Mexico City and Cuba. As mentioned previously, there are a substantial number of spotbeams for Western Arc cities but I have to believe these are for backup.

I suspect they are up to something. The eastern quetzsat beam has an "anomoly" covering Bermuda and covers NA down to Panama. Wonder if they are working on a"resort" package.
 

Will Dish install 2 dishes

bangor locals moved from conus to TID#1132 - no longer appear

Users Who Are Viewing This Thread (Total: 0, Members: 0, Guests: 0)

Who Read This Thread (Total Members: 1)