Method, apparatus and program product for verifying flight information

By retrieving and receiving messages in the flight information system, verifying the matching of flight information and providing notifications, the accuracy of data verification during aircraft flight is solved, and the reliability and safety of the flight information system is improved.

CN112131870BActive Publication Date: 2024-12-06THE BOEING CO
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202010381120.6
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2019-06-24
Filing Date
2020-05-08
Publication Date
2024-12-06
Estimated Expiration
2040-05-08

AI Technical Summary

Technical Problem

During the aircraft flight, it is difficult to effectively verify the accuracy and consistency of flight information, resulting in possible data input errors, affecting flight safety and efficiency.

Method used

By retrieving and receiving messages in the flight information system, comparing flight information in the first and second messages, verifying their matching, and providing notifications when mismatch, using the processor to perform parsing and comparison codes, supporting different format types message parsing and verification, including bit, byte, character and data field level matching checks.

Benefits of technology

Ensure accurate input and verification of flight information, reduce data errors, improve the reliability and safety of flight information systems, and provide timely notifications to deal with potential data mismatch problems.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN112131870B_ABST
    Figure CN112131870B_ABST
Patent Text Reader

Abstract

The present disclosure relates to methods, apparatus, and program products for verifying flight information. Specifically, a method is disclosed, the method comprising: retrieving a first message, the first message comprising flight information input into a flight information system associated with a flight. The method also comprises: receiving a second message, the second message comprising flight information input into a flight information system associated with the flight based on the first message. The method further comprises: verifying that the flight information sent in the first message matches the flight information received in the second message. In addition, the method comprises: providing a notification in response to verifying that the flight information sent in the first message does not match the flight information received in the second message.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates generally to aircraft, and more particularly to verifying flight information of an aircraft during flight of the aircraft. Background Art

[0002] The aircraft may be equipped with a computer system or a computer system that controls part of the flight of the aircraft. During flight, various data may be provided to the computer system to maintain or adjust the flight of the aircraft. Summary of the invention

[0003] The subject matter of this application has been developed in response to the current state of the art. Therefore, the subject matter of this application has been developed to verify flight information of a flight.

[0004] A method is disclosed herein. The method includes retrieving a first message, the first message including flight information input into a flight information system associated with a flight. The method also includes receiving a second message, the second message including flight information input into a flight information system associated with the flight based on the first message. The method further includes: verifying that the flight information sent in the first message matches the flight information received in the second message. In addition, the method includes providing a notification in response to verifying that the flight information sent in the first message does not match the flight information received in the second message. The foregoing subject matter of this paragraph characterizes Example 1 of the present disclosure.

[0005] In response to determining that the flight information received in the second message is within a threshold of the flight information sent in the first message, the flight information sent in the first message matches the flight information received in the second message. The foregoing subject matter of this paragraph characterizes Example 2 of the present disclosure, wherein Example 2 also includes subject matter according to Example 1 above.

[0006] The first message and the second message include different format types, so that the first message and the second message are parsed to identify the flight information in each message for verification. The aforementioned subject matter of this paragraph characterizes Example 3 of the present disclosure, wherein Example 3 also includes subject matter according to any one of Examples 1 to 2 above.

[0007] Verification includes: comparing the flight information of the first message and the second message based on the format of the first message and the second message to determine whether the flight information of the first message matches the flight information of the second message. The aforementioned subject matter of this paragraph characterizes Example 4 of the present disclosure, wherein Example 4 also includes the subject matter according to Example 3 above.

[0008] The comparison of the flight information between the first message and the second message is performed on one or more of the following: on a per-bit basis, on a per-byte basis, on a per-character basis, on a per-data field basis, and on a per-message basis. The foregoing subject matter of this paragraph characterizes Example 5 of the present disclosure, wherein Example 5 also includes subject matter according to Example 4 above.

[0009] In response to one of when the first message is received and when the user approves the input of the flight information, the flight information sent in the first message is input into the flight information system. The aforementioned subject matter of this paragraph characterizes Example 6 of the present disclosure, wherein Example 6 also includes subject matter according to any one of Examples 1 to 5 above.

[0010] The method further includes detecting an input event in response to flight information in the first message being input into the flight information system. In response to the input event, retrieving the first message and receiving the flight information in the second message. The foregoing subject matter of this paragraph characterizes Example 7 of the present disclosure, wherein Example 7 also includes subject matter according to Example 6 above.

[0011] The type of notification provided and the method of delivery are determined based on the significance of the flight information that is input into the flight information system and does not match the flight information sent in the first message. The aforementioned subject matter of this paragraph characterizes Example 8 of the present disclosure, wherein Example 8 also includes subject matter according to any one of Examples 1 to 7 above.

[0012] The notification is configured as one or more of a push notification for a mobile application, a text message, an email message, a website, and a web service. The foregoing subject matter of this paragraph characterizes Example 9 of the present disclosure, wherein Example 9 also includes subject matter according to any one of Examples 1 to 8 above.

[0013] One of the first message and the second message includes an Aircraft Communications Addressing and Reporting System (“ACARS”) message format.The foregoing subject matter of this paragraph characterizes Example 10 of the present disclosure, wherein Example 10 also includes subject matter according to any of Examples 1 to 9 above.

[0014] The second message is published and broadcast to a system that is subscribed to receive messages including flight information input into the flight information system. The foregoing subject matter of this paragraph characterizes Example 11 of the present disclosure, wherein Example 11 also includes subject matter according to any one of Examples 1 to 10 above.

[0015] In response to the query for flight information, a second message is received from the flight information system. The foregoing subject matter of this paragraph characterizes Example 12 of the present disclosure, wherein Example 12 also includes subject matter according to any one of Examples 1 to 11 above.

[0016] A device is further disclosed herein. The device includes a processor. The device also includes a memory storing executable code that can be executed by the processor to perform the following steps: retrieving a first message, the first message including flight information input into a flight information system associated with the flight; receiving a second message, the second message including flight information input into a flight information system associated with the flight based on the first message; verifying that the flight information sent in the first message matches the flight information received in the second message; and providing a notification in response to verifying that the flight information sent in the first message does not match the flight information received in the second message. The foregoing subject matter of this paragraph characterizes Example 13 of the present disclosure.

[0017] In response to determining that the flight information received in the second message is within a threshold of the flight information sent in the first message, the flight information sent in the first message matches the flight information received in the second message. The foregoing subject matter of this paragraph characterizes Example 14 of the present disclosure, wherein Example 14 also includes subject matter according to Example 13 above.

