NASASpaceFlight.com Forum
Commercial and US Government Launch Vehicles => ULA - Delta, Atlas, Vulcan => Topic started by: jacqmans on 01/14/2014 03:19 pm
-
Article - By William Graham:
https://www.nasaspaceflight.com/2016/06/ula-atlasv-muos-5-launch/
Live Coverage:
https://www.youtube.com/watch?v=nFxTr00Mtdw
Background:
Fifth Lockheed Martin MUOS Secure Communications Satellite Completes Assembly, Enters System Test
SUNNYVALE, Calif., January 13, 2014 – The fifth Lockheed Martin [NYSE: LMT] Mobile User Objective System (MUOS) satellite for the U.S. Navy is entering its first system test faster than the previous build, now that integration is complete. Engineers and technicians recently mated its system module and core to the multi-beam assembly (MBA), which hosts 16 ultra-high frequency (UHF) antennas for distributed, global communications coverage.
The MBA’s antennas beam down coverage to Earth, with each covering thousands of miles of terrain. Supporting UHF satellite communications, MUOS will provide secure mobile users with assured communications, including the new capability of simultaneous voice, video and data.
“Our fifth MUOS satellite shows strong learning curve benefits. Compared to our last build, we are approximately 20 percent ahead of schedule,” said Iris Bombelyn, vice president of Narrowband Communications at Lockheed Martin. “We are continuously improving our manufacturing, test, launch and orbit operations to best serve the U.S. Navy and users that need secure, mobile voice and data communications.”
Designed and built by Lockheed Martin, the MUOS antenna rests on an A2100 bus, also built by Lockheed Martin, and uses a system module provided by General Dynamics. Together, the system enables communications coverage using the Wideband Code Division Multiple Access standard, providing a 10-fold increase in transmission throughput over the current UHF satellite system.
Lockheed Martin Space Systems, Sunnyvale, Calif., is the MUOS prime contractor and system integrator. The Navy's Program Executive Office for Space Systems, Chantilly, Va., and its Communications Satellite Program Office, San Diego, Calif., are responsible for the MUOS program.
-
The article in the first post is actually referring to MUOS SV5, which launched as mission MUOS-4 in September.
-
I thought SV3 launched as MUOS 4.
-
Here's the serial numbers as I understand them.
21 Jan 2015 MUOS 3 (SV-4)
2 Sep 2015 MUOS 4 (SV-5)
5 May 2016 MUOS 5 (SV-3)
-
This launch is May 5 not July.
SpaceflightNow says July. What's your source?
http://spaceflightnow.com/2015/07/31/atlas-5-team-begins-stacking-most-powerful-variant-for-navy-launch/
-
This launch is May 5 not July.
SpaceflightNow says July. What's your source?
http://spaceflightnow.com/2015/07/31/atlas-5-team-begins-stacking-most-powerful-variant-for-navy-launch/
Sometimes people don't want to reveal sources.
-
Here's the serial numbers as I understand them.
21 Jan 2015 MUOS 3 (SV-4)
2 Sep 2015 MUOS 4 (SV-5)
5 May 2016 MUOS 5 (SV-3)
This is correct. I am also currently planning on a May launch.
-
https://www.facebook.com/ulalaunch/photos/pcb.10153714301225379/10153714294955379/?type=3&theater
Florida Sen. Bill Nelson (wearing red) visited ULA’s Decatur, Alabama, factory last week. He toured the factory as part of his oversight responsibilities on the Senate's Commerce Committee and the Armed Services Committee. There are 31 missions in various stages of production in ULA’s Alabama facility, including missions that support national security, space exploration and commercial capabilities.
Amateur question. The big line is...?
-
Lockheed Martin’s MUOS Production Line Ships Fifth Secure Communications Satellite to Florida for May Launch (http://www.lockheedmartin.com/us/news/press-releases/2016/march/160302-ssc-muos-satellite-shipping.html)
MUOS-5 is third satellite to launch in 16 months for U.S. Navy’s Smart Phone-Like Network
On March 3, MUOS-5, the next satellite scheduled to join the U.S. Navy’s Mobile User Objective System (MUOS) secure communications network, arrived at Cape Canaveral after shipping from Lockheed Martin’s satellite manufacturing facility in Sunnyvale, California.
CAPE CANAVERAL AIR FORCE STATION, Fla., March 9, 2016 – The U.S. Navy and Lockheed Martin (NYSE: LMT) delivered the fifth Mobile User Objective System (MUOS) satellite to Cape Canaveral Air Force Station, Florida, on March 3, prior to its expected May launch.
The spacecraft will be the third MUOS satellite launched in a 16-month span, a cadence that demonstrates the production line concept put into place for the delivery of this five-satellite build.
MUOS-5 is the latest addition to a network of orbiting satellites and relay ground stations that is revolutionizing secure communications for mobile military forces. Users with operational MUOS terminals will be able to seamlessly connect beyond line-of-sight around the world and into the Global Information Grid. MUOS’ new capabilities include simultaneous, crystal-clear voice, video and mission data, over a secure high-speed Internet Protocol-based system, similar to today’s smart phones.
MUOS-5 will complete the Navy’s baseline constellation and serve as an on-orbit spare for the system, ensuring the network is always available to support U.S. and allied mobile forces.
“As MUOS-5’s launch approaches, MUOS-4 is preparing to begin operations on-station, enabling MUOS’ near-global coverage,” said Mark Woempner, program director of Lockheed Martin’s Narrowband Communications mission area. “We are proud that we will soon be providing our mobile forces access to the system’s enhanced communications capabilities from nearly anywhere, including further into polar regions than ever before.”
Lockheed Martin manufactured MUOS-5 at its Sunnyvale, California facility. For its trip to Florida the satellite was loaded aboard a C-5 Galaxy aircraft at nearby Moffett Federal Air Field by the 60th Air Mobility Wing of Travis Air Force Base. Astrotech Space Operations, a Lockheed Martin wholly-owned subsidiary in Florida, will complete MUOS-5’s pre-launch processing.
The satellite joins MUOS-1, MUOS-2, MUOS-3, and MUOS-4 already on orbit. All four required MUOS ground stations are complete. More than 55,000 currently fielded radio terminals can be upgraded to be MUOS-compatible, with many of them requiring just a software upgrade.
Once fully operational, the MUOS network will provide 16 times the capacity of the legacy ultra high frequency communications satellite system, which it will continue to support, and eventually replace.
For additional information, photos and video visit: www.lockheedmartin.com/muos (http://www.lockheedmartin.com/muos)
About Lockheed Martin
Headquartered in Bethesda, Maryland, Lockheed Martin is a global security and aerospace company that - with the addition of Sikorsky - employs approximately 126,000 people worldwide and is principally engaged in the research, design, development, manufacture, integration and sustainment of advanced technology systems, products and services.
***
My comment: The travel points of this satellite's journey appear to be Lockheed-Martin, Sunnyvale to Moffett Field to CCAFS Skid Strip to Astrotech, Titusville.
***
-
Amateur question. The big line is...?
LO2 vent valve assembly.
BTW, that booster and its Centaur arrived at the Cape via Delta Mariner this week.
-
***
My comment: The travel points of this satellite's journey appear to be Lockheed-Martin, Sunnyvale to Moffett Field to CCAFS Skid Strip to Astrotech, Titusville.
***
Payload assembly began at the now-shuttered Newtown, PA facility before being shipped to Sunnyvale to be mated into the spacecraft configuration.
-
Atlas V to Launch the Fifth Mobile User Objective System (MUOS-5)
Atlas V MUOS-5 Mission ArtworkRocket/Payload: An Atlas V 551 will launch the U.S. Navy’s fifth Mobile User Objective System (MUOS-5) satellite, built by Lockheed Martin.
Date/Site/Launch Time: Thursday, May 5, from Space Launch Complex-41 at Cape Canaveral Air Force Station, Florida.
Mission Description: The fifth Mobile User Objective System (MUOS-5) satellite is the latest addition to a network of orbiting satellites and relay ground stations that is revolutionizing secure communications for mobile military forces. Users with operational MUOS terminals can seamlessly connect beyond line-of-sight around the world and into the Global Information Grid. MUOS’ new commercial, cellular-based capabilities include simultaneous, crystal-clear voice, video and mission data, over a secure high-speed Internet Protocol-based system.
Launch Notes: MUOS-5 will mark the ULA’s fourth launch of 2016 and the 63rd Atlas V since the vehicle’s inaugural launch in August 2002. MUOS-5 will be the seventh mission to launch in the 551 configuration; other missions launched in this configuration include four previous MUOS missions as well as the New Horizons mission to Pluto and the Juno mission to Jupiter.
Launch Updates: To keep up to speed with updates to the launch countdown, dial the ULA launch hotline at 1-877-852-4321 or join the conversation at www.facebook.com/ulalaunch, twitter.com/ulalaunch and instagram.com/ulalaunch.
Go Atlas! Go Centaur! Go MUOS-5!
-
https://twitter.com/NASASpaceflight/status/713414601367547905
"ULA delay Atlas V MUOS-5 mission to NET May 12 to further review the data anomaly experienced during the OA-6 mission."
What was the anomaly? Lower than expected thrust?
-
What was the anomaly? Lower than expected thrust?
Premature Atlas stage cutoff. It's all over the OA-6 live thread.
-
What was the anomaly? Lower than expected thrust?
Premature Atlas stage cutoff. It's all over the OA-6 live thread.
At risk of derailing the thread (sorry), what kinda of dV was lost with those 6s of burn time? I realize it can be quite a bit given that's supposed to be the lightest stack that first stage gets to push against. I could calculate it myself but if you know it off the top of your head it'd be nice.
-
Go to the OA-6 thread
-
Can I ask a MUOS-5 related question. So they are delaying 7 days. Does that mean they are stopping all work on MUOS-5 for a week and looking at the data instead?
I assume if they find something in the data that needs correcting, this launch could slip more than 7 days. True? This is a penciled in date until they know the scale of a potential problem?
-
Can I ask a MUOS-5 related question. So they are delaying 7 days. Does that mean they are stopping all work on MUOS-5 for a week and looking at the data instead?
I assume if they find something in the data that needs correcting, this launch could slip more than 7 days. True? This is a penciled in date until they know the scale of a potential problem?
Processing continues. The Centaur just underwent first power application this week, and offsite vertical integration of up-stage components has started and will continue. Slipping the ILC just adds some pad to the integration/test schedule.
Sure, there's potential for further slippage, based on the pace of the investigation. Progress is being made, however.
-
Can I ask a MUOS-5 related question. So they are delaying 7 days. Does that mean they are stopping all work on MUOS-5 for a week and looking at the data instead?
I assume if they find something in the data that needs correcting, this launch could slip more than 7 days. True? This is a penciled in date until they know the scale of a potential problem?
Processing continues. The Centaur just underwent first power application this week, and offsite vertical integration of up-stage components has started and will continue. Slipping the ILC just adds some pad to the integration/test schedule.
Sure, there's potential for further slippage, based on the pace of the investigation. Progress is being made, however.
Correct me if I'm wrong, but as I understand it they are going to delay the Atlas CCB move from the ASOC to the SLC-41 VIF by a day or so to do some checks that they cant easily do in the VIF while stacked on the MLP.
-
Can I ask a MUOS-5 related question. So they are delaying 7 days. Does that mean they are stopping all work on MUOS-5 for a week and looking at the data instead?
I assume if they find something in the data that needs correcting, this launch could slip more than 7 days. True? This is a penciled in date until they know the scale of a potential problem?
Processing continues. The Centaur just underwent first power application this week, and offsite vertical integration of up-stage components has started and will continue. Slipping the ILC just adds some pad to the integration/test schedule.
Sure, there's potential for further slippage, based on the pace of the investigation. Progress is being made, however.
Correct me if I'm wrong, but as I understand it they are going to delay the Atlas CCB move from the ASOC to the SLC-41 VIF by a day or so to do some checks that they cant easily do in the VIF while stacked on the MLP.
I don't see a delay in the updates I receive, but even if there is one it's no big deal.
-
Any new NET date?
-
May 12 is the new NET date per ULA.
-
Apologies, I should have been more specific. I was looking for a new one after the May 12 date. I had heard 5/27 from someone, but thought I would check here since the people here seem pretty well informed.
-
Apologies, I should have been more specific. I was looking for a new one after the May 12 date. I had heard 5/27 from someone, but thought I would check here since the people here seem pretty well informed.
Why the 27th? Was the mission delayed again?
-
No further delays have been announced.
-
ULA:
Cape Canaveral Air Force Station, Fla. (April 8, 2016) -- The Atlas V MUOS-5 launch is delayed and indefinite on the Eastern Range due to ongoing evaluation of the first stage anomaly experienced during the OA-6 mission. ULA successfully delivered the OA-6 Cygnus spacecraft to the International Space Station (ISS) on March 22. The MUOS-5 spacecraft and launch vehicle are secure at their processing facilities.
-
So Tory Bruno wasn't worried about the manifest dragging out. Crickets chirping?
-
Can the Delta-IV or Delta-IV heavy deliver MUOS-5 to the ego transfer orbit required?
-
Can the Delta-IV or Delta-IV heavy deliver MUOS-5 to the ego transfer orbit required?
One of them could, but they'd be looking at significant lead time to get something built and ready to launch. There's a good chance the time period would be over and above the time it takes to resolve the A-V problem. (That's assuming politics, from different sources, doesn't delay things even longer.) If the decision is made, then, first, all of the payload and launch calculations and planning would have to be re-done, evaluated, and approved before any hardware starts getting assembled.
Regardless of multiple launch options and the commonality of interfaces for payloads, EELV isn't 'plug-n-play'. They don't have multiple boosters and 2nd stages sitting in storage waiting for payloads, either, especially for massive payloads like MUOS (almost 7.5t/6800kg). So the hardware will need time to be manufactured and assembled, and tested.
So there's that lead time, plus the launch operations once the hardware is ready, which can take an additional 2-3 months for the D-IV/D-IVH. So, maybe 10-12 months as a rough estimate (and that's probably an accelerated time table.)
-
Can the Delta-IV or Delta-IV heavy deliver MUOS-5 to the ego transfer orbit required?
Only the Heavy
-
Can the Delta-IV or Delta-IV heavy deliver MUOS-5 to the ego transfer orbit required?
Only the Heavy
It seems like the biggest Delta-IV could get pretty close to the desired orbit, maybe close enough in practice. MUOS is quoted as massing 6740 kg, and the Atlas 551 puts it into a 3463xGEO at 19 degree orbit. If I did the math right, that about 1425 m/s remaining.
Delta-IV M+(5,4) is quoted as lifting 7430 kg to GEO-1800 orbit. So if it lifted MUOS into this orbit, it would have about 700 kg of fuel left over. Assuming a 2t Centaur, a 6.7t MUOS, and ISP of 450, the last 700kg of fuel should be good for an additional 340 m/s or so. If you burned this at apogee, you have about 1470 m/s the satellite must supply.
Considering that GEO station-keeping costs something like 50 m/s per year, that implies only a 1 year reduction in lifetime compared to the Atlas launch. For the savings in cost over a Delta-IV heavy this might be acceptable.
Of course this is just back of the envelope, and you'd need to worry about the mass of the adapter (is it included?), the mass of the kit to burn at apogee, disposal of the stage, etc. But it might just barely be possible (though doubtless the Atlas is more desirable).
-
Delta-IV M+(5,4) is quoted as lifting 7430 kg to GEO-1800 orbit. So if it lifted MUOS into this orbit,
That isn't the desired orbit and hence that is why it is not able to launch MUOS. It doesn't matter Delta-IV M+(5,4) can get it to GEO-1800 orbit. And it is more than just 1 year of spacecraft propellant. There are also some fairing considerations.
-
Given the lead time on RS-68A and other long lead time items, a Delta IV Heavy needs no less than 30 month from ATP to launch. So say three years delay for switching to Delta IV. I guess they will wait to resolve the Atlas V anomaly.
-
Spaceflightnow identifies May 27 as the next date: http://spaceflightnow.com/2016/04/12/new-target-date-for-next-atlas-5-launch/
CAPE CANAVERAL — As the internal investigation continues into the first stage performance trouble on the last Atlas 5 rocket launch, the next mission on the manifest has slipped to May 27.
Originally planned for May 5, the flight of the Navy’s fifth and final planned Mobile User Objective System communications satellite has been postponed twice while engineers work to determine the exact cause of the anomaly.
-
Centennial, Colo., (April 29, 2016) --
Last Friday, in preparation for the MUOS-5 launch, the Atlas V completed the Launch Vehicle on Stand (LVOS) operation, erecting the Atlas V into the Vertical Integration Facility at Cape Canaveral Air Force Station. LVOS will allow configuration of the vehicle to support RD-180 engine inspections and confirm all engine components are ready for launch. The Atlas V MUOS-5 launch is targeted for early summer; a new launch date has not been secured on the Eastern Range. The impact to the remainder of the Atlas V manifest is in review with new launch dates being coordinated with our customers. All missions manifested for 2016 are expected to be successfully executed by the end of the year, including OSIRIS-REx, which will remain in early September to support its critical science window.
-
Targeting June 24 now:
http://spaceflightnow.com/2016/05/03/new-lineup-plan-spelled-out-for-upcoming-atlas-5-rocket-launches/
-
Targeting June 24 now:
http://spaceflightnow.com/2016/05/03/new-lineup-plan-spelled-out-for-upcoming-atlas-5-rocket-launches/
Not sure that is correct , Falcon 9 CRS-9 launch is on that day currently
https://spaceflightnow.com/launch-schedule/
-
Targeting June 24 now:
http://spaceflightnow.com/2016/05/03/new-lineup-plan-spelled-out-for-upcoming-atlas-5-rocket-launches/
Not sure that is correct , Falcon 9 CRS-9 launch is on that day currently
https://spaceflightnow.com/launch-schedule/
that is correct. The CRS-9 will be slipping a couple days at least, as 47S is launching to ISS on 6/24 (as well).
-
Targeting June 24 now:
http://spaceflightnow.com/2016/05/03/new-lineup-plan-spelled-out-for-upcoming-atlas-5-rocket-launches/
Not sure that is correct , Falcon 9 CRS-9 launch is on that day currently
https://spaceflightnow.com/launch-schedule/
Before MUOS moved to that date, ULA had it for NROL-61, and I believe the range was secured. SpaceX never had that date.
-
Atlas V to Launch the Fifth Mobile User Objective System (MUOS-5)
Atlas V MUOS-5 Mission ArtworkRocket/Payload: A United Launch Alliance Atlas V 551 will launch the U.S. Navy’s fifth Mobile User Objective System (MUOS-5) satellite, built by Lockheed Martin.
Date/Site/Launch Time: Confirmed on the Eastern Range for Friday, June 24, 2016, from Space Launch Complex-41 at Cape Canaveral Air Force Station, Florida.
Webcast: The launch will be broadcast live via the ULA website.
Mission Description: The fifth Mobile User Objective System (MUOS-5) satellite is the latest addition to a network of orbiting satellites and relay ground stations that is revolutionizing secure communications for mobile military forces. Users with operational MUOS terminals can seamlessly connect beyond line-of-sight around the world and into the Global Information Grid. MUOS’ new commercial, cellular-based capabilities include simultaneous, crystal-clear voice, video and mission data, over a secure high-speed Internet Protocol-based system.
Launch Notes: MUOS-5 will mark the 63rd Atlas V since the vehicle’s inaugural launch in August 2002. MUOS-5 will be the seventh mission to launch in the 551 configuration; other missions launched in this configuration include four previous MUOS missions as well as the New Horizons mission to Pluto and the Juno mission to Jupiter.
Launch Updates: To keep up to speed with updates to the launch countdown, dial the ULA launch hotline at 1-877-852-4321 or join the conversation at www.facebook.com/ulalaunch, twitter.com/ulalaunch and instagram.com/ulalaunch. Hashtags #MUOS and #AtlasV.
Go Atlas! Go Centaur! Go MUOS-5!
-
Ready to Go: Lockheed Martin-Built MUOS-5 Secure Communications Satellite Encapsulated for June 24 Launch
Date(s): 14-Jun-2016 11:36 AM
MUOS-5 Completes Constellation for U.S. Navy's New Network
CAPE CANAVERAL AIR FORCE STATION, Fla., June 14, 2016 /PRNewswire/ -- The fifth Mobile User Objective System (MUOS) satellite built by Lockheed Martin (NYSE: LMT) for the U.S. Navy was encapsulated in its protective launch vehicle fairing on June 4 . It is scheduled to launch June 24 aboard a United Launch Alliance Atlas V rocket.
MUOS-5 is the latest addition to a network of orbiting satellites and relay ground stations that is revolutionizing secure communications for mobile military forces. Users with MUOS terminals will be able to seamlessly connect beyond line-of-sight around the world and into the Global Information Grid. MUOS' capabilities include simultaneous, crystal-clear voice, video and mission data over a secure high-speed Internet Protocol-based system.
"Like its predecessors, MUOS-5 has two payloads to support both these new Wideband Code Division Multiple Access (WCDMA) waveform capabilities, as well as the legacy Ultra High Frequency (UHF) satellite system, used by many mobile forces today," said Mark Woempner , program director of Lockheed Martin's Narrowband Communications mission area. "On orbit, MUOS-5 will augment the constellation as a WCDMA spare, while actively supporting the legacy UHF system."
The MUOS-5 satellite joins four MUOS satellites already on orbit and four operational ground stations, providing near-global coverage including communications deep into polar regions. More than 55,000 currently fielded radio terminals can be upgraded to be MUOS-compatible, with many of them requiring just a software upgrade.
Once fully operational, MUOS will provide users with 16 times more communications capacity than the legacy system it will eventually replace.
Lockheed Martin manufactured MUOS-5 at its Sunnyvale, California facility. In March, the satellite shipped to the Cape, where it was pre-launch processed and finally encapsulated at Astrotech Space Operations, a wholly owned subsidiary of Lockheed Martin .
The Navy's Program Executive Office for Space Systems and its Communications Satellite Program Office, San Diego, California , are responsible for the MUOS program.
For additional information, photos and video visit: www.lockheedmartin.com/muos
-
MUOS-5 Encapsulation, posted by ULA on Youtube.
https://www.youtube.com/watch?v=5vyq1qrhKB8
-
Looks like some new acoustic protection inside the fairing.
-
MUOS 5 Payload mate, posted by ULA on Youtube.
https://www.youtube.com/watch?v=o2U3s7zF_BQ
https://www.youtube.com/watch?v=GZ-mwt7OCGI
-
-
Atlas V MUOS-5 L-4 Forecast 20 June (http://www.patrick.af.mil/Portals/14/documents/Weather/AV-063%20MUOS-5%20L-4%20Forecast.pdf?ver=2016-06-20-121458-527)
80% favorable
80% favorable, in case of 24 hour delay
-
ULA:
"Everything is progressing toward the ULA Atlas V launch carrying the U.S. Navy's fifth Mobile User Objective System (MUOS-5) satellite, built by Lockheed Martin. The mission is set to lift off on a ULA Atlas V rocket on Friday, June 24 from Space Launch Comple-41 at Cape Canaveral Air Force Station in Florida. The launch window is 10:30-11:14 a.m. EDT. Today’s L-4 forecast shows a 80 percent chance of favorable weather conditions for launch."
-
No changes in the L-3 forecast. Still only a 20% chance of violation for both the 24th and the 25th, with both days watching the cumulus cloud rule.
-
WESTERN NORTH ATLANTIC.
ROCKETS.
1. HAZARDOUS OPERATIONS 241430Z TO 241559Z JUN,
ALTERNATE 251426Z TO 251555Z JUN
IN AREAS BOUND BY:
A. 28-36N 080-36W, 28-38N 080-34W,
28-35N 080-08W, 28-29N 079-18W,
28-26N 079-06W, 28-23N 079-06W,
28-23N 079-17W, 28-28N 080-12W,
28-28N 080-18W, 28-32N 080-33W,
28-33N 080-35W.
B. 28-20N 078-17W, 28-16N 077-45W,
28-13N 077-45W, 28-17N 078-17W.
C. 27-02N 070-00W, 26-50N 068-39W,
26-41N 068-39W, 26-56N 070-00W.
D. 21-50N 050-11W, 21-07N 048-07W,
20-59N 048-07W, 21-45N 050-15W.
2. CANCEL THIS MSG 251655Z JUN 16.//
Authority: EASTERN RANGE OP A7085 141308Z JUN 16.
-
Looks like some new acoustic protection inside the fairing.
Yep. The Helmholtz resonator's are no more.
-
Atlas V MUOS-5 Mission Profile
UnitedLaunchAlliance
Published on Jun 22, 2016
https://youtu.be/Wcdj2KIhlvw?t=001
https://youtu.be/Wcdj2KIhlvw
-
Nice, clear simulation. If only they'd switch to map mode we could also see the numbers for apoapsis and periapsis and the delta-v of the maneuvres.
-
Updated forecast from yesterday, still 80% go for launch day and 24 hr delay (with cumulus clouds the only potential concern).
-
For completeness, here's today's updated forecast - no change to probabilities or potential issues from before.
-
ULA did a live Periscope feed of the roll-out: https://www.periscope.tv/w/1kvKpZVaOomJE (https://www.periscope.tv/w/1kvKpZVaOomJE)
-
Nice pad photo:
Spaceflight Now @SpaceflightNow 2h2 hours ago
From most powerful Delta rocket two weeks ago to most powerful Atlas launching tomorrow https://t.co/brZOD7hfxX
https://twitter.com/SpaceflightNow/status/745970130081951744 (https://twitter.com/SpaceflightNow/status/745970130081951744)
-
Moved for live coverage!
-
ULA note there will be a webcast via youtube starting tomorrow!
Links later today:
https://www.youtube.com/user/UnitedLaunchAlliance
-
Rollout photos from ULA.
-
Cape Canaveral Air Force Station, Fla. (June 23, 2016) A ULA Atlas V rocket, with the MUOS-5 satellite, is rolled from the Vertical Integration Facility to the pad at Space Launch Complex-41.
Photo credit: United Launch Alliance
Additional photos located here: http://www.ulalaunch.com/file-library.aspx
-
Sorry, this one from ULA is too good to not post it!
-
For those who may want to try to catch the Centaur venting http://www.satobs.org/seesat/Jun-2016/0097.html
-
Say what you will about the Atlas, that is one beautiful bird!
-
William Graham's feature article for this mission!
https://www.nasaspaceflight.com/2016/06/ula-atlasv-muos-5-launch/
-
ULA did a live Periscope feed of the roll-out: https://www.periscope.tv/w/1kvKpZVaOomJE (https://www.periscope.tv/w/1kvKpZVaOomJE)
Looks like this'll be Andrea's second launch commentary.
-
In countdown's first weather briefing, conditions favorable for Atlas today with 80% GO odds https://t.co/brZOD7hfxX
https://twitter.com/SpaceflightNow/status/746261168663171072 (https://twitter.com/SpaceflightNow/status/746261168663171072)
-
-
https://youtu.be/nFxTr00Mtdw
-
Tory Bruno on twitter: "Tanking underway"
https://twitter.com/torybruno/status/746332656674045952
-
For those living on the old continent, the launch window is 14:30-15:14 UTC today, so about an hour from now.
-
Just wondering, what determines the color of the first stage of the Atlas V? Usually it's copper but sometimes it's white?
-
Just wondering, what determines the color of the first stage of the Atlas V? Usually it's copper but sometimes it's white?
The first stage of the Atlas V is always orange-coppery. It's the colour of the insulation, because the tanks hold very cold liquid oxygen.
-
Just wondering, what determines the color of the first stage of the Atlas V? Usually it's copper but sometimes it's white?
http://forum.nasaspaceflight.com/index.php?topic=12518.5
The conversion coating process can produce slight differences in color, but they all get it.
-
-
Ah, they've switched over to their traditional webcast countdown....but it's all good.
-
Less than eight minutes until the webcast begins.
L-28 minutes.
-
At around L-19 minutes, the T-4 minute hold should initiate for 15 minutes.
-
4 minutes until the webcast begins.
-
L-23 minutes.
-
And we are live. Let's do this.
-
Looks like the commentator from the GPS IIF-12 broadcast will be informing us for this webcast.
-
-
Looks like more than 80% GO for weather; there are clear skies.
-
Hi Altas V! And https://twitter.com/AndieMarieC is commentating!
-
T-4 minutes and holding.
-
No issues being worked.
-
-
Steve Agid now showing us the launch event timeline.
-
Stock footage is shown from the MUOS 1 and MUOS 2 launches in 2012 and 2013 respectively. Juno's launch from 2011 is also being shown.
-
3D Printing @ ULA
-
L-14 minutes. 10 minutes from resuming the count.
-
100 percent go weather now.
-
-
Not only this will be the third Atlas V launch for 2016; this will be the "Return to Flight" for Atlas V since the Cygnus OA-6 first stage issue was discovered.
-
551
-
Nice 551 graphic
-
Prelaunch activities now being shown; this includes the payload fairing encapsulation and rocket rollout to the pad.
-
L-11 minutes and counting.
-
All iced up and ready to go. Don't blink or you'll miss this one - the 551 wastes no time getting off the pad.
-
The "In Memory Of" segment now being shown.
-
-
Holdfire switches in PROCEED position.
-
-
The final GO/NO GO poll should start any time now.
-
-
in memory
-
Polling for terminal count. All Go.
-
-
All 30 personnel members have given their approval for launch at 14:30 Zulu. Standing by to pick up the count.
-
I like the green board addition.
-
"Green Board"! :)
-
4 minutes and counting.
-
-
T-4 mins and counting!
-
T-4 and counting...
-
Rocketcam on first stage being previewed. This view will be lost prior to stage sep.
-
3 minutes and counting. The first stage and Centaur valves now being closed at this time.
-
-
Tanks to flight pressure.
-
go for launch
-
FTS internal.
-
-
Two minutes and counting. At T-3 seconds, the Sound Suppression Water System will activate to absorb the shock of the 2.5 million pounds of thrust.
-
-
Atlas V now on internal power. T-90 seconds.
-
T-60 seconds.
Launch enable.
-
T-1 minute.
-
-
T-40 seconds. Weather still GO. Range is GREEN as well.
-
Range Green.
Go Atlas. Go Centaur. Go MUOS-5!
-
T-25 seconds. Status check complete. T-15 seconds. LOX topping GO. 10, 9, 8, 7, 6, 5, 4, 3, 2, 1, 0. We have ignition and liftoff of the fifth MUOS satellite and the Return to Flight for Atlas V.
-
Roll program is complete and pitch program is in. Mach 1 and Max-Q have been passed.
-
LAUNCH!!!
-
LAUNCH!!
-
MaxQ
-
-
Passing 1 minute into the flight. Solid boosters and RD-180 continue to burn well.
-
SRB sep nominal.
-
There go the boosters.
-
-
Passing 3 minutes into the flight. Payload fairing has separated along with the CFR. No recontact detected.
-
-
2.5 G throttling for fairing sep.
-
Standing by for BECO. This better occur on time.
-
BECO. Stage sep confirmed. Full thrust on Centaur engine.
-
-
Staging 1-2.
-
There's another rocketcam looking aft at the RL-10C-1 engine.
-
enjoying ;)
-
7 minutes until Centaur MECO-1. The commentator now interviewing Pete Sheehy about the MUOS constellation.
-
1. Was anybody timing the stage 1 burn?
2. When does the boostback burn start?
/s
Cutting to commentators now.
-
It seems as if we lost the rocketcam view on the Centaur. I was looking at the ASOC videoboard.
-
He's rather decorated.
-
Several minutes until Centaur MECO-1. Now that the rocketcam feeds are gone, we'll have to rely on the STK telemetry to see what's going on.
-
Over ten minutes into the flight. Two minutes until Centaur MECO-1.
-
The RL-10C-1 engine continues to burn nominally.
-
RL-10 burning Ox rich
-
We are now positive perigee. Centaur MECO-1 occurring momentarily. And there's MECO-1. Vehicle now in a coast phase.
-
You know, it seems as if each commentator has a script in front of them and cannot say what they want. Am I right?
Now showing a presentation about MUOS.
-
Tory Bruno on twitter-"All systems green"
https://twitter.com/torybruno/status/746353034733588481
-
https://www.youtube.com/watch?v=h-3BTUWTiEc
-
17 minutes Mission Elapsed Time.
-
Photos: 45th Space Wing at Patrick Air Force Base, Fla.
-
21 minutes into the flight. Centaur MES-2 should occur within several minutes from now.
-
Centaur MES-2.
-
Second burn.
-
Less than 5 minutes until Centaur MECO-2. RL-10C-1 continues to burn well.
-
The commentator resuming her interview with Pete Sheehy.
-
Tables have turned. Pete Sheehy now asking the commentator a bunch of questions via social media.
-
Answering viewer questions.
Boiloff rate of LOX?
Negligible, we never calculated it.
-
Centaur still burning nominally. Several minutes between now and Centaur MECO-2.
-
1.5 degrees of yaw angle to compensate for 5 asymmetric boosters.
-
40,000 lines of code for Atlas avionics.
-
Still on social media questions, but the tables are flipping yet again. Pete Sheehy now answering the questions.
Oh, wait! Just one question before going back to the STK telemetry.
-
Centaur MECO-2. A two-hour coast phase will now follow.
ULA webcast should end pretty soon.
-
New fabric acoustical protection being used inside the fairings now for more clearance and protection.
-
MECO-2. Now a long coast phase.
-
The third Centaur burn should last nearly one minute before MECO-3 and eventually the separation of MUOS 5.
A launch replay now being traditionally played before the webcast completion.
-
Once again, Chris, it was an honor to provide the play-by-play despite the mission being not over yet.
-
Super job by all,
Once again, Chris, it was an honor to provide the play-by-play despite the mission being not over yet.
Super job and thanks to all that joined in. Mission still in progress of course.
William's article updated to where we currently are:
https://www.nasaspaceflight.com/2016/06/ula-atlasv-muos-5-launch/
-
Interesting KSC TV HD on the bars at termination of broadcast.
-
To be honest, I was nervous up until Booster Engine Cutoff, after which I was relieved for the remainder of the flight.
-
By the way, this marked the 42nd day launch of an Atlas V. Launch occurred 4 hours and 4 minutes after sunrise (6:26 AM).
-
1. Was anybody timing the stage 1 burn?
2. When does the boostback burn start?
/s
Cutting to commentators now.
1. I got about 4:30 from the launch replay video--ignition at 0:56, cutoff at 5:26 (not totally accurate due to commentator delay.) The launch aritcle lists the burn as 4:25.6.
-
RELEASE #062416
45th SW supports successful Atlas V MUOS-5 launch
By 45th Space Wing Public Affairs
CAPE CANAVERAL AIR FORCE STATION, Fla. – The Air Force’s 45th Space Wing supported United Launch Alliance’s successful launch of the MUOS-5 spacecraft aboard an Atlas V rocket from Space Launch Complex 41 here June 24, 2016, at 10:30 a.m. ET.
The ULA Atlas V rocket is carrying the U.S. Navy's fifth Mobile User Objective System satellite built by Lockheed Martin. MUOS is the U.S. military’s answer to secure and reliable tactical communications. This next generation narrowband satellite communications system will provide significantly improved and assured communications for mobile warfighters.
“Today’s successful launch is the culmination of the 45th Space Wing, Space and Missile Systems Center, Navy and ULA’s close partnership and dedicated teamwork,” said Brig. Gen. Wayne Monteith, 45th Space Wing commander and mission Launch Decision Authority. “We continue our unwavering focus on mission success and guaranteeing assured access to space for our nation, while showcasing why the 45th Space Wing is the ‘World's Premiere Gateway to Space.’”
-
Centaur MES-3 should occur at 17:19 UTC (1:19 PM EDT).
Centaur MECO-3 should occur 58 seconds after MES-3.
Spacecraft separation should occur at 17:23 UTC (1:23 PM EDT).
-
1. I got about 4:30 from the launch replay video--ignition at 0:56, cutoff at 5:26 (not totally accurate due to commentator delay.) The launch aritcle lists the burn as 4:25.6.
Atlas burns to depletion so no worries about a long burn there. I guess a really long burn could mean an underperforming powerhead on the engine and thereby gravity losses, but <5s is attributable to other variables.
-
4 minutes away from MES-3.
-
We have Centaur MES-3. RL-10C-1 is up and running.
-
Centaur MECO-3. The powered portion of the MUOS 5 mission is complete.
-
Spacecraft sep should be in about 2 and a half minutes.
-
MUOS 5 separation. Congrats to the U.S. Navy and United Launch Alliance on the 63rd Atlas V launch; the 62nd successful mission since 2002.
-
MUOS 5 separation. Congrats to the U.S. Navy and United Launch Alliance on the 63rd Atlas V launch; the 62nd successful mission since 2002.
Now awaiting for Centaur's CCAM and MES-4 depletion burn to its graveyard orbit.
-
MUOS 5 separation. Congrats to the U.S. Navy and United Launch Alliance on the 63rd Atlas V launch; the 62nd successful mission since 2002.
Now awaiting for Centaur's CCAM and MES-4 depletion burn to its graveyard orbit.
I forgot this event; my apologies.
-
Congrats to ULA and the U.S. Navy, I enjoyed the updated coverage with the info banner and polling board, and of course the Youtube option. Seems almost everyone has gone Youtube these days except Arianespace (yes, that's a hint).
-
Congrats to ULA's Atlas & Centaur teams, US Navy, LM, AJR and other for the successful launch and deployment.
8)
-
According to today's updated NSF US launch thread (https://forum.nasaspaceflight.com/index.php?topic=8184.msg1552764#msg1552764) and Gunter's Space Page (http://space.skyrocket.de/doc_lau/atlas-5.htm), the next time we'll see an Atlas V 551 launch is from the Cape in mid-2017, with AFSPC 11 (whatever that is).
Thank you to the NSF crew who covered the launch for this thread!
Congratulations to the entire Atlas/Centaur/MUOS team!
-
Excellent work everyone and congrats to ULA and the US Navy!
Below are the press release, launch photo and caption. Additional photo + video posted here: http://www.ulalaunch.com/file-library.aspx
Cape Canaveral Air Force Station, Fla. (June 24, 2016) – A United Launch Alliance (ULA) Atlas V rocket carrying the MUOS-5 mission lifts off from Space Launch Complex-41 at 10:30 a.m. EDT.
Photo by United Launch Alliance
cid:[email protected]
United Launch Alliance Successfully Launches MUOS-5 Satellite for the U.S Air Force and U.S. Navy
MUOS-5 completes the five-satellite constellation and acts as an on-orbit spare
Cape Canaveral Air Force Station, Fla., (June 24, 2016) – A United Launch Alliance (ULA) Atlas V rocket successfully launched the MUOS-5 satellite for the U.S. Navy. The rocket lifted off from Space Launch Complex-41 June 24 at 10:30 a.m. EDT.
MUOS-5 is the final satellite in the five-satellite constellation, which provides warfighters with significantly improved and assured communications worldwide.
“We are honored to deliver the final satellite in the MUOS constellation for the U.S. Navy,” said Laura Maginnis, ULA vice president, Custom Services. “Congratulations to our navy, air force and Lockheed Martin mission partners on yet another successful launch that provides our warfighters with enhanced communications capabilities to safely and effectively conduct their missions around the globe.”
The mission was ULA’s fifth launch in 2016 and 108th launch since the company formed in 2006. MUOS-5 was the seventh mission to be launched aboard an Atlas V Evolved Expendable Launch Vehicle (EELV) 551 configuration vehicle, which includes a 5-meter diameter payload fairing and five solid rocket boosters. The Atlas booster for this mission was powered by the RD AMROSS RD-180 engine and the Centaur upper stage was powered by the Aerojet Rocketdyne RL10C-1 engine.
“I am so proud of the team for all their hard work and commitment to 100 percent mission success,” Maginnis said. “It is amazing to deliver our second national security payload from the Cape in just two weeks. I know this success is due to our amazing people who make the remarkable look routine.”
ULA's next launch is the Atlas V NROL-61 mission for the National Reconnaissance Office, scheduled for July 28 from Space Launch Complex-41 at Cape Canaveral Air Force Station, Florida.
The EELV program was established by the U.S. Air Force to provide assured access to space for Department of Defense and other government payloads. The commercially developed EELV program supports the full range of government mission requirements, while delivering on schedule and providing significant cost savings over the heritage launch systems.
With more than a century of combined heritage, United Launch Alliance is the nation’s most experienced and reliable launch service provider. ULA has successfully delivered more than 100 satellites to orbit that provide critical capabilities for troops in the field, aid meteorologists in tracking severe weather, enable personal device-based GPS navigation and unlock the mysteries of our solar system.
For more information on ULA, visit the ULA website at www.ulalaunch.com, or call the ULA Launch Hotline at 1-877-ULA-4321 (852-4321). Join the conversation at www.facebook.com/ulalaunch, twitter.com/ulalaunch and instagram.com/ulalaunch.
-
ULA pics.
-
-
New fabric acoustical protection being used inside the fairings now for more clearance and protection.
Hey my question made the cut! 8)
Great launch.
-
Congratulations to ULA & partners on a perfect launch!
That 551 does get off the pad in a hurry, doesn't it? Lovely to watch.
-
Congratulations to ULA & partners on a perfect launch!
That 551 does get off the pad in a hurry, doesn't it? Lovely to watch.
Compared to the 401, it seems to just leap off the pad.
My congrats as well!
-
I captured something that seems interesting - one of solids barfed a large piece of unburned fuel. Is this normal?
-
I captured something that seems interesting - one of solids barfed a large piece of unburned fuel. Is this normal?
Yes. The STS SRBs did it too.
-
Congrats to ULA and go Navy! :)
-
Atlas V MUOS-5 Launch Highlights
UnitedLaunchAlliance
Published on Jun 24, 2016
https://youtu.be/adb6FQwDnEw?t=001
https://youtu.be/adb6FQwDnEw
-
Atlas V MUOS-5 Rocket Cam
UnitedLaunchAlliance
Published on Jun 24, 2016
https://youtu.be/V_ign_djMm8?t=001
https://youtu.be/V_ign_djMm8
-
Atlas V MUOS-5 Rocket Cam
UnitedLaunchAlliance
Published on Jun 24, 2016
https://www.youtube.com/watch?v=V_ign_djMm8?t=001
https://www.youtube.com/watch?v=V_ign_djMm8
That solar wing radiator (or was it the photovoltaic panel itself) on the right definitely felt the fairing jettisoning.
-
Congratulations to ULA, LM, Navy and the range on another picture perfect launch.
-
Congrats to ULA .
8)
-
I captured something that seems interesting - one of solids barfed a large piece of unburned fuel. Is this normal?
Yes. The STS SRBs did it too.
Check out this big chunk that came out of Discovery's solids at 1:19:
https://www.youtube.com/watch?v=wqERz1IW7MQ
-
Congratulations to ULA and USN for the successful launch! I didn't see a press kit for this launch. Here's a one page flyer from ULA's website.
-
MUOS-5 Mobile User Objective System - 06-24-2016
USLaunchReport
Published on Jun 24, 2016
Muos-5 completes the high tech secure worldwide, pole to pole communications system for the entire US Military. Works in conjunction with four huge ground stations Australia, Hawaii, Sicily and Virginia.
https://youtu.be/i1rb-QcXMqk?t=001
https://youtu.be/i1rb-QcXMqk
-
No orbit details, even for the Centaur...
41622 MUOS 5 2016-041A PAYLOAD
41623 ATLAS 5 CENTAUR R/B 2016-041B ROCKET BODY
-
You need to go here for the orbit details:
http://www.satobs.org/seesat/Jun-2016/0121.html
-
For those who may want to try to catch the Centaur venting http://www.satobs.org/seesat/Jun-2016/0097.html
The same observer who found Mentor 7 (with help from veteran observers) photographed venting and the payload. http://sattrackcam.blogspot.nl/2016/06/muos-5-gto-insertion-and-centaur-fuel.html
-
1. I got about 4:30 from the launch replay video--ignition at 0:56, cutoff at 5:26 (not totally accurate due to commentator delay.) The launch aritcle lists the burn as 4:25.6.
Atlas burns to depletion so no worries about a long burn there. I guess a really long burn could mean an underperforming powerhead on the engine and thereby gravity losses, but <5s is attributable to other variables.
The burn duration was < 0.25 sec of pre-flight prediction. As I mentioned in a previous post (in some other thread I can't find), the duration itself doesn't reveal much about performance. You could have high thrust and high flowrates (nominal ISP), resulting in an earlier BECO, or you could have nominal thrust and high flow rates (lower ISP), resulting in an earlier BECO. One good, one bad.
A 3-sigma high or low propellant load can also affect BECO time, as the stage burns to depletion. Really have to see the state vector at BECO.
-
Atlas V MUOS-5 Launch Compilation Remote Pad And Press Site Video
Video Credit: Melanie Lee / Matthew Travis / Zero-G News
Published on Jul 1, 2016
Atlas V MUOS-5 Launch Compilation Remote Pad And Press Site Video
https://youtu.be/SKyGvojVLv0?t=001
https://youtu.be/SKyGvojVLv0
-
Amateur observers may have found the payload on the way to it's final orbit. http://www.satobs.org/seesat/Jul-2016/0014.html
-
http://spaceflightnow.com/2016/07/08/navys-new-muos-5-communications-satellite-hits-snag-in-space/
-
Shades of the AEHF failure? Didn't it also have a Japanese IHI supplied motor?
-
MUOS and AEHF are both on an LM bus, right?
-
http://www.navy.mil/submit/display.asp?story_id=95601
Story Number: NNS160708-18Release Date: 7/8/2016 2:27:00 PM
A A A Email this story to a friend Print this story
From Space and Naval Warfare Systems Command Public Affairs
SAN DIEGO (NNS) -- The fifth Mobile User Objective System satellite, which successfully launched aboard a United Launch Alliance Atlas 5 on June 24, was projected to reach its geosynchronous orbit and enter its test location 22,000 miles above Hawaii by July 3.
The satellite experienced an anomaly that required the transfer maneuver to be temporarily halted.
The Navy's Program Executive Office for Space Systems has reconfigured the satellite from orbital transfer into a stabilized, safe intermediate orbit to allow the MUOS team to evaluate the situation and determine options for proceeding.
MUOS-5 was launched as an on-orbit spare to provide immediate redundancy to the MUOS constellation, which is performing nominally. MUOS-5 is an on-orbit spare, and delay in reaching its test location will have no impact upon current legacy or Wideband Code Division Multiple Access satellite communications operations.
MUOS-1 through MUOS-4 are now in orbit and supporting operations via their legacy payloads that provide ultra high frequency satellite communications for the Department of Defense.
The Navy's Program Executive Office for Space Systems, located at the Space and Naval Warfare Systems Command in San Diego, is responsible for the MUOS program.
For more information, visit http://www.public.navy.mil/spawar/PEOSpaceSystems.
For more news from Space and Naval Warfare Systems Command, visit http://www.navy.mil/local/spawar.
For more information, visit http://www.navy.mil, http://www.facebook.com/usnavy, or http://www.twitter.com/usnavy.
-
The white orbit is the ~15250 x 35700 km, 9.8 degree inclined GTO orbit in which Paul Camilleri and me have observed the satellite over the period July 3-9. i.e. this is the orbit it is currently stranded in.
The red orbit is the initial insertion orbit from June 24. The grey orbit is the sunsynchronous geosynchronous (sorry, I was tired...) orbit it was aimed for.
(http://i19.photobucket.com/albums/b176/marcoaliaslama/satellites/MUOS5_insert_GTOstranded_GEO_polar_anot_zpscnowj9gy.jpg)
(http://i19.photobucket.com/albums/b176/marcoaliaslama/satellites/MUOS5_insert_GTOstranded_GEO_oblique_anot_zpsdg4xveqw.jpg)
-
Is it a possibility that the reason of the apogee propulsion failure might link to the soldering defect that shuffled it two launches behind schedule?
(MUOS 5 is known as SV-3)
-
Is it a possibility that the reason of the apogee propulsion failure might link to the soldering defect that shuffled it two launches behind schedule?
(MUOS 5 is known as SV-3)
Without any information on the nature of the issue, it is only speculation.
-
Is it a possibility that the reason of the apogee propulsion failure might link to the soldering defect that shuffled it two launches behind schedule?
(MUOS 5 is known as SV-3)
Unlikely, though anomalies on govt satellites are classified. Still I don't see much overlap between the repaired item and the propulsion system.
The soldering issue was discovered last spring during thermal vacuum testing on a component of the MUOS legacy UHF payload provided by Boeing Space and Intelligence Systems of El Segundo, Calif. Boeing, which built the Navy’s earlier-generation UHF Follow-On mobile communications satellites, is a subcontractor to Lockheed Martin on MUOS. - See more at: http://spacenews.com/39833bad-soldering-pushes-3rd-muos-satellite-toward-end-of-the-launch-queue/#sthash.AcQnqiBh.dpuf
-
<snip> though anomalies on govt satellites are classified. <snip>
Not always, they where pretty open after the fact about what happened to AEHF 1 (USA 214). If it is something related to the non-classified nature of the satellite. I think they will eventually release the cause with some level of detail.
-
From Mike Gruss on Twitter:
"Navy: MUOS-5 "experienced a failure of the orbit raising propulsion system." DoD is considering alternate orbit adjustment options."
Ouch.
-
There was also this from AmericaSpace:
In an unrelated, important military space development, AmericaSpace has also learned exclusively that the Navy/Lockheed Martin Mobile Objective User System MUOS-5 communications spacecraft has begun climbing, after earlier being stuck 12,000 miles below its intended geosynchronous orbit checkout location over the Pacific Ocean.
The problem, likely involving propulsion and possibly control as well, occurred when the 7-ton spacecraft was halfway up its planned nine-day transfer to geosynchronous orbit following launch from Cape Canaveral on an Atlas-V on June 24 (see AmericaSpace report June 25).
Navy spokesman Steve Davis at the Space and Naval Warfare Systems Command in San Diego said the Navy is not yet ready to release details on the problem.
Sources told AmericaSpace, however, that an initial maneuver this month was able to move the spacecraft 25 miles higher, brightening hopes that the $611 million satellite can be eventually elevated to geosynchronous orbit even if it has to inch its way up.
http://www.americaspace.com/?p=94629
I believe that was posted on July 27, but I'm not 100% sure. I'm not up on the satellite tracking so I'm not sure if that slight raise would be noticeable to amateur observers.
-
I'm not up on the satellite tracking so I'm not sure if that slight raise would be noticeable to amateur observers.
Latest amateur orbit confirms this, period raised about 3 min.
-
U.S. Navy narrows MUOS-5 problem to orbit raising propulsion system
But in an Aug. 2 statement, the Navy said the satellite “experienced a failure of the orbit raising propulsion system,” five days into a 10-day climb, halting the transfer maneuver that would push the satellite from its initial elliptical launch orbit to geosynchronous orbit.
As a result, the Navy is “considering alternate orbit adjustment options, calculating mission impact and investigating all options before proceeding,” said Steven Davis, a spokesman for Space and Naval Warfare Systems Command.
“The MUOS 5 satellite is currently stable, safe and under positive control,” he said.
http://spacenews.com/u-s-navy-narrows-muos-5-problem-to-orbit-raising-propulsion-system/
-
I'm not up on the satellite tracking so I'm not sure if that slight raise would be noticeable to amateur observers.
The effect of even a small maneuver will increase with time, so it will become noticeable at some point.
-
Spaceflightnow article: http://spaceflightnow.com/2016/08/02/navy-looks-for-plan-b-to-salvage-its-newest-communications-satellite/
But it appears the satellite has performed some orbit-raising in recent days, albeit tiny compared to large-scale maneuvers. The Navy has not confirmed any movements, but hobbyists keeping tabs on the stricken satellite have seen the tell-tale signs.
“When Scott Tilley observed MUOS 5 on July 21 near 11:00 UTC, it was still in the orbit in which it had been stranded by the propulsion system failure on June 29. When he next observed it, on July 30 at 10:00 UTC, it was nearly 17 minutes late relative the orbit it had been in on July 21. That is an indication that it made one or more maneuvers in the interim. The orbit change probably was not large. A precise determination is pending further observations,” said Ted Molczan, a respected satellite observer.
...
With the 100-pound-thrust main engine now out of commission, ground controllers will look to the satellite’s small thrusters for saving the mission.
The craft is equipped with 18 monopropellant hydrazine thrusters designed for attitude control — a dozen 0.2-pound thrusters and six 5-pound thrusters.
...
The situation is reminiscent of the Air Force’s first Advanced Extremely High Frequency satellite that experienced a main propulsion system failure after launch due to a clogged fuel line. It was able to achieve geosynchronous orbit using its xenon-fed electric thrusters with no reduction to mission life.
But the MUOS satellites do not have a xenon propulsion system, only hydrazine.
-
Do the RCS thrusters share a common fuel tank with the main engine? Or would they have to sacrifice station-keeping propellent to get it to a usable orbit?
-
Do the RCS thrusters share a common fuel tank with the main engine? Or would they have to sacrifice station-keeping propellent to get it to a usable orbit?
I think that A2100 RCS uses monopropellant hydrazine while the liquid apogee engine burns hydrazine and N2O4. Something like this maybe. https://www.google.com/patents/US7762498
There's a chance they can reach GEO, but I suspect it will cost a lot of the operational life. They need another 600-700 ish m/s delta/v, maybe more. That's probably a big chunk of the planned station keeping delta-v budget. This all assumes that the problem isn't pressurization, which could be common to both systems.
- Ed Kyle
-
Do the RCS thrusters share a common fuel tank with the main engine? Or would they have to sacrifice station-keeping propellent to get it to a usable orbit?
Also:
Is the main engine mono-propellant or bi-propellant? It's typical for ISP reason to use a bi-propellant engine for the GTO to GSO transfer. I believe AEHF-1 used a similar engine from IHI which was bi-propellant (Hydrazine and Nitrogen Tetroxide).
If that is the case, you not only take an ISP hit because of the smaller engines, but also don't get the bi-propellant ISP benefit and have the dead weight of the Nitrogen Tetroxide you can not use. They will have to lug the Nitrogen Tetroxide all the way up hill to GSO.
So the question now becomes how many years will getting to GSO take off the satellites life?
-
Ed, you beat me to it...
-
Question based on Ed's patent posting. It looks like the apogee engine is pump fed vs. pressure fed.
So this brings up a few questions:
-Could it be a failed pump
-Pump verses pressure fed in this case should lead to a significant ISP hit
-It looks like the pumps are electronically powered. Is that a first (for operational rocket engines)?
-Blown breaker in the pump controller? Or other electrical problem?
Not to be morbid, but on such a complex system the reason behind this could be very interesting.
-
Question based on Ed's patent posting. It looks like the apogee engine is pump fed vs. pressure fed.
So this brings up a few questions:
-Could it be a failed pump
-Pump verses pressure fed in this case should lead to a significant ISP hit
-It looks like the pumps are electronically powered. Is that a first (for operational rocket engines)?
-Blown breaker in the pump controller? Or other electrical problem?
Not to be morbid, but on such a complex system the reason behind this could be very interesting.
Ironically, the patent touts the advantage of being able to test the pumps during payload integration...but there are plenty of other potential culprits too.
-
Would it be normal for a spacecraft to have a share hydrazine tank, and a smaller oxidiser tank solely for the biprop engine? Or is it more likely to be two completely separate systems (different pressurisation requirements might point to this?)
-
Both AEHF and MUOS had orbit raising propulsion anomalies. And it was in 25% of the cases. I'm surprised because we don't usually see those propulsion failures on commercial satellites. Thus, I'm very surprised to see this level of problems on ultra expensive and ultra n-tuple checked programs. Is this just really bad luck on LM side?
-
This satellite would be a prime candidate for OA new satellite servicing satellites. The first version of these should be ready by 2020 and are designed to latch onto a satellite and provide station keeping.
-
https://en.wikipedia.org/wiki/Lockheed_Martin_A2100
http://aviationweek.com/awin/arc-apogee-engine-boosts-two-lockheed-martin-satellites
https://en.wikipedia.org/wiki/LEROS
(no pumps)
Common hydrazine tank for boost and stationkeeping. (this is becoming more common)
-
I'm not up on the satellite tracking so I'm not sure if that slight raise would be noticeable to amateur observers.
Latest amateur orbit confirms this, period raised about 3 min.
Orbit period was previously 943 minutes, I checked the n2yo tracker today and it now says 955 minutes.
http://www.n2yo.com/?s=41622
-
Updated Orbital Parameters as of 17 minutes ago are:
The following elements have been compiled and based on observations by Scott Tilley, Peter Wakelin and Brad Young:
MUOS 5 15776 X 35698 km
1 41622U 16041A 16229.03465278 .00000000 00000-0 00000-0 0 05
2 41622 9.7702 322.7056 3101628 182.2968 197.2306 1.50856547 03
Arc 20160812.65-0816.03 WRMS resid 0.002 totl 0.001 xtrk
Ted Molczan
-
The press release used to write the story above. http://www.peterson.af.mil/News/Article-Display/Article/918082/neighborhood-watch-supports-navy-operations
‘Neighborhood Watch’ supports Navy operations
By Jennifer Thibault, 50th Space Wing Public Affairs / Published August 17, 2016
Geosynchronous Space Situational Awareness Program artist rendering. Air Force Space Command’s “Neighborhood Watch” Satellites, the Geosynchronous Space Situational Awareness Program, recently responded to the Navy’s request for help with a satellite of its own.
SCHRIEVER AIR FORCE BASE, Colo. - Air Force Space Command’s “Neighborhood Watch” Satellites, the Geosynchronous Space Situational Awareness Program, recently responded to the Navy’s request for help with a satellite of its own.
The Joint Functional Component Command for Space officially tasked the 1st Space Operations Squadron to support Navy’s ongoing Mobile User Objective System-5 anomaly effort after the satellite failed to reach its target geosynchronous orbit on July 3.
Anomaly resolution in space is challenging for many reasons, one being it’s difficult to see what’s going on with the satellite. Traditionally, engineers, analysts and operators comb through telemetry to come up with possible reasons for the anomaly, however in cases like this GSSAP is able to provide Electro Optical Space Situational Awareness on the status of space objects to include location, orbit and size of the space object.
GSSAP crews conduct Rendezvous and Proximity Operations to get the best possible vantage point for collecting SSA data when requested. In this case, the mission was to help rescue MUOS-5.
Once tasked, 1 SOPS mission planning cell began the deliberate, customized mission planning to determine how to execute the operation and maximize the probability for success. The satellites’ differing orbits and the various forces at play, including astrodynamics, reminded crewmembers that success was not inevitable.
Capt. Barbara Dyer, 1 SOPS mission commander, led the crew that accomplished the command and control operations to collect MUOS-5 imagery on her 10th shift.
“I knew we were prepared. We had completed the rehearsal of concept for the unique mission,” she said. “We recognized the newness of what we’re doing will drive new expectations.”
Second Lt. Nathan Paddock is the satellite vehicle operator who executed the C2 for the operations.
“There were a lot of different people on the operations floor during the shift,” he said. “Senior leadership was there encouraging us and reminding us that this was something very important. I am new to the Air Force and the job, but knowing leadership trusted me and expected excellence is something that’s unique to this work.”
The audience and mission importance added to the pressure to achieve success but that didn’t deter Paddock.
“I liked it. I thrive under pressure,” he said. “The crew engineers gave us a lot of support and helped me stay calm and relaxed. I know they had my back.”
The crew conducted SSA missions with other 1 SOPS assets, like the Space Based Space Surveillance system, in preparing for and during the mission.
While planning and operations were conducted at Schriever, another aspect of this unique mission occurred at Point Mugu, California.
“Due to the complexity of the program we wanted someone on site to provide context to Navy leadership, explain our operations, facilitate information sharing and ensure there was robust coordination during the operations,” said Lt Col Casey Beard, 1 SOPS commander.
The squadron’s mission planning cell chief, Capt. Brett Kasischke, was just up the road at Vandenberg AFB, California, to participate in an exercise. He capitalized on the opportunity and extended his stay in California.
“I quickly immersed myself into the mission’s requirements and served as an intermediary; I ensured data was sent at appropriate times as well as supported the team back at Schriever,” Kasischke said.
The mission’s full impact is yet to be determined, but there are successes already to be celebrated.
“I am proud of the team effort across the community,” said Beard. “From our crew here at Schriever to the Space and Missile System Center, the Joint Functional Component Command for Space, the Joint Space Operations Center, our Navy counterparts at Point Magu and the contractors who dedicated 800 hours to mission planning, it was a true team effort and couldn’t have happened without everyone coming together.”
“The detailed planning was an outstanding learning event for our crews. Our tactics, techniques and procedures were refined and, when called upon to assist with another satellite anomaly, we will be ready. We have more confidence in our teams and our training programs,” said Kasischke. “The dynamic nature of the mission and complexity of operations, it’s what we’re here to do and it’s going to shape future operations.”
-
Oops, they misspelled Pt. Mugu. :-X
-
MUOS 5 is in an slightly inclined geostationary transfer orbit.
The 2 operational GSSAP satellites are in geosynchronous orbits.
My deduction: The GSSAP satellites were moved, and maybe their orbits temporarily inclined?, so that their geocentric longitude matched the apogee of MUOS 5. This would allow documentation imagery.
If both GSSAP satellites were used, they could be spaced in geosynchronous orbit to match geocentric longitudes of successive MUOS 5 apogees. MUOS 5 is currently completing about 1.5 orbital revolutions/day (from Heavens-above.com http://www.heavens-above.com/orbit.aspx?satid=41622&).
MUOS 5's relative velocity would be lowest at apogee (Kepler's laws), so that would make GSSAP imagery attempts easier?
This work may explain why MUOS 5's orbit hasn't changed much in recent days--to allow the imagery documentation.
Question for the amateur satellite observers: Are there any conjunctions of MUOS 5 and either of the operational GSSAPs?
Heavens-above.com has orbital elements for USA 253 as of October 9, 2015, and for USA 254 as of August 12, 2016. (GSSAP 1 & 2)
http://www.heavens-above.com/orbit.aspx?satid=40099&
http://www.heavens-above.com/orbit.aspx?satid=40100&
-
Peter B. de Selding @pbdes 3h3 hours ago
Sat builders studying possible link between thruster failures on US military MUOS & Intelsat IS-33 sats despite different thruster builders.
-
Peter B. de Selding @pbdes 3h3 hours ago
Sat builders studying possible link between thruster failures on US military MUOS & Intelsat IS-33 sats despite different thruster builders.
Both use Moog valves?
-
Slow progress is being made based on the latest amateur observations http://www.satobs.org/seesat/Sep-2016/0096.html
-
Peter B. de Selding @pbdes 3h3 hours ago
Sat builders studying possible link between thruster failures on US military MUOS & Intelsat IS-33 sats despite different thruster builders.
Both use Moog valves?
Yes, that is what i understand
-
Slow progress is being made based on the latest amateur observations http://www.satobs.org/seesat/Sep-2016/0096.html
Thanks for the update, I've been waiting on this for about a week now.
-
Gesundheit
-
Applicable part of a post in the SBIRS GEO-3 thread copied over for reference...
Fueling of the satellite and the launch, originally scheduled for Oct. 3, was delayed on Sep. 10 by Lt Gen Samuel Greaves, SMC commander and Air Force Program Executive Officer for Space (PEO/Space) to give the SBIRS government/contractor engineering team time to investigate a potential parts issue discovered on two other non-SBIRS satellites. A preliminary review of the data suggested a possible issue with the liquid apogee engines. A Liquid Apogee Engine is used by the SBIRS satellite to provide the thrust required to raise the satellite to the proper orbit after the spacecraft has been released from the launch vehicle. Earlier this month, a non-Lockheed Martin commercial satellite experienced a similar anomaly to the July MUOS-5 event. The Air Force is working to understand the commonality between the two anomalous engines and the SBIRS design. The SBIRS satellite remains safe at the launch base.
To date, the joint government and industry team has reviewed approximately 90% of the design, build, and test data from the anomalies. Additionally, all design similarities between the SBIRS liquid apogee engines and the anomalous engines have been fully documented and are understood. The team expects to complete the investigation within the next couple of weeks.
-
Period has been 955m for the last couple weeks. Today its changed to 984m.
http://www.n2yo.com/?s=41622
Up to 1038m now.
-
Is there current elements (apogee/perigee) ?
-
Is there current elements (apogee/perigee) ?
You can calculate SMA from the period.
Perigee Altitude = 2*SMA - 2*EarthRadius - ApogeeAltitude
http://orbitsimulator.com/gravity/articles/smaCalculator.html
-
Is there current elements (apogee/perigee) ?
You can calculate SMA from the period.
Perigee Altitude = 2*SMA - 2*EarthRadius - ApogeeAltitude
http://orbitsimulator.com/gravity/articles/smaCalculator.html
Sorry - I'm not a mathematician... :(
-
Is there current elements (apogee/perigee) ?
You can calculate SMA from the period.
Perigee Altitude = 2*SMA - 2*EarthRadius - ApogeeAltitude
http://orbitsimulator.com/gravity/articles/smaCalculator.html
Sorry - I'm not a mathematician... :(
PALT = 2*(33959.4 km) - 2*(6378.1 km) - 35786 km = 19377 km
19377 x 35786 km
or
10463 x 19323 nmi
-
Heavens Above will also give you data, not sure if n2yo and HA update with the same data.
http://heavens-above.com/orbit.aspx?satid=41622&lat=0&lng=0&loc=Unspecified&alt=0&tz=UCT
-
Thanks !!
-
According to the amateur observers the orbit is now 28031 x 36688 km
http://www.satobs.org/seesat/Oct-2016/0034.html
-
Orbit 30483 x 36788 km (9.10.2016)
-
Orbit 30483 x 36788 km (9.10.2016)
today 34764 x 36017 km
http://heavens-above.com/orbit.aspx?satid=41622&lat=0&lng=0&loc=Unspecified&alt=0&tz=UCT
-
I would assume they are using the maneuvering thrusters to raise its orbit then? What impact will this have on life expectancy given they are only mono propellant versus the main engine is bi-propellant. I would think this would exhaust a considerable amount of the fuel needed for station keeping.
Perhaps they plan to put it in service this way and later attempt to use it as an experiment for refueling?
-
Orbit 30483 x 36788 km (9.10.2016)
today 34764 x 36017 km
http://heavens-above.com/orbit.aspx?satid=41622&lat=0&lng=0&loc=Unspecified&alt=0&tz=UCT
update 20.10.16:
9,68° 34551 x 36665 km
-
Moved again since yesterday:
Period (minutes)
943
955 12-Aug
984 18-Sep
1038 28-Sep
1265 10-Oct
1328 12-Oct (today)
and now 1427 !
http://www.n2yo.com/?s=41622
-
Moved again since yesterday:
Period (minutes)
943
955 12-Aug
984 18-Sep
1038 28-Sep
1265 10-Oct
1328 12-Oct (today)
and now 1427 !
http://www.n2yo.com/?s=41622
At least MUOS 5 is getting to where it needs to be, although with the exception of low propellant.
-
MUOS 5 will have a shorter lifespan :(
-
MUOS 5 will have a shorter lifespan :(
I know. Ever since the main propulsion system failed.
At least we have the minimum amount of four MUOS satellites in their correct orbits.
-
MUOS 5 will have a shorter lifespan :(
I know. Ever since the main propulsion system failed.
At least we have the minimum amount of four MUOS satellites in their correct orbits.
I wouldn't be surprised if MUOS-5 is switched from Spare to Primary status since its life will now be shorter than the others.
-
http://heavens-above.com/orbit.aspx?satid=41622&lat=0&lng=0&loc=Unspecified&alt=0&tz=UCT
inclination: 9.6745°
perigee height: 34810 km
apogee height: 36764 km
period about 1436 min
inclination can be corrected in the future
(inclination MUOS 1 to MUOS 4 4...5°)
-
Ted Molczan estimates the remaining propellant quantities aboard MUOS 5: http://www.satobs.org/seesat/Oct-2016/0139.html (http://www.satobs.org/seesat/Oct-2016/0139.html)
He considers it likely that MUOS 5 will stay at the Western stable libration point to minimize the need for station keeping maneuvers. He finds that in order to reach the current geosynchronous orbit at this libration point, the orbital inclination was not reduced to the typical 5 deg values, but instead was kept close to the 9.7 deg that the orbit was in after the liquid apogee engine failed.
-
http://www.satobs.org/seesat/Oct-2016/0148.html
I had a similar thought. Bring MUOS-5 into service until it exhausts its fuel...
-
From Space and Naval Warfare Systems Command Public Affairs
SAN DIEGO (NNS) -- The Navy's fifth Mobile User Objective System (MUOS) satellite has reached operational orbit and has successfully deployed its arrays and antennas.
On Oct. 22, the MUOS team raised the MUOS-5 satellite to an operationally-suitable orbit. The team completed a series of deployments of the satellite's solar arrays and antennas, with the last occurring successfully Oct. 30.
MUOS-5 launched June 24 from Cape Canaveral Air Force Station and experienced a failure of its orbit raising propulsion system that halted the satellite's transfer orbit maneuver to its geosynchronous test orbit. The MUOS team ensured the satellite remained stable, safe, and under positive control while it investigated the issue and examined options.
"We are very proud of the commitment our team members demonstrated," said Capt. Joe Kan, program manager for the Navy Communications Satellite Program Office. "Working together with industry, we were able to execute an alternative propulsion method to maneuver MUOS-5 to reach a position that is operationally suitable."
MUOS-5 is scheduled to begin on-orbit Nov. 3. It will complete the five-satellite MUOS constellation once on-orbit testing is complete.
"The system will undergo on-orbit testing before final acceptance of the system by the Navy and offering it up for operational use," said Cmdr. Jason Pratt, MUOS principal assistant program manager. "The satellite and its payloads will go through rigorous tests with our ground systems and terminals to make sure everything operates properly."
The MUOS system is designed to provide improved communications capabilities to users around the world, regardless of where they are in relation to a satellite. The MUOS constellation and associated ground network will provide 3G-like cellphone communications for the next decade and beyond.
The Navy's Program Executive Office for Space Systems, located at the Space and Naval Warfare Systems Command in San Diego, is responsible for the MUOS program.
For more information, visit http://www.navy.mil, http://www.facebook.com/usnavy, or http://www.twitter.com/usnavy.
For more news from Space and Naval Warfare Systems Command, visit http://www.navy.mil/local/spawar/ or http://www.public.navy.mil/spawar/PEOSpaceSystems/.
http://www.navy.mil/submit/display.asp?story_id=97520
-
MUOS-5 Secure Communications Satellite Reaches Orbit, Begins Pre-Operational Testing
4-Nov-2016 11:34 AM
SUNNYVALE, Calif. , Nov. 4, 2016 /PRNewswire/ -- The fifth Mobile User Objective System (MUOS) satellite built by Lockheed Martin (NYSE:LMT) for the U.S. Navy has reached orbit, successfully deployed its solar arrays and antennas, and is beginning pre-operational, on-orbit testing.
Originally launched from Cape Canaveral Air Force Station on June 24 , MUOS-5 experienced an anomaly with its orbit raising propulsion system on its way to geosynchronous orbit on June 29 . Out of caution, the Navy and Lockheed Martin engineering team immediately placed the satellite in a safe mode in transfer orbit as they investigated and examined their options.
"In the end, the Navy and Lockheed Martin engineering team were able to isolate the issue and develop a work-around using alternative propulsion," said Mark Woempner , director of Narrowband Communications Systems at Lockheed Martin . "Once we had a plan together, in early October we carefully re-started orbit raising maneuvers."
MUOS-5 completed orbit raising on Oct. 22 , and successfully deployed its solar arrays for power generation and its antennas for mission operations on Oct. 30 . The satellite will begin on-orbit testing before being turned over to the Navy for further testing and eventual commissioning into service.
For the Navy , MUOS-5 completes a network of orbiting satellites and relay ground stations that is revolutionizing secure communications for mobile military forces. Users with MUOS-capable terminals will be able to seamlessly connect beyond line-of-sight around the world and into the Global Information Grid, as well as into the Defense Switched Network. MUOS' capabilities include simultaneous, crystal-clear voice, video and mission data over a secure high-speed Internet Protocol-based system.
The MUOS network provides near-global coverage, including communications reach deep into polar regions. Once fully operational, the network will provide users with 16 times more communications capacity than the legacy system it will eventually replace.
The Navy's Program Executive Office for Space Systems and its Communications Satellite Program Office responsible for the MUOS program are based in San Diego . Lockheed Martin assembled and tested all five now-on-orbit MUOS satellites at its Sunnyvale, California , facility.
For additional MUOS information, photos and video visit: www.lockheedmartin.com/muos.
-
Well, I've done everything I need to do. Hopefully the rest of the rest of the team proves out an operational bird. This has been a wild ride.
-
News Release Issued: Apr 24, 2017 (12:26pm EDT)
U.S. Navy's Fifth Lockheed Martin-Built MUOS Satellite Now Supporting Troops with Ultra High Frequency Communications
MUOS-5 Completes Global Military Cellular Network As Spare For Next-Generation Capabilities
SUNNYVALE, Calif., April 24, 2017 /PRNewswire/ -- The fifth Lockheed Martin (NYSE-LMT)-built Mobile User Objective System (MUOS-5) satellite is now delivering secure, beyond-line-of-sight communications to troops with legacy Ultra High Frequency (UHF) radios.
The U.S. Navy, working with Army Forces Strategic Command, configured one of MUOS-5's two communications payloads – its legacy UHF payload – to provide additional support for the Navy's legacy UHF satellite communications mission. Today, narrowband UHF communications is used by every Combatant Command in aircraft, ships, submarines, ground vehicles, as well as by troops in the field and special operations.
Eventually, legacy narrowband UHF communications will transition to next generation Wideband Code Division Multiple Access (WCDMA) capabilities provided by MUOS. To facilitate that transition, MUOS was intentionally designed with two communications payloads.
"Each MUOS satellite can simultaneously support both new WCDMA waveform capabilities and legacy UHF satellite communications," explained Mark Woempner, director of Narrowband Communications Systems at Lockheed Martin. "With MUOS 1-4 already on orbit providing near global WCDMA coverage, MUOS-5 will actively support legacy UHF communications and serve as an on-orbit WCDMA spare."
MUOS-5 is the latest edition to a network of orbiting satellites and relay ground stations that is revolutionizing communications for mobile forces. Users with new MUOS terminals will be able to seamlessly connect beyond line-of-sight around the world and into the Global Information Grid, as well as into the Defense Switched Network. MUOS' capabilities include simultaneous, crystal-clear voice, video and mission data over a secure high-speed Internet Protocol-based system.
More than 55,000 currently fielded radio terminals can be upgraded to be MUOS-compatible, with many of them requiring just a software upgrade.
Once fully operational, MUOS will provide users with more than 10 times the communications capacity of the legacy system it will replace. The network provides near-global coverage, including communications into polar regions. MUOS also has demonstrated successful communication of Integrated Broadcast Service (IBS) messages to in-flight test aircraft.
"The industry team for MUOS is an incredible partnership. Next for MUOS, we are laser-focused on bringing the complete system to full operational capability for the Navy," said Woempner. "Early combatant commander testing began in July 2016, and we have already received valuable user feedback and are working to rapidly incorporate their needs into the system."
MUOS-5 begins this transition after successful completing post-launch, on-orbit testing on January 19. The satellite completed orbit raising and successfully deployed its solar arrays and antennas for mission operations on Oct. 30, 2016.
Originally launched on June 24, 2016, MUOS-5 experienced an anomaly with its orbit raising propulsion system on its way to geosynchronous orbit. The Navy and Lockheed Martin engineering teams were able to isolate the issue and deliver MUOS to operational orbit using alternative propulsion.
The Navy's Program Executive Office for Space Systems and its Communications Satellite Program Office responsible for the MUOS program are based in San Diego, California. Lockheed Martin assembled and tested all five now-on-orbit MUOS satellites at its Sunnyvale, California, facility.
For additional MUOS information, photos and video visit: www.lockheedmartin.com/muos
-
U.S. Navy Accepts Fifth Lockheed Martin-Built MUOS Satellite for New Secure Global Military Cellular Network
MUOS-5 Supports Legacy UHF Comms; Serves As Spare For New Capabilities
NAVAL BASE VENTURA COUNTY, POINT MUGU, Calif., Nov. 16, 2017 /PRNewswire/ -- The U.S. Navy's Communications Satellite Program Office, PMW 146, and Lockheed Martin (NYSE: LMT) handed over full operational control of the fifth Mobile User Objective System (MUOS) satellite to the Naval Satellite Operations Center (NAVSOC).
The October 11 milestone followed the successful completion of the MUOS-5 satellite's on-orbit testing and delivery of all operational products needed to "fly" the satellite. In April, the Navy, working with Army Forces Strategic Command (ARSTRAT), configured one of MUOS-5's two communications payloads – its legacy Ultra High Frequency (UHF) payload – for testing.
The handover of this satellite to NAVSOC clears the final hurdle allowing for ARSTRAT to provide the payload's final configurations to support the Navy's legacy UHF satellite communications mission.
"Today, every Combatant Command in aircraft, ships, submarines, ground vehicles, as well as by troops in the field and special operations, rely upon secure, beyond-line-of-sight UHF satellite communications provided by the Navy," said Mark Woempner, Lockheed Martin's director for Narrowband Communications. "ARSTRAT's final configuration of MUOS-5's UHF legacy payload allows the satellite to fully support our military forces in these Combatant Commands."
Eventually, legacy narrowband UHF communications will transition to next generation Wideband Code Division Multiple Access (WCDMA) capabilities. To facilitate that transition, all five on-orbit MUOS satellites were intentionally designed with two communications payloads to support both Legacy UHF and WCDMA.
Early combatant commander testing of the on-orbit WCDMA payloads began in July 2016. The new MUOS capabilities will revolutionize communications for mobile forces with simultaneous, crystal-clear voice, video and mission data over a secure high-speed Internet Protocol-based system. Users with new MUOS terminals will be able to seamlessly connect beyond line-of-sight around the world and into the Global Information Grid, as well as into the Defense Switched Network, as part of the Navy's worldwide cellular network.
Once fully operational, the MUOS network of five on-orbit satellites and four relay ground stations will provide more than 10 times the communications capacity of the legacy UHF satellite system. MUOS' network already provides near-global coverage, including communications into polar regions. MUOS also has demonstrated successful communication of Integrated Broadcast Service (IBS) messages.
"We continue to receive great and constructive feedback on MUOS' capabilities as more users try it out. Similar to a civilian cellular phone service, upgrades to this new secure global military cellular network are ground-based and designed in an AGILE software development environment. We continue to make upgrades to the system based on user needs and look forward to bringing its full capabilities to our warfighters," Woempner said.
Today there are more than 55,000 radio terminals currently fielded that can be upgraded to be MUOS-compatible, with many of them requiring just a software upgrade.
The Navy's Program Executive Office for Space Systems and its Communications Satellite Program Office responsible for the MUOS program are based in San Diego, California. Lockheed Martin assembled and tested all five now-on-orbit MUOS satellites at its Sunnyvale, California, facility.
For additional MUOS information, photos and video visit: www.lockheedmartin.com/muos