huebner

www.nasa.gov

Ares Design Influence from Ares I-X Flight Data

(as of 12/4/2009)

Lawrence D. HuebnerVehicle Integration Office

Ares Projects Office

Project Management Challenge 2010Galveston, TX

February 9-10, 2010

Special Thanks to James S. Richards

National Aeronautics and Space Administration

Used with Permission

Background and Purpose

2National Aeronautics and Space Administration

♦Performing the Ares I-X flight test early in the Constellation Program manifest allows flight test data to be used by the Ares Projects Office to partially validate and perhaps modify the tools and models being used to design and develop Ares I.

♦This briefing will provide a summary of the plans for Ares I-X flight evaluation and specific examples of how the Ares I-X flight test data will be used for addressing validation of tools, models, and processes.

Ares I-X Ascent Flight Scenario


Ares I-X Flight Test Objectives

Secondary Objectives1. Quantify the effectiveness of the First

Stage separation motors

2. Characterize induced environments and loads on the FTV during ascent flight phases

3. Demonstrate a procedure to determine the vehicle’s pre-launch geodetic orientation vector for initialization of the flight control system

4. Deleted

5. Characterize induced loads on the LV on the launch pad (under review)

6. Assess potential Ares I access locations in the VAB and on the Pad

7. Assess First Stage electrical umbilical performance

Primary Objectives1. Demonstrate control of a vehicle

dynamically similar to the Ares I/Orion vehicle using Ares I relevant flight control algorithms

2. Perform an in-flight separation/staging event between an Ares I-similar First Stage and a representative Upper Stage

3. Demonstrate assembly and recovery of a new Ares I-like First Stage element at KSC

4. Demonstrate First Stage separation sequencing, and quantify First Stage atmospheric entry dynamics, and parachute performance

5. Characterize magnitude of integrated vehicle roll torque throughout First Stage flight


Ares I-X Instrumentation Summary


Description CM/LAS USS IS FS TotalsCalorimeter 8 12 15 62 97Radiometer 6 6Gas Temperature Probe 1 12 13Static Pressure 4 11 8 39 62Differential Pressure 9 9Temperature 21 1 77 99

Thermal Totals 33 25 23 205 286

Description CM/LAS USS IS FS TotalsInternal Microphones 1 1 2 4Accelerometer (LF) 15 16 11 42Accelerometer (HF) 5 3 8Biaxial Accelerometer (LF) 24 24Triaxial Accelerometer (LF) 12 12Triaxial Accelerometer (HF) 3 6 9Strain Gauges 8 8Biaxial Strain Gauge 24 24Triaxial Strain Gauge 12 36 6 54Operational Pressure Transducer 2 2

Structures Totals 21 43 47 76 187

Description CM/LAS USS IS FS TotalsForward Skirt Sep. Pyro Shock 2 2

Shock Totals 0 0 0 2 2

Thermal

Structures

Pyro Shock

CM/LAS USS IS FS TotalsAir Data Vanes 2 25 Hole Probe (10 channels) 10 10Total Air Temperature Probe 2 2SIGI INU 20 20BDM Case Strain 8 8BTM Case Strain 4 4

GN&C/Trajectory Totals 14 0 0 32 46

Description CM/LAS USS IS FS TotalsUnsteady Pressure (HF) 17 8 1 11 37Unsteady Pressure (HF) 9 11 2 22Unsteady Pressure (LF) 66 65 16 92 239

Aero Totals 92 84 19 103 298

Description CM/LAS USS IS FS TotalsVideo Camera 1 4 5

Video Totals 0 1 0 4 5

Description CM/LAS USS IS FS TotalsLockheeed Accelerometer (HF) 6 7 13Master DAU Status 26 13 39Remote DAU Status 12 18 30

House Keeping Totals 0 44 0 38 82

DFI Totals 160 197 89 460 906Notes: LF=Low Frequency, HF=High Frequency, INU=Inertial Navigation Unit

House Keeping

GN&C/Trajectory

Aerosciences

On-Board Video

