Method and device for adjusting performance variables of an aircraft

Abstract

A method and device for adjusting performance variables of an aircraft. The device which is intended for adjusting performance variables, the performance variables being generated by at least one performance module, includes an auxiliary data input unit for entering into a flight management system correction data intended to be used for adjusting at least one associated performance variable, and a correction unit for carrying out a correction, the correction including adjusting the associated performance variable on the basis of the input correction data.

Claims

1. A method for adjusting performance variables of an aircraft, the method comprising: a correction data input step, implemented by at least one auxiliary data input, comprising entering correction data into a computer and/or the flight management system, the correction data to be used for adjusting at least one associated performance variable; a checking step comprising checking, during the correction data input step, if the entered correction data are in conformity with a set of authorizations and prohibitions, the set of authorizations and prohibitions being predetermined and recorded in a memory, the checking step also comprising issuing a correction authorization or a correction rejection as a function of a result of the checking step; and a correction step, implemented by the flight management system, comprising carrying out a correction solely upon issuance of the correction authorization during the checking step, the correction comprising adjusting the associated performance variable based on the correction data.

2. The method according to claim 1, wherein the set of authorizations and prohibitions comprises at least one of: at least one list of performance variables, for which a correction is authorized; parameters as a function of which the correction data are defined; acceptable limit values for the values of the correction data; and at least one list of performance variables, for which a correction is not authorized.

3. The method according to claim 1, wherein the correction data comprises at least one of: a multiplier and/or a bias; and a mathematical function.

4. The method according to claim 3, wherein the correction step comprises: for an item of correction data corresponding to a multiplier and/or to a bias, applying the multiplier and/or the bias to the associated performance variable; and for an item of correction data corresponding to a mathematical function, applying the mathematical function to the associated performance variable.

5. The method according to claim 1, comprising an alert step comprising generating an indication of rejection of correction data, intended for at least one operator, when the correction rejection is issued in the checking step.

6. The method according to claim 1, wherein the auxiliary data input comprises a data transmission link.

7. The method according to claim 1, wherein the auxiliary data input comprises a data loading and configuration system of a DLCS (Data Loading Configuration System) type.

8. The method according to claim 1, wherein the auxiliary data input comprises an onboard electronic device comprising applications.

9. A device for adjusting performance variables of an aircraft, the device comprising: at least one auxiliary data input for entering correction data into a computer and/or the flight management system, the correction data being configured for use in adjusting at least one associated performance variable; a checking unit for checking, while the correction data is entered into computer and/or the flight management system, if the entered correction data are in conformity with a set of authorizations and prohibitions, the set of authorizations and prohibitions being predetermined and recorded in a memory, the checking unit also being configured to issue a correction authorization or a correction rejection as a function of whether the entered correction data are in conformity with the set of authorizations and prohibitions; and a correction unit configured for carrying out a correction comprising adjusting the associated performance variable based on the correction data solely upon issuance of the correction authorization by the checking unit.

10. The device according to claim 9, wherein the device is configured to generate an indication of rejection of correction data, intended for at least one operator, when the correction rejection is issued by the checking unit.

11. The device according to claim 9, wherein the auxiliary data input comprises a data transmission link.

12. The device according to claim 9, wherein the auxiliary data input comprises a data loading and configuration system of a DLCS (Data Loading Configuration System) type.

13. The device according to claim 9, wherein the auxiliary data input comprises an onboard electronic device comprising applications.

14. A flight management system of an aircraft, the flight management system comprising: at least one performance database; at least one data input; a performance computation unit configured to generate performance variables based on data from the at least one performance database and on data entered using the data input unit; and at least one device for adjusting performance variables according to claim 9.

15. The flight management system according to claim 14, wherein the memory is separate from the at least one performance database.

16. The flight management system according to claim 14, wherein the set of authorization and prohibitions comprises at least one of: at least one list of performance variables, for which a correction is authorized; parameters as a function of which the correction data are defined; acceptable limit values for the values of the correction data; and at least one list of performance variables, for which a correction is not authorized.

17. The flight management system according to claim 14, wherein the memory is a part of the at least one performance database.

18. The device according to claim 9, wherein the set of authorization and prohibitions comprises at least one of: at least one list of performance variables, for which a correction is authorized; parameters as a function of which the correction data are defined; acceptable limit values for the values of the correction data; and at least one list of performance variables, for which a correction is not authorized.

19. The device according to claim 9, wherein the correction data comprises at least one of: a multiplier and/or a bias; and a mathematical function.

