Systems and methods for monitoring gear retract braking load alleviation system

Abstract

To provide systems and methods for monitoring a gear retract braking (GRB) load alleviation system.SOLUTION: A method for monitoring a gear retract braking load alleviation system includes receiving a plurality of wheel speed measurements from a wheel speed sensor associated with a wheel of a landing gear during an in-air operation. The method includes determining a landing gear load metric based on the plurality of wheel speed measurements. The method also includes, in response to the landing gear load metric satisfying a landing gear load threshold, generating an alert indicating a potential maintenance issue associated with the landing gear.SELECTED DRAWING: Figure 3

Description

[Technical Field]

[0001] FIELD OF THE DISCLOSURE

[0001] The present disclosure relates generally to systems and methods for monitoring a gear retract brake (GRB) alleviation system. [Background technology]

[0002]

[0002] Some aircraft are supported on the ground by landing gear systems that retract into the aircraft's fuselage after takeoff. Each landing gear in a landing gear system may include a shock strut (e.g., an oleo-pneumatic shock) and one or more wheels. The landing gear systems may include a nose landing gear system and two main landing gear systems. The nose landing gear system may include a shock strut with a pair of wheels. The nose landing gear wheels do not include a braking system, and rotation of the nose landing gear system wheels after takeoff is arrested by contact with brake linings mounted within the aircraft's wheel wells.

[0003]

[0003] Each landing gear in the main landing gear system includes a shock strut with one or more pairs of wheels. Each wheel in the main landing gear system includes multiple disc brakes. The multiple disc brakes may be hydraulically or otherwise powered (e.g., using electromagnets). If hydraulically powered, separate normal and alternate brake hydraulic systems provide active and passive sources of hydraulic brake power used to brake and stabilize the aircraft after landing. Selection of the alternate brake hydraulic system is automatic upon detecting a loss of hydraulic system pressure in the normal brake hydraulic system. The normal and alternate brake hydraulic systems have separate hydraulic components that are joined before connecting to the brakes with shuttle valves. Common brake lines (e.g., one for each wheel) run to the multiple disc brakes on the wheels.

[0004] After an aircraft takes off, a hydraulic landing gear retraction system engages to retract the landing gear system into the wheel well. The hydraulic landing gear retraction system includes a GRB load reduction system. The GRB load reduction system stops the rotation of the main landing gear system wheels in a controlled manner to avoid applying high loads to main landing gear system components. Before the landing gear is fully retracted, brake pressure is applied to stop the wheels before they enter the wheel well. This brake pressure is reduced from the aircraft's system pressure, flow-limited, staggered, and actively controlled by an electrohydraulic servo valve to reduce landing gear loads. These factors combine to reduce the torque load on the multiple disc brakes compared to a hard-stopped wheel stop. Use of the GRB load reduction system reduces loads on shock strut components and other main landing gear components that may be critically affected by high loads (e.g., shock strut hard stops and intermediate structures connecting the wheels to the shock struts).

[0005] An aircraft may include a system for monitoring the GRB load alleviation system to detect problems with the GRB load alleviation system. Some existing monitors for the GRB system include monitors coupled to specific components of the GRB load alleviation system, but such monitors may not indicate problems when one or more unmonitored components are not operating properly. Monitoring all components of the GRB load alleviation system may be impractical due to considerations of complexity, reliability, availability of data processing resources, and weight. Other existing monitors for the GRB load alleviation system measure loads directly via sensors (e.g., strain gauges), but such monitors add complexity and weight and may need to be frequently calibrated to ensure reliable outputs. It would be desirable to provide a monitoring system for the GRB load alleviation system that monitors the operation of the entire GRB load alleviation system without the need to directly measure loads. Summary of the Invention

[0006] In one particular embodiment, a method includes receiving, during airborne operation, a plurality of wheel speed measurements from wheel speed sensors associated with landing gear wheels. The method includes determining a landing gear load metric based on the plurality of wheel speed measurements. The method also includes generating an alert indicating a potential maintenance issue associated with the landing gear in response to the landing gear load metric satisfying a landing gear load threshold.

[0007] In another particular embodiment, a system includes one or more processors configured to receive a plurality of wheel speed measurements from wheel speed sensors associated with wheels of a landing gear. The one or more processors are configured to determine a landing gear load metric based on the plurality of wheel speed measurements. The one or more processors are also configured to generate an alert indicating a potential maintenance issue associated with the landing gear in response to determining that the landing gear load metric meets a landing gear load threshold.

[0008] In another particular embodiment, a non-transitory computer-readable medium includes instructions that, when executed by one or more processors, cause the one or more processors to receive a plurality of wheel speed measurements from wheel speed sensors associated with wheels of a landing gear. The instructions cause the one or more processors to determine a landing gear load metric based on the plurality of wheel speed measurements. The instructions further cause the one or more processors to generate an alert indicating a potential maintenance issue associated with the landing gear in response to determining that the landing gear load metric meets a landing gear load threshold.

