Search NASA⌕ Search

SEARCH · Search NASA

Results for “PROGRAMMING”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 613 records · Page 34

Model Checker for Java Programs

Java Pathfinder (JPF) is a verification and testing environment for Java that integrates model checking, program analysis, and testing. JPF consists of a custom-made Java Virtual Machine (JVM) that interprets bytecode, combined with a search interface to allow the complete behavior of a Java program to be analyzed, including interleavings of concurrent programs. JPF is implemented in Java, and its architecture is highly modular to support rapid prototyping of new features. JPF is an explicit-state model checker, because it enumerates all visited states and, therefore, suffers from the state-explosion problem inherent in analyzing large programs. It is suited to analyzing programs less than 10kLOC, but has been successfully applied to finding errors in concurrent programs up to 100kLOC. When an error is found, a trace from the initial state to the error is produced to guide the debugging. JPF works at the bytecode level, meaning that all of Java can be model-checked. By default, the software checks for all runtime errors (uncaught exceptions), assertions violations (supports Java s assert), and deadlocks. JPF uses garbage collection and symmetry reductions of the heap during model checking to reduce state-explosion, as well as dynamic partial order reductions to lower the number of interleavings analyzed. JPF is capable of symbolic execution of Java programs, including symbolic execution of complex data such as linked lists and trees. JPF is extensible as it allows for the creation of listeners that can subscribe to events during searches. The creation of dedicated code to be executed in place of regular classes is supported and allows users to easily handle native calls and to improve the efficiency of the analysis.

Visser, Willem↗

Programs for Testing Processor-in-Memory Computing Systems

The Multithreaded Microbenchmarks for Processor-In-Memory (PIM) Compilers, Simulators, and Hardware are computer programs arranged in a series for use in testing the performances of PIM computing systems, including compilers, simulators, and hardware. The programs at the beginning of the series test basic functionality; the programs at subsequent positions in the series test increasingly complex functionality. The programs are intended to be used while designing a PIM system, and can be used to verify that compilers, simulators, and hardware work correctly. The programs can also be used to enable designers of these system components to examine tradeoffs in implementation. Finally, these programs can be run on non-PIM hardware (either single-threaded or multithreaded) using the POSIX pthreads standard to verify that the benchmarks themselves operate correctly. [POSIX (Portable Operating System Interface for UNIX) is a set of standards that define how programs and operating systems interact with each other. pthreads is a library of pre-emptive thread routines that comply with one of the POSIX standards.]

Katz, Daniel S.↗

Advancing Systems Engineering Excellence: The Marshall Systems Engineering Leadership Development Program

As NASA undertakes increasingly complex projects, the need for expert systems engineers and leaders in systems engineering is becoming more pronounced. As a result of this issue, the Agency has undertaken an initiative to develop more systems engineering leaders through its Systems Engineering Leadership Development Program; however, the NASA Office of the Chief Engineer has also called on the field Centers to develop mechanisms to strengthen their expertise in systems engineering locally. In response to this call, Marshall Space Flight Center (MSFC) has developed a comprehensive development program for aspiring systems engineers and systems engineering leaders. This presentation will summarize the two-level program, which consists of a combination of training courses and on-the-job, developmental training assignments at the Center to help develop stronger expertise in systems engineering and technical leadership. In addition, it will focus on the success the program has had in its pilot year. The program hosted a formal kickoff event for Level I on October 13, 2009. The first class includes 42 participants from across MSFC and Michoud Assembly Facility (MAF). A formal call for Level II is forthcoming. With the new Agency focus on research and development of new technologies, having a strong pool of well-trained systems engineers is becoming increasingly more critical. Programs such as the Marshall Systems Engineering Leadership Development Program, as well as those developed at other Centers, help ensure that there is an upcoming generation of trained systems engineers and systems engineering leaders to meet future design challenges.

Hall, Philip↗

Program Calculates Forces in Bolted Structural Joints

FORTRAN 77 computer program calculates forces in bolts in the joints of structures. This program is used in conjunction with the NASTRAN finite-element structural-analysis program. A mathematical model of a structure is first created by approximating its load-bearing members with representative finite elements, then NASTRAN calculates the forces and moments that each finite element contributes to grid points located throughout the structure. The user selects the finite elements that correspond to structural members that contribute loads to the joints of interest, and identifies the grid point nearest to each such joint. This program reads the pertinent NASTRAN output, combines the forces and moments from the contributing elements to determine the resultant force and moment acting at each proximate grid point, then transforms the forces and moments from these grid points to the centroids of the affected joints. Then the program uses these joint loads to obtain the axial and shear forces in the individual bolts. The program identifies which bolts bear the greatest axial and/or shear loads. The program also performs a fail-safe analysis in which the foregoing calculations are repeated for a sequence of cases in which each fastener, in turn, is assumed not to transmit an axial force.

