ebook img

NASA Technical Reports Server (NTRS) 20110010950: Orion Pad Abort 1 Flight Test - Ground and Flight Operations PDF

6.2 MB·English
Save to my drive
Quick download
Download
Most books are stored in the elastic cloud where traffic is expensive. For this reason, we have a limit on daily download.

Preview NASA Technical Reports Server (NTRS) 20110010950: Orion Pad Abort 1 Flight Test - Ground and Flight Operations

Orion Pad Abort 1 Flight Test Ground and Flight Operations Davis Hackenberg [email protected] Wayne Hicks [email protected] The Operations Team with the PA-1 Test Vehicle 1 Presentation Overview •  Operational Planning •  Facilities Preparation •  Integration and Testing •  Flight Ops •  Other Challenges and Successes 2 OPERATIONAL PLANNING 3 Approach to Operational Planning PROCESS PRODUCTS Develop top-level operational concepts and integration sequences. Project’s Concepts, Assumptions, & Constraints Concept of Operations For each major sequence, identify the activities and tasks to perform. Ground Operations Plan Integration Activities and Tasks Hardware Integration Flow Use the task descriptions to identify requirements. Facility Requirements Facility Requirement Documents GSE Plan Ground Support Equipment Requirements GSE IRDs, ICDs, Specs Transportation Plans Transportation Requirements Roles and Responsibilities Knowing the work to be performed and how equipment will be operated, identify the safety hazards and the mitigations. Safety Requirements Documents Systems Safety Hazard Report Safety Hazards & Mitigations Site Safety Plans Emergency Preparedness Plans Develop procedures to perform the integration tasks and to operate equipment. Include safety mitigations. Master Procedures List Procedures Integration & Test Procedures Identify personnel and skills mixes needed to perform tasks and operate equipment. Staffing Plan Ground Operations Team Training Requirements (Plan) Flight Operations Team Training Records 4 Project’s overarching concepts, assumptions, & constraints drove the operational planning Operations Group Responsibilities Considerations drove the Ground Operations planning •  Plan for six flight tests: •  Integrate the Test Vehicle in 2 phases to reduce time •  Two (2) Pad Abort tests spent at launch site •  Four (4) Ascent Abort tests •  For PA-1: •  Prepare the Test Vehicles •  Perform non-hazardous Crew Module integration at •  Build the Launch Facilities NASA Dryden Flight Research Center •  Provide Mission Architecture to •  Assemble Launch Abort System at Launch Site control test vehicle and to •  Perform final hazardous processing at Launch Site capture vehicle performance and aerodynamic data Considerations drove the Mission Operations Architecture •  Perform the flight tests •  Perform flight tests on an equipped test range •  Test range large enough to contain flight trajectories Mandates •  Use Mobile Launch Concept •  Meet ambitious launch schedule •  Protect for late installation of Considerations drove the Launch Faciltiies long lead time and life-limited •  Support both Pad Abort and Ascent Abort tests items •  Provide integration areas for Launch Abort System, •  Use aggressive test and Crew Module, and Abort Test Booster. verification approach •  Launch Complex sited for hazardous ordnance processing and explosives operations 5 Concept of Operations Document established top level vehicle, ground, and flight operations concepts Contents 1. Organizational Roles and Responsibilities 2. Goals and Objectives NASA Project Orion Flight Test Office 3.  Abort Flight Test Scenarios Abort Flight Test 4.  Test Vehicle Concepts Concept of 5.  Ground Operations and Integration Flows Operations 6.  Flight Operations FTO-AFT-OPS-001 7.  Flight Operations for Ares Launch Opportunity January 19, 2007 8.  Training Revision A Purpose •  Identifies organizational roles and responsibilities •  Describes the Test Vehicle, its components and the component functions, and the component providers. •  Described the top-level integrations flows and the integration locations. •  Describes the mission architecture and the roles for conducting the flight operations. •  Conveys top-level guidance from which to start developing requirements and specifications 6 Ground Operations Plan provided the detailed integration flows, activities, and task descriptions Contents (Abbreviated Listing) 1. Roles and Responsibilities 3.  Approach to Development NASA Project Orion Flight Test Office 4.  Ground Planning Documentation Abort Flight Test 5.  Facilities PA-1 Ground 6.  Ground Support Equipment Operations 7.  Initial Integration at Dryden Flight Research Center Plan 8.  Final Integration at WSMR FTO-AFT-OPS-001 9.  Pad Operations at WSMR January 19, 2007 Revision A 10. Recovery and Disposition Activities after Flight Test Purpose •  Provides the detailed hardware integration flows. •  Assembly and integration tasks described in detail. •  Identifies personnel, facility, and equipment resources required to perform each task. •  Includes over 250 storyboards •  Task descriptions provide the starting point for developing procedures. 7 Over 250 Storyboards like this one used pictures to convey the integration sequences 1 1 Each operation linked to Integration Flow 3 2 Activity Sequence includes detailed task descriptions 3 Flight Hardware clearly shown 5 4 •  Crew Module (in this example) 4 Ground Support Equipment: •  Crew Module Transporter 6 •  Crew Module Lift Fixture 4 5 Facility Resources can be identified: 2 •  Aircraft Integration Facility 6 Facility Equipment and placements: •  Mobile Crane •  Load Cell 7 7 Procedures •  Convert Integration Stand to Transporter •  Transport Crew Module •  Critical Lift Pre-Task Planning •  CM Weight Determination Procedure •  “Critical Lift” involves hazardous ops 3 8 Personnel 6 8 •  Task Team Leader •  Tug Operator •  Safety Lead •  Mobilizer Operators 8 •  QA Lead •  Crane Operator •  Lift Manager •  Mechanics 8 Storyboards were good predictors of actual operations Storyboard Actual 9 Storyboard for the Crew Module Iyy Inertia Test Storyboard Actual 10

See more

The list of books you might like

Most books are stored in the elastic cloud where traffic is expensive. For this reason, we have a limit on daily download.