Systems and methods for aircraft thrust rating model processing

By accessing and checking engine data in the FMC's non-volatile memory to align with EEC data, the system addresses data duplication issues, ensuring accurate and efficient thrust model calculations in aircraft systems.

JP2024167168APending Publication Date: 2024-12-03THE BOEING CO
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
JP2024078989
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-05-15
Filing Date
2024-05-14
Publication Date
2024-12-03

AI Technical Summary

Technical Problem

The duplication of Thrust Rating Model (TRM) data in both the Flight Management Computer (FMC) and the Electronic Engine Controller (EEC) of an aircraft leads to inefficiencies and potential errors due to mismatched data updates.

Method used

The FMC accesses engine data from non-volatile memory and performs error checking operations to select an engine thrust rating based on engine rating identifiers, ensuring consistency with EEC data, and dynamically updates the thrust model data to avoid manual errors.

Benefits of technology

This approach reduces redundant data storage, minimizes errors, and ensures accurate thrust model calculations by maintaining consistent engine data across systems, enhancing flight management efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024167168000001_ABST
    Figure 2024167168000001_ABST
Patent Text Reader

Abstract

To provide determination of thrust rating model data to be used by an aircraft.SOLUTION: An aircraft includes engines, electronic engine controllers (EECs) associated with the engines, and a flight management computer (FMC). An error check operation of the (FMC) is performed to determine whether to select an engine thrust model based on an engine rating identifier associated with engine data. The processor is also configured to select, based on a plurality of local thrust rating model (TRM) identifiers, intermix thrust model data to be used by the (FMC) during a flight of the aircraft. The intermix thrust model data is associated with a thrust model identifier that is common to two or more engines of the aircraft.SELECTED DRAWING: Figure 2
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001]

[0001] The present disclosure relates generally to determining thrust rating model data for use by aircraft. [Background technology]

[0002]

[0002] A flight management computer (FMC) installed in a modern aircraft performs various functions such as navigation, guidance, flight planning, data link, and performance management. For example, the performance management function of the FMC uses airplane and engine models and optimization algorithms to generate a full flight regime vertical profile consistent with the selected performance mode within the constraints of the flight plan. Inputs to the performance management function include, for example, fuel flow, total fuel, engine data and limits, altitude, airspeed, Mach number, temperature, vertical speed, progress along the flight plan, and pilot input from the flight display unit (CDU). Based on these inputs and the airplane and engine models, the performance management function outputs information such as the results of the thrust limit calculation (TLC), target Mach numbers, target calibrated airspeed (CAS) values, target thrust values, and flight crew advisory data. The performance management function may also use aerodynamic and propulsive performance data stored in a performance database (PDB) to calculate a predicted flight profile and associated trip forecast parameters, such as economy speed, optimum altitude, expected arrival time, and predicted fuel consumption.

[0003] To perform various calculations of performance management functions, the FMC uses large data set tables (Performance Data Refinement (PDR) tables). At least some of these data tables duplicate data that is also stored in the Electronic Engine Controller (EEC) of each engine of the aircraft. For example, one type of data used by the FMC is Thrust Rating Model (TRM) data. TRM data for each engine of the aircraft is traditionally stored in both the FMC and the engine's EEC. This duplication of data storage is inefficient and can lead to errors if one set of tables is updated and the other is not. Summary of the Invention

[0004] In one particular embodiment, a method includes accessing, by one or more processors of a Flight Management Computer (FMC) of the aircraft, first engine data from a non-volatile memory of the FMC. The method also includes performing, by the one or more processors, one or more error checking operations based on at least the first engine data to determine whether to select an engine thrust rating for a thrust model of the aircraft based in part on a first engine rating identifier associated with the first engine data.

[0005] In another particular embodiment, an aircraft includes two or more engines and two or more electronic engine controllers (EECs). Each EEC is associated with a respective one of the two or more engines. The aircraft also includes an FMC communicatively coupled to the two or more EECs. The FMC includes a non-volatile memory and one or more processors configured to access first engine data from the non-volatile memory. The one or more processors are also configured to perform one or more error checking operations based on at least the first engine data to determine whether to select an engine thrust rating for a thrust model of the aircraft based in part on a first engine rating identifier associated with the first engine data.

[0006]

[0006] In another particular embodiment, a non-transitory computer-readable medium stores a plurality of instructions executable by one or more processors. The instructions, when executed, cause the one or more processors to access engine data associated with an engine of the aircraft from a non-volatile memory of the FMC. The instructions further cause the one or more processors to perform one or more error checking operations based at least on the engine data. The instructions further cause the one or more processors to select an engine thrust rating for a thrust model of the aircraft. The engine thrust rating is selected from among the engine data accessed from the non-volatile memory or from engine data received from an EEC of the aircraft based at least in part on a result of the one or more error checking operations.

[0007] In another particular embodiment, a method includes determining, by one or more processors of the FMC between power-up of an FMC of an aircraft and subsequent takeoff of the aircraft, a plurality of local thrust rating model (TRM) identifiers including at least one TRM identifier for each respective one of a plurality of engines of the aircraft. The method also includes selecting, by the one or more processors of the FMC based on the plurality of local TRM identifiers, intermix thrust model data to be used by the FMC during flight of the aircraft. The intermix thrust model data is associated with a thrust model identifier common to the plurality of engines.

[0008]

[0008] In another particular embodiment, an aircraft includes two or more engines and two or more EECs. Each EEC is associated with a respective one of the two or more engines. The aircraft also includes an FMC communicatively coupled to the two or more EECs. The FMC includes one or more processors. The one or more processors are configured to determine, between power-up of the FMC and subsequent takeoff of the aircraft, a plurality of local TRM identifiers including at least one local TRM identifier for each respective one of the two or more engines. The one or more processors are also configured to select intermix thrust model data for use by the FMC during flight of the aircraft based on the plurality of local TRM identifiers. The intermix thrust model data is associated with a thrust model identifier common to the two or more engines.

[0009]

[0009] In another particular embodiment, a non-transitory computer-readable medium stores a plurality of instructions executable by one or more processors. The instructions, when executed, cause the one or more processors to determine, between power-up of an aircraft FMC and subsequent takeoff of the aircraft, a plurality of local TRM identifiers including at least one TRM identifier for each respective one of a plurality of engines of the aircraft. The instructions further cause the one or more processors to select intermix thrust model data for use by the FMC during flight of the aircraft based on the plurality of local TRM identifiers. The intermix thrust model data is associated with a thrust model identifier common to the plurality of engines.

[0010]

[0010] The features, functions, and advantages described herein may be realized alone in various implementations or may be combined in yet other implementations, further details of which may be understood with reference to the following description and drawings. [Brief description of the drawings]

[0011] [Figure 1]

[0011] FIG. 1 is a diagram illustrating an example of an aircraft in accordance with certain embodiments of the present disclosure. [Diagram 2]

[0012] 2 is a flow chart illustrating an example of a method for dynamically determining thrust model data for an aircraft in accordance with certain aspects of the present disclosure. [Diagram 3]

[0013] 3 is a flow chart illustrating an embodiment of a method for initialization that may be performed as an aspect of the method of FIG. 2. [Figure 4]

[0014] 4, 5 and 6 are flow charts illustrating an embodiment of a method of narrowing a selection range that may be performed as an aspect of the method of FIG. [Diagram 5] 4, 5 and 6 are flow charts illustrating an embodiment of a method of narrowing a selection range that may be performed as an aspect of the method of FIG. [Figure 6] 4, 5 and 6 are flow charts illustrating an embodiment of a method of narrowing a selection range that may be performed as an aspect of the method of FIG. [Figure 7]

[0015] 3 is a flow chart showing an embodiment of a rating processing method that may be implemented as an aspect of the method of FIG. 2. [Figure 8]

[0016] 3 is a flow chart illustrating an embodiment of a method of selection processing that may be performed as an aspect of the method of FIG. 2. [Figure 9]

[0017] 2 is a flow chart illustrating an embodiment of the life cycle of the aircraft of FIG. 1. [Figure 10]

[0018] FIG. 2 is a block diagram of a particular implementation of the aircraft of FIG. 1 . [Figure 11]

[0019] FIG. 1 is a block diagram of a computing environment including a computing device configured to support aspects of computer-implementable methods and computer-executable program instructions (or codes) according to the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0012]

[0020] The systems and methods disclosed herein reduce duplicate data storage by an aircraft's FMC and EEC. In particular, the FMC stores in non-volatile memory engine data associated with the most recent in-flight engine configuration. Other TRM tables and engine data are stored in the EEC but are not duplicated with the FMC. One technical advantage of such an arrangement is more efficient memory utilization since duplicate data is not stored in multiple places. Another technical advantage is reduced opportunity for error due to one data set (e.g., data stored in the EEC) differing from another data set (e.g., data stored in the FMC). For example, as described in more detail below, when new engine data is needed by the FMC, the engine data can be accessed from the EEC, thereby avoiding data mismatches.

[0013]

[0021] In the disclosed system and method, engine data common between the EEC and the TRM of the FMC is uploaded on demand from the EEC to the FMC. The FMC will maintain a copy of the engine data from the EEC in the non-volatile memory (NVM) of the FMC. During initialization, the integrity of the engine data stored in the NVM of the FMC is checked for internal consistency as well as consistency with the engine data stored in the EEC. For example, a cyclic redundancy check (CRC) or other error detection operation may be used to determine whether the engine data stored in the NVM should be used or whether data from one or more of the EECs should be requested. In normal operation, it is expected that the engine data stored in the NVM of the FMC will pass the data integrity check. The FMC will then use the engine data from the NVM for thrust model calculations during the subsequent flight.

[0014]

[0022] In non-normal operation, the engine data stored in the MVM of the FMC cannot be expected to pass the data integrity check. For example, a CRC value calculated based on the engine data stored in the NVM of the FMC may not match an expected CRC value for the engine data, such as due to a bit flip as a result of electromagnetic interference or another failure of the NVM. As another example, a CRC value calculated based on the engine data stored in the NVM of the FMC may not match a CRC value from one of the EECs, indicating that the engine data stored in the NVM does not match the engine data stored in the EEC (e.g., due to an engine change). In such non-normal conditions, the FMC retrieves engine data from one or more of the EECs, stores the retrieved engine data in the NVM, and uses the retrieved engine data for subsequent in-flight thrust model calculations.