Buder, Daniel A.↗

Web Program for Development of GUIs for Cluster Computers

WIGLAF (a Web Interface Generator and Legacy Application Facade) is a computer program that provides a Web-based, distributed, graphical-user-interface (GUI) framework that can be adapted to any of a broad range of application programs, written in any programming language, that are executed remotely on any cluster computer system. WIGLAF enables the rapid development of a GUI for controlling and monitoring a specific application program running on the cluster and for transferring data to and from the application program. The only prerequisite for the execution of WIGLAF is a Web-browser program on a user's personal computer connected with the cluster via the Internet. WIGLAF has a client/server architecture: The server component is executed on the cluster system, where it controls the application program and serves data to the client component. The client component is an applet that runs in the Web browser. WIGLAF utilizes the Extensible Markup Language to hold all data associated with the application software, Java to enable platform-independent execution on the cluster system and the display of a GUI generator through the browser, and the Java Remote Method Invocation software package to provide simple, effective client/server networking.

Czikmantory, Akos↗

Evaluation of NASA SPoRT's Pseudo-Geostationary Lightning Mapper Products in the 2011 Spring Program

NASA's Short-term Prediction Research and Transition (SPoRT) program is a contributing partner with the GOES-R Proving Ground (PG) preparing forecasters to understand and utilize the unique products that will be available in the GOES-R era. This presentation emphasizes SPoRT s actions to prepare the end user community for the Geostationary Lightning Mapper (GLM). This preparation is a collaborative effort with SPoRT's National Weather Service partners, the National Severe Storms Laboratory (NSSL), and the Hazardous Weather Testbed s Spring Program. SPoRT continues to use its effective paradigm of matching capabilities to forecast problems through collaborations with our end users and working with the developers at NSSL to create effective evaluations and visualizations. Furthermore, SPoRT continues to develop software plug-ins so that these products will be available to forecasters in their own decision support system, AWIPS and eventually AWIPS II. In 2009, the SPoRT program developed the original pseudo geostationary lightning mapper (PGLM) flash extent product to demonstrate what forecasters may see with GLM. The PGLM replaced the previous GLM product and serves as a stepping-stone until the AWG s official GLM proxy is ready. The PGLM algorithm is simple and can be applied to any ground-based total lightning network. For 2011, the PGLM used observations from four ground-based networks (North Alabama, Kennedy Space Center, Oklahoma, and Washington D.C.). While the PGLM is not a true proxy product, it is intended as a tool to train forecasters about total lightning as well as foster discussions on product visualizations and incorporating GLM-resolution data into forecast operations. The PGLM has been used in 2010 and 2011 and is likely to remain the primary lightning training tool for the GOES-R program for the near future. This presentation will emphasize the feedback received during the 2011 Spring Program. This will discuss several topics. Based on feedback from the 2010 Spring Program, SPoRT created two variant PGLM products, which NSSL produced locally and provided in real-time within AWIPS for 2011. The first is the flash initiation density (FID) product, which creates a gridded display showing the number of flashes that originated in each 8 8 km grid box. The second product is the maximum flash density (MFD). This shows the highest PGLM value for each grid point over a specific period of time, ranging from 30 to 120 minutes. In addition to the evaluation of these two new products, the evaluation of the PGLM itself will be covered. The presentation will conclude with forecaster feedback for additional improvements requested for future evaluations, such as within the 2012 Spring Program.

Stano, Geoffrey T.↗

The Integration and Test Program of the James Webb Space Telescope

The James Webb Space Telescope (JWST) project has entered into a comprehensive integration and test (I&T) program that over the coming years will assemble the various elements of the observatory (the Optical Telescope Element [OTE], the Integrated Science Instrument Module [ISIM], and the Spacecraft) and verify the readiness of the integrated system for launch. The I&T program as replanned for a 2018 launch readiness date has a number of interesting features. These include a streamlined ISIM cryo-vacuum test program at Goddard Space Flight Center, a streamlined OTIS (OTE + ISIM) test program at Johnson Space Center (JSC), the addition of a second Core cryo-vacuum thermal test, the enhancement of the Pathfinder program at JSC, and enhancement of the subsystem-level testing program for the MIRI cryo-cooler. These latter activities all serve to reduce the risk heading into the end-to-end optical and thermal testing of the telescope at JSC, leading to reduced cost and schedule risk for that critical activity. We report here on the overall I&T program for JWST and on the status of the hardware and plans that support it.

