Recommended Posts

https://www.nasa.gov/feature/nasa-spacex-agree-on-plans-for-crew-launch-day-operations

Quote

NASA, SpaceX Agree on Plans for Crew Launch Day Operations

 

NASA's Commercial Crew Program and SpaceX are finalizing plans for launch day operations as they prepare for the company's first flight test with astronauts on board. The teams are working toward a crew test flight to the International Space Station, known as Demo-2, with NASA astronauts Bob Behnken and Doug Hurley in April 2019.  

A key question the program and the company have been assessing is whether the astronauts will climb aboard the Crew Dragon spacecraft before or after SpaceX fuels the Falcon 9 rocket. NASA has made the decision to move forward with SpaceX's plan to fuel the rocket after the astronauts are in place. While the agreement makes this plan the baseline for operations, it is contingent upon NASA's final certification of the operation.

"To make this decision, our teams conducted an extensive review of the SpaceX ground operations, launch vehicle design, escape systems and operational history," said Kathy Lueders, manager of NASA's Commercial Crew Program. "Safety for our personnel was the driver for this analysis, and the team’s assessment was that this plan presents the least risk."

Additional verification and demonstration activities, which include five crew loading demonstrations of the Falcon 9 Block 5, will be critical to final certification of this plan. These loading demonstrations will verify the flight crew configuration and crew loading timeline prior to Demo-2. After these conditions have been met, NASA will assess any remaining risk before determining that the system is certified to fly with crew.

If all goes according to plan, on launch day, the Falcon 9 composite overwrap pressure vessels, known as COPVs, will be loaded with helium and verified to be in a stable configuration prior to astronaut arrival at the launch pad. The astronauts then will board the spacecraft about two hours before launch, when the launch system is in a quiescent state. After the ground crews depart the launch pad, the launch escape systems will be activated approximately 38 minutes before liftoff, just before fueling begins. SpaceX launch controllers then will begin loading rocket grade kerosene and densified liquid oxygen approximately 35 minutes before launch. The countdown and launch preparations can be stopped automatically up to the last moment before launch. In the unlikely event of an emergency at any point up to and after launch, the launch escape systems will allow the astronauts to evacuate safely.

This timeline is consistent with the fueling procedures SpaceX uses for its commercial resupply missions and satellite launches.

The crew launches of NASA’s Commercial Crew partners SpaceX and Boeing will return the nation’s ability to launch our astronauts from the United States to and from the International Space Station on American spacecraft.

 

This seems like the best way to do it to me, in my head, loading the propellant before you get on the rocket seems more dangerous cause your not strapped into a safety mechanism, what happens if there is an issue as you are walking up to the thing.

 

I guess there is a lot of other things to consider, mostly that more issues happen during loading. But every time i just think its safer to be in the capsule with an escape system than not.

Starliner control console. 

 

No touch screens, you use physical buttons to navigate through menus and flip pages. Not unlike some old MSDOS programs. Some features borrowed from Orion. 

 

Still, Boeing stresses it's intended to be an automated taxi.

 

DlEsLaBW0AAu780.jpg

 

 

Edited by DocM

Observe the land of double standards ... sheesh. This is what that Professor (now colleague) of mine was talking about before regarding all of the arbitrary crap being pulled on SpaceX. 2, even 3 times the amount of testing and redundancy relative to everyone else's gear simply to harass and delay them. :no: 

 

Look at 'em. Just look at 'em.

Overpressure from launches causing damage to the tower being the primary reason why. :yes: There are internal upgrades that are going to be going into it once the cladding is installed that have to be protected, and possibly the Crew Access Area is gonna need to be climate controlled too.

 

Then the matter of whether the site will be used to launch BFR or not ... still undecided. South Texas is still a better fit due to logistics. Depends on a bunch of factors, chief among them what the FAA says concerning the planned launch corridor at this point but if the point-to-point BFS flights work out well then it'll alleviate a lot of concerns.

Can't get everywhere shooting the gap between the Keys and Cuba, or going South of Cuba, to avoid overflight issues. The best trajectories look to be GEO, Lunar and interplanetary.

 

For P2P Florida may be better; launch polar-ish then a dogleg to Asia, Oz and NZ. Straight shots to Europe and the ME (KSA is interested, likely UAE as well.)

 

Deployed

 

Edited by DocM
  • Like 1

I completely agree. What I'd like to see are flights out of the Cape, Vandy and South Texas. Use Vandy for polar tracks, ST and KSC for the rest of the flight tracks.

 