[0009] In another particular embodiment, a device includes means for receiving, during airborne operation, a plurality of wheel speed measurements from wheel speed sensors associated with landing gear wheels. The device also includes means for determining a landing gear load metric based on the plurality of wheel speed measurements. The device also includes means for generating an alert indicating a potential maintenance issue associated with the landing gear in response to the landing gear load metric satisfying a landing gear load threshold. [Brief explanation of the drawings]

[0010] [Figure 1] 1 illustrates an exemplary system for monitoring a GRB load reduction system, according to some embodiments of the present disclosure. [Figure 2]

[0011] 1 illustrates an exemplary GRB load reduction system, according to some embodiments of the present disclosure. [Figure 3]

[0012] 1 is a flowchart of an example method for monitoring a GRB load reduction system, according to some embodiments of the present disclosure. [Figure 4]

[0013] FIG. 1 is a block diagram of a computing environment including a computing device configured to support aspects of computer-implemented methods and computer-executable program instructions (or code) according to some embodiments of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0011]

[0014] An aircraft may be equipped with one or more GRB load alleviation systems for controlling the rotation of the wheels of the main landing gear system after takeoff to avoid high loads on the main landing gear system components due to abruptly stopping the rotation of the wheels. The GRB load alleviation systems may be monitored to identify when a problem exists with one or more of the GRB load alleviation systems. A problem with one or more of the GRB load alleviation systems may cause a problem with the main landing gear system.

[0012]

[0015] A technical advantage of the present disclosure is the ability to monitor the operation of the GRB load mitigation system as a whole to identify problems, instead of monitoring individual components of the GRB load mitigation system. Additionally, the systems and methods of the present disclosure use the outputs of wheel speed sensors already installed on the landing gear to monitor the GRB load mitigation system.

[0013]

[0016] Another technical advantage of the present disclosure in some aspects is the use of a dynamic model of the GRB load alleviation system to predict mechanical loads on system components from wheel speed sensors, thereby eliminating potentially problematic reliance on direct measurement of loads (e.g., via strain gauges). Another technical advantage of the present disclosure is that the systems and methods disclosed herein are agnostic to the type of brake in a landing gear braking system. The present disclosure is applicable to hydraulic brakes, electric brakes, etc.

[0014]

[0017] The drawings and the following description illustrate specific, exemplary embodiments. Those skilled in the art will recognize that they may devise various configurations, not explicitly described or shown herein, that embody the principles described herein and fall within the scope of the claims that follow. Furthermore, any examples described herein are intended to aid in the understanding of the principles of the disclosure and are not intended to be limiting. Consequently, the disclosure is not limited to the specific embodiments or examples described below, but is limited by the claims and their equivalents.

[0015]

[0018] Certain embodiments are described herein with reference to the drawings. In the description, common features are marked with common reference numerals throughout the drawings. Various terms are used herein only to describe particular implementations and are not intended to be limiting. For example, the singular forms "a" and "the" are intended to include the plural (unless the context clearly dictates otherwise). Furthermore, some features described herein may exist in the singular in some embodiments and in the plural in other embodiments. To illustrate, FIG. 1 depicts a system 100 including one or more processors ("processor(s) 106" in FIG. 1), indicating that in some embodiments, the system 100 includes a single processor 106 and in other embodiments, the system 100 includes multiple processors 106. For ease of reference herein, such features are generally introduced as "one or more" features, followed by a single or optionally multiple features (typically indicated by "s"). This is unless it is explicitly stated that multiple aspects relate to multiple features.

[0016]

[0019] Furthermore, the terms "comprise," "comprises," and "comprising" are used interchangeably with "include," "includes," and "including." Furthermore, the term "wherein" is used interchangeably with the term "where." As used herein, "exemplary" indicates an example, an implementation, and / or an aspect and should not be construed as limiting or as indicating a preferred or preferred implementation. As used herein, ordinal terms (e.g., "first," "second," "third," etc.) modifying elements such as structures, components, acts, etc. do not in themselves indicate a priority or order of one element over another, but merely distinguish one element from another element having the same name (apart from its use as an ordinal term). 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.

[0017]

[0020] 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) can refer to actively generating, calculating, or determining a parameter (or signal), or can refer to using, selecting, or accessing a parameter (or signal) that has already been generated, for example, by another component or device. As used herein, "connected" or "coupled" may include "communicatively coupled," "electrically coupled," or "physically coupled," or may also (or alternatively) include any combination thereof. Two devices (or components) can 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 via electrical communication, can send and receive electrical signals (digital signals 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 coupled, electrically coupled, or physically coupled) without any intervening components.

[0018]

[0021] 1 illustrates an example system 100 for monitoring a GRB load mitigation system of an aircraft, in accordance with some embodiments of the present disclosure. In some implementations, system 100 includes a computing device 102 configured to communicate with one or more first wheel speed sensors 104 and / or one or more second wheel speed sensors 110.

[0019]