Kimble, Randy↗

National Report on the NASA Sounding Rocket and Balloon Programs

The U. S. National Aeronautics and Space Administration (NASA) Sounding Rockets and Balloon Programs conduct a total of 30 to 40 missions per year in support of the NASA scientific community and other users. The NASA Sounding Rockets Program supports the science community by integrating their experiments into the sounding rocket payloads, and providing both the rocket vehicle and launch operations services. Activities since 2011 have included two flights from Andoya Rocket Range, more than eight flights from White Sands Missile Range, approximately sixteen flights from Wallops Flight Facility, two flights from Poker Flat Research Range, and four flights from Kwajalein Atoll. Other activities included the final developmental flight of the Terrier-Improved Malemute launch vehicle, a test flight of the Talos-Terrier-Oriole launch vehicle, and a host of smaller activities to improve program support capabilities. Several operational missions have utilized the new Terrier-Malemute vehicle. The NASA Sounding Rockets Program is currently engaged in the development of a new sustainer motor known as the Peregrine. The Peregrine development effort will involve one static firing and three flight tests with a target completion data of August 2014. The NASA Balloon Program supported numerous scientific and developmental missions since its last report. The program conducted flights from the U.S., Sweden, Australia, and Antarctica utilizing standard and experimental vehicles. Of particular note are the successful test flights of the Wallops Arc Second Pointer (WASP), the successful demonstration of a medium-size Super Pressure Balloon (SPB), and most recently, three simultaneous missions aloft over Antarctica. NASA continues its successful incremental design qualification program and will support a science mission aboard WASP in late 2013 and a science mission aboard the SPB in early 2015. NASA has also embarked on an intra-agency collaboration to launch a rocket from a balloon to conduct supersonic decelerator tests. An overview of NASA's Sounding Rockets and Balloon Operations, Technology Development and Science support activities will be presented.

Eberspeaker, Philip↗

Improve Problem Solving Skills through Adapting Programming Tools

There are numerous ways for engineers and students to become better problem-solvers. The use of command line and visual programming tools can help to model a problem and formulate a solution through visualization. The analysis of problem attributes and constraints provide insight into the scope and complexity of the problem. The visualization aspect of the problem-solving approach tends to make students and engineers more systematic in their thought process and help them catch errors before proceeding too far in the wrong direction. The problem-solver identifies and defines important terms, variables, rules, and procedures required for solving a problem. Every step required to construct the problem solution can be defined in program commands that produce intermediate output. This paper advocates improved problem solving skills through using a programming tool. MatLab created by MathWorks, is an interactive numerical computing environment and programming language. It is a matrix-based system that easily lends itself to matrix manipulation, and plotting of functions and data. MatLab can be used as an interactive command line or a sequence of commands that can be saved in a file as a script or named functions. Prior programming experience is not required to use MatLab commands. The GNU Octave, part of the GNU project, a free computer program for performing numerical computations, is comparable to MatLab. MatLab visual and command programming are presented here.

Shaykhian, Linda H.↗

C++ Programming Language

C++ Programming Language: The C++ seminar covers the fundamentals of C++ programming language. The C++ fundamentals are grouped into three parts where each part includes both concept and programming examples aimed at for hands-on practice. The first part covers the functional aspect of C++ programming language with emphasis on function parameters and efficient memory utilization. The second part covers the essential framework of C++ programming language, the object-oriented aspects. Information necessary to evaluate various features of object-oriented programming; including encapsulation, polymorphism and inheritance will be discussed. The last part of the seminar covers template and generic programming. Examples include both user defined and standard templates.

Shaykhian, Gholam Ali↗

Station Program Note Pull Automation

