EP3007152B1

EP3007152B1 - System and method to determine OOOI times of an aircraft

Info

Publication number: EP3007152B1
Application number: EP14187838.9A
Authority: EP
Inventors: Ahmet Turan Balkan; Fuad Hamidov
Original assignee: Tav Bilisim Hizmetleri AS
Current assignee: Tav Bilisim Hizmetleri AS
Priority date: 2014-10-06
Filing date: 2014-10-06
Publication date: 2019-04-24
Anticipated expiration: 2034-10-06
Also published as: EP3007152A1

Description

Field of the invention

The invention relates to a system to determine the times of an aircraft to touch the runway, to park at a parking position, to leave a parking position and to take off from the runway.

Background of the invention

Transponders are usually used to identify aircrafts in air traffic control radar and are usually used to avoid collisions between aircrafts. The Secondary Surveillance Radar (SSR) depends on an embedded transponder which replies to interrogations of the secondary radar. The interrogation mode of a transponder is the format of a sequence of pulses, referred to as a code used to determine detailed information from the aircraft. There are different types of interrogation modes: Modes 1 to 5 are reserved for military use whereas Modes A, B, C, D and S are dedicated to civilian use.
Modes A and C are developed for airframe identification and altitude reporting and this is still widely used in air traffic control and management of air space. However, with the increase of air traffic, the Air Traffic Control Radar Beacon System (ATCRBS) has nearly become saturated. There are also problems of False Replies Uncorrelated In Time (FRUIT) due to the technology used by modes A and C.
Mode S technology was developed in the seventies and was widely deployed in the eighties. The advantages of Mode S technology over Mode A and C is that it is addressable, more accurate and reliable and that it can operate with greater capacity. A transponder which receives a valid Mode S discrete interrogation replies 128 µs after reception. The reply is transmitted on 1090 MHz carrier with 56 bit or 112 bit Pulse Positioning Modulation (PPM). Mode-S uses a monopulse SSR, as in Modes A and C, but it has an increased accuracy. Each Mode S interrogation includes an International Civil Aeronautics Organization (ICAO) 24-bit aircraft address, which corresponds to the registration number of the aircraft as a 24-bit parity check for validation. In basic Mode S surveillance, the information is limited to altitude reporting, basic airframe information and aircraft identification.
More and more aircraft are using today the Automatic Dependent Surveillance-Broadcast (ADS-B). Since radars have a limited precision on the position of aircrafts, the idea behind ADS-B is to use the Global Navigation Satellite Systems (GNSS) to measure the position of the airframe and to transmit this position by radio in the Mode S message. Aircraft equipped with Mode S, are able to send and receive 56 bits messages. The 1090ES (Extended Squitter) is an extension of the Mode S radar transponders which emit at 1090 MHz. This modification allows to send 112 bits messages which include the position of the aircraft calculated by the GNSS system and eventually to receive them. On the ground, these ADS-B information can be received either by a SSR or by a simple omnidirectional antenna much cheaper. The mode (A, C or S) of the reply is then decoded and the information is demodulated within each mode. Since most of commercial aircrafts are already equipped with transponders, the 1090ES is a very cheap solution for these aircrafts.
ASDE-X uses data which come different types of radars, sensors and transponders. The merging of all these data allows the ASDE-X to determine the position of aircraft and to identify aircraft and vehicles on the airport surfaces, as well as determine aircraft approaching the airport.
Aircraft travel times and delays often need to be accurately evaluated for a variety of reasons. One of the reasons is to evaluate performance of an air carrier, required by Eurocontrol, the FAA etc. The data used to evaluate the performance include "OOOI" data which corresponds to the operations of an aircraft: Out of the stand, Off the ground, On the ground, and Into the stand. This data along with airline schedules allow for the calculation of route times, stand arrival time delay, stand delay, taxi times etc. for every flight. Another reason is to improve ground operations such as baggage handling, refuelling of air carriers. Late arriving flights may also imply a new stand assignment which drastically complicates the organization of ground operations. Planning and staffing of airlines are however planned according to scheduled times and it is therefore important to have realistic Scheduled Times of Departure (STD) and Scheduled Times of Arrival (STA). Realistic STD and STA are also important for passengers in order to meet their expectations.
The article by B. S. Levy et al. entitled "Objective and Automatic Estimation of Excess Taxi-Times" (Integrated Comunications, Navigaiton and Surveillance Conference, 2008, ICNS 2008, IEEE, Piscataway, NJ, USA, 5 May 2008, pages 1 to 10, XP031283424, ISBN: 978-1-4244-2303-3) discloses a methodology for the determination of taxi-times using Airport Surface Detection Equipment - Model X (ASDE-X) for the determination of fuel burn during excess taxi-times, that is, between an 'on' event (landing) and an 'in' event', and between an 'out' event and an 'off' event (take-off) including any holding between the designated end positions. Sensor data from different sources is used in the determination.
OOOI times are significant because these times are used as the basis of predictions and in calculation of delays. For these and other reasons it is important that OOOI data have sufficient completeness and accuracy.
ACARS, Aircraft Communications Addressing and Reporting System, is a digital datalink system for the transmission of messages between an aircraft and a ground station. These messages can be transmitted by satellite or by radio. The main function of ACARS is related to the detection of the major flight phases of an aircraft, the OOOI operations. For planes equipped with ACARS systems, OOOI operations are automatically detected using sensors. 'Wheels "out" of the stand' corresponds to the time an aircraft pushes back from the stand and is measured when the parking brake is released, with the associated change in brake pressure. It corresponds to the Actual Time of Departure (ATD). 'Wheels "off" the runway' corresponds to the time an aircraft takes-off. 'Wheels "on" the runway' corresponds to the actual time an aircraft lands on the runway. Finally, 'wheels "in"' corresponds to the actual time an aircraft arrives at the stand or in the parking position. It also corresponds to the Actual Time of Arrival (ATA).
However, not all aircraft use the ACARS system. One of the reasons for this is cost. Another reporting option is to use a Docking Guidance System (DGS). DGS employs a technology based on lasers to help pilots to park the aircraft at the stand and the flight crew or the ground personnel transmits the departure and arrival times by radio, electronic or even by written communications.
When OOOI times are not available they are estimated according to FAA guidelines for US.
It is therefore an object of the present invention to provide a reliable and simple method to measure OOOI times.