[0022] In some embodiments, the first wheel speed sensor(s) 104 includes one or more components configured to provide a first plurality of wheel speed measurements 118 associated with a first wheel 112 of the landing gear 116 during operation in the air. The second wheel speed sensor(s) 110 includes one or more components configured to provide a second plurality of wheel speed measurements 120 associated with a second wheel 114 of the landing gear 116 during operation in the air. An aircraft may include two or more landing gears 116. In FIG. 1 , the landing gear 116 includes a pair of wheels 112, 114, but in other embodiments, the landing gear 116 may include one or more additional pairs of wheels.

[0020]

[0023] In some aspects, the first plurality of wheel speed measurements 118 and / or the second plurality of wheel speed measurements 120 may include one or more types of measurements associated with the rotational speed of the respective wheels 112, 114. For example, the wheel speed measurements 118, 120 may include direct wheel speed measurements, wheel position measurements over time, etc. In some configurations, the wheel speed measurements 118, 120 may include additional data associated with the wheel speeds to contextualize the wheel speed measurements 118, 120. For example, if some portions of the wheel speed measurements 118, 120 include wheel position measurements, additional data identifying a respective timestamp for each wheel position measurement may be included within the wheel speed measurements 118, 120. In other configurations, this additional data may be communicated to the computing device 102 individually or in some combination thereof.

[0021]

[0024] In some implementations, computing device 102 includes one or more processors 106 coupled to memory 108. Processor(s) 106 are configured to receive a first plurality of wheel speed measurements 118, a second plurality of wheel position measurements 120, or some combination thereof. In some aspects, processor(s) 106 include a metric identification module 122 and an alert generator 128.

[0022]

[0025] The metric identification module 122 may be configured to determine a landing gear load metric 124 based on the received wheel speed measurements 118, 120. In some aspects, the metric identification module 122 may be configured to determine the landing gear load metric 124 based on a wheel speed metric 126 determined for each wheel 112, 114 of the landing gear 116. The first wheel speed metric 126 for the first wheel 112 is based on the first plurality of wheel speed measurements 118, and the second wheel speed metric 126 for the second wheel 114 is based on the second plurality of wheel speed measurements 120.

[0023]

[0026] In some aspects, landing gear load metric 124 may be based on one or more metrics associated with GRB loads. For example, landing gear load metric 124 may include a wheel acceleration metric associated with first wheel 112, second wheel 114, or a combination thereof.

[0024]

[0027] In some implementations, the processor(s) 106 may be configured to determine whether the landing gear load metric 124 meets the landing gear load threshold 132. The landing gear load threshold 132 may be retrieved from the memory 108. For example, the landing gear load threshold 132 may include data indicating a combined wheel acceleration limit of −300 rad / s / s for an accumulated 0.125 seconds per landing gear retract. In other implementations, the wheel acceleration limit and accumulated time limit may have other values. The metric identification module 122 may be configured to generate the landing gear load metric 124 based on the first plurality of wheel speed measurements 118, the second plurality of wheel speed measurements 120, or a combination thereof. The processor(s) 106 may be configured to determine whether the wheel speed measurements 118, 120 indicate that the acceleration of the first wheel 112 and / or the second wheel 114 is less than the landing gear load threshold 132. In one particular implementation, the processor(s) 106 may be configured to determine whether the wheel speed measurements 118, 120 indicate a wheel acceleration less than −300 rad / s / s and then generate a time value associated with the wheel speed measurements 118, 120. If the time value is greater than 0.125 seconds, the processor(s) 106 may be configured to count instances where the landing gear load metric 124 meets the landing gear load threshold 132, indicating that one or more of the wheels 112, 114 is rapidly decelerating.

[0025]

[0028] In some aspects, the metric identification module 122 may be configured to identify the landing gear load metrics 124 based on a dynamic model 134. The dynamic model 134 may be retrieved from the memory 108. The dynamic model 134 may include one or more parameters, data values, relationships, etc. associated with the GRB load alleviation system. The dynamic model 134 may enable load prediction from the state of the GRB load alleviation system rather than directly sensing the load. For example, the dynamic model 134 may model the state of a cantilevered beam rotational inertia on a hard stop. Such a dynamic model 134 may be integrated using a discrete-time ordinary differential equation solution (e.g., Runge-Kutta method) to determine estimated landing gear loads. In other configurations, the dynamic model 134 may include additional springs, dampers, rotational inertia, brakes, hard stops, pivots, gas or hydraulic chambers and valves, electrical, gas, or hydraulic actuators, or other components. In the same or alternative configurations, the dynamic model 134 may include consideration of static and dynamic friction, temperature, pressure, other variables, or any combination thereof.

[0026]

[0029] Dynamic model 134 may be used to predict loads from component states and system states of the GRB load alleviation system. Component states may include, for example, brake inertia and tire inertia. Brake inertia may be estimated based on one or more brake wear measurements. Tire inertia may be based on one or more tire wear measurements. Other component states and system states may include whether the landing gear is retracted, whether the aircraft is accelerating, air loads, whether the landing gear has multiple configurations (i.e., the landing gear is semi-levered), whether the wheels, tires, or a combination thereof have multiple configurations, whether the braking system or other control systems have multiple states, etc.

