- \n
- STS-133 UPDATES<\/li>\n
- L2 STS-133 Special Section<\/li>\n
- Click here to Join L2<\/li>\n<\/ul>\n
In terms of the APU operations while docked to the ISS, the MOD FRR noted that flight specific analysis for STS-133\/ULF-5 was completed on Sept. 16 and had been submitted for final review and approval; nonetheless, the approval process was not complete by the time of the MOD FRR and thus could not be closed.<\/p>\n
Final analysis review and acceptance was expected by September 30 and, once approved, will be incorporated into the STS-133\/ULF-5 Flight Rules with \u201cappropriate information.\u201d<\/p>\n
Second, the Hook Requirements for Docked Operations open work included an \u201cAnalysis to examine the docking interface loads that would be experienced with multiple hooks out scenarios.\u201d<\/p>\n
Aerospace & Defense
<\/path>Rocket launch schedules <\/path>Spaceflight news subscription <\/path>\n (adsbygoogle = window.adsbygoogle || []).push({});<\/p>\n
The analysis itself was complete prior to the MOD FRR, like the APU Operations analysis, but was included in the MOD FRR presentation because of its \u201cnew ops\u201d status.<\/p>\n
Updates to the ULF5_C10-2 Hook Requirements for Docked Operations flight rule have already been made and were submitted as a Change Request into the \u201cWorkflow\u201d for STS-133 on Sept. 13.<\/p>\n
All work on this front, as well as all work on the APU Operation while docked arena, carried an Expected Completion Date of Sept. 30.<\/p>\n
Non-Standard Open Work:<\/p>\n
Meanwhile, the Space Transportation Vehicle Division also presented information on the non-standard open work left for the STS-133 pre-launch flow.<\/p>\n
![\"\"](\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2010\/10\/A32.jpg\" "\\"A3\\"")
Overall, three items gained mentions in this category, including some non-standard open work in the LCC\/MEL\/MIL field \u2013 not to be confused with the already completed standard LCC\/MEL\/MIL open work.<\/p>\n\u201cThe Launch Commit Criteria Minimum Equipment List and Mandatory Instrumentation Lists have been reviewed and verified as complete and accurate\u201d with one exception, notes the Space Transportation Vehicle Division MOD FRR presentation \u2013 available for download on L2.<\/p>\n
This exception relates to the different crack pressures discovered on Cabin Relief Valves on OV-103 (Discovery) and OV-104 (Atlantis). \u201cDuring scheduled testing, one of the Cabin Relief Valves on OV-103, and one on OV-104 were found to have different crack pressures than previous (still within requirements).\u201d<\/p>\n
These different Cabin Relief Valve crack pressures mandated an update to the LCC in terms of the upper limits for cabin pressure and Air Lock\/Payload Bay Door pressure sensors.<\/p>\n
In all, the LCN is still working to document the new valves and is expected to approve them and the new pressure limits by Oct. 15 \u2013 prior to the Agency, or SOMD (Space Operations Mission Directorate), FRR on Oct. 19.<\/p>\n
![\"\"](\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2010\/10\/A41.jpg\" "\\"A4\\"")
Secondly, the SSME (Space Shuttle Main Engine) TVC (Thermal Vacuum Chamber) and Elevon Hydraulic Switching Valve failure gained particular note.<\/p>\n\u201cIn response to a S0044 NO-GO call for an SSME TVC switching valve out of config, the risk and credibility of a switching valve failure was reviewed,\u201d notes the MOD FRR presentation.<\/p>\n
The investigation quickly found that no LCC exists for this scenario \u2013 where the \u201csole switching status indicates that a valve has unexpectedly swapped or failed to transition.\u201d Nonetheless, extensive screening showed that these valves have an extensive design requirement, control, and verification process to ensure that they do not fail.<\/p>\n
In fact, the most likely cause of this type of failure \u2013 a contamination of the hydraulic fluid \u2013 is also highly unlikely due the strict controls in place.<\/p>\n
Based on this data, and the review conducted so far, the informal recommendation that no LCC is required for this scenario has been made; this recommendation, and the investigation itself, will be reviewed by the KSC Launch Integration Manager \u2013 at which point a decision will made to either accept or reject the recommendation.<\/p>\n
Seeing as how the Launch Integration Manager was scheduled to review this issue by Oct. 1, it is highly probable that this issue will gain further mention at the SSP FRR on Wednesday.<\/p>\n
STS-133 Specific Articles: http:\/\/www.nasaspaceflight.com\/tag\/sts-133\/<\/p>\n
Finally, as similarly stated in the Standard open work section, the Space Transportation Vehicle Division notes that \u201cAll significant differences from previous flights have been reviewed by FTP, POWG, or other appropriate operations forum and, where required, documented [as] either new procedures or new flight rules.\u201d<\/p>\n
That is, all significant differences were approved expect DAP configuration\/constraints and PM (Pump Module) Venting Attitude Control.<\/p>\n
For the DAP configurations and constraints, \u201cThe current version of the flight rules and crew procedures contain the preliminary data from C. S. Draper Laboratory.\u201d<\/p>\n
At the time of the MOD FRR, the final version of the C.S. Draper Lab memo had not yet been received. The memo was expected by L-30 day (Oct. 1).<\/p>\n
\u201cUpon receipt of the official memo, GNC (Guidance Navigation & Control) will review the document, and update any DAP constraints in the FDF (Flight Data Files) and Flight Rules as required.\u201d<\/p>\n
In addition to the DAP open work, PM venting attitude control for EVA-2 was also of particular discussion and also related to the C.S. Draper Lab.<\/p>\n
\u201cPM Venting Attitude Control Analysis \u2013 The venting of the failed pump module (PM) has been added to EVA 2,\u201d notes the MOD FRR presentation.<\/p>\n
C.S. Draper, at the time of the Readiness Review, was still working to certify Shuttle attitude control via the VRCS (Vernier Reaction Control System) and ALT during the venting of the PM.<\/p>\n
C.S. Draper was expected to complete the certification process by Oct. 1, with documentation of this procedure in the DAP Loads and Constrains Memo as well as in CHIT 8931 following.<\/p>\n
Procedure Updates for RAMBO, MAUI, Water Dumps, and Deorbit Prep Coldsoak:<\/p>\n
In addition to the standard and non-standard work that is reviewed prior to every Space Shuttle mission, preparations for STS-133 also included updates to the nominally performed RAMBO-2 burn, MAUI burn, Waste Water dump, and Deorbit Prep Coldsoak.<\/p>\n
![\"\"](\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2010\/10\/A52.jpg\" "\\"A5\\"")
For RAMBO-2, \u201cDoD (Department of Defense) reported that the window for RAMBO-2 is ~5 minutes versus the original 14 minutes.\u201d<\/p>\nGiven the shortened timeframe for this burn, the RAMBO-2 crew procedures have been reworked to accommodate more flexibility and burn options into the schedule. \u201cPer the DoD request, the procedure was also modified to perform each burn at a specified TIG (Time of IGnition) within an opportunity window instead of simply starting the sequence at a specified MET (Mission Elapsed Time).<\/p>\n
These changes were reviewed by the crew in June and have been updated into the JOIP procedure; the entire updated ORB OPS FS procedure was since submitted for final approval.<\/p>\n
Moreover, the DoD also brought forth a request to update the MAUI burn. \u201cDuring the STS-130 MAUI procedure this accel mode firing resulted in cross coupling which the DoD is afraid could degrade the experiment data.\u201d<\/p>\n
As such, the DoD requested the deletion of the accel mode firing in favor of the full VRCS and PRCS burn but maintained for the PRCS only burn.<\/p>\n
![\"\"](\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2010\/10\/A71.jpg\" "\\"A7\\"")
\u201cIn addition, three MAUI procedures are being placed in the STS-133 ORB OPS FS to cover full sequence and for the PRCS only and VRCS only procedures,\u201d notes the MOD FRR presentation.<\/p>\nAs with the RAMBO-2 changes, the crew reviewed the MAUI changes in June and all necessary steps toward final approval are in place.<\/p>\n
Third on the list of procedural changes review by the MOD was in the water dump category.<\/p>\n
\u201cOn STS-131, a water dump was performed in a biased posigrade attitude when it should have been performed in a retrograde attitude,\u201d notes the MOD presentation. \u201cFlight Rule A2-109 Preferred Attitude for Water Dumps did not cover the FD3 dump situation and an incorrect attitude was chosen for the dump.\u201d<\/p>\n
As such, an updated version of this rule will be implemented for all future Shuttle missions. The new version of the rule will cover cases \u2013 like STS-131 \u2013 where the phasing rate between Shuttle and ISS is greater than 50nm\/rev.<\/p>\n
\u201cIf the phasing rate is greater than 50 nm\/rev, the dump will now be constrained to occur from ten minutes after the relative apogee to fifteen minutes prior to the next relative apogee. This will not negatively affect the dump plan.\u201d<\/p>\n
The necessary changes have been coordinated with and approved by the Flight Techniques Panel and are currently proceeding through the CR system.<\/p>\n
Lastly, the MOD FRR reviewed changes to the Deorbit Prep Coldsoak and Comm Attitudes.<\/p>\n
Under the new rule, a +\/- 10 degree pitch flexibility to the \u201ccurrent biased tail sun inertial Radiator Coldsoak attitude\u201d will be implemented to help improve comm coverage during this phase of orbital free-flight.<\/p>\n
Additionally, \u201cIn an effort to reduce structural thermal gradients and stresses on the vehicle during entry\/landing the new flight rule also specifies a yaw bias to the deorbit thermal\/comm attitude dependent on beta angle (direction of yaw bias opposite of beta angle).\u201d<\/p>\n
Flexibility to the yaw bias has also been included to improve comm coverage during this phase of flight if needed.<\/p>\n
Thus, all \u201cCommand procedures have been reviewed by personnel with command responsibility to assure clarity, completeness and compatibility with this vehicle\/flight\u201d and all personnel are ready and able to execute the command procedures as documented for STS-133.<\/p>\n
(Lead Photograph: Larry Sullivan, NASASpaceflight.com and MaxQ Entertainment)<\/p>\n","protected":false},"excerpt":{"rendered":"
With just under one month to go before the final launch of Discovery, the tell-tale series of Flight Readiness Reviews (FRRs) are underway as NASA prepares to close out the year with the STS-133 flight to the ISS. Among the various items discussed at the STS-133 Mission Operations Directorate (MOD) FRR was the remaining standard and […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"footnotes":"","_links_to":"","_links_to_target":""},"categories":[2],"tags":[3610,9051],"class_list":["post-40640","post","type-post","status-publish","format-standard","hentry","category-news","tag-frr","tag-sts-133"],"acf":[],"_links":{"self":[{"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/posts\/40640"}],"collection":[{"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/comments?post=40640"}],"version-history":[{"count":0,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/posts\/40640\/revisions"}],"wp:attachment":[{"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/media?parent=40640"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/categories?post=40640"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/tags?post=40640"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}