Summary of the invention

In accordance with one aspect of the present invention, there is provided a method of determining an in-time of an aircraft using aircraft transponder data as defined in claim 1.
The use of the transponder data allows a simple method to accurately determine the in-time of an aircraft. No additional hardware is necessary for the implementation of the proposed method.
In an embodiment of the present invention, the transponder data from the aircraft further includes flight data including data indicating if the flight is an arrival flight or a departure flight, and the method of determining the in-time further comprises the step of verifying if said flight is an arrival flight, and determining the actual processing time as the in-time of the aircraft if the flight is also an arrival flight.
This allows a gain in computational time, since only the data indicating an arrival flight is processed to determine the in-time of the aircraft.
Advantageously, the transponder data is a Mode S message.
A Mode S message comprises the registration number of the aircraft and preferably its position from the GNSS system. The combination of the mode-S message data and a database allows an accurate computation of the OOOI times of the aircraft.
Preferably, the method further comprises the step of comparing said parsed transponder data with data available in a flight data database, and adding data from the flight data database to said parsed transponder data to create more complete flight data.
Advantageously, the method further comprises the step of verifying if the aircraft is on a runway, and determining the actual processing time as the in-time of the aircraft if the aircraft is also not on the runway.
In another embodiment of the present invention, the method further comprises determining an on-time of an aircraft prior to determining said in-time thereof.
In an embodiment of the present invention, said parking coordinates are stand coordinates or parking spot coordinates.
It is an object of the present invention to provide a system to determine an in-time of an aircraft as defined in claim 8..
This method allows the determination of the on-time of an aircraft without the need of new special hardware. Only data available in a database and the transponder data are necessary for determining the on-time.
In an embodiment of the present invention, the method further comprises the step of verifying if a previous on-time is available for said aircraft and determining an actual processing time as the on-time of the aircraft if there is also no on-time available for said aircraft.
The on-time is only valid if no previous on-time has been previously calculated.
It is an object of the present invention to also provide a system to determine an on-time of an aircraft prior to determining said in-time thereof.
It is an object of the present invention to provide a method to determine an out-time of an aircraft as defined in claim 10.
This method allows the determination of the out-time of an aircraft without the need of new special hardware. Only data available in a database and the transponder data are necessary for determining the out-time.
It is an object of the present invention to provide a method to determine an off-time of an aircraft as defined in claim 13.
This method allows the determination of the off-time of an aircraft without the need of new special hardware. Only data available in a database and the transponder data are necessary for determining the off-time.
It is an object of the present invention to provide a system to determine an out-time of an aircraft as defined in claim 12.
It is an object of the present invention to provide a system to determine an off-time of an aircraft after said out-time thereof.
Advantageously, the on-time, the in-time, the out-time and the off-time described above are used to determine the OOOI time of an aircraft as defined in claim 14.
The method allows a simple and accurate way of determining OOOI times of an aircraft. Also, there is no need to provide new hardware in the aircraft for this accurate computation. This is performed using the already existing hardware on board of the aircraft.
A system for determining said on-, in-, out- and off-times of an aircraft at an airport is defined in claim 15.