Upon commencement of my internship, I was in charge of maintaining the CoFR (Certificate of Flight Readiness) Tool. The tool acquires data from existing Excel workbooks on NASA's and Boeing's databases to create a new spreadsheet listing out all the potential safety concerns for upcoming flights and software transitions. Since the application was written in Visual Basic, I had to learn a new programming language and prepare to handle any malfunctions within the program. Shortly afterwards, I was given the assignment to automate the Station Program Note (SPN) Pull process. I developed an application, in Python, that generated a GUI (Graphical User Interface) that will be used by the International Space Station Safety & Mission Assurance team here at Johnson Space Center. The application will allow its users to download online files with the click of a button, import SPN's based on three different pulls, instantly manipulate and filter spreadsheets, and compare the three sources to determine which active SPN's (Station Program Notes) must be reviewed for any upcoming flights, missions, and/or software transitions. Initially, to perform the NASA SPN pull (one of three), I had created the program to allow the user to login to a secure webpage that stores data, input specific parameters, and retrieve the desired SPN's based on their inputs. However, to avoid any conflicts with sustainment, I altered it so that the user may login and download the NASA file independently. After the user has downloaded the file with the click of a button, I defined the program to check for any outdated or pre-existing files, for successful downloads, to acquire the spreadsheet, convert it from a text file to a comma separated file and finally into an Excel spreadsheet to be filtered and later scrutinized for specific SPN numbers. Once this file has been automatically manipulated to provide only the SPN numbers that are desired, they are stored in a global variable, shown on the GUI, and transferred over to a new Excel worksheet for comparison. I managed to get my application to acquire the CSWG (Computer Safety Working Group) and the SPNWG (Space Station Working Group) SPN's with just two mouse clicks for each pull, as opposed to several from the original process. When all three pulls are performed, an Excel sheet containing all three different results will be generated for the user to compare and determine which SPN's will be presented or reviewed the following month. The experience from this internship has been spectacular. As a high school senior who will begin attending college in the fall, this internship has been both educationally and occupationally beneficial. The internship has allowed me the opportunities to learn new programming languages, effectively network with NASA personnel from a variety of departments at JSC, and allowed me to learn new professional skills and etiquette. My internship at NASA's Johnson Space Center has further motivated me to pursue a Master's degree in Software Engineering and strive for a prosperous career with NASA as a civil servant.

Delgado, Ivan↗

NASA's Physics of the Cosmos and Cosmic Origins Technology Development Programs

The strategic astrophysics missions of the coming decades will help answer the questions "How did our universe begin and evolve?" and "How did galaxies, stars, and planets come to be?" Enabling these missions requires advances in key technologies far beyond the current state of the art. NASA's Physics of the Cosmos (PCOS) and Cosmic Origins (COR) Program Offices manage technology maturation projects funded through the Strategic Astrophysics Technology (SAT) program to accomplish such advances. The PCOS and COR Program Offices, residing at the NASA Goddard Space Flight Center (GSFC), were established in 2011, and serve as the implementation arm for the Astrophysics Division at NASA Headquarters. We present an overview of the Programs' technology development activities and the current technology investment portfolio of 23 technology advancements. We discuss the process for addressing community-provided technology gaps and Technology Management Board (TMB)-vetted prioritization and investment recommendations that inform the SAT program. The process improves the transparency and relevance of our technology investments, provides the community a voice in the process, and promotes targeted external technology investments by defining needs and identifying customers. The Programs' priorities are driven by strategic direction from the Astrophysics Division, which is informed by the National Research Council's (NRC) "New Worlds, New Horizons in Astronomy and Astrophysics" (NWNH) 2010 Decadal Survey report [1], the Astrophysics Implementation Plan (AIP) [2] as updated, and the Astrophysics Roadmap "Enduring Quests, Daring Visions" [3]. These priorities include technology development for missions to study dark energy, gravitational waves, X-ray and inflation probe science, and large far-infrared (IR) and ultraviolet (UV)/optical/IR telescopes to conduct imaging and spectroscopy studies. The SAT program is the Astrophysics Division's main investment method to mature technologies that will be identified by study teams set up to inform the 2020 Decadal Survey process on several large astrophysics mission concepts.

SPIE paper↗

2015 Annual Report for the Flight Opportunities Program

