IP Library Granted Patent US 12,587,266
Granted Patent B2
US 12,587,266 · App. 16/598,716 · Granted Mar 24, 2026

Systems and methods for using flight data recorder data

Inventor: Eduardo M. Carro (Sarasota, FL)
H04B7/18508G08G5/20H04L65/61H04L67/12
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,587,266
App. No.
16/598,716
Granted
Mar 24, 2026
Kind
B2
Abstract

A flight data recorder (FDR) may include a script engine configured to run an algorithm in order to obtain, analyze and use FDR and Cockpit Voice and Data Recorder (CVDR) data for non-Technical Standard Orders (TSO) applications. The script engine may be configured, by the algorithm, to analyze flight data received by the FDR and use the flight data to output a trigger via an Ethernet port or an ARINC 429 output. The script engine may also analyze the flight data and stream at least a portion of the flight data via the Ethernet port or the ARINC port.

Claims (32)

1 . A data processing method comprising:

a scripting engine disposed within a flight data recorder (FDR) receiving a plurality of algorithms from a script database within the flight data recorder; and

the scripting engine running the plurality of algorithms and thereby analyzing flight data and outputting a trigger from the FDR, based on the flight data, according to one or more of the plurality of algorithms.

2 . The data processing method according to claim 1 , wherein the outputting the trigger from the FDR comprises outputting the trigger via at least one of an Ethernet port and an Aeronautical Radio, Incorporated (ARINC) 429 output.

3 . The data processing method according to claim 2 , wherein the outputting the trigger further comprises outputting the trigger via the at least one of the Ethernet port and the ARINC 429 output to a server via a wireless transmission.

4 . The data processing method according to claim 1 , further comprising the FDR receiving the flight data from an external device.

5 . The data processing method according to claim 1 , wherein the FDR is a line replaceable unit, and the method further comprises loading the plurality of algorithms onto the script database of the flight data recorder via a data loader.

6 . The data processing method according to claim 1 , wherein the running the algorithm further comprises streaming at least a portion of the flight data from the FDR via at least one of an Ethernet port and an Aeronautical Radio, Incorporated (ARINC) 429 output.

7 . The data processing method according to claim 6 , wherein the streaming further comprises streaming at least the portion of the flight data via the at least one of the Ethernet port and the ARINC 429 output to at least one of a satellite data unit and an Automatic Dependent Surveillance-Broadcast (ADS-B) Mode S transponder.

8 . A flight data recorder (FDR) comprising:

a trigger script database which stores therein a plurality of algorithms;

a scripting engine configured to run the plurality of algorithms and thereby analyze flight data and output a trigger based on the flight data;

an Ethernet port; and

an Aeronautical Radio, Incorporated (ARINC) 429 output;

wherein the scripting engine is configured to output the trigger via at least one of the Ethernet port and the ARINC 429 output.

9 . The FDR according to claim 8 , wherein the Ethernet port and the ARINC 429 output are each configured to output data to a server via a wireless transmission.

10 . The FDR according to claim 8 , further comprising a flight data receiver configured to receive the flight data from an external device.

11 . The FDR according to claim 8 , further comprising:

a Python interpreter.

12 . The FDR according to claim 11 , wherein the FDR is a line replaceable unit, and the scripting engine is configured to receive the first algorithm and the second algorithm via a data loader.

13 . The FDR according to claim 11 , wherein the scripting engine is further configured to run the second algorithm and thereby stream Health and Usage Monitoring System (HUMS) flight data from the FDR via at least one of the Ethernet port and the ARINC 429 output.

14 . The FDR according to claim 8 , wherein the scripting engine is further configured to run the plurality of algorithms and thereby stream at least a portion of the flight data from the FDR via at least one of the Ethernet port and the ARINC 429 output.

15 . A flight data recorder (FDR) comprising:

a trigger script database which stores therein a plurality of algorithms;

a scripting engine configured to receive and run the plurality of algorithms;

an Ethernet port; and

an Aeronautical Radio, Incorporated (ARINC) 429 output;

wherein the scripting engine is further configured to:

receive and run a first algorithm of the plurality of algorithms;

receive and run a second algorithm of the plurality of algorithms, thereby changing an algorithm run by the scripting engine; and

by running the second algorithm, analyze flight data and output a trigger based on the flight data.

16 . The FDR according to claim 15 , wherein the scripting engine comprises a Python interpreter.

Assignments (3)
SECURITY INTEREST Recorded Mar 28, 2025
From: L3HARRIS AVIATION PRODUCTS, INC.
To: ARES CAPITAL CORPORATION
Reel/Frame 070662/0251 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 30, 2024
From: L3 TECHNOLOGIES, INC.
To: L3HARRIS AVIATION PRODUCTS, INC.
Reel/Frame 069269/0841 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 22, 2023
From: CARRO, EDUARDO M.
To: L3 TECHNOLOGIES, INC.
Reel/Frame 064993/0952 →
Continuity (2)
Provisional Application 62744510 · Oct 11, 2018
Related Publication 20200119806A1 · Apr 16, 2020
References Cited (13)
US 6493629B1 · Van Bosch · 2002 [cited by applicant]
US 9975640B1 · Wang · 2018 [cited by examiner]
US 10713859B1 · McZeal, Jr. · 2020 [cited by examiner]
US 20050228558A1 · Valette · 2005 [cited by examiner]
US 20120191273A1 · Jacobs · 2012 [cited by examiner]
US 20160055685A1 · Lilly · 2016 [cited by examiner]
US 20160075443A1 · Schmutz · 2016 [cited by examiner]
US 20160176538A1 · Bekanich · 2016 [cited by applicant]
US 20170063944A1 · Nyikos · 2017 [cited by examiner]
US 20170259942A1 · Ziarno · 2017 [cited by examiner]
US 20180044034A1 · Newman · 2018 [cited by examiner]
International Search Report and Written Opinion for International Application No. PCT/US2019/055665 dated Jan. 14, 2020, 12 pages. [cited by applicant]
Communication pursuant to Article 94(3) EPC dated Jul. 5, 2023 (Jul. 5, 2023), 9 pages, issued on related European patent application 19797881.0 by the European Patent Office. [cited by applicant]