[0027]

[0030] In some configurations, inputs to the dynamic model 134 may include one or more measurements, calculations, data values, data derivations, etc. associated with the GRB load alleviation system. For example, the inputs may include brake pressure, electrohydraulic servo valve pressure, brake metering valve pressure, shock strut fluid pressure, shock strut fluid temperature, brake temperature, brake force or torque, landing gear component force or torque, electric brake actuator measurements (e.g., position, velocity, acceleration, force, voltage, current, etc.), brake heat sink wear (e.g., obtained via position measurements or indirectly estimated), landing gear position state(s) (e.g., obtained from control lever position, landing gear latch state, proximity sensors, etc.), wheel position, wheel speed, wheel acceleration, jerk sensor(s), inertial sensor(s) on wheels, inertial sensor(s) on tires, inertial sensor(s) on brakes, inertial sensor(s) on landing gear, inertial sensor(s) on fuselage, etc.

[0028]

[0031] In one particular aspect, the processor(s) 106 may also be configured to filter one or more inputs of the dynamic model 134 as part of an error mitigation process, an error correction process, or some combination thereof. If one or more of the inputs to the dynamic model 134 contribute to errors (e.g., unnecessary false positives) in the system 100, the one or more of the inputs may be filtered to improve the performance of the dynamic model 134.

[0029]

[0032] In response to landing gear load metric 124 meeting landing gear load threshold 132, alert generator 128 may be configured to generate alert 130 indicating a potential maintenance issue associated with landing gear 116. Alert 130 may include, for example, a visual alert, an audible alert, a tactile alert, a text-based alert (e.g., a log entry, a message to flight crew and / or maintenance personnel, etc.), other suitable alert, or a combination thereof.

[0030]

[0033] In some aspects, the alert 130 is based on a characteristic of the output from the dynamic model 134. For example, the output from the dynamic model 134 may include an acceleration limit associated with the wheel(s) 112, 114 of the landing gear 116. Illustratively, if the acceleration of the first wheel 112, the second wheel 114, or both, meets an acceleration threshold, the dynamic model 134 may indicate that a particular operating mode or set of operating modes is not a normal operating mode.

[0031]

[0034] In one particular aspect, a potential maintenance issue is associated with a particular mode of operation. For example, a particular mode of operation may enable the GRB load alleviation system to impart one or more large impacts to the landing gear(s) 116. A particular mode of operation may enable one or more wheels 112, 114 to rapidly decelerate. A particular mode of operation may be associated with one or more GRB load alleviation system components that enable the rapid deceleration of the wheels 112, 114. This may include one or more electrohydraulic servo valves (e.g., one or more anti-slide valves), one or more brake metering valves, or a combination thereof, that enable the rapid deceleration of the wheels 112, 114.

[0032]

[0035] In exemplary operation, the system 100 may be implemented using a counter that decrements after a certain number of known good cycles and a landing gear cycle count. The counter is initially set to zero and is utilized so that a number of abnormal operating modes must be detected before an alert identifying the problem is generated. The landing gear cycle count is also initially set to zero. Detection of a problem by the monitoring system with the GRB load alleviation system does not require any action from the aircraft pilot and does not need to be immediately addressed. The system 100 is initiated each time the landing gear handle is moved to the “up” position (i.e., each time the landing gear retraction system is activated). During airborne operation, the first wheel speed sensor 104 communicates a first plurality of wheel speed measurements 118 to the computing device 102, and the second wheel speed sensor 110 communicates a second plurality of wheel speed measurements 120 to the computing device 102. After determining the landing gear load metric 124 based on the wheel speed measurements 118, 120 and the output of the dynamic model 134, if the landing gear load metric 124 meets the landing gear load threshold 132, the computing device 102 indicates a particular operating mode of the GRB load alleviation system that is not a normal operating mode, increments a counter by 1, and sets the number of landing gear cycles to 0. After completion of landing gear retraction, if the number of landing gear cycles is greater than or equal to the landing gear cycle threshold (e.g., 100, 50, or some other number of cycles), the counter is decremented by 1, and the GRB load alleviation system waits for the next activation of the landing gear retraction system. If the counter is less than the counter threshold (e.g., 10 or some other specified number), the GRB load alleviation system waits for the next activation of the landing gear retraction system.

[0033]

[0036] If the counter equals the counter threshold, the particular operating mode is the active particular operating mode and an alert 130 is generated. Based on the landing gear load metric(s) 124, an associated message may provide troubleshooting details. Use of the counter and the number of landing gear cycles may be discontinued until maintenance is performed. If the landing gear load metric(s) 124 for a subsequent cycle indicate further troubleshooting details that differ from the troubleshooting details associated with the active particular operating mode, a further alert 130 and associated message may be generated.

[0034]