Development Flight Instrumentation (DFI)Instrumentation that provides engineering data requested by Ares I/Ares I-X discipline leads and elements to enable model verification and detailed information about flight vehicle performance and environments.

Operational Flight Instrumentation (OFI)Instrumentation required to verify the launch readiness and performance of the avionic systems and flight control system for the successful operation of the flight vehicle.608 parameters (FTINU, discrete, analog measurements)

Ares I-X External DFI Sensor Layout


Ares I-X Post-Flight Integrated Plans

Ares I-X Flight Test Data

Post-Flight Data Analysis

• Mission Success

• System Performance

30-60-90 Day Reports

Flight Evaluation• Ares I Use of Ares I-X Data

to Influence the Design: Model & Process PartialValidation

• Updated Ares I Models andProcesses

• Integrated Flight Evaluation Report

Mission Management OfficePlanning: AI1-SYS-DAP

Ares Projects OfficePlanning: CxP 72312

Results AffectingFlight Evaluation

Supporting Products for Flight Evaluation


Ares I-X Post-Flight Data Analysis Baseline Schedule

National Aeronautics and Space Administration 8

Ares I-X Supporting Product Coordination


♦ Plan: Formal product delivery agreement between MMO and APO in place prior to flight.♦ Approach

• Requests from Ares I to Ares I-X for Supporting Products will be formally documented using the Constellation Analysis Integration Tool (CAIT) Task Description Sheets (TDSs)

• Requests coordinated and negotiated with the product supplier prior to submission for formal approval• Formal agreements documented by Ares I (JP10) and Ares I-X (SE&I) signoff of TDSs

♦ TDS Status: All 22 have been approved♦ Ares I-X Supporting Products delivery dates in baseline Flight Evaluation Plan (CxP 72312)

are currently TBR• CR CLV-FITO-0058 in-work to resolve CXP 72312 TBRs.



• Mission Success











Task Description Sheet Summary


Count Number Title Status1 CLV-07-1017 Ares I-X Post-flight Best Estimated Traject

(BET)Approved

2 CLV-07-1018 First Stage Performance Products Approved3 CLV-07-1021 As-Built Hardware Description Approved4 CLV-07-1022 As-Built Instrumentation Description Approved5 CLV-07-1023 Master Events List Approved6 CLV-07-1024 RoCS Performance Approved7 CLV-07-1025 Reconstructed Mass Properties Approved8 CLV-07-1028 Ground Information to Support Acoustic an

Over Pressure TaskApproved

9 CLV-07-1030 MIDDS & Atmospheric Data Approved10 CLV-07-1031 Reconstructed Aerodynamics Approved11 CLV-07-1034 Vehicle Position from Integration of On-Bo

Acceleration MeasurementsApproved

12 CLV-07-1035 Thrust Oscillation Transfer Function Approved13 CLV-07-1038 NASTRAN Structural Models Approved14 CLV-07-1040 Vibroacoustic and Shock Design and Test Data Approved

15 CLV-07-1042 Ground and Cast Glance Imagery at Separation

Approved

16 CLV-07-1043 Model & Specification Data for Instrumentation

Approved

17 CLV-07-1044 Roll Disturbance Torque Assessment and Rolling Moment Model

Approved

18 CLV-07-1049 Ares I-X Photographic Observations from F Stage Ignition to Tower Clear

Approved

19 CLV-07-1052 Upper Stage Simulator Statistical Energy Analysis (SEA) Final Preflight Models

Approved

20 CLV-07-1054 FIRST STAGE PRE-LAUNCH DATA TO SUPP FLIGHT EVALUATION

Approved

21 CLV-07-1056 First Stage Vibroacoustics and Shock Post Flight Analysis Results

Approved

22 CLV-07-1058 Photographs of Installed High Frequency Pressure Transducers

Approved10/22/09

Ares I-X Post-Flight Integrated Plans



• Mission Success












Ares Projects Office Flight Data Utilization Plans


♦Anticipated activities utilizing Ares I-X flight data• Model validation by technical disciplines

– Utilize flight data for model validation.– Update models based on validation effort (if necessary).– Exercise updated models in Ares I vehicle analyses as influenced by Ares I-X