[0015]

[0023] Because the FMC maintains engine data associated with the most recently detected configuration, when new engine data is obtained from one or more of the EECs, the disclosed system and method dynamically narrows the selection range of engine thrust ratings that are compatible with all of the aircraft's engines. A technical advantage of dynamically narrowing the selection range of engine thrust ratings that are compatible with all of the aircraft's engines is that it reduces the opportunity for error. For example, in a system in which the FMC replicates all of the TRM data stored in the EEC, the narrowing of the selection range is performed manually and saved as a configuration setting. When one or more of the aircraft's engines are replaced or significantly overhauled and updated, the configuration setting indicating the engine thrust ratings that are compatible with all of the engines would have to be manually updated. By dynamically performing the operations to narrow the selection range of compatible engine thrust ratings for the aircraft's engines, the possibility of manual updates being omitted or performed incorrectly can be avoided.

[0016]

[0024] The drawings and the following description show several specific exemplary embodiments. Those skilled in the art will recognize that, even if not explicitly described or shown in the present specification, they may devise various configurations that embody the principles described herein and are included in the scope of the claims that follow this specification. Furthermore, any examples described herein are intended to aid in the understanding of the principles of the present disclosure and are not intended to be limiting. As a result, the present disclosure is not limited to the specific embodiments or examples described below, but is limited by the claims and their equivalents.

[0017]

[0025] Certain embodiments are described herein with reference to the drawings. In the description, common features are given common reference numbers throughout the drawings. In some drawings, multiple instances of a particular type of feature are used. Although these features are physically and / or logically different, the same reference number is used for each, and the different instances are distinguished by adding a letter to the reference number. When features as a group or type are referred to herein (e.g., when no particular one of the features is referred to), the reference number is used without a distinguishing letter. However, when one particular feature of multiple features of the same type is referred to herein, the reference number is used with a distinguishing letter. For example, referring to FIG. 1, multiple engines are shown and associated with reference numbers 102A and 102B. When referring to a particular one of these engines, such as engine 102A, the distinguishing letter "A" is used. However, when referring to any one of these engines or these engines as a group, the reference number 102 is used without a distinguishing letter.

[0018]

[0026] As used herein, various terms are used for the purpose of describing particular embodiments only and are not intended to be limiting. For example, the singular forms "a," "an," and "the" are intended to include the plural, unless the context clearly indicates otherwise. Additionally, some features described herein may exist in the singular in some embodiments and in the plural in other embodiments. As shown, FIG. 1 illustrates a flight management computer 110 that includes one or more processors ("(one or more) processors" 112 in FIG. 1). This indicates that in some embodiments, the flight management computer 110 includes a single processor 112 and in other embodiments, the flight management computer 110 includes multiple processors 112. For ease of reference herein, such features are generally introduced as "one or more" features, followed by a single or optionally multiple features (typically as indicated by "s"), unless it is clearly indicated that multiple aspects relate to multiple features.

[0019]

[0027] Furthermore, the term "comprise, comprise, and comprising" is used interchangeably with "include, includes, including." Furthermore, the term "wherein" is used interchangeably with the term "where." As used herein, "exemplary" refers to an example, an implementation, and / or an aspect, and should not be construed as limiting, or as indicating a preference or preferred embodiment. As used herein, ordinal terms (e.g., "first," "second," "third," and the like) used to modify elements, such as structures, components, operations, etc., do not in themselves indicate a priority or order of the element relative to another element, but rather merely distinguish the element from another element having the same name (except for the use of ordinal terms). As used herein, the term "set" refers to a grouping of one or more elements, and the term "plurality" refers to a plurality of elements.

[0020]

[0028] As used herein, "generating," "calculating," "using," "selecting," "accessing," and "determining" are interchangeable unless the context indicates otherwise. For example, "generating," "calculating," or "determining" a parameter (or signal) may refer to actively generating, calculating, or determining a parameter (or signal), or may refer to using, selecting, or accessing a parameter (or signal) that has already been generated, for example, by another component or device. "Coupled," as used herein, may include "communicatively coupled," "electrically coupled," or "physically coupled," and may further (or alternatively) include any combination thereof. Two devices (or components) may be directly or indirectly coupled (communicatively coupled, electrically coupled, or physically coupled) via one or more other devices, components, wires, buses, networks (wired networks, wireless networks, or combinations thereof), etc. Two devices (or components) that are electrically coupled can be included in the same device or different devices and can be connected via electronics, one or more connectors, or inductive coupling, as illustrative, non-limiting examples. In some implementations, two devices (or components) that are communicatively coupled, such as by electrical communication, can send and receive electrical signals (digital or analog signals) directly or indirectly via one or more wires, buses, networks, etc. As used herein, "directly coupled" is used to describe two devices that are coupled (e.g., communicatively connected, electrically coupled, or physically coupled) without any intervening components.

[0021]

[0029] FIG. 1 illustrates an example of an aircraft 100 in accordance with certain embodiments of the present disclosure. The aircraft 100 of FIG. 1 includes two or more engines 102, shown as a first engine 102A and a second engine 102B. Each of the engines 102 is associated with a respective electronic engine controller (EEC) 104, shown in FIG. 1 as a first EEC 104A and a second EEC 104B. Each EEC 104 includes (e.g., stores in a local memory) engine data 106 associated with the engine 102 associated with the EEC 104. For example, the first EEC 104A stores engine data 106A associated with the first engine 102A, and the second EEC 104B stores engine data 106B associated with the second engine 102B. Various types of engine data are referred to herein, including engine data, engine rating identifiers, thrust rating identifiers, and thrust rating model identifiers. As used herein, "engine data" is used as a blanket term that may include engine rating identifiers, thrust rating identifiers, thrust rating model identifiers, and possibly other engine data. As used herein, the terms "engine rating identifier" and "thrust rating identifier" are synonymous, and the term "thrust rating model identifier" refers to uniquely defined rating data for an engine that is independent of a bill of materials (BOM) for the engine.

[0022]

[0030] Aircraft 100 also includes a Flight Management Computer (FMC) 110. In one embodiment shown in FIG. 1, FMC 110 includes one or more processors 112, non-volatile memory (NVM) 114, and random access memory (RAM) 116. In this context, RAM 116 includes working memory of FMC 110, such as cache, registers, and similar volatile memory. NVM includes any type of memory that retains stored information when power is not applied, such as flash memory, electrically erasable programmable read only memory (EEPROM), magnetoresistive memory (MRAM), and other types of non-volatile memory. FMC 110 can communicate with each of EECs 104 via one or more buses or other data connections of aircraft 100.

[0023]

[0031] In one embodiment shown in FIG. 1, the NVM 114 includes (e.g., stores) engine data 120 and instructions 118 executable by the processor(s) 112. As described in more detail with reference to FIGS. 2-8, the engine data 120 stored by the NVM 114 generally corresponds to data used in the most recent flight of the aircraft 100, but under certain circumstances, the engine data 120 is updated to include engine data 106 from one of the EECs 104. For example, if a technician finds that the engine data 120 is inaccurate, the technician may update the engine data 120 in the NVM 114. As shown, the technician may update the engine data 120 after one of the engines 102 is changed. In one particular aspect, as described further below, the FMC 110 operates at each start as if the engine data 120 is suspect. Therefore, the FMC 110 performs various error checking operations to verify and validate or replace the engine data 120 at each start.

[0024]

[0032] In contrast, the engine data 106 stored by the EEC 104 is known to be accurate. The EEC 104 reads the configuration of the plug sets in the associated engines 102 and determines the engine data based thereon. For example, the configuration of the plug sets associated with the first engine 102A indicates the thrust rating identifier of the engine 102A. Similarly, the configuration of the plug sets associated with the second engine 102B indicates the thrust rating identifier of the engine 102B. If one of the engines 102 is replaced (e.g., as part of routine maintenance of the aircraft 100), the new engine will have plug sets that may be configured to indicate a different thrust rating identifier. The EEC 104 can detect and interpret the different thrust rating identifier to generate data indicative of the thrust rating of the engine. The EECs 104A and 104B continuously or periodically detect the configuration of the plugs of the engines 102A and 102B, respectively, and interpret the configuration to determine the correct engine data 106 for each engine 102.

[0025]

[0033] In one embodiment shown in FIG. 1 , the instructions 118 stored in the NVM 114 of the FMC 110 include an engine data selector 122 and a thrust model 124. The thrust model 124 is executable by the processor(s) 112 to perform various performance related calculations, such as lateral and vertical trajectory, expected fuel consumption at various waypoints, expected weight at various waypoints, etc. As used herein, a “thrust model” is an aspect of a performance model used by the FMC 110. For example, the thrust model 124 includes, is included within, or corresponds to a performance model. In some implementations, the thrust model 124 is configured to receive input data, such as fuel flow rate, total fuel, flap position, engine data and limits, altitude, airspeed, Mach number, air temperature, vertical speed, progress along the flight plan and pilot inputs, and engine data 120. In some implementations, thrust model 124 is configured to process input data and generate output data, such as Mach number targets, calibrated airspeed and thrust for optimal control of the aircraft, and flight crew advisory data, etc. In other implementations, thrust model 124 can receive more, less, or different input data and can generate more, less, or different output data.

[0026]

[0034] The engine data selector 122 includes instructions executable by the processor(s) 112 to select engine data from among the engine data 106A, 106B, and 120 to be used by the thrust model 124. In one particular aspect, the engine data selector 122 dynamically selects the engine data to be used by the thrust model 124 between power-up of the FMC 110 and the subsequent takeoff of the aircraft 100.

[0027]

[0035] For example, during operation (e.g., during or after power-up of the FMC 110), the engine data selector 122 monitors sensor data from one or more sensors 130 to determine whether an engine data processing condition is satisfied. Generally, engine data processing is performed in situations where it is safe for the FMC to modify available engine data, and the engine data processing condition is specified to limit processing to such situations. For example, the engine data processing condition may be satisfied when the aircraft 100 is on the ground. In this example, while the aircraft 100 is on the ground, the engine data selector 122 may repeatedly execute a series of operations until an exit condition is satisfied. In that case, the exit condition is satisfied when, for example, the engine data 120 for the thrust model 124 is selected. In other examples, the engine data processing condition may be satisfied based on a sensed speed of the aircraft 100, a throttle position of the aircraft 100, or based on another setting, other data, or pilot input. The repeated series of operations is summarized below and described in detail with reference to FIGS. 2-8.