[0018] The first message and the second message include different format types, so that the first message and the second message are parsed to identify the flight information in each message for verification. The aforementioned subject matter of this paragraph characterizes Example 15 of the present disclosure, wherein Example 15 also includes subject matter according to any one of Examples 13 to 14 above.

[0019] The code can be further executed by the processor to verify the flight information in each message by comparing the flight information of the first message and the second message based on the format of the first message and the second message to determine whether the flight information of the first message matches the flight information of the second message. The aforementioned subject matter of this paragraph characterizes Example 16 of the present disclosure, wherein Example 16 also includes the subject matter according to Example 15 above.

[0020] The comparison of the flight information between the first message and the second message is performed on one or more of the following: on a per-bit basis, on a per-byte basis, on a per-character basis, on a per-data field basis, and on a per-message basis. The foregoing subject matter of this paragraph characterizes Example 17 of the present disclosure, wherein Example 17 also includes subject matter according to Example 16 above.

[0021] The code can be further executed by the processor to detect an input event in response to flight information in the first message being entered into the flight information system. In response to the input event, the first message is retrieved, and the flight information is received in the second message, and in response to one of when the first message is received and when the user approves the input of the flight information, the flight information sent in the first message is entered into the flight information system. The aforementioned subject matter of this paragraph characterizes Example 18 of the present disclosure, wherein Example 18 also includes subject matter according to any one of Examples 13 to 17 above.

[0022] The type of notification provided and the method of delivery are determined based on the significance of the flight information that is input into the flight information system and does not match the flight information sent in the first message. The aforementioned subject matter of this paragraph characterizes Example 19 of the present disclosure, wherein Example 19 also includes subject matter according to any one of Examples 13 to 18 above.

[0023] In addition, a program product is disclosed herein, the program product including a computer-readable storage medium storing executable code executable by a processor, the executable code including code for performing the following operations: retrieving a first message, the first message including flight information input into a flight information system associated with a flight; receiving a second message, the second message including flight information input into a flight information system associated with the flight based on the first message; verifying that the flight information sent in the first message matches the flight information received in the second message; and providing a notification in response to verifying that the flight information sent in the first message does not match the flight information received in the second message. The foregoing subject matter of this paragraph characterizes Example 20 of the present disclosure.

[0024] The features, structures, advantages and / or characteristics of the description of the subject matter of the present disclosure may be combined in any suitable manner in one or more embodiments and / or implementations. In the following description, many specific details are provided to give a thorough understanding of the embodiments of the subject matter of the present disclosure. Those skilled in the relevant art will recognize that the subject matter of the present disclosure may be practiced in the absence of one or more of the specific features, details, parts, materials and / or methods of a particular embodiment or implementation. In other cases, additional features and advantages that are not present in all embodiments or implementations may be recognized in certain embodiments and / or implementations. In addition, in some instances, well-known structures, materials or operations are not shown or described in detail to avoid blurring the aspects of the subject matter of the present disclosure. The features and advantages of the subject matter of the present disclosure will become more fully apparent according to the following description and the appended claims, or may be known by the practice of the subject matter set forth below. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] In order that the advantages of the present subject matter may be more readily understood, a more particular description of the subject matter briefly described above will be provided by reference to specific embodiments illustrated in the accompanying drawings. Understanding that these drawings depict only typical embodiments of the present subject matter and are therefore not to be considered limiting of the scope of the present subject matter, the present subject matter will be described and explained with additional specificity and detail through the use of the accompanying drawings, in which:

[0026] Figure 1 is a schematic block diagram of a system for verifying flight information according to one or more examples of the present disclosure;

[0027] Figure 2 is a schematic block diagram of a device for verifying flight information according to one or more examples of the present disclosure;

[0028] Figure 3A An example implementation of a system for verifying flight information according to one or more examples of the present disclosure is shown;

[0029] Figure 3B Another example implementation of a system for verifying flight information according to one or more examples of the present disclosure is shown;

[0030] Figure 4 is a schematic flow chart of a method for verifying flight information according to one or more examples of the present disclosure; and

[0031] Figure 5 is a schematic flow chart of a method for verifying flight information according to one or more examples of the present disclosure. DETAILED DESCRIPTION

[0032] Throughout this specification, references to "one embodiment," "an embodiment," or similar language mean that a specific feature, structure, or characteristic described in conjunction with the embodiment is included in at least one embodiment of the present disclosure. Throughout this specification, appearances of the phrases "in one embodiment," "in an embodiment," and similar language may, but need not, all refer to the same embodiment. Similarly, use of the term "implementation" means an implementation having a specific feature, structure, or characteristic described in conjunction with one or more embodiments of the present disclosure, however, an implementation may be associated with one or more embodiments if no explicit association is indicated.

[0033] Figure 11 is a schematic block diagram illustrating one embodiment of a system 100 for verifying flight information. The system 100 includes one or more information processing devices 102, one or more messaging devices 104, one or more data networks 106, one or more servers 108, and one or more aircraft 110. Those skilled in the art will recognize that even in the Figure 1 A specific number of information processing devices 102, messaging devices 104, data networks 106, one or more servers 108, and aircraft 110 are depicted in the system 100, but according to the present disclosure, any number of information processing devices 102, messaging devices 104, data networks 106, servers 108, and aircraft 110 may be included in the system 100.

[0034] The information processing device 102 of the system 100 may include one or more of the following: a desktop computer, a laptop computer, a tablet computer, a smart phone, a smart speaker (e.g., Amazon Google Apple ), security systems, set-top boxes, game consoles, smart TVs, smart watches, fitness bands or other wearable activity tracking devices, head-mounted optical displays (e.g., virtual reality headsets, smart glasses, or the like), high-definition multimedia interface (“HDMI”) or other electronic display dongles, personal digital assistants, digital cameras, camcorders, or computing devices that include a processor (e.g., a central processing unit (“CPU”), a processor core, a field programmable gate array (“FPGA”) or other programmable logic, an application specific integrated circuit (“ASIC”), a controller, a microcontroller and / or other semiconductor integrated circuit devices), volatile memory and / or non-volatile storage media.

[0035] In some embodiments, information processing device 102 is communicatively coupled to one or more other information processing devices 102 via data network 106 and may be located on aircraft 110, one or more servers 108, and / or one or more aircraft 110, as described below. Information processing device 102 may include: a processor, a processor core, and / or the like configured to execute various programs, program codes, systems, applications, instructions, functions, and / or the like for sending and receiving messages, comparing information, storing and querying data in a database, and / or the like.