Brief description of the drawings

For a better understanding of the present invention, reference will now be made, by way of example, to the accompanying drawings in which:

Figure 1 shows a flowchart of a system and method to determine the OOOI times.
Figure 2 shows a flowchart of steps in a system or method to determine the in-time and out-time of an aircraft.
Figure 3 shows a further flowchart of steps in a system or method to determine the in-time and out-time of an aircraft.
Figure 4 shows a flowchart of steps in a system or method to determine the on-time of an aircraft.
Figure 5 shows a flowchart of steps in a system or method to determine the off-time of an aircraft.

Description of the invention

The present invention will be described with respect to particular embodiments and with reference to certain drawings but the invention is not limited thereto. The drawings described are only schematic and are non-limiting. In the drawings, the size of some of the elements may be exaggerated and not drawn on scale for illustrative purposes.
Furthermore, the terms first, second, third and the like in the description and in the claims, are used for distinguishing between similar elements and not necessarily for describing a sequential or chronological order. The terms are interchangeable under appropriate circumstances and the embodiments of the invention can operate in other sequences than described or illustrated herein.
Furthermore, the various embodiments, although referred to as "preferred" are to be construed as exemplary manners in which the invention may be implemented rather than as limiting the scope of the invention.
The term "comprising", used in the claims, should not be interpreted as being restricted to the elements or steps listed thereafter; it does not exclude other elements or steps. It needs to be interpreted as specifying the presence of the stated features, integers, steps or components as referred to, but does not preclude the presence or addition of one or more other features, integers, steps or components, or groups thereof. Thus, the scope of the expression "a device comprising A and B" should not be limited to devices consisting only of components A and B, rather with respect to the present invention, the only enumerated components of the device are A and B, and further the claim should be interpreted as including equivalents of those components.
A simple, robust and accurate method to calculate OOOI times is described wherein OOOI time calculation refers to Out of the stand, Off the ground, On the ground and Into the stand. The stand is the parking position. It is for example the stand or a parking spot allocated to the aircraft. Therefore, in this description, we refer to this position as the stand position.
The Runway Thresholds are markings across the runway which define the beginning and the end of the space intended for landing and take-off.
The Mode S transponder messages include the coordinates of the plane calculated by a Global Navigation Satellite System such as the GPS. The aircraft are equipped with ADS-B and the Mode S messages include the coordinates of the aircraft.
The AODB (Airport Operation DataBase) is a resilient, comprehensive central repository for operational data management activities. It delivers the efficiency of centralized operational database of an airport along with guaranteed, consistent and robust operational performance. The AODB stores, distributes and manages all real-time flight data, in addition to all aeronautical and non-aeronautical service data, and it quickly transforms this data into accurate financial figures. The AODB is a multi-tiered application. Interaction between the user interface and service layers, which is designed by utilizing Service Oriented Architecture (SOA), is event-based. The AODB user interface is designed as a RIA, (Rich Internet Application) it takes advantage of cross browser and platform compatibility in addition to taking advantage of the web deployment model's traditional benefits. The AODB is configurable depending on the operation and size of the airport. The AODB is equally well suited for small, medium-sized or large airports. According to the needs of the customer, it can be downsized or dedicated "cost effective" solutions can be tailored. The AODB further includes an interface capable of receiving Mode S messages and interpreting them.
The definition of "in-time" used in this application is the time that the aircraft arrives in its parking position. The parking position can be a stand position or a parking spot allocated to the aircraft. It should be understood that throughout the application, where stand or parking spot is used, the one can be replaced by the other.
The definition of "out-time" used in this application is the time that the aircraft leaves its parking position.
The definition of "off-time" used in this application is the time that the aircraft is no longer in contact with the runway.
The definition of "on-time" used in this application is the time that the aircraft is touching the runway.
Referring to Figure 1, Figure 1 illustrates a flow chart of a system that is used to determine OOOI times based on transponder Mode S messages. The method is executed for every Mode S message received. Usually, the transponder of an aircraft sends a Mode S message every few seconds. Preferably, the time interval between two consecutive Mode S messages of an aircraft is lower than 5 seconds.
The transponder of the aircraft replies to signals from a Secondary Surveillance Radar 100 by transmitting the Mode S message 102. This Mode S message includes the aircraft identification number, the pressure altitude, the GPS position and the speed of the aircraft. The signal corresponding to the Mode S message is sent to an SBS receiver (antenna) 104 which decodes the transponder signal from the aircraft, demodulates it and converts the analog signal to a digital message 106. The SBS receiver then sends this digital message to an application, part of a control system, responsible of reading, parsing and processing the digital data 108. In this control system, another application is responsible for listening to specific ports which receive the converted digital messages. The messages are received byte by byte and the application is able to distinguish each message and its corresponding source. The digital signal corresponding to the analog Mode S message is analysed. The corresponding data is inserted into a predefined flight data structure which comprises the following data fields:

registration number of the aircraft,
flight ID,
coordinates of the aircraft at time t
pressure altitude at time t
scheduled time of departure (STD)
scheduled time of arrival (STA)
actual time of departure (ATD)
actual time of arrival (ATA)
actual time of in-block (AIBT)
actual time of off-block (AOBT)
for a given airport if the flight is an arrival flight or a departure flight
aircraft speed
OOOI times
call sign (alternative alphanumeric flight number)
...

This flight data structure is updated and completed during the process, some fields can be empty.
In step 110, this flight data structure is subsequently compared to the data already available in the AODB 114 from different integrated sources. To find the flight in the AODB, the system can use different search criteria as the flight date and time, the airline and the flight ID, the registration number of the aircraft, the call-sign, etc.
If the current flight is not yet comprised in the database (arrow 111 in flow chart), the new flight data is, in step 113, added to the database 114. Additional flight data can be added to the AODB 114 from other sources of information such as AFTN, airline-ground handling systems, slot.
If the current flight is in the AODB 112, then the method continues with step 115. The flight data structure is checked and updated if necessary depending on the Mode S transponder message data. The most important data being the identification number because it allows identification of the aircraft.
Step 130 consists in checking whether the aircraft is already on the runway. This step is performed with a comparison of its coordinates, available in the flight data structure, to the runway coordinates. If the aircraft is not on the runway (arrow 131), the next step 132 consists in determining if the aircraft is in the stand position and if its speed has recently changed. A negative reply 133 leads to perform the "Log message" step 134, which consists in saving an appropriate message, to be used later on. In case of a positive reply 135, the method verifies at step 136 if the flight is an arrival flight. If it is (arrow 137), the system performs the "in" time determination method 200.
If it is not an arrival flight (arrow 138), the system performs the "out" time determination method 300. The sequence of operations used to determine these "in" and "out" times are described in more detail later in this description.
However, if, at step 130, the outcome is that the aircraft is on the runway (arrow 141), it means the aircraft is about to take off or that it has just landed. Therefore, step 142 checks if the current flight is an arrival flight. In case of a positive reply 143, the system performs the "on" time determination method 400. In case of a negative reply 144, the system performs the "off" time determination method 500. The sequence of operations used to determine these "on" and "off" times are described in more detail later in this description.
When these four outcomes 200, 300, 400 and 500 have all been determined, the data is collected at step 600 and the OOOI times 700 of the aircraft are available for further use.
Referring now to Figure 2, Figure 2 illustrates the method to determine the "in" time 200. The method includes the following steps and starts after step 136 of Figure 1. All the data of the aircraft are available in the flight data structure. Step 220 consists in getting aircraft coordinates and checking whether the speed is close to zero. Theoretically, the speed should be zero. However, sometimes transponders may send incorrect speed values. These incorrect values are found by comparing the speed values of the previous and the next messages. Each airport has its own regulation regarding the speed limit for which a plane is assumed to be in its parking position. Usually, this speed limit value is around 3 knots.
If it is not the case, the system logs the available data in step 225 for further use. If the speed is close to zero, the method compares the aircraft coordinates to the stand coordinates in step 230. If the coordinates do not lie in a range corresponding to the stand coordinates, the method stops and performs logs the data in step 235 for further use. While the coordinates lie in the range of the stand coordinates, the next step consists in checking whether a previous "in" time has been saved in step 240. While no previous "in" time is available, the current time corresponds to an actual "in" time and the "in" time is set to the current time. The stand coordinates which correspond to the current GPS coordinates of the aircraft saved in the flight data structure are also set as "stand" coordinates. This is performed in step 245 where the "in" time and the "stand" coordinates are set. However, if a previous "in" time has already been stored, the method verifies if there is a previous "out" time with step 250. While there is no previous "out" time, the method sets the "out" time to the current time with step 255. If a previous "out" time has been saved, the method verifies if the speed of the aircraft was higher than zero in the previous data with the verification step 260. If it is not the case, the plane is about to leave and the "out" time can be updated with step 265. However, if the aircraft was moving in the previous data, it implies that the plane has just arrived in the gate and a new "in" time can be saved. The coordinates of the stand position are also stored from the available GPS data saved in the flight data structure. The "in" time and the stand coordinates are saved in step 270.
Referring to Figure 3, Figure 3 illustrates the flow chart corresponding to the processing of the "out" time. Pilots may turn the transponders off. However, they should be turned on before leaving the stand. Once a transponder is turned on, it starts sending messages. The method actually compares the coordinates of the aircraft with the stand coordinates and checks the speed. If the speed is different from zero and/or the coordinates are different from those of the allocated stand, it means that the aircraft is about to leave the stand. The method includes the following steps and starts after the arrival flight verification 136 step of Figure 1. In this case, the flight is a departure flight. The aircraft coordinates are available and the speed is available from the transponder Mode S message.. The first step consists in checking whether the speed of the aircraft is close to zero with step 320. If it is not, or if the aircraft is moving fast, the data is logged in step 325 for further use. If it is moving slowly, the method verifies whether the aircraft coordinates lie in the range corresponding to the allocated stand. If they do not, the next step is to log the data 335 for further use. If they do, the method checks if the speed in the previous data is higher than zero in step 340. If it is not, the method performs the step of updating the "out" time in step 345. If the plane was previously moving, the method performs the step of adding a new "in" time as well as a new stand coordinate in step 350.
Referring now to Figure 4, Figure 4 illustrates the sequence of events used to determine the "on" time 400. The aircraft coordinates are compared with coordinates corresponding to the runway thresholds coordinates. If the aircraft coordinates (longitude and latitude) lie in this zone and if the altitude corresponds to that of the runway, the current time is stored as an actual "on" time candidate. For validation, the method continues to verify whether or not the next messages support this "on" time candidate. When the below conditions are met, then the time becomes a real "on" time:

the next coordinates of the plane must correspond to the coordinates of a point on the runway and/or the taxiway further away in the moving direction of the plane,
the altitude must correspond to the previous one (small differences are tolerated based on a given threshold),
the plane must be decelerating.

While these 3 conditions are not met, it means that the current flight can be either a training flight, that pilots may train to approach the runway, or it could be any technical problem which has lead the pilot to cancel landing. However, in these scenarios, the data is stored as "on" approach time for further reporting in AODB.
The method includes the following steps and starts after the arrival flight verification step 142. The first condition concerns the altitude of the aircraft and the method verifies if the altitude of the aircraft is close to the altitude of the runway in step 420. If it is not, the method stops by storing the flight data structure in memory and performs the step of logging the data in step 425. If the altitude of the aircraft is close to that of the runway, the method continues with step 430 where the coordinates of the aircraft are compared to the runway thresholds coordinates. While the coordinates of the aircraft do not lie in a range corresponding to the runway thresholds coordinates, the method stops and the flight data structure is logged in step 435. However, if the coordinates lie in that particular range, the method then verifies if there is any other "on" time previously saved 440. If there is no other "time", the current time corresponds to the actual "on" time and the method performs the step of setting the "on" time in step 445. Step 445 also comprises the setting of the thresholds ("Set "on" time & threshold"). If the actual "on" time is not valid, the method needs to verify whether the speed of the aircraft is increasing with the condition 450. If it is not, the method stops and logs the data in step 455. If the speed of the aircraft is increasing, it means that the plane has taken off again and the method stops with the status "Set Touch and Go" 460.
Referring now to Figure 5, Figure 5 illustrates the sequence of operations for determining the "off" time 500. In step 520, the coordinates of the aircraft are compared with the runway thresholds coordinates. If the aircraft coordinates (longitude and latitude) lie in the corresponding range of the runway coordinates, it means that the aircraft is ready for take-off and the system continues to monitor the movements of the aircraft until it passes the take-off zone on the runway and the altitude of the aircraft becomes higher than the altitude of the runway. Once the above condition is met, the time is saved as actual take-off time. The method includes the following steps and starts after the arrival flight verification 142 step. In this case, the flight is a departure flight and the first verification step of the method concerns the comparison of the coordinates of the aircraft with respect to the runway thresholds coordinates (step 520). If the position of the aircraft is not in the zone of the runway thresholds coordinates, the method stops with logging the data in step 525. Otherwise, the method continues with an altitude check in step 530: is the altitude of the aircraft increasing with respect to previous data? A negative reply leads the method to stop and to log data in step 535. However, a positive reply means that the aircraft is taking off. Subsequently, step 540 verifies whether there is a previous "off" time set. With a negative reply, the method can save the actual time as the "off" time in step 545. With a positive reply, the method stops and logs the data in step 550.
In Figures 2, 3, 4 and 5, the sequences of operations for determining the "in" 200, "out" 300, "on" 400 and "off" 500 times have respectively been described.
Referring now to Figure 1, step 600 is dedicated to collect the four times acquired in steps 200, 300, 400, 500. Step 700 accurately calculates the OOOI time of an aircraft from the "in", "out", "on" and "off" times.