[0028]

[0036] During the initialization process, engine data selector 122 accesses engine data 120 from NVM 114 of FMC 110. Engine data selector 122 performs one or more error checking operations based on engine data 120 (and potentially other data) to determine whether to select an engine thrust rating for thrust model 124 based in part on an engine rating identifier associated with engine data 120. When engine 102 starts, EEC 104 begins sending data to engine data selector 122, which includes data received from EEC 104 during the initialization process as that data is available. For example, during one or more initial iterations of operation of engine data selector 122, only data stored in NVM 114 may be available to engine data selector 122. Engine 102A may then be started. EEC 104A may begin sending data, such as an engine rating identifier for engine 102A, error check data (e.g., cyclic redundancy check (CRC) data) associated with engine data 106A, or a portion thereof. During this period, engine data selector 122 may perform one or more iterations based on the data from NVM 114 and the data transmitted by EEC 104A. Further, engine 102B may be started. EEC 104B may begin sending data, such as an engine rating identifier for engine 102B, error check data (e.g., cyclic redundancy check (CRC) data) associated with engine data 106B, or a portion thereof. During this period, engine data selector 122 may perform one or more iterations based on the data from NVM 114, the data transmitted by EEC 104A, and the data transmitted by EEC 104B. Although in one embodiment shown in FIG. 1, aircraft 100 includes only two engines 102, in other implementations, aircraft 100 includes three or more engines. In such embodiments, these additional engines are also associated with the EEC, which transmits data when their respective engines start.The engine data selector 122 utilizes the data from these EECs as it becomes available.

[0029]

[0037] The error checking operation(s) performed by engine data selector 122 may include, for example, calculating a CRC value for engine data 120 stored in NVM 114 and comparing the calculated CRC value to a CRC value previously determined and stored in NVM 114. By comparing the calculated CRC value with the stored CRC value, engine data selector 122 determines whether any changes have occurred to engine data 120 since engine data 120 was stored in NVM 114. For example, if NVM 114 has been damaged in a manner that has altered one or more bits of engine data 120, the calculated CRC value should not match the stored CRC value, indicating that engine data 120 is unreliable. In this situation, engine data selector 122 may cause engine data 120 to be erased, overwritten, or invalidated, and engine data 120 will not be used during the selection of an engine thrust rating to be used by thrust model 124.

[0030]

[0038] If the calculated CRC value matches the stored CRC value, further processing is performed to determine whether the engine data 120 in NVM 114 matches the engine data 106 of one of the EECs 104. For example, EEC 104A transmits a CRC value associated with engine data 106A, and engine data selector 122 compares the CRC value received from EEC 104A with the CRC value stored in NVM 114 for engine 102A. Similarly, when EEC 104B transmits a CRC value associated with engine data 106B, engine data selector 122 compares the CRC value received from EEC 104B with the CRC value stored in NVM 114 for engine 102B. If the CRC value received from a particular EEC 104 does not match the CRC value stored in NVM 114 for the corresponding engine 102, the engine data selector 122 causes at least a portion of the engine data 120 for that engine 102 to be erased, overwritten, or invalidated, and at least that portion of the engine data 120 is not used during the selection of an engine thrust rating to be used by the thrust model 124.

[0031]

[0039] If the CRC value received from a particular EEC 104 matches the CRC value stored in NVM 114 for the corresponding engine 102, the engine data selector 122 waits for sufficient data to be received to begin operation to select an engine thrust rating that matches two or more engines 102. For example, the engine data selector 122 waits until at least two EECs 104 report thrust rating identifiers for their respective engines 102 (e.g., until it receives a first thrust rating identifier associated with engine 102A from EEC 104A and a second thrust rating identifier associated with engine 102B from EEC 104B). The engine data selector 122 then proceeds to determine a rating identifier based on the received thrust rating identifiers (e.g., a single rating identifier based on the first thrust rating identifier from EEC 104A and the second thrust rating identifier from EEC 104B). If the engine data 120 in NVM 114 passes the error checking operation, the engine data selector 122 may also consider the first engine rating identifier from NVM 114 when selecting the single rating identifier.

[0032]

[0040] In one particular aspect, the determination of the single rating identifier by the engine data selector 122 determines a plurality of local thrust rating model (TRM) identifiers including at least one local TRM identifier for each respective one of the plurality of engines 102 of the aircraft 100 and selects intermix thrust model data to be used by the FMC 110 during flight of the aircraft 100 based on the plurality of local TRM identifiers. In this context, intermix thrust model data refers to the specific engine data used by the thrust model 124 that is compatible with all of the engines 102 of the aircraft 100. For example, the intermix thrust model data is associated with a thrust model identifier that is common to the engines 102 of the aircraft 100.

[0033]

[0041] In one particular aspect, determining the plurality of local TRM identifiers includes accessing an FMC engine rating for the particular engine 102 from NVM 114 and obtaining an EEC engine rating for the particular engine 102 from an EEC 104 associated with the particular engine. Engine data selector 122 may determine the local rating identifier for the particular engine based on a selected one of the FMC engine rating for the particular engine or the EEC engine rating for the particular engine. For example, engine data 120 in NVM 114 may include an FMC engine rating for each of engines 102A and 102B of aircraft 100. Further, engine data 106A for EEC 104A may include an EEC engine rating for engine 102A. Engine data 106B for EEC 104B may include an EEC engine rating for engine 102B. In this example, engine data selector 122 may obtain an EEC engine rating for engine 102A from EEC 104A and select from among the EEC engine rating for engine 102A and the FMC engine rating for engine 102A as the local rating identifier for engine 102A. Similarly, in this example, engine data selector 122 may obtain an EEC engine rating for engine 102B from EEC 104B and select from among the EEC engine rating for engine 102B and the FMC engine rating for engine 102B as the local rating identifier for engine 102B.

[0034]

[0042] In some embodiments, based on a determination that the EEC engine rating is valid, the EEC engine rating for the particular engine (rather than the FMC engine rating for the particular engine) is selected as the local rating identifier. In some such embodiments, based on a determination that the EEC engine rating is not valid and the FMC engine rating is valid, the FMC engine rating for the particular engine is selected as the local rating identifier. In some such embodiments, based on a determination that the EEC engine rating for the particular engine is valid and the FMC engine rating for the particular engine is not valid, engine data selector 122 sets a flag (e.g., one or more data bits, signals, etc.) indicating detection of changed engine data for the particular engine.

[0035]

[0043] After selecting the local rating identifier for each engine 102, the engine data selector 122 determines a local thrust rating model (TRM) identifier for each engine 102. In this context, the TRM identifier uniquely defines the rating data for an engine independent of a bill of materials (BOM) for the engine. In contrast, the rating identifier includes both the rating data and information about the engine's BOM. The local TRM identifier for each engine is determined, for example, based on mapping data that maps rating identifiers (e.g., the local rating identifier for each engine 102) to TRM identifiers.

[0036]

[0044] The engine data selector 122 selects the intermix thrust model data based on the local TRM identifier. For example, in some implementations, a single local TRM identifier (e.g., a representative local TRM identifier from among the local TRM identifiers for all of the engines 102 of the aircraft 100) is selected as a comparison target. In this embodiment, the other local TRM identifiers are compared to the comparison target to identify a common rating identifier as the single rating identifier. For example, when a first local TRM identifier for engine 102A is selected as the comparison target, a second local TRM identifier for engine 102B is compared to the comparison target. The single local TRM identifier (e.g., the representative local TRM identifier) ​​is designated as the common rating identifier based on a determination that each of the multiple local TRM identifiers matched the representative local TRM identifier.

[0037]

[0045] The engine data selector 122 provides the common rating identifier to a thrust model 124 for use in subsequent flights of the aircraft. For example, the thrust model 124 performs one or more on-board calculations based on the engine thrust ratings indicated by the common rating identifier.

[0038]

[0046] Figure 2 illustrates a flow chart of one embodiment of a method 200 for dynamically determining thrust model data for an aircraft in accordance with certain aspects of the present disclosure. Figures 3-8 illustrate various aspects of the method 200 of Figure 2. Method 200, including each of the aspects described in Figures 3-8, may be performed by one or more processors executing instructions, such as by processor(s) 112 of FMC 110 executing instructions 118 of Figure 1.

[0039]

[0047] Method 200 begins at block 202 with initialization of FMC 110. For example, method 200 may begin with a power-up or reboot of FMC 110 in preparation for flight.

[0040]

[0048] At block 204, the method 200 includes accessing a rating identifier (if any such rating identifier is available) from NVM 114 of FMC 110. For example, the rating identifier may be stored as a component (e.g., a data field) of engine data 120 in NVM 114. Any rating identifier stored in NVM 114 is generally one that has been retained by NVM 114 since a previous flight of aircraft 100.

[0041]

[0049] At block 206, the method 200 begins periodic input / output (I / O) processing. Input processing of the periodic I / O processing may include, for example, receiving data from the EEC 104. Output processing of the periodic I / O processing may include, for example, providing an engine thrust rating to the thrust model 124 for use in performing on-board calculations. In some circumstances, the output processing may also or alternatively include providing an alert to the crew of the aircraft 100 indicating an error or fault condition, such as data from one or more of the EECs 104 being unavailable, an engine 102 being incompatible (based on available thrust rating identifiers), no particular data satisfying an error check, etc.

[0042]

[0050] At block 208, method 200 includes determining whether engine data processing can continue, e.g., whether the aircraft 100 is on the ground or another engine data processing condition is met. Periodic I / O processing continues repeatedly until the determination at block 208 indicates that an engine data processing condition is no longer met (e.g., the aircraft 100 is no longer on the ground) or until the periodic I / O processing is stopped due to a fault condition. Thus, if the determination at block 208 is that engine data processing cannot continue, then periodic I / O processing ends at block 210.

[0043]

