# US 10,482,774 B2 · Management of notices to airmen > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 10,482,774 B2 - Document ID: US10482774B2 - Status: Granted - Kind: B2 - Application number: 15/849,359 - Filed: 2017-12-20 - Published: 2018-06-28 - Granted: 2019-11-19 - Earliest claimed: 2016-12-22 - Assignees: Thales - Applicants: Thales - Inventors: Antoine-adrien Bonnet; Christophe Lerat - Web page: https://patentgrep.com/patent/US10482774B2 ## CPC - G08G 5/34: for flight plan modification - G06F 40/30: Semantic analysis - G08G 5/21: located onboard the aircraft - G08G 5/26: Transmission of traffic-related information between aircraft and ground stations - G08G 5/50: Navigation or guidance aids - G08G 5/51: for control when on the ground, e.g. taxiing or rolling - G08G 5/54: for approach or landing - G08G 5/55: for a single aircraft - G08G 5/74: for monitoring terrain - G08G: TRAFFIC CONTROL SYSTEMS (guiding railway traffic, ensuring the safety of railway traffic B61L; arrangement of road signs or traffic signals E01F9/00; radar or analogous systems, sonar systems, lidar systems specially adapted for traffic control G01S13/91, G01S15/88, G01S17/88; {radar or analogous systems, sonar systems, lidar systems specially adapted for anti-collision purposes G01S13/93, G01S15/93, G01S17/93}) - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract A description is given of a method, implemented by a computer, for managing a notice to airmen, comprises the steps of: receiving at least one notice to airmen; receiving one or more elements of a navigation database associated with a flight plan of an aircraft; comparing the content of the received notice to airmen with the elements of the navigation database associated with a flight plan of an aircraft. Various developments describe in particular the detection of unavailable elements on the basis of analysis of the content of the messages, processing operations performed on the portion of the messages expressed in natural language, diverse methods of notifying the pilot, the intervention of third-party operators in the management of the messages, the enrichment of data and various implementation variants with regard to the system (flight management system FMS and/or electronic flight bag EFB). ## Claims ### Claim 1 A method, implemented by a computer, for managing a notice to airmen, comprising steps of: receiving at least one notice to airmen message with a computer; receiving one or more elements of a navigation database associated with a flight plan of an aircraft with the computer; comparing with the computer a content of the received notice to airmen message with the one or more elements of the navigation database associated with the flight plan of the aircraft; and carrying out semantic analysis with the computer of the content of the received notice to airmen message expressed in natural language. ### Claim 2 (depends on 1) The method according to claim 1, comprising a step of determining, on a basis of the content of the received notice to airmen message, that an element of the navigation database associated with the flight plan of the aircraft is unavailable. ### Claim 3 (depends on 1) The method according to claim 1, comprising a step of comparing the content of the received notice to airmen message with a database associated with a flight plan of the aircraft, and further comprising a step of determining a presence of one or more keywords from among a plurality of predefined keywords. ### Claim 4 (depends on 1) The method according to claim 1, comprising a step of associating the content of a notice to airmen message with one flight plan from among a plurality. ### Claim 5 (depends on 1) The method according to claim 1, comprising the step of notifying a pilot if a presence of an unavailable element has been determined. ### Claim 6 (depends on 5) The method according to claim 5, comprising the step of receiving confirmation of the element determined as being unavailable. ### Claim 7 (depends on 1) The method according to claim 1, comprising a step of tagging the navigation database. ### Claim 8 (depends on 1) The method according to claim 1, wherein an event for triggering a comparison and/or a notification step being dependent on a flight context and/or on a revision of a current flight plan of the aircraft. ### Claim 9 (depends on 8) The method according to claim 8, comprising a step of sending a reminder notification in an event of use of an element, determined as being unavailable, of the navigation database. ### Claim 10 (depends on 1) The method according to claim 1, comprising a step of collecting a plurality of notices to airmen. ### Claim 11 (depends on 1) The method according to claim 1, wherein the content of a message being enriched with non-avionic external data. ### Claim 12 (depends on 1) A computer program product, said computer program product comprising non-transitory code instructions configured to perform the steps of the method according to claim 1 when the non-transitory code instructions of said computer program product are executed on a computer. ### Claim 13 (depends on 1) A system comprising means for implementing the steps of the method according to claim 1. ### Claim 14 (depends on 13) The system according to claim 13, comprising an electronic flight bag (EFB) and/or a flight management system (FMS). ### Claim 15 (depends on 1) The method according to claim 1, wherein the computer comprises at least one of the following: an electronic flight bag (EFB) or a flight management system (FMS).