Search Results

The purpose of this standard is to provide a method for packaging aircraft software parts for distribution using contemporary media or by electronic distribution. This project intends to standardize and provide guidance for the storage of floppy based software, currently packaged in media set parts. This standard format can be then stored or distributed on a single physical media member (CD-ROM), or by electronic crate. The obsolescence of floppy disks drive an urgent need for this guidance.

This document specifies how application to application navigation is managed on tablet EFB devices. Topics include: inter-application navigation for users, blending of multiple applications into a single workflow, single data entry with data shared across applications.

This standard defines a common configuration report format that can be retrieved from an aircraft for use by ground tools and maintenance personnel. Reports will be generated in Extensible Markup Language (XML) format and structured as defined by this document. Several optional elements and attributes are defined to allow flexibility for a given report. This standard provides aircraft manufacturers, regulatory agencies, and airlines a format standard for aircraft configuration reporting, and facilitates automated comparison of configuration data reports (e.g., authorized versus as flying, etc.).

This document defines an Aircraft Data Interface Function (ADIF) developed for aircraft installations that incorporate network components based on commercially available technologies. This document defines a set of protocols and services for the exchange of aircraft avionics data across aircraft networks. A common set of services that may be used to access specific avionics parameters are described. The ADIF may be implemented as a generic network service, or it may be implemented as a dedicated service within an ARINC 759 Aircraft Interface Devices (AID) such as those used with an Electronic Flight Bag (EFB). Supplement 8 includes improvements in the Aviation Data Broadcast Protocol (ADBP), adds support for the Media Independent Aircraft Messaging (MIAM) protocol, and contains data security enhancements. It also includes notification and deprecation of the Generic Aircraft Parameter Service (GAPS) protocol that will be deleted in a future supplement.

The purpose of this document is to provide an overview of data networking standards recommended for use in commercial aircraft installations. These standards provide a means to adapt commercially defined networking standards to an aircraft environment. It refers to devices such as bridges, switches, routers and hubs and their use in an aircraft environment. This equipment, when installed in a network topology, can optimize data transfer and overall avionics performance.

This document describes the technical requirements, architectural options, and recommended interface standards to support an Autonomous Distress Tracking (ADT) System intended to meet global regulatory requirements for locating aircraft in distress situations and after an accident. This document is prepared in response to International Civil Aviation Organization (ICAO) and individual Civil Aviation Authorities (CAAs) initiatives.

This document defines a standard implementation for strong client authentication and encryption of Wi-Fi-based client connections to onboard Wireless LAN (WLAN) networks. WLAN networks may consist of multi-purpose inflight entertainment system networks operating in the Passenger Information and Entertainment System (PIES) domain, dedicated aircraft cabin wireless networks or localized Aircraft Integrated Data (AID) devices operating in the Aircraft Information Services (AIS) domain. The purpose of this document is to focus on the client devices requiring connections to these networks such as electronic flight bags, flight attendant mobile devices, onboard Internet of Things (IoT) devices, AID devices (acting as clients) and mobile maintenance devices. Passenger devices are not within the focus of this document.

The difficulty in locating crash sites has prompted international efforts for alternatives to quickly recover flight data. This document describes the technical requirements and architectural options for the Timely Recovery of Flight Data (TRFD) in commercial aircraft. ICAO and individual Civil Aviation Authorities (CAAs) levy these requirements. The ICAO Standards and Recommended Practices (SARPs) and CAA regulations cover both aircraft-level and on-ground systems. This report also documents additional system-level requirements derived from the evaluation of ICAO, CAA, and relevant industry documents and potential TRFD system architectures. It describes two TRFD architectures in the context of a common architectural framework and identifies requirements. This report also discusses implementation recommendations from an airplane-level perspective.

This standard sets forth the desired characteristics of Aviation Ku-band Satellite Communication (Satcom) and Ka-band Satcom Systems intended for installation in all types of commercial air transport aircraft. The intent of this characteristic is to provide guidance on the interfaces, form, fit, and function of the systems. This document also describes the desired operational capability of the equipment needed to provide a broadband transport link that can be used for data, video, and voice communications typically used for passenger communications and/or entertainment. The systems described in this characteristic are not qualified, at this writing, for aviation safety functions.

ARINC 814 defines an XML encoding and compression standard for aviation. It is based on the Open Geospatial Consortium (OGC) Binary XML document. Binary XML encoding is extended in a way that is both flexible and robust. Compression is added on top of the binary encoding. ARINC 814 is expected to be used with Aeronautical Databases, in particular, ARINC Specification 813: Embedded Interchange Format for Terrain Databases, ARINC Specification 815: Embedded Interchange Format for Obstacle Databases, and ARINC Specification 816: Embedded Interchange Format for Airport Mapping Database.

