-
#20
by
landofgrey
on 18 Oct, 2013 21:05
-
I have a query in as to the likelihood of the launch slipping past MAVEN. From everything I've been hearing here around the cape, it seems likely, but I want to get something more or less official even if off-the-record.
Ah... a reply. I'm being told it's too soon to tell as of now. So... we'll see.
Matt
-
#21
by
Star One
on 19 Oct, 2013 11:12
-
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
How is that this effects this mission & not other Delta IV missions we have already seen this year, is it purely because it's another GPS mission?
-
#22
by
ugordan
on 19 Oct, 2013 11:14
-
My guess is it's got something to do with the "some updated conclusions". I.e. they OK-d the engine based on earlier investigation but they're now having some second thoughts about that.
-
#23
by
Star One
on 19 Oct, 2013 11:24
-
My guess is it's got something to do with the "some updated conclusions". I.e. they OK-d the engine based on earlier investigation but they're now having some second thoughts about that.
Does it indicate there is block of engines with this issue?
-
#24
by
ugordan
on 19 Oct, 2013 11:31
-
Since the last few flights went off without a hitch, I would say it's not a multiple engine issue. Whatever happened seems to be very rare/unlikely, they likely just want to understand it as best as they possibly can in order to guarantee this doesn't happen again.
-
#25
by
russianhalo117
on 19 Oct, 2013 16:48
-
Since the last few flights went off without a hitch, I would say it's not a multiple engine issue. Whatever happened seems to be very rare/unlikely, they likely just want to understand it as best as they possibly can in order to guarantee this doesn't happen again.
A hold preventing launch was placed on several DIVs by Phase II of the commission to allow for inspection of the DCSS and the engine modifications and other changes implemented after the engine failure. If they are happy with the results they will release this DIV just like all of the DIVs since engine incident happened. This process will repeat for the foreseeable future for DCSS stages that have had the required mods implemented while the engine was attached to the DCSS during the modification process. This stage by stage review by the investigation will end soon as the engines that were not installed at the time of the incident can be inspected before installation to a DCSS. This is my understanding. Also RL-10C conversions begin flying at the end of 2014 to the beginning of 2015.
-
#26
by
WHAP
on 19 Oct, 2013 17:19
-
Since the last few flights went off without a hitch, I would say it's not a multiple engine issue. Whatever happened seems to be very rare/unlikely, they likely just want to understand it as best as they possibly can in order to guarantee this doesn't happen again.
A hold preventing launch was placed on several DIVs by Phase II of the commission to allow for inspection of the DCSS and the engine modifications and other changes implemented after the engine failure. If they are happy with the results they will release this DIV just like all of the DIVs since engine incident happened. This process will repeat for the foreseeable future for DCSS stages that have had the required mods implemented while the engine was attached to the DCSS during the modification process. This stage by stage review by the investigation will end soon as the engines that were not installed at the time of the incident can be inspected before installation to a DCSS. This is my understanding. Also RL-10C conversions begin flying at the end of 2014 to the beginning of 2015.
This is more than the one-at-a-time clearance that was previously performed. ugordon is on the right track. RL-10C conversions will fly on Atlas, not Delta.
-
#27
by
Galactic Penguin SST
on 31 Oct, 2013 17:50
-
Just scrolled by
http://earth-info.nga.mil/GandG/sathtml/satinfo.html and saw this:
Satellite Freq.
PRN/SVN Plane Std # Block
---------+-------+-----+----------+-Scheduled-Upcoming-Launches---------------------------------
30/64 D4 IIF-5 Mid-November 2013...will be given PRN30...after launch,
SVN49 will be assigned PRN06...then SVN36 will be put
into 'spare' status...
Wonder if that's true as of right now?
BTW the spacecraft will go to plane D, slot 4 to replace SVN34 (GPS IIA-13, launched on August 30, 1993), which will in turn become a spare satellite on plane D. SVN64 will use PRN30, now used by the problematic SVN49/GPS IIR-20, which will switch to PRN06. SVN36/GPS IIA-15, which currently uses PRN06, will be switched to a backup role.
-
#28
by
jacqmans
on 17 Nov, 2013 22:28
-
Photo of the Rocket taken today from the media bus as we went out to Pad-41.
-
#29
by
Galactic Penguin SST
on 18 Nov, 2013 22:23
-
-
#30
by
jacqmans
on 19 Nov, 2013 02:40
-
-
#31
by
Chris Bergin
on 05 Dec, 2013 14:46
-
Per L2 Cape Pad schedule, this is not going next. The Delta IV / AFSPC-04 mission is next to launch from SLC-37, on February 27.
-
#32
by
edkyle99
on 05 Dec, 2013 14:51
-
Per L2 Cape Pad schedule, this is not going next. The Delta IV / AFSPC-04 mission is next to launch from SLC-37, on February 27.
Same, or different, rocket?
- Ed Kyle
-
#33
by
Galactic Penguin SST
on 05 Dec, 2013 14:56
-
Per L2 Cape Pad schedule, this is not going next. The Delta IV / AFSPC-04 mission is next to launch from SLC-37, on February 27.
Same, or different, rocket?
- Ed Kyle
Can ULA swap the rocket? (both will use the M+(4,2) configuration)
-
#34
by
russianhalo117
on 05 Dec, 2013 19:08
-
Per L2 Cape Pad schedule, this is not going next. The Delta IV / AFSPC-04 mission is next to launch from SLC-37, on February 27.
Same, or different, rocket?
- Ed Kyle
Can ULA swap the rocket? (both will use the M+(4,2) configuration)
yes they have done it before, I think once
-
#35
by
Chris Bergin
on 05 Dec, 2013 21:06
-
Updating via L2 again. Late Feb NET.
-
#36
by
macpacheco
on 18 Jan, 2014 15:04
-
Just picked up a change in:
http://earth-info.nga.mil/GandG/sathtml/satinfo.htmlSatellite Freq.
PRN/SVN Plane Std # Block
---------+-------+-----+----------+-Scheduled-Upcoming-Launches---------------------------------
30/64 A3 IIF-5 Scheduled for 20 February 2014...will be given PRN30...after
launch, SVN49 will be assigned PRN06...then SVN36 will be
put into 'spare' status...
Before it was late winter / early spring 2014. So perhaps we can adopt NET Feb 20th 2014 ?
-
#37
by
averagespacejoe
on 27 Jan, 2014 02:47
-
Trying to verify the launch window but I heard 8:40 pm EST on 2/20
-
#38
by
input~2
on 27 Jan, 2014 05:45
-
Launch Vehicle/Mission: Delta 4/GPS 2F-5
Date: Feb. 20, 2014
-
#39
by
Chris Bergin
on 28 Jan, 2014 13:11
-
Launch window: 2040-2059L (Pending)