[0051] If the determination at block 208 is that engine data processing can continue, the method 200 begins an initialization process at block 212. The initialization process includes performing an error check on the engine data 120 from the NVM 114. If any data was received from the EEC 104, the initialization process also includes performing an error check on the data from the EEC 104. Figure 3 illustrates one particular example of operations that may be performed as part of the initialization process.

[0044]

[0052] 3, a method 300 of performing the initialization process of FIG. 2 according to one particular embodiment includes determining, at block 304, whether engine data 120 and associated CRC data are available in NVM 114 of FMC 110. The CRC data used in the determination associated with block 304 is a CRC value previously calculated based on engine data 120 and stored in NVM 114. If engine data 120 and associated CRC data are not available, the method 300 continues to block 306, where the engine data and CRC data in NVM 114 (hereinafter referred to as “NVM CRC data” and “NVM engine data” to distinguish them from similar values ​​received from EEC 104 in later operations) are cleared. Clearing the NVM CRC data and NVM engine data may include, for example, overwriting portions of NVM 114 allocated to storing these data, marking portions of NVM 114 allocated to storing these data as invalid or available, or other memory management operations that render any NVM CRC data and NVM engine data (e.g., partial data or potentially corrupted data) unavailable for subsequent processing steps.

[0045]

[0053] If the NVM engine data and the NVM CRC data are not available, the method 300 continues at block 308 where a determination is made whether any of the EECs 104 have sent a CRC check value. If the EECs 104 have provided a CRC check value for the particular engine 102, the method 300 includes determining whether the CRC check value for the particular engine 102 is equal to the NVM CRC value of the NVM CRC data for the particular engine 102, at block 312. If the CRC check value for the particular engine 102 is not equal to the NVM CRC value for the particular engine 102, the method 300 continues at block 306 where the particular data (e.g., the NVM engine data and the NVM CRC data) of the NVM 114 is cleared.

[0046]

[0054] Returning to block 308, if the EEC 104 for the particular engine 102 has not provided a CRC check value for the engine 102, the method 300 includes setting the CRC check value for the particular engine 102 equal to the NVM CRC value of the NVM data for the particular engine 102. The method 300 then continues to block 312, where it is determined whether the CRC check for the particular engine 102 equals the NVM CRC value for the particular engine 102. The operations performed in block 310 ensure that the CRC check value for the particular engine 102 equals the NVM CRC value for the particular engine 102. Thereby, the method 300 does not default to clearing the NVM CRC data and engine data in block 306 in the absence of a CRC check value received from the particular EEC. Rather, in this situation, the initialization process ends in block 214 and may be repeated in subsequent iterations.

[0047]

[0055] 2, after the initialization process is completed at block 214, the method 200 includes determining, at block 216, whether the rating (or ratings) stored in the NVM 114 as part of the engine data 120 is from one of the EECs 104. If the determination at block 216 is that the rating(s) stored in the NVM 114 have not been received from the EEC 104, the method 200 includes reporting a fault condition and waiting for data from the EEC 104, at block 218. Although in typical operation, the engine data 120 stored in the NVM 114 includes data received from the EEC 104, in some situations the engine data 120 may be updated in other manners, such as manually as part of an engine maintenance operation.

[0048]

[0056] The method 200 continues at block 220, where it is determined whether at least one thrust rating identifier (thrust rating ID) has been received from the EEC 104. The remaining operations of the method 200 are dependent on receipt of a thrust rating ID from the EEC 104. Thus, if no thrust rating ID has been received from the EEC 104, the method 200 returns to block 208.

[0049]

[0057] If at least one thrust rating ID has been received from the EEC 104, the method 200 includes determining whether a count of thrust rating IDs received from the EEC 104 is greater than or equal to two, at block 222. If more than one thrust rating ID has been received from the EEC 104, the method 200 determines whether the received thrust rating IDs are compatible with one another (e.g., based on a compatibility matrix stored in the FMC 110), at block 224. If it is determined at block 224 that two or more of the thrust rating IDs are not compatible with one another, the method 200 includes reporting a fault condition, at block 226, and terminating periodic I / O processing, at block 228.

[0050]

[0058] If, at block 224, it is determined that the received thrust rating IDs are compatible with each other, or if, at block 222, it is determined that only one thrust rating ID has been received, then method 200 begins a process of narrowing the selection range at block 230. The process of narrowing the selection range includes operations to select intermix thrust model data (e.g., a set of thrust model data that is compatible with all of the engines 102 of the aircraft 100). Because each engine 102 may be operated at various levels, the intermix thrust model data may be considered as the greatest common factor (e.g., the highest performance that all of the engines have in common) among the levels at which the engines may be operated. Figures 4-6 illustrate one embodiment of operations that may be performed as part of the process of narrowing the selection range.

[0051]

[0059] FIG. 4 illustrates a method 400 for determining a local thrust rating model (TRM) identifier for a set of engines. In FIG. 4, the method 400 is based on an FMC E(n) rating ID 402 and an EEC E(n) rating ID 404. The FMC E(n) rating ID 402 includes an engine rating identifier from the NVM 114 of the FMC 110. The EEC E(n) rating ID 404 includes an engine rating identifier received from the EEC 104. Each engine rating identifier in the FMC E(n) rating ID 402 is for a corresponding one of the engines 102 of the aircraft 100, as indicated by an index n. Similarly, each engine rating identifier in the EEC E(n) rating ID 404 is for a corresponding one of the engines 102 of the aircraft 100, as indicated by an index n. Each index n is an integer value assigned to uniquely identify an engine 102 among the set of engines 102 of the aircraft. For example, engine 102A may be assigned an index value n=1 and engine 102B may be assigned an index value n=2. In this example, FMC E(1) rating ID 402 refers to the engine rating identifier stored in NVM 114 for engine 102A, and EEC E(1) rating ID 404 refers to the engine rating identifier for the same engine (i.e., engine 102A) received from EEC 104A. Similarly, FMC E(2) rating ID 402 refers to the engine rating identifier stored in NVM 114 for engine 102B, and EEC E(2) rating ID 404 refers to the engine rating identifier for the same engine (i.e., engine 102B) received from EEC 104B. In aircraft 100 that includes more than two engines 102, index values ​​n greater than or equal to three are assigned to the other engines 102.

[0052]

[0060] The method 400 includes a set of operations 406 for selecting a local engine rating identifier (local E(n) rating ID) 430 for each engine 102. In one embodiment shown in FIG. 4, the operation 406 for selecting a local E(n) rating ID 430 includes determining, for each engine, whether an EEC E(n) rating ID 404 and an FMC E(n) rating ID 402 are valid. Although in the embodiment shown in FIG. 4, these determinations are shown as being performed sequentially in a particular order, these determinations may be performed in parallel or in an order different than that shown in FIG. 4. In one particular embodiment shown in FIG. 4, the method 400 includes determining, in block 408, whether each EEC E(n) rating ID 404 is valid, and then determining, in block 410 or block 420, whether the corresponding FMC E(n) rating ID 402 is valid. In one particular aspect, the FMC 110 may store a list of valid engine rating identifiers that are used to determine the validity of the EEC E(n) rating ID 404 and the FMC E(n) rating ID 402.

[0053]

[0061] 4, for a particular engine E(n), if the EEC E(n) rating ID 404 is valid and the corresponding FMC E(n) rating ID 402 is also valid, the method 400 includes determining, at block 412, whether the FMC E(n) rating ID 402 is equal to the EEC E(n) rating ID 404. If the FMC E(n) rating ID 402 is equal to the EEC E(n) rating ID 404, then a local E(n) rating ID 430 for the engine is set equal to the EEC E(n) rating ID 404 for the engine, at block 414. If the FMC E(n) rating ID 402 is not equal to the EEC E(n) rating ID 404, then in block 416 a flag is set indicating that the FMC E(n) rating ID 402 for the engine has changed, and in block 418 the local E(n) rating ID for the engine 430 is set equal to the EEC E(n) rating ID 404 for the engine.

[0054]

[0062] In FIG. 4 , if the EEC E(n) rating ID 404 is valid and the corresponding FMC E(n) rating ID 402 is not valid for a particular engine E(n), the method 400 includes setting a flag indicating that the FMC E(n) rating ID 402 for the engine has changed, at block 416, and setting the local E(n) rating ID 430 for the engine equal to the EEC E(n) rating ID 404 for the engine, at block 418.

[0055]

[0063] If the EEC E(n) rating ID 404 for the particular engine E(n) is not valid and the corresponding FMC E(n) rating ID 402 is valid, the method 400 includes setting the local E(n) rating ID 430 for the engine equal to the FMC E(n) rating ID 402 for the engine, at block 422. If the EEC E(n) rating ID 404 for the particular engine E(n) is not valid and the corresponding FMC E(n) rating ID 402 is not valid, the method 400 includes setting the local E(n) rating ID 430 for the engine to invalid, at block 424.

[0056]

[0064] After the local E(n) rating ID 430 for the engine is determined, the method 400 includes, at block 432, mapping the local E(n) rating ID 430 to a corresponding local E(n) TRM ID 434. The mapping may be performed via a lookup operation using mapping data that maps engine rating identifiers to thrust model identifiers.

[0057]

[0065] 5 illustrates a method 500 illustrating one particular embodiment of operations 502 for determining a single local TRM ID 520 to be used in the method 600 as a comparison target. Operation 502 illustrates just one embodiment of operations that may be used to select a local TRM ID 520 from among the local E(n) TRM IDs 434.

[0058]

[0066] 5, operation 502 determines whether an engine rating change flag is set to TRUE in block 504. For example, the engine rating change flag may be initialized to a FALSE value and changed to TRUE in block 416 of FIG. 4 in response to a determination that the EEC E(n) rating ID 404 for the engine is valid and the FMC E(n) rating ID 402 is not valid, or in response to a determination that the EEC E(n) rating ID 404 for the engine is valid and the FMC E(n) rating ID 402 is valid and the FMC E(n) rating ID 402 for the engine is not equal to the EEC E(n) rating ID 404 for the engine.

[0059]