[0036] In one embodiment, the flight information message device 104 is configured to retrieve a first message sent to a flight information system, such as a flight management system of the aircraft 110. The first message may include flight information entered into the flight information system. In further embodiments, the flight information message device 104 receives flight information entered into the flight information system associated with the flight based on the first message. Flight information from the flight information system may be received in a second message. In certain embodiments, the flight information message device 104 verifies that the flight information sent in the first message matches the flight information received in the second message, and provides a notification in response to verifying or determining that the flight information in the first message and the second message do not match. In this manner, the flight information message device 104 can verify that flight information including important flight information is being received and correctly entered into the flight information system, and if not, provide timely alerts or notifications to other interested, subscribed, or registered systems via the data network 106.

[0037] In various embodiments, the flight information message device 104 is located on the aircraft 110 as part of a flight information system or other computing system associated with the aircraft 110, on a ground-based computing system, and / or some combination of the two. In some embodiments, the flight information message device 104 is implemented as a hardware device that can be installed or deployed on the information processing device 102, on the server 108, on the aircraft 110, and / or elsewhere on the data network 106. In some examples, the flight information message device 104 includes a hardware device, such as a secure hardware dongle or other hardware device device (e.g., a set-top box, a network device, etc.) that is connected to the aircraft 110 via a wired connection (e.g., a universal serial bus ("USB") connection) or a wireless connection (e.g., a wireless communication network). The flight information message device 104 may be a device that is attached to a laptop computer, a server 108, a tablet computer, a smart phone, a security system, etc.; the hardware device is attached to an electronic display device (e.g., a television or monitor using an HDMI port, a DisplayPort port, a Mini DisplayPort port, a VGA port, a DVI port, etc.); and / or the like. The hardware device of the flight information message device 104 includes a power interface, a wired and / or wireless network interface, a graphics interface attached to a display, and / or a semiconductor integrated circuit device as described below that is configured to perform the functions described herein with respect to the flight information message device 104.

[0038] In some examples, the flight information message device 104 includes a semiconductor integrated circuit device (e.g., one or more chips, dies, or other discrete logic hardware), such as a field programmable gate array (“FPGA”) or other programmable logic, firmware for the FPGA or other programmable logic, microcode for execution on a microcontroller, an application specific integrated circuit (“ASIC”), a processor, a processor core, etc. In one embodiment, the message device 104 is mounted on a printed circuit board using one or more wires or connections (e.g., to volatile memory, non-volatile storage media, network interfaces, peripheral devices, graphics / display interfaces, etc.). In some examples, the hardware device includes: one or more pins, pads, or other electrical connections configured to send and receive data (e.g., communicate with one or more wires of a printed circuit board, etc.), and one or more hardware circuits and / or other circuits configured to perform various functions of the flight information message device 104.

[0039] In some embodiments, the semiconductor integrated circuit device or other hardware device of the flight information message device 104 includes and / or is communicatively connected to one or more volatile storage media, which volatile storage media may include but are not limited to random access memory ("RAM"), dynamic RAM ("DRAM"), cache memory, etc. In one embodiment, the semiconductor integrated circuit device or other hardware device of the flight information message device 104 includes and / or is communicatively connected to one or more non-volatile storage media, which non-volatile storage media may include but are not limited to: NAND flash memory, NOR flash memory, nano random access memory (nano RAM or NRAM), nanocrystal wire-based memory, silicon-oxide based sub-10 nanometer process memory, graphene memory, silicon-oxide based sub-10 nanometer process memory, graphene memory, silicon-oxide-nitride-oxide-silicon ("SONOS: Silicon-Oxide-Nitride-Oxide-Silicon"), resistive RAM ("RRAM"), programmable metallization cell ("PMC"), conductive bridge RAM ("CBRAM"), magnetoresistive RAM ("MRAM"), dynamic RAM ("DRAM"), phase change RAM ("PRAM" or "PCM"), magnetic storage media (e.g., hard disk, tape), optical storage media, etc.

[0040] In another embodiment, the flight information message device 104 may include software services and software applications. The flight information message device, system, module and / or the like may be executed in a memory on another device and communicate with the illustrated computing system, flight information system, aircraft 110 or other information processing device 102 via hosted inter-computer communication to process flight information including flight information and various flight information parameters.

[0041] In one embodiment, data network 106 includes a digital communication network that transmits digital communications. In some examples, data network 106 includes a wireless network such as a wireless cellular network, such as a Wi-Fi network, In some examples, data network 106 includes a wide area network ("WAN"), a storage area network ("SAN"), a local area network (LAN), a fiber optic network, the Internet, or other digital communication network. In some examples, data network 106 includes two or more networks. In one example, data network 106 includes one or more servers, routers, switches, and / or other networking equipment. In some examples, data network 106 includes one or more computer-readable storage media, such as a hard drive, an optical drive, a non-volatile memory, a RAM, etc.

[0042] In one example, the wireless connection is a mobile phone network. In one example, the wireless connection employs a Wi-Fi network based on any one of the Institute of Electrical and Electronics Engineers ("IEEE") 802.11 standards. Alternatively, in some examples, the wireless connection is In addition, in several examples, the wireless connection uses radio frequency identification ("RFID") communication, including RFID communication by the International Organization for Standardization ("ISO"), the International Electrotechnical Commission ("IEC"), the American Society for Testing and Materials, and the International Electrotechnical Commission ("ISO"). (American Society for Testing and Material, )、DASH7 TM Alliance and EPCGlobal TM Established RFID standards.

[0043] Alternatively, the wireless connection may be based on the IEEE 802 standard. In one embodiment, the wireless connection is provided by Sigma Designed by Alternatively, wireless connections can be made using the Innovations defined and / or connect.

[0044] The wireless connection may be an infrared connection including at least a protocol conforming to that established by the Infrared Data Association ("the Infrared Data Association"). ) defined by the Infrared Physical Layer Specification ("IrPHY") . Alternatively, the wireless connection may be a cellular telephone network communication. As of the date of filing of this application, all standards and / or connection types include the latest versions and revisions of the standards and / or connection types.

[0045] In one embodiment, one or more servers 108 are implemented as blade servers, mainframe servers, tower servers, rack servers, and / or the like. In some examples, one or more servers 108 are configured as mail servers, web servers, application servers, FTP servers, media servers, data servers, network servers, file servers, virtual servers, and / or the like. In some examples, one or more servers 108 are communicatively coupled (e.g., networked) to one or more information processing devices 102 via a data network 106. In some examples, one or more servers 108 store data in a data structure such as a database, a data repository, and the like.

