SES-9

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
SES-9
SES-9 (25200743545).jpg
SES-9 satellite in its payload fairing in preparation for launch on a Falcon 9 rocket
Mission type Communication
Operator SES[1]
COSPAR ID 2016-013B
SATCAT № 41381
Mission duration 15 years[1]
Spacecraft properties
Bus BSS-702HP[1]
Manufacturer Boeing[1]
Launch mass 5,271 kilograms (11,621 lb)[2]
Start of mission
Launch date 4 March 2016
Rocket Falcon 9 full thrust
Launch site Cape Canaveral SLC-40
Contractor SpaceX
Orbital parameters
Reference system Geocentric[1]
Regime Geostationary[1]
Longitude 108.2° East[1]
Transponders
Bandwidth 81 ku transponders with frequency equivalent to 36 Mhz each

SES-9 is a geostationary communication satellite operated by SES S.A. SES-9 was successfully launched on Falcon 9 full thrust on 4 March 2016.

Satellite

The payload on Flight 22 is SES-9, a large commsat intended to eventually operate in geostationary orbit in an orbital slot at 108.2 degrees east longitude, providing communication services to northeast Asia, South Asia and Indonesia, as well as maritime communications for vessels in the Indian Ocean,[3] as well as provide mobility beams for "seamless in-flight connectivity for domestic Asian flights operating in countries like Indonesia and the Philippines".[4]

The satellite was built by Boeing, using a model BSS-702HP satellite bus.[5]

SES-9 had a mass of approximately 5,271 kilograms (11,621 lb) at launch,[2] the largest Falcon 9 payload yet to a highly-energetic geosynchronous transfer orbit (GTO).[4]

Market and coverage

SES-9 has 57 high-power Ku-band transponders, equivalent to 81 transponders of 36 MHz bandwidth and, co-located at 108.2°E alongside SES-7, it will provide additional and replacement capacity for DTH broadcasting and data in North east Asia, South Asia and Indonesia, and maritime communications for the Indian Ocean. Broadcasts are on six Ku-band coverage beams:[6]

  • South Asia Beam. Centred on India with a 55dBW signal (40cm dish) and taking in Pakistan, Bangladesh, Sri Lanka, Nepal, and parts of Myanmar.
  • North East Asia Beam. Centred on the Philippines with a 55dBW signal (40cm dish) and taking in the eastern seaboard of China and parts of Indonesia.
  • South East Asia Beam. Centred on Indonesia with a 54dBW signal (45cm dish) and taking in Malaysia, Singapore, and parts of Papua New Guinea.
  • West Indian Ocean Beam. Centred on the Gulf of Oman with a 53dBW signal (50cm dish) and taking in the Arabian Peninsula, East Africa, and the western coast of India and Pakistan.
  • East Indian Ocean Beam. Centred on the Bay of Bengal with a 54dBW signal (45cm dish) and taking in southern and eastern India, Sri Lanka, and parts of Bangladesh, Myanmar, Thailand and Malaysia.
  • Australia Beam. Centred on Adelaide in Australia with a 55dBW signal (40cm dish) and taking in South Australia and parts of Western Australia, Northern Territory (including Alice Springs), New South Wales and Victoria.

Launch

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Lua error in package.lua at line 80: module 'strict' not found.

A successful static fire test of the rocket was completed on 22 February 2016.[5] The launch was scheduled for 24 February 2016 at 6:46pm local time, with a backup launch window the next day at the same time.[4] Neither day produced a launch however as both attempts were aborted: on 24 February, prior to propellant loading "out of an abundance of caution, in order to get the rocket’s liquid oxygen propellant as cold as possible"; and on 25 February, just two minutes prior to launch "citing a last-minute problem with propellant loading."[7]

Subsequently the launch was rescheduled for the evening of Sunday 28 February at 6:46pm EST (23:46 UTC), with a fallback slot the same time next day.[8] The Sunday launch attempt was aborted less than two minutes before liftoff due to fouled range. Another attempt was made the same evening, however, the rocket aborted a moment after ignition due to low thrust alarm. Rising oxygen temperatures due to a boat entering the launch area, together with a suspected helium bubble, were suggested by Elon Musk as the likely reasons for the alarm being triggered.[9]

See also

References

  1. 1.0 1.1 1.2 1.3 1.4 1.5 1.6 Lua error in package.lua at line 80: module 'strict' not found.
  2. 2.0 2.1 Lua error in package.lua at line 80: module 'strict' not found.
  3. Lua error in package.lua at line 80: module 'strict' not found.
  4. 4.0 4.1 4.2 Lua error in package.lua at line 80: module 'strict' not found.
  5. 5.0 5.1 Lua error in package.lua at line 80: module 'strict' not found.
  6. SES-9 fact sheet SES. Accessed March 30, 2016
  7. Lua error in package.lua at line 80: module 'strict' not found.
  8. Lua error in package.lua at line 80: module 'strict' not found.
  9. Lua error in package.lua at line 80: module 'strict' not found.

External links

  • SES site
  • Media related to Lua error in package.lua at line 80: module 'strict' not found. at Wikimedia Commons