Optimized flight monitoring and turnaround handling

Patent metadata

Field	Value
Publication number	US-2025232681-A1
Application number	US-202418412345-A
Country	US
Kind code	A1
Filing date	Jan 12, 2024
Priority date	Jan 12, 2024
Publication date	Jul 17, 2025
Grant date	—

Abstract

The present disclosure provides techniques for optimized flight monitoring. A first set of traffic data for a flight is accessed. The first set of traffic data is saved in a data store. A user interface is updated to display the first set of traffic data for the flight. A second set of traffic data for the flight is received, where the second set of traffic data is received at a later time than the first set of traffic data. A progress of the flight is monitored by comparing the first and second sets of traffic data. Upon detecting a delay in the progress of the flight, the flight is highlighted on the user interface.

First claim

What is claimed is:

1 . A method comprising:
accessing a first set of traffic data for a flight; storing the first set of traffic data in a data store; updating a user interface to display the first set of traffic data for the flight; receiving a second set of traffic data for the flight, wherein the second set of traffic data is received at a later time than the first set of traffic data; monitoring a progress of the flight by comparing the first and second sets of traffic data; and upon detecting a delay in the progress of the flight, highlighting the flight on the user interface.

2 . The method of claim 1 , wherein:
the first set of traffic data is received at a first time when an aircraft associated with the flight has not landed, and the first set of traffic data comprises a first estimated time of arrival (ETA) of the flight; the second set of traffic data is received at a second time when the aircraft associated with the flight has not landed, and the second set of traffic data comprises a second estimated time of arrival (ETA) of the flight; and detecting the delay in the progress of the flight further comprises determining that the second ETA is later than the first ETA.

3 . The method of claim 1 , wherein:
the first set of traffic data is received at a first time when an aircraft associated with the flight has not landed, and the first set of traffic data comprises a first estimated time of arrival (ETA) of the flight; the second set of traffic data is received at a second time when the aircraft associated with the flight has already landed, and the second set of traffic data comprises an actual time of arrival (ATA); and detecting the delay in the progress of the flight further comprises determining that the ATA is later than the first ETA.

4 . The method of claim 1 , wherein each of the first and second sets of traffic data for the flight comprises at least one of:
(i) a flight identification number for the flight; (ii) a call sign for the flight; (iii) a registration number for an aircraft associated with the flight; (iv) an arrival airport of the flight; (v) a departure airport of the flight; (vi) a date of the flight; (vii) an estimated off-block time (EOBT); (viii) an estimated take-off time (ETOT); (vx) an estimated time of arrival (ETA); (x) an actual take-off time (ATOT); (xi) an actual time of arrival (ATA); or (xii) flight state information.

5 . The method of claim 1 , further comprising:
updating the user interface to display the second set of traffic data for the flight; and updating the data store to store the second set of traffic data for the flight.

6 . The method of claim 1 , further comprising:
identifying a linking flight associated with the flight; receiving traffic data for the linking flight; and calculating a turnaround time for the linking flight based on a comparison between the traffic data for the linking flight and the second set of traffic data for the flight.

7 . The method of claim 6 , wherein the linking flight is scheduled to depart subsequent to the arrival of the flight and is operationally linked to the flight for aircraft allocation.

8 . The method of claim 6 , wherein:
the second set of traffic data for the flight is received at a second time when an aircraft associated with the flight has already landed; the second set of traffic data for the flight comprises an actual time of arrival (ATA) of the flight; the traffic data for the linking flight comprises an estimated off-block time (EOBT) of the linking flight; and the turnaround time for the linking flight is determined based on a difference between the EOBT of the linking flight and the ATA of the flight.

9 . The method of claim 6 , further comprising:
updating the user interface to display the turnaround time for the linking flight; and updating the data store to store the turnaround time for the linking flight.

10 . The method of claim 6 , further comprising highlighting the linking flight on the user interface when the turnaround time for the linking flight falls below a defined threshold.

11 . The method of claim 6 , further comprising:
receiving additional traffic data for the flight; and updating the turnaround time for the linking flight using the additional traffic data for the flight.

12 . The method of claim 11 , wherein the additional traffic data for the flight comprises a travel time between a time when an aircraft associated with the flight landed at an arrival airport and a time when the aircraft arrived at a gate.

13 . The method of claim 12 , wherein:
the second set of traffic data for the flight is received at a second time when an aircraft associated with the flight has already landed; the second set of traffic data for the flight comprises an actual time of arrival (ATA) of the flight; the traffic data for the linking flight comprises an estimated off-block time (EOBT) of the linking flight; and the turnaround time for the linking flight is determined based on a difference between the EOBT of the linking flight and a sum of the ATA and the travel time of the flight.

14 . A system comprising:
one or more computer processors; and one or more memories collectively containing one or more programs, which, when executed by the one or more computer processors, perform operations, the operations comprising:
accessing a first set of traffic data for a flight;
storing the first set of traffic data into a data store;
updating a user interface to display the first set of traffic data for the flight;
receiving a second set of traffic data for the flight, wherein the second set of traffic data is received at a later time than the first set of traffic data;
monitoring a progress of the flight by comparing the first and second sets of traffic data; and
upon detecting a delay in the progress of the flight, highlighting the flight on the user interface.

15 . The system of claim 14 , wherein:
the first set of traffic data is received at a first time when an aircraft associated with the flight has not landed, and the first set of traffic data comprises a first estimated time of arrival (ETA) of the flight; the second set of traffic data is received at a second time when the aircraft associated with the flight has not landed, and the second set of traffic data comprises a second estimated time of arrival (ETA) of the flight; and detecting the delay in the progress of the flight further comprises determining that the second ETA is later than the first ETA.

16 . The system of claim 14 , wherein:
the first set of traffic data is received at a first time when an aircraft associated with the flight has not landed, and the first set of traffic data comprises a first estimated time of arrival (ETA) of the flight; the second set of traffic data is received at a second time when the aircraft associated with the flight has already landed, and the second set of traffic data comprises an actual time of arrival (ATA); and detecting the delay in the progress of the flight further comprises determining that the ATA is later than the first ETA.

17 . The system of claim 14 , wherein the one or more programs, which, when executed on any combination of the one or more computer processors, perform the operations further comprising:
identifying a linking flight associated with the flight; receiving traffic data for the linking flight; and calculating a turnaround time for the linking flight based on a comparison between the traffic data for the linking flight and the

Assignees

• Boeing Co

Inventors

• Güemes Jiménez Alejandro
• Costas Pablo
• Lopez Leones Javier
• Peña Ortiz Nicolas
• Muñoz Hernández Andrés
• Morales Tirado Elisa

Classifications

• G08G5/727

  from a ground station · CPC title

• G08G5/34 Primary

  for flight plan modification · CPC title

• G08G5/20 Primary

  Arrangements for acquiring, generating, sharing or displaying traffic information (arrangements for monitoring traffic G08G5/72) · CPC title