20. The device according to claim 19, wherein: when an item of correction data corresponds to a multiplier and/or to a bias, the correction unit is configured to apply the multiplier and/or the bias to the associated performance variable; and when an item of correction data corresponds to a mathematical function, the correction unit is configured to apply the mathematical function to the associated performance variable.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

(1) The appended figures will give a good understanding of how the disclosure herein may be embodied. In these example figures, identical references denote similar elements. More particularly:

(2) FIG. 1A is a block diagram of a particular embodiment of a flight management system comprising a device for adjusting performance variables;

(3) FIG. 1B is a block diagram of a variant of the embodiment shown in FIG. 1A; and

(4) FIG. 2 is the block diagram of a method for adjusting performance variables implemented by the device shown in FIG. 1.

DETAILED DESCRIPTION

(5) The device 1 illustrating an embodiment corresponding to a first alternative embodiment of the disclosure herein and shown in block diagram form in FIG. 1A is intended for adjusting performance variables of an aircraft, in particular of a transport aircraft.

(6) The performance variables are generated by at least one performance module 2 integrated in a flight management system 3 of the FMS (standing for Flight Management System in English) type, also shown in FIG. 1A, and can be used by the flight management system 3 and/or can be supplied via a link 18 to a user system (not shown).

(7) The device 1 forms part of the flight management system 3.

(8) As shown in FIG. 1A, the performance module 2 which uses at least one performance model, comprises:

(9) a (performance) computation unit 4 COMP (standing for Performance Computation Unit in English);

(10) at least one performance database 5 PDB (standing for Performance Data Base in English); and

(11) at least one data input unit 6 (INPUT1) making it possible to enter data, into the flight management system 3, as illustrated by an arrow 7.

(12) The data entered, via the data input unit 6, can be data entered manually by the pilot, data transmitted by a data link of the airline company to which the aircraft belongs and options configurable by the airline company. The data input unit 6 is configured, in the usual way, in order to allow such data inputs.

(13) The computation unit 4 carries out, in the usual way, performance computations which are required for accomplishing various functions, for example in order to provide fuel consumption and/or flight time of the aircraft along a flight plan predictions. In order to do this, the computation unit 4 contains usual algorithms which make it possible to compute from a set of input data a set of variables at the output relating to the performance of the aircraft.

(14) These performance variables resulting from a performance computation are generated by the computation unit 4 on the basis of data coming from the performance database 5 and of data entered by the data input unit 6.

(15) By way of illustration, a performance variable V.sub.i({X}) can depend on a vector of parameters {X} comprising a plurality n of parameters x.sub.j, namely {X}={x.sub.1, x.sub.2, . . . , x.sub.n}.

(16) The performance data are loaded into the performance database 5 via a link 9. The performance database 5 comprises one or more performance files. Each performance file contains a set of data relating to the engine or to the aerodynamics or other data relative to performance such as the characteristic speeds of the aircraft, this being for a given type of aircraft, that is to say for a particular combination of a given type of aerodynamic structure and a given type of engines.

(17) The input data can be the weight of the aircraft, thrust adjustments or correction factors which are intended to better adjust the performance model of the aircraft. The following can be mentioned in particular:

(18) a performance factor which is used for adjusting the fuel flow such as represented in the performance model; and

(19) an idling factor which is used for adjusting the idling thrust produced by the engine such as represented in the performance model.

(20) A purpose of these factors is to compensate for the differences between the data associated with the type of the aircraft in the performance database and individual characteristics of the aircraft, which can notably exhibit degraded performance due to age. The performance model which comprises a performance file and correction factors such as the aforethe performance and idling factors, is not sufficiently accurate to be able to represent the individual performance of the aircraft in different flight conditions such as the takeoff, the climb, the cruising flight, the descent, the landing, etc.

(21) Also, in order to refine (or adjust) the performance variables, the device 1 comprises, according to the embodiment of the disclosure herein:

(22) at least one auxiliary data input unit 10 (INPUT2) configured for entering correction data into the flight management system 3, as illustrated by an arrow 11. The input correction data are representative of current effective characteristics and capabilities of the aircraft and are intended to be used for adjusting at least one so-called associated performance variable;

(23) a checking unit 12 CHECK (standing for Checking Unit in English) which is configured for checking, during the input of correction data via the auxiliary data input unit 10, if the input correction data are in conformity with a set of authorizations and prohibitions. The authorizations and prohibitions are predetermined and are recorded (or loaded) via a link 13 in a memory 14 AUTHORIZED (standing for Authorized correction in English). The checking unit 12 is also configured for issuing a correction authorization or a correction rejection as a function of the result of the check that it carries out; and