[0067] 5, if the engine rating change flag is set to true, the method 500 includes selecting the local E(n) TRM ID 434 for the default engine (engine E(1) in FIG. 5) as the local TRM ID 520 to be used as the comparison target, at block 506. If the engine rating change flag is not set to true (e.g., is false), the operation 502 includes retrieving the FMC E(n) rating ID 508 for the engine to determine whether the FMC E(n) rating ID 508 is valid, at block 510. If the FMC E(n) rating ID 508 is not valid, the default engine is selected as the local TRM ID 520 to be used as the comparison target, at block 506. If the FMC E(n) rating ID 508 is valid, the method 500 includes, at block 512, mapping the FMC E(n) rating ID 508 to a local E(n) TRM ID (e.g., using the mapping data used in block 432) and using the local E(n) TRM ID as the local TRM ID 520 used as a comparison target.

[0060]

[0068] 6 illustrates one particular embodiment of a method 600 for determining a thrust model rating identifier (e.g., a common TRM rating ID) that is common to all of the engines. Method 600 illustrates just one embodiment of operations that may be used to select a common TRM ID from among the local E(n) TRM IDs.

[0061]

[0069] 6, a placeholder variable (p) is initialized to zero at block 650, and a particular value of index n is set (during the first iteration) or incremented (in subsequent iterations) at block 602. Method 600 also includes determining whether the local E(n) TRM ID for the engine that corresponds to the current value of index n is valid at block 604. If the local E(n) TRM ID is not valid, method 600 returns to block 602 and increments the index n value.

[0062]

[0070] If the local E(n) TRM ID is valid, the method 600 includes determining whether the local E(n) TRM ID is equal to the local TRM ID 520 (e.g., a previously selected comparison target) at block 606. If the local E(n) TRM ID is equal to the local TRM ID 520, the method 600 includes setting the value of a placeholder variable p to the value of index n at block 608 and determining whether all of the engines (e.g., each value of index n) have been checked at block 610.

[0063]

[0071] If all of the engines have not been checked, the method 600 returns to block 602 and increments index n. If all of the engines have been checked, the method 600 includes determining whether the value of the placeholder variable p is zero at block 612. If the value of the placeholder variable p is equal to zero at block 612, this indicates that no engines exist that meet the condition to reset the value of the placeholder variable p from zero to the engine's index n (e.g., at block 608). Thus, if the value of the placeholder variable p is equal to zero at block 612, the method 600 may provide a failure indication at block 624, in which case the method 600 may terminate periodic I / O processing (e.g., at block 228).

[0064]

[0072] If the value of the placeholder variable p is not equal to zero at block 612, then the method 600 sets the common TRM rating ID equal to the E(p) TRM rating ID at block 614 (where the value of the placeholder variable p is used as an index to specify the engine).

[0065]

[0073] Returning to block 606, if the local E(n) TRM ID is not equal to the local TRM ID 520, the method 600 includes, at block 620, identifying a set of authorized proxy (AP) E(n) TRM IDs associated with the local E(n) TRM ID for the particular engine in question. In this context, the AP E(n) TRM ID comprises a superset of the TRM IDs associated with the engine. The local E(n) TRM ID is a subset of that superset. Other TRM IDs of the AP E(n) TRM ID are associated with stepped down or stepped up performance conditions (relative to the baseline values ​​associated with the local E(n) TRM ID). The engine can operate in stepped down and stepped up performance conditions, which are not the default (e.g., optimal) performance conditions associated with the engine.

[0066]

[0074] The method 600 includes, at block 622, determining whether any of the AP E(n) TRM IDs match the local TRM ID 520. If one of the AP E(n) TRM IDs matches the local TRM ID 520, the method 600 proceeds to block 610. If none of the AP E(n) TRM IDs match the local TRM ID 520, the method 600 includes, at block 638, determining whether all of the engines are associated with a local TRM ID equal to the AP E(n) TRM ID. If all of the engines are associated with a local TRM ID equal to the AP E(n) TRM ID, the method 600 proceeds to block 640. equal to the local E(n) TRM ID, and returning to block 608. If not all of the engines are associated with a local TRM ID equal to the AP E(n) TRM ID, the method 600 results in a failure indication at block 642 (e.g., because at least one engine does not have a compatible TRM ID).

[0067]

[0075] 2, after the selection narrowing process is completed, at block 232, the method 200 includes initiating a rating process, at block 234. The rating process includes operations to update the engine data 120 stored in the NVM 114, as necessary, as well as error checking operations. For example, if the NVM CRC data and engine data 120 for a particular engine are cleared, then new CRC data and engine data received from the EEC 104 for the engine 102 are stored in the NVM 114 as part of the rating process, at block 306 of FIG.

[0068]

[0076] 7 illustrates one particular embodiment of a method 700 for performing a rating process. Method 700 illustrates just one embodiment of operations that may be used to process ratings. The rating process performed by method 700 may be performed at different times within method 200. For example, the rating process may be performed before a selection narrowing process.

[0069]

[0077] Method 700 includes a set of operations that are performed for each EEC E(n) rating ID received when processing occurs. The operations of method 700 include, at block 704, determining whether the FMC E(n) rating ID is available in NVM 114. For example, if the FMC E(n) rating ID was cleared from NVM 114 at block 306, the FMC E(n) rating ID will not be available when the determination is performed at block 704. If the FMC E(n) rating ID is not available in NVM 114, method 700 includes, at block 706, storing the E(n) rating ID from the EEC (i.e., the EEC E(n) rating ID) in NVM 114 of FMC 110. Thus, the EEC E(n) rating ID becomes the FMC E(n) rating ID in this situation.

[0070]

[0078] If the FMC E(n) rating ID is available in NVM 114 at block 704, the method 700 includes determining whether the EEC E(n) rating ID is equal to the FMC E(n) rating ID at block 708. If the EEC E(n) rating ID is not equal to the FMC E(n) rating ID, the method 700 proceeds to block 706 and stores the EEC E(n) rating ID as the FMC E(n) rating ID. If the EEC E(n) rating ID is equal to the FMC E(n) rating ID, the method 700 includes determining whether EEC E(n) CRC data is available at block 710.

[0071]

[0079] If the EEC E(n) CRC data is not available at block 710 or if the EEC E(n) CRC data was stored as an FMC E(n) rating ID at block 706, method 700 includes requesting E(n) CRC data from the EEC for the particular engine at block 712 and requesting E(n) engine data from the EEC for the particular engine at block 714. Method 700 also includes calculating an E(n) CRC value based on the E(n) engine data received from the EEC at block 716, and determining whether the received E(n) CRC data matches the E(n) CRC value calculated based on the E(n) engine data received from the EEC at block 718. If the received E(n) CRC data does not match the E(n) CRC value calculated based on the E(n) engine data received from the EEC, the method 700 includes reporting a fault condition, at block 720, and terminating periodic I / O processing, at block 228.

[0072]

[0080] If the received E(n) CRC data matches the E(n) CRC value calculated based on the E(n) engine data received from the EEC, or if EEC E(n) CRC data is available at block 710, the method 700 includes determining whether all received rating IDs have been processed at block 722. If all of the received rating IDs have not been processed, the method 700 returns to block 704 to process other received rating IDs. If all of the received rating IDs have been processed, the method 700 ends rating processing at block 236.

[0073]

[0081] Referring back to Figure 2, after the rating process is completed at block 236, the method 200 includes initiating a selection process at block 238. The selection process includes operations for selecting rating information for subsequent use. Figure 8 illustrates one particular embodiment of a method 800 for performing the selection process. Method 800 illustrates just one embodiment of operations that may be used for the selection process.

[0074]

[0082] Method 800 includes determining, at block 802, whether engine data from all of the EECs of aircraft 100 has been received and checked. If engine data from all of the EECs of aircraft 100 has been received and checked, method 800 ends the selection process, at block 240.

[0075]

[0083] If engine data from all of the EECs of the aircraft 100 has not been received and checked, the method 800 repeats comparing engine ratings associated with the engines 102 of the aircraft 100. Repeating the engine ratings includes setting an index n equal to 1, at block 804. The method 800 also includes determining whether the E(n) rating ID is equal to a common rating ID identified via the narrowing selection process, at block 806. If the E(n) rating ID is not equal to the common rating ID, the method 800 includes incrementing the index n, at block 808. The method 800 further includes determining whether the data for all of the engines has been checked (e.g., whether the value of the index n exceeds the count N of the engines of the aircraft 100), at block 810. If the data for all of the engines has been checked, the method 800 includes reporting a fault condition due to an invalid intermix downmix selection, at block 812. If the data for all of the engines has not been checked, the method 800 returns to block 806 .

[0076]

[0084] If, at block 806, the E(n) rating ID is equal to a common rating ID identified via the narrowing selection process, the method 800 includes, at block 816, determining whether E(n) CRC data for engine n is stored in NVM 114 of FMC 110. If the E(n) CRC data is stored in NVM 114, the method 800 includes, at block 820, determining whether the FMC E(n) CRC data matches the EEC E(n) CRC data.

[0077]

[0085] If the FMC E(n) CRC data matches the EEC E(n) CRC data or if E(n) CRC data for the engine is not stored in NVM 114, method 800 includes storing the E(n) CRC data and the engine data in NVM 114 of FMC 110, at block 818. Method 800 ends the selection process, at block 240, based on a determination that the FMC E(n) CRC data matches the EEC E(n) CRC data or after the E(n) CRC data and the engine data are stored in NVM 114. Referring back to FIG. 2, after the selection process is ended, at block 240, method 200 returns to block 208.

[0078]

[0086] Figure 9 is a flow chart illustrating a method 900 illustrating the life cycle of an aircraft that includes FMC 110 of Figure 1. During pre-production, the example method 900 includes, at 902, specification and design of an aircraft, such as aircraft 100 described with reference to Figure 1. During specification and design of the aircraft, method 900 may include specification and design of FMC 110. At 904, method 900 includes sourcing materials. The sourcing of materials may include sourcing materials for FMC 110.

[0079]

[0087] During production, the method 900 includes, at 906, manufacturing of components and subassemblies, and, at 908, system integration of the aircraft. For example, the method 900 may include manufacturing of components and subassemblies of the FMC 110, as well as system integration of the FMC 110. At 910, the method 900 includes certification and delivery of the aircraft, and, at 912, placing the aircraft in service. Certification and delivery may include certification of the FMC 110 for service. While in service by a customer, the aircraft may be scheduled for routine maintenance and service, which may also include modifications, reconfigurations, refurbishments, etc. At 914, the method 900 includes performing maintenance and service on the aircraft. The maintenance and service may include performing maintenance and service on the FMC 110.