[0037] In some aspects, computing device 102 may be associated with, integrated into, or otherwise included within an aircraft. System 100 may also include components not shown in FIG. 1 . For example, computing device 102 may also include a receiver configured to receive first plurality of wheel speed measurements 118, second plurality of wheel speed measurements 120, or a combination thereof. The receiver may be configured to receive data, for example, via a computer bus. As a further example, system 100 may also include one or more input / output interfaces, one or more network interfaces, etc. Additionally, while FIG. 1 illustrates memory 108 of system 100 as storing particular data, more, less, and / or different data may be present in memory 108 without departing from the scope of this disclosure.

[0035]

[0038] 1 illustrates certain operations occurring within computing device 102, these operations may be performed by other components of system 100 without departing from the scope of the present disclosure. For example, one or more components external to computing device 102 may be configured to host or otherwise incorporate some or all of the components of metric identification module 122, alert generator 128, or some combination thereof. Such component(s) may be located remotely from computing device 102 and accessed via a modem of computing device 102. As a further example, memory 108 may be one or more storage devices, which may be located remotely from computing device 102, remotely from each other, or a combination thereof.

[0036]

[0039] 1 depicts the computing device 102, the first wheel 112, the second wheel 114, and the landing gear 116 separately, other configurations are possible without departing from the scope of this disclosure. For example, the computing device 102 may be integrated into one or more components of the landing gear 116. As a further example, one or more components of the computing device 102 may be distributed across multiple computing devices (e.g., a group of processor cores).

[0037]

[0040] 2 illustrates an example GRB load mitigation system 200 according to some embodiments of the present disclosure. In the example system 200, the computing device 102 of FIG. 1 is inserted into an existing GRB load mitigation system without requiring additional sensors to be placed in the system.

[0038]

[0041] In some embodiments, system 200 includes an anti-slide automatic brake control unit (AACU) 228 coupled to a system including brake metering valves 202. Brake metering valves 202 meter pressure to brakes 201 coupled to first wheels 112 and second wheels 114. The AACU is an electronic device configured to control anti-slide and automatic braking components used to control the brakes of first wheels 112 and second wheels 114. In some aspects, AACU 228 includes a first anti-slide card 222 coupled to a second anti-slide card 224. Each of anti-slide cards 222, 224 includes a landing gear retract brake load shedding proportional / integral control module 218 configured to provide a control signal to anti-slide valve 204. The AACU 228 is also configured to receive a first plurality of wheel speed measurements 118 from a first wheel speed sensor 104 coupled to the first wheel 112 and a second plurality of wheel speed measurements 120 from a second wheel speed sensor 110 coupled to the second wheel 114. In some embodiments, an anti-skid valve 204 enables shedding of the first wheel 112 and the second wheel 114 after takeoff. In some aspects, the anti-skid valve 204 may be coupled to the wheels 112, 114 via a restrictor-equipped check valve 208 and a flow limiter 214. In some aspects, the restrictor-equipped check valve 208 may be coupled between a fuse 206 and a shuttle valve 210 associated with one of the wheels 112, 114. For example, the restrictor-equipped check valve 208 shown in FIG. 2 is coupled between the fuse 206 and the shuttle valve 210 associated with the first wheel 112.

[0039]

[0042] In some embodiments, system 200 controls the braking of the wheels 112, 114 of the aircraft's main landing gear system after the aircraft takes off. AACU 228 may use wheel speed measurements 118, 120 to control the shedding of the wheels 112, 114. By adding computing device 102 to the GRB shedding system, system 200 can monitor components of the GRB shedding system without adding additional sensors to the GRB shedding system. Although computing device 102 is illustrated as separate from other components of system 200, one or more components of computing device 102 may be associated with, integrated into, or otherwise included within the GRB shedding system. For example, computing device 102 may be integrated with AACU 228 within a single electronic device.

[0040]

[0043] 3 is a flowchart of an example method 300 for monitoring a GRB offloading system, according to some embodiments of the present disclosure. Method 300 may be initiated, performed, or controlled by one or more processors executing instructions, such as processor(s) 106 of FIG. 1 executing instructions from memory 108.

[0041]

[0044] In some implementations, the method 300 includes receiving, during airborne operation, a plurality of wheel speed measurements from wheel speed sensors associated with wheels of a landing gear at block 302. For example, the processor(s) 106 of FIG. 1 may receive a plurality of wheel speed measurements 118, 120 from wheel speed sensors 104, 110 associated with wheels 112, 114 of a landing gear 116 during airborne operation.

[0042]

[0045] The method 300 determines a landing gear load metric based on the plurality of wheel speed measurements at block 304. For example, the processor(s) 106 of FIG. 1 may determine the landing gear load metric 124 based on the plurality of wheel speed measurements 118, 120.

[0043]

[0046] Method 300 also includes generating an alert indicating a potential maintenance issue associated with the main landing gear system in response to the landing gear load metric meeting the landing gear load threshold, at block 306. For example, processor(s) 106 in FIG. 1 may generate alert 130 indicating a potential maintenance issue associated with landing gear 116 in response to landing gear load metric 124 meeting landing gear load threshold 132.