[0046] Figure 2 One embodiment of a device 200 for verifying flight information is depicted. The device 200 includes an embodiment of the messaging device 104. In some embodiments, the messaging device 104 includes one or more of a flight information retrieval module 202, a message receiving module 204, a verification module 206, a notification module 208, and an input event module 210, which are described in detail below.

[0047] In one embodiment, the flight information retrieval module 202 is configured to retrieve messages that have been or are being sent to an aircraft 110, such as a commercial airplane, helicopter, and / or the like, or other flight information systems associated with the aircraft 110. In one embodiment, the message is sent from a ground-based messaging system, a ground-based computing system, a ground-based communication system, and / or the like that is communicatively coupled to the aircraft 110 via a data network 106, such as a cellular data network, a satellite data network, an airborne radio transmission network, and / or the like. An example of such a network is an aircraft communications addressing and reporting system (ACARS), which is a digital data link system for transmitting short messages between an aircraft 110 and a ground station via airband radio or satellite.

[0048] Thus, the message is an electronic message such as a text message, an email message, a short message service ("SMS") message, an ACARS message, and / or another type of electronic message. The electronic message may have a known, predefined, predetermined, or otherwise recognizable format. For example, the flight information sent in the message may be located in predefined fields within the message (e.g., there may be a message header field, a message size / length field, a message parity field, and a message payload field, which may be divided into different predefined fields including code or other information that the flight management system may partition, read, and implement).

[0049] In some embodiments, the message includes flight information that is input into a flight information system such as a flight management system of the aircraft 110. As used herein, a flight management system is a special computer system that automates various in-flight tasks such as flight planning. In other embodiments, the message is sent to a variety of flight information systems, such as an airline flight planning system, an air traffic processor system, an air traffic control trajectory prediction system, a communication management unit system, and / or the like. In light of this disclosure, one skilled in the art will recognize the various information systems that may be associated with flight management of the aircraft 110.

[0050] The flight information may include status information tracked from ground-based computers and / or messaging services, such as the amount of fuel remaining, the weight of the aircraft 110, wind speed, barometric readings, the speed of the aircraft 110, and / or the like that the flight information system may use, for example, via a flight management system, to maintain or adjust the flight settings of the aircraft 110. Other flight information may include information such as commands or actions, for example, a command to decrease or increase the speed of the aircraft, a command to increase or decrease the altitude of the aircraft, and / or the like.

[0051] In one embodiment, the flight information retrieval module 202 retrieves the transmitted message (e.g., the message including the flight information transmitted to the aircraft 110) from a storage location of the ground-based computing system. In some embodiments, the flight information retrieval module 202 retrieves the transmitted message (e.g., the message including the flight information received by the aircraft 110) from a storage location on the aircraft 110.

[0052] In one embodiment, the message receiving module 204 is configured to receive a message including flight information input into the flight information system based on the first message. The flight information received in the second message may be received in a different message, which may have the same or different format as the message including the flight information sent to the flight information system, for example, the message sent to the flight management system of the aircraft 110 may be sent via a satellite network, and the message received from the aircraft 110 may be received via an airborne radio network.

[0053] The message receiving module 204 may query a database, log file, system, and / or the like to obtain flight information that has been entered into a flight information system (e.g., a flight management system of the aircraft 110). The message receiving module 204 may check the flight information in response to new flight information being received, entered, or entered into the flight information system. For example, a pilot may verify flight information received from a ground-based messaging service and confirm the flight information before entering the flight management system, and the message receiving module 204 may receive a notification, event, signal, trigger, or the like indicating that new information has been received and entered into the flight management system. In some embodiments, the flight information may be altered, modified, changed, adjusted, etc. by the pilot, other crew members, users, or through different systems before being entered into the flight information system.

[0054] The message receiving module 204 may query the flight information system to obtain information received in and / or entered into the flight information system. In some embodiments, the message receiving module 204 sends the flight information in the message to a ground-based messaging service for further comparison or analysis, as explained below with reference to the verification module 206. In some embodiments, the message receiving module 204 sends the flight information in the queried message to a verification module 206, which is part of or in communication with the flight information system, to further analyze the queried flight information (e.g., whether it matches the flight information received at the aircraft 110 and / or entered by the pilot / crew member), wherein the result (e.g., whether the received / entered flight information matches the flight information being used by the flight management system) is sent to the ground-based messaging service. In some embodiments, the flight information is automatically entered into the flight information system in response to a user, such as an air traffic controller, pilot, or other crew member, verifying and confirming the entry of the information into the flight information system, which avoids errors that may occur when manually entering the information into the flight information system.

[0055] In some embodiments, the message receiving module 204 associates the queried flight information with the message received at the flight information system, so that the flight information received or input into the flight information system is mapped to the following message, which triggers the flight information input into the flight information system. For example, the message containing the queried flight information may also include an identifier for the corresponding message received at the aircraft 110, such as a unique message identifier, a timestamp of when the message received at the aircraft 110 was sent or received, and / or the like.

[0056] In one embodiment, the flight information may be streamed to and / or from a flight information system associated with a flight of an aircraft, such as aircraft 110. In such an embodiment, the flight information retrieval module 202 and the message receiving module 204 are combined, communicatively linked, operatively connected, etc., into a flight information socket (e.g., a network socket) where flight information is received and queried by subscribing, registering, etc. to send and receive communications over the socket.

[0057] For example, the flight information system may be implemented as a publisher in a publisher / subscriber based system, wherein the message receiving module 204, other systems, and / or other devices are implemented or configured as a subscription system for messages including flight information sent from the flight information system. The flight information system may "publish" messages, e.g., send a message containing flight information from the flight information system, which is then broadcast, streamed, or otherwise transmitted to "subscribers" or registered systems, such as the message receiving module 204. In this manner, the message receiving module 204 may receive messages including flight information in real time or with minimal delay between the time the message is sent and the time the message is received by the message receiving module 204, so that accurate verification of the flight information being used in the flight information system may be performed.