Claims

A method of determining an in-time of an aircraft, comprising the steps of:-
a) receiving transponder data from said aircraft, said transponder data including at least coordinate data, altitude data and speed data of said aircraft;

b) parsing said transponder data;

c) verifying if speed data is close to zero;

d) verifying if said aircraft coordinates are close to parking coordinates available in a database;

e) verifying if said speed data of said aircraft is decreasing; and

f) determining an actual processing time as said in-time of the aircraft if said aircraft coordinates are close to said parking coordinates, said speed data is zero, and a previous speed is higher than zero.
A method according to claim 1, wherein said transponder data from said aircraft further includes flight data including data indicating if the flight is an arrival flight or a departure flight, said method further comprising the step of verifying if said flight is an arrival flight, and determining said actual processing time as said in-time of the aircraft if said flight is also an arrival flight.
A method according to claim 1 or 2, wherein said transponder data is a Mode S message.
A method according to any one of the preceding claims, further comprising the step of comparing said parsed transponder data with data available in a flight data database, and adding data from said flight data database to said parsed transponder data to create more complete flight data.
A method according to any one of the preceding claims, wherein said method further comprises the step of verifying if said aircraft is on a runway, and determining said actual processing time as said in-time of said aircraft if said aircraft is also not on the runway.
A method according to any one of the preceding claims, further comprising, prior to step c), the steps of:-
verifying if said aircraft altitude is close to the airport altitude available in said database;