This document defines an open encoding format for obstacle databases. This format, when designed and implemented, will enable a quick, economic, and efficient use of Obstacle Databases (ObsDBs). However, since industry does not require applications to be standardized, data interpretation is not addressed in this document.

This document defines an open encoding format for terrain databases. This format, when designed and implemented, will enable a quick, economic, and efficient use of Terrain Databases (TerrDBs). However, since industry does not require applications to be standardized, data interpretation is not addressed in this document.

ARINC Specification 848 is a functional standard based on a protocol specification profile for a secured network interface. The purpose is to define a common method of initiating a mutually authenticated tunnel between an aircraft service and its Enterprise service. ARINC Specification 848 defines a standard implementation for securing the communications between an onboard Local Area Network (LAN) and an Enterprise LAN on the ground. Various aircraft network architectures and various air to ground communication channels (aka media) are accommodated in this document. For example, L-band Satellite Communication (Satcom), Ku/Ka-band Satcom, Gatelink Cellular, and Gatelink are considered.

This presentation proposes an approach to use ABS wheel speed sensor signals together with other vehicle state information from a brake control module to detect an unbalanced tire or tires in real-time. The proposed approach consists of two-stage algorithms that mix a qualitative method using band-pass filtering with a quantitative parameter identification using conditional least squares. This two-stage approach can improve the robustness of tire imbalance or imbalances. The proposed approach is verified through vehicle testing and the test results show the effectiveness of the approach. Presenter Jianbo Lu, Ford Motor Co.

When vehicles share certain information wirelessly via Dedicated Short Range Communications (DSRC), they enable a new layer of electronic vehicle safety that, when needed, can generate warnings to drivers and even initiate automatic preventive actions. Vehicle location and velocity provided by Global Navigation Systems (GNSS), including GPS, are key in allowing vehicle path estimation. GNSS is effective in accurately determining a vehicle's location coordinates in most driving environments, but its performance suffers from obstructions in dense urban environments. To combat this, augmentations to GNSS are being contemplated and tested. This testing has been typically done using a reference GNSS system complimented by expensive military-grade inertial sensors, which can still fail to provide adequate reference performance in certain environments.

Virtual testing is a method that simulates lab testing using multi-body dynamic analysis software. The main advantages of this approach include that the design can be evaluated before a prototype is available and virtual testing results can be easily validated by subsequent physical testing. The disadvantage is that accurate specimen models are sometimes hard to obtain since nonlinear components such as tires, bushings, dampers, and engine mounts are hard to model. Therefore, virtual testing accuracy varies significantly. The typical virtual rigs include tire and spindle coupled test rigs for full vehicle tests and multi axis shaker tables for component tests. Hybrid simulation combines physical and virtual components, inputs and constraints to create a composite simulation system. Hybrid simulation enables the hard to model components to be tested in the lab.

Polypropylene is typically reinforced with commodities that are non renewable and require a great deal of energy to produce. The marketplace needs a reinforcement that can offer beneficial physical properties, such as impact, while being attained from a renewable green source. Compounding flax fiber, which is traditionally an agricultural waste product burned by farmers, with polypropylene yields physical properties similar to traditional glass filled polypropylene. This combination should lead to cost saving opportunities while not sacrificing part performance. Presenter James Preston, Rhetech Inc.

Finding ways to reduce the amount of fuel burned per flight takes top priority in aircraft operations and design. Three experts show how the smallest on-board components can make a huge difference.

Optical fiber has begun replacing copper in avionic networks. So far, however, it has been mainly restricted to non-critical applications (video transmission to the flight deck, IFE?). In order to take advantage of the high-bandwidth, low weight, no EMI properties of optical fibers in all data transmission networks, it will be necessary to improve the testing. One part of the puzzle, which is still missing, is the self-test button: the possibility to check the network and detect potential failures before they occur. The typical testing tool of a technician involved in optical fiber cables is the ?light source ? optical power meter? pair. With this tool, one can measure the insertion loss of the fiber link. A second important parameter, the return loss at each optical connector, is not analysed. In addition, this is only a global measurement, which does not allow the detection of possible weak points.

Edgewater Computer Systems Inc. product RTEdge Platform 1.2 is a software toolset supporting proof based engineering, implementation and deployment of software components, built using the RTEdge AADL Microkernel modeling subset. This is a small subset of the AADL component model and execution semantics, covering threads and thread-groups communicating solely through asynchronous event ports and through explicitly shared data ports. Threads behavior is expressed as state machines and dispatch run time semantics is encoded in a Run-time Executive, enforcing pre-emptive priority dispatch based on statically assigned event priorities, with ceiling priority protocol access to shared data. This simple AADL microkernel semantic core can support all dispatch policies, communication and synchronization mechanisms of a fully fledged AADL run time environment, permitting the systematic use of the RTEdge static analysis tools for AADL compliant software components.