Fuel accounting system and methods
First Claim
1. A method for managing aircraft fuel, the method comprising the steps of:
- a) receiving a first fuel amount data for a fueling event from an Aircraft Communications Addressing and Reporting System (ACARS) located on an aircraft, the first fuel amount data representing one fueling event of a plurality of fueling events that have occurred over a selected period of time, each fueling event representing a fueling of a select aircraft of a plurality of aircrafts by a fueling agent;
b) receiving a second fuel amount data derived from the fueling agent for the fueling event, the second fuel amount data comprising data originating from a fuel dispenser vehicle used to fuel the select aircraft;
c) comparing the first fuel amount data and the second fuel amount data, by at least one computer processor, to determine whether one or more corresponding pieces of information from the first fuel amount data and the second fuel amount data match; and
d) releasing the first fuel amount data for reconciliation with the fueling agent when the one or more corresponding pieces of information match.
1 Assignment
0 Petitions
Accused Products
Abstract
Various embodiments of the present invention provide systems and methods for fuel accounting that enables an organization to verify that fueling being paid for has in fact been dispensed into their aircraft. In particular, various embodiments provide systems and methods to verify whether a particular fueling event occurred. In addition, various embodiments provide systems and methods to facilitate the front-end data capture of a fueling event by the organization operating the aircraft via a data pathway not under control of a fueling agent. Furthermore, various embodiments provide for systems and methods to allow an organization operating aircraft to verify fuel uplifted and fuel inventory over a selected period of time.
33 Citations
12 Claims
-
1. A method for managing aircraft fuel, the method comprising the steps of:
-
a) receiving a first fuel amount data for a fueling event from an Aircraft Communications Addressing and Reporting System (ACARS) located on an aircraft, the first fuel amount data representing one fueling event of a plurality of fueling events that have occurred over a selected period of time, each fueling event representing a fueling of a select aircraft of a plurality of aircrafts by a fueling agent; b) receiving a second fuel amount data derived from the fueling agent for the fueling event, the second fuel amount data comprising data originating from a fuel dispenser vehicle used to fuel the select aircraft; c) comparing the first fuel amount data and the second fuel amount data, by at least one computer processor, to determine whether one or more corresponding pieces of information from the first fuel amount data and the second fuel amount data match; and d) releasing the first fuel amount data for reconciliation with the fueling agent when the one or more corresponding pieces of information match. - View Dependent Claims (2, 3, 4, 5, 6)
-
-
7. A system for managing aircraft fuel, the system comprising:
at least one computer processor configured to; a) receive a first fuel amount data directly from an Aircraft Communications Addressing and Reporting System (ACARS) located on an aircraft, the first fuel amount data representing one fueling event of a plurality of fueling events that have occurred over a selected period of time, each fueling event representing a fueling of a select aircraft of a plurality of aircrafts by a fueling agent; b) receive a second fuel amount data derived from the fueling agent for the fueling event, the second fuel amount data originating from a fuel dispenser vehicle used to fuel the select aircraft; c) compare the first fuel amount data and the second fuel amount data to determine whether one or more corresponding pieces of information from the first fuel amount data and the second fuel amount data match; and d) release the first fuel amount data for reconciliation with the fueling agent when the one or more corresponding pieces of information match. - View Dependent Claims (8, 9, 10, 11, 12)
Specification