This disclosure generally relates to systems and methods for flying an aircraft. More particularly, this disclosure relates to systems and methods for monitoring an aircraft's turbulent environment and providing instructions or warnings to the aircraft's crew based on the monitored turbulent environment.
Turbulence is an unstable flight condition with rapid variations in either flight path or attitude. It can reduce an aircraft's margins of control and stability and hazardous levels can impart significant “g” loads on an airframe.
Turbulence detection is useful during approach to landing while the flight crew attempts to keep the aircraft on a stabilized flight path. Unstabilized approaches can lead to dangerous landing conditions such as tailstrikes, hard landings, long landings, and bounced landings.
Systems and methods are available for providing “go-around” instructions to an aircraft crew if an unsafe landing is being attempted. Traditionally, aircraft warnings are based on an aircraft's vertical speed and height above the ground, but an aircraft's turbulent environment is not considered.
This disclosure relates to methods and systems for monitoring an aircraft's turbulent environment and providing instructions or warnings to the aircraft's crew based on the monitored turbulent environment. Advantageously, the systems and methods may reduce dangerous landing conditions such as tailstrikes, hard landings, long landings, and bounced landings.
In one embodiment, a warning method for an aircraft includes receiving a first parameter indicative of an aircraft's flight path, calculating a stable approach value based on the first parameter, receiving a second parameter indicative of the aircraft's turbulence, calculating a turbulence factor based on the second parameter, calculating a safe landing value based on the stable approach value and the turbulence factor, comparing the safe landing value to a threshold value, and providing an aircraft warning when the safe landing value fails to meet the threshold value.
In some embodiments, the first parameter includes the aircraft's vertical speed and the aircraft's height above the ground.
In some embodiments, the second parameter includes the aircraft's pitch rate and the aircraft's vertical acceleration rate. In some embodiments, the aircraft's pitch rate includes a frequency of a pitch's oscillation. In some embodiments, the aircraft's vertical acceleration rate includes a maximum vertical acceleration over a period of time.
In some embodiments, the second parameter includes a frequency of a vertical acceleration rate of the aircraft. In some embodiments, the second parameter includes an acceleration of the aircraft about an axis, a rate of change of an acceleration of the aircraft about an axis, a yaw rate of the aircraft, or a roll rate of the aircraft.
In some embodiments, calculating the safe landing value includes normalizing the stable approach value and the turbulence factor. In some embodiments, calculating the safe landing value includes adding the stable approach value and the turbulence factor or multiplying the stable approach value and the turbulence factor.
In some embodiments, the aircraft warning includes a go-around instruction, tailstrike warning, a hard landing warning, a long landing warning, or a bounce landing warning.
In one embodiment, an aircraft warning system includes a first module that receives multiple first parameters indicative of an aircraft's flight path, a second module that calculates a stable approach value based on the multiple first parameters, a third module that receives multiple second parameters indicative of the aircraft's turbulence, a fourth module that calculates a turbulence factor based on the multiple second parameters, a fifth module that calculates a safe landing value based on the stable approach value and the turbulence factor, a sixth module that compares the safe landing value to a threshold value, and a seventh module that provides an aircraft warning when the safe landing value fails to meet the threshold value.
In some embodiments, the multiple first parameters include the aircraft's vertical speed and the aircraft's height above the ground.
In some embodiments, the multiple second parameters include the aircraft's pitch rate and the aircraft's vertical acceleration rate. In some embodiments, the aircraft's pitch rate includes a frequency of a pitch's oscillation. In some embodiments, the aircraft's vertical acceleration rate includes a maximum vertical acceleration over a period of time.
In some embodiments, the second parameter includes a frequency of a vertical acceleration rate of the aircraft. In some embodiments, the second parameter includes an acceleration of the aircraft about an axis, a rate of change of an acceleration of the aircraft about an axis, a yaw rate of the aircraft, or a roll rate of the aircraft.
In some embodiments, the fifth module normalizes the stable approach value and the turbulence factor. In some embodiments, the fifth module adds the stable approach value and the turbulence factor or multiplies the stable approach value and the turbulence factor.
In some embodiments, the aircraft warning includes a go-around instruction, tailstrike warning, a hard landing warning, a long landing warning, or a bounce landing warning.
In one embodiment, a warning method for an aircraft includes receiving multiple first parameters indicative of an aircraft's flight path, calculating a stable approach value based on the multiple first parameters, receiving multiple second parameters indicative of the aircraft's turbulence, calculating a turbulence factor based on the multiple second parameters, calculating a safe landing value based on the stable approach value and the turbulence factor, comparing the safe landing value to a threshold value, and providing an aircraft warning when the safe landing value fails to meet the threshold value.
In some embodiments, the multiple first parameters include the aircraft's vertical speed and the aircraft's height above the ground. In some embodiments, the multiple second parameters include the aircraft's pitch rate and the aircraft's vertical acceleration rate.
In one embodiment, a warning method for an aircraft includes receiving a stable approach value, receiving a parameter indicative of the aircraft's turbulence, calculating a turbulence factor based on the parameter, calculating a safe landing value based on the stable approach value and the turbulence factor, comparing the safe landing value to a threshold value, and providing an aircraft warning when the safe landing value fails to meet the threshold value. In some embodiments, the stable approach value is a glide slope signal. In some embodiments, the turbulence factor is a glide slope deviation. In some embodiments, the safe landing value is substituted for a stable approach value in a bus (e.g., an ARINC bus) before an error is detected. Exemplary systems and methods of substituting signals in a bus are disclosed in U.S. patent application Ser. No. 14/450,165, the content of which is incorporated herein in its entirety.
In the following description of embodiments, reference is made to the accompanying drawings which form a part hereof, and in which it is shown by way of illustration specific embodiments in which the claimed subject matter may be practiced. It is to be understood that other embodiments may be utilized and structural changes may be made without departing from the scope of the claimed subject matter.
In some embodiments, an aircraft's turbulent environment is monitored and warnings or instructions are given to the aircraft's crew based on the monitored turbulent environment. Advantageously, this may reduce dangerous landing conditions such as tailstrikes, hard landings, long landings, and bounced landings.
Thus, the effect of turbulence distracts the crew from the already complicated approach procedure, thereby reducing performance margin and increasing the risk of tailstrikes, hard landings, long landings, bounced landings, and other accidents. However, because the crew in
In some embodiments, a safe landing value is calculated based on a stable approach value and a turbulence factor.
Method 200 includes receiving a first parameter indicative of an aircraft's flight path 202. In some embodiments, receiving a first parameter comprises receiving multiple first parameters. In some embodiments, the first parameter includes the aircraft's vertical speed and the aircraft's height above the ground.
Method 200 includes calculating a stable approach value based on the first parameter 204. Traditionally, the stable approach value may be compared to a threshold. For example, a measured vertical air speed may be compared to a vertical speed limit. In other traditional examples, deviations of angle of attack and/or airspeed from a nominal value, or deviations from the glide slope of an instrument landing system, are used.
Method 200 includes receiving a second parameter indicative of the aircraft's turbulence 206. Advantageously, this may represent the actual turbulent environment experienced by the aircraft, rather than estimating a turbulent environment based on a radar-based turbulent detection. The actual turbulent environment can give a direct measure of the impact on performance margin and provide improved guidance for warnings and instructions.
In some embodiments, receiving a second parameter comprises receiving multiple second parameters. In some embodiments, the second parameter includes the aircraft's pitch rate and the aircraft's vertical acceleration rate. In some embodiments, the aircraft's pitch rate includes a frequency of a pitch's oscillation, such as the number of pitch “maximums” during a certain time period, for example. In some embodiments, the aircraft's vertical acceleration rate includes a maximum vertical acceleration over a period of time, such as the maximum vertical acceleration over one second, for example.
In some embodiments, the second parameter includes a frequency of a vertical acceleration rate of the aircraft. In some embodiments, the second parameter includes an acceleration of the aircraft about an axis or a rate of change of an acceleration of the aircraft about an axis. In some embodiments, the second parameter includes a yaw rate or a roll rate.
Method 200 includes calculating a turbulence factor based on the second parameter 208. In some embodiments, the turbulence factor is calculated using TF=abs({dot over (a)}v)+k{dot over (θ)} abs({dot over (θ)}) where:
TF is the turbulence factor,
is the vertical acceleration rate gain,
{dot over (a)}v is the vertical acceleration rate,
k{dot over (θ)} is the pitch rate gain, and
{dot over (θ)} is the pitch rate.
In some embodiments, the vertical acceleration rate is a measured value or a filtered or moving average. In some embodiments, the pitch rate is a measured value or a filtered or moving average.
Method 200 includes calculating a safe landing value based on the stable approach value and the turbulence factor 210. In some embodiments, calculating the safe landing value includes normalizing the stable approach value and the turbulence factor. In some embodiments, normalizing the stable approach value and the turbulence factor comprises adjusting one value so that it has the same dimensions as the other value or adjusting both values so that they have the same dimensions.
In some embodiments, calculating the safe landing value includes adding the stable approach value and the turbulence factor or multiplying the stable approach value and the turbulence factor. In some embodiments, the safe landing value is calculated using SLV=Vs+TF or SLV=TF×Vs, where:
SLV is the safe landing value,
TF Is the turbulence factor, and
Vs is the sink rate with positive being in the descending direction.
In some embodiments, additional flight-specific parameters may be incorporated into the calculation of the safe landing value. For example, a safe landing value may also be based on the type of airplane, the experience of the crew, weather conditions, a destination airport, the weight of the airplane and cargo, or flap/slat position of the airplane.
In some embodiments, method 200 includes applying a lag or moving averages (e.g., a moving average is the average value of a parameter over a predetermined time period) to factor out unsteady turbulence factors. In some embodiments, a first order damping or a low pass filter is applied to the parameter to smooth out unsteady, high frequency variations. In some embodiments, the damping or low pass filter is calculated using
where:
x(t) is the response of the system,
k is the gain of the system,
s is the laplace variable,
t is the time constant of the system, and
u(t) is the input to the system.
Method 200 includes comparing the safe landing value to a threshold value 212. In some embodiments, the threshold value is a static threshold value. In some embodiments, the threshold value changes as a function of height above touchdown. In some embodiments, the threshold is based on previous flight data in order to determine acceptable and unacceptable values.
Method 200 includes providing an aircraft warning when the safe landing value fails to meet the threshold value 214. In some embodiments, the aircraft warning includes a go-around instruction, tailstrike warning, a hard landing warning, a long landing warning, or a bounce landing warning.
In some embodiments, the turbulence factor calculated above in step 208 is used in a non-landing situation. During cruising, for example, a turbulence warning alerts the flight crew to decelerate to the turbulence penetration speed. Like the approach case discussed above, a similar algorithm detects turbulence during cruise using aircraft speeds, accelerations and their rates, and attitude rates and then applies a turbulence factor to provide a warning to the crew or provide flight instructions.
Aircraft warning system 300 includes a flight path module 302 that receives a first parameter indicative of the aircraft's flight path. In some embodiments, flight path module 302 receives multiple first parameters indicative of the aircraft's flight path. In some embodiments, the first parameter includes the aircraft's vertical speed and the aircraft's height above the ground. In some embodiments, the first parameter is received from sensors on the aircraft, such as an altimeter, an airspeed indicator, a seismometer, an accelerometer, and a gyroscope, for example.
Aircraft warning system 300 includes a stable approach value module 304 that calculates a stable approach value based on the first parameter.
Aircraft warning system 300 includes an aircraft turbulence module 306 that receives a second parameter indicative of the aircraft's turbulence. In some embodiments, aircraft turbulence module 306 receives multiple second parameters indicative of the aircraft's turbulence.
In some embodiments, the second parameter includes the aircraft's pitch rate and the aircraft's vertical acceleration rate. In some embodiments, the aircraft's pitch rate includes a frequency of a pitch's oscillation. In some embodiments, the aircraft's vertical acceleration rate includes a maximum vertical acceleration over a period of time. In some embodiments, the second parameter is received from sensors on the aircraft, such as an altimeter, an airspeed indicator, a seismometer, an accelerometer, and a gyroscope, for example.
In some embodiments, the second parameter includes a frequency of a vertical acceleration rate of the aircraft. In some embodiments, the second parameter includes an acceleration of the aircraft about an axis or a rate of change of an acceleration of the aircraft about an axis.
Aircraft warning system 300 includes a turbulence factor module 308 that calculates a turbulence factor based on the second parameter.
Aircraft warning system 300 includes a safe landing value module 310 that calculates a safe landing value based on the stable approach value and the turbulence factor. In some embodiments, the safe landing value module normalizes the stable approach value and the turbulence factor. In some embodiments, normalizing the stable approach value and the turbulence factor comprises adjusting one value so that it has the same dimensions as the other value or adjusting both values so that they have the same dimensions.
In some embodiments, the safe landing value module adds the stable approach value and the turbulence factor or multiplies the stable approach value and the turbulence factor.
Aircraft warning system 300 includes a comparison module 312 that compares the safe landing value to a threshold value.
Aircraft warning system 300 includes an aircraft warning module 314 that provides an aircraft warning when the safe landing value fails to meet the threshold value. In some embodiments, the aircraft warning includes a go-around instruction, tailstrike warning, a hard landing warning, a long landing warning, or a bounce landing warning.
In one embodiment, a warning method for an aircraft includes receiving a stable approach value, receiving a parameter indicative of the aircraft's turbulence, calculating a turbulence factor based on the parameter, calculating a safe landing value based on the stable approach value and the turbulence factor, comparing the safe landing value to a threshold value, and providing an aircraft warning when the safe landing value fails to meet the threshold value. In some embodiments, the stable approach value is a glide slope signal. In some embodiments, the turbulence factor is a glide slope deviation. In some embodiments, the safe landing value is substituted for a stable approach value in a bus (e.g., an ARINC bus) before an error is detected. Exemplary systems and methods of substituting signals in a bus are disclosed in U.S. patent application Ser. No. 14/450,165, the content of which is incorporated herein in its entirety.
The term “module” as used herein, refers to software, firmware, hardware, and any combination of these elements for performing the associated functions described herein. Additionally, for purpose of discussion, the various modules are described as discrete modules; however, as would be apparent to one of ordinary skill in the art, two or more modules may be combined to form a single module that performs the associated functions.
One skilled in the relevant art will recognize that many possible modifications and combinations of the disclosed embodiments can be used, while still employing the same basic underlying mechanisms and methodologies. The foregoing description, for purposes of explanation, has been written with references to specific embodiments. However, the illustrative discussions above are not intended to be exhaustive or to limit the disclosure to the precise forms disclosed. Many modifications and variations can be possible in view of the above teachings. The embodiments were chosen and described to explain the principles of the disclosure and their practical applications, and to enable others skilled in the art to best utilize the disclosure and various embodiments with various modifications as suited to the particular use contemplated.
Further, while this specification contains many specifics, these should not be construed as limitations on the scope of what is being claimed or of what may be claimed, but rather as descriptions of features specific to particular embodiments. Certain features that are described in this specification in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination. Moreover, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a subcombination or variation of a subcombination.
This application is a continuation of U.S. patent application Ser. No. 15/143,123 filed Apr. 29, 2016, which is a continuation of Ser. No. 15/056,989 filed Feb. 29, 2016, which claims the benefit of U.S. Provisional Application No. 62/190,177 filed Jul. 8, 2015. The disclosures of which are incorporated herein in their entireties.
Number | Name | Date | Kind |
---|---|---|---|
3291421 | Krame et al. | Dec 1966 | A |
3665465 | Miller | May 1972 | A |
3691356 | Miller | Sep 1972 | A |
3712122 | Harris et al. | Jan 1973 | A |
3805033 | Manke et al. | Apr 1974 | A |
3934221 | Bateman et al. | Jan 1976 | A |
3936797 | Andresen, Jr. | Feb 1976 | A |
3994455 | Simpson | Nov 1976 | A |
4092716 | Berg et al. | May 1978 | A |
4319218 | Bateman | Mar 1982 | A |
4373184 | Lambregts | Feb 1983 | A |
4431994 | Gemin | Feb 1984 | A |
4536843 | Lambregts | Aug 1985 | A |
4551723 | Paterson | Nov 1985 | A |
4675823 | Noland | Jun 1987 | A |
4764872 | Miller | Sep 1988 | A |
5020747 | Orgun et al. | Jun 1991 | A |
5031102 | Robbins et al. | Jul 1991 | A |
5038141 | Grove | Aug 1991 | A |
5187478 | Grove | Feb 1993 | A |
5220322 | Bateman et al. | Jun 1993 | A |
5402116 | Ashley | Mar 1995 | A |
5406487 | Tanis | Apr 1995 | A |
5781126 | Paterson et al. | Jul 1998 | A |
5901927 | Ho | May 1999 | A |
6121899 | Theriault | Sep 2000 | A |
6186447 | Virdee | Feb 2001 | B1 |
6216064 | Johnson et al. | Apr 2001 | B1 |
6422517 | DeWitt et al. | Jul 2002 | B1 |
6462703 | Hedrick | Oct 2002 | B2 |
6507289 | Johnson et al. | Jan 2003 | B1 |
6711479 | Staggs | Mar 2004 | B1 |
6761336 | DeWitt et al. | Jul 2004 | B2 |
6845304 | Young | Jan 2005 | B1 |
6940427 | Bateman | Sep 2005 | B2 |
6999023 | Block | Feb 2006 | B2 |
7088264 | Riley | Aug 2006 | B2 |
7725220 | Petrich et al. | May 2010 | B2 |
8027756 | Davis et al. | Sep 2011 | B2 |
8126600 | Conner et al. | Feb 2012 | B2 |
8175763 | Yamane et al. | May 2012 | B2 |
8321071 | Klooster | Nov 2012 | B2 |
8478458 | Faurie et al. | Jul 2013 | B2 |
8494693 | Murphy | Jul 2013 | B2 |
8630756 | Fleiger-Holmes et al. | Jan 2014 | B2 |
8660722 | Dumoulin et al. | Feb 2014 | B2 |
8723695 | Bourret et al. | May 2014 | B2 |
8788128 | McCusker | Jul 2014 | B1 |
8831799 | Levine et al. | Sep 2014 | B1 |
8903572 | Hagelin | Dec 2014 | B1 |
20010052562 | Ishihara et al. | Dec 2001 | A1 |
20020030607 | Conner et al. | Mar 2002 | A1 |
20020075171 | Kuntman et al. | Jun 2002 | A1 |
20020077731 | Hilb | Jun 2002 | A1 |
20030016145 | Bateman | Jan 2003 | A1 |
20030093187 | Walker | May 2003 | A1 |
20030206119 | Riley | Nov 2003 | A1 |
20040057177 | Glahn | Mar 2004 | A1 |
20040070521 | Greene | Apr 2004 | A1 |
20060041345 | Metcalf | Feb 2006 | A1 |
20060052912 | Meunier | Mar 2006 | A1 |
20060195235 | Ishihara | Aug 2006 | A1 |
20060220921 | Foucart | Oct 2006 | A1 |
20060271249 | Testrake et al. | Nov 2006 | A1 |
20070239326 | Johnson et al. | Oct 2007 | A1 |
20080243316 | Sacle et al. | Oct 2008 | A1 |
20090138144 | Flannigan et al. | May 2009 | A1 |
20090207047 | Ross, III | Aug 2009 | A1 |
20090262008 | Thomas et al. | Oct 2009 | A1 |
20100090867 | Christophe | Apr 2010 | A1 |
20110029158 | Klooster | Feb 2011 | A1 |
20110077858 | Coulmeau | Mar 2011 | A1 |
20110098967 | Khial | Apr 2011 | A1 |
20110199253 | Delga et al. | Aug 2011 | A1 |
20110251740 | Gomez Ledesma | Oct 2011 | A1 |
20110276217 | Sim | Nov 2011 | A1 |
20120053760 | Burnside et al. | Mar 2012 | A1 |
20120056760 | Bourret et al. | Mar 2012 | A1 |
20120095625 | Ishihara et al. | Apr 2012 | A1 |
20120191273 | Jacobs et al. | Jul 2012 | A1 |
20120265374 | Yochum | Oct 2012 | A1 |
20120316706 | Guedes | Dec 2012 | A1 |
20130030614 | Ding | Jan 2013 | A1 |
20130245982 | Buchanan et al. | Sep 2013 | A1 |
20130274964 | Jesse et al. | Oct 2013 | A1 |
20140074326 | Pereira | Mar 2014 | A1 |
20140090471 | Hsu | Apr 2014 | A1 |
20140129058 | Elahi | May 2014 | A1 |
20140172202 | Greene | Jun 2014 | A1 |
20140229056 | Catt | Aug 2014 | A1 |
20150120098 | Catalfamo et al. | Apr 2015 | A1 |
20150120099 | Herbert et al. | Apr 2015 | A1 |
20150123821 | Greene | May 2015 | A1 |
Number | Date | Country |
---|---|---|
1 843 127 | Oct 2007 | EP |
2 892 503 | Apr 2007 | FR |
2 956 491 | Aug 2011 | FR |
2 964 466 | Mar 2012 | FR |
2 300 167 | Oct 1996 | GB |
Entry |
---|
Cashman et al., “Operational Use of Angle of Attack on Modern Commercial Jet Airplanes,” Dec. 31, 2012, 7 pages. |
Supplementary European Search Report for EP 13897022.3, dated Jun. 21, 2017, 3 pages. |
International Search Report and Written Opinion for PCT/US2013/68580, dated Jul. 11, 2014, 14 pages. |
Jeff Scott, “Angle of Attack and Pitch Angle,” Feb. 29, 2004, accessed May 24, 2016. |
<http://www.aerospaceweb.org/question/aerodynamics/q0165.shtml>. |
Number | Date | Country | |
---|---|---|---|
20170305573 A1 | Oct 2017 | US |
Number | Date | Country | |
---|---|---|---|
62190177 | Jul 2015 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 15143123 | Apr 2016 | US |
Child | 15647167 | US | |
Parent | 15056989 | Feb 2016 | US |
Child | 15143123 | US |