News from today's CFT briefing:
* CFT planned for early February 2023.
* ISS program still plans to alternate Starliner & Crew Dragon missions, one each per year.
* The four major issues from OFT-2 have been resolved:
** OMAC thruster issues likely due to debris -- CFT inspected to ensure it won't happen again.
** RCS thruster problems due to sensor timing issues -- Timing tweaked in mission data load.
** Thermal Conditioning System high pump pressures due to flow restrictions -- Some unneeded filters removed.
** VESTA navigation system generated more data than expected -- Flight software altered to accommodate the data.
* Service Module and Crew Module to be mated in November.
* Work flow supports a February 2023 CFT.
* Boeing is working to have a Starliner ready for PCM-1 in Fall 2023!
* Atlas through PCM-6. Boeing in talk with launch providers about what to do after that; will likely make decision early next year.
* CFT will use the same (but slightly enhanced) short-term solution for the sticky NTO valve problem as was used on OFT-2, but they are redesigning the valve (better moisture sealing; change in material), possibly ready in time for PCM-1.
Some quotes:
4:41Currently we are targeting a launch date as early as February of 2023. It's a busy time frame around there, and so early February is likely the best windowms]best window.
6:21As you know, long term, we're planning a Starliner visit once a year. Steve mentioned Suni [Sunita Williams] and Butch [Barry Wilmore]. We expect this mission to be docked about eight days. We're still working the details, but think approximately eight days or so. Butch and Suni, in addition to the Starliner activities, we're going to have them do ISS activities, whether it be research utilization and commercialization work or technology delopment, just like we did with Bob and Doug when they were on their SpaceX test mission.
7:43The OFT-2 flight, we reported after the mission, was very successful and we were very happy with the observed performance of all our hardware, our software, and of course our team. After the flight we did a lot of in-depth post-test analysis. There are 252 FTOs, or Flight Test Objectives, that we had planned, and we went through and looked at all the data associated with all of those FTOs. And we're just wrapping up with the final report now. Matter of fact, we turn it in tomorrow. So based on that analysis we're even more pleased with how the flight performed, and we're very much looking forward to flying crew on CFT next.
9:22Four major areas needing to be looked at and understood really well and then driving some changes for CFT.
The first one was the OMAC [Orbital Maneuvering and Attitude Control] thrusters. If you remember, during the flight we had two thrusters that were deselected during orbital insertion. There was very in-depth fault tree analysis that was performed, and it was determined -- or it's being determined and we're working toward flight rationale -- that we had some debris related conditions that resulted in the deselection and reselecting other thrusters to enable the orbital insertion. So we have done all the inspections required on CFT to make sure that that same condition doesn't exist, and we're ready to move toward the flight rationale once we complete all of the fault tree analysis. But we've done everything we need to do on CFT to clear it.
10:17Also on the Service Module and the Crew Module there were RCS thrusters that were deselected as well. We've determined that the main leading cause of that is low inlet pressures and some manifold dynamics that delayed the sensor responses, and those can be remedied by a very small change to the mission data load that's prepared for each mission. So it's really a tweak of timing and tolerances to be able to make sure that doesn't happen to us again. So that's all in work for CFT.
10:53The active thermal conditioning system -- you remember we had some high pump pressures that were detected during the mission. So we've determined that that was due to a restriction of flow through the lines. There were some filters in the system that we've determined are really not required, and so we've removed those filters to alleviate that problem from happening again in the future.
11:24And then in the area of the VESTA [Vision-based, Electro-optical Sensor Tracking Assembly] performance. The VESTA system performed very well, but we found that it was collecting quite a bit of data and was more data than could be managed. So we've altered our flight software to accommodate this increase in data, and that's all part of a software revision that's currently in work.
11:49So all that work, along with the team carefully reviewing the flight software and CFT vehicle, all that has resulted in accepting the conditions for CFT for flight. All this work has been planned into our schedules and we've determined that launch readiness date that Steve talked about in the February time frame. Of course as we get closer to that date we'll be able to get an exact date for you.
The preparation of the vehicle on CFT is going extremely well. The Service Module and the Crew Module are on plan, scheduled to be mated in the November time frame. The engineering products, the VCNs [Verification Closure Notices], and all the hazard reports are all in work and we have good plans that get us to support that date in February. And then we have one flight software revision that we're doing that also will support the early February opportunity. Mission operations planning and simulations and training is all in work, and again all will support the schedule. So we're in good shape to execute these plans to be ready for that flight in February.
13:06One other added area is PCM-1 [Post Certification Mission 1]. We have gone through all the same process of baselining our schedules and understanding everything that needs to be completed and we're targeting a Fall opportunity. Both the Crew Module and the Service Module are also in work on the floor, so we have four vehicles in flow in the C3PF [Commercial Crew and Cargo Processing Facility], and when we get closer to vehicle readiness we'll be working a launch date with Steve and company as well.
Q&A:
14:03Stephen Clark - Spaceflight Now: Was it work on those 4 main areas that pushed CFT from end of year 2022 to February 2023?
Mark Nappi: Yes.
15:14Joey Roulette - Reuters: Any other problems than those 4 main areas? Also, any plans to certify Vulcan for Starliner?
Mark Nappi:"I'll start with the second half first. We are certainly looking at the launch vehicle integration for when we run out of Atlases after PCM-6. So yes, that is actively in work. Our teams are working with the launch vehicle providers for that, and we'll be having to make a decision probably sometime early next year on what we're going to go do as moving forward." Re first half: There were a number of smaller items as well, with corrections implemented into the flow, but the 4 outlined were the major ones which impacted the schedule.
Steve Stitch: Other minors issues -- such as having to reboot the NASA Docking System. But nothing else really major. "Overall the flight went extremely well."
17:55Jeff Foust - SpaceNews: What other station activities in the Feburary 2023 time frame?
Steve Stitch: Late February is pretty busy preparing for a Soyuz handover in early March, then the Crew-5 / Crew-6 handover.
Joel Montalbano: First six months of 2023 incredibly busy with SpaceX Cargo mission, Crew-5 / Crew-6 handover, Soyuz handover, Progress mission, Northrop Grumman mission, and an Axiom-2 mission as well. "From a priority standpoint, CFT is a big deal for us. Our Agency goal is to get two US commercial providers up and running as soon as we can. And so when these guys are ready in February, we'll be making sure there's room for them. And they will be high priority unless we're working a major issue onboard Space Station."
20:23Irene Klotz - Aviation Week: What's up with the valve redesign [for the sticky NTO valves which scrubbed the 2021 OFT-2 attempt]?
Mark Nappi: Recapped problem and near-term solution for OFT-2. Problem did not reoccur on OFT-2. Will fly the same near-term solution on CFT, but enhanced slightly since incorporated during build. Also actively working on a valve redesign "to completely seal the areas where moisture can come in and to change the material from aluminum to something probably closer to CRES [Corrosion Resistant (Stainless) Steel] so that we don't see the same type of combination of issues that will create corrosion. That design schedule has been laid out. It's tight for PCM-1, so we have to go work that schedule to see if we can get it in for PCM-1. If we can't then obviously we have other alternatives. But our goal is to try to get it done as soon as possible."
23:03Tim Fernholz - Quartz: Any non-NASA customers for Starliner in the works? Will Starliner be profitable?
Mark Nappi: Boeing's priority is meeting commitments to NASA, flying PCM-1 through 6. But Boeing is also looking at what can be done to increase the profitability of the program. "There are a number of things we are actively working, as in the PAM [Private Astronaut Missions] missions, we have an opportunity to create a 5th seat for our vehicle, and then there are other opportunities in Low Earth Orbit. There seems to be a very big market for us to address. In order to do that, there's quite a bit of activity in our company to determine how do we want to work on our vehicle to make it long lasting and something that can be turned around quickly and be able to support the number of missions that are out there in our Low Earth Orbit market. We are actively working that to understand what we can go accomplish."
24:56Marcia Dunn - Associated Press: What was the source of the debris behind the OMAC thruster problem?
Mark Nappi: "Unfortunately we don't get the hardware back. So we will never know exactly what was the issue." Fault tree analysis suggests debris as leading root cause -- could make a number of guesses as to source, but don't know. Inspection ensures it will not be an issue for CFT.
26:44Marcia Smith - SpacePolicyOnline.com: How disruptive have Dragon capsule return weather delays been, and will this be less of an issue with Starline?
Steve Stitch: Meeting Dragon return weather criteria has been challenging, but Starliner will also have wind limits for landing which may be equally challenging, though we did have good conditions for OFT-1 & 2.
Joel Montalbano: Mission extensions do cause a small impact with consumables, though about a week's worth is planned for; the good thing is that the astronauts are tasked with additional work during a mission extension. There's always more work to do on Station than people to do it.
29:50David Kerley - Discovery Channel: What plans are there for crew accommodations during handovers?
Joel Montalbano: We now have an extra sleep station in the Columbus module called CASA [Crew Alternate Sleep Accommodation]; crew can sleep in visiting vehicles; there's extra room in Columbus module and in the airlock. Sleep arrangements are planned in advance in coordination with the crews, and each crew has their own preference, but the extra crew is easy to accommodate for the short amount of time of a handover.
31:09Stephen Clark: Is Boeing still a launch vehicle agnostic spacecraft, and is Boeing really looking at other providers than ULA?
Mark Nappi: Yes, Boeing is looking at different options; it's just part of the business. Yes, Starliner is launch vehicle agnostic, but not easily so, given the need for different adapters and launch operations with different providers.
32:35Irene Klotz: Can you discuss the new requirements for PAM [Private Astronaut Mission] missions?
Kathryn Lueders: Learned a lot from Axiom-1. At least for next couple PAM missions we will require an experienced crew member to support the other PAM members to ensure the PAM operations go smoothly. The PAM operations went smoothly as a joint team with Axiom-1, but we will continue to learn as we go.
36:50Joey Roulette: When will Soyuz / Starliner seat swaps start?
Joel Montalbano: Will start working that this fall. Current Integrated Crew Agreement is for one flight per year in 2022, 2023, & 2024 with Soyuz / Crew Dragon seat swaps, but as soon as the September / October campaigns are over we will work on trying to fold in Boeing and make it a long-term agreement with a seat swap on every flight. The goal is a modification to the existing agreement, with Starliner on the same terms as Crew Dragon, that being a no-cost barter, regardless of the vehicle.
38:50David Kerley: What is the protocol for testing Starliner flight software revisions?
Mark Nappi: Rigorous software release process: choice (by Boeing & NASA) of items to be included in a new revision; coordination through a Program Control Board; then the software change process itself with a rigorous set of software sprints, exhaustive testing through the simulation and labs, released as version and tested again with more parties. Just recently, at end of July, identified items to go into Rev 1.5.2, and they are now going through that rigorous process and won't be released until late October / early November.
David Kerley: Is it tested once it's on the vehicle?
Mark Nappi: "Absolutely."
Steve Stitch: NASA team follows along with every software change. Boeing's ASIL [Avionics and Software Integration Lab] facility is a replica of the avionics system with the flight software for testing. It is also deployed to simulators and tested with crew training. NASA has also implemented an ASIL mission rehearsal where all the sequences used for flight are run through. Same process used for OFT-2, and software performed very well for that flight.
42:16Kathryn Lueders: Closing remarks: Teams are working together well toward the early 2023 CFT. Everyone wishes Artemis well on *its* uncrewed test flight. "Go Artemis!"
⬛