flight data.• This will NOT be completed for all disciplines by IVBR and will impact Element CDRs.

• Elements use available Ares I updated analyses to support their CDRs.• Ares VI integrates element CDR results and performs integrated analyses

for Ares I CDR.

12

Flight Evaluation Plan


♦CxP 72312, “Flight Evaluation Plan for Ares I Use of Ares I-X Flight Data” defines: • Engineering flight evaluation tasks to be executed to support design tool

validation– Primarily organized around technical discipline lines– Task owners responsible for definition and execution

• Task Title• Task Identification Number• Task Owner• Task Content• Task Product• Schedule for Task Product• Supporting Products Required for Task• Flight Measurements Required for Task

• Plans for management of flight evaluation efforts• Documentation of results from tasks

♦Baseline CxP 72312 Released May 19, 2009♦CR is in-work to revise CxP 72312

• Eliminate TBDs and TBRs• Updates reflecting “new” MSFC org. structure• Awaiting completion of agreements on open TDSs

13


Ares I-X Flight Evaluation Task List

Task # Task Title Task ID1 High-Altitude Deceleration (HAD) Model Validation FSS0012 First Stage Thermal Model Validation for Ascent and Re-Entry Heating FSS0023 Validation of First Stage Aft Skirt Vibration Environments Models FSS0034 Application of Ares I-X Thrust Oscillation Forcing Function to Ares I FSS0045 Evaluation of Motor Age on the Ares I-X First Stage Performance FSS0056 Validation of Thrust Oscillation Modeling FSS0067 Updated Ares I Rollout Loads Using Ares I-X Derived Base Acceleration IVSL0018 Updated Ares I Ground Wind Loads Using Ares I-X Ground Measurement System (GMS) Data IVSL0029 Updated Ares I Liftoff Loads Using Ares I-X Flight Data IVSL00310 Perform Loads Reconstruction for Ares I-X IVSL00411 Updated Ares I Separation Loads Using Ares I-X Flight Data IVSL00512 Validation of Vibroacoustic Prediction Methodology and Empirical Scaling Techniques SLD00113 Validation of Separation Pyroshock Attenuation Models SHOCK00114 Aerodynamic Database Generation Process Validation AD00115 Aeroelastic Fluctuating Pressure Model Validation AD00216 Validation of Ascent Aerodynamic Heating Code for Protuberances AT00117 Validation of First Stage Reentry Aerodynamic Heating Code AT00218 SRM Plume Radiation Code Validation AT00319 Validation of Semi-Empirical and Computational Fluid Dynamics (CFD)-Based Solutions for First Stage Plume Convection AT00420 Validation of CFD Code for First Stage Plume Induced Flow Separation AT00521 Validation of CFD Code for Small Motor/Engine Plume Impingement AT00622 Validation of FS RSRM Shutdown Spike Curve Fit Built into Current Models AT00723 Validation of Ares I Liftoff Acoustic Environments AA00124 Validation of Ares I Ascent Acoustic Environments AA00225 Validation of Ares I Venting Analysis Tools VENT00126 Gyrocompass Alignment for Launch GNC00127 Validation of Flight Control System Design Tools GNC00328 Validation of Trajectory Reconstruction Capability TR-PER00129 Validation of Best Estimate Trajectory (BET) Generation Capability TR-PER00230 Validation of SRB Performance Knock-Down TR-PER00331 Validation of First Stage/Upper Stage Separation Dynamics Modeling TR-PER00432 Validation of Vehicle Drift Modeling TR-PER00533 Evaluation of Abort Triggers Using Ares I-X Flight Data TR-PER006

(from CxP 72312, Flight Evaluation Plan for Ares I Use of Ares I-X Flight Data)

14

Typical Flight Evaluation Task Schedule

Time DescriptionL - 2 weeks Analytical Predictions for Comparison Completed

and DocumentedL + 4 days Preliminary Flight Data Available for ComparisonL + 35 days Best Source Flight Data Available for ComparisonL + 36 days Flight Evaluation Kickoff MeetingL + 8 weeks Initial Comparisons of Predicted and Actual Data