verifying if said aircraft coordinates are close to runway coordinates available in said database; and

determining an actual processing time as said on-time of said aircraft if said aircraft altitude is close to said airport altitude and said aircraft coordinates are close to said runway coordinates.
A method according to claim 6, further comprising the step of verifying if a previous on-time is available for said aircraft and determining said actual processing time as said on-time of the aircraft if there is also no on-time available for said aircraft.
A system configured for determining an in-time of an aircraft, comprising:-
a receiver configured for receiving transponder data from said aircraft, said transponder data including at least coordinate data, altitude data and speed data of said aircraft;

a database configured for storing at least airport altitude data, runway coordinate data and parking coordinate data;

a processor configured for parsing said transponder data, verifying if speed data is close to zero, verifying if said aircraft coordinates are close to parking coordinates available from said database, verifying if said speed data of said aircraft is decreasing, and generating, as said in-time, an actual processing time if said aircraft coordinates are close to said parking coordinates, said speed data is zero, and a previous speed is higher than zero; and

a memory configured for storing said in-time of said aircraft.
A system according to claim 8, wherein said processor is further configured for verifying if said aircraft altitude is close to airport altitude available from said database, verifying if said aircraft coordinates are close to runway coordinates available from said database, and generating as said on-time, an actual processing time if said aircraft altitude is close to said airport altitude and if said aircraft coordinates are close to said runway coordinates; and
said memory is further configured for storing said on-time of said aircraft.
A method of determining an out-time of an aircraft at an airport, comprising the steps of:-
i) receiving transponder data from said aircraft, said transponder data including at least coordinate data and speed data of said aircraft;

ii) parsing said transponder data;

iii) verifying if said aircraft coordinates are close to parking coordinates available in a database;

iv) verifying if said speed data of said aircraft is increasing; and

v) determining an actual processing time as said out-time of said aircraft at said airport if said aircraft coordinates are close to said parking coordinates, speed is increasing, and a previous speed is zero.
A method according to claim 10, further comprising, after step v), the steps of:-
verifying if said aircraft altitude is close to airport altitude available from said database;

verifying if said aircraft coordinates are close to runway coordinates available from said database;

verifying if a previous aircraft altitude is lower than a current aircraft altitude; and

determining an actual processing time as said off-time of said aircraft if said aircraft altitude is close to said airport altitude, said aircraft coordinates are close to said runway coordinates, and if said previous aircraft altitude is lower than said current aircraft altitude.
A system configured for determining an out-time of an aircraft at an airport, comprising:-
a receiver configured for receiving transponder data from an aircraft, said transponder data including at least coordinate data and speed data of said aircraft;

a database configured for storing at least airport altitude data, runway coordinate data and parking coordinate data;

a processor configured for parsing said transponder data,, verifying if said aircraft coordinates are close to parking coordinates available from said database, verifying if said speed data of said aircraft is increasing, and generating, as said out-time, an actual processing time if said aircraft coordinates are close to said parking coordinates, speed is increasing, and a previous speed is zero; and