Welcome to this third edition of the Flight Opportunities program annual report. In this edition, we continue our story of pathfinding NASA's role in the partnership with the U.S. commercial space and space technology R&D communities to advance national space interests and develop technologies critical to NASA's future missions. 2015 was the year in which a planned change to our payload solicitation strategy saw its first tangible result. As you might remember from our 2014 annual report, in 2015 we set out to facilitate a more direct interaction between flight providers and technology developers by providing fixed funding awards to researchers to directly purchase the flight service(s) that best meet their needs. The selection and award of the first six REDDI-F1 flight grants to non-U.S. government researchers was an important milestone in this regard. From now on, using the REDDI-F1 solicitation appendix, the program will enable non-U.S. government researchers to directly purchase flight services on the emerging suborbital market. The same (or similar) commercial flight services will be available to NASA and other U.S. government agencies (OGA) through commercial contracts that NASA has established through our program. For the latter, our program is available to provide campaign management services, similar to the role we play(ed) for technology payloads remaining in our pool from earlier selections. The full impact of this broader strategic change will likely become more visible in the years ahead as our legacy pool gets depleted and we have implemented a new NASA- and OGA-specific call for proposals. One observation that can already be made after two rounds of REDDI-F1 solicitations is that through this change, the list of commercial flight service providers of interest to non-U.S. government researchers has grown from five in 2014 to nine in 2015. On the industry development front, our Announcement of Collaborative Opportunities (ACO) solicitation was promoted to an STMD-wide solicitation and released in 2015 in combination with the Tipping Point solicitation. A total of 22 awards was announced in November 2015, 12 of which are ACO awards, and six of these are funded by Flight Opportunities. Through these ACO awards, the program funds NASA technical expertise and NASA test facilities to aid industry partners in maturing key space technologies, in our case focusing on small launch vehicle technology development. Flight test activity in 2015 saw a steady 13 campaigns with 31 payload-flights (29 unique payloads). Thirteen new payloads were selected into the program in FY2015, and 14 payloads completed flight testing, bringing the total number of completed technology demonstration payloads to 69. Overall, we are pleased with the evolution and growth of the Flight Opportunities program and look forward to continued success in our partnership with the technology R&D community and the commercial space sector.

Flight Testing↗

SLS-SPEC-159 Cross-Program Design Specification for Natural Environments (DSNE) Revision E

The DSNE completes environment-related specifications for architecture, system-level, and lower-tier documents by specifying the ranges of environmental conditions that must be accounted for by NASA ESD Programs. To assure clarity and consistency, and to prevent requirements documents from becoming cluttered with extensive amounts of technical material, natural environment specifications have been compiled into this document. The intent is to keep a unified specification for natural environments that each Program calls out for appropriate application. This document defines the natural environments parameter limits (maximum and minimum values, energy spectra, or precise model inputs, assumptions, model options, etc.), for all ESD Programs. These environments are developed by the NASA Marshall Space Flight Center (MSFC) Natural Environments Branch (MSFC organization code: EV44). Many of the parameter limits are based on experience with previous programs, such as the Space Shuttle Program. The parameter limits contain no margin and are meant to be evaluated individually to ensure they are reasonable (i.e., do not apply unrealistic extreme-on-extreme conditions). The natural environments specifications in this document should be accounted for by robust design of the flight vehicle and support systems. However, it is understood that in some cases the Programs will find it more effective to account for portions of the environment ranges by operational mitigation or acceptance of risk in accordance with an appropriate program risk management plan and/or hazard analysis process. The DSNE is not intended as a definition of operational models or operational constraints, nor is it adequate, alone, for ground facilities which may have additional requirements (for example, building codes and local environmental constraints). "Natural environments," as the term is used here, refers to the environments that are not the result of intended human activity or intervention. It consists of a variety of external environmental factors (most of natural origin and a few of human origin) which impose restrictions or otherwise impact the development or operation of flight vehicles and destination surface systems.

Roberts, Barry C.↗

A Summary and Analysis of NASA's Strategic Astrophysics Technology PCOS/COR Investments Since Program Inception

The NASA Strategic Astrophysics Technology (SAT) Program was established in 2009 as a new technology maturation program to fill the gap in the Technology Readiness Level (TRL) range from 3 to 6. Since the inception of the program, 47 tasks have been awarded under the auspices of the NASA Physics of the Cosmos (PCOS) Program in the areas of optics and detectors as well as lasers, electronics, and micro-thruster subsystems. In addition, 31 tasks have been awarded under the auspices of the NASA Cosmic Origins (COR) Program to develop optics, coatings, cooling subsystems, and detectors from the Far-IR to the Far-UV. We present the PCOS/COR portfolio distribution in terms of specific technology areas addressed and show an analysis of the rate and cost of TRL advancements. We present highlights of the infusion success stories that have emerged from the SAT maturation program as it relates to enabling future NASA astrophysics strategic missions. Finally, we present an outlook for future technology priorities for investment by the SAT Program.