Presented to Appropriate Panel/TeamL + 12 weeks Final Comparisons of Predicted and Actual Data

Presented to Panel/Team - Data Comparisons - Model and Process Updates Assessment

L + 20 weeks Panel/Team Review of Final Task Product Completed

L + 22 weeks Technical Management Team Vetting of Final Task Product Completed

L + 24 weeks Updates to Model and/or Process Implemented for use in Ares I Critical Design Review Analyses

L + 26 weeks Task Product Transmitted to Flight Evaluation for Integration into the Final Flight Report

L + 28 weeks Final Flight Evaluation Review PresentationL + 30 weeks Integrated Flight Evaluation Report Delivered

Notes: Bold Font = Flight Evaluation Milestone L = Launch


Flight Evaluation Schedule

♦Ares I-X Flight Evaluation Kickoff Meeting: December 16, 2009

♦Task Products transferred to FEWG: May 19, 2010

♦Final FEWG Presentation/Review: June 2, 2010

♦Final Flight Evaluation Report delivered: June 16, 2010


Flight Evaluation Schedule Based on 10/28/2009 Launch


Flight Evaluation Start(Best Source Data)

Results Vetted by AFSIG/FS CE

Submit Report Input Final FE Report Delivered

11/27/09

Note: Two weeks added to evaluation time for holidays.


Ares I-X Flight Evaluation Task Example 1

18

♦AD001: Aerodynamic Database Generation Process Validation

♦Task Owner: Robert Hall

♦Task Content• Comparison of Ares I-X flight data with preflight database to validate

aerodynamic database generation process (wind tunnel test data and CFD analyses to flight configuration and conditions)

• Based on a comparison between prediction results and flight data, the process will be updated as required

♦Task Product• Technical report with comparisons between preflight predicted data Ares I-X

measured flight data• Report will document process adjustments resulting from evaluation of Ares I-X

data and provide rationale for process adjustments

♦Measurement Summary• 59 High-frequency pressure measurements• 239 Low-frequency pressure measurements


19

♦ AT001: Validation of Ascent Aerodynamic Heating Code CLVMIN for Protuberances

♦ Task Owner: Mark D’Agostino

♦ Task Content• Historical test data from wind tunnel tests has been used to derive existing amplification

factors in the CLVMIN code for protuberances• Ares I-X flight data will be used to validate CLVMIN math models by comparing preflight

prediction data with measured flight data• Based on comparisons, the model and/or amplification factors will be updated as required

♦ Task Product• Technical report with comparisons between preflight Ares I-X prediction levels and

measured flight data for aerodynamic heating for protuberances• Report will document model and amplification factor adjustments resulting from evaluation

of Ares I-X data and provide rationale for model/CLVMIN amplification factor adjustments

♦ Measurement Summary• 36 Calorimeters• 36 Temperatures• 31 Static Pressures



20

♦ AA002: Validation of Ares I Ascent Acoustic Environments

♦ Task Owner: Darren Reed

♦ Task Content• Ares I-X flight data will provide a significant resource for Ares I acoustic model and

process validation• Acceptable geometry, correct Strouhal number, realistic Reynolds number, correct boundary layer

conditions, and a correct relationship between the size of the pressure transducer and the vehicle• Preflight predictions of the Ares I-X ascent acoustic environment will be made using the

Ares I design tools for comparison with the Ares I-X flight data• Updates to Ares I prediction models and processes will be implemented for development

of the Ares I CDR liftoff acoustics environment development

♦ Task Product• Technical report showing the ascent acoustic environment comparisons between preflight

predicted data and Ares I-X measured flight data• Report will document model and process adjustments resulting from evaluation of the

flight data and provide rationale for the adjustments

♦ Measurement Summary• 60 High-frequency unsteady pressure measurements



21

♦GNC003: Validation of Flight Control System Design Tools

♦Task Owner: Mike Hannan

♦Task Content• Validation of Ares I control system design and analysis tools (MAVERIC and

SAVANT)• Comparing measured vehicle response to pre-programmed test inputs to what