a memory configured for storing said out-time of said aircraft at said airport.
A system according to claim 12, wherein said processor is further configured for verifying if said aircraft altitude is close to airport altitude available from said database, verifying if said aircraft coordinates are close to runway coordinates available from said database, verifying if a previous aircraft altitude is lower than a current aircraft altitude, and generating, as said off-time, an actual processing time if said aircraft altitude is close to said airport altitude, said aircraft coordinates are close to said runway coordinates, and said previous aircraft altitude is lower than said current aircraft altitude; and
said memory is further configured for storing said off-time of said aircraft at said airport.
A method of determining on-, in- out-, and off- times, OOOI, of an aircraft at an airport, the method comprising the steps of:-
receiving transponder data from said aircract, said transponder data including at least coordinate data, altitude data and speed data of said aircraft;

parsing said transponder data;

verifying if said aircraft altitude is close to the airport altitude available in a database;

verifying if said aircraft coordinates are close to runway coordinates available from said database;

determining an actual processing time as said on-time of said aircraft if said aircraft altitude is close to said airport altitude and said aircraft coordinates are close to said runway coordinates;

verifying if speed data is close to zero;

verifying if said aircraft coordinates are close to parking coordinates available from said database;

verifying if said speed data of said aircraft is decreasing;

determining an actual processing time as said in-time of the aircraft if said aircraft coordinates are close to said parking coordinates, said speed data is zero, and a previous speed is higher than zero;

verifying if said aircraft coordinates are close to parking coordinates available from said database;

verifying if said speed data of said aircraft is increasing;

determining an actual processing time as said out-time of said aircraft if said aircraft coordinates are close to said parking coordinates, speed is increasing, and a previous speed is zero;

verifying if said aircraft altitude is close to airport altitude available from said database;

verifying if said aircraft coordinates are close to runway coordinates available from said database;

verifying if a previous aircraft altitude is lower than a current aircraft altitude; and

determining an actual processing time as said off-time of said aircraft if said aircraft altitude is close to said airport altitude, said aircraft coordinates are close to said runway coordinates, and if said previous aircraft altitude is lower than said current aircraft altitude.
A system configured for determining on-, in- out-, and off- times, OOOI, of an aircraft at an airport, comprising:-
a receiver configured for receiving transponder data from said aircract, said transponder data including at least coordinate data, altitude data and speed data of said aircraft;

a database configured for storing at least airport altitude data, runway coordinate data and parking coordinate data;

a processor configured for:-
parsing said transponder data;

verifying if said aircraft altitude is close to the airport altitude available from said database;

verifying if said aircraft coordinates are close to runway coordinates available from said database;

determining an actual processing time as said on-time of said aircraft if said aircraft altitude is close to said airport altitude and said aircraft coordinates are close to said runway coordinates;

verifying if speed data is close to zero;

verifying if said aircraft coordinates are close to parking coordinates available from said database;

verifying if said speed data of said aircraft is decreasing;

determining an actual processing time as said in-time of the aircraft if said aircraft coordinates are close to said parking coordinates, said speed data is zero, and a previous speed is higher than zero;

verifying if said aircraft coordinates are close to parking coordinates available from said database;

verifying if said speed data of said aircraft is increasing;

determining an actual processing time as said out-time of said aircraft if said aircraft coordinates are close to said parking coordinates, speed is increasing, and a previous speed is zero;

verifying if said aircraft altitude is close to airport altitude available from said database;

verifying if said aircraft coordinates are close to runway coordinates available from said database;

verifying if a previous aircraft altitude is lower than a current aircraft altitude; and

determining an actual processing time as said off-time of said aircraft if said aircraft altitude is close to said airport altitude, said aircraft coordinates are close to said runway coordinates, and if said previous aircraft altitude is lower than said current aircraft altitude; and

a memory configured for storing said on-, in-, out- and off-times of said aircraft at said airport.