[0080]

[0088] Each of the processes of method 900 may be performed or implemented by a system integrator, a third party, and / or an operator (e.g., a customer). For purposes of this description, a system integrator may include, but is not limited to, any number of aircraft manufacturers and subcontractors of major systems, a third party may include, but is not limited to, any number of vendors, subcontractors, and suppliers, and an operator may be an airline, a leasing company, a military entity, a service organization, etc.

[0081]

[0089] Aspects of the present disclosure may be described in the context of an embodiment of a vehicle. One particular embodiment of the aircraft 100 of FIG. 1 is shown in FIG.

[0082]

[0090] In one embodiment of Figure 10, aircraft 100 includes an airframe 1018 and an interior 1022 having systems 1020. Examples of systems 1020 include one or more of a propulsion system 1024, an electrical system 1026, an environmental system 1028, and a hydraulic system 1030. Any number of other systems may be included. In the embodiment shown in Figure 10, propulsion system 1024 includes engine 102 and EEC 104. Systems 1020 of one embodiment of Figure 10 also include FMC 110 of Figure 1.

[0083]

[0091] 11 is a block diagram of a computing environment 1100 including a computing device 1110 configured to support aspects of the computer-implemented methods and computer-executable program instructions (or code) according to the present disclosure. For example, the computing device 1110, or portions thereof, is configured to execute instructions to initiate, perform, or control one or more of the operations described with reference to FIGS. 1-10.

[0084]

[0092] The computing device 1110 includes one or more processors 1120. The processor(s) 1120 are configured to communicate with a system memory 1130, one or more storage devices 1140, one or more input / output interfaces 1150, one or more communication interfaces 1160, or any combination thereof. The system memory 1130 includes volatile memory devices (e.g., random access memory (RAM) devices), non-volatile memory devices (e.g., read-only memory (ROM) devices, programmable read-only memory, and flash memory), or both. The system memory 1130 stores an operating system 1132, which may include a basic input / output system for booting the computing device 1110 and a complete operating system that allows the computing device 1110 to interact with a user, other programs, or other devices. The system memory 1130 stores system (program) data 1136, such as engine data 120.

[0085]

[0093] The system memory 1130 includes one or more applications 1134 (e.g., collections of instructions) executable by the processor(s) 1120. As one example, the one or more applications 1134 include instructions executable by the processor(s) 1120 to initiate, control, or perform one or more of the operations described with reference to Figures 1-10. As shown, the one or more applications 1134 include a plurality of instructions executable by the processor(s) 1120 to initiate, control, or perform one or more of the operations described with reference to the feature extraction model 122, the trained autonomous agent 124, or a combination thereof.

[0086]

[0094] The one or more storage devices 1140 include non-volatile storage devices, such as magnetic disks, optical disks, or flash memory devices. In a particular embodiment, the storage devices 1140 include both removable and non-removable memory devices. The storage devices 1140 are configured to store an operating system, images of the operating system, applications (e.g., one or more applications 1134), and program data (e.g., program data 1136). In a particular aspect, the system memory 1130, the storage devices 1140, or both, include tangible computer-readable media. In a particular aspect, one or more of the storage devices 1140 are external to the computing device 1110.

[0087]