the tools predict will contribute to validation of the tools and math models• Thrust Vector Control (TVC) performance will be evaluated by comparing the

actual TVC response to commands with predictions of TVC dynamic model (integral to control system design/performance)

♦Task Product• Technical report showing the comparisons between preflight predicted data and

Ares I-X measured flight data• Report will document Flight Control System design tool adjustments resulting

from evaluation of the flight data and provide the rationale for the adjustments

♦Measurement Summary• 190 OFI measurements


Ares I-X HOSC Responsibilities

♦ Goal of Huntsville Operations Support Center (HOSC) is to provide a single repository for Ares I-X post-flight data

♦ Data includes:• OFI and DFI• Video (ground-based, on-board, and airborne)• Voice• KSC Ground Control System and Rollout Data• KSC Test Data• Ares I-X Critical Math Models• Close Out Imagery• Post-Flight Data Analysis products (BET, Recon Mass properties, SRB/BTM/BDM

performance, RoCS performance, etc.)• Post-Flight Data Analysis reports (30, 60 & 90 day)• Meteorological • Range • NASA Debris Radar

♦ Data not physically stored in HOSC will be available via HOSC portals


Ares I-X Post-Flight Key Data Availability Status(as of 12/4/2009)

♦ Ground data (rollout, pre-launch vehicle health and status) available 48 hours after receipt in the KSC Wave Analysis Lab• Status: Data is now available

♦ OFI, DFI and Video delivered to HOSC at L+3 days from the TEL-4 and JDMTA ground sites• Status: Data available to users at HOSC• Assumes no telemetry processing issues

♦ Final meteorological data available at L+3 days• Status: Data has been delivered to LaRC SE&I GN&C for their use• Official delivery to HOSC for long term storage should occur this week

♦ Range radar data to be delivered to HOSC at L+7 days• Status: Data actually delivered to the HOSC L+3 weeks

♦ Ground based imagery (video, & film) will be available to users at L+14 Days• Status: Data is now available• Access via MSFC Photographic Engineering Analysis Lab web site

♦ NASA debris radar data will be delivered to MSFC from JSC at L+30 days• Status: Data delivered to LaRC SE&I GN&C for their use• HOSC will make this data available to users at L+31 days

♦ Best Source flight data available at L+35 days• Status: Data to be delivered to HOSC on 12/7/2009


Ares Flight Evaluation Working Group (FEWG)

Ares I-X FEWGChairman

David Waits

Ares I-X FEWGStaff

Ares I Vehicle Integration

Chief EngineerR.H. Coates

Ares I First StageChief Engineer

Wendy Cruit

Engineering SupportFunction Manager

Van Woodruff

Ares I ProjectRepresentativeLarry Huebner

Ares I-XChief Engineer

Joe Brunty

Ares I Safety & MissionAssurance Representative

Chris Cianciola


FEWG will coordinate, monitor, integrate, and direct evaluation activities and approve evaluation final results

Final Flight Evaluation Report Outline

♦1.0 EXECUTIVE SUMMARY• Summary of the Ares I Flight Evaluation results• Responsible: FEWG Chairman

♦2.0 INTRODUCTION• Provides a discussion of purpose and scope of the report• Responsible: FEWG Chairman

♦3.0 ARES I-X FINAL MISSION ASSESSMENT RESULTS SUMMARY• Extracted/Summarized from the Ares I-X Mission Management Office (MMO)

90-Day Report (Final Report)• Mission Overview as Executed• Mission Anomalies• Implications/Limitations for Planned Ares I Use of the Ares I-X Flight Results• Responsible: Ares I-X Chief Engineer


Final Flight Evaluation Report Outline

♦4.0 ARES I-X DATA QUALITY REPORT• Describes Overall Quality of the Measured Flight Data• Defines Known Problems in the Measured Flight Data (gaps, noise, etc.)• Responsible: Engineering Support Function Manager

♦5.0 INTEGRATED VEHICLE EVALUATION TASK RESULTS• Products of Integrated Design and Analysis Tasks• Products of Other Integrated Vehicle Tasks• Responsible: Ares I Vehicle Integration Chief Engineer

