Airport map display system and data interchange method

[0002] This application claims the benefit of U.S. Provisional Application Nos. 60/336,752; 60/337,182; 60/337,192; and 60/337,295, all filed Dec. 4, 2001, the disclosure of each of which are hereby incorporated by reference.

[0003] 1. Field of the Invention

[0004] The present invention relates to aircraft surface guidance systems (SGS) and, in particular, to a communications interchange for transmitting airport map data to a display system on an aircraft.

[0005] 2. Technical Background

[0006] There is considerable interest in enhancing the field surface guidance for aircraft. After an aircraft lands on a runway at an airport, the next step is to taxi the aircraft to a desired destination such as a passenger loading/unloading gate. A pilot can easily become confused or lost amid the many runways, taxiways, ramps, and buildings that make up an airport. The problem is more significant at large airports and is particularly significant at night when the multitude of lights can make it more difficult to taxi the aircraft to the desired destination.

[0007] Efficient taxi operations save time and money. With airports becoming more crowded, aircraft often spend considerable time taxiing between runways and gates. Taxi time is even longer if the pilot makes a wrong turn, becomes lost, or blunders onto the wrong runway or taxiway. In addition, a wrong turn or navigation blunder can cause delays for other aircraft at the airport.

[0008] A main feature of an airport surface guidance capability is the presentation of an airport map that is readily available to the pilot. One conventional approach to present such a map is on a head-down display (HDD) that is displayed in the forward field of view of the pilot. The pilot typically enters or selects a taxi path that has been approved by ground controllers. The airport map then indicates the current aircraft position and the taxi path is shown overlaid on the airport map. The map gives a pilot situational awareness of where the aircraft is relative to the taxi instructions. A key aspect to a practical avionics implementation for surface guidance must generally include a communications bus or data link for transmitting the large amounts of data typically required to adequately represent an airport map on a display screen.

[0009] An obstacle for the practical implementation of an airport map system is the requirement to clearly display an airport map, preferably with taxi paths and current aircraft position overlaid on the map. Prior avionics systems have attempted to display airport maps by storing the airport map as a digital picture. While this approach works, representation of the airport map in this manner requires large amounts of memory for each airport. A digital representation of an airport map can consume more than one gigabyte of memory. In addition, such digital maps require a correspondingly high speed communications bus to transmit the map data to a display system. This requirement, coupled with the fact that many avionics systems have limited data storage capability and do not have high speed buses, have stymied efforts to implement airport maps on many aircraft. Another approach for displaying airport maps has been to upgrade aircraft avionics systems with new equipment that has large data storage capability and high speed data buses. However, these systems must be designed, certified, integrated with the exiting avionics suite, and installed. All this makes such an upgrade very costly and, therefore, this approach is economically infeasible for many aircraft.

[0010] Any airport map system should be adequate not only to accomplish the task of displaying airport maps, but to also make the maps useful and cost-effective. It is also desirable to design a map system that may be retrofit into existing aircraft avionics systems.

[0011] The continuing goal, therefore, is to find ways to reduce costs, reduce taxi errors, reduce taxi time, and improve airport efficiency.

[0012] To address the goals stated above and other goals, the inventive airport map display system comprises a unique data interchange method for facilitating the communication of airport map data through existing data buses without the need to design or install new high speed data buses. The airport map display system of the current invention also translates map data into a scale that is more user friendly on certain existing display systems. When the invention is implemented using a raster type display system for displaying the airport map data, the vector group labels are redefined to display airport map symbology as opposed to enroute symbology. For retrofit applications, the airport map display system is activated responsive to a preexisting dual use input activated when a taxi-related page is being displayed.

[0013] According to one aspect of the present invention, the airport map display system is integrated as an extension of the flight management system (FMS) which provides the enroute planning function for the aircraft. FMSs are already installed in many aircraft and an FMS comprises many of the components required to implement the airport map display system of the invention. For example, an FMS may comprise a processor, data storage devices, a user interface, and is typically in communication with multiple display systems.

[0014] In another aspect of the present invention, the airport map data is translated into a scale that is compatible with a target display system. In this manner, the airport map display system of the invention is compatible with a larger selection of preexisting display systems.

[0015] Yet another aspect of the invention is the manipulation of raster display interfaces of existing systems by redefining the vector group labels to facilitate the display of airport map symbology.

[0016] It is clear that the invention is a significant improvement over the prior art systems. Further, those skilled in the art will recognize that the invention is not limited to use with an FMS. It should be appreciated that other processors, display screens, and data entry devices may be used to practice the present invention.

