The present invention generally relates to aircraft wingtip strike prevention, and more particularly relates to systems and methods for passively detecting aircraft wingtip strikes.
Aircraft pilots often maneuver an aircraft while on the ground. This may happen during ground operations such as when the aircraft is taxiing, being maneuvered to or from a hangar, or to or from a terminal.
Obstacles on the ground, such as structures, other vehicles and other obstacles, may lie in the path of the aircraft. These obstacles can be detected by the pilot via line of sight. However, in many instances, due to the dimensions of the aircraft (e.g., large wing sweep angles, distance from cockpit to wingtip) and the pilot's limited field of view, it can be difficult to monitor extremes of the aircraft during ground operations. As a result, the operator may fail to detect obstacles that are located in “blind spots” in proximity to the aircraft. In many cases, the pilot may not detect an obstacle until it is too late to take corrective action. To alleviate this, many aircraft include active sensors or cameras or to sense potential or imminent strikes.
Collisions with an obstacle can not only damage the aircraft, but can also put the aircraft out of service and result in flight cancellations. The costs associated with the repair and grounding of an aircraft are significant. As such, the timely detection and avoidance of obstacles that lie in the ground path of a vehicle is an important issue that needs to be addressed.
Currently, there is no economical system available to protect aircraft from wingtip strikes. As aircraft increase in size, the probability and cost of a strike incident increases. Therefore, there is a need for a system that can be retro-fitted onto aircraft with a minimum of effort, and that does not rely on active sensors or flight crew personnel. The present invention addresses at least this need.
This summary is provided to describe select concepts in a simplified form that are further described in the Detailed Description. This summary is not intended to identify key or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter.
In one embodiment, a method for passively detecting aircraft wingtip strikes includes generating a digital base map of at least a portion of an aerodrome that includes one or more specific wingtip strike threats, the digital base map represented by a plurality of aerodrome cells. A numeric value is assigned to each of the aerodrome cells. The numeric value assigned to each aerodrome cell is representative of the specific wingtip strike threat associated with that aerodrome cell. An index count array is generated. The index count array has a separate entry for each numeric value. A digital aircraft structure is generated that is representative of an aircraft, and is represented by a plurality of aircraft cells. A portion of the aerodrome cells are replaced with the plurality of aircraft cells. Each numeric value of the aerodrome cells that are replaced is counted to determine a replacement count associated therewith. The replacement count associated with each numeric value is entered into the separate entry in the index count array for that numeric value. One or more potential aircraft wingtip strikes are detected based on the replacement counts in the index count array.
In another embodiment, a passive aircraft wingtip strike detection system includes an aerodrome database and a processor. The aerodrome database has aerodrome data stored therein that includes data representative of specific wingtip strike threats. The processor is in operable communication with the aerodrome database. The processor is configured to selectively retrieve aerodrome data from the aerodrome database and, upon retrieval thereof to: generate a digital base map of at least a portion of an aerodrome that includes one or more specific wingtip strike threats, assign a numeric value to each of the aerodrome cells that is representative of the specific wingtip strike threat associated with that aerodrome cell, generate an index count array having a separate entry for each numeric value, generate a digital aircraft structure representative of an aircraft and that is represented by a plurality of aircraft cells, replace a portion of the aerodrome cells with the plurality of aircraft cells, count each numeric value of the aerodrome cells that are replaced to determine a replacement count associated therewith, enter the replacement count associated with each numeric value into the separate entry in the index count array for that numeric value, and detect one or more potential aircraft wingtip strikes based on the replacement counts in the index count array.
Furthermore, other desirable features and characteristics of the passive strike detection system and method will become apparent from the subsequent detailed description and the appended claims, taken in conjunction with the accompanying drawings and the preceding background.
The present invention will hereinafter be described in conjunction with the following drawing figures, wherein like numerals denote like elements, and wherein:
The following detailed description is merely exemplary in nature and is not intended to limit the invention or the application and uses of the invention. As used herein, the word “exemplary” means “serving as an example, instance, or illustration.” Thus, any embodiment described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other embodiments. All of the embodiments described herein are exemplary embodiments provided to enable persons skilled in the art to make or use the invention and not to limit the scope of the invention which is defined by the claims. Furthermore, there is no intention to be bound by any expressed or implied theory presented in the preceding technical field, background, brief summary, or the following detailed description.
Referring first to
The aerodrome database 104 has aerodrome data stored therein. The aerodrome data are representative of various specific wingtip strike threats and various other aerodrome structures. As used herein, the term “specific wingtip strike threat” encompasses both the presence and absence of solid physical structure that an aircraft wing may strike. In particular, a specific wingtip strike encompasses an open region that includes no solid physical structure, as well as various physical structures present at an aerodrome. Such physical structures may include, for example, terminal buildings, non-terminal buildings, fixed obstacles (e.g., fences, posts, light poles, signage), and moving objects (e.g., baggage carts, other aircraft). The various other aerodrome structures may include, for example, runways and taxiways. The wingtip strike threats and other aerodrome structures may be variously represented. But in the depicted embodiment these entities are represented in the form of individual sections (or segments), lines, points, and circles, depending on the objects. Preferably, though not necessarily, the aerodrome data are stored in a relatively simple compressed format that can be easily and rapidly decompressed by the processor 106.
The processor 106 is in operable communication with the aerodrome database 104 and is configured to selectively retrieve aerodrome data therefrom. As may be appreciated, the aerodrome data that the processor 106 selectively retrieves are representative of the aerodrome at which the aircraft is presently located. As may also be appreciated, for those embodiments in which the aerodrome data are stored in a compressed format, the processor 106 generates the digital base map by decompressing the retrieved aerodrome data. The processor 106, upon retrieval of the aerodrome data, generates a digital base map of at least a portion of the aerodrome, which may include one or more terminal buildings, non-terminal buildings, fixed objects, and moving objects. In the depicted embodiment, the digital base map is copied to a geo-referenced memory array 108.
The processor 106 is also in operable communication with the avionics 102 and is coupled to receive the aircraft data therefrom. The processor 106 is configured, upon receipt of these data, to determine current aircraft position, speed, and orientation, and, at least in some embodiments, to predict future aircraft positions, speeds, and orientations. The processor 106 is additionally configured, upon receipt of the aircraft data, to generate a digital aircraft structure representative of the aircraft 110 and dispose the digital aircraft structure onto the digital base map. As will be described further below, the digital aircraft structure that the processor 106 generates includes a protective envelope around the aircraft.
Referring now to
As
The processor 106, in addition to generating the digital base map 202 with an overlain digital aircraft structure 204, is configured to assign a numeric value to each of the aerodrome cells 208 and to generate an index count array 112 (see
Referring back to
Referring once again to
The processor 106 is configured, based on the retrieved aerodrome data and on the current and future aircraft positions, speeds and orientations, to implement a passive wingtip strike threat detection process. This detection process, which will now be described in more detail, is based on the content of the index count array 112, and more specifically the content of each entry in the index count array 112. This is because the content of each entry in the index count array 112 varies based on the number aerodrome cells 208 of a specific numeric value that are replaced by an aircraft cell 212.
Reference should now be made to
The digital aircraft structure 204, which is represented by a plurality of aircraft cells 212, is also generated (308), and a portion of the aerodrome cells 208 are replaced with the plurality of aircraft cells 212 (312). Each numeric value of the aerodrome cells 208 that are replaced has its associated index count array entry incremented (314). More specifically, each numeric value of the aerodrome cells 208 that are replaced is counted to determine an associated replacement count, and the replacement count associated with each numeric value is then entered into the separate entry in the index count array for that numeric value. A determination is then made whether one or more potential aircraft wingtip strikes is detected based on the replacement counts in the index count array 112 (318). If no strikes are detected, the aircraft state data are updated (322) and a portion of the process repeats (308-318). If a strike is detected, an alert is generated (324).
To more clearly illustrate the above-described process, reference should be made to
At the point in time illustrated in
As the aircraft moves along its actual or predicted path, the entries in the index count array will remain the same as depicted in
It is noted that if there is only one type of threat being protected against, the process 300 may stop as soon as a potential aircraft wingtip strike is detected. If multiple threats are being protected against, then the entire digital aircraft structure 204 can be rendered onto the digital working map 202. Moreover, whether the processor 106 detects one or multiple threats, it will generate one or more alert signals. Returning to
The system and method described herein provides a passive system that utilizes a database or map of airport/aerodrome structures that are potential collision hazards. In essence, a “graphical” threat detection approach is implemented that is relatively insensitive to the complexity of aerodrome geometry and eliminates the need for conventional wingtip strike sensors. Although sensors may still be needed in tight spaces such as gates, the system and method disclosed herein provides adequate protection from fixed obstacles.
Those of skill in the art will appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both. Some of the embodiments and implementations are described above in terms of functional and/or logical block components (or modules) and various processing steps. However, it should be appreciated that such block components (or modules) may be realized by any number of hardware, software, and/or firmware components configured to perform the specified functions. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention. For example, an embodiment of a system or a component may employ various integrated circuit components, i.e., memory elements, digital signal processing elements, logic elements, or look-up tables, which may carry out a variety of functions under the control of one or more microprocessors or other control devices. In addition, those skilled in the art will appreciate that embodiments described herein are merely exemplary implementations.
The various illustrative logical blocks, modules, and circuits described in connection with the embodiments disclosed herein may be implemented or performed with a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, i.e., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.
The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC.
In this document, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Numeric ordinals such as “first,” “second,” “third,” etc. simply denote different singles of a plurality and do not imply any order or sequence unless specifically defined by the claim language. The sequence of the text in any of the claims does not imply that process steps must be performed in a temporal or logical order according to such sequence unless it is specifically defined by the language of the claim. The process steps may be interchanged in any order without departing from the scope of the invention as long as such an interchange does not contradict the claim language and is not logically nonsensical.
Furthermore, depending on the context, words such as “connect” or “coupled to” used in describing a relationship between different elements do not imply that a direct physical connection must be made between these elements. For example, two elements may be connected to each other physically, electronically, logically, or in any other manner, through one or more additional elements.
While at least one exemplary embodiment has been presented in the foregoing detailed description of the invention, it should be appreciated that a vast number of variations exist. It should also be appreciated that the exemplary embodiment or exemplary embodiments are only examples, and are not intended to limit the scope, applicability, or configuration of the invention in any way. Rather, the foregoing detailed description will provide those skilled in the art with a convenient road map for implementing an exemplary embodiment of the invention. It being understood that various changes may be made in the function and arrangement of elements described in an exemplary embodiment without departing from the scope of the invention as set forth in the appended claims.
This application claims the benefit of U.S. Provisional Application No. 61/933,335 filed Jan. 30, 2014.
Number | Date | Country | |
---|---|---|---|
61933335 | Jan 2014 | US |