- Joined
- Oct 30, 2009
- Messages
- 14,019
- Reaction score
- 4
- Points
- 0
SpaceX and NASA are nearing completion of the software assurance process, and SpaceX is submitting a request to the Cape Canaveral Air Force Station for a May 19th launch target with a backup on May 22nd.
Thus far, no issues have been uncovered during this process, but with a mission of this complexity we want to be extremely diligent.
WASHINGTON -- In response to today's SpaceX announcement finalizing a new target date for the launch of its Falcon 9 rocket and Dragon spacecraft, NASA issued the following statement from William Gerstenmaier, associate administrator for Human Exploration and Operations at the agency's Headquarters in Washington:
"After additional reviews and discussions between the SpaceX and NASA teams, we are in a position to proceed toward this important launch. The teamwork provided by these teams is phenomenal. There are a few remaining open items but we are ready to support SpaceX for its new launch date of May 19."
{...}
FWIW, SpaceX now is looking at it's first night launch! 4:55 a.m. EDT.
I wonder how can the ISS handle so much traffic in the later years (roughly 4x Soyuz + 5x Progress + 1x ATV + 1x HTV + 3x Dragon + 3x Cygnus per year!)?
Well, there used to be what, 2-3 shuttle flights per year, at least? Without that traffic, other flights are needed to take up the logistical 'slack', so to speak.
I really, really wish SpaceX had considered doing a "rendezvous" with, for example, a Progress cargo vehicle before going directly to the ISS. This would have allowed them to work out the kinks out of any software and hardware beforehand, before risking, in some peoples minds, a $100 billion asset in the ISS.
I'm aware that the docking mechanisms of the Dragon and Progress are not compatible, but it wouldn't actually have to dock with Progress to prove its capability. This is because the Dragon will not dock on its own to the ISS but only come to within close proximity to the station where it will be grappled by the robot arm to link with the station.
So it would suffice to just prove it could come within the specified distance to the Progress, or other orbiting vehicle, and stay within that specified distance without colliding with it. In fact it could do this multiple times with different orbiting craft to give further confidence in its capabilities.
Bob Clark
COTS Demo Flight 2 is the planned second test-flight for SpaceX's uncrewed Dragon cargo spacecraft, Dragon C2+, and the third overall flight for the company's two-stage Falcon 9 launch vehicle. It is expected to be the first American vehicle to visit the International Space Station (ISS) since the end of the Space Shuttle program, and the first commercial spacecraft to ever rendezvous and be berthed with another spacecraft.[2]
The flight is under contract to NASA as the second Dragon mission in the Commercial Orbital Transportation Services (COTS) phase one program. The purpose of the COTS program is to develop and demonstrate commercial sources for cargo re-supply of the ISS.
Initially, the mission was to carry out a fly-by of the ISS, practice rendezvous maneuvers and berthing communications, and return to Earth. In July 2011, NASA gave tentative approval for combining the objectives of COTS 2 and COTS Demo Flight 3 into one flight. The proposed mission will first test rendezvous techniques and communications between Dragon and the ISS. If all goes well, then the mission's next phase would include berthing the Dragon to the ISS using the Canadarm2, staying for almost three weeks, and having astronauts unload cargo, and then load it with Earth-bound cargo. It would then be unberthed and return to Earth with a splashdown in the Pacific Ocean near the California coast.
In December 2011, NASA formally approved the merger of the COTS 2 and 3 missions into the Dragon C2+ flight. There have been several launch date delays since the mission was announced, most recently on 2 May 2012. The new targeted launch date is 19 May. If all the COTS objectives are successfully completed, then the Falcon 9-Dragon system will be certified to start regular cargo delivery missions to the ISS.
Yeah I'm pretty sure we all knew that already...
On this blog post I discuss a proposal of Robert Zubrin to solve the problem of private spacecraft docking with the ISS:
On Commercial Flights to the ISS and "space tugs".
http://exoscientist.blogspot.com/2012/05/on-commercial-flights-to-iss-and-space.html
Bob Clark
One of the key pre-launch requirements for SpaceX’s upcoming Dragon mission to the ISS – the completion of software validation tasks for the spacecraft’s approach and berthing with the orbital outpost – has been passed, pending the expected completion of “action items”. The milestone means the latest launch date target of May 19 now holds a large amount of confidence.
{...}
SpaceX’s Dragon capsule on Tuesday won approval from International Space Station managers to approach and possibly berth with the outpost next week, putting it a step closer to a planned early Saturday launch from Cape Canaveral.
The flight readiness review, which followed up one held in mid-April, confirmed improvements to the Dragon’s software systems and that the station and its crew would be ready to support the unmanned capsule’s arrival.
“Everyone is GO for launch,” NASA said in a Twitter message after the station team completed its review.
{...}
{...}
In a forecast issued today, meteorologists with the Air Force 45th Space Wing said there is a 70 percent chance conditions will be acceptable for launch. The prime concern is the possibility of thick electrically charged clouds. Launching in those conditions could cause the rocket to trigger destructive bolts of lightning in flight.
SpaceX would have a second opportunity to launch next Tuesday. The early forecast for an attempt then calls for a 60 percent chance of acceptable conditions.
{...}
{...}
FLIGHT DAY 1
Prelaunch events:[table="head;width=500"]Time to liftoff,H:M:S|Event
7:30:30|Vehicles are powered on
3:50:00|Commence loading liquid oxygen (LOX)
3:40:00|Commence loading RP-1 (rocket-grade kerosene)
3:15:00|LOX and RP-1 loading complete
0:10:30|Falcon 9 terminal count autosequence starts
0:05:30|Dragon terminal count auto starts
0:02:30|SpaceX Launch Director verifies go for launch
0:02:00|Range Control Officer (USAF) verifies range is go for launch
0:01:00|Command flight computer state to startup, turn on pad deck and Niagara Water
0:00:40|Pressurize propellant tanks
0:00:03|Engine controller commands engine ignition sequence to start
0:00:00|Falcon 9 Launch[/table]
Ascent events:[table="head;width=500"]Time after liftoff,H:M:S|Event
0:01:24|Max Q
0:03:00|1st stage engine shutdown/Main Engine Cut Off (MECO)
0:03:05|1st and 2nd stages separate
0:03:12|Stage 2 engine starts
0:03:52|Dragon nose cone jettisoned
0:09:14|2nd stage engine cut off (SECO)
0:09:49|Dragon separates from 2nd stage[/table]
On orbit operations/initial demonstrations in the far field:[table="head;width=500"]Time after liftoff,H:M:S|Event
0:11:53|Start sequence to deploy solar arrays
0:54:49|Demonstrate absolute GPS
2:26:48|Start GNC Bay door deployment (holds sensors necessary for rendezvous)
2:40:49|Relative navigation sensors checkout, checks LIDAR and Thermal Imager
8:46:52|Demonstrate full abort, demonstrates Dragon’s ability to abort with a continuous burn
9:57:58|Pulsed abort demonstration, checks Dragon’s ability to perform abort using pulsating burns
10:37:58|Demonstrate Dragon’s ability to free drift[/table]
{...}