Personally I think KSC is the standard option for anything "up and out" (GTO+, TLI, etc), but ST is a better option (or could be made such) from a logistical standpoint. It's much, much closer to SpaceX's facilities than KSC, they don't have to go through a big hassle to get it to the launch site, and the Gulf is a huge body of water in it's own right. The dogleg maneuver isn't that big of a deal in the grand scheme of things and BFR/BFS has tons of spare dV to spend on the inclination change as it shoots the gap between Florida and Cuba.

 

Even if it looks like the dV can't be spared for a mission there's always the potential to launch from KSC and it'll eliminate that issue entirely. :yes: 

 

Speaking of KSC, looks like the tower got a cleaning and a new coat of primer .... :D 

55 minutes ago, Unobscured Vision said:

>

Speaking of KSC, looks like the tower got a cleaning and a new coat of primer .... :D 

 

I'd expect an overcoat before mounting the external panels. Curious as to B&W, metallic or ??

  • Like 1

Likely it'll be a protectant to deal with the salt content (as well as the humidity) in the air. That stuff is rough on metals.

 

End result will likely be a grey-white appearance.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Microsoft's fast coding model MAI-Code-1-Flash comes to Copilot Business and Enterprise by Karthik Mudaliar Microsoft’s recently announced MAI-Code-1-Flash model is now generally available to GitHub Copilot Business and Copilot Enterprise customers. With this support, organizations can have more centralized policy controls and billing while finally being able to use Microsoft’s lightweight, first-party coding model. According to GitHub’s announcement, Business and Enterprise plan administrators must enable the MAI-Code-1-Flash policy in Copilot settings before developers can access the model. Microsoft says that MAI-Code-1-Flash is for fast, iterative coding work rather than the most demanding architectural or debugging tasks. GitHub’s official model comparison page says that the model is great for "general-purpose coding and writing," while it excels at fast, accurate code completions and explanations Microsoft introduced MAI-Code-1-Flash on June 2 as part of a broader collection of internally developed MAI models. GitHub subsequently expanded support to Copilot CLI, the Copilot cloud agent, GitHub.com chat, GitHub Mobile, Visual Studio, JetBrains IDEs, Eclipse, and Xcode, but said support for managed Business and Enterprise customers was still on the way. In Microsoft’s own benchmark testing, MAI-Code-1-Flash scored 51.2% on SWE-Bench Pro, compared with 35.2% for Anthropic’s Claude Haiku 4.5. Microsoft also claimed that the model used up to 60% fewer tokens on SWE-Bench Verified. Do note that these are vendor-run results rather than independent measurements. The model is billed at provider list pricing under GitHub’s usage-based system. GitHub currently lists MAI-Code-1-Flash at $0.75 per million input tokens, $0.075 per million cached input tokens, and $4.50 per million output tokens. For organizations, the main incentive to use MAI-Code-1-Flash is likely to be efficiency rather than maximum capability. A smaller model that responds quickly and limits unnecessary output is quite useful for repetitive agent tasks at scale, especially after GitHub Copilot’s move toward usage-based billing. The "Flash" model is recommended for fast work and not necessarily for huge repositories with loads of context. It's better if teams compare their output with other larger models, especially if they're working on security-sensitive changes and complex, multi-file work.
    • yes AND no the "original" or plain/normal Optiplex 7010 won't be getting any more new firmware updates BUT the Optiplex SFF/SFF Plus {small form factor}, Micro/Micro Plus & Tower/Tower Plus 7010 editions DO get new updates such as this new one   and here are similar guides from the Dell web site for Dell systems: https://www.dell.com/support/kbdoc/en-us/000390990/secure-boot-transition-faq https://www.dell.com/support/kbdoc/en-us/000347876/microsoft-2011-secure-boot-certificate-expiration
    • AT&T has been spying on US citizens with the NSA for decades.. they just know how to keep it more under wraps.. the evil level is still there.
  • Recent Achievements

    • One Year In
      bernmeister earned a badge
      One Year In
    • Week One Done
      Scoobystu earned a badge
      Week One Done
    • Week One Done
      tuben earned a badge
      Week One Done
    • First Post
      OffsetAbs earned a badge
      First Post
    • Reacting Well
      OffsetAbs earned a badge
      Reacting Well
  • Popular Contributors

    1. 1
      +primortal
      462
    2. 2
      +Edouard
      213
    3. 3
      PsYcHoKiLLa
      157
    4. 4
      Steven P.
      72
    5. 5
      FloatingFatMan
      71
  • Tell a friend

    Love Neowin? Tell a friend!