[0058] In one embodiment, the verification module 206 is configured to verify that the flight information in the message sent to the flight information system associated with the flight matches the flight information in the message received from the flight information system associated with the flight, which flight information may include flight information received at the aircraft 110, flight information input into the flight information system (e.g., the flight management system of the aircraft 110), flight information queried or received from the flight information system, and / or the like. In other words, the verification module 206 can verify whether the flight information is correctly received, input, sent, etc. If the verification module 206 determines that the flight information between the messages matches, then the flight information sent to the flight information system associated with the flight is correctly input into the flight information system; otherwise, the data input into the flight information system is erroneous.

[0059] In some embodiments, the verification module 206 verifies a match between the flight information in a message sent to a flight information system associated with the flight and the flight information queried or received from the flight information system associated with the flight (e.g., flight information entered into a flight management system) and sent from the flight information system in a different message by comparing the flight information on a per-message basis, a per-data-field basis, a per-word basis, a per-byte basis, a per-bit basis, a per-character basis, and / or the like.

[0060] For example, if the message sent to the flight information system associated with the flight and the message received from the flight information system associated with the flight are of the same type (e.g., an ACARS message), the verification module 206 may perform a message-to-message comparison, or may compare corresponding fields within the message that include flight information data and / or the like. However, if the messages are of different types, the verification module 206 may need to locate the flight information in the message so that the flight information can be compared. For example, the verification module 206 may locate the flight information based on a predefined format of the message (e.g., an ACARS message may store flight information in a predefined field, location, or place within the message). However, if the message does not have a predefined format, the verification module 206 may locate the flight information in the message using text, character, or string processing (such as artificial intelligence) based on context, natural language processing, regular expressions, and / or the like to locate the flight information, the field where the flight information is located, and / or the like.

[0061] In one embodiment, validation module 206 determines that flight information of two messages matches in response to determining that flight information received in a message from a flight information system associated with the flight (e.g., flight information queried from a flight management system) and flight information sent in a message to a flight information system associated with the flight are within or meet a threshold, amount, range, etc. For example, a ground-based messaging system may send a message with flight information that provides a planned, predicted, or estimated weight (e.g., 70 tons) for aircraft 110, and the message received from the flight information system associated with the flight may include a weight value that was actually entered or input into the flight management system.

[0062] If the verification module 206 determines that the weight values ​​in the message are not the same, e.g., the weight value sent to the flight information system associated with the flight does not match the weight value received at the flight information system associated with the flight or entered into the flight management system of the aircraft 110, the verification module 206 can determine whether the weight value is within a predetermined threshold (e.g., ±100 pounds). If so, the verification module 206 can determine that the flight information matches and the flight information sent to the flight information system associated with the flight has been correctly entered into the flight information system. Otherwise, the verification module 206 determines that there is a mismatch and that incorrect flight information was entered into the flight information system. Other examples of flight information that may be important for verification include performance initialization data, takeoff reference data, and / or the like.

[0063] In one embodiment, notification module 208 is configured to provide a notification in response to verification module 206 verifying that the flight information sent in the message to the flight information system associated with the flight does not match the flight information received in the message from the flight information system associated with the flight. The notification may include, for example, a push notification to a mobile application, a text message, an email message, a website posting, a web service, and / or the like.

[0064] In some embodiments, the type and method of delivery of notifications provided by the notification module 208 depends on the prominence, importance, and / or the like of the flight information. For example, if the flight information is relatively important and the verification module 206 determines that the flight information is not correctly entered based on a comparison of messages sent and received from a flight information system associated with the flight, the notification module 208 may trigger an alarm, alert, push notification, etc. intended to attract the attention of a user (e.g., ground crew, flight traffic controller, etc.) by triggering sounds, lights, obstructing a user display with a message, triggering an emergency call or alarm, and / or the like. Otherwise, if the flight information is less important, the notification module 208 may send a less noticeable or less distracting notification to the user.

[0065] In one embodiment, the input event module 210 is configured to detect an input event in response to flight information in a message received at a flight information system associated with a flight being input into a flight management system. As described above, flight information received at a flight information system associated with a flight may be manually input into a flight management system by an air traffic controller, pilot, or other crew member, may be verified and confirmed by an air traffic controller, pilot, or other crew member for automatic input into a flight information system, or may be automatically input into a flight information system without verification. The type of feedback required to input flight information into a flight information system may depend on the significance, importance, etc. of the flight information, which may be indicated in a message received at a flight information system associated with a flight using a flag or other indicator.

[0066] In one embodiment, the flight information system or the aircraft 110 may issue a signal, alert, notification, event, and / or the like in response to flight information being input into the flight information system. In response to the event, the input event module 210 performs the following operations: triggering the flight information retrieval module 202 to retrieve the message sent to the aircraft 110; triggering the message receiving module 204 to query or receive the flight information input into the flight information system in response to receiving a message with the flight information at the flight information system associated with the flight; and triggering the verification module 206 to verify that the flight information received at the flight information system associated with the flight matches the flight information input into the flight information system. Alternatively, or in addition, in one embodiment, the input event module 210 is configured to listen, subscribe, and / or register to receive and / or queue incoming and / or outgoing messages when incoming and / or outgoing messages that can be used to verify flight information are sent and received.

[0067] Figure 3A One embodiment of a flight information verification system (FIVS) 301 is depicted. In one embodiment, the FIVS 301 is a ground-based message computing system that is connected to the aircraft 110 via a network such as the Internet (e.g., an Internet Protocol network) 302, an ACARS (e.g., a satellite or radio air band) network 304, and / or the like. A message router 306 (which may be implemented as or used by the flight information retrieval module 202 and / or the message receiving module 204) may be configured to send messages from the FIVS 301 to the aircraft 110 through the networks 302, 304, and / or receive messages from the aircraft 110 at the FIVS 301. The message router 306 may be implemented as a standalone device (e.g., a message server) or a hardware and / or software module.

[0068] In one embodiment, the message router 306 may store messages that have been sent or queued to be sent to the aircraft 110 in the database 310 along with an identifier that uniquely identifies the message. The message router 306 may also store messages received from the aircraft 110 that contain flight information from the flight management system of the aircraft 110 in the database 310 along with an identifier for the received message and an identifier for the corresponding message sent to the aircraft 110. In one embodiment, the verification module 206 may use or trigger a message comparator 308 (e.g., an IP message or ACARS message comparator) to compare the flight information portion of the message sent to the aircraft 110 and the message received from the aircraft 110 to determine whether the flight information matches. The message comparator 308 may store the compared messages, the comparison results, and / or other attributes of the messages (e.g., the type of message, the percentage of match, whether the flight information is exactly the same or within a predetermined threshold, the importance or significance of the flight information, and / or the like) in an active or temporary data store (such as the database 312).

