Abstract: A propulsion assembly having a pylon, a turbomachine comprising an engine and a fan that is enclosed by a fan casing, a nacelle surrounding the engine and the fan casing and having a load support disposed in the top part of the nacelle, a front engine attachment between the pylon and a front part of the engine, a rear engine attachment between the pylon and a rear part of the engine, a front fan attachment between the fan casing and the load support, and a rear pylon attachment between the pylon and the load support. Such a propulsion assembly allows a reduction in bulk since the load of the turbojet engine is distributed between the load support and the pylon, and the pylon is attached to the engine.

Abstract: A propulsion assembly having a pylon, a turbomachine comprising an engine and a fan that is enclosed by a fan casing, a nacelle surrounding the engine and the fan casing and having a load support disposed in the top part of the nacelle, a front engine attachment between the pylon and a front part of the engine, a rear engine attachment between the pylon and a rear part of the engine, a front fan attachment between the fan casing and the load support, and a rear pylon attachment between the pylon and the load support. Such a propulsion assembly allows a reduction in bulk since the load of the turbojet engine is distributed between the load support and the pylon, and the pylon is attached to the engine.

Abstract: A flight management system architecture with separate core and supplementary modules. In the core module, generic functionalties relative to the flight management of the aircraft are implemented. In the supplementary module, supplementary functions are implemented. The supplementary functionalities include functionalties specific to an entity to which the aircraft belongs such as the specific aircraft model, a family of aircraft, a company, an alliance, and so on. The flight management system also includes a message exchange interface in which enables the core and supplementary modules to exchanges messages with each other. The core and supplementary modules includes corresponding core module and supplementary module interfacing functionaltities that respectively interface with generic and specific man-machine interfaces.

Abstract: A flight management system with core and supplementary modules is proposed. The core module may include generic applications that implement generic functionalities related to a flight management of the aircraft. The supplementary module may include supplementary applications that implement supplementary functionalities specific to an entity to which the aircraft belongs. The supplementary module may be divided into principal and auxiliary partitions (or entities), and the supplementary applications, also referred to as principal applications, may be implemented in the principal partition. One or more auxiliary applications may be implemented in the auxiliary partition. Each auxiliary application may be associated with one or more principal applications such that the execution of the principal application requires the associated auxiliary application to be executed.

Abstract: A flight management system architecture with separate core and supplementary modules. In the core module, generic functionalties relative to the flight management of the aircraft are implemented. In the supplementary module, supplementary functions are implemented. The supplementary functionalities include functionalties specific to an entity to which the aircraft belongs such as the specific aircraft model, a family of airdraft, a company, an alliance, and so on. The flight management system also includes a message exchange interface in which enables the core and supplementary modules to exchanges messages with each other. The core and supplementary modules includes corresponding core module and supplementary module interfacing functionaltities that respectively interface with generic ans specific man-machine interfaces.

Abstract: A flight management system architecture with two separate modules is proposed. In the core module, generic functionalities relative to the flight management of the aircraft are implemented. In the supplementary module, supplementary functions are implemented. The supplementary functionalities include functionalities specific to an entity to which the aircraft belongs such as the specific aircraft model, a family of airdraft, a company, an alliance, and so on. The flight management system also includes a message exchange interface in which enables the core and supplementary modules to exchanges messages with each other. The core and supplementary modules includes corresponding core module and supplementary module interfacing functionalities that respectively interface with generic and specific man-machine interfaces.

Abstract: A flight management system includes: an avionics core implementing generic aircraft management functionalities and providing services associated with the generic functionalities; at least one remote functionality in an open world part performing a function of interfacing between the avionics core and the open world applications run on the open world part which need to communicate with the avionics core, wherein the remote functionality ensures homogeneity and consistency of data exchanged and guaranteeing integrity and security of data exchanges, and an exchange interface of between the avionics core and the open world functionality supporting data exchanges.