(24) a correction unit 15 CORRECT (standing for Correction Unit in English) which is configured for carrying out a correction, and for doing so solely in the case of the issue of a correction authorization by the checking unit 12. The correction consists of or comprises adjusting the associated performance variable (by correcting it) on the basis of the correction data entered by the auxiliary data input unit 10. The results can be used by the system.

(25) Thus, the device 1 is capable of correcting performance variables computed on the basis of the performance database 5 (which is intended for a type of aircraft) in order to optimize them, by adapting them (or adjusting them) to the characteristics peculiar to the aircraft in question, this being via correction data representative of the current effective characteristics and capabilities of the aircraft in question. This adaptation is carried out without having to generate a new performance database.

(26) The set of authorizations and prohibitions, stored in the memory 14, comprises at least one of the following elements:

(27) at least one list of performance variables, for which a correction is authorized and, additionally, a list of performance variables for which a correction is not authorized. These two lists are mutually exclusive and together cover all of the performance variables computed on the basis of each performance file;

(28) parameters on the basis of which the correction data are defined. It is stated how the corrections are specified (as a function of which parameters). The parameters which can be used for defining the corrections must be compatible with a list of parameters which can be used for defining correction data and interpolation functionalities, for example the Mach number, the weight, the attitude, the centre of gravity. In general, the parameters which are already used for defining the data of the initial performance file can also be used as parameters for the correction data. For example, in the case where a scale factor (or multiplier) S.sub.i is defined for adjusting a performance variable computed on the basis of the performance data L.sub.i, the parameters {Y} for tabulating S.sub.i are specified, for example {Y}={Mach,CG}, CG representing the centre of gravity of the aircraft;

(29) acceptable limit values for the limit values that a correction can have. By way of example, in the case of a correction in the form of a scale factor S.sub.i({Y}) as described above, a table of maximum authorized values S.sub.i.sup.MAX({Y}) and a table of minimum authorized values S.sub.i.sup.MIN({Y}) are defined numerically.

(30) The definition of the performances and the production of the performance database 5 is, in general, the responsibility of the original manufacturer of the aircraft. In the context of the present disclosure, the definition of all of the authorizations and prohibitions is also preferably allocated to the original manufacturer of the aircraft. Thus, the subsequent adjustment of the performance variables can be limited to that which is (previously) authorized by the original manufacturer.

(31) Moreover, the correction data comprise at least one of the following elements:

(32) a scale factor (or multiplier) and/or a bias;

(33) a mathematical function.

(34) In a particular embodiment, the units 4, 12 and 15 form part of a central processing unit 8.

(35) Moreover, the device 1 also comprises an alert unit 16 ALERT (standing for Alert Unit in English), for example a display screen, which is configured for generating an indication of correction rejection, of an audible and/or visual type, for at least one operator, when a correction rejection is issued by the checking unit 12.

(36) In a first embodiment, the memory 14, in which the authorizations and prohibitions are recorded, forms part of the same database as the performance database 5, as illustrated by a reference 17 in FIG. 1.

(37) Moreover, in a second embodiment, the memory 14 is separate from the performance database 5.

(38) In the context of the present disclosure, memory is understood to be any element or storage space able to store data.

(39) Moreover, in a particular embodiment, the auxiliary data input unit 10 comprises at least one (and preferably several) of the following elements:

(40) a data transmission link. In this case, data correction tables are transmitted to the flight management system 3, by AOC messages through the (wireless) data transmission link, using for example the ACARS system or other data link(s). The flight management system 3 comprises appropriate functions for receiving and storing the data (including an automatic reception by data link of several successive messages if the correction data does not form part of an individual message);

(41) a data loading and configuration system of the DLCS type. In this case, the data correction tables are transmitted to the flight management system 3 via the data loading and configuration system;

(42) an onboard electronic device comprising applications, of the EFB (standing for Electronic Flight Bag in English) type. In this case, the correction data are transmitted to the flight management system 3 by the electronic device; and/or

(43) a manual input unit. In this case, the correction data are entered manually into the flight management system 3 by an operator via a dedicated interface comprising that manual input unit.

(44) The functioning of the device 1 such as described above is explained below by presenting an adjustment method that it implements. This adjustment method comprises, notably, the following steps E1 to E3, as shown in FIG. 2:

(45) a correction data input step E1, implemented by the auxiliary data input unit 10, consisting of or comprising entering correction data into the flight management system 3, the correction data being representative of current effective characteristics and capabilities of the aircraft and being intended to be used for adjusting at least one so-called associated performance variable;

(46) a checking step E2, implemented by the checking unit 12, consisting of or comprising checking, during the entry of correction data, if the input correction data are in conformity with a set of authorizations and prohibitions, the authorizations and prohibitions being predetermined and recorded in the memory 14 of the flight management system 3, the checking step E2 consisting of or comprising issuing a correction authorization or correction rejection as a function of the result of the check; and