[0069] Notification module 208 may examine the comparison results to determine whether to send a notification regarding the mismatch in flight information. In the depicted embodiment, notification module 208 may provide a message or other information to network service 314 for presentation to user 320 on a web page served by network server 316. The notification may include whether the information matches, a threshold used to determine a match, the prominence or importance of the information, the time the message was sent, the state of aircraft 110 (e.g., altitude, speed, etc.) when the message was sent, and / or the like.

[0070] Figure 3B Another embodiment of a flight information validation system ("FIVS") 301 is depicted. Figure 3B Basically similar to the above Figure 3A FIVS 301 as described in. Figure 3B The FIVS 301 is depicted as a ground-based message computing system connected to the aircraft 110 via a local network 340 and a message router 342 that may be located on the local network 340. As used herein, the local network 340 is configured to handle multiple communication protocols (e.g., Internet, airline, air traffic control protocols) over multiple communication channels (e.g., Internet, radio or satellite networks).

[0071] Similar to Figure 3A In the FIVS 301 in FIG. 1 , the local message comparator 344 may compare the flight information of the message sent to the aircraft 110 with the corresponding flight information of the message received from the aircraft 110. The results of the comparison may be stored in the database 312, such as and / or the like such a relational database.

[0072] The notification module 208 provides a notification to one or more users 320 via a web service 346, such as a web service built on a JavaScript engine, based on the results of the comparison. The notification can then be presented to the user 320 via a web page provided by the web server 348.

[0073] Figure 4 is a schematic flow chart illustrating one embodiment of a method 400 for verifying flight information. The method 400 begins and retrieves 402 a first message including flight information entered into a flight information system associated with a flight. The method 400 receives 404 a second message including flight information entered into a flight information system associated with the flight based on the first message.

[0074] The method 400 determines 406 whether the flight information from the first message matches the flight information from the second message. If so, the method 400 ends. Otherwise, the method 400 provides 408 a notification in response to verifying that the flight information sent in the first message does not match the flight information received in the second message, and the method 400 ends. In some embodiments, the flight information retrieval module 202, the message receiving module 204, the verification module 206, and the notification module 208 perform multiple steps of the method 400.

[0075] Figure 5 is a schematic flow chart illustrating one embodiment of a method 500 for verifying flight information. The method 500 begins and determines 502 whether an input event is detected, e.g., whether flight information has been input or entered into a flight information system. If not, the method 500 continues to monitor 502 for input events. Otherwise, the method 500 includes retrieving 504 a first message including flight information that was input into a flight information system associated with the flight.

[0076] The method 500 receives 506 a second message including flight information input into a flight information system associated with the flight based on the first message. The method 500 determines 508 whether the flight information from the first message matches the flight information from the second message within a predetermined threshold. If so, the method 500 continues to monitor 502 for input events.

[0077] Otherwise, the method determines 510 the significance, importance, etc. of the flight information, and / or a mismatch (e.g., degree or amount of difference) between the flight information from the message sent to the flight information system associated with the flight and the message received from the flight information system associated with the flight. The method 500 provides 512 a notification in response to verifying that the flight information sent in the first message does not match the flight information received in the second message based on the significance and / or mismatch of the flight information, and the method 500 ends. In some embodiments, the flight information retrieval module 202, the message receiving module 204, the verification module 206, the notification module 208, and the input event module 210 perform multiple steps of the method 500.

[0078] In the above description, certain terms may be used, such as "upper", "lower", "upper", "lower", "horizontal", "vertical", "left", "right", "above", "below", etc. When appropriate, these terms are used to provide some clear description when dealing with relative relationships. However, these terms are not intended to imply absolute relationships, positions and / or orientations. For example, with respect to an object, the "upper" surface can become the "lower" surface simply by turning the object over. Nevertheless, it is still the same object. In addition, unless otherwise expressly stated, the terms "include", "comprise", "have" and their variations mean "including but not limited to". Unless otherwise expressly stated, the list of items listed does not imply that any or all of the items in the items are mutually exclusive and / or mutually inclusive. Unless otherwise expressly stated, the terms "one", "an" and "the" also refer to "one or more". In addition, the term "multiple" can be defined as "at least two".

[0079] In addition, examples of an element "connected" to another element in this specification may include direct and indirect connections. Direct connection may be defined as an element connected to another element and forming a certain contact with the other element. Indirect connection may be defined as a connection between two elements that are not in direct contact with each other, but have one or more additional elements between the connected elements. In addition, as used herein, fixing an element to another element may include direct fixing and indirect fixing. In addition, as used herein, "adjacent" does not necessarily mean contact. For example, an element may be adjacent to another element without contacting the element.

[0080] Unless otherwise specifically stated or understood in the context of use, conditional language used herein, such as, specifically, "can," "may," "might," "likely," "for example," and the like, is generally intended to convey that certain examples include certain features, elements, and / or steps, while other examples do not. Thus, such conditional language is generally not intended to imply that one or more examples require features, elements, and / or steps in any way, or that one or more examples must include logic for determining (whether or not there is input or prompting) whether these features, elements, and / or steps are included in any particular example or are to be performed in any particular example. Similarly, the term "or" is used in its inclusive sense (rather than in its exclusive sense), such that, for example, when used to connect a list of elements, the term "or" means one, some, or all of the elements in the list.

[0081] As used herein, when used with a list of items, the phrase "at least one" means that different combinations of one or more of the listed items can be used, and only one of the items in the list may be needed. The item can be a specific object, thing, or category. In other words, "at least one" means that any combination of items or the number of items can be used from the list, but not all items in the list may be needed. For example, "at least one of item A, item B, and item C" may mean item A; item A and item B; item B; item A, item B, and item C; or item B and item C. In some cases, "at least one of item A, item B, and item C" may mean, for example, but not limited to, two of item A, one of item B, and ten of item C; four of item B and seven of item C; or other suitable combinations.

[0082] Unless otherwise indicated, the terms "first", "second", etc. are used herein merely as labels and are not intended to impose order, position, or hierarchy requirements on the items to which these terms refer. Furthermore, reference to an item, such as a "second", does not require or preclude the existence of an item, such as a "first" or lower numbered item and / or an item, such as a "third" or higher numbered item.