COR↗

Centennial Challenges Program Update: From Humanoids to 3D-Printing Houses on Mars, How the Public Can Advance Technologies for NASA and the Nation

The Centennial Challenges (CC) program, part of NASA's Space Technology Mission Directorate (STMD), was founded upon the principle that engaging the public at large was a very important part of garnering the true magnitude of grassroots American innovation and ingenuity. The program uses a focused problem-statement approach to obtain solutions and/or stimulate innovation in key NASA technology gaps by catalyzing sources outside of the traditional aerospace community. The CC program announced the first two challenge competitions in 2005 incentivizing the public to participate using a congressionally authorized prize purse. Since then, the program has developed and executed more than 18 competitions and has awarded over $9 million in prize money. The challenges have covered a variety of technology areas, including propulsion, robotics, communications and navigation, human health, science instrumentation, nanotech, materials and structures, and aerodynamics. Centennial Challenges' accomplishments from October 2016 to December 2017--including significant increases in the amount and diversity of participants; increase in prize purse awards; strong alignments with NASA missions; and partnerships with industry, academia, and other government agencies-are summarized in this paper. Technological advancements, communication strategies, and legal authority are also discussed. NASA is leading the government agencies in the area of prizes and competitions to push technologies, and the CC program is one powerful example of NASA's continuing commitment to technological advancement and innovation through non-traditional programs. Currently, the Agency has in place the proven infrastructure, policies, and people needed to enable the successful use of competition tools, including the ones used as part of the CC program.

Centennial Challenge Prize↗

UH-60A Airloads Flight Test Program: Data Counter 8513

The data collection portion of the UH-60A Airloads Flight Test Program was conducted between July 1993 and February 1994. At the time, the UH-60A Airloads Program was the most comprehensive and data-rich rotorcraft flight test program that NASA and the U.S. Army had ever attempted. It was part of the Modern Technology Rotors Program, where several different rotors were tested in small- and full-scale wind tunnels combined with flight testing. The UH-60A portion of this program allowed for comparison between other tests performed and served as a scientific quality database for validating current and new computational and simulation models. The UH-60A flight test data was stored in a comprehensive, easily accessed database known as the Tilt Rotor Engineering Database System, or TRENDS. With over 30 years of rotor testing experience, NASA and the Army’s goal of the Airloads Flight Test Program was to collect data for a wide range of operating conditions and provide an extensive amount of data to improve the understanding of rotors and validate and improve prediction codes. This report presents the entire archived data set from Counter 8513 (Run 85, point 13) from the UH-60A Airloads Flight Test Program. There were 1,078 total data set counters acquired and archived during 57 accumulated flight hours and 31 research flights. Over 900 counters were research flight data acquisition data points. Counter 8513 is a low-speed, level-flight test condition.

Kufeld, Robert M.↗

UH-60A Airloads Flight Test Program: Data Counter 9505

The data collection portion of the UH-60A Airloads Flight Test Program (ref. 1) was conducted between July 1993 and February 1994. At the time, the UH-60A Airloads Program was the most comprehensive and data-rich rotorcraft flight test program that NASA and the U.S. Army had ever attempted. It was part of the Modern Technology Rotors Program (ref. 2), where several different rotors were tested in small- and full-scale wind tunnels combined with flight testing. The UH-60A portion of this program allowed for comparison between other tests performed and served as a scientific quality database for validating current and new computational and simulation models. The UH-60A flight test data was stored in a comprehensive, easily accessed database known as the Tilt Rotor Engineering Database System, or TRENDS (ref. 3). With over 30 years of rotor testing experience (ref. 4), NASA and the Army’s goal of the Airloads Flight Test Program was to collect data for a wide range of operating conditions, and to provide an extensive amount of data to improve the understanding of rotors and validate and improve prediction codes. This report presents the entire archived data set from Counter 9505 (Run 95, point 5) from the UH-60A Airloads Flight Test Program. There were 1,078 total data set counters acquired and archived during 57 accumulated flight hours and 31 research flights. Over 900 counters were research flight data acquisition data points. Counter 9505 is a low altitude, moderate airspeed, level-flight test condition. Ground acoustic microphone data was acquired for this counter but the acoustic data is not included in this report.

Kufeld, Robert M.↗