+

WO2003107299A2 - Procede et dispositif de protection contre des incursions de pistes - Google Patents

Procede et dispositif de protection contre des incursions de pistes Download PDF

Info

Publication number
WO2003107299A2
WO2003107299A2 PCT/US2003/009508 US0309508W WO03107299A2 WO 2003107299 A2 WO2003107299 A2 WO 2003107299A2 US 0309508 W US0309508 W US 0309508W WO 03107299 A2 WO03107299 A2 WO 03107299A2
Authority
WO
WIPO (PCT)
Prior art keywords
aircraft
data
incursion
protected area
airport
Prior art date
Application number
PCT/US2003/009508
Other languages
English (en)
Other versions
WO2003107299A3 (fr
Inventor
William C. Brodegard
Dean E. Ryan
Original Assignee
Ryan International Corporation
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Ryan International Corporation filed Critical Ryan International Corporation
Priority to AU2003269807A priority Critical patent/AU2003269807A1/en
Publication of WO2003107299A2 publication Critical patent/WO2003107299A2/fr
Publication of WO2003107299A3 publication Critical patent/WO2003107299A3/fr

Links

Classifications

    • G—PHYSICS
    • G08—SIGNALLING
    • G08G—TRAFFIC CONTROL SYSTEMS
    • G08G5/00—Traffic control systems for aircraft
    • G08G5/50—Navigation or guidance aids
    • G08G5/51—Navigation or guidance aids for control when on the ground, e.g. taxiing or rolling
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B64—AIRCRAFT; AVIATION; COSMONAUTICS
    • B64F—GROUND OR AIRCRAFT-CARRIER-DECK INSTALLATIONS SPECIALLY ADAPTED FOR USE IN CONNECTION WITH AIRCRAFT; DESIGNING, MANUFACTURING, ASSEMBLING, CLEANING, MAINTAINING OR REPAIRING AIRCRAFT, NOT OTHERWISE PROVIDED FOR; HANDLING, TRANSPORTING, TESTING OR INSPECTING AIRCRAFT COMPONENTS, NOT OTHERWISE PROVIDED FOR
    • B64F1/00—Ground or aircraft-carrier-deck installations
    • B64F1/002—Taxiing aids

Definitions

  • the present invention relates generally to instruments that warn against or prevent runway incursions.
  • a runway incursion occurs whenever an airplane, vehicle, person, or other object on the ground enters an area of an airport in which it creates a collision hazard with another airplane that is taking off or landing at an airport.
  • pilots have relied on visual aids such as airfield markings (e.g., painted center lines), signs, and lighting, used in conjunction with a chart of the airport in order to navigate the airfield surface. Pilots may also receive via radio a taxi route from air traffic control (ATC) to follow while on the airfield surface. The pilot must then memorize or record the taxi route, re-state it to the controller for confirmation, and then follow airfield markings while avoiding other surface traffic and obstructions.
  • ATC air traffic control
  • the ground controller must remember the taxi routes given to all aircraft and monitor aircraft movements so that no aircraft is directed into a potential conflict. Aircraft flight crews navigate on the airport surface primarily by sight to ascertain positions along their assigned taxi route. When in doubt of their location, the ground controller (if one is available) can be queried by radio.
  • the FAA has also initiated a long-term strategy for mitigating runway incursion focusing on airport infrastructure upgrades and improving the ATC surface surveillance picture.
  • an aircraft carried device for providing incursion information comprises a processor that receives inputs of aircraft data defining, for example, a position, velocity and acceleration of the aircraft, and that determines when the aircraft commits an incursion of a runway (or, more generally, a "protected area") of an airport or when an incursion is likely.
  • the device may also include at least one alert device coupled to the processor, wherein the at least one alert device is responsive to the processor and generates a warning condition when the aircraft commits an incursion or is likely to commit an incursion of a protected area.
  • the aircraft pilot or other operator is provided with information to validate or possibly override a controller's order, and the pilot can avoid runway incursions at both towered and non-towered airports.
  • a runway incursion monitoring method comprises receiving aircraft data aboard an aircraft defining at least the aircraft's position, receiving airport data aboard the aircraft defining protected areas of an airport, determining whether the aircraft commits an incursion or is likely to commit an incursion of a protected area, and generating a warning condition if the aircraft commits an incursion or if the aircraft is likely to commit an incursion.
  • the pilot is warned when a runway incursion has occurred or is likely to occur. The pilot may then take corrective action to avoid a collision or other disruption of airport operations.
  • FIG. 1 illustrates a segment of an airport.
  • FIG. 2 illustrates a first embodiment of a runway incursion monitor.
  • FIG. 3 illustrates a second embodiment of a runway incursion monitor.
  • FIG. 4 illustrates a third embodiment of a runway incursion monitor.
  • FIG. 5 illustrates a method for monitoring runway incursions.
  • FIG. 6 illustrates an alternative method for monitoring runway incursions.
  • FIG. 7 illustrates a method for operating an runway incursion device.
  • FIG. 1 illustrates a segment of an airport 100.
  • Airport layouts may vary substantially, and FIG. 1 is therefore merely an example of an airport layout to explain the operation of the runway incursion monitor embodiments disclosed herein.
  • the airport segment 100 comprises a runway 10, a first taxiway 15, a second taxiway 55, and a plurality of hold short lines 80a, 80b, 80c, and 80d.
  • a protected runway exclusion area 20 (the shaded area in FIG. 1), or simply "protected area” 20, is bounded by a boundary 22.
  • the boundary 22 generally comprises the hold short lines 80a, 80b, 80c, 80d, and the outer boundaries ofthe runway 10 that are indicated by bold outline.
  • the protected area 20 can be defined as an area that is reserved to an aircraft that is either taking off or preparing to take off, or landing on the runway 20.
  • an aircraft 90 is taking off, and an aircraft 92 is taxiing on the second taxiway 55.
  • an aircraft having a runway incursion monitor can avoid inadvertently or improperly entering the protected area 20. For example, the pilot ofthe aircraft 92 having a runway incursion monitor could be warned against entering the protected area 20 during taxiing.
  • the boundary 22 may alternatively comprise "extended" hold short lines 81a, 81b, 81c, and 8 Id. Extending the boundary 22 of the protected area 20 provides a greater safety margin to the pilot of the aircraft 92. Any portion of the boundary 22 may be extended in this way. The boundary 22 may be extended outward an arbitrary distance, according to the desired increase in safety.
  • FIG. 2 illustrates a first embodiment of a runway incursion monitor 200.
  • the runway incursion monitor 200 functions to insure that an aircraft 92 (see FIG. 1) carrying an incursion monitor does not cross the boundary 22 of the protected area 20 without advance warning to the pilot, or, to warn the pilot when her aircraft has already entered the protected area. Intrusions into, or "incursions" of the protected areas of the airport are thereby avoided.
  • the runway incursion monitor 200 comprises a data processor 220 coupled to a source 230 of position data.
  • the source 230 of position data can be, for example, a global positioning system (GPS) mounted on the aircraft.
  • An airport mapping database (AMDB) 210 is also coupled to the data processor 220 and includes airport data descriptive of the airport.
  • the AMDB 210 may include, for example, a digital description of some or all of the airport's surface operating areas for aircraft, including, for example, areas such as ramps, taxiways, and runways, and hold short boundaries.
  • One embodiment of an AMDB may comprise a CD-ROM having a description of airport geography.
  • the AMDB 210 can be mounted on the aircraft and coupled to the data processor 220.
  • the AMDB 210 could be a database formed by data describing the airport geography, broadcasted to the aircraft from the airport ATC.
  • the data processor 220 may be coupled to alert devices such as, for example, an audio indicator 240 and a visual indicator 260.
  • the audio indicator 240 and the visual indicator 260 may emit audible and visual warnings, respectively, when an aircraft is likely to or has crossed a hold short boundary, or any other part ofthe boundary of a protected area.
  • the audio indicator 240 and the visual indicator 260 may also emit warnings or convey other information under other circumstances.
  • the visual indicator 260 can comprise one or more colored lights that may be illuminated to reflect different messages, such as yellow for "caution.”
  • the yellow caution light may, for example, be used to indicate that a runway incursion is likely to occur in the future.
  • a red light may indicate a runway incursion has already occurred.
  • a green light may indicate that there is no present likelihood of a runway incursion.
  • the data processor 220 may also be coupled to an input device 280.
  • the input device 280 allows the pilot or other device operator to utilize additional functions of the runway incursion monitor 200. The additional functions are described in detail below.
  • the input device 280 can comprise, for example, an input keypad, a keyboard, or one or more labeled buttons for use by the operator.
  • the runway incursion monitor 200 receives aircraft position data from the source 230 of position data, and airport surface operating area data from the airport mapping database AMDB 210. Referring back to FIG. 1, the data processor 220 can continually or intermittently compare the present position of the aircraft with the protected area 20 of the airport 100 defined by the border 22. Referring to FIGS. 1 and 2, the runway incursion monitor 200 registers a "warning condition" for the aircraft when the present position of the aircraft 92 makes a transition from the unprotected to the protected side of one of the hold short lines 80a-d, thereby violating the protected area 20.
  • the warning condition may include a warning from the indicators 240, 260.
  • the warning can be, for example, an audio warning from the audio indicator 240, a visual warning from the visual indicator 260, or a combination of audio and visual warnings.
  • the runway incursion monitor 200 may also provide an advance warning of an expected or likely incursion by the aircraft into a protected area. The warning condition is registered and a warning is provided before the aircraft actually violates the protected area.
  • One way for the runway incursion monitor 200 to provide advance warning is to use data such as aircraft data and airport descriptive data to predict when a runway incursion is likely to occur.
  • the data processor 220 can receive or calculate aircraft data, such as aircraft position and velocity, and predict the aircraft's position at some future time t. The prediction may be based on the assumption that the aircraft velocity will be maintained constant or relatively constant. Aircraft data such as acceleration may also be a factor in a more sophisticated application.
  • the airport characteristic data can be provided by the AMDB 210.
  • the data processor 220 will generate a warning condition, preferably activating one or more of the warning indicators 240, 260, if the predicted or expected aircraft position involves a transition from an unprotected to a protected side of a hold short line (i.e., an incursion of a protected area).
  • the warning condition can be registered and an audio/visual warning generated at the time the aircraft is expected to come within a preselected distance of a boundary, or at a predetermined time before an expected incursion of a protected area.
  • the runway incursion monitor 200 alerts a pilot of an expected or existing incursion of a protected area of an airport.
  • the audio indicator 240 may be, for example, a speaker in the cockpit ofthe aircraft, or an audio signal source coupled to headphones worn by the pilot.
  • the visual indicator 260 can be, for example, a display screen, or one or more lights. Other alert devices may be used in addition to or in lieu of these devices.
  • the pilot or other operator may deactivate one or more ofthe alert devices 240, 260 by acknowledging the warning condition using the input device 280.
  • FIG. 3 illustrates a second embodiment of a runway incursion monitor 300.
  • the runway incursion monitor 300 receives the aircraft data of position, velocity, and acceleration to more precisely predict the motion of an aircraft as a function of time.
  • One equation which can be used to describe position as a function of time is:
  • P(t) is the expected aircraft location at future time t
  • the runway incursion monitor 300 comprises a data processor 220 coupled to the airport mapping database 210, an audio indicator 240, a visual indicator 260, and an input device 280.
  • the data processor 220 is also coupled to sources of aircraft data, such as a source 230 of position data, a source 305 of linear velocity data, a source 310 of linear acceleration data, a source 320 of heading data, source 340 of angular velocity data, and a source 350 of angular acceleration data.
  • the linear velocity data, linear acceleration data, angular velocity data, and angular acceleration data can be derived from the position data and the heading data, or provided as individual inputs to the data processor 220.
  • the heading data and linear velocity data can be calculated from the position data, or provided as individual inputs to the data processor 220.
  • the operation ofthe monitor 300 is discussed in further detail below with reference to the method illustrated by FIG. 5.
  • FIG. 4 illustrates an embodiment of a runway incursion monitor 400 having additional devices that provide data to the data processor 220.
  • the runway incursion monitor 400 includes a data processor 220, an AMDB 210, an audio indicator 240, a visual indicator 260 and an input device 280, as are generally described with reference to the embodiments illustrated in FIGS. 2 and 3.
  • Additional devices include an air traffic control (ATC) data link 410, an airspeed sensor 420, a moving map display 430, a weight-on- wheels (WOW) sensor 435, and a laptop computer 460.
  • ATC air traffic control
  • WOW weight-on- wheels
  • the additional devices included in the runway incursion monitor 400 allow a more detailed and accurate calculation of when there is a likely or existing incursion of a protected area of an airport by an aircraft carrying the runway incursion monitor 400.
  • the ATC data link 410 provides data that can improve the accuracy of the position fix of the runway incursion monitor 400.
  • the ATC data link 410 can also be used to allow input of high speed data and the transmission of information to other monitors and to ATC personnel.
  • the airspeed sensor 420 indicates the airspeed of the aircraft.
  • the moving map 430 displays runways likely to be affected by a present or likely incursion.
  • the moving map 430 receives data from the data processor 220, and when an incursion warning is activated, the affected runway(s) are highlighted and/or displayed prominently on a moving map.
  • the WOW sensor 435 indicates whether there is weight supported by the aircraft's wheels.
  • the WOW data is used to determine when the aircraft is airborne.
  • the laptop computer 460 may be used by the pilot to, for example, input taxi
  • the runway incursion monitor 400 can utilize the inputs of latitude, longitude, altitude, velocity, acceleration as discussed with reference to FIGS. 3 and 4.
  • the source of these data is illustrated as a source 470 of position data.
  • FIG. 5 illustrates a method for monitoring runway incursions.
  • the method illustrated in FIG. 5 can be used to determine whether an aircraft carrying a runway incursion monitor has committed an incursion of a protected area or will likely commit an incursion.
  • the method can be performed using the runway aircraft incursion monitors 200, 300 or 400 described above.
  • step 510 the processor 220 determines the present position of the aircraft on which the monitor is carried using aircraft position data.
  • step 515 the motion parameters of the aircraft are determined.
  • the motion parameters may include aircraft data such as the aircraft's linear velocity, linear acceleration, heading, angular velocity and angular acceleration, depending upon the inputs available to or requested by the data processor 220.
  • step 520 determines whether the aircraft is airborne. This determination is made according to the sensor inputs available to the processor 220. For example, referring to FIG. 4, the WOW sensor 435 output can be used to determine whether the aircraft is airborne. Other devices and methods useful to determine whether the aircraft is airborne include, for example, a switch operable by the pilot, a "landing gear down" sensor, and a comparison of the aircraft altitude with the altitude of the terrain at the aircraft's position. The airspeed or groundspeed of the aircraft can also be used to determine whether the aircraft is airborne.
  • step 520 If the aircraft is traveling at a speed above a minimum value, such as 45 knots, it is likely that the aircraft is either airborne or in a takeoff condition, because aircraft seldom taxi at a speed of 45 knots or greater. [42] If it is determined at step 520 that the aircraft is airborne, any current warning conditions are cleared in step 530. In general, if the aircraft is airborne, then runway incursion prevention is not required.
  • step 540 is performed to determine if the aircraft is accelerating towards takeoff.
  • the aircraft's present position locates it on a runway and the aircraft's acceleration is positive, then a conclusion could be drawn that the aircraft is accelerating towards takeoff.
  • a positive acceleration can be determined in the data processor 220 according to data from the source 310 of linear acceleration data. If the processor 220 determines that the aircraft is accelerating toward takeoff, existing warning conditions are cleared in step 530.
  • step 550 is performed to determine if there is a current warning condition.
  • a current warning condition may exist if an incursion or a likely incursion was detected in a previous execution of the runway incursion method. If there is no current warning condition, step 560 is performed to calculate an expected future position ofthe aircraft.
  • the future position may be calculated according to equation (1) recited above, for example. A more sophisticated calculation can incorporate, for example, angular acceleration values.
  • the future position of the aircraft is calculated in order to determine whether the aircraft is in danger of violating a protected area.
  • the future position ofthe aircraft may be calculated to predict the aircraft's expected position at a selected future time t.
  • the time t can be selected to provide sufficient response time to the pilot before the aircraft actually crosses a boundary of a protected area. For example, a future time t of 20 seconds would provide a pilot sufficient time to alter the aircraft's path if it is in danger of committing an incursion into a protected area. A shorter time can be used to avoid unnecessary warnings.
  • the future position at time t may be calculated based on some or all of the known aircraft data, including the motion parameters of linear velocity, angular velocity, linear acceleration, angular acceleration, and heading, and the present position ofthe aircraft.
  • step 570 determines if the future position would result in an incursion of a protected area.
  • the hold short lines can be "extended" outward an arbitrary amount to increase the margin of safety.
  • the protected area may thereby be extended as shown in FIG. 1, where hold short lines 81a-81d provide an extended protected area 20.
  • each of the hold short lines, or other boundaries of a protected area can be extended 10-20 feet outward.
  • the additional distance increases the time available for the pilot to react to a likely incursion of a protected area.
  • the processor 220 can determine whether the aircraft comes within a minimum distance of the boundary of the protected area. If so, the processor can conclude that an incursion is likely. The distance can be dependent upon the velocity ofthe aircraft, so that sufficient time is allotted to warn the pilot of a fast-moving aircraft.
  • step 570 if an incursion is likely to occur at future time t, then a warning condition is generated in step 580.
  • the warning condition can include a warning signal that can be an audio signal, a visual signal, a combination thereof, or an alternative signal designed to warn the pilot of a possible incursion of a protected area. If no incursion is determined to be likely at time t, the method returns to step 530 where warning conditions are cleared.
  • step 550 if there is a current warning condition, the processor 220 determines whether the aircraft is inside a protected area in step 590. This condition can be determined by comparing the present aircraft position with airport data from the AMDB 210. If at step 590 it is determined that the aircraft is currently within a protected area, then step 592 is performed to determine if the pilot has acknowledged the current warning condition determined in step 550. The pilot can acknowledge a current warning condition by, for example, inputting data at the input device 280 (see FIG. 2). If the pilot has not acknowledged the current warning condition, the warning condition is maintained as "active" in step 598. The method then returns to step 510. If the warning condition is active, the warning indicators 240, 260 can continue to produce warning signals.
  • the pilot may, at her option, mute an audio warning signal, while maintaining a visual warning signal. [50] If the pilot has acknowledged a warning condition, the warning condition is cleared in step 596. The future position of the aircraft is then calculated in step 560 and the method proceeds as described above.
  • step 590 if the aircraft is not determined to be in a protected area, the warning condition determined in step 550 is cleared in step 596. The future position of the aircraft is then calculated in step 560 and the method proceeds as described above.
  • the input device 280 allows several additional functions to be performed by the runway incursion monitors described above. For example, when the aircraft turns and stops at a runway, the data processor 220 recognizes the aircraft is holding short. At this time, the visual indicator 260 may give a status indication, such as, for example, an illuminated yellow status light. An audible announcement of status may also accompany the visual indication.
  • An input at the input device 280 can be used to elicit a current location or status of the aircraft such as: "HOLDING SHORT, RUNWAY 9-27, INTERSECTION TAXIWAY BRAVO. RUNWAY 9, RIGHT TURN, 5000 FEET REMAINING.
  • the airport mapping database 210 may contain the digital data necessary for the data processor 220 to compare the aircraft's current position to the airport geography, including runways and other protected areas ofthe airport.
  • the AMDB can also extract a verbal text string indicating the status ofthe aircraft, for use by the flight crew.
  • the runway incursion monitor can also indicate a landing status for an aircraft. For example, when an embodiment of a runway incursion monitor is in use aboard an aircraft that is preparing to land, the runway incursion monitor can issue a reminder to indicate that the aircraft is cleared to land, and may allow verification that the aircraft is aligned with the correct runway. For example, when in the air, on final approach, the pilot can input a query at the input device 280 to determine whether ATC has granted clearance to land.
  • the visual indicator 260 can respond with a positive (e.g., a green light) or a negative (e.g., a red light) indication as to landing clearance. Audio indications may also be generated.
  • the query by the pilot can be the press of a button, or a more detailed input at, for example, a keyboard.
  • a second input at the input device 280 can be entered after entering final approach to task the runway incursion monitor to announce the assigned runway.
  • the assigned runway can be displayed on the visual indicator 260, or announced over the audio indicator 240.
  • the landing clearance and the announced runway should be the same. If not, corrective action can be taken before the flare.
  • the data processor 220 can be set to alarm when the future position is greater than a predetermined distance from the assigned taxi route. In this embodiment the data processor 220 determines the distance between the taxi route and the future position and between the future position and the nearest protected boundary.
  • FIG. 6 illustrates an alternative method for monitoring runway incursions.
  • the aircraft position is determined.
  • aircraft motion parameters such as velocity, acceleration, heading, angular velocity and angular acceleration are determined.
  • the data processor 220 compares the aircraft position with the airport data from the AMDB 210 to determine if the aircraft's present position is on a runway. If the aircraft is on a runway, the processor 220 assumes that an incursion has not occurred and that the pilot does not require a warning. The method then returns to step 610.
  • step 640 determines if the aircraft is airborne. If the aircraft is not airborne, then a future predicted position is determined in step 650. The future position may be calculated by projecting the present position at a time t along the trajectory described by the simultaneous solution of linear and angular motion algorithms.
  • step 660 the predicted position and the present position of the aircraft are compared to the protected area 20 to determine if the predicted or the present position lie in a protected area 20. If yes, in step 670, the processor 220 determines whether it is physically possible for the aircraft to travel from its present position to its predicted position (if the present position is in a protected area a path is considered to exist). An arc drawn between the aircraft's present position and its predicted position at time t is the track that the aircraft will follow as it taxis. If a continuous surface approved for transit by aircraft does not exist between the present position and the predicted position, the processor 220 assumes that the aircraft will not follow the predicted route and that the incursion from that predicted position will not occur. Therefore, a warning condition is not generated and the method returns to step 610.
  • step 680 determines if the aircraft is holding short awaiting permission to enter the runway. Since the aircraft is next to the boundary ofthe protected area when holding short (see FIG. 1), it is possible that the predicted position may be in the protected area. Warning the pilot of an impending runway incursion when holding short would be an erroneous warning, and could distract the pilot. Therefore, if the aircraft is holding short, the alert devices 240, 260 are not activated. Alternatively, the alert devices 240, 260 can give an indication that the aircraft is holding short. The status of holding short can be input, for example, by the pilot at the input device 280.
  • a warning condition is generated in step 690.
  • the warning condition can include activation of the audio indicator 240 and the video indicator 260.
  • An audio warning could be in the format of: "CAUTION RUNWAY 09-27 AHEAD" wherein 09-27 is the runway number.
  • the visual indicator 260 can display the foregoing message in flashing text, for example. Alternatively, a red lamp may be lighted in the view of the pilot.
  • a moving map such as the moving map 430 illustrated in FIG. 4, can display the affected runway, and the predicted incursion point.
  • the input device 280 may be used to acknowledge the approach to the runway, such as when the processor 220 determines that an incursion is likely. If the pilot acknowledges the warning condition in step 695, the warning condition is cleared in step 697 and the method returns to step 610. If the pilot does not acknowledge the warning condition, the warnings from the devices 240, 260 may continue until the pilot acknowledges or corrects the condition.
  • the input device 280 can include a "mute/position update" button. A method of enabling the mute and position update functions is discussed below with reference to FIG. 7.
  • the runway incursion monitor embodiments discussed above may use position data from the source 230 of position data as the only external data source.
  • the source 230 may be, for example, a GPS receiver on the aircraft that is in communication with the processor 220.
  • an inertial navigation system could be included on the aircraft to provide position and motion data to the processor 220. If not using velocity and acceleration information, the data processor 220 prediction algorithms may be simplified by setting the predicted aircraft position at time t equal to the present aircraft position.
  • the incursion monitor 200 may advantageously generate a warning condition when the aircraft reaches a predetermined distance from the protected area.
  • step 560 can be replaced with a step in which the processor 220 determines a predetermined distance from a protected area.
  • Step 570 would accordingly register a likely incursion if the aircraft is located within the predetermined distance of the protected area.
  • step 650 could be used to determine the predetermined distance from the protected area boundaries
  • step 660 could register a likely incursion if the aircraft passed into the predetermined distance.
  • the extended hold short boundaries 81a-81d could be used to define the predetermined distance from the boundary 22.
  • the data processor 220 may routinely calculate the distance between the aircraft's present position and a protected area, in addition to calculating the predicted position of the aircraft. Therefore, if a failure in the runway incursion monitor were to disrupt the future position calculation, a backup function could warn the pilot that the aircraft is near the protected area. This function could be used if, for example, the runway incursion monitor had no access to velocity data.
  • the data processor 220 may set aircraft velocity to zero and the future position prediction algorithms may set the future position equal to the present position.
  • a warning condition will be generated (i.e., the processor 220 determines that an incursion is likely) if the aircraft moves within the preselected distance.
  • the airport mapping database can include a complete description of the airport environment, including the location of all hold short lines, for example. If particular sets of data are not provided to the airport mapping database, airport characteristics such as the location of hold short lines can be instead be determined and stored in the airport mapping database. For example, if the airport mapping database lacks data defining hold short lines, hold short lines can be determined using available airport database and FAA hold short line criteria. The "extended" hold short lines discussed above may also be determined and stored.
  • FIG. 7 illustrates an example of a method of operating a runway incursion monitor embodiments discussed above.
  • the input device 280 can be a single button.
  • Step 710 illustrates a state where a warning condition exists and both audio and visual warnings are given by the audio indicator 240 and the visual indicator 260, respectively.
  • the warning condition in this example can exist due to a likely incursion at a future time t, and the visual warning is a yellow light. If the aircraft had already crossed a boundary of a protected area, the light could be red.
  • a single press of the input button 280 mutes the audio indicator 240 (step 730), so that the pilot is not unnecessarily distracted.
  • step 740 the pilot presses the button 280 a second time and obtains a position update via the audio indicator 240.
  • the position update may also include an alert as to the next airport feature in the path ofthe aircraft.
  • the yellow warning light can remain on.
  • the runway incursion monitor monitors aircraft status when the aircraft is stopped short.
  • the input device 280 can be a single button.
  • the runway incursion device 200 may recognize that the aircraft 92 is holding short.
  • the visual indicator 260 can display a yellow light, but no audible announcement is made.
  • a double- press ofthe button can be used elicit a current location on the airport announcement such as: "HOLDING SHORT, RUNWAY 9-27, INTERSECTION TAXIWAY BRAVO. RUNWAY 9, RIGHT TURN, 5000 FEET REMAINING. RUNWAY 27, LEFT TURN, TWO THOUSAND FIVE HUNDRED FEET REMAINING.”
  • pilots of aircraft having a runway incursion monitor have higher situational awareness in the airport environment. Higher situational awareness reduces the number of runway incursions at towered airports, thereby increasing safety.

Landscapes

  • Engineering & Computer Science (AREA)
  • Aviation & Aerospace Engineering (AREA)
  • Mechanical Engineering (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Traffic Control Systems (AREA)

Abstract

L'invention concerne un dispositif d'incursion de piste compris dans un avion comportant un signal d'avertissement de sortie ou d'incursion probable de piste. Ce dispositif permet de déterminer des positions actuelles et futures de l'avion et d'établir, si l'avion a commis ou va commettre une incursion de piste. Ce dispositif peut utiliser des entrées provenant d'un système de positionnement global, afin de déterminer la position de l'avion et d'autres données de déplacement concernant l'avion. Ledit dispositif peut aussi utiliser des données provenant d'une base de données de mappage d'aéroport, afin de déterminer quelles parties de l'aéroport constituent des zones de pistes protégées. Si le dispositif détermine qu'une incursion de piste a eu lieu ou va probablement avoir lieu, un signal d'avertissement peut être produit pour avertir le pilote.
PCT/US2003/009508 2002-04-01 2003-03-31 Procede et dispositif de protection contre des incursions de pistes WO2003107299A2 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU2003269807A AU2003269807A1 (en) 2002-04-01 2003-03-31 Method and device for protection against runway incursions

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US36853902P 2002-04-01 2002-04-01
US60/368,539 2002-04-01
US31511402A 2002-12-10 2002-12-10
US10/315,114 2002-12-10

Publications (2)

Publication Number Publication Date
WO2003107299A2 true WO2003107299A2 (fr) 2003-12-24
WO2003107299A3 WO2003107299A3 (fr) 2004-06-17

Family

ID=29739307

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2003/009508 WO2003107299A2 (fr) 2002-04-01 2003-03-31 Procede et dispositif de protection contre des incursions de pistes

Country Status (2)

Country Link
AU (1) AU2003269807A1 (fr)
WO (1) WO2003107299A2 (fr)

Cited By (35)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2005086107A2 (fr) 2004-02-28 2005-09-15 Honeywell International Inc. Systeme de sensibilisation et de conseil pour pistes d'aeroports
US7079951B2 (en) 2002-05-15 2006-07-18 Honeywell International Inc. Ground operations and imminent landing runway selection
WO2006106210A1 (fr) 2005-04-04 2006-10-12 Airbus France Procédé et dispositif d'aide à la navigation au sol d'un avion sur un aéroport
WO2006111480A1 (fr) * 2005-04-22 2006-10-26 Thales Procede et dispositif embarque, pour aeronef, d'alerte d'incursion de piste
FR2891644A1 (fr) * 2005-09-30 2007-04-06 Thales Sa Procede et dispositif d'aide pour la circulation d'un mobile a la surface d'un aeroport.
FR2891646A1 (fr) * 2005-09-30 2007-04-06 Thales Sa Procede et dispositif embarque d'aide au roulage dans un aeroport.
FR2891645A1 (fr) * 2005-09-30 2007-04-06 Thales Sa Procede et dispositif d'evaluation de la liceite de la situation d'un mobile sur la surface d'un aeroport.
WO2007093301A1 (fr) * 2006-02-18 2007-08-23 Heinz Wipf Procédé et dispositif destinés à empêcher qu'un objet mobile ne pénètre dans une section d'une voie de circulation
EP1835369A2 (fr) 2005-09-19 2007-09-19 Honeywell International Inc. Système d'évitement d'incursion de base et affichage
WO2008035981A2 (fr) * 2006-09-19 2008-03-27 Unified Messaging Systems As Procédé et système de prévention des accidents
WO2009090185A2 (fr) * 2008-01-18 2009-07-23 Heinz Wipf Procédé et système pour empêcher un objet mobile d'entrer dans une section protégée
US7587278B2 (en) 2002-05-15 2009-09-08 Honeywell International Inc. Ground operations and advanced runway awareness and advisory system
US7612716B2 (en) 1999-03-05 2009-11-03 Era Systems Corporation Correlation of flight track data with other data sources
US7667647B2 (en) 1999-03-05 2010-02-23 Era Systems Corporation Extension of aircraft tracking and positive identification from movement areas into non-movement areas
US7739167B2 (en) 1999-03-05 2010-06-15 Era Systems Corporation Automated management of airport revenues
US7777675B2 (en) 1999-03-05 2010-08-17 Era Systems Corporation Deployable passive broadband aircraft tracking
US7782256B2 (en) 1999-03-05 2010-08-24 Era Systems Corporation Enhanced passive coherent location techniques to track and identify UAVs, UCAVs, MAVs, and other objects
US7889133B2 (en) 1999-03-05 2011-02-15 Itt Manufacturing Enterprises, Inc. Multilateration enhancements for noise and operations management
US7908077B2 (en) 2003-06-10 2011-03-15 Itt Manufacturing Enterprises, Inc. Land use compatibility planning software
US7965227B2 (en) 2006-05-08 2011-06-21 Era Systems, Inc. Aircraft tracking using low cost tagging as a discriminator
EP2259245A3 (fr) * 2009-06-02 2011-10-19 Honeywell International Inc. Système d'alarme de surface d'aéroport fermé
US8072382B2 (en) 1999-03-05 2011-12-06 Sra International, Inc. Method and apparatus for ADS-B validation, active and passive multilateration, and elliptical surveillance
US8203486B1 (en) 1999-03-05 2012-06-19 Omnipol A.S. Transmitter independent techniques to extend the performance of passive coherent location
WO2012172183A1 (fr) * 2011-06-16 2012-12-20 Tracker Oy Procédé d'avertissement et agencement pour une cible mobile
US8446321B2 (en) 1999-03-05 2013-05-21 Omnipol A.S. Deployable intelligence and tracking system for homeland security and search and rescue
EP2211324B1 (fr) * 2009-01-23 2013-10-02 The Boeing Company Système et procédé de détection et prévention d'incursion, d'excursion et de confusion sur une piste d'aviation
EP2709084A2 (fr) * 2012-09-14 2014-03-19 Honeywell International Inc. Systèmes et procédés pour fournir une prise de conscience et des alertes d'entrée sur piste
EP2720214A2 (fr) * 2012-09-05 2014-04-16 Honeywell International Inc. Systèmes et procédés permettant d'améliorer la sensibilité à l'état de piste
EP2942604A1 (fr) * 2014-04-10 2015-11-11 Honeywell International Inc. Détermination de localisation de pistes
US9293052B2 (en) 2013-10-23 2016-03-22 Honeywell International Inc. System and method for modulating alerts for an intended runway
EP3002214A1 (fr) * 2014-09-30 2016-04-06 Honeywell International Inc. Système de commande motrice de taxi électrique et procédé d'un aéronef
WO2020118433A1 (fr) * 2018-12-11 2020-06-18 Eagle Aerospace Ltd. Procédé et système pour évaluer des performances d'atterrissage d'aéronef et de mouvement de surface
CN115123571A (zh) * 2022-07-06 2022-09-30 武汉理工大学 智慧机场及智慧机场跑道车辆实时跟踪渲染方法与系统
US11727818B1 (en) * 2017-05-05 2023-08-15 Architecture Technology Corporation Aircraft surface state event track system and method
JP7544417B1 (ja) 2024-01-04 2024-09-03 佑斗 井澤 乗り物の移動を支援する方法及び装置

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5629691A (en) * 1995-05-26 1997-05-13 Hughes Electronics Airport surface monitoring and runway incursion warning system
US5740047A (en) * 1990-10-09 1998-04-14 Harold R. Pilley GNSS based, seamless, multi-dimensional control and management system for vehicles operating in a multi-dimensional environment

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5740047A (en) * 1990-10-09 1998-04-14 Harold R. Pilley GNSS based, seamless, multi-dimensional control and management system for vehicles operating in a multi-dimensional environment
US5629691A (en) * 1995-05-26 1997-05-13 Hughes Electronics Airport surface monitoring and runway incursion warning system

Cited By (52)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7612716B2 (en) 1999-03-05 2009-11-03 Era Systems Corporation Correlation of flight track data with other data sources
US7667647B2 (en) 1999-03-05 2010-02-23 Era Systems Corporation Extension of aircraft tracking and positive identification from movement areas into non-movement areas
US7739167B2 (en) 1999-03-05 2010-06-15 Era Systems Corporation Automated management of airport revenues
US7777675B2 (en) 1999-03-05 2010-08-17 Era Systems Corporation Deployable passive broadband aircraft tracking
US7782256B2 (en) 1999-03-05 2010-08-24 Era Systems Corporation Enhanced passive coherent location techniques to track and identify UAVs, UCAVs, MAVs, and other objects
US7889133B2 (en) 1999-03-05 2011-02-15 Itt Manufacturing Enterprises, Inc. Multilateration enhancements for noise and operations management
US8446321B2 (en) 1999-03-05 2013-05-21 Omnipol A.S. Deployable intelligence and tracking system for homeland security and search and rescue
US8203486B1 (en) 1999-03-05 2012-06-19 Omnipol A.S. Transmitter independent techniques to extend the performance of passive coherent location
US8072382B2 (en) 1999-03-05 2011-12-06 Sra International, Inc. Method and apparatus for ADS-B validation, active and passive multilateration, and elliptical surveillance
US7117089B2 (en) 2001-03-06 2006-10-03 Honeywell International Inc. Ground runway awareness and advisory system
US7206698B2 (en) 2002-05-15 2007-04-17 Honeywell International Inc. Ground operations and imminent landing runway selection
US7363145B2 (en) 2002-05-15 2008-04-22 Honeywell International Inc. Ground operations and imminent landing runway selection
US7079951B2 (en) 2002-05-15 2006-07-18 Honeywell International Inc. Ground operations and imminent landing runway selection
US7587278B2 (en) 2002-05-15 2009-09-08 Honeywell International Inc. Ground operations and advanced runway awareness and advisory system
US7908077B2 (en) 2003-06-10 2011-03-15 Itt Manufacturing Enterprises, Inc. Land use compatibility planning software
WO2005086107A2 (fr) 2004-02-28 2005-09-15 Honeywell International Inc. Systeme de sensibilisation et de conseil pour pistes d'aeroports
WO2005086107A3 (fr) * 2004-02-28 2006-04-20 Honeywell Int Inc Systeme de sensibilisation et de conseil pour pistes d'aeroports
WO2006106210A1 (fr) 2005-04-04 2006-10-12 Airbus France Procédé et dispositif d'aide à la navigation au sol d'un avion sur un aéroport
FR2884953A1 (fr) * 2005-04-22 2006-10-27 Thales Sa Procede et dispositif embarque, pour aeronef, d'alerte d'incursion de piste
WO2006111480A1 (fr) * 2005-04-22 2006-10-26 Thales Procede et dispositif embarque, pour aeronef, d'alerte d'incursion de piste
EP1835369A2 (fr) 2005-09-19 2007-09-19 Honeywell International Inc. Système d'évitement d'incursion de base et affichage
EP1835369A3 (fr) * 2005-09-19 2009-02-25 Honeywell International Inc. Système d'évitement d'incursion de base et affichage
US7630829B2 (en) 2005-09-19 2009-12-08 Honeywell International Inc. Ground incursion avoidance system and display
FR2891645A1 (fr) * 2005-09-30 2007-04-06 Thales Sa Procede et dispositif d'evaluation de la liceite de la situation d'un mobile sur la surface d'un aeroport.
US7634353B2 (en) 2005-09-30 2009-12-15 Thales Method and device for aiding the flow of a craft on the surface of an airport
US7589644B2 (en) 2005-09-30 2009-09-15 Thales Method and onboard device to assist running in an airport
FR2891644A1 (fr) * 2005-09-30 2007-04-06 Thales Sa Procede et dispositif d'aide pour la circulation d'un mobile a la surface d'un aeroport.
US7739047B2 (en) 2005-09-30 2010-06-15 Thales Method and device for evaluating the licitness of the situation of a craft on the surface of an airport
FR2891646A1 (fr) * 2005-09-30 2007-04-06 Thales Sa Procede et dispositif embarque d'aide au roulage dans un aeroport.
CN101385060B (zh) * 2006-02-18 2010-10-20 海因茨·威普弗 用于防止可移动物体侵入某段交通道的方法和系统
KR101079731B1 (ko) * 2006-02-18 2011-11-04 세이프게이트 인터내셔날 에이비 이동가능한 객체의 교통로의 섹션으로의 침입 방지 방법 및 시스템
WO2007093301A1 (fr) * 2006-02-18 2007-08-23 Heinz Wipf Procédé et dispositif destinés à empêcher qu'un objet mobile ne pénètre dans une section d'une voie de circulation
US7965227B2 (en) 2006-05-08 2011-06-21 Era Systems, Inc. Aircraft tracking using low cost tagging as a discriminator
WO2008035981A2 (fr) * 2006-09-19 2008-03-27 Unified Messaging Systems As Procédé et système de prévention des accidents
WO2008035981A3 (fr) * 2006-09-19 2008-05-08 Unified Messaging Systems As Procédé et système de prévention des accidents
WO2009090185A3 (fr) * 2008-01-18 2011-06-03 Heinz Wipf Procédé et système pour empêcher un objet mobile d'entrer dans une section protégée
WO2009090185A2 (fr) * 2008-01-18 2009-07-23 Heinz Wipf Procédé et système pour empêcher un objet mobile d'entrer dans une section protégée
EP2211324B1 (fr) * 2009-01-23 2013-10-02 The Boeing Company Système et procédé de détection et prévention d'incursion, d'excursion et de confusion sur une piste d'aviation
EP2259245A3 (fr) * 2009-06-02 2011-10-19 Honeywell International Inc. Système d'alarme de surface d'aéroport fermé
WO2012172183A1 (fr) * 2011-06-16 2012-12-20 Tracker Oy Procédé d'avertissement et agencement pour une cible mobile
EP2720214A2 (fr) * 2012-09-05 2014-04-16 Honeywell International Inc. Systèmes et procédés permettant d'améliorer la sensibilité à l'état de piste
EP2709084A2 (fr) * 2012-09-14 2014-03-19 Honeywell International Inc. Systèmes et procédés pour fournir une prise de conscience et des alertes d'entrée sur piste
US9293052B2 (en) 2013-10-23 2016-03-22 Honeywell International Inc. System and method for modulating alerts for an intended runway
EP2942604A1 (fr) * 2014-04-10 2015-11-11 Honeywell International Inc. Détermination de localisation de pistes
US9406235B2 (en) 2014-04-10 2016-08-02 Honeywell International Inc. Runway location determination
EP3002214A1 (fr) * 2014-09-30 2016-04-06 Honeywell International Inc. Système de commande motrice de taxi électrique et procédé d'un aéronef
US9640082B2 (en) 2014-09-30 2017-05-02 Honeywell International Inc. Electric taxi motive control system and method of an aircraft
US11727818B1 (en) * 2017-05-05 2023-08-15 Architecture Technology Corporation Aircraft surface state event track system and method
WO2020118433A1 (fr) * 2018-12-11 2020-06-18 Eagle Aerospace Ltd. Procédé et système pour évaluer des performances d'atterrissage d'aéronef et de mouvement de surface
US11724819B2 (en) 2018-12-11 2023-08-15 Eagle Aerospace Ltd. Method and system for assessing aircraft landing and surface movement performances
CN115123571A (zh) * 2022-07-06 2022-09-30 武汉理工大学 智慧机场及智慧机场跑道车辆实时跟踪渲染方法与系统
JP7544417B1 (ja) 2024-01-04 2024-09-03 佑斗 井澤 乗り物の移動を支援する方法及び装置

Also Published As

Publication number Publication date
AU2003269807A8 (en) 2003-12-31
AU2003269807A1 (en) 2003-12-31
WO2003107299A3 (fr) 2004-06-17

Similar Documents

Publication Publication Date Title
WO2003107299A2 (fr) Procede et dispositif de protection contre des incursions de pistes
US8378852B2 (en) Aircraft-centered ground maneuvering monitoring and alerting system
US7818099B2 (en) System and method for alerting a user of an aircraft of a possible entrance into a selected airspace
US8373579B2 (en) Aircraft ground maneuvering monitoring system
US7630829B2 (en) Ground incursion avoidance system and display
US7382288B1 (en) Display of airport signs on head-up display
US7737867B2 (en) Multi-modal cockpit interface for improved airport surface operations
US10214300B2 (en) System and method for displaying runway overrun information
US7962279B2 (en) Methods and systems for alerting an aircraft crew member of a potential conflict between aircraft on a taxiway
US7772992B2 (en) Method and device for assisting the ground navigation of an aeroplane in an airport
EP3364396A2 (fr) Systèmes d'affichage et procédés pour prévenir des incursions de pistes
US8271184B2 (en) Method and system for monitoring an aircraft taxiing phase
CN104249813B (zh) 用于显示跑道灯光信息的飞行器系统和方法
EP1875169B1 (fr) Systeme et procede permettant d'afficher l'espace aerien protege associe a une manoeuvre d'approche indirecte
US7564372B1 (en) Display of hold lines on head-up display
US7342514B1 (en) Display of automatic dependent surveillance (ADS-B) information on head-up display
US9189964B1 (en) System, module, and method for presenting runway traffic information
EP2779140B1 (fr) Système et procédé d'alerte d'un équipage à des altitudes limites
US20140343761A1 (en) System and method for performing an aircraft automatic emergency descent
EP2781884B1 (fr) Système et procédé d'affichage graphique de données de vitesse dans l'espace aérien
EP1764759A1 (fr) Système et procédé d'affichage des espaces aérien protégé ou interdit dans un avion
EP2866112B1 (fr) Système et procédé permettant de moduler des alertes pour une piste d'atterrissage élue
EP3869159A1 (fr) Panneau de guidage de vol avancé avec affichage de futurs points de cheminement et de contraintes
US20110298648A1 (en) Method and on board device for providing pilot assistance in the lack of air control
EP3696792A1 (fr) Systèmes et méthodes d'alerte en cas d'inhibition incorrecte de systèmes d'alerte

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A2

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ OM PH PL PT RO RU SD SE SG SK SL TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW

AL Designated countries for regional patents

Kind code of ref document: A2

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LU MC NL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
122 Ep: pct application non-entry in european phase
NENP Non-entry into the national phase

Ref country code: JP

WWW Wipo information: withdrawn in national office

Country of ref document: JP

点击 这是indexloc提供的php浏览器服务，不要输入任何密码和下载