Abstract: A system to manage transmissions of data between a flight management system (e.g., of an avionics type) of an aircraft and a portable electronic (e.g., of an open world type) is proposed. The data management system may be implemented in flight management system architecture with core and supplementary modules that are distinct from each other. The core module may implement a set of generic functionalities related to a flight management of the aircraft, and the supplementary module may implement supplementary functionalities specific to an entity to which the aircraft belongs. The data management system may comprise a data securing module that monitors data to be transmitted between the flight management system and the portable electronic device, and allows or prevents the data transmission based on the monitoring results.

Abstract: A flight management system includes: an avionics core implementing generic aircraft management functionalities and providing services associated with the generic functionalities; at least one remote functionality in an open world part performing a function of interfacing between the avionics core and the open world applications run on the open world part which need to communicate with the avionics core, wherein the remote functionality ensures homogeneity and consistency of data exchanged and guaranteeing integrity and security of data exchanges, and an exchange interface of between the avionics core and the open world functionality supporting data exchanges.

Abstract: A mission management system to manage both ground and flight phases of a mission of an aircraft is proposed. The mission management system may be implemented in flight management system architecture with core and supplementary modules distinct from each other. The core module may implement a set of generic functionalities related to a flight management of the aircraft, and the supplementary module may implement supplementary functionalities specific to an entity to which the aircraft belongs. The mission management system may include a flight management unit to define and manage a flight plan and associated flight trajectory, an airport navigation unit to define and manage a ground plan and associated ground trajectory, and a mission management unit to manage a continuity between the ground and flight phases of the mission and prediction computations made by the flight management and the airport navigation units.

Abstract: A flight management system with core and supplementary modules is proposed. The core module may include generic applications that implement generic functionalities related to a flight management of the aircraft. The supplementary module may include supplementary applications that implement supplementary functionalities specific to an entity to which the aircraft belongs. The supplementary module may be divided into principal and auxiliary partitions (or entities), and the supplementary applications, also referred to as principal applications, may be implemented in the principal partition. One or more auxiliary applications may be implemented in the auxiliary partition. Each auxiliary application may be associated with one or more principal applications such that the execution of the principal application requires the associated auxiliary application to be executed.

Abstract: A flight management system architecture with two separate modules is proposed. In the core module, generic functionalties relative to the flight management of the aircraft are implemented. In the supplementary module, supplementary functions are implemented. The supplementary functionalities include functionalties specific to an entity to which the aircraft belongs such as the specific aircraft model, a family of airdraft, a company, an alliance, and so on. The flight management system also includes a message exchange interface in which enables the core and supplementary modules to exchanges messages with each other. The core and supplementary modules includes corresponding core module and supplementary module interfacing functionaltities that respectively interface with generic and specific man-machine interfaces.

Abstract: A system to manage transmissions of data between a flight management system (e.g., of an avionics type) of an aircraft and a portable electronic (e.g., of an open world type) is proposed. The data management system may be implemented in flight management system architecture with core and supplementary modules that are distinct from each other. The core module may implement a set of generic functionalities related to a flight management of the aircraft, and the supplementary module may implement supplementary functionalities specific to an entity to which the aircraft belongs. The data management system may comprise a data securing module that monitors data to be transmitted between the flight management system and the portable electronic device, and allows or prevents the data transmission based on the monitoring results.

Abstract: A mission management system to manage both ground and flight phases of a mission of an aircraft is proposed. The mission management system may be implemented in flight management system architecture with core and supplementary modules distinct from each other. The core module may implement a set of generic functionalities related to a flight management of the aircraft, and the supplementary module may implement supplementary functionalities specific to an entity to which the aircraft belongs. The mission management system may include a flight management unit to define and manage a flight plan and associated flight trajectory, an airport navigation unit to define and manage a ground plan and associated ground trajectory, and a mission management unit to manage a continuity between the ground and flight phases of the mission and prediction computations made by the flight management and the airport navigation units.