[0083] As used herein, a system, device, structure, article, element, component, or hardware that is "configured to" perform a specified function is actually capable of performing the specified function without any changes, rather than merely having the potential to perform the specified function after further modification. In other words, a system, device, structure, article, element, component, or hardware that is "configured to" perform a specified function is specifically selected, created, implemented, utilized, programmed, and / or designed for the purpose of performing the specified function. As used herein, "configured to" means an existing feature of a system, device, structure, article, element, component, or hardware that enables the system, device, structure, article, element, component, or hardware to perform the specified function without further modification. For the purposes of this disclosure, a system, device, structure, article, element, component, or hardware that is described as "configured to" perform a particular function may be additionally or alternatively described as "suitable for" and / or "operative to" perform that function.

[0084] The schematic flow chart included herein is generally described as a logical flow chart. In this way, the sequence and the marked steps depicted represent an embodiment of the proposed method. Other steps and methods that are equivalent to one or more steps or parts thereof of the method shown in function, logic or effect can be envisioned. In addition, the format and symbols adopted are provided to explain the logical steps of the method, and are understood to not limit the scope of the method. Although various arrow types and line types can be adopted in the flow chart, it should be understood that they do not limit the scope of the corresponding method. In fact, some arrows or other connectors can be used to represent only the logical flow of the method. For example, an arrow can represent a waiting or monitoring period of unspecified duration between the enumerated steps of the method depicted. In addition, the order in which a particular method occurs may strictly comply with or may not strictly comply with the order of the corresponding steps shown.

[0085] The implementation of the various modules may take the form of a fully hardware implementation, a fully software implementation (including firmware, resident software, microcode, etc.), or an implementation that combines software and hardware aspects, which are generally referred to herein as "circuits," "modules," or "systems." In addition, the implementation may take the form of a program product implemented in one or more computer-readable storage devices, which store machine-readable code, computer-readable code, and / or program code, hereinafter referred to as code. The storage device may be tangible, non-transitory, and / or non-transmitting. The storage device may not contain signals. In some embodiments, the storage device only uses signals to access the code.

[0086] Modules may be implemented as hardware circuits including custom very-large-scale integration (VLSI) circuits or gate arrays, off-the-shelf semiconductors (such as logic chips, transistors or other discrete components). Modules may also be implemented as programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices, etc.

[0087] Modules may also be implemented as code and / or software to be executed by various types of processors. The identified module of code may, for example, include one or more physical or logical blocks of executable code, which may, for example, be organized into objects, procedures, or functions. However, the executable files of the identified modules do not have to be physically together, but may include different instructions stored in different locations, which, when logically combined together, constitute the module and achieve the stated purpose of the module.

[0088] In fact, a code module can be a single instruction, or many instructions, and can even be distributed on several different code segments, between different programs, and across several storage devices. Similarly, operational data can be identified and illustrated herein within a module, and can be implemented in any suitable form and can be organized within a data structure of any suitable type. Operational data can be collected into a single data set, or can be distributed in different locations, including being distributed on different computer-readable storage devices. When a module or part of a module is implemented as software, the software portion is stored on one or more computer-readable storage devices.

[0089] The module may utilize any combination of one or more computer readable media. The computer readable medium may be a computer readable storage medium. The computer readable storage medium may be a storage device storing code. The storage device may be, for example but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical or semiconductor system, device or apparatus, or any suitable combination of the foregoing.

[0090] More specific examples of storage devices (a non-exhaustive list) would include the following: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer-readable storage medium may be any tangible medium that can contain or store a program for use by or in connection with an instruction execution system, apparatus, or device.

[0091] The code for performing the operations of the embodiments may be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Python, Ruby, Java, Smalltalk, C++, and the like, as well as conventional procedural programming languages ​​such as the "C" programming language, and / or machine languages ​​such as assembly languages. The code may be executed entirely on the user's computer, partially on the user's computer, as a separate data packet, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the latter case, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or a connection may be established with an external computer (e.g., through the Internet using an Internet service provider).

[0092] Without departing from the spirit or essential features of the present invention, the subject matter may be implemented in other specific forms. The described embodiments are considered to be illustrative and non-restrictive in all respects. All changes that fall within the equivalent meaning and scope of the claims should be included within the scope of the claims.

[0093] Furthermore, the present disclosure includes implementations according to the following clauses:

[0094] Clause 1. A method (400 / 500), the method (400 / 500) comprising the steps of:

[0095] retrieving (402 / 504) a first message including flight information entered into a flight information system associated with the flight;

[0096] receiving (404 / 506) a second message including flight information entered into a flight information system associated with the flight based on the first message;

[0097] verifying (406 / 508) that the flight information sent in the first message matches the flight information received in the second message; and

[0098] A notification is provided (408 / 512) in response to verifying that the flight information sent in the first message does not match the flight information received in the second message.

[0099] Clause 2. A method (400 / 500) according to clause 1, wherein, in response to determining that the flight information received in the second message is within a threshold of the flight information sent in the first message, the flight information sent in the first message matches the flight information received in the second message.

[0100] Clause 3. The method (400 / 500) of any one of clauses 1 to 2, wherein the first message and the second message comprise different format types such that the first message and the second message are parsed to identify flight information in each message for verification.

[0101] Clause 4. The method (400 / 500) of clause 3, wherein the verification (406) comprises comparing the flight information of the first message and the second message based on the formats of the first message and the second message to determine whether the flight information of the first message matches the flight information of the second message.

[0102] Clause 5. A method (400 / 500) according to clause 4, wherein the comparison of flight information between the first message and the second message is performed on one or more of the following: on a per-bit basis, on a per-byte basis, on a per-character basis, on a per-data field basis, and on a per-message basis.

[0103] Clause 6. A method (400 / 500) according to any one of clauses 1 to 5, wherein the flight information sent in the first message is entered into the flight information system in response to one of when the first message is received and when a user approves the entry of the flight information.

[0104] Clause 7. The method (400 / 500) according to Clause 6 further comprises the following steps: detecting (502) an input event in response to flight information in the first message being entered into the flight information system, wherein, in response to the input event, the first message is retrieved and the flight information is received in the second message.

[0105] Clause 8. A method (400 / 500) according to any one of clauses 1 to 7, wherein the type and delivery method of the notification provided is determined (510) based on the significance of flight information entered into the flight information system and which does not match the flight information sent in the first message.

[0106] Clause 9. The method (400 / 500) of any one of clauses 1 to 8, wherein the notification is configured as one or more of a push notification to a mobile application, a text message, an email message, a website, and a web service.