(47) a correction step E3, implemented by the correction unit 15, consisting of or comprising carrying out a correction solely in the case of issue of a correction authorization during the checking step E2, the correction consisting of or comprising adjusting (by correcting it) an associated performance variable on the basis of the correction data.

(48) The method also comprises:

(49) a prior step E0 consisting of or comprising determining the authorizations and prohibitions and of recording them in the memory 14 of the flight management system 3; and

(50) an alert step E4, implemented by the alert unit 16, consisting of or comprising generating a correction rejection indication, to at least one operator, when a correction rejection is issued in the checking step E2.

(51) The checking step E2 therefore consists of or comprises checking to determine if the input correction data is in conformity with the set of authorizations and prohibitions contained in the memory 14.

(52) By way of illustration, it can be a matter of checking if the parameters on the basis of which the correction data are defined are the same as those of the correction authorizations. In this case, for example for a correction in the form of a scale factor which depends in the correction data on the Mach number and altitude parameters, if the corresponding definition of the authorized correction data depends on the Mach number and the centre of gravity, the correction request is rejected, because the names of the parameters are not all in conformity.

(53) By way of additional illustration, it can also be a matter of checking if all of the tabulated numerical values of the correction data are within the authorized maximum and minimum numerical values. In this case, for example for tabulated values of a scale factor S.sub.i({Y}) in the correction data and tabulated values of S.sub.i.sup.MAX({Y}) and of S.sub.i.sup.MIN({Y}) within the authorized correction limits, the correction is authorized if for all of the tabulated elements of S.sub.i({Y}) the following rule is verified: S.sub.i.sup.MIN({Y})S.sub.i({Y})S.sub.i.sup.MAX({Y}). If not, the correction data is rejected.

(54) In a first embodiment, the correction implemented by the correction unit 15, in the correction step E3, consists of or comprises, for an item of correction data corresponding to a scale factor and/or to a bias, applying this scale factor and/or this bias to the associated performance variable in order to obtain a corrected (or adjusted) performance variable.

(55) By way of example, the correction data correspond to a scale factor S.sub.i({Y}) and to a bias B.sub.i({Z}), obtained by interpolation on the basis of a set of correction data S.sub.i and B.sub.i respectively using vectors of parameters {Y} and {Z}. The correction data S.sub.i and B.sub.i are associated with a performance variable V.sub.i({Y}) computed from the data L.sub.i using the vector of parameters {X}. The computation formula used for obtaining the corrected performance variable V.sub.icorr (destined to replace the variable V.sub.i coming from the performance module 2) is in this case:
V.sub.i corr({X},{Y},{Z})=S.sub.i({Y})*V.sub.i({X})+B.sub.i({Z}).

(56) Moreover, in a second embodiment, the correction implemented by the correction unit 15, in the correction step E3, consists of or comprises, for an item of correction data corresponding to a mathematical function, applying that mathematical function to the performance variable in order to obtain a corrected variable intended to replace it.

(57) More precisely, the correction data can correspond to quantities defining a polynomial function, an exponential function, a logarithmic function, a neural network or another mathematical function.

(58) For example, in the context of a quadratic polynomial function, the correction data correspond to the coefficients of that function: A.sub.i({Y}), C.sub.i({Z}), D.sub.i({U}). In this case, the correction unit 15 computes the corrected correction variable V.sub.icorr, according to this type of function or functions. For the example of the quadratic polynomial function, the following is obtained for the corrected variable V.sub.icorr (intended to replace the variable V.sub.i):
V.sub.i corr({X},{Y},{Z},{U})=A.sub.i({Y})*V.sub.i({X}).sup.2+C.sub.i({Z})*V.sub.i({X})+D.sub.i({U}).

(59) In an embodiment corresponding to a second alternative embodiment of the disclosure herein and shown in FIG. 1B, the performance module 2, integrated in the flight management system 3 of the FMS type and which implements at least one performance model, comprises:

(60) a (performance) computation unit 4 COMP (standing for Performance Computation Unit in English);

(61) at least one performance database 5 PDB (standing for Performance Data Base in English); and

(62) at least one data input unit 6 (INPUT1) making it possible to enter data, into the flight management system 3, as illustrated by an arrow 7.

(63) In order to refine (or adjust) the performance variables, the device 1 comprises:

(64) at least one auxiliary data input unit 20A (LOAD) configured for entering correction data into the flight management system 3, as illustrated by an arrow 21. The input correction data are representative of current effective characteristics and capabilities of the aircraft and are intended to be used for adjusting at least one so-called associated performance variable; and

