Search Results

This standard sets forth the desired characteristics of a second-generation aviation Ku-band and Ka-band satellite communication (satcom) system intended for installation in all types of aircraft.

., AeroMACS, Inmarsat SwiftBroadband (SBB) Satcom, and Iridium NEXT/Certus Satcom).

This standard defines the Aircraft Communications Addressing and Reporting System (ACARS), a VHF data link that transfers character-oriented data between aircraft systems and ground systems. This communications facility enables the aircraft to operate as part of the airline's command, control and management system.

ARINC 628, Part 9 defines general architectural philosophy and aircraft infrastructure for the proper use and interface of various cabin information network related equipment. It specifies a generic on-board infrastructure with commercial server technology, high-speed data communication and exchange via wired and wireless LAN for a wide range of applications. Supplement 4 defines web-based interfaces for cabin control panels and recognizes current standards for commercial browsers and applications. It incorporates current network security practices, including reference to ARINC 842 Digital Certificates.

This standard defines ADS system functions. It describes the ADS to ground-based application end-to-end operation. Includes a brief overview of the entire ADS system in order to aid the reader in understanding the ADS environment.

The Role of Autonomous Unmanned Ground Vehicle Technologies in Defense Applications Information Warfare - Staying Protected at the Edge Designing Connectivity Solutions for an Electric Aircraft Future Redesigning the Systems Engineering Process to Speed Development of E-Propulsion Aircraft Four RF Technology Trends You Need to Know for Satellite Communication Device Design Manufacturer Reduces Risk and Improves Quality of Military Radar Receivers Instrumentation for Fabrication and Testing of High-Speed Single-Rotor and Compound-Rotor Systems Precision data acquisition is required to generate a comprehensive set of measurements of the blade surface pressures, pitch link loads, hub loads, rotor wakes and performance of high-speed single-rotor and compound-rotor systems to support the development of next-generation rotorcraft.

This standard sets forth the desired interface characteristics of the data link service provider to the data link user. Provides data link users the information needed to develop applications and to encourage uniformity and standardization (to the extent possible) among various data link service providers. Contains general and specific guidance concerning the interfaces between the data link service providers and both the airborne and ground user.

This standard defines the air transport industry's standards for the transfer of digital data between avionics system elements. Part 2 provides the formats of data words with discrete bit encoding.

The purpose of this document is to facilitate an understanding of aircraft information security and to develop aircraft information security operational concepts. This common understanding is important since a number of subcommittees and working groups within the aeronautical industry are considering aircraft information security. This document also provides an aircraft information security process framework relating to airline operational needs that, when implemented by an airline and its suppliers, will enable the safe and secure dispatch of the aircraft in a timely manner. This framework facilitates development of cost-effective aircraft information security and provides a common language for understanding security needs.

The purpose of this document is to provide an industry standard for ACARS Message Security (AMS), which permits ACARS datalink messages to be exchanged between aircraft and ground systems in a secure, authenticated manner using a uniform security framework. The security framework described herein is based on open international standards that are adapted to the ACARS datalink communications environment.

A generic data transfer interface is defined for use between avionics computing equipment that exchanges binary message-oriented data. This interface was developed so that various manufacturers can partition Air Traffic Services (ATS) applications and protocols in different manners between various equipment.

This report sets forth guidance for IP-based onboard networks and systems residing in the Airline Information Services (AIS) and Passenger Information and Entertainment Services (PIES) Domains by establishing a common set of security related data elements and format(s) that are produced by aircraft systems, suitable for use by airline IT and/or avionic supplier analytical ground tools.

The purpose of ARNC 633 is to specify the format and exchange of Aeronautical Operational Control (AOC) communications. Examples of ARINC 633 AOC Structures/Messages include: Flight Plan, Load Planning (i.e., Weight and Balance and Cargo Planning Load Sheets), NOTAMs, Airport and Route Weather data, Minimum Equipment Lists (MEL) messages, etc. The standardization of AOC messages enable the development of applications shared by numerous airlines on different aircraft types. Benefits include improved dispatchability and reduce operator cost.

How Electrification and Autonomy Can Unlock the Potential of Unmanned Ground Vehicles VITA 90: Small Form Factors for UAVs and Other Space Constrained Platforms 3D Scanning Provides Key Weapon for Aerospace and Defense Manufacturing New Approach to Viscosity Enables Complex Motions in Soft Robots Ghoul Tool: The Weapon-Mountable Counter UAS Transmitter Autonomous Surveillance Technologies Relating to Dismounted Soldiers The development of the autonomous applications for dismounted Soldier systems is paramount to defeating our adversaries, such as China and Russia, in future combat. A comprehensive literature re-view is necessary to assist in defining the best path forward. Robust MADER: Decentralized Multiagent Drone Trajectory Planner Communication delays can be catastrophic for multiagent systems. However, most existing state-of-the-art multiagent trajectory planners assume perfect communication and therefore lack a strategy to rectify this issue in real-world environments.

This standard consolidates and defines various interface parameters, except for power, that may be required to support the operation of an IFES on any airplane model. Supplement 2 adds an Ethernet interface between the aircraft Cabin Services System (CSS) and In-Flight Entertainment System. This interface may be used to exchange information between the CSS and The Passenger Service System (PSS), passenger address/entertainment, airplane mode, navigation, and operational data.

Advanced CT Inspection and Data Analysis Designing for the Connected Battlespace Engineering an Aircraft Hydrogen Powertrain Open System Software for Critical Applications Making Fully Digital Beamforming for Radar and Electronic Warfare Applications a Reality Defeating Commercial Drone Threats with Software Defined Radio Quantifying Eye Movement Trajectory Similarity for Use in Human Performance Experiments in Intelligence, Surveillance, and Reconnaissance (ISR) Research Using ScanMatch, a Matlab software package, to determine the similarity of two strings of eye tracking data provides useful background and recommendations for potential applications in Intelligence, Surveillance, and Reconnaissance (ISR) research. Stochastic Surveillance and Distributed Coordination Designing fast and unpredictable motion strategies for robotic surveillance agents in complex environments using Markov chain modeling and optimization methods.

The purpose of this specification is to support the exchange of certain Aeronautical Operational Control (AOC) air-ground and ground-ground messages. These messages are defined in this specification, apart from those defined in ARINC Specification 620, because they have unique qualities. Like the messages defined in ARINC Specification 620, their usage necessitates a single definition.

This document sets forth guidance for life-cycle management of public/private (i.e., asymmetric) keys that are used to secure interactions among systems.

The purpose of ARNC 633 is to specify the format and exchange of Aeronautical Operational Control (AOC) communications. Examples of ARINC 633 AOC Structures/Messages include: Flight Plan, Load Planning (i.e., Weight and Balance and Cargo Planning Load Sheets), NOTAMs, Airport and Route Weather data, Minimum Equipment Lists (MEL) messages, etc. The standardization of AOC messages enable the development of applications shared by numerous airlines on different aircraft types. Benefits include improved dispatchability and reduce operator cost.

This document defines the exchange of Aeronautical Operational Control (AOC) message formats used for air-to-ground communication and ground-to-ground communication. ARINC Specification 633 simplifies the integration of AOC software from different suppliers, intended for use by different airlines, on different aircraft types. It is expected that AOC applications will be hosted on an Electronic Flight Bags (EFB). Supplement 2 includes an extensive updates to the Flight Plan schema per ICAO Flight Plan 2012. New XML schemas are added to define AOC messages for airport weather, air traffic information services (ATIS), crew list, passenger list, notice to airmen, pilot report, and hazard advisory.