Search NASA⌕ Search

SEARCH · Search NASA

Results for “RTCA”

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 55 records · Page 3
All sourcesNASA NTRSDOE OSTI
NASA NTRS1995

Computer simulation and performance assessment of the packet-data service of the Aeronautical Mobile Satellite Service (AMSS)

The ICAO Aeronautical Mobile Communications Panel (AMCP) completed the drafting of the Aeronautical Mobile Satellite Service (AMSS) Standards and Recommended Practices (SARP's) and the associated Guidance Material and submitted these documents to ICAO Air Navigation Commission (ANC) for ratification in May 1994. This effort, encompassed an extensive, multi-national SARP's validation. As part of this activity, the US Federal Aviation Administration (FAA) sponsored an effort to validate the SARP's via computer simulation. This paper provides a description of this effort. Specifically, it describes: (1) the approach selected for the creation of a high-fidelity AMSS computer model; (2) the test traffic generation scenarios; and (3) the resultant AMSS performance assessment. More recently, the AMSS computer model was also used to provide AMSS performance statistics in support of the RTCA standardization activities. This paper describes this effort as well.

Ferzali, Wassim↗
NASA NTRS1998

Defining the ATC Controller Interface for Data Link Clearances

The Controller Interface (CI) is the primary method for Air Traffic Controllers to communicate with aircraft via Controller-Pilot Data Link Communications (CPDLC). The controller, wearing a microphone/headset, aurally gives instructions to aircraft as he/she would with today's voice radio systems. The CI's voice recognition system converts the instructions to digitized messages that are formatted according to the RTCA DO-219 Operational Performance Standards for ATC Two-Way Data Link Communications. The DO-219 messages are transferred via RS-232 to the ATIDS system for uplink using a Mode-S datalink. Pilot acknowledgments of controller messages are downlinked to the ATIDS system and transferred to the Cl. A computer monitor is used to convey information to the controller. Aircraft data from the ARTS database are displayed on flight strips. The flight strips are electronic versions of the strips currently used in the ATC system. Outgoing controller messages cause the respective strip to change color to indicate an unacknowledged transmission. The message text is shown on the flight strips for reference. When the pilot acknowledges the message, the strip returns to its normal color. A map of the airport can also be displayed on the monitor. In addition to voice recognition, the controller can enter messages using the monitor's touch screen or by mouse/keyboard.

Rankin, James↗
NASA NTRS1998

A Formal Model of Partitioning for Integrated Modular Avionics

The aviation industry is gradually moving toward the use of integrated modular avionics (IMA) for civilian transport aircraft. An important concern for IMA is ensuring that applications are safely partitioned so they cannot interfere with one another. We have investigated the problem of ensuring safe partitioning and logical non-interference among separate applications running on a shared Avionics Computer Resource (ACR). This research was performed in the context of ongoing standardization efforts, in particular, the work of RTCA committee SC-182, and the recently completed ARINC 653 application executive (APEX) interface standard. We have developed a formal model of partitioning suitable for evaluating the design of an ACR. The model draws from the mathematical modeling techniques developed by the computer security community. This report presents a formulation of partitioning requirements expressed first using conventional mathematical notation, then formalized using the language of SRI'S Prototype Verification System (PVS). The approach is demonstrated on three candidate designs, each an abstraction of features found in real systems.

DiVito, Ben L.↗
NASA NTRS2000

Free Flight Simulation: An Initial Examination of Air-Ground Integration Issues

The concept of "free flight" is intended to emphasize more flexibility for operators in the National Airspace System (RTCA, 1995). This may include the potential for aircraft self-separation. The purpose of this simulation was to begin examining some of the communication and procedural issues associated with self-separation in an integrated air-ground environment. Participants were 10 commercial U.S. flight crews who flew the B747-400 simulator and 10 Denver ARTCC controllers who monitored traffic in an ATC simulation. A prototypic airborne alerting logic and flight deck display features were designed to allow for increased traffic and maneuvering information. Eight different scenarios representing different conflict types were developed. The effects of traffic density (high and low) and different traffic convergence angles (obtuse, acute, and right) were assessed. Conflict detection times were found to be lower for the flight crews in low density compared to high density scenarios. For the controllers, an interaction between density and convergence angle was revealed. Analyses on the controller detection times found longer detection times in the obtuse high density compared to obtuse low density, as well as the shortest detection times in the high density acute angle condition. Maneuvering and communication events are summarized, and a discussion of future research issues is provided.

Lozito, Sandra↗
NASA NTRS2002

Development of Intent Information Changes to Revised Minimum Aviation System Performance Standards for Automatic Dependent Surveillance Broadcast (RTCA/DO-242A)

RTCA Special Committee 186 has recently adopted a series of changes to the original Minimum Aviation System Performance Standards (MASPS) for Automatic Dependent Surveillance Broadcast (ADS-B). The new document will be published as DO-242A. Major changes to the MASPS include a significant restructuring and expansion of the intent parameters for future ADS-B systems. ADS-B provides a means for aircraft to exchange information about their intended trajectories with each other and with ground systems. NASA and Boeing have played significant roles in recommending these changes and providing supporting analysis. The intent changes are anticipated to provide substantial benefits to several programs and operational concepts under development by the two organizations. Major changes include the addition of Target State reports and the replacement of Trajectory Change Point reports with Trajectory Change reports. These changes have been designed to better reflect the capabilities of existing and future aircraft avionics, while providing benefits to current and proposed applications. DO-242A implements intent information elements that can be supported by current avionics systems and data buses. Provisions are made for future incorporation of other intent elements, as needed to meet operational requirements. This document summarizes the reasons for the DO-242A intent changes and provides a detailed overview of current and future intended ADS-B MASPS changes related to aircraft intent.

Barhydt, Richard↗
NASA NTRS2002

Newly Enacted Intent Changes to ADS-B MASPS: Emphasis on Operations, Compatibility, and Integrity

Significant changes to the intent reporting structure in the Minimum Aviation System Performance Standards (MASPS) for Automatic Dependent Surveillance Broadcast (ADS-B) have recently been approved by RTCA Special Committee 186. The re-structured intent formats incorporate two major changes to the current MASPS (DO-242): addition of a Target State (TS) report that provides information on the horizontal and vertical targets for the current flight segment and replacement of the current Trajectory Change Point (TCP) and TCP+1 reports with Trajectory Change (TC) reports. TC reports include expanded information about TCPs and their connecting flight segments, in addition to making provisions for trajectory conformance elements. New intent elements are designed to accommodate a greater range of intent information, better reflect operational use and capabilities of existing and future aircraft avionics, and aid trajectory synthesis and conformance monitoring systems. These elements are expected to benefit near-term and future Air Traffic Management (ATM) applications, including separation assurance, local traffic flow management, and conformance monitoring. The current MASPS revision (DO-242A) implements those intent elements that are supported by current avionics standards and data buses. Additional elements are provisioned for inclusion in future MASPS revisions (beyond DO-242A) as avionics systems are evolved.

Barhydt, Richard↗
NASA NTRS2003

Certification Processes for Safety-Critical and Mission-Critical Aerospace Software

This document is a quick reference guide with an overview of the processes required to certify safety-critical and mission-critical flight software at selected NASA centers and the FAA. Researchers and software developers can use this guide to jumpstart their understanding of how to get new or enhanced software onboard an aircraft or spacecraft. The introduction contains aerospace industry definitions of safety and safety-critical software, as well as, the current rationale for certification of safety-critical software. The Standards for Safety-Critical Aerospace Software section lists and describes current standards including NASA standards and RTCA DO-178B. The Mission-Critical versus Safety-Critical software section explains the difference between two important classes of software: safety-critical software involving the potential for loss of life due to software failure and mission-critical software involving the potential for aborting a mission due to software failure. The DO-178B Safety-critical Certification Requirements section describes special processes and methods required to obtain a safety-critical certification for aerospace software flying on vehicles under auspices of the FAA. The final two sections give an overview of the certification process used at Dryden Flight Research Center and the approval process at the Jet Propulsion Lab (JPL).

Nelson, Stacy↗
NASA NTRS2003

Certification Processes for Safety-Critical and Mission-Critical Aerospace Software

This document is a quick reference guide with an overview of the processes required to certify safety-critical and mission-critical flight software at selected NASA centers and the FAA. Researchers and software developers can use this guide to jumpstart their understanding of how to get new or enhanced software onboard an aircraft or spacecraft. The introduction contains aerospace industry definitions of safety and safety-critical software, as well as, the current rationale for certification of safety-critical software. The Standards for Safety-Critical Aerospace Software section lists and describes current standards including NASA standards and RTCA DO-178B. The Mission-Critical versus Safety-Critical software section explains the difference between two important classes of software: safety-critical software involving the potential for loss of life due to software failure and mission-critical software involving the potential for aborting a mission due to software failure. The DO-178B Safety-critical Certification Requirements section describes special processes and methods required to obtain a safety-critical certification for aerospace software flying on vehicles under auspices of the FAA. The final two sections give an overview of the certification process used at Dryden Flight Research Center and the approval process at the Jet Propulsion Lab (JPL).

Nelson, Stacy↗
NASA NTRS2004

DAG-TM Concept Element 11 CNS Performance Assessment: ADS-B Performance in the TRACON

Distributed Air/Ground (DAG) Traffic Management (TM) is an integrated operational concept in which flight deck crews, air traffic service providers and aeronautical operational control personnel use distributed decision-making to enable user preferences and increase system capacity, while meeting air traffic management (ATM) safety requirements. It is a possible operational mode under the Free Flight concept outlined by the RTCA Task Force 3. The goal of DAG-TM is to enhance user flexibility/efficiency and increase system capacity, without adversely affecting system safety or restricting user accessibility to the National Airspace System (NAS). DAG-TM will be accomplished with a human-centered operational paradigm enabled by procedural and technological innovations. These innovations include automation aids, information sharing and Communication, Navigation, and Surveillance (CNS) / ATM technologies. The DAG-TM concept is intended to eliminate static restrictions to the maximum extent possible. In this paradigm, users may plan and operate according to their preferences - as the rule rather than the exception - with deviations occurring only as necessary. The DAG-TM concept elements aim to mitigate the extent and impact of dynamic NAS constraints, while maximizing the flexibility of airspace operations

Raghavan, Rajesh S.↗
NASA NTRS2004

Fact Sheets of CTAS and NASA Decision-Support Tools and Concepts

Distributed Air/Ground (DAG) Traffic Management (TM) is an integrated operational concept in which flight deck crews, air traffic service providers and aeronautical operational control personnel use distributed decision-making to enable user preferences and increase system capacity, while meeting air traffic management (ATM) requirements. It is a possible operational mode under the Free Flight concept outlined by the RTCA Task Force 3. The goal of DAG-TM is to enhance user flexibility/efficiency and increase system capacity, without adversely affecting system safety or restricting user accessibility to the National Airspace System (NAS). DAG-TM will be accomplished with a human-centered operational paradigm enabled by procedural and technological innovations. These innovations include automation aids, information sharing and Communication, Navigation, and Surveillance (CNS) / ATM technologies. The DAG-TM concept is intended to eliminate static restrictions to the maximum extent possible. In this paradigm, users may plan and operate according to their preferences - as the rule rather than the exception - with deviations occumng eyond the year 2015. Out of a total of 15 concept elements, 4 have been selected for initial sutidies (see Key Elements in sidebar). DAG-TM research is being performed at Ames, Glenn, and Langley Research Centers.

Lee, Katharine↗
NASA NTRS2005

Electromagnetic Interference to Flight Navigation and Communication Systems: New Strategies in the Age of Wireless

Electromagnetic interference (EMI) promises to be an ever-evolving concern for flight electronic systems. This paper introduces EMI and identifies its impact upon civil aviation radio systems. New wireless services, like mobile phones, text messaging, email, web browsing, radio frequency identification (RFID), and mobile audio/video services are now being introduced into passenger airplanes. FCC and FAA rules governing the use of mobile phones and other portable electronic devices (PEDs) on board airplanes are presented along with a perspective of how these rules are now being rewritten to better facilitate in-flight wireless services. This paper provides a comprehensive overview of NASA cooperative research with the FAA, RTCA, airlines and universities to obtain laboratory radiated emission data for numerous PED types, aircraft radio frequency (RF) coupling measurements, estimated aircraft radio interference thresholds, and direct-effects EMI testing. These elements are combined together to provide high-confidence answers regarding the EMI potential of new wireless products being used on passenger airplanes. This paper presents a vision for harmonizing new wireless services with aeronautical radio services by detecting, assessing, controlling and mitigating the effects of EMI.

Ely, Jay J.↗
NASA NTRS2009

NASA Manned Launch Vehicle Lightning Protection Development

Historically, the National Aeronautics and Space Administration (NASA) relied heavily on lightning avoidance to protect launch vehicles and crew from lightning effects. As NASA transitions from the Space Shuttle to the new Constellation family of launch vehicles and spacecraft, NASA engineers are imposing design and construction standards on the spacecraft and launch vehicles to withstand both the direct and indirect effects of lightning. A review of current Space Shuttle lightning constraints and protection methodology will be presented, as well as a historical review of Space Shuttle lightning requirements and design. The Space Shuttle lightning requirements document, NSTS 07636, Lightning Protection, Test and Analysis Requirements, (originally published as document number JSC 07636, Lightning Protection Criteria Document) was developed in response to the Apollo 12 lightning event and other experiences with NASA and the Department of Defense launch vehicles. This document defined the lightning environment, vehicle protection requirements, and design guidelines for meeting the requirements. The criteria developed in JSC 07636 were a precursor to the Society of Automotive Engineers (SAE) lightning standards. These SAE standards, along with Radio Technical Commission for Aeronautics (RTCA) DO-160, Environmental Conditions and Test Procedures for Airborne Equipment, are the basis for the current Constellation lightning design requirements. The development and derivation of these requirements will be presented. As budget and schedule constraints hampered lightning protection design and verification efforts, the Space Shuttle elements waived the design requirements and relied on lightning avoidance in the form of launch commit criteria (LCC) constraints and a catenary wire system for lightning protection at the launch pads. A better understanding of the lightning environment has highlighted the vulnerability of the protection schemes and associated risk to the vehicle, which has resulted in lost launch opportunities and increased expenditures in manpower to assess Space Shuttle vehicle health and safety after lightning events at the launch pad. Because of high-percentage launch availability and long-term on-pad requirements, LCC constraints are no longer considered feasible. The Constellation vehicles must be designed to withstand direct and indirect effects of lightning. A review of the vehicle design and potential concerns will be presented as well as the new catenary lightning protection system for the launch pad. This system is required to protect the Constellation vehicles during launch processing when vehicle lightning effects protection might be compromised by such items as umbilical connections and open access hatches.

McCollum, Matthew B.↗
NASA NTRS2010

Guidance for Using Formal Methods in a Certification Context

This paper discusses some of the challenges to using formal methods in a certification context and describes the effort by the Formal Methods Subgroup of RTCA SC-205/EUROCAE WG-71 to propose guidance to make the use of formal methods a recognized approach. This guidance, expected to take the form of a Formal Methods Technical Supplement to DO-178C/ED-12C, is described, including the activities that are needed when using formal methods, new or modified objectives with respect to the core DO-178C/ED-12C document, and evidence needed for meeting those objectives.

Brown, Duncan↗
NASA NTRS2010

C-Band Airport Surface Communications System Standards Development, Phase I

This document is being provided as part of ITT's NASA Glenn Research Center Aerospace Communication Systems Technical Support (ACSTS) contract NNC05CA85C, Task 7: "New ATM Requirements--Future Communications, C-Band and L-Band Communications Standard Development." The proposed future C-band (5091- to 5150-MHz) airport surface communication system, referred to as the Aeronautical Mobile Airport Communications System (AeroMACS), is anticipated to increase overall air-to-ground data communications systems capacity by using a new spectrum (i.e., not very high frequency (VHF)). Although some critical services could be supported, AeroMACS will also target noncritical services, such as weather advisory and aeronautical information services as part of an airborne System Wide Information Management (SWIM) program. AeroMACS is to be designed and implemented in a manner that will not disrupt other services operating in the C-band. This report defines the AeroMACS concepts of use, high-level system requirements, and architecture; the performance of supporting system analyses; the development of AeroMACS test and demonstration plans; and the establishment of an operational AeroMACS capability in support of C-band aeronautical data communications standards to be advanced in both international (International Civil Aviation Organization, ICAO) and national (RTCA) forums. This includes the development of system parameter profile recommendations for AeroMACS based on existing Institute of Electrical and Electronics Engineering (IEEE) 802.16e- 2009 standards

Hall, Edward↗
NASA NTRS2010

Interference Analysis for an Aeronautical Mobile Airport Communications System

The next generation of aeronautical communications for airport surface applications has been identified through a NASA research program and an international collaborative future communications study. The result, endorsed by both the United States and European regulatory agencies is called AeroMACS (Aeronautical Mobile Airport Communications System) and is based upon the IEEE 802.16e mobile wireless standard. Coordinated efforts to develop appropriate aviation standards for the AeroMACS system are now underway within RTCA (United States) and Eurocae (Europe). AeroMACS will be implemented in a recently allocated frequency band, 5091- 5150 MHz. As this band is also occupied by fixed satellite service uplinks, AeroMACS must be designed to avoid interference with this incumbent service. The aspects of AeroMACS operation that present potential interference to the fixed satellite service are under analysis in order to enable the definition of standards that assure that such interference will be avoided. The NASA Glenn Research Center has been involved in this analysis, and the first results of modeling and simulation efforts directed at this analysis are the subject of this paper.12

Wilson, Jeffrey D.↗
NASA NTRS2011

Interference Analysis for an Aeronautical Mobile Airport Communications System

The next generation of aeronautical communications for airport surface applications has been identified through a NASA research program and an international collaborative future communications study. The result, endorsed by both the United States and European regulatory agencies is called AeroMACS (Aeronautical Mobile Airport Communications System) and is based upon the IEEE 802.16e mobile wireless standard. Coordinated efforts to develop appropriate aviation standards for the AeroMACS system are now underway within RTCA (United States) and Eurocae (Europe). AeroMACS will be implemented in a recently allocated frequency band, 5091-5150 MHz. As this band is also occupied by fixed satellite service uplinks, AeroMACS must be designed to avoid interference with this incumbent service. The aspects of AeroMACS operation that present potential interference to the fixed satellite service are under analysis in order to enable the definition of standards that assure that such interference will be avoided. The NASA Glenn Research Center has been involved in this analysis, and the first results of modeling and simulation efforts directed at this analysis are the subject of this presentation.

Wilson, Jeffrey D.↗
NASA NTRS2010

Interference Analysis Status and Plans for Aeronautical Mobile Airport Communications System (AeroMACS)

Interference issues related to the operation of an aeronautical mobile airport communications system (AeroMACS) in the C-Band (specifically 5091-5150 MHz) is being investigated. The issue of primary interest is co-channel interference from AeroMACS into mobile-satellite system (MSS) feeder uplinks. The effort is focusing on establishing practical limits on AeroMACS transmissions from airports so that the threshold of interference into MSS is not exceeded. The analyses are being performed with the software package Visualyse Professional, developed by Transfinite Systems Limited. Results with omni-directional antennas and plans to extend the models to represent AeroMACS more accurately will be presented. These models should enable realistic analyses of emerging AeroMACS designs to be developed from NASA Test Bed, RTCA 223, and European results.

Kerczewski, Robert J.↗
NASA NTRS2012

Certification of COTS Software in NASA Human Rated Flight Systems

Adoption of commercial off-the-shelf (COTS) products in safety critical systems has been seen as a promising acquisition strategy to improve mission affordability and, yet, has come with significant barriers and challenges. Attempts to integrate COTS software components into NASA human rated flight systems have been, for the most part, complicated by verification and validation (V&V) requirements necessary for flight certification per NASA s own standards. For software that is from COTS sources, and, in general from 3rd party sources, either commercial, government, modified or open source, the expectation is that it meets the same certification criteria as those used for in-house and that it does so as if it were built in-house. The latter is a critical and hidden issue. This paper examines the longstanding barriers and challenges in the use of 3rd party software in safety critical systems and cover recent efforts to use COTS software in NASA s Multi-Purpose Crew Vehicle (MPCV) project. It identifies some core artifacts that without them, the use of COTS and 3rd party software is, for all practical purposes, a nonstarter for affordable and timely insertion into flight critical systems. The paper covers the first use in a flight critical system by NASA of COTS software that has prior FAA certification heritage, which was shown to meet the RTCA-DO-178B standard, and how this certification may, in some cases, be leveraged to allow the use of analysis in lieu of testing. Finally, the paper proposes the establishment of an open source forum for development of safety critical 3rd party software.

Goforth, Andre↗