[0017] Additional features and advantages of the invention will be set forth in the detailed description which follows, and in part will be readily apparent to those skilled in the art from that description or recognized by practicing the invention as described in the detailed description which follows, the claims, as well as the appended drawings.

[0018] It is to be understood that the foregoing description is exemplary of the invention only and is intended to provide an overview for the understanding of the nature and character of the invention as it is defined by the claims. The accompanying drawings are included to provide a further understanding of the invention and are incorporated and constitute part of this specification. The drawings illustrate various features and embodiments of the invention which, together with their description serve to explain the principals and operation of the invention.

[0019] FIG. 1 is a block diagram of one embodiment of an airport map display system according to the invention;

[0020] FIG. 2 is a sample interface definition according to the invention;

[0021] FIG. 3 is a sample surface identification format according to the invention;

[0022] FIG. 4 is a flowchart illustrating a sample scaling algorithm according to the invention; and

[0023] FIGS. 5 and 6 are airport map display screens according to the invention.

[0024] Reference will now be made in detail to the present preferred embodiments of the invention, examples of which are illustrated in the accompanying drawings. Wherever possible, the same reference numerals will be used throughout the drawings to refer to the same or like parts.

[0025] Referring to FIG. 1, an exemplary embodiment of the airport map system according to the present invention is shown, and is designated generally throughout by reference numeral 10. The components of the airport map system of the present invention will first be briefly described and then described in detail. The most common use for the invention is as an integrated element in the FMS of an aircraft, such as a commercial passenger or cargo jet, and therefore the following discussion will describe the invention in relation to such an application.

[0026] A block diagram of the airport map system according to the invention and related aircraft systems is shown in FIG. 1. All of the various aircraft systems can comprise the invention and therefore they are collectively referred to as airport map display system 10.

[0027] Airport map display system 10 comprises flight management computer (FMC) 11, multifunction control display unit (MCDU) 12, navigation database (NDB) 13, head-up display (HUD) 14, electronic flight instrument system (EFIS) 15, multi-mode receiver (MMR) 16, transponder 17, and communications management unit (CMU) 18. FMC 11 and MCDU 12 are generally referred to collectively as a flight management system (FMS).

[0028] FMC 11 comprises a processor 11A, and memory 11B. Processor 11A may include any data processor suitable for receiving and processing commands and data. Processor 11A is preferably a microprocessor with sufficient throughput to complete the required FMS and airport map tasks in real-time. Memory 11B preferably comprises both random access memory (RAM) for storing dynamic data and variables, and read-only memory (ROM) for storing program data and static data. Processor 1 A communicates with memory 11B to retrieve program instructions and data and to manipulate and store variables. Processor 11A is also in communication with NDB 13.

[0029] NDB 13 comprises airport map data and taxi route data describing airport runways, taxiways, gates, ramps, standard taxi routes and various other desired airport structures or features as desired. The airport map data is preferably stored in the linked list 13A and standard taxi routes 13B are also stored in the database. However, the airport map data may also be stored in many other formats as desired. NDB 13 is preferably rewritable or replaceable so that the data representative of an airport map and standard taxi route data is easily updated as needed and so that the data remains current regarding changes to airport runways, taxiways, construction, and the like. NDB 13 is constructed of any of various memory storage technologies such as PROM, EPROM, EEPROM, magnetic disk drives, optical disk drives, or various combinations of these and similar devices. The operative requirement merely being the capability to store the data representative of an airport map.

[0030] The user interface is preferably accomplished through MCDU 12 which communicates with FMC 11 and processor 11A. MCDU 12 comprises a display screen 12A, line select keys 19, and a key pad 12B. MCDU 12 is commonly used to enter enroute flight planning commands to the FMC 11 and to output enroute flight data to the pilot, crew, or operator via display screen 12A. The operation of line select keys 19 allows quick selection and deletion of displayed items. According to one embodiment, the invention uses this pre-existing user interface device to accomplish the user interface for ground navigation at airports, although other user interfaces may also be used to practice the invention. For example, other displays such as the EFIS 15 or HUD 14 may be used as part of the user interface if desired since these systems also have user interfaces.