[0107] Clause 10. The method (400 / 500) of any one of clauses 1 to 9, wherein one of the first message and the second message comprises an Aircraft Communications Addressing and Reporting System ("ACARS") message format.

[0108] Clause 11. The method (400 / 500) of any one of clauses 1 to 10, wherein the second message is published and broadcast to a system subscribed to receive messages including flight information input into the flight information system.

[0109] Clause 12. The method (400 / 500) of any one of clauses 1 to 11, wherein the second message is received from the flight information system in response to a query for the flight information.

[0110] Clause 13. A device (104), the device (104) comprising:

[0111] Processor; and

[0112] A memory storing executable code executable by the processor to perform the following steps:

[0113] retrieving (202) a first message including flight information entered into a flight information system associated with the flight;

[0114] receiving (204) a second message including flight information entered into a flight information system associated with the flight based on the first message;

[0115] verifying (206) that the flight information sent in the first message matches the flight information received in the second message; and

[0116] A notification is provided (208) in response to verifying that the flight information sent in the first message does not match the flight information received in the second message.

[0117] Clause 14. A device (104) according to clause 13, wherein, in response to determining that the flight information received in the second message is within a threshold of the flight information sent in the first message, the flight information sent in the first message matches the flight information received in the second message.

[0118] Clause 15. The device (104) of any one of clauses 13 to 14, wherein the first message and the second message comprise different format types such that the first message and the second message are parsed to identify flight information in each message for verification.

[0119] Clause 16. An apparatus (104) according to clause 15, wherein the code can be further executed by the processor to verify (206) the flight information in each message by comparing the flight information of the first message and the second message based on the format of the first message and the second message to determine whether the flight information of the first message matches the flight information of the second message.

[0120] Clause 17. An apparatus (104) according to clause 16, wherein the comparison of the flight information between the first message and the second message is performed on one or more of the following: on a per-bit basis, on a per-byte basis, on a per-character basis, on a per-data field basis, and on a per-message basis.

[0121] Clause 18. An apparatus (104) according to any one of clauses 13 to 17, wherein the code is further executable by the processor to detect (210) an input event in response to flight information in the first message being entered into the flight information system, wherein, in response to the input event, the first message is retrieved and the flight information is received in the second message, and in response to one of when the first message is received and when the user approves the entry of the flight information, the flight information sent in the first message is entered into the flight information system.

[0122] Clause 19. An apparatus (104) according to any one of clauses 13 to 18, wherein the type and method of delivery of the notification provided is determined based on the significance of flight information input into the flight information system and which does not match the flight information sent in the first message.

[0123] Clause 20. A program product comprising a computer-readable storage medium storing executable code executable by a processor, the executable code comprising code for:

[0124] retrieving (202) a first message including flight information entered into a flight information system associated with the flight;

[0125] receiving (204) a second message including flight information entered into a flight information system associated with the flight based on the first message;

[0126] verifying (206) that the flight information sent in the first message matches the flight information received in the second message; and

[0127] A notification is provided (208) in response to verifying that the flight information sent in the first message does not match the flight information received in the second message.

Claims

1. A method for verifying flight information, the method comprising the following steps: retrieving a first message sent to a flight information system associated with the flight, the first message including flight information associated with at least one flight setting of the aircraft input into the flight information system; querying, from the flight information system, flight information associated with the at least one flight setting of the aircraft; receiving a second message from the flight information system, the second message including queried flight information input into the flight information system; verifying that the flight information sent in the first message matches the flight information received in the second message to confirm that the flight information sent in the first message was correctly entered into the flight information system, wherein the flight information sent in the first message matches the flight information received in the second message in response to determining that a percentage of matches between the first message and the second message satisfies a threshold; and In response to verifying that the flight information sent in the first message does not match the flight information received in the second message, providing a notification, the notification including the time when the first message and the second message were sent and the status of the aircraft that was different from the flight information when the first message and the second message were sent.

2. The method according to claim 1, wherein: The first message and the second message include different format types, so that the first message and the second message are parsed to identify the flight information in each message for verification.

3. The method according to claim 2, wherein: The verification includes comparing the flight information of the first message and the second message based on the formats of the first message and the second message to determine whether the flight information of the first message matches the flight information of the second message.

4. The method according to claim 3, wherein: The comparison of the flight information between the first message and the second message is performed on one or more of: a per-bit basis, a per-byte basis, a per-character basis, a per-data field basis, and a per-message basis.

5. The method according to any one of claims 1 to 4, wherein: In response to one of when the first message is received and when a user approves input of the flight information, the flight information sent in the first message is input into the flight information system.

6. The method according to any one of claims 1 to 4, wherein: The type of notification provided and the method of delivery are determined based on the significance of the flight information input into the flight information system and that does not match the flight information sent in the first message.

7. A device for verifying flight information, the device comprising: processor; as well as A memory storing executable code executable by the processor to perform the following steps: retrieving a first message sent to a flight information system associated with the flight, the first message including flight information associated with at least one flight setting of the aircraft input into the flight information system; querying, from the flight information system, flight information associated with the at least one flight setting of the aircraft; receiving a second message from the flight information system, the second message including queried flight information input into the flight information system; verifying that the flight information sent in the first message matches the flight information received in the second message to confirm that the flight information sent in the first message was correctly entered into the flight information system, wherein the flight information sent in the first message matches the flight information received in the second message in response to determining that a percentage of matches between the first message and the second message satisfies a threshold; and In response to verifying that the flight information sent in the first message does not match the flight information received in the second message, providing a notification, the notification including the time when the first message and the second message were sent and the status of the aircraft that was different from the flight information when the first message and the second message were sent.

8. A program product for verifying flight information, the program product comprising a computer-readable storage medium storing executable code executable by a processor, the executable code comprising code for performing the following operations: retrieving a first message sent to a flight information system associated with the flight, the first message including flight information associated with at least one flight setting of the aircraft input into the flight information system; querying, from the flight information system, flight information associated with the at least one flight setting of the aircraft; receiving a second message from the flight information system, the second message including queried flight information input into the flight information system; verifying that the flight information sent in the first message matches the flight information received in the second message to confirm that the flight information sent in the first message was correctly entered into the flight information system, wherein In response to determining that the percentage of matches between the first message and the second message satisfies a threshold, the flight information sent in the first message matches the flight information received in the second message; and In response to verifying that the flight information sent in the first message does not match the flight information received in the second message, providing a notification, the notification including the time when the first message and the second message were sent and the status of the aircraft that was different from the flight information when the first message and the second message were sent.