[0095] The one or more input / output interfaces 1150 enable the computing device 1110 to communicate with one or more input / output devices 1170 to facilitate interaction with a user. For example, the one or more input / output interfaces 1150 may include a display interface, an input interface, or both. For example, the input / output interface 1150 may be adapted to receive input from a user, from another computing device, or a combination thereof. In some embodiments, input / output interface 1150 conforms to one or more standard interface protocols, including a serial interface (e.g., a universal serial bus (USB) interface or (IEEE (Institute of Electrical and Electronics Engineers) interface standard), a parallel interface, a display adapter, an audio adapter, or a custom interface. ("IEEE" is a registered trademark of the Institute of Electrical and Electronics Engineers, Inc. of Piscataway, NJ). In some implementations, input / output device(s) 1170 include one or more user interface devices and a display, including any combination of buttons, keyboards, pointing devices, displays, speakers, microphones, touch screens, and other devices.

[0088]

[0096] The processor(s) 1120 are configured to communicate with a device or controller 1180 via one or more communication interfaces 1160. For example, the one or more communication interfaces 1160 may include a network interface. The device or controller 1180 may include, for example, the EEC 104, one or more other devices, or any combination thereof.

[0089]

[0097] In some implementations, a non-transitory computer-readable medium stores instructions that, when executed by one or more processors, cause the one or more processors to initiate, perform, or control operations to perform some or all of the functions described above. For example, the instructions may be executable to perform one or more of the operations or methods of FIGS. 1-11. In some implementations, some or all of one or more of the operations or methods of FIGS. 1-11 may be performed by one or more processors (e.g., one or more central processing units (CPUs), one or more graphics processing units (GPUs), one or more digital signal processors (DSPs)) executing instructions through dedicated hardware circuitry, or any combination thereof.

[0090]

[0098] Certain aspects of the present disclosure are described below as a set of interrelated examples.

[0091]

[0099] According to Example 1, a method includes accessing, by one or more processors of a Flight Management Computer (FMC) of an aircraft, first engine data from a non-volatile memory of the FMC, and performing, by the one or more processors, one or more error checking operations based on at least the first engine data to determine whether to select an engine thrust rating for a thrust model of the aircraft based in part on a first engine rating identifier associated with the first engine data.

[0092]

[0100] Example 2 includes the method of example 1, where the one or more error checking operations include calculating a cyclic redundancy check (CRC) value based on the first engine data and comparing the calculated CRC value with a CRC value from the non-volatile memory of the FMC.

[0093]

[0101] Example 3 includes the method of example 1 or 2, in which the one or more error checking operations include comparing a CRC value received from an electronic engine controller (EEC) with a corresponding CRC value from the non-volatile memory of the FMC.

[0094]

[0102] Example 4 includes the method of example 3, further including clearing the first engine data from the non-volatile memory of the FMC based on a result of the one or more error checking operations.

[0095]

[0103] Example 5 includes the method of any one of examples 1 to 4, further including receiving, at the one or more processors of the FMC, a first thrust rating identifier associated with a first engine of the aircraft from a first EEC of the aircraft; receiving, at the one or more processors of the FMC, a second thrust rating identifier associated with a second engine of the aircraft from a second EEC of the aircraft; and determining a single rating identifier based on the first thrust rating identifier, the second thrust rating identifier, and the first engine rating identifier.

[0096]

[0104] Example 6 includes the method of example 5, in which determining the single rating identifier includes: for the first engine, determining a first local engine rating identifier based on the first thrust rating identifier and the first engine rating identifier, mapping the first local engine rating identifier to a first local thrust rating model (TRM) identifier; for the second engine, determining a second local engine rating identifier based on the second thrust rating identifier and a second engine rating identifier from the non-volatile memory of the FMC, mapping the second local engine rating identifier to a second local TRM identifier; designating a single local TRM identifier as a comparison target; and comparing the first local engine rating identifier, the second local engine rating identifier, or both, to the comparison target to identify a common rating identifier as the single rating identifier.

[0097]

[0105] Example 7 includes the method of any one of examples 1-6, further including receiving sensor data after power-up of the FMC, where the first engine data is accessed in response to the sensor data indicating that the aircraft is on the ground.

[0098]

[0106] Example 8 includes the method of example 7, further including, after selecting the engine thrust ratings for the thrust model of the aircraft, performing one or more on-board calculations based on the engine thrust ratings.

[0099]

[0107] Example 9 includes the method of any one of examples 1 to 8, further including accessing, from the non-volatile memory of the FMC, further engine data for each engine of one or more further engines of the aircraft; and performing, by the one or more processors, one or more further error checking operations based on the further engine data to determine whether to select the engine thrust rating for the thrust model of the aircraft based in part on one or more engine rating identifiers associated with the further engine data.

[0100]

[0108] According to Example 10, a device (such as a line replacement unit (LRU)) includes a memory configured to store a plurality of instructions, and a processor configured to execute the plurality of instructions to perform any one of the methods of Examples 1 to 9.

[0101]

[0109] According to Example 11, a non-transitory computer-readable medium stores a plurality of instructions that, when executed by a processor, cause the processor to perform the method of any one of Examples 1 to 9.

[0102]

[0110] According to Example 12, an apparatus comprises means for carrying out the method of any one of Examples 1 to 9.

[0103]

[0111] According to Example 13, an aircraft includes two or more engines, two or more EECs, each EEC associated with a corresponding one of the two or more engines, and an FMC communicatively coupled to the two or more EECs, where the FMC includes a non-volatile memory and one or more processors, the one or more processors configured to: access first engine data from the non-volatile memory; and perform one or more error checking operations based on at least the first engine data to determine whether to select an engine thrust rating for a thrust model of the aircraft based in part on a first engine rating identifier associated with the first engine data.

[0104]

[0112] Example 14 includes the aircraft of example 13, in which the one or more error checking operations include calculating a CRC value based on the first engine data and comparing the calculated CRC value to a CRC value from the non-volatile memory of the FMC.

[0105]

[0113] Example 15 includes the aircraft of example 13 or 14, in which the one or more error checking operations include comparing a CRC value received from an EEC with a corresponding CRC value from the non-volatile memory of the FMC.

[0106]

[0114] Example 16 includes the aircraft of example 15, in which the one or more processors are further configured to clear the first engine data from the non-volatile memory of the FMC based on a result of the one or more error checking operations.

[0107]

[0115] Example 17 includes the aircraft of any one of examples 13-16, in which the one or more processors are further configured to: receive, from a first EEC of the two or more EECs, a first thrust rating identifier associated with a first engine of the aircraft, receive, from a second EEC of the two or more EECs, a second thrust rating identifier associated with a second engine of the aircraft, and determine a single rating identifier based on the first thrust rating identifier, the second thrust rating identifier, and the first engine rating identifier.

[0108]

[0116] Example 18 includes the aircraft of example 17, in which case, to determine the single rating identifier, the one or more processors are configured to: determine, for the first engine, a first local engine rating identifier based on the first thrust rating identifier and the first engine rating identifier, map the first local engine rating identifier to a first local TRM identifier; determine, for the second engine, a second local engine rating identifier based on the second thrust rating identifier and a second engine rating identifier from the non-volatile memory of the FMC, map the second local engine rating identifier to a second local TRM identifier, designate a single local TRM identifier as a comparison target; and compare the first local engine rating identifier, the second local engine rating identifier, or both to the comparison target to identify a common rating identifier as the single rating identifier.

[0109]

[0117] Example 19 includes the aircraft of any one of examples 13-18, further including one or more sensors configured to generate sensor data indicative of whether the aircraft is on the ground, where the one or more processors are configured to access engine data from the non-volatile memory and select the engine thrust rating for the thrust model based on the sensor data indicating the aircraft is on the ground.

[0110]

[0118] Example 20 includes the aircraft of example 19, in which the one or more processors are further configured to, after selecting the engine thrust rating for the thrust model of the aircraft, perform one or more on-board calculations based on the engine thrust rating.

[0111]

[0119] Example 21 includes the aircraft of any one of examples 13-20, in which the one or more processors are further configured to: access additional engine data for each additional engine of the two or more engines from the non-volatile memory; and perform one or more additional error checking operations based on the additional engine data to determine whether to select the engine thrust rating for the thrust model of the aircraft based in part on one or more engine rating identifiers associated with the additional engine data.

[0112]

[0120] According to Example 22, a non-transitory computer-readable medium stores a plurality of instructions executable by one or more processors that, when executed, cause the one or more processors to access engine data associated with an engine of an aircraft from a non-volatile memory of an FMC, perform one or more error checking operations based on at least the engine data accessed from the non-volatile memory, and select an engine thrust rating for a thrust model of the aircraft, where the engine thrust rating is selected from among the engine data accessed from the non-volatile memory or from engine data received from an EEC of the aircraft based at least in part on results of the one or more error checking operations.

[0113]

[0121] Example 23 includes the non-transitory computer-readable medium of example 22, wherein the instructions are executable by one or more processors. When executed, the instructions cause the one or more processors to: determine, for a first engine of the aircraft, a first local engine rating identifier based on the engine data from the FMC and a first thrust rating identifier received from a first EEC associated with the first engine, map the first local engine rating identifier to a first local TRM identifier; determine, for a second engine of the aircraft, a second local engine rating identifier based on the engine data from the FMC and a second thrust rating identifier received from a second EEC associated with the second engine, map the second local engine rating identifier to a second local TRM identifier; designate a single local TRM identifier as a comparison target; compare the first local engine rating identifier, the second local engine rating identifier, or both to the comparison target; and determine a single rating identifier based on the comparison.

[0114]

[0122] According to Example 24, a method includes determining, by one or more processors of an FMC of an aircraft between power-up of the aircraft and subsequent takeoff of the aircraft, a plurality of local TRM identifiers including at least one local TRM identifier for each respective one of a plurality of engines of the aircraft, and selecting, by the one or more processors of the FMC, intermix thrust model data for use by the FMC during flight of the aircraft based on the plurality of local TRM identifiers, where the intermix thrust model data is associated with a thrust model identifier common to the plurality of engines.

[0115]

[0123] Example 25 includes the method of example 24, in which determining the plurality of local TRMs includes accessing an FMC engine rating for a particular engine of the plurality of engines from a non-volatile memory of the FMC, obtaining an EEC engine rating for the particular engine from an EEC associated with the particular engine, and determining a local rating identifier for the particular engine based on a selected one of the FMC engine rating for the particular engine or the EEC engine rating for the particular engine.

[0116]

[0124] Example 26 includes the method of example 25, in which determining the plurality of local TRMs includes determining a local TRM identifier for the particular engine based on the local rating identifier for the particular engine and mapping data that maps rating identifiers to TRM identifiers.

[0117]

[0125] Example 27 includes the method of example 25 or 26. Determining the plurality of local TRMs includes selecting the EEC engine rating for the particular engine as the local rating identifier based on a determination that the EEC engine rating is valid.

[0118]

[0126] Example 28 includes the method of any one of examples 25-27. In this case, determining the plurality of local TRM identifiers includes selecting the FMC engine rating for the particular engine as the local rating identifier based on a determination that the EEC engine rating is not valid and the FMC engine rating is valid.

[0119]

[0127] Example 29 includes the method of any one of examples 25 to 28, further including setting a flag indicating detection of an engine data change for the particular engine based on a determination that an EEC engine rating for the particular engine is valid and an FMC engine rating for the particular engine is not valid.

[0120]

[0128] Example 30 includes the method of any one of examples 24-29. In this case, selecting the intermix thrust model data includes determining a common rating identifier based on the plurality of local TRM identifiers.

[0121]

[0129] Example 31 includes the method of example 30. In that case, determining the common rating identifier includes selecting a representative local TRM identifier from among the plurality of local TRM identifiers, and comparing each of the plurality of local TRM identifiers to the representative local TRM identifier.

[0122]

[0130] Example 32 includes the method of example 31. In that case, the representative local TRM identifier is designated as the common rating identifier based on a determination that each of the plurality of local TRM identifiers matches the representative local TRM identifier.

[0123]

[0131] According to example 33, a device (e.g., an LRU) includes a memory configured to store a plurality of instructions, and a processor configured to execute the plurality of instructions to perform any one of the methods of examples 24 to 32.

[0124]

[0132] According to Example 34, a non-transitory computer-readable medium stores a plurality of instructions that, when executed by a processor, cause the processor to perform the method of any one of Examples 24 to 32.

[0125]

[0133] According to Example 35, an apparatus comprises means for carrying out the method of any one of Examples 24 to 32.

[0126]

[0134] According to Example 36, an aircraft includes two or more engines, two or more EECs, each EEC associated with a corresponding one of the two or more engines, and an FMC communicatively coupled to the two or more EECs, wherein the FMC includes one or more processors configured to: determine, between power-up of the FMC and subsequent takeoff of the aircraft, a plurality of local TRM identifiers including at least one local TRM identifier for each respective one of the two or more engines; and select intermix thrust model data to be used by the FMC during flight of the aircraft based on the plurality of local TRM identifiers, wherein the intermix thrust model data is associated with a thrust model identifier common to the two or more engines.

[0127]

[0135] Example 37 includes the aircraft of example 36, in which to determine the plurality of local TRM identifiers, the one or more processors are configured to: access a first FMC engine rating for a first engine of the two or more engines from a non-volatile memory of the FMC; obtain a first EEC engine rating for the first engine from a first EEC associated with the first engine; and determine a first local rating identifier for the first engine based on a selected one of the first FMC engine rating or the first EEC engine rating.

[0128]

[0136] Example 38 includes the aircraft of example 36 or 37, in which the one or more processors are configured to determine a first local TRM identifier of the plurality of local TRM identifiers based on the first local rating identifier and mapping data that maps rating identifiers to TRM identifiers.

[0129]

[0137] Example 39 includes the aircraft of example 38. In this case, to determine the first local TRM identifier, the one or more processors are configured to select the first EEC engine rating as the first local rating identifier based on a determination that the first EEC engine rating is valid.

[0130]

[0138] Example 40 includes the aircraft of example 38 or 39. In this case, to determine the first local TRM identifier, the one or more processors are configured to select the first FMC engine rating as the first local rating identifier based on a determination that the first EEC engine rating is not valid and the first FMC engine rating is valid.

[0131]

[0139] Example 41 includes the aircraft of any one of examples 37-40, in which the one or more processors are further configured to set a flag indicating a detection of an engine data change for the particular engine based on determining that an EEC engine rating for the particular engine is valid and an FMC engine rating for the particular engine is not valid.

[0132]

[0140] Example 42 includes the aircraft of any one of examples 36 or 41. In this case, to select the intermix thrust model data, the one or more processors are configured to determine a common rating identifier based on the plurality of local TRM identifiers.

[0133]

[0141] Example 43 includes the aircraft of example 42, in which to determine the common rating identifier, the one or more processors are configured to: select a representative local TRM identifier from among the plurality of local TRM identifiers; and compare each of the plurality of local TRM identifiers to the representative local TRM identifier.

[0134]

[0142] Example 44 includes the aircraft of example 43, in which the one or more processors are configured to designate the representative local TRM identifier as the common rating identifier based on a determination that each of the plurality of local TRM identifiers matches the representative local TRM identifier.

[0135]

[0143] According to Example 45, a non-transitory computer-readable medium stores a plurality of instructions executable by one or more processors that, when executed, cause the one or more processors to: determine, between power-up of an FMC of an aircraft and subsequent takeoff of the aircraft, a plurality of local TRM identifiers including at least one local TRM identifier for each respective one of a plurality of engines of the aircraft; and select, based on the plurality of local TRM identifiers, intermix thrust model data to be used by the FMC during flight of the aircraft. The intermix thrust model data is associated with a thrust model identifier common to the plurality of engines.

[0136]

[0144] Example 46 includes the non-transitory computer-readable medium of example 45, in which to determine the plurality of local TRM identifiers, the one or more processors are configured to: access a first FMC engine rating for a first engine of the plurality of engines from a non-volatile memory of the FMC, obtain a first EEC engine rating for the first engine from a first EEC associated with the first engine, and determine a first local rating identifier for the first engine based on a selected one of the first FMC engine rating or the first EEC engine rating.

[0137]

[0145] Example 47 includes the non-transitory computer-readable medium of example 45 or 46, in which the one or more processors are configured to determine a first local TRM identifier of the plurality of local TRM identifiers based on the first local rating identifier and mapping data that maps rating identifiers to TRM identifiers.

[0138]

[0146] Example 48 includes the non-transitory computer-readable medium of example 47. In this case, to determine the first local TRM identifier, the one or more processors are configured to select the first EEC engine rating as the first local rating identifier based on a determination that the first EEC engine rating is valid.

[0139]

[0147] Example 49 includes the non-transitory computer-readable medium of example 47 or 48. In this case, to determine the first local TRM identifier, the one or more processors are configured to select the first FMC engine rating as the first local rating identifier based on a determination that the first EEC engine rating is not valid and the first FMC engine rating is valid.

[0140]

[0148] Example 50 includes the non-transitory computer-readable medium of any one of examples 46-49, in which the one or more processors are further configured to set a flag indicating detection of an engine data change based on determining that an EEC engine rating for the particular engine is valid and an FMC engine rating for the particular engine is not valid.

[0141]

[0149] Example 51 includes the non-transitory computer-readable medium of any one of examples 45 to 50. In this case, to select the intermix thrust model data, the one or more processors are configured to determine a common rating identifier based on the plurality of local TRM identifiers.

[0142]

[0150] Example 52 includes the non-transitory computer-readable medium of example 51, in which to determine the common rating identifier, the one or more processors are configured to select a representative local TRM identifier from among the plurality of local TRM identifiers and compare each of the plurality of local TRM identifiers to the representative local TRM identifier.

[0143]

[0151] Example 53 includes the non-transitory computer-readable medium of example 52, in which the one or more processors are configured to designate the representative local TRM identifier as the common rating identifier based on a determination that each of the plurality of local TRM identifiers matches the representative local TRM identifier.

[0144]

[0152] The illustrations of the various embodiments described herein are intended to provide a general understanding of the structure of the various embodiments. These illustrations are not intended to exhaustively describe all elements and features of the apparatus and systems that utilize the structures or methods described herein. Upon review of the present disclosure, many other implementations may become apparent to those skilled in the art. Other implementations may be utilized and derived from the present disclosure, such that structural and logical substitutions and changes may be made without departing from the scope of the present disclosure. For example, the method steps may be performed in an order different from that shown in the figures, or one or more method steps may be omitted. Correspondingly, the present disclosure and the figures should be considered illustrative rather than restrictive.

[0145]

[0153] Moreover, while specific examples have been shown and described herein, any subsequent configurations designed to achieve the same or similar results may be substituted for the specific embodiment shown. The present disclosure is intended to include any and all subsequent adaptations or variations of the various embodiments. Combinations of the above-described embodiments, as well as other embodiments not specifically described herein, will be apparent to those of skill in the art upon review of this specification.

[0146]

[0154] The Abstract of the Disclosure is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. In addition, in the above Detailed Description, various features may be grouped together or described within a single embodiment for the purpose of brevity of the disclosure. The above examples are illustrative of the disclosure, but are not limiting. It should also be understood that numerous modifications and variations are possible in accordance with the principles of the disclosure. As reflected in the following claims, the claimed subject matter may correspond to fewer than all features of any of the disclosed embodiments. Correspondingly, the scope of the disclosure is defined by the following claims and their equivalents.

Claims

1. accessing (204) the first engine data (120) from a non-volatile memory (114) of a Flight Management Computer (FMC) (110) of the aircraft (100); and performing, by the one or more processors, one or more error checking operations based on at least the first engine data to determine whether to select an engine thrust rating for a thrust model of the aircraft based in part on a first engine rating identifier associated with the first engine data.

2. 2. The method of claim 1, wherein the one or more error checking operations include comparing (312) a cyclic redundancy check (CRC) value received from an electronic engine controller (EEC) (104) with a corresponding CRC value from the non-volatile memory of the FMC.

3. 3. The method of claim 2, further comprising clearing (306) the first engine data from the non-volatile memory of the FMC based on a result of the one or more error checking operations.

4. receiving (206), at the one or more processors of the FMC, from a first electronic engine controller (EEC) (104) of the aircraft, a first thrust rating identifier associated with a first engine (102) of the aircraft; receiving, at the one or more processors of the FMC, from a second EEC of the aircraft, a second thrust rating identifier associated with a second engine of the aircraft (206); and 2. The method of claim 1, further comprising determining (502) a single rating identifier (614 common rating identifier) ​​based on the first thrust rating identifier, the second thrust rating identifier, and the first engine rating identifier.

5. Determining the single rating identifier comprises: determining (406) a first local engine rating identifier for the first engine based on the first thrust rating identifier and the first engine rating identifier; Mapping (432) the first local engine rating identifier to a first local thrust rating model (TRM) identifier; determining (406) a second local engine rating identifier for the second engine based on the second thrust rating identifier and a second engine rating identifier from the non-volatile memory of the FMC; Mapping the second local engine rating identifier to a second local TRM identifier (432); Designating a single local TRM identifier as a comparison target (502); and 5. The method of claim 4, further comprising: comparing (614) the first local engine rating identifier, the second local engine rating identifier, or both, to the comparison target to identify a common rating identifier as the single rating identifier.

6. 2. The method of claim 1, further comprising receiving (208) sensor data after a power-up of the FMC, wherein the first engine data is accessed in response to the sensor data indicating an engine data processing condition is satisfied.

7. in response to performing the one or more error checking operations to determine whether to select the engine thrust rating for the thrust model indicating selecting the engine thrust rating; selecting the engine thrust rating for the thrust model of the aircraft; and The method of claim 6 , further comprising performing one or more on-board calculations based on the engine thrust ratings.

8. accessing additional engine data for each of one or more additional engines of the aircraft from the non-volatile memory of the FMC; and 2. The method of claim 1, further comprising performing, by the one or more processors, one or more further error checking operations based on the further engine data to determine whether to select the engine thrust rating for the thrust model of the aircraft based in part on one or more engine rating identifiers associated with the further engine data.

9. Two or more engines (102); two or more electronic engine controllers (EECs) (104), each EEC associated with a corresponding one of the two or more engines; and 1. An aircraft (100) comprising a Flight Management Computer (FMC) (110) communicatively coupled to the two or more EECs, the FMC including a non-volatile memory (114) and one or more processors (112), the one or more processors (112) comprising: Accessing first engine data from the non-volatile memory (204); and performing one or more error checking operations (300-600) based on at least the first engine data to determine whether to select an engine thrust rating for a thrust model of the aircraft based in part on a first engine rating identifier associated with the first engine data.

10. 10. The aircraft of claim 9, wherein the one or more error checking operations include comparing (312) a cyclic redundancy check (CRC) value received from the EEC with a corresponding CRC value from the non-volatile memory of the FMC.

11. 11. The aircraft of claim 10, wherein the one or more processors are further configured to clear (306) the first engine data from the non-volatile memory of the FMC based on a result of the one or more error checking operations.

12. The one or more processors: receiving (206) a first thrust rating identifier associated with a first engine of the aircraft from a first EEC of the two or more EECs; receiving (206) a second thrust rating identifier associated with a second engine of the aircraft from a second EEC of the two or more EECs; and 10. The aircraft of claim 9, further configured to: determine (502) a single rating identifier (614 common rating identifier) ​​based on the first thrust rating identifier, the second thrust rating identifier, and the first engine rating identifier.

13. To determine the single rating identifier, the one or more processors: determining (406) a first local engine rating identifier for the first engine based on the first thrust rating identifier and the first engine rating identifier; Mapping (432) the first local engine rating identifier to a first local thrust rating model (TRM) identifier; determining (406) a second local engine rating identifier for the second engine based on the second thrust rating identifier and a second engine rating identifier from the non-volatile memory of the FMC; Mapping the second local engine rating identifier to a second local TRM identifier (432); Designating a single local TRM identifier as a comparison target (502); and 13. The aircraft of claim 12, configured to compare (614) the first local engine rating identifier, the second local engine rating identifier, or both, to the comparison target to identify a common rating identifier as the single rating identifier.

14. 10. The aircraft of claim 9, further comprising one or more sensors (130) configured to generate sensor data indicative of whether an engine data processing condition is satisfied, the one or more processors configured to access engine data from the non-volatile memory and select the engine thrust rating for the thrust model based on the sensor data indicating that the engine data processing condition is satisfied.

15. 15. The aircraft of claim 14, wherein the one or more processors are further configured to, after selecting the engine thrust ratings for the thrust model of the aircraft, perform one or more on-board calculations based on the engine thrust ratings.

16. The one or more processors: accessing further engine data for each further engine of the two or more engines from the non-volatile memory; and 10. The aircraft of claim 9, further configured to: perform one or more further error checking operations based on the further engine data to determine whether to select the engine thrust rating for the thrust model of the aircraft based in part on one or more engine rating identifiers associated with the further engine data.

17. A non-transitory computer-readable medium (114) storing a plurality of instructions (118) executable by one or more processors (112), the plurality of instructions, when executed, causing the one or more processors to: accessing (204) engine data (120) associated with an engine of the aircraft from a non-volatile memory of a flight management computer (FMC) (110); performing one or more error checking operations (300-600) based on at least the engine data accessed from the non-volatile memory; and selecting (806) an engine thrust rating for the aircraft thrust model (124); the engine thrust rating is selected from among the engine data accessed from the non-volatile memory or from engine data received from an electronic engine controller (EEC) of the aircraft based at least in part on results of the one or more error checking operations.

18. 20. The non-transitory computer-readable medium of claim 17, wherein the one or more error checking operations include comparing (312) a cyclic redundancy check (CRC) value received from the EEC with a corresponding CRC value from the non-volatile memory of the FMC.

19. 20. The non-transitory computer-readable medium of claim 18, wherein the instructions are executable by one or more processors, and the instructions, when executed, cause the one or more processors to clear the engine data from the non-volatile memory of the FMC based on a result of the one or more error checking operations (306).

20. The instructions executable by one or more processors, when executed, cause the one or more processors to: determining (406), for a first engine of the aircraft, a first local engine rating identifier based on the engine data from the FMC and a first thrust rating identifier received from a first EEC associated with the first engine; Mapping (432) the first local engine rating identifier to a first local thrust rating model (TRM) identifier; determining (406) for a second engine of the aircraft, a second local engine rating identifier based on the engine data from the FMC and a second thrust rating identifier received from a second EEC associated with the second engine; Mapping the second local engine rating identifier to a second local TRM identifier (432); Designating (506) a single local TRM identifier as a comparison target; performing a comparison (600) of the first local engine rating identifier, the second local engine rating identifier, or both, to the comparison target; and 20. The non-transitory computer-readable medium of claim 17, further comprising: determining (614) a single rating identifier based on the comparison.