[0031] HUD 14 and EFIS 15 are shown in communication with FMC 11 via display signal 11C. HUD 14 projects an image to a combiner positioned along the forward line of sight of the pilot such that a pilot can view the image and also look out the front windshield of the aircraft simultaneously. EFIS 15 (also referred to as a HDD) is typically positioned below the front windshield of the aircraft. EFIS 15 comprises one or more display screens which are typically implemented using cathode ray tubes (CRTs), flat panel displays, or functionally similar display devices. Once the airport map is selected, the map is preferably displayed to the pilot on either the HUD 14 or EFIS 15. The EFIS 15 is the more preferred display device. The EFIS 15, HUD 14, and MCDU 12 each have display screens that may be used to practice the invention.

[0032] Several communications systems are also coupled to the FMC 11. MMR 16 receives navigation or position signals such as global positioning system (GPS) signals, differential GPS (DGPS), local area augmentation system (LAAS) signals, wide area augmentation system (WAAS) signals, and the like. These signals are communicated to the FMC 11 where the position of the aircraft relative to airport features is determined. This aircraft position information or similar information from other sources, is then used to compute an appropriate display signal 11C.

[0033] Transponder 17 and CMU 18 provide additional input and output communications channels. Transponder 17, for example, may receive signals such as automatic dependent surveillance broadcast (ADS-B) from other aircraft or air traffic control (ATC). This information may be used to add the position of other vehicles to the displayed airport map. CMU 18 comprises a data link with ATC or similar controlling authority through which taxi routes, plans and instructions are communicated, negotiated, modified, and approved or denied.

[0034] There exist many standards related to communications in the aviation industry, and particularly in the field of avionics. Aeronautical Radio, Inc. (ARINC), of 2551 Riva Road, Annapolis, Md., publishes a variety of standards relating to avionics. Two such publications disclose aviation communications standards. ARINC 429 is a standard relating to a communications bus frequently used on aircraft. ARINC Characteristic 702A, entitled “Advanced Flight Management Computer System” was published Dec. 31, 1996, and relates to, among other things, the communication protocols between an FMS and a display system. Both of these aforementioned publications are hereby incorporated by reference.

[0035] FIG. 2 is a sample interface definition according to the invention. In order to utilize existing EFIS interfaces on aircraft, the taxi path and airport map features utilize the existing vector group labels. These labels were intended for other purposes such as for displaying enroute symbology. The airport map display system uses these vector group labels to represent the taxi path (both active and modified) and the airport map (e.g., runways and taxiways). The active and modified flight plan labels are used for the taxi route and modified taxi route respectively. Similarly, the offset flight plan label is used for the airport map symbology. The airport map depicts the pavement outlines and may also include conic sections to depict various curved pavement areas. The positions (i.e., position locations or coordinates) are absolute latitude/longitude position coordinates which may use twenty (20) bits of data in the BNR format that is referenced in the ARINC specifications. FIG. 3 illustrates a sample format for surface identifiers. Preferably, this includes text identifiers for runways and taxiways (e.g., R25, B42).

[0036] FIG. 4 illustrates one algorithm for transposing latitude and longitude coordinates to affect the expanded scaling required for the airport map data presentation. Formula 1 calculates Δ (delta) latitude from the absolute latitude and the reference latitude (i.e., the aircraft latitude) and then multiplied by an Earth radius constant. Formula 2 calculates Δ longitude from the reference longitude and the reference latitude. Course is computed from the Δ latitude and Δ longitude. Distance is computed from Δ latitude and A longitude. Scale is computed from distance times ten (10) to achieve a scaling factor of ten (10). Other scaling factors may be achieved by using other multipliers as desired. The new latitude and new longitude position coordinates are computed as shown in formulas 6 and 7 in FIG. 4.

[0037] FIGS. 5 and 6 illustrate resulting displays according to the invention. Aircraft symbology 51 is shown on runway 52. Runway 52 is indicated by two parallel dashed lines. Taxi route 53 proceeds along runway 52 and turns left and proceeds along taxiway 55 to terminal building 54. Taxiways 55 are represented by single dashed lines. In use, the symbology is more discernable since the symbology may be displayed in different colors. For example, runways 52 may be displayed in white dashed lines, taxiways 55 may be displayed in blue dashed lines, and taxi routes 53 and buildings 54 may be displayed in solid magenta lines. FIG. 6 illustrates another resulting display embodied on an EFIS display screen and shown in a larger scale (i.e., a larger area of the airport is displayed).

[0038] It will become apparent to those skilled in the art that various modifications to the preferred embodiment of the invention as described herein can be made without departing from the spirit or scope of the invention as defined by the appended claims.