[0044]

[0047] In some implementations, method 300 may include fewer, more, and / or different steps without departing from the scope of this disclosure. For example, method 300 may also include filtering the input of the dynamic model as part of the error mitigation process. As another example, method 300 may also include filtering the output of the dynamic model as part of the error correction process.

[0045]

[0048] 1 and 2 may be implemented to achieve one or more of the technical advantages described in more detail above. For example, method 300 may enable monitoring the health of a GRB load mitigation system without additional sensors being added to the system.

[0046]

[0049] 4 is a block diagram of a computing environment 400 including a computing device 410 configured to support aspects of computer-implemented methods and computer-executable program instructions (or code) according to some embodiments of the present disclosure. For example, computing device 410, or portions thereof, are configured to execute instructions to initiate, perform, or control one or more of the operations described in more detail above with reference to FIGS. 1-3. In one particular aspect, computing device 410 may include, correspond to, or be included within computing device 102 of FIG. 1, one or more servers, one or more virtual devices, or a combination thereof.

[0047]

[0050] Computing device 410 includes one or more processors 420. In one particular aspect, processor(s) 420 correspond to processor(s) 106 of FIG. 1. Processor(s) 420 are configured to communicate with system memory 430, one or more storage devices 450, one or more input / output interfaces 440, one or more communication interfaces 460, or any combination thereof. System memory 430 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. System memory 430 stores operating system 432, which may include a basic input / output system for booting computing device 410 as well as a full operating system for enabling computing device 410 to interact with users, other programs, and other devices. The system memory 430 stores system (program) data 438, such as the first plurality of wheel speed measurements 118 and / or the second plurality of wheel speed measurements 120, the landing gear load thresholds 132, the alerts 130 of FIG. 1, or a combination thereof.

[0048]

[0051] The system memory 430 includes one or more applications 434 (e.g., collections of instructions) executable by the processor(s) 420. As one example, the one or more applications 434 include instructions 436 executable by the processor(s) 420 to initiate, control, or perform one or more of the operations described with reference to Figures 1-3. Illustratively, the one or more applications 434 include instructions 436 executable by the processor(s) 420 to initiate, control, or perform one or more of the operations described with respect to receiving wheel speed measurements 118, 120, determining landing gear load metric 124, and generating alert 130 in Figure 1.

[0049]

[0052] In one particular implementation, system memory 430 includes a non-transitory computer-readable medium (e.g., a computer-readable storage device) having stored thereon instructions 436 that, when executed by processor(s) 420, cause processor(s) 420 to initiate, perform, or control operations for monitoring a landing gear brake load alleviation system. The operations include receiving, during airborne operation, a plurality of wheel speed measurements from wheel speed sensors associated with the landing gear wheels. The operations also include determining a landing gear load metric based on the plurality of wheel speed measurements. The operations also include generating an alert indicating a potential maintenance issue associated with the landing gear in response to the landing gear load metric meeting a landing gear load threshold.

[0050]

[0053] The one or more storage devices 450 include non-volatile storage devices, such as magnetic disks, optical disks, or flash memory devices. In a particular embodiment, the storage devices 450 include both removable and non-removable memory devices. The storage devices 450 are configured to store an operating system, operating system images, applications (e.g., one or more applications 434), and program data (e.g., program data 438). In a particular aspect, the system memory 430, the storage devices 450, or both, comprise tangible computer-readable media. In a particular aspect, one or more of the storage devices 450 reside external to the computing device 410.

[0051]

[0054] The one or more input / output interfaces 440 enable the computing device 410 to communicate with one or more input / output devices 470 to facilitate interaction with a user. For example, the one or more input / output interfaces 440 may include a display interface, an input interface, or both. For example, the input / output interface 440 may be adapted to receive input from a user, receive input from another computing device, or a combination thereof. In some embodiments, input / output interface 440 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 embodiments, input / output device(s) 470 include one or more user interface devices and displays, including any combination of buttons, keyboards, pointing devices, displays, speakers, microphones, touchscreens, and other devices.

[0052]

[0055] The processor(s) 420 are configured to communicate with a device or controller 480 via one or more communication interfaces 460. For example, the one or more communication interfaces 460 may include a network interface. The device or controller 480 may include, for example, the first wheel speed sensor(s) 104, the second wheel speed sensor(s) 110 of FIG. 1, or a combination thereof.

[0053]

[0056] In some implementations, a non-transitory computer-readable medium (e.g., a computer-readable storage device) 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-3. In some implementations, some or all of one or more of the operations or methods of FIGS. 1-3 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)), or any combination thereof, that execute instructions through dedicated hardware circuitry.

[0054]

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

[0055]

[0058] Furthermore, 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, and other embodiments not specifically described herein, will be apparent to those of skill in the art upon review of this specification.

[0056]