♦6.0 FIRST STAGE EVALUATION TASK RESULTS• Products of First Stage Systems Tasks• Responsible: Ares I First Stage Chief Engineer


Summary

♦Flight evaluation plans for Ares I use of Ares I-X flight data have been established and are being executed.

♦Presentation provided information on:• Ares I-X flight test objectives and measurement summary• Ares I-X data analysis plan overview• Ares I flight evaluation plan details

• Flight evaluation schedule• Task list• Task schedule• Task examples• Creation of Ares Flight Evaluation Working Group• Flight evaluation report schedule and outline

♦ Intent of flight evaluation task execution is to influence the design of Ares I prior to their Critical Design Review by partial validation of the tools, models, and processes being used by technical disciplines and elements.



BACKUP

28


Ares I-X Primary Objectives Assessment to Support Ares I

Objective Description Status Approach/Ares I Application

P-1 Demonstrate control of a vehicle dynamically similar to the Ares I / Orion vehicle using Ares I relevant flight control algorithms.

♦Ares I-X uses the same overall architecture and augmentation approaches as Ares I.

♦Differences in filtering, anti-drift augmentation. GN&C parameters are dictated by differences in structural dynamics and sensor locations.

P-2 Perform an in-flight separation/ staging event between an Ares I-similar First Stage and a representative Upper Stage.

♦Considering the differences with Ares I separation, Ares I-X provides flight data to evaluate or characterize: • First Stage thrust side load at separation.• Effectiveness of BDMs.• Timing of events.• Shock attenuation via pyro shock sensors.• Basic kinematics of separation.

P-3 Demonstrate assembly and recovery of a new Ares I-like First Stage element at KSC.

♦Ares I-X is a pathfinder vehicle for stacking, assembly, and recovery operations at KSC.

P-4 Demonstrate First Stage separation sequencing, and quantify First Stage atmospheric entry dynamics, and parachute performance.

♦Ares I-X demonstrates first stage tumble, re-entry, deceleration using prototype parachutes, as well as tow-back and lift of first stage, but not secondary separation of interstage.♦Flight data will be used to assess first-stage atmospheric entry dynamics models.

P-5 Characterize magnitude of integrated vehicle roll torque throughout First Stage flight.

♦Agreement on requirement to perform PTI maneuvers to obtain total (aerodynamic and RSRM-induced) roll data via RoCS“blackout” intervals.

G

G

G

YG

YG

29


Ares I-X Secondary Objectives Assessment to Support Ares I

Objective Description Status Approach/Ares I Application

S-1 Quantify the effectiveness of the First Stage separation motors.

♦Booster Deceleration Motors incorporate case strain measurements to know the motor fired and infer performance.

S-2 Characterize induced environments and loads on the FTV during ascent flight phases.

♦A significant percentage of the Development Flight Instrumentation sensors will be used to satisfy this objective.

♦Roughly one-third of the sensors are of particular interest to Ares.

S-3 Demonstrate a procedure to determine the vehicle’s pre-launch geodetic orientation vector for initialization of the flight control system.

♦Ares I-X employs a FTINU. Ares I will employ a FTINU derived system and estimate the initial attitude in a like manner.

♦Gyrocompass alignment (GCA) tests have been conducted in the VAB and validated with optical measurements.

♦Objective will be satisfied upon acceptance of GCA data.

S-5 Characterize induced loads on the LV on the launch pad.

♦Ground Measurement List with 79 sensors coordinated by GS, GO, Ares Projects Office, and Ares I-X to satisfy this objective.

S-6 Assess potential Ares I access locations in the VAB and on the Pad.

♦Ares I personnel witnessed stacking operations and modal surveys in VAB HB3.

S-7 Assess First Stage electrical umbilical performance.

♦Ares I-X will provide initial understanding and assessment of the electrical umbilical location and performance for incorporation into the Ares I configuration.

G

G

G

G

G

G

30

Silver Bullet Sensor Summary