(65) a correction unit 15 CORRECT (standing for Correction Unit in English) which is configured for carrying out a correction. The correction consists of or comprises adjusting the associated performance variable (by correcting it) on the basis of the correction data entered via the auxiliary data input unit 20A. The results can be used by the system.

(66) The correction data are prepared and checked outside of the system 1, in particular on the ground, for example in an operational centre of the airline company operating the aircraft, by a computer 22. As shown in FIG. 1B, this computer 22 comprises: at least one data input unit 10B (INPUT2) configured for entering correction data into the computer 22, as illustrated by an arrow 11B. The input correction data are representative of current effective characteristics and capabilities of the aircraft and are intended to be used for adjusting at least one so-called associated performance variable; a checking unit 12B CHECK (standing for Checking Unit in English) which is configured for checking, during the input of correction data via the auxiliary data input unit 10B, if the input correction data are in conformity with a set of authorizations and prohibitions. The authorizations and prohibitions are predetermined and are recorded (or loaded) in a memory 14B AUTHORIZED (standing for Authorized correction in English). The checking unit 12B is also configured for issuing a correction authorization or a correction rejection as a function of the result of the check that it carries out; and a load generation unit 20G (LOAD) configured for producing at least one load file when a correction authorization is issued by the checking unit 12B. This load file is intended to be loaded into the flight management system 3 of the aircraft. The load file contains the correction data entered into the computer 22 by the data input unit 10B (possibly converted into a binary format), as well as an electronic signature making it possible to check the integrity and the authenticity of the file.

(67) Moreover, the computer 22 also comprises an alert unit 16B ALERT (standing for Alert Unit in English), for example a display screen, which is configured for generating an indication of correction rejection, of audible and/or visual type, for at least one operator, when a correction rejection is issued by the checking unit 12B.

(68) The input of the correction data into the flight management system 3, by the auxiliary data input unit 20A, such as illustrated by the arrow 21 corresponds to the loading into the flight management system 3 of a load file produced by the computer 22 as described above. According to one embodiment, this load file can be loaded into the flight management system 3 by a data link (represented in FIG. 1B by a dashed line between the computer 22 and the flight management system). According to another embodiment, the load file can be loaded into the flight management system 3 by a data loading and configuration system of the DLCS type. According to yet another embodiment, the load file can be loaded into the flight management system 3 by an onboard electronic device comprising applications, of the EFB type. The auxiliary data input unit 20A checks the validity of the electronic signature of the load file and accepts the correction data contained in the load file only if the electronic signature is valid. The checking of the validity of the electronic signature makes it possible to ensure, on the one hand, that the correction data are actually coming from the computer 22 and, on the other hand, that these correction data have been verified as being in conformity with the set of authorizations and prohibitions by the checking unit 12B of the computer 22.

(69) In comparison with the first alternative, in the second alternative, the checking unit 12B, and the memory 14B, are shifted from the flight management system 3 to the computer 22 outside of the flight management system. This makes it possible to reduce the complexity of the flight management system 3 in comparison with the first alternative.

(70) The different embodiments described with reference to the first alternative shown in FIG. 1A are also able to be applied to the second alternative shown in FIG. 1B, insofar as they are technically compatible with that second alternative. Consequently, these embodiments will not be further described in the context of the second alternative.

(71) The subject matter disclosed herein can be implemented in software in combination with hardware and/or firmware. For example, the subject matter described herein can be implemented in software executed by a processor or processing unit. In one exemplary implementation, the subject matter described herein can be implemented using a computer readable medium having stored thereon computer executable instructions that when executed by a processor of a computer control the computer to perform steps. Exemplary computer readable mediums suitable for implementing the subject matter described herein include non-transitory devices, such as disk memory devices, chip memory devices, programmable logic devices, and application specific integrated circuits. In addition, a computer readable medium that implements the subject matter described herein can be located on a single device or computing platform or can be distributed across multiple devices or computing platforms.

(72) While at least one exemplary embodiment of the invention(s) is disclosed herein, it should be understood that modifications, substitutions and alternatives may be apparent to one of ordinary skill in the art and can be made without departing from the scope of this disclosure. This disclosure is intended to cover any adaptations or variations of the exemplary embodiment(s). In addition, in this disclosure, the terms comprise or comprising do not exclude other elements or steps, the terms a, an or one do not exclude a plural number, and the term or means either or both. Furthermore, characteristics or steps which have been described may also be used in combination with other characteristics or steps and in any order unless the disclosure or context suggests otherwise. This disclosure hereby incorporates by reference the complete disclosure of any patent or application from which it claims benefit or priority.