[0059] 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. Additionally, in the above Detailed Description, various features may be grouped together or described within a single embodiment for the purpose of conciseness of the disclosure. The above examples are illustrative of the disclosure, not limiting. Furthermore, many modifications and variations are possible in accordance with the principles of the disclosure. As reflected in the following claims, claimed subject matter may not be directed to all features of any disclosed embodiment. Accordingly, the scope of the disclosure is defined by the following claims and their equivalents.

[0057]

[0060] Furthermore, the present disclosure includes embodiments according to the following examples.

[0058]

[0061] According to Example 1, a method includes receiving, during airborne operation, a plurality of wheel speed measurements from wheel speed sensors associated with wheels of a landing gear; determining a landing gear load metric based on the plurality of wheel speed measurements; and generating an alert indicating a potential maintenance issue associated with the landing gear in response to the landing gear load metric satisfying a landing gear load threshold.

[0059]

[0062] Example 2 includes the method of example 1, also including receiving a second plurality of wheel speed measurements from a second wheel speed sensor associated with a second wheel of the landing gear, and determining the landing gear load metric includes determining a wheel speed metric for the wheel and a second wheel speed metric for the second wheel, the second wheel speed metric being based on the second plurality of wheel speed measurements.

[0060]

[0063] Example 3 includes the method of example 1 or example 2, in which determining the landing gear load metric includes analyzing the plurality of wheel speed measurements to determine the wheel speed metric.

[0061]

[0064] Example 4 includes the method of example 3, wherein the wheel speed metrics include wheel acceleration metrics.

[0062]

[0065] Example 5 includes any of examples 3 and 4, wherein the plurality of wheel speed measurements includes a plurality of wheel position measurements.

[0063]

[0066] Example 6 includes the method of any one of examples 1 to 5, wherein determining the landing gear load metric includes determining the landing gear load metric based on a dynamic model of the landing gear.

[0064]

[0067] Example 7 includes the method of example 6, further including filtering the dynamic model input as part of the error mitigation process.

[0065]

[0068] Example 8 includes the method of example 6 or example 7, further including filtering the output of the dynamic model as part of the error correction process.

[0066]

[0069] Example 9 includes the method of any one of examples 6 to 8, wherein the alert is based on a characteristic of the dynamic model.

[0067]

[0070] Example 10 includes the method of example 9, wherein the potential security issue is associated with a particular mode of operation.

[0068]

[0071] According to Example 11, the system includes one or more processors configured to receive a plurality of wheel speed measurements from wheel speed sensors associated with wheels of a landing gear; determine a landing gear load metric based on the plurality of wheel speed measurements; and generate an alert indicating a potential maintenance issue associated with the landing gear in response to determining that the landing gear load metric meets a landing gear load threshold.

[0069]

[0072] Example 12 includes the system of example 11, wherein the one or more processors are further configured to: receive a second plurality of wheel speed measurements from a second wheel speed sensor associated with a second wheel of the landing gear; and determining the landing gear load metric includes determining a wheel speed metric for the wheel and a second wheel speed metric for the second wheel, the second wheel speed metric being based on the second plurality of wheel speed measurements. Determining the landing gear load metric also includes using a dynamic model of the landing gear to determine the landing gear load metric based on the wheel speed metric and the second wheel speed metric.

[0070]

[0073] Example 13 includes the system of example 11 or 12, wherein determining the landing gear load metric includes performing an analysis of the plurality of wheel speed measurements to determine the wheel speed metric.

[0071]

[0074] Example 14 includes the system of example 13, wherein the wheel speed metrics include wheel acceleration metrics.

[0072]

[0075] Example 15 includes the system of example 13 or 14, wherein the plurality of wheel speed measurements includes a plurality of wheel position measurements.

[0073]

[0076] Example 16 includes the system of any of examples 11-15, wherein determining the landing gear load metric is based on a dynamic model of the landing gear.

[0074]

[0077] Example 17 includes the system of example 16, wherein the one or more processors are further configured to filter inputs of the dynamic model as part of the error mitigation process.

[0075]

[0078] Example 18 includes the system of example 16 or 17, wherein the one or more processors are further configured to filter the output of the dynamic model as part of an error correction process.

[0076]

[0079] Example 19 includes the system of any one of examples 16-18, wherein the alert is based on a characteristic of the dynamic model.

[0077]

[0080] Example 20 includes the system of example 19, wherein the potential security issue is associated with a particular mode of operation.

[0078]

[0081] According to Example 21, a non-transitory computer-readable medium includes instructions that, when executed by one or more processors, cause the one or more processors to receive a plurality of wheel speed measurements from wheel speed sensors associated with wheels of a landing gear; determine a landing gear load metric based on the plurality of wheel speed measurements; and generate an alert indicating a potential maintenance issue associated with the landing gear in response to the landing gear load metric satisfying a landing gear load threshold.

[0079]

[0082] Example 22 includes the non-transitory computer-readable medium of example 21, wherein the instructions, when executed by the one or more processors, further cause the one or more processors to receive a second plurality of wheel speed measurements from a second wheel speed sensor associated with a second wheel of the landing gear; and determining the landing gear load metric includes determining a wheel speed metric for the wheel and a second wheel speed metric for the second wheel, the second wheel speed metric being based on the second plurality of wheel speed measurements.

