US20050261813A1 - Method and apparatus for predicting runway overrun - Google Patents
Method and apparatus for predicting runway overrun Download PDFInfo
- Publication number
- US20050261813A1 US20050261813A1 US11/192,267 US19226705A US2005261813A1 US 20050261813 A1 US20050261813 A1 US 20050261813A1 US 19226705 A US19226705 A US 19226705A US 2005261813 A1 US2005261813 A1 US 2005261813A1
- Authority
- US
- United States
- Prior art keywords
- aircraft
- runway
- distance
- landing
- monitor
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G08—SIGNALLING
- G08G—TRAFFIC CONTROL SYSTEMS
- G08G5/00—Traffic control systems for aircraft, e.g. air-traffic control [ATC]
- G08G5/0073—Surveillance aids
- G08G5/0086—Surveillance aids for monitoring terrain
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B64—AIRCRAFT; AVIATION; COSMONAUTICS
- B64C—AEROPLANES; HELICOPTERS
- B64C25/00—Alighting gear
- B64C25/32—Alighting gear characterised by elements which contact the ground or similar surface
- B64C25/42—Arrangement or adaptation of brakes
- B64C25/426—Braking devices providing an automatic sequence of braking
-
- G—PHYSICS
- G01—MEASURING; TESTING
- G01C—MEASURING DISTANCES, LEVELS OR BEARINGS; SURVEYING; NAVIGATION; GYROSCOPIC INSTRUMENTS; PHOTOGRAMMETRY OR VIDEOGRAMMETRY
- G01C23/00—Combined instruments indicating more than one navigational value, e.g. for aircraft; Combined measuring devices for measuring two or more variables of movement, e.g. distance, speed or acceleration
- G01C23/005—Flight directors
-
- G—PHYSICS
- G08—SIGNALLING
- G08G—TRAFFIC CONTROL SYSTEMS
- G08G5/00—Traffic control systems for aircraft, e.g. air-traffic control [ATC]
- G08G5/02—Automatic approach or landing aids, i.e. systems in which flight data of incoming planes are processed to provide landing data
- G08G5/025—Navigation or guidance aids
Definitions
- the invention relates to aircraft safety equipment and more particularly to an apparatus and method for increasing flight crew situational awareness during landing.
- Landing is one of the most demanding tasks in flying. During the landing process, the aircraft must be brought to a safe and complete stop. To perform the landing properly, the aircraft must approach the runway within certain attitude, track, speed, and rate of descent limits. An approach outside of these limits can result in a “hard” landing, overrunning the runway end, or otherwise contacting the runway surface in an uncontrolled manner. Any one of these events has the potential to cause severe damage to the aircraft and may additionally result in passenger injuries or fatalities.
- Pilots Landing too fast and landing too far down a runway may contribute to runway overrun accidents. Pilots are trained to monitor these conditions during the approach, and to initiate a go-around maneuver if a safe landing is not assured. The effectiveness of pilot training depends, however, on the skill and judgment of the pilot in recognizing a possible runway overrun condition, and in executing the appropriate response. Pilots with varying levels of skill are therefore likely to respond differently to the same scenario.
- the pilot's vision is the sole data source for estimating runway position information. Even with existing high standards for pilot eyesight, some variation in acuity will occur as the pilot's physical condition, alertness, and state of rest vary. If the pilot's vision is the sole source of data used to determine whether a go-around or aborted takeoff is necessary, then variations in visual acuity, distractions or poor visibility may reduce the quality of the data used in the pilot's decision. In addition, a pilot may fly for years without experiencing a runway overrun, and the pilot may be slow to recognize a problem during landing.
- Aircraft safety can be improved by mitigating the effects of differing pilot skill levels and situational awareness during the landing phase of flight.
- a method of providing situational awareness during landing of an aircraft comprises determining a critical point on a runway, the critical point indicating a point at which if the aircraft lands beyond the critical point, there is a likelihood of the aircraft overrunning the runway. If a path projection from the aircraft intersects the runway beyond the critical point, an alert is provided.
- a method of providing timely alert messages in an aircraft during landing comprises determining message data regarding the aircraft's status during a landing phase, determining aircraft speed, adjusting a message based on the message data according to aircraft speed, and announcing the adjusted message.
- a method for monitoring for runway overrun when an aircraft is landing on a runway comprises determining an aircraft's position on the runway after the aircraft has touched down, determining the aircraft's groundspeed, determining the aircraft's deceleration, calculating a runway distance remaining before the aircraft on the runway, calculating a distance required to reach a desired speed at said deceleration, and generating an alert if the required distance is greater than the remaining runway distance.
- FIG. 1 is a schematic side elevational view of a runway landing environment.
- FIG. 2 is a block diagram of a first embodiment of a runway overrun monitor.
- FIG. 3 is a top plan view of a portion of the runway landing environment illustrated in FIG. 1 .
- FIG. 4 is a schematic side elevational view of a portion of the runway landing environment illustrated in FIG. 1 , including several descent slopes.
- FIG. 5 illustrates a method of providing accurately timed alert messages.
- FIG. 6 illustrates a method of providing situational awareness after touchdown.
- a runway overrun monitor provides an aircraft crew with a source of reliable and accurate data during the landing phase. Available information includes, for example, messages notifying the crew that under current conditions, the aircraft will not have enough runway to land safely. Information can also include alerts that the aircraft will exceed a maximum touchdown speed, or that maximum tailwind or crosswind limits will be exceeded. The above alerts can be provided automatically by the runway overrun monitor.
- the runway overrun monitor may be configured to omit unsolicited, routine information.
- the pilot or crew may, however, solicit information such as, for example, tailwind and crosswind component values, runway identification, runway remaining for landing, and speed over the ground.
- FIG. 1 illustrates a runway environment 100 .
- the runway environment 100 is illustrated as including a runway 110 , a runway start 114 , a touchdown zone (TDZ) 115 , a critical point 116 , an aircraft path projection 125 , a touchdown aim point 130 , and a first checkpoint 150 .
- the touchdown zone 115 is the length of the runway 110 where aircraft customarily touch down on landing.
- a common TDZ length is 75 feet, beginning at 500 feet past the runway start 114 . TDZ lengths and locations on runways vary, however.
- an aircraft 121 descends along the path projection 125 to touch down at the touchdown aim point 130 .
- the touchdown aim point 130 is the location of the intersection of the path projection 125 with the runway 110 .
- the pilot uses the aircraft brakes and reverse engine thrust, if available, to slow the aircraft 121 to a safe speed.
- the touchdown aim point may vary along the runway 110 .
- the touchdown aim point 130 is a predictor of the position along the runway 110 at which the aircraft 121 will actually touch down.
- the distance between the actual touchdown point and the runway end 120 is the available runway for slowing the aircraft 121 before it overruns the runway 110 .
- runway remaining This distance between the predictor touchdown point 130 and the runway 120 may be referred to as “runway remaining” as the aircraft 121 approaches touchdown.
- calculations for runway distance remaining may be adjusted according to landing flare.
- a runway overrun can be generally defined as a situation in which the aircraft 121 proceeds past the runway end 120 at a groundspeed too high for safely attempting to turn the aircraft 121 onto a taxiway.
- the path projection 125 of the aircraft 121 is monitored to determine whether the touchdown aim point 130 is either in front of or beyond the critical point 116 .
- the critical point 116 may be defined as indicating a point at which if the aircraft lands beyond the critical point 116 , there is a likelihood of the aircraft overrunning the runway 110 . Alerts are provided if the touchdown aim point 130 is beyond the critical point 116 .
- FIG. 2 illustrates a runway overrun monitor 200 capable of performing the alert functions described above.
- the runway overrun monitor 200 functions to apprise the pilot or crew members of the status of the aircraft carrying the monitor 200 .
- the runway overrun monitor 200 comprises a data processor 201 coupled to a source 202 of company or manufacturer supplied runway data, a source 204 of aircraft performance data, a source 206 of aircraft position data, and a source 208 of avionics data.
- the data processor 201 may also be coupled to alert devices such as an audio indicator 220 and a visual indicator 222 .
- the audio indicator 220 can be, for example, a speaker, or a source of audio input coupled to headphones worn by a pilot.
- the visual indicator 222 can be, for example, one or more colored lights on a panel, or a display screen such as an LCD or CRT monitor.
- a weight on wheels (WOW) sensor 210 may be coupled to the processor 201 to provide an indication as to when the aircraft is airborne.
- the data processor 201 may be coupled to an input device 224 .
- the input device 224 may be used to solicit information from the monitor 200 .
- the input device 224 may also be used at any time to request a data update from the runway overrun monitor 200 .
- the input device 224 may include, for example, a “request update” button, or one or more keys designated for this purpose. Allowing the pilot or other operator to request specific updates reduces unnecessary background noise in the cockpit, while ensuring that the pilot receives alert information without looking inside the cockpit and away from the runway.
- the monitor 200 can include a single button that can be used to request information, and to mute further alerts.
- the input device 224 can therefore be used to acknowledge an alert. In a preferred embodiment, alerts are given only once, however, and acknowledgement of alerts is not necessary.
- the runway data from the source 202 describes the state of the runway that the aircraft carrying the runway overrun monitor 200 is preparing to land on or take off from.
- the runway data may include, for example, the length, and gradient of the intended landing runway.
- the runway data may also include a map of the airport, which includes data defining the runways at the airport, including the runway identifications.
- the runway data can be used to compare aircraft position with the distance to any of the runway boundaries, including the aircraft's height above ground in relation to a runway environment.
- Runway data can be taken from, for example, an airport mapping database (AMDB) including a digital description of the airport geography, such as the location of runways and a description of the altitude of the runways.
- AMDB airport mapping database
- the aircraft performance data from the source 204 may include, for example, company policy limits with respect to landing and stopping distance characteristics of an aircraft as a function of, for example, aircraft weight, with corrections based on, for example, wind direction, runway slope, runway surface condition, atmospheric altitude and outside temperature.
- the aircraft performance data may also include a list of manufacturer or company regulations defining various aspects of flight. For example, a company regulation may define maximum permissible airspeeds, groundspeeds, descent angles, minimum runway, required gear and flap configurations, etc., for different stages of landing.
- the aircraft operator (the chief pilot, for example) can input a general required landing distance for the aircraft.
- the general required landing distance may be altered by the processor 201 according to factors such as, for example, the presence of a tailwind component, altitude, runway gradient, and air temperature. Additional aircraft performance data is therefore not required.
- the aircraft position data from the source 206 may include, for example, aircraft altitude, latitude, longitude, track over the ground, descent slope and groundspeed.
- the position data can be used to calculate the aircraft's vertical and horizontal acceleration.
- the monitor 200 may be coupled to one or more of an inertial navigation system, an altimeter, a global positioning system receiver, and an accelerometer to obtain aircraft position data.
- Position data can be differentiated with respect to time to obtain velocity, including groundspeed, and acceleration data.
- the position data can be in the form of, for example, longitude, latitude and altitude. Velocity may also be provided directly from the global positioning system, or from the inertial navigation system.
- the avionics (more specifically, air data and heading) data from the source 208 can include, for example, data such as pressure, airspeed, true airspeed and wind vector (wind vector may be estimated using the true airspeed, groundspeed, track and heading) and direction, which may be provided as tailwind/headwind components, may also be supplied to the monitor 200 .
- the monitor 200 may use this data to determine, for example, tailwind and crosswind components.
- FIGS. 1, 3 and 4 illustrate an embodiment of a method for providing situational awareness during landing.
- FIG. 1 the aircraft 121 is illustrated as approaching the runway 110 .
- the point 150 illustrates a first checkpoint, and can serve as a starting point at which the runway overrun monitor 200 begins monitoring the aircraft's situation during landing. As an alternative, monitoring may begin when the visual path point 125 intersects with the touch down zone 115 .
- FIG. 3 is a top plan view of the runway 110 .
- an aircraft follows a descent slope during landing.
- the descent slope is typically defined as some optimal angle of descent for the aircraft.
- descent slopes may be inclined at an angle in the range of about 3-4°.
- Maximum (i.e., steepest) descent slope values for the aircraft 121 may be provided by, for example, the aircraft operator, such as the owning corporation of the aircraft 121 .
- an aircraft maintains a constant angle of descent as it approaches the runway.
- the path projection 125 illustrated in FIGS. 1, 3 and 4 is preferably inclined at the same angle as a preferred descent slope angle of descent for the aircraft 121 .
- the path projection 125 is at an angle ⁇ to horizontal.
- the path projection 125 extends from the aircraft 121 and intersects level (i.e., zero gradient) ground at the angle ⁇ . In an ideal landing, the touchdown aim point 130 would stay at the same location on the runway 110 throughout the landing procedure.
- the path projection 125 is preferably extended at a constant angle ⁇ during the landing operation.
- the path projection 125 is monitored in order to determine whether the intersection of the path projection 125 with the runway 110 is before or beyond the critical point 116 .
- the intersection point is labeled as the touchdown aim point 130 . It is significant when the touchdown aim point 130 is beyond the critical point 116 because if the aircraft 121 continues on that path projection 125 without adjustment, the aircraft 121 may not be able to stop safely before the runway end 120 .
- Monitoring may begin, for example, at the point 150 .
- the point 150 can correspond to the location of the outer marker for a runway. Such a point can be at a distance of, for example, about 5 miles away from the runway 110 .
- Monitoring may also begin once the path projection 125 intersects with the TDZ 115 , and alerts may be provided to the pilot or crew of the aircraft 121 when certain conditions are met.
- FIG. 4 is an isolated view of a portion of the runway 110 .
- Several descent slopes 125 1 , 125 2 , 125 3 and corresponding touchdown aim points 130 1 , 130 2 , 130 3 are illustrated, corresponding to times t 1 , t 2 , t 3 , respectively.
- the aircraft 121 will land in front of the critical point 116 .
- the path projection 125 2 has moved towards the critical point 116 , but remains in front of the critical point 116 .
- the path projection 125 3 intersects the runway at a touchdown aim point 130 3 beyond the critical point 116 . At this time, if the aircraft 121 continues on its current path projection 125 3 , there is a chance that the aircraft 121 may not have enough runway to land safely.
- the monitor 200 may issue an unsolicited alert.
- the alert may have the form of an audible message, such as a message stating the amount of runway the aircraft 121 will have available, after touchdown, to stop the aircraft 121 .
- the alert message can have the form “RUNWAY REMAINING 4000 FEET.”
- the alert message should be short and should contain minimal information so that the pilot is not unnecessarily distracted.
- the monitor 200 may periodically determine whether the touchdown aim point 130 passes over the critical point 116 . In general, the monitor 200 issues an alert the first time the touchdown aim point 130 passes over the critical point 116 . It is preferable that further alerts are not provided for each updating period, because the pilot is already made aware of the potentially dangerous situation. However, if after an alert is issued, and the touchdown aim point 130 again moves in front of the critical point 116 (i.e., runway overrun no longer likely), further alerts may be provided if the touchdown aim point 130 once again moves beyond the critical point 116 . The monitor 200 may continue to monitor for runway distance remaining until touchdown.
- the monitor 200 may monitor other aircraft conditions. For example, referring to FIG. 1 , when the aircraft reaches point 150 , the monitor 200 can determine whether the aircraft 121 is in a desired configuration for landing.
- the required configuration can be defined according to, for example, company regulations, such as would govern a commercial carrier.
- the required configuration may also be defined by standards recommended by the aircraft manufacturer, or by input by the pilot.
- a configuration check can evaluate the following: whether aircraft landing gear is down; whether a required flap position is detected; whether a maximum tailwind component is exceeded; whether a maximum crosswind component is exceeded; whether the aircraft is above a maximum altitude; whether the aircraft is exceeding a maximum airspeed; and whether the aircraft is exceeding a maximum groundspeed.
- the monitor 200 may monitor for a touchdown aim point 130 that passes over the critical point 116 .
- Each of the above factors or conditions can be selectively monitored and reported, depending on the usefulness of the information to the pilot. In general, the monitor 200 will not provide unsolicited alerts if there are no potential problems detected for the landing. Exemplary reporting options are discussed below.
- the configuration check can be termed as a check of whether the aircraft is “in the slot.” “In the slot” is a term indicating that an aircraft is operating within prescribed airspeed, gear position, flap position, power setting, and altitude parameters. A check of whether an aircraft is in the slot is usually made between the runway outer marker and some distance from the runway. Referring to FIG. 3 , an aircraft in the slot can also indicate that the aircraft is within an angular range ⁇ about the runway 110 centerline 140 . In general, when an aircraft is outside of the angular range ⁇ , the pilot is not warned. A pilot in this situation will likely be aware of the aircraft's location outside of the angular range ⁇ .
- the final approach course is an imaginary line extending back along a runway centerline from the approach end of the runway 110 .
- the aircraft 121 can be considered to “track” the final approach course when the aircraft 121 is within a certain azimuth range ⁇ of the runway centerline 140 (see FIG. 3 ).
- the azimuth range ⁇ may be, for example, +/ ⁇ five degrees.
- the final approach course may extend, for example, five miles before the runway 110 out to point 150 .
- a specified lateral offset l 1 from the runway centerline 140 may also be used to define the final approach course.
- the offset l 1 can be, for example, about 250 feet.
- the aircraft 121 altitude may be too high to obtain tailwind and crosswind component values that are useful to evaluate the feasibility of a landing. Tailwind and crosswind component checks may therefore be delayed until the aircraft 121 is at a lower altitude.
- Alert messages should be as brief and informative as possible. For example, if landing gear is not down in the configuration check, a message “NOT IN LANDING CONFIGURATION, GEAR” may be provided. Similarly, “NOT IN LANDING CONFIGURATION, FLAPS” can indicate flaps in the wrong position, or “NOT IN LANDING CONFIGURATION, AIRSPEED,” may indicate an airspeed outside of recommended parameters, and “NOT IN LANDING CONDITION, ALTITUDE,” can indicate an altitude outside of recommended parameters.
- the monitor 200 may enable monitoring of additional factors affecting the landing.
- point 160 may correspond to a point where the aircraft 121 altitude is lower, in the range of, for example, 500 feet or less.
- tailwind and crosswind values may be more accurately determined as they affect landing on the runway 110 .
- the monitor 200 may issue an alert informing the pilot of the condition. Monitoring for excessive tailwind or crosswind values may continue until the aircraft 121 is at a height of about 100 feet. At 100 feet, alerts may be addressed solely to whether sufficient runway remains for landing. In general, a tailwind or crosswind alert is given only once, as repetition may distract the pilot.
- Crosswind alerts can indicate the crosswind component and direction.
- a crosswind alert can have the form “RIGHT CROSSWIND 20 KNOTS.”
- a tailwind announcement can have the form “TAILWIND 10 KNOTS.”
- crosswind and tailwind announcements may be delayed until the aircraft 121 is at a lower altitude.
- tailwind and crosswind alerts are issued after the aircraft 121 descends below 300 feet, and cease when the aircraft descends below 100 feet.
- the monitor 200 may monitor to determine whether the aircraft 121 will exceed a maximum touchdown speed or is currently exceeding a maximum airspeed. Monitoring for exceedance of maximum touchdown speed can begin at point 150 , for example. In one embodiment, alerting for exceedance of maximum touchdown speed begins when the aircraft 121 descends to an altitude of about 300 feet. Other altitudes are also appropriate.
- the threshold altitude value may be, for example, 100 feet. At this time, alerts relating to crosswind, tailwind, and groundspeed, etc., may be extraneous and may distract the pilot.
- the critical point 116 may be determined according to, for example, operator-recommended landing distances.
- the critical point 116 is determined as a function of runway length and runway distance required for the aircraft to land and stop safely. Required landing distance for an aircraft is dependent upon aircraft type, runway gradient, airport elevation, density altitude, established company parameters, and other factors determining the length of runway required for an aircraft to land safely. This information can be stored on computer-readable media, for example, and may be accessible by the monitor 200 .
- the monitor 200 can also adjust the critical point 116 according to prevailing conditions. For example, the presence of a tailwind increases the distance required for an aircraft to land, thereby moving the critical point to the left in FIG. 1 .
- the required landing distance may also be adjusted according to runway altitude, runway gradient, and air temperature.
- the monitor 200 may account for aircraft flare occurring just before touchdown.
- the monitor 200 can account for flare in at least two ways.
- a first way to account for flare is to add an expected flare distance to the landing distance, and increase landing distance accordingly. This method results in the critical point 116 being moved to the left in FIG. 1 .
- flare can be accounted for by virtually shifting the path projection 125 to the right in FIG. 1 by the expected flare distance.
- the information provided to the pilot should be simple and as easily understood as possible. Therefore, distances are preferably rounded off to hundreds, or thousands of feet. For example, during the time when the aircraft is about to touch down, measurements of runway remaining are preferably rounded off to the nearest thousand foot increment. There are at least two ways of implementing this feature. A first way is to round the runway remaining figure down, so the pilot has a conservative estimate of runway remaining. Another is to round up or down, this method being less preferred. Another method is to time the sounding of an alert message so the threshold hundred or thousand foot increment message is accurate when received by the pilot. A method of timing messages is discussed in detail below with reference to FIG. 5 .
- Safety margins can also be programmed into the runway overrun monitor 200 .
- the pilot or other operator can program the monitor 200 to consistently underestimate runway remaining figures by a selected percentage or by a selected distance.
- the pilot can end alerts from the monitor at any time. Alerts can be ended at the input 224 .
- the input 224 can act as a “mute” button by a single press of a button. The pilot may take this action if he no longer plans on landing.
- the monitor 200 can be reactivated when, for example, the aircraft 121 arrives at its next visual path point.
- the pilot or crew can also solicit information from the monitor 200 at any time.
- Solicited information can include any of the announcements discussed above.
- Solicited alerts can be requested, for example, at the input 224 .
- a single button can be used as a mute button as discussed above, and as a means for requesting unsolicited updates.
- the pilot can double-press a button on the input 224 to request a runway identification, the distance to the TDZ 115 , and ground speed.
- Such an announcement may have the form “RUNWAY TWO FOUR LEFT, NINE MILES TO TOUCHDOWN, 120 KNOTS OVER THE GROUND.”
- the pilot may again solicit information by a double-press of a button on the input 224 .
- This further information can include another runway identification, and groundspeed announcement.
- the relatively high speeds at which the aircraft 121 travels renders the timeliness of alert messages of high importance. For example, an aircraft traveling at 150 knots traverses 250 feet per second. Therefore, any time-offset between a time when the message is accurate and when the message is actually received by the pilot can result in the pilot receiving erroneous information.
- FIG. 5 illustrates a method of ensuring that accurate alert messages are provided to a pilot or other operator.
- the timing of alert messages is calculated so that the information is accurate when received by the pilot.
- an audible message is presented so that at the end of the message, the data conveyed in the message is accurate.
- the runway overrun monitor 200 disclosed in FIG. 2 can be programmed to announce messages in accordance with the method discussed below.
- message data is determined in step S 300 .
- the message data may correspond to any of the alert messages discussed above, and the message data determined in step S 300 may be determined accordingly.
- the message data can include a statement regarding runway remaining d RR .
- a speed of the aircraft 121 is determined.
- the speed can be, for example, the groundspeed or airspeed of the aircraft 121 .
- the groundspeed is determined.
- the message data and the aircraft speed can be determined concurrently, as shown in FIG. 5 , or serially (not shown).
- step S 304 the message is adjusted in order to compensate for factor such as the time required to announce the message, and for other factors.
- Step S 304 can be determined according to steps S 306 -S 314 below:
- step S 306 the time at which the message data is accurate is indexed as t 0 for the piece of information in the message.
- the time t 0 can be indexed to account for time involved in calculating or processing information.
- a time t 0 for a runway remaining message can be adjusted to account for the time required to read, for example, GPS instruments, and to calculate the runway remaining in the processor 201 .
- a time t M required to announce an alert message is determined.
- the message “RUNWAY REMAINING 4000 FEET” requires about 2.1 seconds to announce. If the pilot wants to hear the end of the message—i.e, the word “FEET”—when the aircraft has 4000 feet remaining, t M is equal to about 2.1 seconds. The time necessary to understand the massage and to react could also be considered when determining t M . If the pilot wants to hear the word “4000” when the aircraft has 4000 feet remaining, t M is equal to about 1.8 seconds. The time required t M can therefore be calculated according to operator preferences. A default setting can be included in the monitor 200 so that t M is calculated according to the time required to announce the entire message.
- a distance value d x is determined.
- the distance value d x represents the distance the aircraft 121 travels during the time t M required to announce an alert message.
- Equation 1 d x indicates a distance traveled in a direction aligned the runway 110 length while traveling with an x-component of velocity v x .
- a distance value d contained in the message is adjusted by subtracting dx. If the relevant distance is runway remaining, the message data can include a statement regarding runway remaining d RR .
- step 314 the message data is revised according to the adjusted runway remaining value d RRA .
- step 316 the alert is announced, including the adjusted runway remaining value d RRA .
- the method discussed above includes a feedback loop to address the situation in which the new distance d RR results in a new message length t M .
- Activation of the feedback loop may be subject to a threshold change message length ⁇ t M in message length t M .
- a standard time t M can be assigned for all messages of this type. This approximation may be made because an announcement of “RUNWAY REMAINING 4000 FEET” has approximately the same t M as “RUNWAY REMAINING 500 FEET.”
- the method for providing timely message data described above can be applied during both solicited and unsolicited announcements.
- the monitor 200 may also continue to provide situational awareness after the aircraft 121 has touched down. A method for providing situational awareness after touchdown is discussed below with reference to FIG. 6 .
- Closure rates between aircraft can be extremely fast. For example, at a closure rate of 1200 knots, an aircraft travels about one mile every ten seconds.
- traffic alert announcements may be generated, for example, when traffic is within about 30 seconds of a point of closest approach between an aircraft and the traffic. Therefore, the length of time required to make a position announcement is a significant part of the time available to avoid the oncoming traffic. Further, the last item announced in an announcement may be the range between an aircraft and the traffic, which changes very quickly.
- closure rate is especially high when the traffic is an aircraft and the two aircraft are on a collision course. It is therefore critical in collision alerting systems that closure ranges are as accurate as possible when presented to the pilot. Accuracy of range announcements is particularly important because the pilot's perception of threat is based on the range between the aircraft and the traffic. Therefore, the closer oncoming traffic is, the more relevant it is to the pilot.
- traffic alert announcements are announced based on a predictive algorithm, similar to the runway remaining announcements discussed above.
- the range announcements from the traffic alerting system should be made so that the announced range is accurate at the end of the announcement, or, concurrently with the announcement of the range.
- a collision alerting system adjusts a calculated range between an aircraft and traffic using a predictive algorithm.
- the range is predicted in the following manner:
- a detected traffic alerting range R d between the aircraft and traffic is determined.
- a time ta required to announce the range R d is determined.
- the closing rate CR between the aircraft and the traffic is then determined.
- the detected traffic alerting range R d is adjusted so that it will be accurate when the range is actually announced.
- the adjusted range R a is then announced.
- a standard time t a may be used, rather than calculating the actual time required to make an announcement.
- FIG. 6 illustrates a method for monitoring landing overrun after touchdown.
- step 610 it is determined if the aircraft 121 is landing. This step can be performed by the processor 201 recognizing, for example, a landing gear position, or, by recognizing a decrease in altitude. The pilot can also manually input an indication that the aircraft 121 is landing. If the aircraft 121 is not landing, the method returns to step 610 .
- step 620 the runway overrun device 200 monitors to determine whether the aircraft 121 has touched down. This determination is made according to the sensor inputs available to the processor 201 . For example, referring to FIG. 2 , the WOW sensor 210 output can be used to determine whether the aircraft 121 is airborne. Other devices and methods useful to determine whether the aircraft 121 is airborne include a comparison of the aircraft altitude with the altitude of the terrain at the aircraft's position. If the aircraft 121 has not yet touched down, the method returns to step 610 .
- the processor 201 calculates a required deceleration distance D REQ in step 630 .
- the required deceleration distance D REQ is the distance that will be traveled by the aircraft 121 in decelerating from the current groundspeed to a desired groundspeed.
- the desired groundspeed can be, for example, zero, or some speed that allows the aircraft 121 to turn at the runway end, such as a maximum taxi speed.
- the required deceleration distance is based on runway remaining, and is calculated using the values of groundspeed upon landing.
- the time to decelerate to the desired groundspeed may be determined using the deceleration rate.
- the deceleration rate can be measured directly, using, for example, an accelerometer, or calculated by determining the time derivative of the measured groundspeed.
- Aircraft deceleration can be determined as a deceleration function by extrapolating a curve from three or more position data points.
- step 635 the runway distance remaining D RW is determined.
- the remaining runway distance D RW is calculated by comparing the aircraft position with the data from the source 202 of runway data.
- step 640 it is determined whether the groundspeed of the aircraft is less than a maximum taxi speed. If the aircraft 121 is traveling at a speed below the maximum value, such as, for example, 10 knots, it is likely that the aircraft 121 is taxiing. If so, the method ends and the runway overrun monitor 200 ceases to monitor for a runway overrun.
- a maximum taxi speed such as, for example, 10 knots
- step 650 it is determined whether the required deceleration distance D REQ is greater than the remaining runway distance D RW . If not, the method returns to step 610 . If the required deceleration distance D REQ is greater than the remaining runway distance D RW , an alert is generated in step 660 .
- the warning can comprise, for example, an audio message broadcast by the audio indicator 220 , a visual message displayed by the visual indicator 222 , or a combination audio and visual message.
- the audio message can contain an indication of the calculated runway distance remaining D RW soon after touchdown and aircraft groundspeed.
- the visual indicator 222 can display similar information, including a running display of the remaining runway distance D RW , and, for example, a flashing warning indicator. Broadcasts of the remaining runway distance D RW and the aircraft's groundspeed can be updated periodically.
- the pilot receives a warning when the remaining runway distance D RW is insufficient to safely decelerate the aircraft 121 at the current deceleration function.
- the information from the runway overrun monitor allows the pilot to increase the rate of deceleration, such as by increasing the braking force, or by increasing reverse engine thrust, if available.
- the processor 201 can determine whether the aircraft 121 has exceeded a predetermined groundspeed in conjunction with having less than a specified remaining runway distance D RW . For example, if the aircraft 121 is traveling at a rate of 75 knots over ground, and 2,000 feet of runway remain, a warning can be generated stating the groundspeed and remaining runway.
- the trigger for generating an alert can be reference to a table specifying, for example, that at a remaining runway distance of 2,000 feet, a warning will be generated when aircraft groundspeed exceeds 70 knots.
- a table of remaining runway distance D RW versus groundspeed can be manually entered by an operator, or preprogrammed in the processor 201 .
- the above threshold values for remaining runway distance D RW and groundspeed can be adjusted according to airport and runway conditions and aircraft performance data.
- the required deceleration for a safe stop can be compared to the aircraft's actual deceleration. An alert may be provided if the aircraft's deceleration is not sufficient.
Landscapes
- Engineering & Computer Science (AREA)
- Radar, Positioning & Navigation (AREA)
- Remote Sensing (AREA)
- Aviation & Aerospace Engineering (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Mechanical Engineering (AREA)
- Traffic Control Systems (AREA)
Abstract
A critical point on a runway indicates a point at which an aircraft may experience a runway overrun if landing beyond the critical point. A path projection is extended from the aircraft at a descent slope angle to determine whether the aircraft will land beyond the critical point at the current descent slope. Timely alerts may be provided by accounting for the time required to announce a distance value, and the distance traveled during the announcement.
Description
- This application claims priority to the provisional application assigned attorney docket number 21035-00026, U.S. Application Ser. No. 60/448,906, filed in the United States Patent and Trademark Office on Feb. 24, 2003, and entitled “RUNWAY OVERRUN MONITOR AND METHOD FOR MONITORING RUNWAY OVERRUNS.”
- 1. Technical Field
- The invention relates to aircraft safety equipment and more particularly to an apparatus and method for increasing flight crew situational awareness during landing.
- 2. Related Art
- Landing is one of the most demanding tasks in flying. During the landing process, the aircraft must be brought to a safe and complete stop. To perform the landing properly, the aircraft must approach the runway within certain attitude, track, speed, and rate of descent limits. An approach outside of these limits can result in a “hard” landing, overrunning the runway end, or otherwise contacting the runway surface in an uncontrolled manner. Any one of these events has the potential to cause severe damage to the aircraft and may additionally result in passenger injuries or fatalities.
- Landing too fast and landing too far down a runway may contribute to runway overrun accidents. Pilots are trained to monitor these conditions during the approach, and to initiate a go-around maneuver if a safe landing is not assured. The effectiveness of pilot training depends, however, on the skill and judgment of the pilot in recognizing a possible runway overrun condition, and in executing the appropriate response. Pilots with varying levels of skill are therefore likely to respond differently to the same scenario.
- In most landing and departure situations, the pilot's vision is the sole data source for estimating runway position information. Even with existing high standards for pilot eyesight, some variation in acuity will occur as the pilot's physical condition, alertness, and state of rest vary. If the pilot's vision is the sole source of data used to determine whether a go-around or aborted takeoff is necessary, then variations in visual acuity, distractions or poor visibility may reduce the quality of the data used in the pilot's decision. In addition, a pilot may fly for years without experiencing a runway overrun, and the pilot may be slow to recognize a problem during landing.
- Aircraft safety can be improved by mitigating the effects of differing pilot skill levels and situational awareness during the landing phase of flight.
- According to a first aspect, a method of providing situational awareness during landing of an aircraft comprises determining a critical point on a runway, the critical point indicating a point at which if the aircraft lands beyond the critical point, there is a likelihood of the aircraft overrunning the runway. If a path projection from the aircraft intersects the runway beyond the critical point, an alert is provided.
- According to a second aspect, a method of providing timely alert messages in an aircraft during landing comprises determining message data regarding the aircraft's status during a landing phase, determining aircraft speed, adjusting a message based on the message data according to aircraft speed, and announcing the adjusted message.
- According to a third aspect, a method for monitoring for runway overrun when an aircraft is landing on a runway comprises determining an aircraft's position on the runway after the aircraft has touched down, determining the aircraft's groundspeed, determining the aircraft's deceleration, calculating a runway distance remaining before the aircraft on the runway, calculating a distance required to reach a desired speed at said deceleration, and generating an alert if the required distance is greater than the remaining runway distance.
- Those skilled in the art will appreciate the above stated advantages and other advantages and benefits of various embodiments of the invention upon reading the following detailed description of the embodiments with reference to the below-listed drawings.
- According to common practice, the various features of the drawings are not necessarily drawn to scale. Dimensions of various features may be expanded or reduced to more clearly illustrate the embodiments of the invention.
- The present invention is described with reference to the accompanying drawings. In the drawings, like reference numbers indicate identical or functionally similar elements.
-
FIG. 1 is a schematic side elevational view of a runway landing environment. -
FIG. 2 is a block diagram of a first embodiment of a runway overrun monitor. -
FIG. 3 is a top plan view of a portion of the runway landing environment illustrated inFIG. 1 . -
FIG. 4 is a schematic side elevational view of a portion of the runway landing environment illustrated inFIG. 1 , including several descent slopes. -
FIG. 5 illustrates a method of providing accurately timed alert messages. -
FIG. 6 illustrates a method of providing situational awareness after touchdown. - A runway overrun monitor provides an aircraft crew with a source of reliable and accurate data during the landing phase. Available information includes, for example, messages notifying the crew that under current conditions, the aircraft will not have enough runway to land safely. Information can also include alerts that the aircraft will exceed a maximum touchdown speed, or that maximum tailwind or crosswind limits will be exceeded. The above alerts can be provided automatically by the runway overrun monitor.
- To minimize cockpit confusion during landing, the runway overrun monitor may be configured to omit unsolicited, routine information. The pilot or crew may, however, solicit information such as, for example, tailwind and crosswind component values, runway identification, runway remaining for landing, and speed over the ground.
-
FIG. 1 illustrates arunway environment 100. Therunway environment 100 is illustrated as including arunway 110, arunway start 114, a touchdown zone (TDZ) 115, acritical point 116, anaircraft path projection 125, atouchdown aim point 130, and afirst checkpoint 150. Thetouchdown zone 115 is the length of therunway 110 where aircraft customarily touch down on landing. A common TDZ length is 75 feet, beginning at 500 feet past therunway start 114. TDZ lengths and locations on runways vary, however. - During the landing phase, an
aircraft 121 descends along thepath projection 125 to touch down at thetouchdown aim point 130. Thetouchdown aim point 130 is the location of the intersection of thepath projection 125 with therunway 110. The pilot then uses the aircraft brakes and reverse engine thrust, if available, to slow theaircraft 121 to a safe speed. As the aircraft approaches touchdown, the touchdown aim point may vary along therunway 110. Thus, thetouchdown aim point 130 is a predictor of the position along therunway 110 at which theaircraft 121 will actually touch down. Once theaircraft 121 touches down, the distance between the actual touchdown point and therunway end 120 is the available runway for slowing theaircraft 121 before it overruns therunway 110. This distance between thepredictor touchdown point 130 and therunway 120 may be referred to as “runway remaining” as theaircraft 121 approaches touchdown. As discussed below, calculations for runway distance remaining may be adjusted according to landing flare. A runway overrun can be generally defined as a situation in which theaircraft 121 proceeds past therunway end 120 at a groundspeed too high for safely attempting to turn theaircraft 121 onto a taxiway. - According to one aspect of the invention, the
path projection 125 of theaircraft 121 is monitored to determine whether thetouchdown aim point 130 is either in front of or beyond thecritical point 116. Thecritical point 116 may be defined as indicating a point at which if the aircraft lands beyond thecritical point 116, there is a likelihood of the aircraft overrunning therunway 110. Alerts are provided if thetouchdown aim point 130 is beyond thecritical point 116. -
FIG. 2 illustrates a runway overrunmonitor 200 capable of performing the alert functions described above. The runway overrun monitor 200 functions to apprise the pilot or crew members of the status of the aircraft carrying themonitor 200. The runway overrun monitor 200 comprises adata processor 201 coupled to asource 202 of company or manufacturer supplied runway data, asource 204 of aircraft performance data, asource 206 of aircraft position data, and asource 208 of avionics data. Thedata processor 201 may also be coupled to alert devices such as anaudio indicator 220 and avisual indicator 222. Theaudio indicator 220 can be, for example, a speaker, or a source of audio input coupled to headphones worn by a pilot. Thevisual indicator 222 can be, for example, one or more colored lights on a panel, or a display screen such as an LCD or CRT monitor. A weight on wheels (WOW)sensor 210 may be coupled to theprocessor 201 to provide an indication as to when the aircraft is airborne. - The
data processor 201 may be coupled to aninput device 224. Theinput device 224 may be used to solicit information from themonitor 200. Theinput device 224 may also be used at any time to request a data update from the runway overrun monitor 200. Theinput device 224 may include, for example, a “request update” button, or one or more keys designated for this purpose. Allowing the pilot or other operator to request specific updates reduces unnecessary background noise in the cockpit, while ensuring that the pilot receives alert information without looking inside the cockpit and away from the runway. In a preferred embodiment, themonitor 200 can include a single button that can be used to request information, and to mute further alerts. Theinput device 224 can therefore be used to acknowledge an alert. In a preferred embodiment, alerts are given only once, however, and acknowledgement of alerts is not necessary. - The runway data from the
source 202 describes the state of the runway that the aircraft carrying the runway overrun monitor 200 is preparing to land on or take off from. The runway data may include, for example, the length, and gradient of the intended landing runway. The runway data may also include a map of the airport, which includes data defining the runways at the airport, including the runway identifications. The runway data can be used to compare aircraft position with the distance to any of the runway boundaries, including the aircraft's height above ground in relation to a runway environment. Runway data can be taken from, for example, an airport mapping database (AMDB) including a digital description of the airport geography, such as the location of runways and a description of the altitude of the runways. - The aircraft performance data from the
source 204 may include, for example, company policy limits with respect to landing and stopping distance characteristics of an aircraft as a function of, for example, aircraft weight, with corrections based on, for example, wind direction, runway slope, runway surface condition, atmospheric altitude and outside temperature. The aircraft performance data may also include a list of manufacturer or company regulations defining various aspects of flight. For example, a company regulation may define maximum permissible airspeeds, groundspeeds, descent angles, minimum runway, required gear and flap configurations, etc., for different stages of landing. - In a preferred embodiment, the aircraft operator (the chief pilot, for example) can input a general required landing distance for the aircraft. The general required landing distance may be altered by the
processor 201 according to factors such as, for example, the presence of a tailwind component, altitude, runway gradient, and air temperature. Additional aircraft performance data is therefore not required. - The aircraft position data from the
source 206 may include, for example, aircraft altitude, latitude, longitude, track over the ground, descent slope and groundspeed. The position data can be used to calculate the aircraft's vertical and horizontal acceleration. Themonitor 200 may be coupled to one or more of an inertial navigation system, an altimeter, a global positioning system receiver, and an accelerometer to obtain aircraft position data. Position data can be differentiated with respect to time to obtain velocity, including groundspeed, and acceleration data. The position data can be in the form of, for example, longitude, latitude and altitude. Velocity may also be provided directly from the global positioning system, or from the inertial navigation system. - The avionics (more specifically, air data and heading) data from the
source 208 can include, for example, data such as pressure, airspeed, true airspeed and wind vector (wind vector may be estimated using the true airspeed, groundspeed, track and heading) and direction, which may be provided as tailwind/headwind components, may also be supplied to themonitor 200. Themonitor 200 may use this data to determine, for example, tailwind and crosswind components. -
FIGS. 1, 3 and 4 illustrate an embodiment of a method for providing situational awareness during landing. - Referring to
FIG. 1 , theaircraft 121 is illustrated as approaching therunway 110. Thepoint 150 illustrates a first checkpoint, and can serve as a starting point at which the runway overrun monitor 200 begins monitoring the aircraft's situation during landing. As an alternative, monitoring may begin when the visual path point 125 intersects with the touch downzone 115.FIG. 3 is a top plan view of therunway 110. - According to conventional landing procedures, an aircraft follows a descent slope during landing. The descent slope is typically defined as some optimal angle of descent for the aircraft. For example, descent slopes may be inclined at an angle in the range of about 3-4°. Maximum (i.e., steepest) descent slope values for the
aircraft 121 may be provided by, for example, the aircraft operator, such as the owning corporation of theaircraft 121. Preferably, an aircraft maintains a constant angle of descent as it approaches the runway. - The
path projection 125 illustrated inFIGS. 1, 3 and 4 is preferably inclined at the same angle as a preferred descent slope angle of descent for theaircraft 121. InFIG. 1 , thepath projection 125 is at an angle θ to horizontal. Thepath projection 125 extends from theaircraft 121 and intersects level (i.e., zero gradient) ground at the angle θ. In an ideal landing, thetouchdown aim point 130 would stay at the same location on therunway 110 throughout the landing procedure. Thepath projection 125 is preferably extended at a constant angle θ during the landing operation. - According to one aspect of the invention, the
path projection 125 is monitored in order to determine whether the intersection of thepath projection 125 with therunway 110 is before or beyond thecritical point 116. The intersection point is labeled as thetouchdown aim point 130. It is significant when thetouchdown aim point 130 is beyond thecritical point 116 because if theaircraft 121 continues on thatpath projection 125 without adjustment, theaircraft 121 may not be able to stop safely before therunway end 120. - Monitoring may begin, for example, at the
point 150. Thepoint 150 can correspond to the location of the outer marker for a runway. Such a point can be at a distance of, for example, about 5 miles away from therunway 110. Monitoring may also begin once thepath projection 125 intersects with theTDZ 115, and alerts may be provided to the pilot or crew of theaircraft 121 when certain conditions are met. -
FIG. 4 is an isolated view of a portion of therunway 110. Several descent slopes 125 1, 125 2, 125 3 and corresponding touchdown aim points 130 1, 130 2, 130 3 are illustrated, corresponding to times t1, t2, t3, respectively. As shownFIG. 4 , at time t1, if thecurrent path projection 125 1 is maintained, theaircraft 121 will land in front of thecritical point 116. At time t2, as a result of changing conditions, thepath projection 125 2 has moved towards thecritical point 116, but remains in front of thecritical point 116. At time t3, thepath projection 125 3 intersects the runway at atouchdown aim point 130 3 beyond thecritical point 116. At this time, if theaircraft 121 continues on itscurrent path projection 125 3, there is a chance that theaircraft 121 may not have enough runway to land safely. - If the
monitor 200 detects that thecurrent path projection 125 i indicates that theaircraft 121 is likely to land beyond thecritical point 116, themonitor 200 may issue an unsolicited alert. The alert may have the form of an audible message, such as a message stating the amount of runway theaircraft 121 will have available, after touchdown, to stop theaircraft 121. For example, the alert message can have the form “RUNWAY REMAINING 4000 FEET.” The alert message should be short and should contain minimal information so that the pilot is not unnecessarily distracted. - As the
aircraft 121 approaches therunway 110, themonitor 200 may periodically determine whether thetouchdown aim point 130 passes over thecritical point 116. In general, themonitor 200 issues an alert the first time thetouchdown aim point 130 passes over thecritical point 116. It is preferable that further alerts are not provided for each updating period, because the pilot is already made aware of the potentially dangerous situation. However, if after an alert is issued, and thetouchdown aim point 130 again moves in front of the critical point 116 (i.e., runway overrun no longer likely), further alerts may be provided if thetouchdown aim point 130 once again moves beyond thecritical point 116. Themonitor 200 may continue to monitor for runway distance remaining until touchdown. - The
monitor 200 may monitor other aircraft conditions. For example, referring toFIG. 1 , when the aircraft reachespoint 150, themonitor 200 can determine whether theaircraft 121 is in a desired configuration for landing. The required configuration can be defined according to, for example, company regulations, such as would govern a commercial carrier. The required configuration may also be defined by standards recommended by the aircraft manufacturer, or by input by the pilot. - A configuration check can evaluate the following: whether aircraft landing gear is down; whether a required flap position is detected; whether a maximum tailwind component is exceeded; whether a maximum crosswind component is exceeded; whether the aircraft is above a maximum altitude; whether the aircraft is exceeding a maximum airspeed; and whether the aircraft is exceeding a maximum groundspeed. As discussed above, the
monitor 200 may monitor for atouchdown aim point 130 that passes over thecritical point 116. Each of the above factors or conditions can be selectively monitored and reported, depending on the usefulness of the information to the pilot. In general, themonitor 200 will not provide unsolicited alerts if there are no potential problems detected for the landing. Exemplary reporting options are discussed below. - The configuration check can be termed as a check of whether the aircraft is “in the slot.” “In the slot” is a term indicating that an aircraft is operating within prescribed airspeed, gear position, flap position, power setting, and altitude parameters. A check of whether an aircraft is in the slot is usually made between the runway outer marker and some distance from the runway. Referring to
FIG. 3 , an aircraft in the slot can also indicate that the aircraft is within an angular range β about therunway 110centerline 140. In general, when an aircraft is outside of the angular range β, the pilot is not warned. A pilot in this situation will likely be aware of the aircraft's location outside of the angular range β. The final approach course is an imaginary line extending back along a runway centerline from the approach end of therunway 110. Theaircraft 121 can be considered to “track” the final approach course when theaircraft 121 is within a certain azimuth range β of the runway centerline 140 (seeFIG. 3 ). The azimuth range β may be, for example, +/−five degrees. The final approach course may extend, for example, five miles before therunway 110 out topoint 150. A specified lateral offset l1 from therunway centerline 140 may also be used to define the final approach course. The offset l1 can be, for example, about 250 feet. - At
point 150, theaircraft 121 altitude may be too high to obtain tailwind and crosswind component values that are useful to evaluate the feasibility of a landing. Tailwind and crosswind component checks may therefore be delayed until theaircraft 121 is at a lower altitude. - Alert messages should be as brief and informative as possible. For example, if landing gear is not down in the configuration check, a message “NOT IN LANDING CONFIGURATION, GEAR” may be provided. Similarly, “NOT IN LANDING CONFIGURATION, FLAPS” can indicate flaps in the wrong position, or “NOT IN LANDING CONFIGURATION, AIRSPEED,” may indicate an airspeed outside of recommended parameters, and “NOT IN LANDING CONDITION, ALTITUDE,” can indicate an altitude outside of recommended parameters.
- Referring to
FIG. 1 , at apoint 160, themonitor 200 may enable monitoring of additional factors affecting the landing. For example,point 160 may correspond to a point where theaircraft 121 altitude is lower, in the range of, for example, 500 feet or less. At this time, tailwind and crosswind values may be more accurately determined as they affect landing on therunway 110. If a maximum tailwind or crosswind component value is exceeded, themonitor 200 may issue an alert informing the pilot of the condition. Monitoring for excessive tailwind or crosswind values may continue until theaircraft 121 is at a height of about 100 feet. At 100 feet, alerts may be addressed solely to whether sufficient runway remains for landing. In general, a tailwind or crosswind alert is given only once, as repetition may distract the pilot. - Crosswind alerts can indicate the crosswind component and direction. For example, a crosswind alert can have the form “RIGHT CROSSWIND 20 KNOTS.” Similarly, a tailwind announcement can have the form “TAILWIND 10 KNOTS.” As stated above, crosswind and tailwind announcements may be delayed until the
aircraft 121 is at a lower altitude. In one preferred embodiment, tailwind and crosswind alerts are issued after theaircraft 121 descends below 300 feet, and cease when the aircraft descends below 100 feet. - The
monitor 200 may monitor to determine whether theaircraft 121 will exceed a maximum touchdown speed or is currently exceeding a maximum airspeed. Monitoring for exceedance of maximum touchdown speed can begin atpoint 150, for example. In one embodiment, alerting for exceedance of maximum touchdown speed begins when theaircraft 121 descends to an altitude of about 300 feet. Other altitudes are also appropriate. - When the
aircraft 121 reaches a threshold altitude, all alerts except for insufficient runway alerts may cease. The threshold altitude value may be, for example, 100 feet. At this time, alerts relating to crosswind, tailwind, and groundspeed, etc., may be extraneous and may distract the pilot. - The
critical point 116 may be determined according to, for example, operator-recommended landing distances. Thecritical point 116 is determined as a function of runway length and runway distance required for the aircraft to land and stop safely. Required landing distance for an aircraft is dependent upon aircraft type, runway gradient, airport elevation, density altitude, established company parameters, and other factors determining the length of runway required for an aircraft to land safely. This information can be stored on computer-readable media, for example, and may be accessible by themonitor 200. Themonitor 200 can also adjust thecritical point 116 according to prevailing conditions. For example, the presence of a tailwind increases the distance required for an aircraft to land, thereby moving the critical point to the left inFIG. 1 . The required landing distance may also be adjusted according to runway altitude, runway gradient, and air temperature. - In determining the
critical point 116, themonitor 200 may account for aircraft flare occurring just before touchdown. Themonitor 200 can account for flare in at least two ways. A first way to account for flare is to add an expected flare distance to the landing distance, and increase landing distance accordingly. This method results in thecritical point 116 being moved to the left inFIG. 1 . Alternatively, flare can be accounted for by virtually shifting thepath projection 125 to the right inFIG. 1 by the expected flare distance. - The information provided to the pilot should be simple and as easily understood as possible. Therefore, distances are preferably rounded off to hundreds, or thousands of feet. For example, during the time when the aircraft is about to touch down, measurements of runway remaining are preferably rounded off to the nearest thousand foot increment. There are at least two ways of implementing this feature. A first way is to round the runway remaining figure down, so the pilot has a conservative estimate of runway remaining. Another is to round up or down, this method being less preferred. Another method is to time the sounding of an alert message so the threshold hundred or thousand foot increment message is accurate when received by the pilot. A method of timing messages is discussed in detail below with reference to
FIG. 5 . - Safety margins can also be programmed into the runway overrun monitor 200. For example, the pilot or other operator can program the
monitor 200 to consistently underestimate runway remaining figures by a selected percentage or by a selected distance. - The pilot can end alerts from the monitor at any time. Alerts can be ended at the
input 224. Theinput 224 can act as a “mute” button by a single press of a button. The pilot may take this action if he no longer plans on landing. Themonitor 200 can be reactivated when, for example, theaircraft 121 arrives at its next visual path point. - The pilot or crew can also solicit information from the
monitor 200 at any time. Solicited information can include any of the announcements discussed above. Solicited alerts can be requested, for example, at theinput 224. For simplicity of themonitor 200, a single button can be used as a mute button as discussed above, and as a means for requesting unsolicited updates. For example, at a relatively far distance out (e.g., about 10 miles) from theTDZ 115, the pilot can double-press a button on theinput 224 to request a runway identification, the distance to theTDZ 115, and ground speed. Such an announcement may have the form “RUNWAY TWO FOUR LEFT, NINE MILES TO TOUCHDOWN, 120 KNOTS OVER THE GROUND.” - After reaching
point 150, which may correspond to a location of the airport outer marker, the pilot may again solicit information by a double-press of a button on theinput 224. This further information can include another runway identification, and groundspeed announcement. - The relatively high speeds at which the
aircraft 121 travels renders the timeliness of alert messages of high importance. For example, an aircraft traveling at 150 knots traverses 250 feet per second. Therefore, any time-offset between a time when the message is accurate and when the message is actually received by the pilot can result in the pilot receiving erroneous information. -
FIG. 5 illustrates a method of ensuring that accurate alert messages are provided to a pilot or other operator. According to one aspect, the timing of alert messages is calculated so that the information is accurate when received by the pilot. For example, in one embodiment, an audible message is presented so that at the end of the message, the data conveyed in the message is accurate. The runway overrun monitor 200 disclosed inFIG. 2 can be programmed to announce messages in accordance with the method discussed below. - Referring to
FIG. 5 , message data is determined in step S300. The message data may correspond to any of the alert messages discussed above, and the message data determined in step S300 may be determined accordingly. For example, the message data can include a statement regarding runway remaining dRR. - In step S302, a speed of the
aircraft 121 is determined. The speed can be, for example, the groundspeed or airspeed of theaircraft 121. In a preferred embodiment, the groundspeed is determined. The message data and the aircraft speed can be determined concurrently, as shown inFIG. 5 , or serially (not shown). - In step S304, the message is adjusted in order to compensate for factor such as the time required to announce the message, and for other factors. Step S304 can be determined according to steps S306-S314 below:
- In step S306, the time at which the message data is accurate is indexed as t0 for the piece of information in the message. The time t0 can be indexed to account for time involved in calculating or processing information. For example, a time t0 for a runway remaining message can be adjusted to account for the time required to read, for example, GPS instruments, and to calculate the runway remaining in the
processor 201. - In step S308, a time tM required to announce an alert message is determined. For example, the message “RUNWAY REMAINING 4000 FEET” requires about 2.1 seconds to announce. If the pilot wants to hear the end of the message—i.e, the word “FEET”—when the aircraft has 4000 feet remaining, tM is equal to about 2.1 seconds. The time necessary to understand the massage and to react could also be considered when determining tM. If the pilot wants to hear the word “4000” when the aircraft has 4000 feet remaining, tM is equal to about 1.8 seconds. The time required tM can therefore be calculated according to operator preferences. A default setting can be included in the
monitor 200 so that tM is calculated according to the time required to announce the entire message. - In step S310, a distance value dx is determined. The distance value dx represents the distance the
aircraft 121 travels during the time tM required to announce an alert message. Time tM is calculated according to the aircraft speed, and aircraft motion may be governed by the following equation:
d x =v x ×t M Equation 1 - In Equation 1, dx indicates a distance traveled in a direction aligned the
runway 110 length while traveling with an x-component of velocity vx. - In
step 312, a distance value d contained in the message is adjusted by subtracting dx. If the relevant distance is runway remaining, the message data can include a statement regarding runway remaining dRR. The adjusted runway remaining value dRRA is:
d RRA =d RR −d x Equation 2 - In
step 314, the message data is revised according to the adjusted runway remaining value dRRA. - In
step 316, the alert is announced, including the adjusted runway remaining value dRRA. - The method discussed above includes a feedback loop to address the situation in which the new distance dRR results in a new message length tM. Activation of the feedback loop may be subject to a threshold change message length ΔtM in message length tM.
- As an alternative to calculating a time tM for each distance message having a different distance value dRR, a standard time tM can be assigned for all messages of this type. This approximation may be made because an announcement of “RUNWAY REMAINING 4000 FEET” has approximately the same tM as “RUNWAY REMAINING 500 FEET.”
- The method for providing timely message data described above can be applied during both solicited and unsolicited announcements.
- The
monitor 200 may also continue to provide situational awareness after theaircraft 121 has touched down. A method for providing situational awareness after touchdown is discussed below with reference toFIG. 6 . - Closure rates between aircraft can be extremely fast. For example, at a closure rate of 1200 knots, an aircraft travels about one mile every ten seconds. In a collision alerting system (not shown), traffic alert announcements may be generated, for example, when traffic is within about 30 seconds of a point of closest approach between an aircraft and the traffic. Therefore, the length of time required to make a position announcement is a significant part of the time available to avoid the oncoming traffic. Further, the last item announced in an announcement may be the range between an aircraft and the traffic, which changes very quickly.
- The closure rate is especially high when the traffic is an aircraft and the two aircraft are on a collision course. It is therefore critical in collision alerting systems that closure ranges are as accurate as possible when presented to the pilot. Accuracy of range announcements is particularly important because the pilot's perception of threat is based on the range between the aircraft and the traffic. Therefore, the closer oncoming traffic is, the more relevant it is to the pilot.
- In accordance with a present embodiment of a traffic alerting system, traffic alert announcements are announced based on a predictive algorithm, similar to the runway remaining announcements discussed above. In other words, the range announcements from the traffic alerting system should be made so that the announced range is accurate at the end of the announcement, or, concurrently with the announcement of the range.
- In one embodiment of a collision alerting system, a collision alerting system adjusts a calculated range between an aircraft and traffic using a predictive algorithm. The range is predicted in the following manner:
- First, a detected traffic alerting range Rd between the aircraft and traffic is determined. Next, a time ta required to announce the range Rd is determined. The closing rate CR between the aircraft and the traffic is then determined. Then, the detected traffic alerting range Rd is adjusted so that it will be accurate when the range is actually announced. The actual or adjusted range Ra can be calculated according to the formula:
R a =R d −CR×t a Equation 3 - The adjusted range Ra is then announced.
- As discussed above, a standard time ta may be used, rather than calculating the actual time required to make an announcement.
-
FIG. 6 illustrates a method for monitoring landing overrun after touchdown. Instep 610 it is determined if theaircraft 121 is landing. This step can be performed by theprocessor 201 recognizing, for example, a landing gear position, or, by recognizing a decrease in altitude. The pilot can also manually input an indication that theaircraft 121 is landing. If theaircraft 121 is not landing, the method returns to step 610. - If the
aircraft 121 is landing, instep 620 therunway overrun device 200 monitors to determine whether theaircraft 121 has touched down. This determination is made according to the sensor inputs available to theprocessor 201. For example, referring toFIG. 2 , theWOW sensor 210 output can be used to determine whether theaircraft 121 is airborne. Other devices and methods useful to determine whether theaircraft 121 is airborne include a comparison of the aircraft altitude with the altitude of the terrain at the aircraft's position. If theaircraft 121 has not yet touched down, the method returns to step 610. - If the
aircraft 121 has reached the ground, theprocessor 201 calculates a required deceleration distance DREQ instep 630. The required deceleration distance DREQ is the distance that will be traveled by theaircraft 121 in decelerating from the current groundspeed to a desired groundspeed. - The desired groundspeed can be, for example, zero, or some speed that allows the
aircraft 121 to turn at the runway end, such as a maximum taxi speed. The required deceleration distance is based on runway remaining, and is calculated using the values of groundspeed upon landing. The time to decelerate to the desired groundspeed may be determined using the deceleration rate. The deceleration rate can be measured directly, using, for example, an accelerometer, or calculated by determining the time derivative of the measured groundspeed. Aircraft deceleration can be determined as a deceleration function by extrapolating a curve from three or more position data points. - In
step 635, the runway distance remaining DRW is determined. The remaining runway distance DRW is calculated by comparing the aircraft position with the data from thesource 202 of runway data. - In
step 640, it is determined whether the groundspeed of the aircraft is less than a maximum taxi speed. If theaircraft 121 is traveling at a speed below the maximum value, such as, for example, 10 knots, it is likely that theaircraft 121 is taxiing. If so, the method ends and the runway overrun monitor 200 ceases to monitor for a runway overrun. - In
step 650, it is determined whether the required deceleration distance DREQ is greater than the remaining runway distance DRW. If not, the method returns to step 610. If the required deceleration distance DREQ is greater than the remaining runway distance DRW, an alert is generated instep 660. The warning can comprise, for example, an audio message broadcast by theaudio indicator 220, a visual message displayed by thevisual indicator 222, or a combination audio and visual message. For example, the audio message can contain an indication of the calculated runway distance remaining DRW soon after touchdown and aircraft groundspeed. Thevisual indicator 222 can display similar information, including a running display of the remaining runway distance DRW, and, for example, a flashing warning indicator. Broadcasts of the remaining runway distance DRW and the aircraft's groundspeed can be updated periodically. - According to the above method, the pilot receives a warning when the remaining runway distance DRW is insufficient to safely decelerate the
aircraft 121 at the current deceleration function. The information from the runway overrun monitor allows the pilot to increase the rate of deceleration, such as by increasing the braking force, or by increasing reverse engine thrust, if available. - As an alternative to step 650, the
processor 201 can determine whether theaircraft 121 has exceeded a predetermined groundspeed in conjunction with having less than a specified remaining runway distance DRW. For example, if theaircraft 121 is traveling at a rate of 75 knots over ground, and 2,000 feet of runway remain, a warning can be generated stating the groundspeed and remaining runway. - The trigger for generating an alert can be reference to a table specifying, for example, that at a remaining runway distance of 2,000 feet, a warning will be generated when aircraft groundspeed exceeds 70 knots. A table of remaining runway distance DRW versus groundspeed can be manually entered by an operator, or preprogrammed in the
processor 201. The above threshold values for remaining runway distance DRW and groundspeed can be adjusted according to airport and runway conditions and aircraft performance data. - As an alternative to or in addition to the above embodiment, the required deceleration for a safe stop can be compared to the aircraft's actual deceleration. An alert may be provided if the aircraft's deceleration is not sufficient.
- The foregoing description of the specific embodiments will so fully reveal the general nature of the invention that others can, by applying knowledge within the skill of the art (including the contents of the references cited herein), readily modify and/or adapt for various applications such specific embodiments, without undue experimentation, without departing from the general concept of the present invention. Therefore, such adaptations and modifications are intended to be within the meaning and range of equivalents of the disclosed embodiments, based on the teaching and guidance presented herein.
- It is to be understood that the phraseology or terminology herein is for the purpose of description and not of limitation, such that the terminology or phraseology of the present specification is to be interpreted by the skilled artisan in light of the teachings and guidance presented herein, in combination with the knowledge of one of ordinary skill in the art.
Claims (8)
1-15. (canceled)
16. A method for monitoring for runway overrun when an aircraft is landing on a runway, comprising:
determining an aircraft's position on the runway after the aircraft has touched down;
determining the aircraft's groundspeed;
calculating a runway distance remaining before the aircraft on the runway;
calculating a distance required to reach a desired speed; and
generating an alert if the required distance is greater than the remaining runway distance.
17. The method of claim 16 , comprising:
determining the aircraft's deceleration.
18. The method of claim 17 , wherein calculating a distance required to reach a desired speed comprises:
calculating a distance required to reach a desired speed at said deceleration
19. The method of claim 18 , wherein determining an aircraft's deceleration comprises:
calculating the aircraft deceleration function as a rate of change of said aircraft groundspeed.
20. The method of claim 16 , wherein calculating a runway distance remaining comprises:
comparing the aircraft position to a runway end position; and
calculating the distance along a length of the runway between the aircraft position and the runway end position.
21. The method of claim 17 , comprising:
determining a required deceleration to reach the desired speed; and
generating an alert if the absolute value of the current deceleration is less than the absolute value of the required deceleration.
22-23. (canceled)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/192,267 US20050261813A1 (en) | 2003-02-24 | 2005-07-29 | Method and apparatus for predicting runway overrun |
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US44890603P | 2003-02-24 | 2003-02-24 | |
US10/442,147 US20040167685A1 (en) | 2003-02-24 | 2003-05-21 | Runway overrun monitor and method for monitoring runway overruns |
US10/972,328 US6978205B2 (en) | 2003-02-24 | 2004-10-26 | Method and apparatus for predicting runway overrun |
US11/192,267 US20050261813A1 (en) | 2003-02-24 | 2005-07-29 | Method and apparatus for predicting runway overrun |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/972,328 Division US6978205B2 (en) | 2003-02-24 | 2004-10-26 | Method and apparatus for predicting runway overrun |
Publications (1)
Publication Number | Publication Date |
---|---|
US20050261813A1 true US20050261813A1 (en) | 2005-11-24 |
Family
ID=32871904
Family Applications (4)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/442,147 Abandoned US20040167685A1 (en) | 2003-02-24 | 2003-05-21 | Runway overrun monitor and method for monitoring runway overruns |
US10/972,328 Expired - Fee Related US6978205B2 (en) | 2003-02-24 | 2004-10-26 | Method and apparatus for predicting runway overrun |
US11/192,267 Abandoned US20050261813A1 (en) | 2003-02-24 | 2005-07-29 | Method and apparatus for predicting runway overrun |
US11/192,278 Expired - Fee Related US7085630B2 (en) | 2003-02-24 | 2005-07-29 | Method and apparatus for predicting runway overrun |
Family Applications Before (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/442,147 Abandoned US20040167685A1 (en) | 2003-02-24 | 2003-05-21 | Runway overrun monitor and method for monitoring runway overruns |
US10/972,328 Expired - Fee Related US6978205B2 (en) | 2003-02-24 | 2004-10-26 | Method and apparatus for predicting runway overrun |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/192,278 Expired - Fee Related US7085630B2 (en) | 2003-02-24 | 2005-07-29 | Method and apparatus for predicting runway overrun |
Country Status (1)
Country | Link |
---|---|
US (4) | US20040167685A1 (en) |
Cited By (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
FR2895726A1 (en) * | 2006-01-03 | 2007-07-06 | Thales Sa | Aircraft`s braking intensity adjustment providing method for use in airport, involves recovering data concerning aircraft or runway when aircraft is landing, and acquiring position of aircraft on runway and speed in taxiing phase |
US20100198432A1 (en) * | 2009-02-04 | 2010-08-05 | Honeywell International Inc. | Stable approach monitor (sam) system |
US20110022291A1 (en) * | 2005-10-13 | 2011-01-27 | Honeywell International Inc. | Perspective-view visual runway awareness and advisory display |
US20130218374A1 (en) * | 2012-02-22 | 2013-08-22 | Honeywell International Inc. | Display system and method for generating a display |
US20140257601A1 (en) * | 2013-03-06 | 2014-09-11 | Gulfstream Aerospace Corporation | Runway overrun monitor |
US8903572B1 (en) * | 2009-08-11 | 2014-12-02 | The Boeing Company | Aircraft landing evaluation system |
WO2018125866A1 (en) * | 2016-12-28 | 2018-07-05 | Hydro-Aire, Inc. | System and method for simplified aircraft brake distance estimation |
US20180273200A1 (en) * | 2017-03-27 | 2018-09-27 | Honeywell International Inc. | Avionic display systems and methods for generating vertical situation displays including instability prediction and avoidance symbology |
US10152195B2 (en) | 2015-12-14 | 2018-12-11 | Honeywell International Inc. | Aircraft display system pertaining to energy management |
US10227140B2 (en) | 2014-07-11 | 2019-03-12 | Cmc Electronics Inc | System and method for detecting and alerting the user of an aircraft of an impendent adverse condition |
US20190112073A1 (en) * | 2017-10-12 | 2019-04-18 | Rosemount Aerospace Inc. | Automated aircraft landing performance analysis |
US10839701B2 (en) | 2018-06-05 | 2020-11-17 | Honeywell International Inc. | Methods and systems for stabilized approach energy management |
US10854091B2 (en) | 2018-07-03 | 2020-12-01 | Honeywell International Inc. | Energy management visualization methods and systems |
Families Citing this family (67)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7394402B2 (en) * | 2001-02-02 | 2008-07-01 | Honeywell International Inc. | Tailwind alerting system to prevent runway overruns |
US8023936B2 (en) * | 2004-04-19 | 2011-09-20 | The Boeing Company | Method and system for monitoring ad-hoc network nodes |
US20050234788A1 (en) * | 2004-04-19 | 2005-10-20 | Hudson John G | Method and system for billing for internet services for ad-hoc network nodes |
CA2586766A1 (en) * | 2004-11-10 | 2006-12-28 | L-3 Communications Avionics Systems, Inc. | Takeoff and landing performance indicator for fixed wing aircraft |
US8615038B2 (en) * | 2004-12-06 | 2013-12-24 | Nokia Corporation | Video coding, decoding and hypothetical reference decoder |
FR2885439B1 (en) * | 2005-05-09 | 2010-11-19 | Airbus France | METHOD AND DEVICE FOR AIDING THE CONTROL OF AN AIRCRAFT DURING AN APPROACH PHASE FOR LANDING |
US20070120708A1 (en) * | 2005-09-09 | 2007-05-31 | Honeywell International Inc. | Methods and systems for monitoring aircraft approach between approach gates |
US7412324B1 (en) * | 2005-09-28 | 2008-08-12 | Rockwell Collins, Inc. | Flight management system with precision merging |
FR2895072B1 (en) * | 2005-12-20 | 2008-02-29 | Thales Sa | METHOD FOR AVOIDING CONFUSIONS OF LANDING ROADS |
FR2897593B1 (en) * | 2006-02-17 | 2012-09-14 | Airbus France | METHOD AND SYSTEM FOR PREDICTING THE POSSIBILITY OF COMPLETELY STOPPING AN AIRCRAFT ON A LANDING TRAIL. |
US7555372B2 (en) * | 2006-04-21 | 2009-06-30 | Honeywell International Inc. | Method and apparatus to display landing performance data |
FR2902081B1 (en) * | 2006-06-12 | 2008-07-11 | Airbus France Sas | LANDING ASSISTANCE METHOD AND DEVICE FOR AIRCRAFT |
FR2903801B1 (en) * | 2006-07-12 | 2008-09-12 | Airbus France Sas | METHOD AND DEVICE FOR PREDICTING THE STOPPING POSITION OF AN AIRCRAFT DURING LANDING. |
US20090200421A1 (en) * | 2006-08-08 | 2009-08-13 | Vinayak Virkar | Efficient airport runway management system |
FR2906066B1 (en) * | 2006-09-15 | 2008-12-19 | Thales Sa | METHOD OF ESTIMATING THE POINT OF TOUCHING WHEELS OF AN AIRCRAFT ON A LANDING TRAIL AND THE DISTANCE TO BE FOLLOWED FROM THE POINT OF TOUCH TO REACH A CONTROLLED SPEED. |
US20080215198A1 (en) * | 2006-09-22 | 2008-09-04 | Richards Robert E | Method and apparatus for providing takeoff runway information and predicting end of runway overrun |
US20080140727A1 (en) * | 2006-12-07 | 2008-06-12 | Karl Christian Pschierer | Method and apparatus for managing geographic information system data |
FR2914097B1 (en) * | 2007-03-20 | 2014-05-23 | Airbus France | METHOD AND DEVICE FOR AIDING THE CONTROL OF AN AIRCRAFT DURING A LANDING PHASE |
FR2914770B1 (en) * | 2007-04-04 | 2015-11-06 | Airbus France | METHOD AND DEVICE FOR DETERMINING A DELAY MARGIN AT AIRCRAFT LANDING |
FR2915610B1 (en) * | 2007-04-24 | 2009-07-10 | Thales Sa | METHOD FOR CALCULATING AN AIRCRAFT APPROACH TRACK TO AN AIRPORT |
US8533180B2 (en) * | 2007-06-13 | 2013-09-10 | The Boeing Company | Method and apparatus for enhancing a geographic information system database with operational data |
US8055395B1 (en) * | 2007-06-21 | 2011-11-08 | Rockwell Collins, Inc. | Methods and devices of an aircraft crosswind component indicating system |
US8126600B2 (en) * | 2008-06-18 | 2012-02-28 | Honeywell International Inc. | Method and apparatus for improving pilot situational awareness during flare to touchdown |
US20100017050A1 (en) * | 2008-07-18 | 2010-01-21 | Watts Randy | Apparatus and method for determining and indicating distance between flaring airplane & landing surface |
US8825238B2 (en) * | 2008-07-22 | 2014-09-02 | Honeywell International Inc. | Aircraft systems and methods for monitoring energy height |
US8473126B2 (en) * | 2008-07-28 | 2013-06-25 | Passur Aerospace, Inc. | Surface management at an airport |
US20100036550A1 (en) * | 2008-08-05 | 2010-02-11 | Honeywell International Inc. | Systems and methods for improving pilot situational awareness during landing |
FR2936079B1 (en) * | 2008-09-16 | 2010-09-17 | Thales Sa | METHOD FOR MONITORING THE LANDING PHASE OF AN AIRCRAFT |
US20100127896A1 (en) * | 2008-11-21 | 2010-05-27 | Bland Hugh Schwarting | Optical path alignment landing system |
US8451144B2 (en) * | 2009-02-04 | 2013-05-28 | Honeywell International Inc. | Flaps overspeed advisory system |
US20110118909A1 (en) * | 2009-11-19 | 2011-05-19 | Honeywell International Inc. | Systems and methods of detecting low takeoff performance due to incorrect weight information |
US8040259B2 (en) * | 2009-11-23 | 2011-10-18 | Honeywell International Inc. | Systems and methods for alerting to traffic proximity in the airport environment |
US20120209458A1 (en) * | 2011-02-14 | 2012-08-16 | Honeywell International Inc. | Systems and methods for verifying an available runway length |
US8630756B2 (en) * | 2011-04-12 | 2014-01-14 | The Boeing Company | Airplane position assurance monitor |
FR2978282B1 (en) * | 2011-07-22 | 2013-08-30 | Thales Sa | METHOD AND DEVICE FOR FILTERING ALERTS FROM AN AIRCRAFT COLLISION DETECTION SYSTEM |
US8868265B2 (en) | 2011-11-30 | 2014-10-21 | Honeywell International Inc. | System and method for aligning aircraft and runway headings during takeoff roll |
US9278674B2 (en) * | 2012-01-18 | 2016-03-08 | Engineered Arresting Systems Corporation | Vehicle operator display and assistive mechanisms |
US9165366B2 (en) | 2012-01-19 | 2015-10-20 | Honeywell International Inc. | System and method for detecting and displaying airport approach lights |
US8797191B2 (en) | 2012-07-13 | 2014-08-05 | Honeywell International Inc. | Systems and methods for displaying runway information |
US11657721B1 (en) | 2013-08-26 | 2023-05-23 | Otto Aero Company | Aircraft with flight assistant |
US10502584B1 (en) | 2012-12-28 | 2019-12-10 | Sean Patrick Suiter | Mission monitor and controller for autonomous unmanned vehicles |
US20140343765A1 (en) * | 2012-12-28 | 2014-11-20 | Sean Patrick Suiter | Flight Assistant with Automatic Configuration and Landing Site Selection |
US9663223B1 (en) | 2013-02-11 | 2017-05-30 | The Boeing Company | Aircraft braking performance and runway condition determination |
US9196166B2 (en) | 2013-03-06 | 2015-11-24 | Gulfstream Aerospace Corporation | Runway takeoff monitor |
US9262932B1 (en) * | 2013-04-05 | 2016-02-16 | Rockwell Collins, Inc. | Extended runway centerline systems and methods |
FR3005758B1 (en) * | 2013-05-14 | 2015-06-26 | Thales Sa | METHOD AND SYSTEM FOR MONITORING THE FLIGHT PHASE OF AN AIRCRAFT IN THE APPROACH PHASE TO A LANDING TRACK |
US9529010B2 (en) | 2013-06-17 | 2016-12-27 | Honeywell International Inc. | Flight deck display systems and methods for visually indicating low speed change conditions during takeoff and landing |
US9340300B2 (en) | 2013-09-16 | 2016-05-17 | The Boeing Company | On-ground braking alerts for airplanes |
US9082301B2 (en) | 2013-10-28 | 2015-07-14 | The Boeing Company | Aircraft stopping performance display and warning |
US20150127196A1 (en) * | 2013-11-06 | 2015-05-07 | Honeywell International Inc. | System and method for alerting of remaining runway upon landing based on deceleration |
US9117370B1 (en) * | 2014-03-12 | 2015-08-25 | Honeywell International Inc. | System and method for identifying runway position during an intersection takeoff |
US9430948B2 (en) * | 2014-04-16 | 2016-08-30 | The Boeing Company | Landing alerts for preventing runway excursions |
FR3027722B1 (en) * | 2014-10-24 | 2020-12-25 | Thales Sa | ENERGY MANAGEMENT IN THE APPROACH TRAJECTORY |
FR3033924B1 (en) * | 2015-03-16 | 2017-03-03 | Sagem Defense Securite | AUTOMATIC ASSISTANCE METHOD FOR LANDING AN AIRCRAFT |
US10059466B2 (en) * | 2015-03-18 | 2018-08-28 | Louis DeGagne | System and method for dynamically determining runway stopping distance |
US9573698B1 (en) | 2015-08-06 | 2017-02-21 | Honeywell International Inc. | Flight deck display systems and methods for generating cockpit displays including dynamically-adjusted usable runway length symbology |
FR3049265B1 (en) * | 2016-03-24 | 2019-09-13 | Airbus Operations | METHOD AND DEVICE FOR DISPLAYING A HELP SYMBOL FOR AIDING AN AIRCRAFT DURING A LANDING PHASE |
CA3035934C (en) | 2016-09-09 | 2024-03-26 | Bombardier Inc. | Automatic arming of aircraft steep approach function |
US11275388B2 (en) * | 2018-11-13 | 2022-03-15 | Honeywell International Inc. | Systems and methods for an enhanced stable approach monitor |
WO2020121664A1 (en) * | 2018-12-14 | 2020-06-18 | 株式会社Nttドコモ | Information processing device |
US11155343B2 (en) * | 2018-12-17 | 2021-10-26 | The Boeing Company | Brake systems for aircraft and related methods |
CN112319145A (en) * | 2019-07-20 | 2021-02-05 | 陈泽明 | Safety protection wheel hub |
US11449077B2 (en) * | 2019-12-13 | 2022-09-20 | The Boeing Company | Method and computing system for identifying incorrect aircraft alignment |
US11282400B2 (en) * | 2020-07-27 | 2022-03-22 | Rockwell Collins, Inc. | Runway overrun awareness alerting system with discrete indicator |
CN113380075B (en) * | 2021-06-08 | 2022-02-08 | 东航技术应用研发中心有限公司 | Method and system for measuring landing air distance |
US20230136572A1 (en) * | 2021-10-28 | 2023-05-04 | Honeywell International Inc. | Systems and methods for monitoring and providing alerts for takeoff runway intersections |
CN115959286B (en) * | 2023-03-17 | 2023-06-06 | 商飞软件有限公司 | Civil aircraft landing automatic brake control system and control method thereof |
Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4120540A (en) * | 1973-09-06 | 1978-10-17 | The Boeing Company | Aircraft automatic braking system |
US4122522A (en) * | 1974-05-20 | 1978-10-24 | Smith Gerald R | Aircraft ground monitoring system |
US4454582A (en) * | 1979-07-23 | 1984-06-12 | The Boeing Company | Method and apparatus for continuously determining a chronodrasic interval |
US4638437A (en) * | 1984-06-25 | 1987-01-20 | The Boeing Company | Aircraft performance margin indicator |
US5499025A (en) * | 1987-08-06 | 1996-03-12 | The United States Of America As Represented By The Administrator Of The National Aeronautics And Space Administration | Airplane takeoff and landing performance monitoring system |
US5968106A (en) * | 1997-08-05 | 1999-10-19 | The Boeing Company | Aircraft stop-to-position autobrake control system |
US6591171B1 (en) * | 1996-05-14 | 2003-07-08 | Honeywell International Inc. | Autonomous landing guidance system |
Family Cites Families (23)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
GB1178673A (en) * | 1966-01-29 | 1970-01-21 | Elliott Brothers London Ltd | Improvements in and relating to the Control of Aircraft |
US4043194A (en) * | 1976-08-20 | 1977-08-23 | Tanner Jesse H | Wind shear warning system |
US4368517A (en) * | 1978-03-16 | 1983-01-11 | Bunker Ramo Corporation | Aircraft landing display system |
US5077673A (en) * | 1990-01-09 | 1991-12-31 | Ryan International Corp. | Aircraft traffic alert and collision avoidance device |
US5591171A (en) * | 1991-06-14 | 1997-01-07 | Brown; Byron L. | Adapter and method for measuring pressures of fluid materials |
FR2717935B1 (en) * | 1994-03-24 | 1996-05-31 | Sextant Avionique | Method and device for preventing collisions of aerodynes with obstacles in relief. |
JP3849891B2 (en) * | 1996-09-09 | 2006-11-22 | ソニー株式会社 | Filter device and wireless communication terminal device |
US5904728A (en) * | 1996-10-11 | 1999-05-18 | Visteon Technologies, Llc | Voice guidance timing in a vehicle navigation system |
GB2322611B (en) * | 1997-02-26 | 2001-03-21 | British Aerospace | Apparatus for indicating air traffic and terrain collision threat to an aircraft |
JP3269441B2 (en) * | 1997-12-22 | 2002-03-25 | 三菱電機株式会社 | Weather radar equipment |
JP2001191276A (en) * | 1999-10-29 | 2001-07-17 | Sony Corp | Robot system, robot device and exterior thereof |
US6473003B2 (en) * | 2000-05-15 | 2002-10-29 | United Parcel Service Of America, Inc. | Selectable range ring for an ADS-B CDTI cockpit display |
US6765495B1 (en) * | 2000-06-07 | 2004-07-20 | Hrl Laboratories, Llc | Inter vehicle communication system |
EP1309837B1 (en) * | 2000-08-18 | 2006-12-13 | Honeywell International Inc. | Glideslope monitor for aircraft |
US6683556B2 (en) * | 2000-10-10 | 2004-01-27 | Sandel Avionics, Inc. | Method and apparatus for predictive altitude display |
US6792340B2 (en) * | 2001-05-01 | 2004-09-14 | Ronald Dunsky | Apparatus and method for providing live display of aircraft flight information |
US20030055951A1 (en) * | 2001-08-01 | 2003-03-20 | Chemali Emilio F. | Products, apparatus and methods for handling computer software/hardware messages |
US6801158B2 (en) * | 2001-09-20 | 2004-10-05 | Honeywell International Inc. | Annunciation of the distance to a target position in a global positioning system landing system |
US6965816B2 (en) * | 2001-10-01 | 2005-11-15 | Kline & Walker, Llc | PFN/TRAC system FAA upgrades for accountable remote and robotics control to stop the unauthorized use of aircraft and to improve equipment management and public safety in transportation |
US6828921B2 (en) * | 2001-12-05 | 2004-12-07 | The Boeing Company | Data link clearance monitoring and pilot alert sub-system (compass) |
US6748325B1 (en) * | 2001-12-07 | 2004-06-08 | Iwao Fujisaki | Navigation system |
US6720891B2 (en) * | 2001-12-26 | 2004-04-13 | The Boeing Company | Vertical situation display terrain/waypoint swath, range to target speed, and blended airplane reference |
JP4068494B2 (en) * | 2003-04-08 | 2008-03-26 | アルパイン株式会社 | Communication data relay method and inter-vehicle communication system |
-
2003
- 2003-05-21 US US10/442,147 patent/US20040167685A1/en not_active Abandoned
-
2004
- 2004-10-26 US US10/972,328 patent/US6978205B2/en not_active Expired - Fee Related
-
2005
- 2005-07-29 US US11/192,267 patent/US20050261813A1/en not_active Abandoned
- 2005-07-29 US US11/192,278 patent/US7085630B2/en not_active Expired - Fee Related
Patent Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4120540A (en) * | 1973-09-06 | 1978-10-17 | The Boeing Company | Aircraft automatic braking system |
US4122522A (en) * | 1974-05-20 | 1978-10-24 | Smith Gerald R | Aircraft ground monitoring system |
US4454582A (en) * | 1979-07-23 | 1984-06-12 | The Boeing Company | Method and apparatus for continuously determining a chronodrasic interval |
US4638437A (en) * | 1984-06-25 | 1987-01-20 | The Boeing Company | Aircraft performance margin indicator |
US5499025A (en) * | 1987-08-06 | 1996-03-12 | The United States Of America As Represented By The Administrator Of The National Aeronautics And Space Administration | Airplane takeoff and landing performance monitoring system |
US6591171B1 (en) * | 1996-05-14 | 2003-07-08 | Honeywell International Inc. | Autonomous landing guidance system |
US5968106A (en) * | 1997-08-05 | 1999-10-19 | The Boeing Company | Aircraft stop-to-position autobrake control system |
Cited By (27)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20110022291A1 (en) * | 2005-10-13 | 2011-01-27 | Honeywell International Inc. | Perspective-view visual runway awareness and advisory display |
US8594916B2 (en) * | 2005-10-13 | 2013-11-26 | Honeywell International Inc. | Perspective-view visual runway awareness and advisory display |
US20070208466A1 (en) * | 2006-01-03 | 2007-09-06 | Thales | System and method to assist in the braking of an aircraft on a landing runway |
US20100299005A1 (en) * | 2006-01-03 | 2010-11-25 | Thales | System and method to assist in the braking of an aircraft on a landing runway |
US20100299004A1 (en) * | 2006-01-03 | 2010-11-25 | Thales | System and method to assist in the braking of an aircraft on a landing runway |
US8478460B2 (en) * | 2006-01-03 | 2013-07-02 | Thales | System and method to assist in the braking of an aircraft on a landing runway |
US8515601B2 (en) | 2006-01-03 | 2013-08-20 | Thales | System and method to assist in the braking of an aircraft on a landing runway |
FR2895726A1 (en) * | 2006-01-03 | 2007-07-06 | Thales Sa | Aircraft`s braking intensity adjustment providing method for use in airport, involves recovering data concerning aircraft or runway when aircraft is landing, and acquiring position of aircraft on runway and speed in taxiing phase |
US8600586B2 (en) * | 2009-02-04 | 2013-12-03 | Honeywell International Inc. | Stable approach monitor (SAM) system |
US20100198432A1 (en) * | 2009-02-04 | 2010-08-05 | Honeywell International Inc. | Stable approach monitor (sam) system |
US8903572B1 (en) * | 2009-08-11 | 2014-12-02 | The Boeing Company | Aircraft landing evaluation system |
US20130218374A1 (en) * | 2012-02-22 | 2013-08-22 | Honeywell International Inc. | Display system and method for generating a display |
EP2654029A3 (en) * | 2012-02-22 | 2016-07-13 | Honeywell International Inc. | Method for generating a flight display |
US9934692B2 (en) * | 2012-02-22 | 2018-04-03 | Honeywell International Inc. | Display system and method for generating a display |
US20140257601A1 (en) * | 2013-03-06 | 2014-09-11 | Gulfstream Aerospace Corporation | Runway overrun monitor |
US9221554B2 (en) * | 2013-03-06 | 2015-12-29 | Gulfstream Aerospace Corporation | Runway overrun monitor |
US10227140B2 (en) | 2014-07-11 | 2019-03-12 | Cmc Electronics Inc | System and method for detecting and alerting the user of an aircraft of an impendent adverse condition |
US10152195B2 (en) | 2015-12-14 | 2018-12-11 | Honeywell International Inc. | Aircraft display system pertaining to energy management |
US20180208165A1 (en) * | 2016-12-28 | 2018-07-26 | Hydro-Aire, Inc. | System and method for simplified aircraft brake distance estimation |
WO2018125866A1 (en) * | 2016-12-28 | 2018-07-05 | Hydro-Aire, Inc. | System and method for simplified aircraft brake distance estimation |
US10814842B2 (en) * | 2016-12-28 | 2020-10-27 | Hydro-Aire, Inc. | System and method for simplified aircraft brake distance estimation |
US20180273200A1 (en) * | 2017-03-27 | 2018-09-27 | Honeywell International Inc. | Avionic display systems and methods for generating vertical situation displays including instability prediction and avoidance symbology |
US10654589B2 (en) * | 2017-03-27 | 2020-05-19 | Honeywell International Inc. | Avionic display systems and methods for generating vertical situation displays including instability prediction and avoidance symbology |
US20190112073A1 (en) * | 2017-10-12 | 2019-04-18 | Rosemount Aerospace Inc. | Automated aircraft landing performance analysis |
US11021263B2 (en) * | 2017-10-12 | 2021-06-01 | Rosemount Aerospace Inc. | Automated aircraft landing performance analysis |
US10839701B2 (en) | 2018-06-05 | 2020-11-17 | Honeywell International Inc. | Methods and systems for stabilized approach energy management |
US10854091B2 (en) | 2018-07-03 | 2020-12-01 | Honeywell International Inc. | Energy management visualization methods and systems |
Also Published As
Publication number | Publication date |
---|---|
US6978205B2 (en) | 2005-12-20 |
US7085630B2 (en) | 2006-08-01 |
US20050261814A1 (en) | 2005-11-24 |
US20040167685A1 (en) | 2004-08-26 |
US20050182531A1 (en) | 2005-08-18 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7085630B2 (en) | Method and apparatus for predicting runway overrun | |
US9058742B2 (en) | Methods for illustrating aircraft situational information | |
US8825238B2 (en) | Aircraft systems and methods for monitoring energy height | |
US10134289B2 (en) | Methods and systems facilitating stabilized descent to a diversion airport | |
EP2135806B1 (en) | Method and apparatus for improving pilot situational awareness during flare to touchdown | |
EP3012590B1 (en) | System and method for displaying runway landing information | |
US7772992B2 (en) | Method and device for assisting the ground navigation of an aeroplane in an airport | |
US9199724B2 (en) | System and method for performing an aircraft automatic emergency descent | |
US9008873B1 (en) | Methods and systems for landing decision point | |
US10839701B2 (en) | Methods and systems for stabilized approach energy management | |
WO2003107299A2 (en) | Method and device for protection against runway incursions | |
US9583010B1 (en) | Vertical path profile generating system, device, and method | |
US10854091B2 (en) | Energy management visualization methods and systems | |
US20090292408A1 (en) | System and method for communicating intent of aircraft | |
US11074823B2 (en) | System for aiding the landing of an aircraft in a landing runway approach phase | |
US8224506B2 (en) | Method and device for determining a maximum stabilization height in the final flight phase of an airplane | |
US10514707B1 (en) | Flight phase stability indicator system and method | |
EP3696792A1 (en) | Systems and methods for alerting improper inhibition of warning systems | |
US20180079495A1 (en) | Systems and methods for forecasting and reducing the occurrence of tire overspeed events during aircraft takeoff and landing | |
EP3626552A1 (en) | Systems and methods for optimizing landing performance | |
EP3306593B1 (en) | Method and system for determining effective approach angle and predicting aircraft landing distance | |
US20220189324A1 (en) | System and method to reduce runway occupancy time using pseudo threshold | |
EP4012684A1 (en) | Dynamic radar vectoring guidance methods and systems | |
US11842629B2 (en) | Dynamic radar vectoring guidance methods and systems | |
EP4012686A1 (en) | System and method to reduce runway occupancy time using pseudo threshold |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |