NASASpaceFlight.com Forum
Commercial and US Government Launch Vehicles => ULA - Delta, Atlas, Vulcan => Topic started by: jacqmans on 07/26/2012 08:33 pm
-
Boeing Ships 3rd GPS IIF Satellite to Cape Canaveral for Launch
IIF series sustaining and modernizing US Air Force GPS constellation
EL SEGUNDO, Calif., July 25, 2012 -- Boeing [NYSE: BA] on July 9 shipped the third of 12 Global Positioning System (GPS) IIF satellites for the U.S. Air Force from the company's Satellite Development Center in El Segundo to Cape Canaveral Air Force Station, Fla., aboard a Boeing-built C-17 Globemaster III airlifter.
SVN-65 is scheduled to be launched in the fourth quarter of this year aboard a United Launch Alliance Delta IV rocket. It will join the first and second Boeing-built GPS IIF satellites, launched May 27, 2010, and July 16, 2011, to continue the sustainment and modernization of the GPS network.
"As each IIF satellite becomes operational, we continue the seamless transformation of the GPS constellation into an even more accurate, reliable and durable navigation resource for the U.S. military and the global civilian user community," said Craig Cooning, vice president and general manager of Boeing Space & Intelligence Systems. "Our efficient pulse-line manufacturing process, adapted from Boeing's commercial airplane production lines, also ensures that we deliver each spacecraft on time and on cost."
SVN-65 will now undergo preflight checkout, fueling and integration to prepare for the early October launch. When on orbit, it will be controlled by the Operational Control Segment, the GPS network’s ground control system. Developed by a Boeing-led team, the OCS entered service in 2007 and was turned over to the Air Force 50th Space Wing in April 2011.
GPS IIF features greater navigational accuracy through improvements in atomic clock technology, a more secure and jam-resistant signal for the military, and a protected, more precise, and interference-free civilian L5 signal for commercial aviation and search-and-rescue operations. Other enhancements to the IIF include an extended 12-year design life and a re-programmable on-orbit processor that can receive software uploads for improved system operation.
Of the remaining nine IIFs that Boeing is building for the Air Force, three are complete and in storage, and six are being assembled and tested.
-
I ran my GPS tracking simulator with it set to the scheduled launch window plus about 90 minutes. That is roughly the time GPS IIF-3 will arrive at the GPS constellation.
GPS Plane A satellites will be orbiting in the general area of space craft separation.
Plane A, Position1 is currently guarded by two GPS IIA satellites SV27 (PRN27) and SV39 (PRN09). They are showing their ages.
SV27 was launched way back on 9 September 1992! Although it's constantly one of the poorest performing satellites, it remains perfectly useful. I'm thinking it's to be replaced.
Evidently GPS IIF-3 refers to the order of launching but in the order of manufacture it will be SV65 because SV64 has been sidelined for additional work.
--- CHAS
-
The Delta IV booster that will launch GPS IIF-3 has arrived at the pad.
http://spaceflightnow.com/delta/d361/rollout.html
'Known as the GPS 2F-3 satellite, this newest spacecraft will take the place of the GPS 2A-21 bird that was launched by a Delta 2 rocket on June 26, 1993 and began its remarkably long-lasting service life on July 21, 1993.'
GPS 2A-21 (SV39) resides at Plane A1. It currently transmits PRN09.
--- CHAS
-
-
-
Is there information on what alternate launch dates would be possible if, just hypothetically, ULA yielded the range (to SpaceX) for Oct 5th?
-
-
In this image it appears some of the scaffolding around the solids (perhaps at their forward attach points?) has been moved away from the vehicle. Is that simply an indication the attachment/inspection is complete?
-
-
In this image it appears some of the scaffolding around the solids (perhaps at their forward attach points?) has been moved away from the vehicle. Is that simply an indication the attachment/inspection is complete?
There's a WDR scheduled for today. So that's why the MST has been retracted to the park position.
-
In this image it appears some of the scaffolding around the solids (perhaps at their forward attach points?) has been moved away from the vehicle. Is that simply an indication the attachment/inspection is complete?
WDR
-
-
just a 'shot in the dark' ;)
-
-
Can't determine if the satellite has been hoisted aboard the rocket. With only nine days to the currently scheduled launch, this should happen soon.
There's a GPS ground station at CCAFS with both monitoring and telecommand capabilities. I suspect there will be extensive end to end testing between the GPS operations center in Colorado and GPS IIF-3 atop the rocket before a readiness 'GO' to initiate a count down is authorized.
Meanwhile, a FCSTDV (velocity change) has been scheduled for the satellite (SVN39) to be replaced. Probably, it's being moved out of the way to be decommissioned and become a Plane A spare. It's still usable after 19 years on orbit!
--- CHAS
-
Can't determine if the satellite has been hoisted aboard the rocket. With only nine days to the currently scheduled launch, this should happen soon.
There's a GPS ground station at CCAFS with both monitoring and telecommand capabilities. I suspect there will be extensive end to end testing between the GPS operations center in Colorado and GPS IIF-3 atop the rocket before a readiness 'GO' to initiate a count down is authorized.
It is on top.
That testing was done before it is integrated with the launch vehicle.
-
A few photos of the GPS satellite encapusled and stacked on top, via ULA:
(see ULA's web photo gallery for more)
-
https://www.facebook.com/photo.php?pid=26203792&l=4678ca0343&id=482808580011
-
But where are the pics with Jim?
-
It's not a NASA payload, so I wouldn't cross my fingers on a Jim Photo Bomb.
-
ULA @ulalaunch
The ULA Launch Readiness Review is complete, and we are go for #GPSIIF3 launch! Thursday's launch window opens at 8:10 am EDT.
-
The mission patch. Arcturus is a commonly used navigation star so I suppose that's the tie-in.
--- CHAS
-
The mission patch. Arcturus is a commonly used navigation star so I suppose that's the tie-in.
--- CHAS
That isn't the mission patch, it is the processing/spacecraft patch.
This is the mission/launch patch
-
Restricted airspace map
-
More restricted airspace from NOTAMs
-
Mission booklet
-
Initial ground trace (from mission booklet)
-
3rd Boeing GPS IIF Satellite Ready for Oct. 4 Launch
SVN-65 to further enhance constellation's power, precision and capacity
CAPE CANAVERAL AIR FORCE STATION, Fla., Oct. 3, 2012 -- The third of 12 Global Positioning System (GPS) IIF satellites Boeing [NYSE: BA] is building for the U.S. Air Force is ready to make the GPS system even more accurate, reliable and secure after successfully completing final checkout for launch.
SVN-65 is scheduled to lift off from Cape Canaveral Air Force Station on Oct. 4 at 8:10 a.m. Eastern time aboard a United Launch Alliance Delta IV vehicle.
"As the GPS IIFs become operational, they are ensuring that the Air Force can meet the current and future needs of both military and civilian users," said Col. Bernie Gruber, director of the U.S. Air Force Space and Missile Systems Center's Global Positioning Systems Directorate.
GPS is a global utility providing highly accurate position, navigation and timing services to billions of people around the world. The GPS IIF satellites are sustaining and modernizing the network with a number of enhancements, including improved atomic clock technology, a more jam-resistant military signal and a protected and more powerful civilian signal. The satellites also feature a 12-year design life for long-term service and reduced operating costs.
"Boeing has worked alongside the Air Force for many years to continuously sustain and improve the GPS constellation," said Craig Cooning, vice president and general manager of Boeing Space & Intelligence Systems. "This new fleet of 12 GPS IIFs will form the core of the GPS constellation for the next decade."
SVN-65 was shipped to the Cape from El Segundo, Calif., on July 9 aboard a Boeing-built C-17 Globemaster III military transport. The satellite has undergone a series of prelaunch tests that validated its operational readiness, including its ability to communicate with the launch site and the Boeing-built Operational Control Segment.
Of the remaining nine GPS IIFs, three are completed and ready to be scheduled for launch as needed while six are in production. The Boeing Satellite Development Center in El Segundo uses an efficient "pulse line" manufacturing process adapted from Boeing commercial airplane assembly techniques.
-
Moving for live coverage now, given it'll be early US time.
-
-
The mobile surface tower has been rolled back.
-
The mission patch. Arcturus is a commonly used navigation star so I suppose that's the tie-in.
--- CHAS
That isn't the mission patch, it is the processing/spacecraft patch.
This is the mission/launch patch
They ought to put the shark's mouth decal on the fairing for these like they did with the D-IIs...
-
The mission patch. Arcturus is a commonly used navigation star so I suppose that's the tie-in.
--- CHAS
That isn't the mission patch, it is the processing/spacecraft patch.
This is the mission/launch patch
They ought to put the shark's mouth decal on the fairing for these like they did with the D-IIs...
Jim would vomit in front of you then..... LOL :P (which I agree: the decal's stupid)
My bad. Guess I didn't realize it's a different world and set of circumstances.
Another snarky reply.
Don't juxtapose unrelated situations and disparage those who point out the irrelevance of the comparison. But, whatever. I'll be on the lookout for "Strawberry B***h" or "Marge" or "The Dragon And His Tail" on a Delta-IV heavy.
Hey, didn't the Delta II that blew up just after launch back in '97 have a shark mouth on the shroud??? ;D
yes it did, which I think is stupid.
Here is something on patches.
http://www.thespacereview.com/article/1033/1
http://www.thespacereview.com/article/1197/1
-
The mission patch. Arcturus is a commonly used navigation star so I suppose that's the tie-in.
GPS launch pays tribute to fallen captain (http://www.schriever.af.mil/news/story.asp?id=123320905)
The launch will also pay tribute to a Capt. Vivian Elmo, former 19th Space Operations Squadron member, who died during a two-car accident Aug. 3, 2011, on Highway 94.
For each launch mission, SMC develops a launch patch which represents significant events or details of the launch story. The mission patch for this IIF satellite launch pays tribute to Elmo, with the launch patch depicting the navigation star, Arcturus, as a sunflower, Elmo's favorite flower.
"Arcturus is the brightest star in the northern celestial hemisphere and the dominant star in the constellation Boötes," Gostomski said. "Prehistoric Polynesian navigators used the star for traveling across the seas and knew Arcturus as the 'Star of Joy.'"
Gostomski said it's fitting that Elmo receives this kind of tribute. Elmo worked as the 50th Space Wing satellite vehicle operator director for GPS IIF-2, which successfully launched July 16, 2011. Elmo also played a critical role in the first successful IIF-1 launch May 27, 2010. Outstanding team performance and efficient approaches for enhancing mission capability displayed throughout the launch preparation process earned Elmo and her team the 2010 Chief of Staff Team Excellence Award.
-
ULA:
Photos and a caption of the Delta IV rollout this evening. First motion of the tower was at 10:13 p.m.
Cape Canaveral Air Force Station, Fla. (Oct. 3, 2012) - A United Launch Alliance Delta IV stands ready for launch at Space Launch Complex-37 with the Air Force’s Global Positioning System (GPS) IIF-3 payload. Launch is set for Thursday, Oct. 4 at 8:10 a.m. EDT. GPS IIF-3 is the third in a series of next generation GPS satellites and will join a worldwide timing and navigation system utilizing 24 satellites in six different planes, with a minimum of four satellites per plane positioned in orbit approximately 11,000 miles above the earths’ surface.
Photo by Pat Corkery, United Launch Alliance
-
And here's William Graham's launch preview/overview!
http://www.nasaspaceflight.com/2012/10/ula-delta-iv-launch-gpsiif-3-from-cape-canaveral/
-
One hour to the ULA webcast, here:
http://www.ulalaunch.com/site/pages/Webcast.shtml
I know it's early in the States, so I've got this covered via my new - and rather cool - flash screenshot program, but if anyone wants to chip in, please do!
-
-
One hour to the ULA webcast, here:
http://www.ulalaunch.com/site/pages/Webcast.shtml
I know it's early in the States, so I've got this covered via my new - and rather cool - flash screenshot program, but if anyone wants to chip in, please do!
Chris,
Care to give us the product name of this flash screenshot program?
-
ULA:
At T-1 hour and counting, everything continues to look good for an on time launch of the GPS IIF-3 satellite for the U.S. Air Force at 8:10 a.m. EDT. The launch team is not currently working any technical issues.
The weather has improved to a 70 percent chance of favorable weather.
-
One hour to the ULA webcast, here:
http://www.ulalaunch.com/site/pages/Webcast.shtml
I know it's early in the States, so I've got this covered via my new - and rather cool - flash screenshot program, but if anyone wants to chip in, please do!
Chris,
Care to give us the product name of this flash screenshot program?
Aye! :)
Greenshot:
http://getgreenshot.org/
-
-
One hour to the ULA webcast, here:
http://www.ulalaunch.com/site/pages/Webcast.shtml
I know it's early in the States, so I've got this covered via my new - and rather cool - flash screenshot program, but if anyone wants to chip in, please do!
Chris,
Care to give us the product name of this flash screenshot program?
Aye! :)
Greenshot:
http://getgreenshot.org/
Sorry for going off-topic but after using it for few months/multible launches, I can confirm that greenshot is awesome for webcasts, especially Shift + Print.
-
ULA just put this out. It's been seen before, but it's still nice:
http://www.ulalaunch.com/site/docs/products/Cutaways/DeltaIVM4Meter_Cutaway.pdf
-
15 mins to the webcast, boys and girls.
-
ULA @ulalaunch
Weather is currently within launch constraints
-
Beautiful light
-
ULA:
T-30 mins. The weather forecast has been upgraded following the 7:30 a.m. weather briefing and there is now an 80 percent chance of favorable weather conditions for launch. Again, the team is not currently working any technical issues.
-
ULA webcast coverage is about to begin.
http://www.ulalaunch.com/site/pages/Webcast.shtml
-
ULA note spacecraft is transferring to internal power
-
It's ok, cause it's free here ;)
-
-
No issues being worked.
-
3:30 min plus mission. ULA only covering the first 25 mins.
-
-
-
-
No one's mentioning BIHs, but it will be at T-4 mins and holding.
-
-
L-15 mins.
-
-
-
Nice touch. L-10 minutes.
-
Load relief file loaded into the RIFCA.
-
Coming up on the vehicle readiness polling.
-
Polling. All go for coming out of the hold.
-
S/C configured for launch.
-
Coming out of the BIH in two minutes.
-
T-4 minutes and counting.
Securing propellant tanks.
-
Vehicle on internal power.
-
-
-
Vehicle ordnance armed.
-
T-2 minutes.
HTPA spin up, hydraulic pressure at 4000 psi.
-
Securing second stage.
-
-
T-60 seconds. Engine start box go.
-
Launch enable. Green board.
-
All tanks ready for launch.
-
Green board, flight lock-in.
-
Liftoff!
-
LAUNCH!!
-
-
-
-
-
-
Mach 1.
-
-
Max-Q.
-
MaxQ
-
-
SRM sep.
-
SRM sep.
-
-
Mach 5.
Altitude 28.3 nm.
-
Saw some debris falling off then.
-
T+3 minutes.
Mach 10.
-
Mach 10.
-
-
Down to partial thrust.
-
-
MECO.
Staging, nozzle deploy, and second stage start.
-
Fairing sep.
-
Staging 1-2 Sep. Second stage ignition.
Fairing Jettison.
-
And ULA now into an interview.
-
-
The Lt. has a lot to say.
-
The Lt. has a lot to say.
Most do
(full disclosure, I'm a SNCO in the AF)
-
Perigee now positive.
SECO-1. Now coasting.
-
Vehicle is in orbit, 87x211nm
-
-
-
3 minutes until next second stage burn.
-
Velocity 17045 ft/s, downrange 3435 nm.
-
Second burn of the upper stage.
-
Two minutes to SECO-2.
-
-
Nice side view shot.
-
4600 miles downrange.
-
SECO-2.
-
SECO.
Orbit 11000x129nm at 43.324 degrees.
Webcast now ending.
-
ULA ending coverage due to the mission length.
-
-
The bird looked really spectacular and beautiful just after SRB jettison. It never ceases to amaze me how clear the long-range tracking camera shots are these days.
-
The bird looked really spectacular and beautiful just after SRB jettison. It never ceases to amaze me how clear the long-range tracking camera shots are these days.
Probably the HD tracking cameras added post Columbia?
-
http://www.youtube.com/watch?v=62LrwX-2u5k (http://www.youtube.com/watch?v=62LrwX-2u5k)
-
According to spaceflihgtnow the exact launch time was 1210:00.242UTC.
-
USAF is optimistic everything will continue well. They already have sent the launch notice:
NOTICE ADVISORY TO NAVSTAR USERS (NANU) 2012062
SUBJ: SVN65 (PRN24) LAUNCH JDAY 278
1. NANU TYPE: LAUNCH
NANU NUMBER: 2012062
NANU DTG: 041222Z OCT 2012
SVN: 65
PRN: 24
LAUNCH JDAY: 278
LAUNCH TIME ZULU: 1210
2. GPS SATELLITE SVN65 (PRN24) WAS LAUNCHED ON JDAY 278.
A USABINIT NANU WILL BE SENT WHEN THE SATELLITE IS SET ACTIVE TO SERVICE.
3. POC: CIVILIAN - NAVCEN AT 703-313-5900, HTTP://WWW.NAVCEN.USCG.GOV
MILITARY - GPS OPERATIONS CENTER AT HTTPS://gps.afspc.af.mil/GPSOC , DSN 560-2541,
COMM 719-567-2541, [email protected] , HTTP://gps.afspc.af.mil/GPSOC/GPS
MILITARY ALTERNATE - JOINT SPACE OPERATIONS CENTER, DSN 276-3514. COMM 805-606-3514.
[email protected]
--- CHAS
-
Waiting for S/C Sep. This is not a success until that point.
-
Waiting for S/C Sep. This is not a success until that point.
Something akin to chickens and their hatching
--- CHAS
-
Target is an altitude about 20,459 KMs and 55 degrees inclination. Keep an eye on this one.
-
Unless I've worked it out wrong, we're several minutes past the S/C Sep point.
-
Unless I've worked it out wrong, we're several minutes past the S/C Sep point.
According to the mission booklet, S/C sep should be at T+3 hours, 33 minutes. With a T0 of 1210UTC, this works out to 1543UTC, so less than 40 minutes from now.
-
Ah good. I was getting my UTCs in a mix.
-
Unless I've worked it out wrong, we're several minutes past the S/C Sep point.
11:43 a.m. EDT
-
SECO-3 underway...
-
Regarding the symbols of the spacecraft/processing patch:
http://www.schriever.af.mil/news/story.asp?id=123320905
--- CHAS
-
Unconfirmed good S/C Sep! There were whispers of some concern early (see L2), but it's ended well, that's the main thing!
-
NORAD's newest tracking data shows an object in a 20459 x 20462 km x 55.00 deg. orbit. Whatever the "spotty thing" was (note that I am thinking of re-subscribing L2 at this moment ;D), there doesn't seems to be a performance shortfall.
-
ULA:
"We have had successful spacecraft separation. This is the last communication regarding the launch of Delta IV GPSIIF-3."
Heh!
Release:
United Launch Alliance Delta IV Rocket Successfully Launches Global Positioning System Satellite for the U.S. Air Force
Launch Marks 65th Successful ULA Launch in Less than Six Years
Cape Canaveral Air Force Station, Fla., (Oct. 4, 2012) – A United Launch Alliance (ULA) Delta IV rocket carrying the Global Positioning System (GPS) IIF-3 payload for the United States Air Force lifted off from Space Launch Complex-37 here at 8:10 a.m. EDT today. This launch marks the 9th ULA launch this year, the 54th Evolved Expendable Launch Vehicle (EELV) mission, and the 65th launch since ULA was formed nearly six years ago.
“Congratulations to the entire team on today’s successful launch of the GPS IIF-3 satellite,” said Jim Sponnick, ULA vice president, Mission Operations. “ULA and our mission partners have a rich heritage with the GPS program and we are proud to have served alongside the government and contractor teams over the last two decades to provide important Global Positioning System capabilities for our national defense and for millions of civilian and commercial users around the world."
This mission was launched aboard a Delta IV Medium-plus configuration vehicle using a ULA single common booster core powered by a Pratt & Whitney Rocketdyne RS-68 main engine, along with two Alliant Techsystems GEM 60 solid rocket motors. The payload was encapsulated by a composite payload fairing and powered by the four-meter diameter upper stage using the PWR RL10B-2 engine. The GPS IIF-3 launch marked the ninth flight of the Delta IV medium+ (4,2) configuration and the 21st flight of the Delta IV family of launch vehicles.
“We are honored to be the primary launch provider for our nation. Reliability, quality, and on-time performance are ULA’s hallmarks,” said Sponnick. “Our nation’s soldiers, sailors, airmen, and Marines rely on our performance in accurately placing our customer’s critical payloads in their required orbits.”
GPS IIF-3 is the third in a series of next generation GPS satellites and will join a worldwide timing and navigation system utilizing 24 satellites in six different planes, with a minimum of four satellites per plane positioned in orbit approximately 11,000 miles above the earths’ surface. The GPS IIF series provides improved accuracy and enhanced performance for GPS users.
The EELV program was established by the United States Air Force United States 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.
ULA's next launch is the Atlas V OTV-3 mission for the Air Force scheduled October 25 from Space Launch Complex-41 at Cape Canaveral Air Force Station, Fla.
ULA program management, engineering, test, and mission support functions are headquartered in Denver, Colo. Manufacturing, assembly and integration operations are located at Decatur, Ala., and Harlingen, Texas. Launch operations are located at Cape Canaveral AFS, Fla., and Vandenberg AFB, Calif.
-
S/C could be catalogued under 38833/ 2012-053A
I found an orbit close to that announced by Penguin above:
20451.8 x 20454.9 km x 55.0°
(elset#2)
-
Cape Canaveral Air Force Station, Fla. (Oct. 4, 2012) – A United Launch Alliance Delta IV rocket blasts off from Space Launch Complex-37 at 8:10 a.m. EDT with the U.S. Air Force’s Global Positioning System (GPS) IIF-3 satellite. This launch marks the 9th ULA launch this year, the 54th Evolved Expendable Launch Vehicle (EELV) mission, and the 65th launch since ULA was formed nearly six years ago. GPS IIF-3 is the third in a series of next generation GPS satellites and will join a worldwide timing and navigation system utilizing 24 satellites in six different planes, with a minimum of four satellites per plane positioned in orbit approximately 11,000 miles above the earths’ surface.
Photo by Pat Corkery, United Launch Alliance
-
ULA:
"We have had successful spacecraft separation. This is the last communication regarding the launch of Delta IV GPSIIF-3."
Heh!
woot!
Congrats to ULA on a job well done
-
This sets the "record", such as it is, for most Delta 4 launches in a calendar year.
Four.
- Ed Kyle
-
Great looking vehicle, great looking launch. Congrats and well done! :)
-
Congrats to ULA on another successful launch!
-
Boeing Modernizes GPS Network with 3rd GPS IIF Satellite
SVN-65 sends 1st signals following launch on Delta IV rocket
Addition to GPS constellation will provide more accurate navigation for military and civilians
CAPE CANAVERAL AIR FORCE STATION, Fla., Oct. 4, 2012 -- The Global Positioning System (GPS), which military, commercial, and civilian users rely on for accurate navigation, is becoming more capable with deployment of the third Boeing [NYSE: BA] GPS IIF for the U.S. Air Force. The IIF model is the most advanced GPS satellite to date.
SVN-65 is on orbit and performing as expected following liftoff at 8:10 a.m. Eastern time from Cape Canaveral Air Force Station aboard a United Launch Alliance Delta IV rocket. Controllers confirmed initial contact with the spacecraft at 11:43 a.m. Eastern time. The satellite's GPS signals will be turned on and tested within a few days.
"With this third IIF satellite now on orbit, Boeing continues to deliver more precise navigation and timing capabilities for military and commercial uses worldwide," said Craig Cooning, vice president and general manager of Boeing Space & Intelligence Systems.
GPS IIF is delivering greater navigational accuracy through improvements in atomic clock technology; a more secure and jam-resistant military signal; a protected, more precise, and interference-free civilian L5 signal, and an extended design life.
Following a sequence of maneuvers and other on-orbit tests, SVN-65 will be placed into medium Earth orbit. After the spacecraft's safety is validated, the Air Force will verify its operability with the rest of the on-orbit constellation and the Boeing-built ground control system known as the Operational Control Segment.
-
Object B (possibly 2nd stage) :
38834/2012-053B in 20448.4 x 21975.3 km x 54.66°
-
Spectacular launch, amazing how far up towards space they can still get a clear picture of the rocket.
-
News Release Issued: October 4, 2012 2:52 PM EDT
ATK Propulsion, Composite and Spacecraft Technologies Help Launch GPS IIF-3 Satellite
ATK Supports the Launch of United Launch Alliance's Delta IV Medium Plus
ARLINGTON, Va., Oct. 4, 2012 /PRNewswire/ -- ATK's (NYSE: ATK) Composite and Propulsion Technologies division supported today's successful launch of a United Launch Alliance Delta IV rocket carrying the GPS IIF-3 satellite.
The Delta IV medium-plus rocket that was used on this flight is in the 4, 2 configuration, which features two ATK 60-inch diameter Graphite Epoxy Motors (GEM). The 53-foot-long motors were mounted on opposing sides of the rocket, with one vectorable motor per side, and provided additional lift capability for the Delta IV medium plus configuration rocket. The GEM 60s burned for approximately 90 seconds and provided 560,000 pounds of thrust to deliver the GPS IIF-3 satellite to its predetermined orbit. The composite cases for the GEM motors were fabricated at the ATK Clearfield, Utah facility and the motor was built at ATK's facility in Magna, Utah.
ATK also designed and produced the nozzle for the Delta IV's RS-68 engine. The Pratt & Whitney Rocketdyne-built RS-68 is the largest hydrogen-fueled engine in the world. ATK also designed and produced the nozzle's thermal protection material, which is capable of shielding the nozzle from the extreme heat of launch when external temperatures can exceed 4,000°F. The nozzle is manufactured at ATK's Promontory, Utah facility.
ATK supplied seven key composite structures for the Delta IV Medium plus launch vehicle: the interstage that provides the interface between the Common Booster Core (CBC) and the cryogenic second stage, a centerbody that integrates the liquid oxygen (LO2) and liquid hydrogen (LH2) tanks, a thermal shield that protect the RS-68 engine during ignition and flight, and a LO2 skirt. The payload was encapsulated by a 4-m (157-in) diameter composite payload fairing, along with a Payload Attach Fitting and Payload Attach Fitting Diaphragm required for payload integration.
The composite structures are four to five meters in diameter and range from one to eight meters in length. They are produced using advanced hand layup, machining, and inspection techniques at the ATK manufacturing facility in Iuka, Miss.
For the GPS IIF-3 satellite ATK provided a host of products including solar arrays, antennas and titanium propellant tanks. ATK designed, manufactured and delivered 12 satellite solar arrays (24 wings) for the Boeing-built GPS IIF-3 satellite. Each array provides up to 3.5 kilowatts of continuous power over the 12-year mission. The arrays were manufactured at ATK's Goleta, Calif., facility. ATK has achieved 100-percent on-orbit success on all solar arrays and deployable systems delivered and launched to date. The composite solar array substrates were manufactured at ATK's San Diego, Calif. facility. Additionally, ATK Goleta manufactured, tested and delivered 12 deployment booms for the Burst Detector Antennae (BDA) for the GPS IIF satellites.
ATK's Rancho Bernardo, Calif. facility performed final assembly and RF (Radio Frequency) test of the antenna suite for GPS IIF between 2003 and 2010. Antennas tested were the TT&C (Telemetry, Tracking & Command), LBS (L-Band System)/ITS (Integrated Transfer System) and BDA (Burst Detection Augmentation), for which gain and antenna pattern data were verified.
The Reaction Control System (RCS) propellant tank for the Delta IV rocket was manufactured at ATK's Commerce, Calif. facility. The GPS IIF has an ullage tank, for which ATK Commerce has responsibility for the blankets, heaters, thermistors and pressurant lines. This tank is a spherical vessel constructed of titanium. The mission will deploy the third satellite in the Block IIF series of the U.S. Air Force's next generation GPS spacecraft that will have improved accuracy, enhanced internal atomic clocks, better anti-jam resistance, a civil signal for commercial aviation and a longer design life.
This newest spacecraft will replace the GPS 2A-21 satellite that was launched by a Delta 2 rocket on June 26, 1993. The IIF series incorporate various improvements to provide greater accuracy, increased signals, and enhanced performance for users.
-
Object B (possibly 2nd stage) :
38834/2012-053B in 20448.4 x 21975.3 km x 54.66°
Very close to the final parameters of 2011-36B, the second stage used during the last GPS 2F launch.
Does anyone have a video covering the SECO 1 period, the end of the first burn of the second stage? I'm interested in comparing mark times with predicted times.
- Ed Kyle
-
From:
http://www.aviationweek.com/Article.aspx?id=/article-xml/asd_10_05_2012_p05-01-503315.xml&utm_source=twitterfeed&utm_medium=twitter
"Operators observed a data anomaly from the Delta IV RL-10B2 upper stage, according to Jessica Rye, United Launch Alliance spokeswoman. The satellite reached its proper orbit and signal acquisition was successful. But officials will analyze the anomaly to determine what happened, if a fix is needed and whether that could affect other launches."
So it wasn't just our imagination. Something did happen.
- Ed Kyle
-
So it wasn't just our imagination. Something did happen.
- Ed Kyle
L2 8)
-
And ULA are now showing some of the issues we've been discussing in L2.
United Launch Alliance Provides Update to Global Positioning System Launch
Centennial, Colo., (Oct. 5, 2012) – ULA successfully launched and deployed the GPS IIF-3 satellite in a precise orbit Thursday, but during the launch, observed an unexpected data signature with the upper stage engine throughout a portion of the flight. The Delta IV’s robust system design, flight software, vehicle margins and propellant reserves enabled the successful outcome for this mission.
The unexpected signature was seen during second stage performance as evidenced by a reduced thrust level of the RL10 engine. The onboard inertial guidance and flight control systems compensated for the lower thrust conditions and the Delta second stage delivered the satellite to the proper orbit.
Per standard processes when a flight data item such as this has been identified, ULA and Pratt & Whitney Rocketdyne have formed a robust investigation team with oversight from major customers. The investigation will thoroughly assess all flight and operational data to determine direct and root causes, and identify/implement appropriate corrective action prior to future flights.
“Though the GPS IIF-3 mission was a complete success, ULA fully understands the challenges of launch and will thoroughly investigate and implement appropriate actions to reliably deliver our customer’s critical capabilities to the orbital positions required,” said Jim Sponnick, ULA’s vice president of Missions Operations.
ULA’s next launch is the Atlas V OTV mission for the Air Force, which utilizes a different model RL10 engine. A thorough review and understanding of this issue will be completed prior to certifying the OTV mission for launch.
ULA program management, engineering, test, and mission support functions are headquartered in Denver, Colo. Manufacturing, assembly and integration operations are located at Decatur, Ala., and Harlingen, Texas. Launch operations are located at Cape Canaveral AFS, Fla., and Vandenberg AFB, Calif.
For more information on ULA, visit the ULA Web site 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 and twitter.com/ulalaunch.
-
According to this story, the second stage RL-10 burned 40 seconds longer than expected during its first firing and it burned 30 seconds longer than expected during its second firing:
http://www.spaceflight101.com/delta-iv-gps-iif-3-launch-updates.html
Why did it take so long to confirm spacecraft separation? Was the rocket not quite where it was supposed to be causing problems acquiring telemetry?
They did finally contact the satellite and determined all is well .. lucky this time.
--- CHAS
-
According to this story, the second stage RL-10 burned 40 seconds longer than expected during its first firing and it burned 30 seconds longer than expected during its second firing:
http://www.spaceflight101.com/delta-iv-gps-iif-3-launch-updates.html
Why did it take so long to confirm spacecraft separation? Was the rocket not quite where it was supposed to be causing problems acquiring telemetry?
They did finally contact the satellite and determined all is well .. lucky this time.
--- CHAS
I wonder how much extra propellant is typically allowed for in the mission planning.
Based on a launch timeline I found, the planned burn time was about 760 seconds. The Payload Planners' Guide gives a maximum burn time for the second stage of 850 seconds, giving about 90 seconds of margin (although the thrust shortfall might have been caused by restricted propellant flow, so that could be longer). So they did get quite lucky indeed.
-
lucky this time
quite lucky indeed
Lucky?
The Delta IV’s robust system design, flight software, vehicle margins and propellant reserves enabled the successful outcome for this mission.
It sure sounds like luck the customer has paid for. Fortune favors those who are well prepared!
-
Lucky?
The Delta IV’s robust system design, flight software, vehicle margins and propellant reserves enabled the successful outcome for this mission.
It sure sounds like luck the customer has paid for. Fortune favors those who are well prepared!
+1
When no word came through at the time of spacecraft separation I was starting to believe there was some kind of failure of the third burn with subsequent LOM. Then Chris came through with the news and I was glad to be proved wrong.
A handy reminder (if one is needed) of how hard this business is.
-
I'm going with lucky. A payload closer to the M4,2 limits would not have made it. It's not like hardware is assigned thinking, "There might be a problem with this engine, so let's put it on a high-margin mission."
But, fortune smiled and that's how it came out. If it's a fleet problem, it manifested itself on a mission where it didn't matter. The investigation should make the fleet more robust.
-
A payload closer to the M4,2 limits would not have made it.
It's probably fair to say a payload at the M4,2 limit would not have made it. But do we know yet if the second stage burned to depletion? The achieved orbit is so good it looks like maybe it had propellant to spare, in which case a payload slightly closer to the M4,2 limit might also have been delivered successfully.
But the main point is that the USAF knew the mass of their payload and knew the capability of the launcher and didn't try to squeeze more payload mass onto the flight. They paid for margin, and yes "luckily" this anomaly was of the type where that margin could be applied to make up the shortfall.
[P.S.: If I were a launch service provider this is definitely the kind of customer I would want to have!]
-
It's probably fair to say a payload at the M4,2 limit would not have made it. But do we know yet if the second stage burned to depletion?
No, the second stage did not burn to depletion. It reached the planned orbit, and it has been tracked in a proper disposal orbit that could only have been reached through the addition of some subsequent delta-v.
Assuming that the problem did not affect specific impulse substantially, a few percent (5-6%?) lower thrust, causing a few percent longer burns, would likely have only required a few more meters per second delta-v. The biggest problem, if it is a problem, would be the late arrival of the payload to its orbit, placing it behind its planned insertion point - something that would not be a big deal to subsequently adjust.
The RL10 expander cycle engine has, or once had, a thrust control valve - even for fixed thrust setups - that was used to handle start up thrust transients. An issue with that thingy is a possibility, I think.
- Ed Kyle
-
Ben Cooper's photos...
http://www.launchphotography.com/GPS_2F-3.html
:o
-
It's probably fair to say a payload at the M4,2 limit would not have made it.
For the Ariane 5 I am pretty sure that any 'missing' payload mass is topped off with balance weights. I know how stupid this sounds but redoing the math for lighter payload is much more work than bolting some iron weights.Just think about the moved centre of gravity when having a lighter payload AND fueling less...
By adding weight you homogenize your ascent profile.. And that is where your internal IMU can sense any performance shortfalls and compensate by burning longer. Apparently that happened with the RL10-2.
-
Just think about the moved centre of gravity when having a lighter payload AND fueling less...
That doesn't make much sense to me. Why would you want to offload propellant if your payload is lighter? Why not carry more propellant instead of iron weights so you increase propellant margins?
By adding weight you homogenize your ascent profile.. And that is where your internal IMU can sense any performance shortfalls and compensate by burning longer. Apparently that happened with the RL10-2.
IMU senses the delta V achieved. It doesn't need a homogenous ascent profile to do be able to compensate for a shortfall, it has its altitude/velocity targets and will work toward that goal. Depending on how adaptive the guidance is, it may miss the precise perigee/apogee target in severe underburn/overburn conditions, but AFAIK that would happen even in an "standard" ascent profile with thrust profiles deviating from expected.
-
I was as surprised as you.. but people working at CSG confirmed it to me.
Think it through: less payload means less weight. Your center of gravity shifts. This might(will) influence your flight control algorithm.
Second: less mass means more acceleration. While your IMU can/should compensate for it (as it did for the Delta IV) being a launch provider I would hesitate to generate a new thrust profile for each payload mass. Just imagine the required certification (and hence cost) for each new flight profile..
It is certainly not reasonable to use dead balance weights, but it is the most cost efficient solution. Having an IMU for fine tuning SECO to enhance injection precision is still priceless.. as it can compensate for quirks as just seen.
-
I'm going with lucky. A payload closer to the M4,2 limits would not have made it. It's not like hardware is assigned thinking, "There might be a problem with this engine, so let's put it on a high-margin mission."
But, fortune smiled and that's how it came out. If it's a fleet problem, it manifested itself on a mission where it didn't matter. The investigation should make the fleet more robust.
So the M4,2 had extra capacity, would the M4 have had enough--assuming a nominal RL-10 burn?
This question may require the exact details of the problem but what have happened if this was the NROL-15 flight? From the discussions so far, NRO dodged a bullet and is breathing a huge sigh of relief...
-
I'm going with lucky. A payload closer to the M4,2 limits would not have made it. It's not like hardware is assigned thinking, "There might be a problem with this engine, so let's put it on a high-margin mission."
But, fortune smiled and that's how it came out. If it's a fleet problem, it manifested itself on a mission where it didn't matter. The investigation should make the fleet more robust.
So the M4,2 had extra capacity, would the M4 have had enough--assuming a nominal RL-10 burn?
This question may require the exact details of the problem but what have happened if this was the NROL-15 flight? From the discussions so far, NRO dodged a bullet and is breathing a huge sigh of relief...
But how close was NROL - 15 really to the edge of the capacity of the uprated DIVH though?
As we know very little about this payload we don't know if in that flight there wasn't also a calculated margin of safety should anything like this happen which would still have meant it was delivered on orbit correctly.
-
Ben Cooper's photos...
http://www.launchphotography.com/GPS_2F-3.html
:o
What an artist. Amazing images
-
What an artist. Amazing images
Indeed. He always leaves me wanting higher resolution versions.
-
Wait, avhollar, you're saying Ariane doesn't reanalyze trajectory for each mission?
-
Their ascent profile is remarkably uniform. Always 36000x250km, 5 deg inclination, argument of perigee around 176 (or was it 178) deg.They will certainly update upper wind data though.
Do you recall how tiny the center-of-gravity allowed region for the space shuttle was? Given that, bolting some weights to the payload adapter is much more reasonable than ending up with 20% fuel left at your destination orbit.
-
I doubt ATV is launched into 36000x250 or an environmental satellite.
Just because Shuttle was a finicky system doesn't mean others are. I'd rather not ballast and be able to fly through problems like Delta IV or Falcon 9 did, or develop an algorithm to use that extra propellant, or have a disposal burn that gets the stage out of the operational orbit.
-
Do you recall how tiny the center-of-gravity allowed region for the space shuttle was? Given that, bolting some weights to the payload adapter is much more reasonable than ending up with 20% fuel left at your destination orbit.
Totally unrelated. Shuttle CG limits were for landing not ascent. Shuttle ascent was just as adaptive as Delta or Atlas.
And no, adding ballast is not more reasonable.
-
A payload closer to the M4,2 limits would not have made it.
It's probably fair to say a payload at the M4,2 limit would not have made it. But do we know yet if the second stage burned to depletion? The achieved orbit is so good it looks like maybe it had propellant to spare, in which case a payload slightly closer to the M4,2 limit might also have been delivered successfully.
But the main point is that the USAF knew the mass of their payload and knew the capability of the launcher and didn't try to squeeze more payload mass onto the flight. They paid for margin, and yes "luckily" this anomaly was of the type where that margin could be applied to make up the shortfall.
[P.S.: If I were a launch service provider this is definitely the kind of customer I would want to have!]
Using Gunter's info.
Atlas V 401 is to be used to deliver the next GPS. Its GTO performance is 4950 kg. Delta IV M+ (4,2) capability to GTO is 5845 kg. A DIV M was not used since it does not have the capability to meet the mission requirements (it will with an RS-68A)
So that should give an indication of the margin that this mission had.
-
A payload closer to the M4,2 limits would not have made it.
It's probably fair to say a payload at the M4,2 limit would not have made it. But do we know yet if the second stage burned to depletion? The achieved orbit is so good it looks like maybe it had propellant to spare, in which case a payload slightly closer to the M4,2 limit might also have been delivered successfully.
But the main point is that the USAF knew the mass of their payload and knew the capability of the launcher and didn't try to squeeze more payload mass onto the flight. They paid for margin, and yes "luckily" this anomaly was of the type where that margin could be applied to make up the shortfall.
[P.S.: If I were a launch service provider this is definitely the kind of customer I would want to have!]
Using Gunter's info.
Atlas V 401 is to be used to deliver the next GPS. Its GTO performance is 4950 kg. Delta IV M+ (4,2) capability to GTO is 5845 kg. A DIV M was not used since it does not have the capability to meet the mission requirements (it will with an RS-68A)
So that should give an indication of the margin that this mission had.
I assume the Atlas 401 costs the DOD less than a Delta IV M+. Any insight why they chose the more expensive launcher for this one ?
-
Availability? Atlas and Delta are booked solid.
-
Availability? Atlas and Delta are booked solid.
But performance wise wasn't it overkill for its payload and costly overkill at that?
-
Wait, avhollar, you're saying Ariane doesn't reanalyze trajectory for each mission?
Their ascent profile is remarkably uniform. Always 36000x250km, 5 deg inclination, argument of perigee around 176 (or was it 178) deg.They will certainly update upper wind data though.
EELV's do not have this restriction. EELV's fly to every orbit that customers have dreamed up uses for satellites, LEO, MEO, GTO, GSO, Earth escape and many more. Just look at the past EELV launches.
-
It's not a restriction. Ariane 5 has been flying all kinds of profiles, too.
It's a simplification that probably helps with cost and reliability of delivering comsats to GTO which is Ariane 5's main business. Something EELVs don't have to bother about since they are not competitive there anyway...
Just kidding. I could bet, EELVs are doing similar things for common flight profiles.
-
"U.S. Air Force Gen. William Shelton, commander of Air Force Space Command, has ordered an “accident investigation board” to review an upper-stage thrust anomaly that occurred during the successful Oct. 4 launch of a GPS satellite aboard a United Launch Alliance (ULA) Delta 4 rocket, the service announced Oct. 11."
http://www.spacenews.com/launch/121012-shelton-investigation-delta-anomaly.html
-
"U.S. Air Force Gen. William Shelton, commander of Air Force Space Command, has ordered an “accident investigation board” to review an upper-stage thrust anomaly that occurred during the successful Oct. 4 launch of a GPS satellite aboard a United Launch Alliance (ULA) Delta 4 rocket, the service announced Oct. 11."
http://www.spacenews.com/launch/121012-shelton-investigation-delta-anomaly.html
Not surprised by this .....too much rides on the RL-10 working as advertised.
-
"U.S. Air Force Gen. William Shelton, commander of Air Force Space Command, has ordered an “accident investigation board” to review an upper-stage thrust anomaly that occurred during the successful Oct. 4 launch of a GPS satellite aboard a United Launch Alliance (ULA) Delta 4 rocket, the service announced Oct. 11."
http://www.spacenews.com/launch/121012-shelton-investigation-delta-anomaly.html
Not surprised by this .....too much rides on the RL-10 working as advertised.
Is there a history of problems with the RL-10B-2 specifically? I know that there was an early MECO with the RL-10A-4 on an early Atlas-V flight but I wasn't aware of any problems with the Delta-IV equivalent.
-
"U.S. Air Force Gen. William Shelton, commander of Air Force Space Command, has ordered an “accident investigation board” to review an upper-stage thrust anomaly that occurred during the successful Oct. 4 launch of a GPS satellite aboard a United Launch Alliance (ULA) Delta 4 rocket, the service announced Oct. 11."
http://www.spacenews.com/launch/121012-shelton-investigation-delta-anomaly.html
Not surprised by this .....too much rides on the RL-10 working as advertised.
Is there a history of problems with the RL-10B-2 specifically? I know that there was an early MECO with the RL-10A-4 on an early Atlas-V flight but I wasn't aware of any problems with the Delta-IV equivalent.
That was traced to a leaking LH valve. I think the previous RL-10 issue was the Delta III chamber breach due to a faulty weld on flight 2 in 1999. I think prior to that it was the two failed restarts in a row in the early 1990's.
It has been a rock solid engine with a long history.
Like everyone else I am curious as to the cause.
Edit: Atlas I AC-70 and AC-71 in 1991 and 1992.
-
From what I've heard (and I'll admit I'm murky on the details), there is general agreement within the national security community that if they are going to invest in any rocket development in the near-term, it should be in creating a replacement for the RL-10. It's a reliable engine, but they've used up all margin and they cannot get much more out of it.
-
From what I've heard (and I'll admit I'm murky on the details), there is general agreement within the national security community that if they are going to invest in any rocket development in the near-term, it should be in creating a replacement for the RL-10. It's a reliable engine, but they've used up all margin and they cannot get much more out of it.
been designed and somewhat tested, not excuted fully.
Many directions can be taken which fork in the road to take?
-
From what I've heard (and I'll admit I'm murky on the details), there is general agreement within the national security community that if they are going to invest in any rocket development in the near-term, it should be in creating a replacement for the RL-10. It's a reliable engine, but they've used up all margin and they cannot get much more out of it.
Do you know if there has been any consideration in the community of removing any commonality between Atlas and Delta so that an accident with one does not ground the whole fleet?
-
From what I've heard (and I'll admit I'm murky on the details), there is general agreement within the national security community that if they are going to invest in any rocket development in the near-term, it should be in creating a replacement for the RL-10. It's a reliable engine, but they've used up all margin and they cannot get much more out of it.
Do you know if there has been any consideration in the community of removing any commonality between Atlas and Delta so that an accident with one does not ground the whole fleet?
From what was posted in that thread by Dr Sowers of ULA it seems like they are looking at more commonality between the two not less.
-
GPS IIF-3 is usable. Here is the official notification to NAVSTAR users:
NOTICE ADVISORY TO NAVSTAR USERS (NANU) 2012070
SUBJ: SVN65 (PRN24) USABLE JDAY 319/0033
1. NANU TYPE: USABINIT
NANU NUMBER: 2012070
NANU DTG: 140038Z NOV 2012
REFERENCE NANU: N/A
REF NANU DTG: N/A
SVN: 65
PRN: 24
START JDAY: 319
START TIME ZULU: 0033
START CALENDAR DATE: 14 NOV 2012
STOP JDAY: N/A
STOP TIME ZULU: N/A
STOP CALENDAR DATE: N/A
2. CONDITION: GPS SATELLITE SVN65 (PRN24) WAS USABLE AS OF JDAY 319
(14 NOV 2012) BEGINNING 0033 ZULU.
3. POC: CIVILIAN - NAVCEN AT 703-313-5900, HTTP://WWW.NAVCEN.USCG.GOV
MILITARY - GPS OPERATIONS CENTER at HTTPS://GPS.AFSPC.AF.MIL/GPSOC,
DSN 560-2541,
COMM 719-567-2541, [email protected],
HTTPS://GPS.AFSPC.AF.MIL
MILITARY ALTERNATE - JOINT SPACE OPERATIONS CENTER, DSN 276-3514,
COMM 805-606-3514, [email protected]
--- CHAS
-
Is there a history of problems with the RL-10B-2 specifically? I know that there was an early MECO with the RL-10A-4 on an early Atlas-V flight but I wasn't aware of any problems with the Delta-IV equivalent.
RL10B-2 failed the first time it was used, during the second Delta III mission on May 5, 1999. The engine performed its first burn to reach a parking orbit, but failed upon restart after a coast period. A failure investigation determined that the RL10B-2 engine's combustion chamber had burst during the restart due to defective brazing of a welded reinforcing strip. Pratt & Whitney subsequently modified its brazing process and its inspection methods.
- Ed Kyle
-
3rd Boeing GPS IIF Begins Operation After Early Handover to US Air Force
Excellent satellite performance advances GPS system modernization
EL SEGUNDO, Calif., Dec. 5, 2012 -- A third Boeing [NYSE: BA] GPS IIF satellite has completed on-orbit checkout and is now part of the active 31-satellite GPS constellation, providing improved performance for both military and civilian users. GPS IIF-3, now designated SVN-65, is being operated by the 50th Space Wing's 2nd Space Operations Squadron at Schriever Air Force Base, Colo., following an Oct. 4 launch from Cape Canaveral Air Force Station in Florida.
"We completed the checkout and validation of SVN-65 in 22 days instead of the scheduled 30," said Col. Bernie Gruber, director of the Space and Missile Systems Center's Global Positioning Systems Directorate. "The smooth transition to operations is reflective of the solid teamwork on the part of the joint Boeing and Air Force Mission Operations team as well as a healthy satellite. Following the handover, orbital maneuvers were completed to position SVN-65 in its final location and the satellite has been set to healthy."
"Our focus on mission success, extending from our supplier shop floors to our program management system and quality controls, has produced a high-performing satellite ready to go to work for the GPS user community," said Craig Cooning, vice president and general manager of Boeing Space and Intelligence Systems.
SVN-65 joins the two Boeing GPS IIFs launched in 2010 and 2011. Together, they are strengthening and enhancing the capabilities of the constellation with improved anti-jamming and greater navigational accuracy. The addition of the third IIF also means that operators can more fully test the new third civilian L5 signal that will aid commercial airline operations and search-and-rescue missions.
Boeing is providing a total of 12 GPS IIFs to the U.S. Air Force, which operates the GPS network. Of the remaining nine to be delivered, six will be completed by the end of 2012 and the remaining three in 2013.
"Boeing has partnered with the Air Force for nearly 40 years to provide this critical resource, accumulating more than 500 years of on-orbit service since the first GPS launch in 1978," said Jan Heide, Boeing GPS IIF program director.
-
3rd Boeing GPS IIF Begins Operation After Early Handover to US Air Force
Boeing is providing a total of 12 GPS IIFs to the U.S. Air Force, which operates the GPS network. Of the remaining nine to be delivered, six will be completed by the end of 2012 and the remaining three in 2013.
You mean they will launch and deploy 6 more satellites in the remaining 26 days of this year? Or this is just about manufacturing, not launching?
-
3rd Boeing GPS IIF Begins Operation After Early Handover to US Air Force
Boeing is providing a total of 12 GPS IIFs to the U.S. Air Force, which operates the GPS network. Of the remaining nine to be delivered, six will be completed by the end of 2012 and the remaining three in 2013.
You mean they will launch and deploy 6 more satellites in the remaining 26 days of this year? Or this is just about manufacturing, not launching?
Satellite construction
-
3rd Boeing GPS IIF Begins Operation After Early Handover to US Air Force
Boeing is providing a total of 12 GPS IIFs to the U.S. Air Force, which operates the GPS network. Of the remaining nine to be delivered, six will be completed by the end of 2012 and the remaining three in 2013.
You mean they will launch and deploy 6 more satellites in the remaining 26 days of this year? Or this is just about manufacturing, not launching?
Satellite construction
I was trying to find when the rest of these bird are scheduled to launch, and it appears from the Boeing site, that is TBD. I could only find a single GPS launch on the manifest for next year. Are they waiting for old GPS sats to reach End-Of-Life, or is there some other reason we would keep these completed GPS sats in storage for a while ?
-
They will be launched at a rate of 2-3 per year. It is cheaper to build all the spacecraft as soon as possible and then stored them until launch vs stretching out the production to meet the launch rate.
-
Well we could also argue about the benefits of on orbit storage verses terrestrial storage ;)
-
Just a note for this thread, that today's ULA press release mentioned some vague details on the GPS IIF-3 Delta's RL10 failure. It was a thrust chamber fuel leak that began during the first engine start sequence.
http://www.ulalaunch.com/site/pages/News.shtml#/126/
Quoting:
"The ULA investigation has concluded that a fuel leak occurred in a specific area of the interior of the thrust chamber, and that this leak started during the first engine start sequence. Although the investigation into the flight data anomaly continues, all credible crossover implications from the Delta anomaly for the OTV-3 Atlas vehicle and engine system have been thoroughly addressed and mitigated, culminating in the flight clearance decision for the OTV-3 launch."
I don't know how they were able to clear the Centaur RL10.
- Ed Kyle
-
Not to read words between the lines that are not real, but what is a thrust chamber? It is not the combustion chamber (aka Delta III flight 2), so could this be the nozzle, specifically the seal in the nozzle extension which is unique to Delta?
Before Jim beats me up and takes my rocket money. Disclaimer, I think this might be an unrealistic stretch.
-
Not to read words between the lines that are not real, but what is a thrust chamber? It is not the combustion chamber (aka Delta III flight 2), so could this be the nozzle, specifically the seal in the nozzle extension which is unique to Delta?
Before Jim beats me up and takes my rocket money. Disclaimer, I think this might be an unrealistic stretch.
The RL10B-2 nozzle extension is carbon-composite ablative, with no propellant circulating through so that no leaks can occur on that part. The main part of the thrust chamber is regeneratively cooled, so it can leak.
The Atlas RL10A-4-2 engine uses a smaller nozzle extension (that is not "extendible" but is fixed) attached to a main thrust chamber that is similar to the RL10B-2 chamber, but that likely operates at lower chamber pressure.
- Ed Kyle
-
Some more details on the failure investigation and results...
http://spaceflightnow.com/delta/d361/investigation.html
-
So, the essence of this is that there was a leak in the main engine nozzle just above its narrowest point that would have meant reduced thrust. I presume that it would have also meant a permanent hard-over TV in the opposite direction to stop the vehicle being forced off course by the exhaust leak, further reducing the energy delivered along the long axis. Am I correct?
This is probably a manufacturing/materials quality control issue. Nothing world-shaking but I'm sure PWR will be required to undertake either extra checks or closer checks on the RL-10B-2 nozzles for a while.
-
This is probably a manufacturing/materials quality control issue. Nothing world-shaking but I'm sure PWR will be required to undertake either extra checks or closer checks on the RL-10B-2 nozzles for a while.
Considering on the Delta III flight 2 failure they had X-Rays that showed the defect area. It would not have taken so long to assign a root cause if the defect(s) had shown up in the X-Rays and pre-flight inspection records. Something more complex than a simple QC issue is at work here.
-
"We completed the checkout and validation of SVN-65 in 22 days instead of the scheduled 30," said Col. Bernie Gruber, director of the Space and Missile Systems Center's Global Positioning Systems Directorate. "The smooth transition to operations is reflective of the solid teamwork on the part of the joint Boeing and Air Force Mission Operations team as well as a healthy satellite. Following the handover, orbital maneuvers were completed to position SVN-65 in its final location and the satellite has been set to healthy."
Given the current affairs this should be applauded. Well done!
-
This is probably a manufacturing/materials quality control issue. Nothing world-shaking but I'm sure PWR will be required to undertake either extra checks or closer checks on the RL-10B-2 nozzles for a while.
Considering on the Delta III flight 2 failure they had X-Rays that showed the defect area. It would not have taken so long to assign a root cause if the defect(s) had shown up in the X-Rays and pre-flight inspection records. Something more complex than a simple QC issue is at work here.
Which is slightly more worrying, when you think of it. RL-10B-2 has a role in the SLS program, after all, and 'something more complex' could push that timeline to the right. Especially if it raises issues regarding human-rating.
-
So, the essence of this is that there was a leak in the main engine nozzle just above its narrowest point that would have meant reduced thrust. I presume that it would have also meant a permanent hard-over TV in the opposite direction to stop the vehicle being forced off course by the exhaust leak, further reducing the energy delivered along the long axis. Am I correct?
My interpretation was that the leak resulted in some off-axis thrust, but not enough to require a "hard over" thrust vector correction. The RL10 likely was gimbaled slightly to correct.
- Ed Kyle
-
Some more details on the failure investigation and results...
http://spaceflightnow.com/delta/d361/investigation.html
This article states: "Those potential causes common to both vehicles have been put to the test against the Atlas engine that will power Tuesday's launch of the X-37B spaceplane, known as Orbital Test Vehicle Flight 3, and officials Friday formally cleared that RL10A-4 for flight."
But an article in Av Week (arrived today, can't find it online yet) was less sanguine. I stated (more or less) that it was "formally cleared" by waiving the requirement that the last failure be understood, and simply taking your chances. It said each customer had this option, and that NASA had already accepted it for the January TDRS flight.
-
This article states: "Those potential causes common to both vehicles have been put to the test against the Atlas engine that will power Tuesday's launch of the X-37B spaceplane, known as Orbital Test Vehicle Flight 3, and officials Friday formally cleared that RL10A-4 for flight."
But an article in Av Week (arrived today, can't find it online yet) was less sanguine. I stated (more or less) that it was "formally cleared" by waiving the requirement that the last failure be understood, and simply taking your chances. It said each customer had this option, and that NASA had already accepted it for the January TDRS flight.
From the Av week article "Effect, No Cause":
satellite owners are proceeding with [...] EELV missions only if they are willing to accept any extra risk resulting from the unknowns surrounding the incident"
The Air Force launched [...] only after acknowledging "acceptable risk" [...] "Each mission owner makes their own determination [...]" NASA has likewise agreed to launch its next satellite...
"We have to find what happened and why, because there is no Plan B," Sheldon said.
One would have to think this situation gave some impetus towards granting SpaceX qualification flights for military contracts.
-
One would have to think this situation gave some impetus towards granting SpaceX qualification flights for military contracts.
There is no connection. New govt contracts requiring a down select, take more than a year.
Also, if following that line of reasoning, then Spacex is not worthy alternative since they have issues too.
-
One would have to think this situation gave some impetus towards granting SpaceX qualification flights for military contracts.
There is no connection. New govt contracts requiring a down select, take more than a year.
Also, if following that line of reasoning, then Spacex is not worthy alternative since they have issues too.
The "situation", one upper stage engine that, if stood down, could stop all launches, has existed for much more than a year. At least some folks had to have been thinking, "What if the RL-10 is grounded?". The recent problem should (I hope) just be demonstrating that people were right to be worried.
And as far as SpaceX being a worthy alternative, even if they too are grounded sometimes, it's still better than a single point of failure. Of course it's not yet proven they can do the job.
-
One would have to think this situation gave some impetus towards granting SpaceX qualification flights for military contracts.
There is no connection. New govt contracts requiring a down select, take more than a year.
Also, if following that line of reasoning, then Spacex is not worthy alternative since they have issues too.
The "situation", one upper stage engine that, if stood down, could stop all launches, has existed for much more than a year. At least some folks had to have been thinking, "What if the RL-10 is grounded?". The recent problem should (I hope) just be demonstrating that people were right to be worried.
And as far as SpaceX being a worthy alternative, even if they too are grounded sometimes, it's still better than a single point of failure. Of course it's not yet proven they can do the job.
If this anomoly has any lasting effects, it would only be in regards to the progress of the Next-Gen Engine contract, and the possible replacement of the RL-10.
-
According to Av Week, the RL-10 investigation is still ongoing, with no conclusions yet. Each customer must still decide of the risk reduction by waiting for a conclusion is worth the delay. There are more Atlas folks going forward than Delta folks.
https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=newssearch&cd=1&cad=rja&ved=0CC0QqQIoADAA&url=http%3A%2F%2Fwww.aviationweek.com%2FBlogs.aspx%3FplckBlogId%3DBlog%3A27ec4a53-dcc8-42d0-bd3a-01329aef79a7%26plckPostId%3DBlog%253A27ec4a53-dcc8-42d0-bd3a-01329aef79a7Post%253A57b2af60-beea-41ba-8c83-1c3fc37e152d&ei=yAz4UOCLEqbp0gGwx4HADw&usg=AFQjCNHe0NdodhTwkFY5q_K53GHOVZKQzA&bvm=bv.41018144,d.dmQ (https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=newssearch&cd=1&cad=rja&ved=0CC0QqQIoADAA&url=http%3A%2F%2Fwww.aviationweek.com%2FBlogs.aspx%3FplckBlogId%3DBlog%3A27ec4a53-dcc8-42d0-bd3a-01329aef79a7%26plckPostId%3DBlog%253A27ec4a53-dcc8-42d0-bd3a-01329aef79a7Post%253A57b2af60-beea-41ba-8c83-1c3fc37e152d&ei=yAz4UOCLEqbp0gGwx4HADw&usg=AFQjCNHe0NdodhTwkFY5q_K53GHOVZKQzA&bvm=bv.41018144,d.dmQ)
-
There are more Atlas folks going forward than Delta folks.
Makes sense. After all, RL-10B-2 is the engine under investigation; RL-10A-4 is related but not identical. I'm sure it's from a different production line and therefore is less likely to be affected by whatever really happened here.
-
Can you explain how you are sure of your statements?
-
Can you explain how you are sure of your statements?
If this post was directed to me, I'm not absolutely sure but I think that it's common sense. Customers would be less willing to take a change with the same engine model that failed. Another engine model of the same family is still increased risk, as there is likely component production common to both, but the risk is still reduced compared to the actual type that failed.
-
Can you explain how you are sure of your statements?
If this post was directed to me, I'm not absolutely sure but I think that it's common sense. Customers would be less willing to take a change with the same engine model that failed. Another engine model of the same family is still increased risk, as there is likely component production common to both, but the risk is still reduced compared to the actual type that failed.
It wasn't me that was questioning, but the part I would question would be "separate production lines". The volume is already tiny; I'd think (without any knowledge) they are built on the same line, with the few variations taken care of at specific stations.
-
There are more Atlas folks going forward than Delta folks.
Makes sense. After all, RL-10B-2 is the engine under investigation; RL-10A-4 is related but not identical.
According to this web site
http://www.spaceandtech.com/spacedata/engines/rl10_specs.shtml
the B-2 variant has a higher chamber pressure than the A-4 (640 psi vs 578). So presumably the fuel pressure must be higher by a similar amount. So whatever it was that busted, it's probably under about 10% less stress in the A-4. Maybe this is part of why Atlas customers seem less worried...
-
There are more Atlas folks going forward than Delta folks.
Makes sense. After all, RL-10B-2 is the engine under investigation; RL-10A-4 is related but not identical. I'm sure it's from a different production line and therefore is less likely to be affected by whatever really happened here.
A recent note in Av Week, (Issue 1-8 April 2013, I can't find the article on-line, titled "Next Boost for Delta IV Could Come in May") talks about this. It says they are at least 90% through the fault tree, and are mitigating each potential issue.
It also says "Because the potential technical issues that could have led to the thrust issue in October were limited to the design of the RL10B-2, the Atlas V and its RL10A are clear for continued launches". But elsewhere in the article, is says "Foreign object debris is one possible culprit". I can't see how this would be RL10B-2 specific...
-
Just read this story from last week..
http://www.thespacereview.com/article/2302/1
Be interesting to see what is released because an ACCIDENT investigation board, not a MISHAP board, was convened and some part of AIBs are usually released. The story also doesn't mention the difference between accident and safety investigation boards although releasability of info from each is described by the left/right side of the folder analogy. I was under the impression that the AIB/SIB are separate panels, not one that issues two reports...
-
I have been unable to locate the report online so I submitted my first Freedom of Information Act request to see if I can get the report if it hasn't been released already. I'll advise whenever I get a status update.
-
I received this response to my FOIA request. Supposedly the report is NOT complete or signed...
"This e-mail contains FOR OFFICIAL USE ONLY (FOUO) information which must be
protected under the Freedom of Information Act (5 U.S.C 552) and/or the
Privacy Act of 1974 (5 U.S.C. 552a). Unauthorized disclosure or misuse of
this PERSONAL INFORMATION may result in disciplinary action, criminal and/or
civil penalties. Further distribution is prohibited without the approval
of the author of this message unless the recipient has a need to know in the
performance of official duties. If you have received this message in error,
please notify the sender and delete all copies of this message."
FOIA Program Manager
150 Vandenberg Street, Suite 1150
Peterson AFB CO 80914
This is in response to your Freedom of Information Act (FOIA)
request seeking release of the AIB report for the investigation of why a
Delta IV RL-10B-2 upper stage engine did not perform as expected during the
Oct 4, 2012 launch of a GPS IIF satellite.
A thorough search was conducted and no records were found responsive
to your request for an AIB report. The investigation has not concluded and
a final report has thus not been signed and approved. Then the reason we
have no record of the final report as the document does not exist.
If you interpret this "no records" response as an adverse action,
you may appeal our decision by writing to the Secretary of the Air Force
within 60 calendar days from the date of this letter. If no appeal is
received, or if the appeal is postmarked after the conclusion of this 60-day
period (9 December 2013), the appeal will be considered closed. Include
your reasons for reconsideration along with a copy of this letter. Mail to:
Secretary of the Air Force
Thru: FOIA Requester Servicing Center (RSC)-Peterson AFB
150 Vandenberg Street, Suite 1105
Peterson AFB CO 80914
Department of Defense Regulation 5400.7 indicates fees be assessed
for processing this request; however, there are no fees associated with this
request.
Please contact me if you have questions concerning your request.
You may contact us at (719)-554-1188 or E-mail [email protected].
Please reference your assigned case number when making inquiries.
-
Have you considered making another FOIA request?
ULA
Cape Canaveral Air Force Station, Fla. (Oct. 18, 2013) -- The launch of the GPS IIF-5 mission on a ULA Delta IV launch vehicle, currently scheduled for Oct. 23, 2013, is being delayed. The team has continued with Phase II of an investigation related to a successful Delta IV launch that occurred in October 2012 in which the second stage RL10B-2 engine thrust was lower than expected. It was determined that a fuel leak occurred within the engine system and that this fuel leak caused the low thrust. The ongoing Phase II investigation has included extremely detailed characterization and reconstructions of the instrumentation signatures obtained from the October 2012 launch and these have recently resulted in some updated conclusions related to dynamic responses that occurred on the engine system during the first engine start event. The GPS IIF-5 Delta IV launch is being delayed to allow the technical team time to further assess these updated conclusions and assess the improvements already implemented and determine whether additional changes are required prior to the next Delta IV launch. The Delta IV booster for the GPS IIF-5 mission has completed the standard processing and checkout on the launch pad and will be maintained in a ready state for spacecraft mate and launch pending completion of this assessment. A new launch date will be established when the assessment of the updated dynamic response information is completed in the coming weeks. The processing of Atlas V vehicles for upcoming missions including the Nov. 18 launch of the MAVEN mission for NASA are proceeding as planned.
Jessica Rye, APR
ULA Communications
-
Have you considered making another FOIA request?
ULA
Cape Canaveral Air Force Station, Fla. (Oct. 18, 2013) -- The launch of the GPS IIF-5 mission on a ULA Delta IV launch vehicle, currently scheduled for Oct. 23, 2013, is being delayed. The team has continued with Phase II of an investigation related to a successful Delta IV launch that occurred in October 2012 in which the second stage RL10B-2 engine thrust was lower than expected. It was determined that a fuel leak occurred within the engine system and that this fuel leak caused the low thrust. The ongoing Phase II investigation has included extremely detailed characterization and reconstructions of the instrumentation signatures obtained from the October 2012 launch and these have recently resulted in some updated conclusions related to dynamic responses that occurred on the engine system during the first engine start event. The GPS IIF-5 Delta IV launch is being delayed to allow the technical team time to further assess these updated conclusions and assess the improvements already implemented and determine whether additional changes are required prior to the next Delta IV launch. The Delta IV booster for the GPS IIF-5 mission has completed the standard processing and checkout on the launch pad and will be maintained in a ready state for spacecraft mate and launch pending completion of this assessment. A new launch date will be established when the assessment of the updated dynamic response information is completed in the coming weeks. The processing of Atlas V vehicles for upcoming missions including the Nov. 18 launch of the MAVEN mission for NASA are proceeding as planned.
Jessica Rye, APR
ULA Communications
I may, but first I'll get in contact with FOIA rep to see if the report will be released--or at least I'll be notified--when the report is concluded based on my original request. I read from the ULA release "The ongoing Phase II investigation..." that the investigation and thus the report, have in fact not been concluded.
-
I resubmitted my request for the AIB report and will advise when I receive a response.
I was on the AF FOIA site looking for the just released full AIB report on the KC-135 that crashed supporting Enduring Freedom. Flight control system failure(s) exacerbated by crew responses to resulting directional instability lead to structural failure and complete separation of the tail section.
http://www.amc.af.mil/news/story.asp?id=123403437
-
Aaah, so it was dutch roll....
-
Just received this from the 21SW FOIA/PA office. Sounds like the report might be done or am I reading too much (release determination) into it?
"We received your Freedom of Information Act request for "release of the
AIB report for the investigation of why a Delta IV RL-10B-2 upper stage engine
did not perform as expected during the Oct 4, 2012 launch of a GPS IIF
satellite." Your case has been assigned number 2014-03313-F. We will make
every effort to provide you a release determination by 19 May 2014..."
-
I'm beginning to doubt this report will ever be finished. I don't think I've ever seen a report take this long...
"This is in response to your Freedom of Information Act (FOIA) request seeking release of the AIB report for the investigation of why a Delta IV RL-10B-2 upper stage engine did not perform as expected during the Oct 4, 2012 launch of a GPS IIF satellite. A thorough search was conducted and no records were found responsive to your request for an AIB report. The investigation is still pending so there is no report to release. "