Search Results

This course is offered in China only and presented in Mandarin Chinese. The course materials are bilingual (English and Chinese). RTCA DO-178C  is the globally-accepted standard for civil aviation software development and certification. Compliance with the objectives of DO-178C is the primary means for meeting airworthiness requirements and obtaining approval of airborne software in TC/STC/TSO, etc. Even after study of the DO-178C, many people lack experience producing DO-178C compliant airborne software in real applications.

This four-hour short course intends to present an overview of electrically powered flight control actuation systems, covering commercial applications. The scope covers issues related to the mechanical design of actuators themselves, with limited reference to their control electronics. Additionally, this course will provide participants an understanding of the design considerations behind these actuation systems.

This four-hour short course will present an overview of hydraulically powered flight control actuation systems used on fly-by-wire aircraft, covering both military and commercial applications. The scope this course covers the issues related to the mechanical design of actuators themselves, as well as their control electronics. Additionally, this course will provide participants an overview of the design considerations behind these flight control actuation systems.

This four-hour short course intends to present an overview of electrohydraulic flow control servovalves commonly used in flight control and utility actuators. The scope of this course covers the history and design of servovalves, as well as their most common performance characteristics. This course will provide participants an understanding of the application of electrohydraulic servovalves in hydraulically powered actuators and preparation of the servovalve procurement specification.

This course is verified by Probitas Authentication as meeting the AS9104/3A requirements for continuing Professional Development. This four-hour short course will provide an overview of design considerations for electrohydrostatic actuation for transport and business aircraft applications.  The instructor will present the critical topics of electrohydrostatic actuation (EHA) from a systems development perspective (V-Approach).  Beginning with aircraft system requirements, the instructors will then guide participants through EHA subsystem requirements, component design, component verification test, aircraft integration, and use. 

The purpose of this four hour short course is to provide information to understand how is established the basic architecture of a Flight Control Actuation System of a transport airplane, i.e. understanding the rationale for the distribution of the control surfaces, power sources, actuators and computers.

This four-hour short course provides key considerations for the comparison of electrically supplied (Power-by-Wire, or PbW) and hydraulically supplied (Power-by-Pipe, of PbP) actuation for aerospace. The focus is put on the consequence, for designers, of changing the physical principles and the technology used. A particular attention is paid to the unavoidable side effects introduced by the technological realization. Simple examples with realistic numerical values are used to make the comparisons quantitatively realistic.

This basic course introduces the intent of the DO-254 standard for commercial avionics hardware development. The content will cover many aspects of avionic hardware including, aircraft safety, systems, hardware planning, requirements, design, implementation, and testing. Participants will learn industry-best practices for real-world hardware development, common DO-254 mistakes and how to prevent them, and how to minimize risks and costs while maximizing hardware quality.

This two-day course will introduce participants to industry best practices for real-world software development and how to avoid common DO-178C mistakes. This course is intended to present the information necessary to help minimize DO-178C risks and costs, while also maximizing software quality during avionics development.  The instructor will guide participants through topics such as aircraft safety, systems, software planning, software requirements, and software design/code/test.  

This course is offered in China only and presented in Mandarin Chinese. The course materials are bilingual (English and Chinese). Participants in this course comprehensive understanding of the DO-254 standard including how the development of airborne electronic hardware (AEH) and the development of the aircraft system are related. It addresses the key objectives, activities, and generated data of the AEH lifecycle and presents common problems in the application of DO-254 and how to prevent them. This course also includes current AEH certification requirements and interprets some of the difficulties in gaining compliance approval.

This course will introduce participants to industry best practices for real-world aviation cyber-security risk-assessment, development & assurance. Participants will learn the information necessary to help minimize DO-326/ED-202-set compliance risks and costs, while also optimizing cyber-security levels for the development, deployment and in-service phases Topics such as aircraft security aspects of safety, systems-approach to security, security planning, the airworthiness security process, and security effectiveness assurance will be covered.

This course is offered in China only and presented in Mandarin Chinese. The course materials are bilingual (English and Chinese). Participants deepen the understanding of the standard and build on how software engineers, inspectors, and DERs can comply with the standard's objectives. Practitioners engage with the implications and rationales of DO-178C in order to effectively tackle real worked applications.

This ARINC Standard specifies the ARINC 758 Mark 2 Communications Management Unit (CMU) as an on-board message router capable of managing various datalink networks and services available to the aircraft. Supplement 4 adds Ethernet interfaces, per ARINC Specification 664 Part 2. This will allow the CMU to communicate with IP based radio transceivers (e.g., L-Band Satellite Communication Systems (Inmarsat SwiftBroadband (SBB) and Iridium Certus), ACARS over IP, AeroMACS, etc.).

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.).

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.

The purpose of this document is to provide guidelines for integrating previously standalone cabin systems such as cabin management systems, In-Flight Entertainment (IFE) systems, In-Flight Connectivity (IFC) systems, galley systems, surveillance systems, etc. Resource sharing between systems can reduce airline costs and/or increase functionality. But, as systems expose their internal resources to external systems, the risk of an intrusion that could degrade function and/or negatively expose the supplier’s or airline’s brand increases. This document provides a recommended IP networking design framework between aircraft systems to reduce the operational security threats while still supporting the necessary intersystem routing.

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.

ARINC Report 686 represents the consensus of industry to prepare a roadmap migration from IPv4 to IPv6. This document describes airline objectives (air and ground side when possible) towards the development and introduction of IPv6. There are three distinct elements considered: 1) the applications for addressing aspects 2) the communication network(s) over which the applications are running for the IP protocol level itself and associated features, and 3) the physical link(s) the network(s) interface.