IP Library › Granted Patent US 12,306,893
Granted Patent B2
US 12,306,893 · App. 18/459,521 · Granted May 20, 2025

Flight-related data management system

Inventors: Ibrahim Brown (Jewett City, CT); Cami L. Santor (Glastonbury, CT); Roger Aiudi (Granby, CT); Patrick J. Smith (Vernon, CT); Fidel Galano (Chicago, IL)
Assignee: RTX Corporation
G06F16/9538G06F16/258G06F16/27
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,306,893
App. No.
18/459,521
Granted
May 20, 2025
Kind
B2
Abstract

A method of providing access to flight-related data of aircraft includes correlating a plurality of data sets that are different from each other and each contain flight-related data for one or more aircraft engines, to determine a plurality of flights of the one or more aircraft engines that correspond to the plurality of data sets. At least a portion of the flight-related data describes operation of the aircraft engines during the plurality of flights. The correlating is performed based on metadata of the plurality of data sets, and the plurality of data sets includes a plurality of first data sets that utilize a plurality of different schemas. The method also includes creating, for each of the plurality of flights and based on the correlating, a respective flight object that represents the flight and includes a plurality of discrete flight data objects that each correspond to a respective one of the plurality of data sets for the flight; and utilizing the flight object for one of the flights to provide access to one or more of the data sets for said one of the flights. A system for aircraft data management is also disclosed.

Claims (47)

1. A method of providing access to flight-related data of aircraft, comprising:

correlating a plurality of data sets that are different from each other and each contain flight-related data for one or more aircraft engines, to determine a plurality of flights of the one or more aircraft engines that correspond to the plurality of data sets, at least a portion of the flight-related data describing operation of the aircraft engines during the plurality of flights, wherein the correlating is performed based on metadata of the plurality of data sets, and the plurality of data sets includes a plurality of first data sets that utilize a plurality of different schemas;

creating, for each of the plurality of flights and based on the correlating, a respective flight object that represents the flight and includes a plurality of discrete flight data objects that each correspond to a respective one of the plurality of data sets for the flight; and

utilizing the flight object for one of the flights to provide access to one or more of the data sets for said one of the flights;

wherein the plurality of data sets includes:

a plurality of snapshot data sets corresponding to discrete events or portions of the plurality of flights; and

a plurality of full flight data sets that include data for entire ones of the plurality of flights.

2. The method of claim 1 , wherein the plurality of data sets also includes a plurality of second data sets that utilize one or more data formats that are different from one or more data formats of the plurality of first data sets.

3. The method of claim 1 , wherein the metadata that said correlating is performed based on includes serial numbers of the aircraft engines, and includes at least one of flight origins, flight destinations, and timestamps for the flights.

4. The method of claim 1 , comprising:

providing a search engine for accessing the plurality of data sets based on the flight objects;

wherein said utilizing the flight object is performed in response to a request to the search engine that identifies said one of the flights or one of the aircraft.

5. The method of claim 1 , wherein each flight data object describes the content and location of its corresponding data set.

6. The method of claim 1 , wherein each flight object includes a flight data object for at least one snapshot data set and a flight data object for at least one full flight data set.

7. The method of claim 1 , wherein said correlating includes:

determining that a particular snapshot data set and a particular full flight data set that each identify a same aircraft engine both correspond to a particular flight of the plurality of flights for the aircraft engine based on a timestamp of the particular snapshot data set being between a start time and end time for said particular full flight data set.

8. The method of claim 1 , wherein said correlating includes:

determining that a first snapshot data set and a second snapshot data set that each identify a same aircraft engine both correspond to a particular flight of the plurality of flights based on:

the first snapshot data set corresponding to a first event or first portion of the particular flight and occurring at a first time; and

the second snapshot data set corresponding to a second event or second portion of the particular flight and occurring at a second time that is within an expected time window for the second event or second portion after said first event or first portion.

9. The method of claim 1 , wherein the plurality of first data sets are from a plurality of different sources, and different ones of the schemas correspond to different ones of the sources.

10. The method of claim 1 , wherein said utilizing the flight object for one of the flights to provide access to one or more of the data sets for said one of the flights includes:

determining a subset of the plurality of the datasets that correspond to a particular flight;

performing analytics for the particular flight based on the determined subset of the plurality of data sets; and

linking results of the analytics for the flight with the flight object for the flight.

11. A system for aircraft data management, comprising:

processing circuitry operatively connected to memory and configured to:

correlate a plurality of data sets that are different from each other and each contain flight-related data for one or more aircraft engines, to determine a plurality of flights of the one or more aircraft engines that correspond to the plurality of data sets, at least a portion of the flight-related data describing operation of the aircraft engines during the plurality of flights, wherein the correlation is performed based on metadata of the plurality of data sets, and the plurality of data sets includes a plurality of first data sets that utilize a plurality of different schemas;

create, for each of the plurality of flights and based on the correlating, a respective flight object that represents the flight and includes a plurality of discrete flight data objects that each correspond to a respective one of the plurality of data sets for the flight; and

utilize the flight object for one of the flights to provide access to one or more of the data sets for said one of the flights;

wherein the plurality of data sets includes:

a plurality of snapshot data sets corresponding discrete events or portions of the plurality of flights; and

a plurality of full flight data sets that include data from flight recorders for entire ones of the plurality of flights.

12. The system of claim 11 , wherein the plurality of data sets also includes a plurality of second data sets that utilize one or more data formats that are different from one or more data formats of the plurality of first data sets.

13. The system of claim 11 , wherein the metadata that the correlation is based on includes serial numbers of the aircraft engines, and includes at least one of flight origins, flight destinations, and timestamps for the flights.

14. The system of claim 11 , wherein each flight data object describes the content and location of its corresponding data set.

15. The system of claim 12 , wherein as part of the correlation, the processing circuitry is configured to:

determine that a particular snapshot data set and a particular full flight data set that each identify a same engine both correspond to a particular flight of the plurality of flights for the engine based on a timestamp of the particular snapshot data set being between a start time and end time for said particular full flight data set.

16. The system of claim 11 , wherein as part of the correlation, the processing circuitry is configured to:

determine that a first snapshot data set and a second snapshot data set that each identify a same engine both correspond to a particular flight of the plurality of flights based on:

the first snapshot data set corresponding to a first event or first portion of the particular flight and occurring at a first time; and

the second snapshot data set corresponding to a second event or second portion of the particular flight and occurring at a second time that is within an expected time window for the second event or second portion after said first event or first portion.

17. The system of claim 11 , wherein the plurality of first data sets are from a plurality of different sources, and different ones of the schemas correspond to different ones of the sources.

18. The system of claim 11 , as part of the utilization of the flight object for one of the flights to provide access to one or more of the data sets for said one of the flights, processing circuitry is configured to:

determine a subset of the plurality of the datasets that correspond to a particular flight;

perform analytics for the particular flight based on the determined subset of the plurality of data sets; and

link results of the analytics for the flight with the flight object for the flight.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 6, 2023
From: BROWN, IBRAHIM; SANTOR, CAMI L.; AIUDI, ROGER; SMITH, PATRICK J.; GALANO, FIDEL
To: RTX CORPORATION
Reel/Frame 064811/0463 →
Continuity (1)
Related Publication 20250077600A1 · Mar 6, 2025
References Cited (21)
US 6480770B1 · Wischmeyer · 2002 [cited by examiner]
US 6606546B2 · Sinex · 2003 [cited by examiner]
US 7983809B2 · Kell · 2011 [cited by examiner]
US 8234068B1 · Young · 2012 [cited by examiner]
US 10057144B2 · Lam et al. · 2018 [cited by applicant]
US 10364049B2 · Floyd · 2019 [cited by examiner]
US 11681929B2 · Strong · 2023 [cited by applicant]
US 20110144897A1 · Dunsky · 2011 [cited by applicant]
US 20130013134A1 · Lieu · 2013 [cited by examiner]
US 20170124780A1 · Jensen · 2017 [cited by examiner]
US 20170233105A1 · Vali · 2017 [cited by examiner]
US 20190019354A1 · Jordan · 2019 [cited by examiner]
US 20190177008A1 · Floyd · 2019 [cited by examiner]
US 20200219409A1 · Cambon · 2020 [cited by examiner]
US 20200371678A1 · Angelini · 2020 [cited by examiner]
US 20210264497A1 · Annakov · 2021 [cited by examiner]
US 20220238025A1 · McCann et al. · 2022 [cited by applicant]
US 20230177966A1 · Janakiraman · 2023 [cited by examiner]
US 20240002067A1 · Guthrie · 2024 [cited by examiner]
US 20240105062A1 · Leones · 2024 [cited by examiner]
European Search Report for European Patent Application No. 24198000.2 dated Jan. 9, 2025. [cited by applicant]