[0080]

[0083] Example 23 includes the non-transitory computer-readable medium of example 21 or 22, wherein determining the landing gear load metric includes performing an analysis of the plurality of wheel speed measurements to determine the wheel speed metric.

[0081]

[0084] Example 24 includes the non-transitory computer-readable medium of example 23, in which the wheel speed metrics include wheel acceleration metrics.

[0082]

[0085] Example 25 includes the non-transitory computer-readable medium of example 23 or 24, wherein the plurality of wheel speed measurements includes a plurality of wheel position measurements.

[0083]

[0086] Example 26 includes the non-transitory computer-readable medium of any of examples 21-25, wherein determining the landing gear load metric is based on a dynamic model of the landing gear.

[0084]

[0087] Example 27 includes the non-transitory computer-readable medium of Example 26, wherein the instructions further cause the one or more processors to filter inputs of the dynamic model as part of an error mitigation process.

[0085]

[0088] Example 28 includes the non-transitory computer-readable medium of example 26 or 27, wherein the instructions further cause the one or more processors to filter an output of the dynamic model as part of an error correction process.

[0086]

[0089] Example 29 includes the non-transitory computer-readable medium of any one of Examples 26 to 28, wherein the alert is based on a characteristic of the dynamic model.

[0087]

[0090] Example 30 includes the non-transitory computer-readable medium of example 29, wherein the potential security issue is associated with a particular mode of operation.

Claims

1. 1. A method (300) comprising: receiving (302) a plurality of wheel speed measurements (118, 120) from wheel speed sensors (104, 110) associated with wheels (112, 114) of a landing gear (116) during operation in the air; determining (304) a landing gear load metric (124) based on the plurality of wheel speed measurements; and generating (306) an alert (130) indicating a potential maintenance issue associated with the landing gear in response to the landing gear load metric meeting a landing gear load threshold (132).

2. 2. The method of claim 1, further comprising receiving a second plurality of wheel speed measurements from a second wheel speed sensor associated with a second wheel of the landing gear, and wherein determining the landing gear load metric comprises determining a wheel speed metric for the wheel and a second wheel speed metric for the second wheel, the second wheel speed metric being based on the second plurality of wheel speed measurements.

3. The method of claim 1 , wherein determining the landing gear load metric comprises analyzing the plurality of wheel speed measurements to determine a wheel speed metric.

4. The method of claim 3 , wherein the wheel speed metric comprises a wheel acceleration metric.

5. The method of claim 3 , wherein the plurality of wheel speed measurements comprises a plurality of wheel position measurements.

6. The method of claim 1 , wherein determining the landing gear load metric comprises determining the landing gear load metric based on a dynamic model of the landing gear (134).

7. The method of claim 6 further comprising filtering the inputs of the dynamic model as part of an error mitigation process.

8. The method of claim 6 further comprising filtering the output of the dynamic model as part of an error correction process.

9. The method of claim 6 , wherein the alert is based on a characteristic of the dynamic model.

10. The method of claim 9 , wherein the potential security issue is associated with a particular mode of operation.

11. A system (100), comprising: receiving a plurality of wheel speed measurements (118, 120) from wheel speed sensors (104, 110) associated with wheels (112, 114) of a landing gear (116); determining a landing gear load metric (124) based on the plurality of wheel speed measurements; and generating an alert indicating a potential maintenance issue associated with the landing gear in response to determining that the landing gear load metric meets a landing gear load threshold.

12. The system of claim 11 , wherein determining the landing gear load metric includes performing an analysis of the plurality of wheel speed measurements to determine a wheel speed metric (126).

13. The system of claim 12 , wherein the wheel speed metric comprises a wheel acceleration metric.

14. The system of claim 12 , wherein the plurality of wheel speed measurements comprises a plurality of wheel position measurements.

15. The system of claim 11 , wherein determining the landing gear load metric is based on a dynamic model of the landing gear (134).

16. 16. The system of claim 15, wherein the one or more processors are further configured to perform filtering of the dynamic model inputs as part of an error mitigation process.

17. 16. The system of claim 15, wherein the one or more processors are further configured to perform filtering of the output of the dynamic model as part of an error correction process.

18. The system of claim 15 , wherein the alert is based on a characteristic of the dynamic model.

19. The system of claim 18 , wherein the potential security issue is associated with a particular mode of operation.

20. A non-transitory computer-readable medium (430) comprising instructions (434), which, when executed by one or more processors (106, 420), cause the one or more processors to: receiving a plurality of wheel speed measurements (118, 120) from wheel speed sensors (104, 110) associated with wheels (112, 114) of a landing gear (116); determining a landing gear load metric (124) based on the plurality of wheel speed measurements; and generating an alert (130) indicating a potential maintenance issue associated with the landing gear in response to determining that the landing gear load metric has met a landing gear load threshold (132).

Images