♦ In January 2009, NESC Technical Fellow for Aerosciences, engaged the Cx and engineering community to identify a subset of current non-mandatory DFI for potential reclassification• Those sensors that we (the customers) would expend “silver bullets” to keep on Ares I-X

♦ Technical prioritization by region (total of 276 measurements):1. RoCS

• Sensors: Unsteady pressure (buffet and aeroacoustic) and thermal instruments• Rationale: Addresses aeroacoustic environment estimation and RoCS plume thermal environments

2. Frustum/Forward Skirt• Sensors: Unsteady pressures• Rationale: Addresses buffet and aeroacoustic pressure environments and static pressure prediction, liftoff

acoustics, and RoCS plume impingement. Wind-tunnel results are significantly different from predictions3. Aft Skirt

• Sensors: Thermal sensors and unsteady pressures• Rationale: Addresses prediction of thermal environments, static pressures, and liftoff acoustics

4. Instrument Unit• Sensors: Unsteady pressures• Rationale: Liftoff and ascent acoustics at a known critical location for Ares I

5. CM/SM Interface• Sensors: Unsteady pressures• Rationale: Addresses fluctuating pressure environments with greatest prediction uncertainty

(shock/separation alternating flow - art vs. science), liftoff acoustics. Wind-tunnel results are significantly different from predictions




32

♦FSS006: Validation of Thrust Oscillation Modeling

♦Task Owner: Tom Nesman

♦Task Content• Reconstructed Solid Rocket Motor performance data coupled with measured

forward end pressure for oscillation amplitude and frequency content• Analysis results compared with historical data from ground tests and Shuttle

flights to validate applicability of the modeling used in Ares I design

♦Task Product• Technical report with comparisons between preflight Ares I-X prediction levels

and Ares I-X reconstructed and measured flight data• Report will document model adjustments resulting from evaluation of Ares I-X

data and provide rationale for model adjustments

♦Measurement Summary• 2 Motor dome pressures from Operational Flight Instrumentation (OFI)• 2 Motor dome pressures from Development Flight Instrumentation (DFI)



33

♦ IVSL004: Perform Loads Reconstruction for Ares I-X

♦ Task Owners: Tom Howsman/Dave McGhee

♦ Task Content• Load reconstruction analysis using Ares I-X Best Estimated Trajectory, Day of Launch

wind measurements, and DFI accelerations• Analysis includes quasi-static aerodynamic, gust, maneuvering, and buffet loads

• Loads from analysis will be compared with Ares I-X flight test data.• Comparison results used to update models and processes in Ares I loads design analyses

♦ Task Product• Technical report with Ares I-X loads analysis results, loads from Ares I-X flight, and a

comparison of the two sets of results• Report will document any changes made to loads models and processes used in Ares I

design analyses and rationale for those changes

♦ Sensor Summary• 54 acceleration measurements• 86 strain gauge measurements• 10 measurements from 5-hole probe• 2 air data vane measurements

• 2 total air temperature measurements• 2 operational pressure transducers• 10 channels from Space-Integrated

GPS/INS Inertial Navigation Unit



34

♦ TR-PER004: Validation of First Stage/Upper Stage Separation Dynamics Modeling

♦ Task Owner: Charles Adams

♦ Task Content• Ares I-X flight data will be used to partially validate the MAVERIC FS/US separation

dynamics modeling process• Individual stage dynamics (FS and US) derived from measured FS rates, ground-based

and airborne imagery, and range radar data will be compared with MAVERIC model results

• Adjustments to MAVERIC and/or the process by which the separation dynamics are analyzed will be made and documented prior to generation of the Ares I CDR stage separation analyses

♦ Task Product• Technical report showing comparisons between post-flight model results and Ares I-X

measured flight data• Report will document MAVERIC tool adjustments and the separation analysis process

adjustments resulting from evaluation of the flight data and provide the rationale for the adjustments

♦ Measurement Summary• 190 OFI measurements

huebner

Technology

x flight evaluation

x flight dataas

ares iares

new ares

potential ares

x flight test data

flight control system

flight vehicle performance