A method of generating landing data
Patent Information
- Application Number
- EP2024812571
- Authority / Receiving Office
- EP · EP
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-11-03
- Filing Date
- 2024-11-04
- Publication Date
- 2026-09-09
AI Technical Summary
Existing methods for managing landing, take-off, and parking fees at aerodromes are labor-intensive, prone to human error, and often require significant investment in hardware, making them costly and inefficient, especially for small or unstaffed airfields.
A method utilizing GPS data and unique airfield and aircraft codes to automatically generate landing logs and trigger payment processes, eliminating the need for manual intervention and reducing the costs associated with hardware installation.
This solution enables fast, accurate, and automated collection of aerodrome service fees, reduces the risk of missed payments, and allows unstaffed or closed aerodromes to remain operational without the need for additional staff or hardware investments.
Smart Images

Figure IB2024060872_08052025_PF_FP_ABST
Abstract
Description
[0001]A Method of Generating Landing Data Field The invention relates to a method of generating landing data and more particularly, but not exclusively, to a method of automatic administration of aerodromes, landing fields helipads and heliports in particular unstaffed or closed aerodromes. The method may also be applied to mobilise and administer unstaffed or closed aerodromes. Background Currently billing, collecting and paying landing, take-off, and parking fees involves various methods. Firstly, voice recognition through transcribing recordings of radio transmissions from aircraft which are operating at the airport and photographing the ID tail numbers. Secondly, radio frequency identity (RFID) tags and transponders installed at airfields and photographing the aircraft. Finally, with traditional systems at small aerodromes, a pilot parks, visits an office and pays cash. This could distract an air traffic controller from his / her key role. Personnel are therefore required to manage and oversee these transactions and to process incoming information. Disadvantages of other methods include they can be slow and labour intensive. Also, considerable time could elapse between landing dates and invoice dates. Human error can cause losses and disputes. Existing systems involve aerodrome investment in hardware, such as cameras, transponders. Hardware is prone to faults and failures or may be weather sensitive. Often installation of such systems is too costly for small airfields and impossible for private airstrips. Consequently, many aerodromes have to close and are unable to re-open and monetise their assets. Prior Art United states patent application number US 2022 / 0068145 (Cummings) discloses a system, device and method for collecting, processing, correcting and employing positional vehicle data transmitted by an aircraft to improve airport and related vehicle operations and tracking. United states patent application number US 2004 / 0243302 (Barry) discloses a system, which receives data from an input feed. The data corresponds to one of operations data and revenue data of an airport facility. United states patent application number US 2003 / 0200138 (Smith) discloses a system and method for automatically generating landing fees and other airport service billing data. The system automatically detects aircraft N-numbers from air traffic control voice data. The system automatically bills aircraft owners for landing fees based upon this data. United states patent application number US 2007 / 0120729 (Barry) discloses a system for receiving data for a plurality of aircraft landings at an airport. United states patent number US 6859694 (Andrews et al) discloses a system and method for filing and closing of flight plans. The invention arose to overcome these problems. Summary of the Invention According to a first aspect there is provided a method of generating landing data with respect to an aircraft for an airfield operator comprising: a) selecting a destination airfield by the aircraft and generating or receiving two codes with respect to, and being unique to the airfield, and aircraft / aircraft type; b) reading aircraft flight data at intervals, the aircraft flight data including GPS data; c) determining from the aircraft data, the landing status of the aircraft at the airfield by comparing the aircraft flight data with pre-set criteria and determining if the data meet the pre- set criteria; d) from step c) determining confirmation whether the aircraft has landed, and if so, e) generating a landing log data. Optionally the step of sending or storing a message from the aircraft is indicative of intent to land at the airfield. Ideally the step of sending a message from the aircraft may indicate aircraft identification and / or aircraft type. Preferably the method of receiving or generating airfield data and / or access codes, where the airfield data optionally includes the pre-set criteria pertaining to destination airfield. At least a portion of the pre-set criteria is determined by aircraft type and / or the destination airfield. Ideally aircraft flight data includes one or both of aircraft speed and / or height. In some embodiments, step c) comprises comparing the aircraft flight data with at least one of a plurality of pre-set criteria and / or thresholds; and determining if the aircraft meets the, or each, pre-set criteria and / or threshold(s). In some embodiments, step c) includes determining if the aircraft is within a preset range of one or more pre-set locations. Optionally pre-set locations are pre-determined GPS locations and / or pre-set distances / locations from or along the runway of the airfield. In addition to step c) a comparison of the aircraft speed and / or height at one or more of each of the pre-set locations may be carried out. The speed and height thresholds are specific or may vary for at least two preset locations. Pre-set locations are computed and / or stored consequent to step a), and or generated consequent to generation of the computed codes. Preferable the method includes the step of determining whether at one or more of the pre-set locations the aircraft is above or below its stalling speed. In some embodiments the step consequent to determining if the aircraft at one or more of the pre-set locations is below stalling speed, is determined in step d) when the aircraft has landed. Step d) or e) may be performed only if all of the pre-set criteria are fulfilled. Landing log data may include one or more of: flight plan / log, aerodrome log, and aerodrome runway statistics, and other aerodrome services, touch down time, flight time, billing data, aircraft identification data. A message may be sent to a remote server or is generated or received from a remote server when the landing log data is generated or sent to a remote server. A device may be adapted to perform any of the method steps. The device may be a mobile, portable, or handheld device. It is appreciated that any of the method steps may be embedded in downloadable application specific software (APP). A special airborne APP recognises a correlation of GPS beacon locations and proprietary system-codes that trigger the debit of an aircraft owner’s account and credit the airfield owner / operator’s account. The present invention has been made in order to mobilise unstaffed aerodromes by auto- triggering prior permission requests (PPRs) to land that contain clauses to indemnify aerodrome owners from possible pilots’ claims. The invention facilitates re-opening of closed aerodromes or extends the hours available of staffed aerodromes to visiting aircraft to provide fast and accurate collection of aerodrome service fees and administrative procedures. In a preferred embodiment of the invention, the APP reads a plurality of GPS data, such as coordinates at five strategic points which are not a simple geo-fence (cross a line) concept but on an approach and runway threshold and along the runway where aircraft unavoidably have to pass one another to land and codes are read as follows: GPS beacon position that identifies an airfield by its code; GPS beacon position that shows intent to land; GPS beacon position located at a beginning of runway; GPS beacon position 120 which is along a centre line of a runway (committed to land); and GPS beacon position 240 yards long runway to read a final code for the system. In a preferred embodiment touch down is established as an aircraft reaches stalling speed, whereby it ceases to fly. This sequence creates five “YES” status signals in the pilot’s APP. The software detects the five “YES” outputs and trigger automatically. These are: 1) automatic payment of landing fees and service charges to airport owner; 2) automatic billing for the airport and bookkeeping entry; 3) a unique database record of the aircraft type and ID which is stored in the APP; 4) a logbook record of the landing for the airport owner; and 5) an accumulation of landings and take-offs for providing a record and statistics for the aerodrome. The system samples GPS coordinates should not be confused with a GPS navigation service nor with the so-called geo-fencing descriptions which are only two dimensional, for example, when a car crosses a GPS line or opens a barrier or gate and pays a parking fee. The invention provides a three dimensional solution with height and speed included as well as analysis of two codes unique to each aerodrome and aircraft type with which the airborne APP instantly correlates the aforementioned data to initiate the above sequence. The invention therefore fulfils a need to develop a cheap and reliable automated solution which substantially reduces the risk of aerodrome fees being missed. Brief Description of the Drawings Figure 1 is an overview of an example of an airfield showing mobile interface APP architecture and the interaction between them; Figure 2 shows how an aircraft unavoidably crosses beacon coordinates and registers with logic gates and when they match an output is sent to an airfield operator and aircraft owner confirming gate positions; Figure 3 shows examples of conditions required to trigger payment; Figure 4 is a flowchart of the method of collecting airfield landing fees and payments using GPS and airfield parameters compared digitally by logic gates, software, triggering collection and payments according to an embodiment of the invention; Figure 4 (continued) shows examples of a computer screen at airport A and a pilots mobile cellular phone screen and a screen of a mobile electronic communication device of an airport supervisor; and Figure 5 is an example of an invoice or ticket printout for accounts or record keeping purposes. Detailed Description of Preferred Embodiments of the Invention This invention relates to the method of obtaining landing permission (PPR) and also charging aircraft owners / operators applicable aerodrome fees that are automatically credited to an airport and triggered by the arrival of an aircraft carrying appropriate APP without any mechanical installations or equipment required by the aerodrome and enabling unstaffed aerodromes to remain open. Referring to Figure 1 shows a diagrammatical hub with a server database 10 connected on- line to all member aerodromes at airfields A, B etc. Data is entered or edited by aerodrome staff or owners. Aircraft 1 is depicted as underway to airfield A. Application specific software (APP) sends a prior permission request (PPR) and alerts airfield A, via the server database 10 of arrival of aircraft 1. Aircraft 1 is committed to landing and passes over a row of pre-programmed GPS beacons and code points, shown in Figure 2. These in turn trigger payments via the server 10 to the airfield operator. It is appreciated that other services and fixed based operator costs, such as fuel and fuel delivery charges, booking services, baggage handling services and passenger transport services, may also be included in a payment schedule. Coordinates and codes are uploaded in the APP when a destination aerodrome is pre-selected by a pilot from a menu on their mobile airborne device, such as a smartphone, during a flight planning stage. This data comprises aerodrome parameters such an elevation altitude above sea level (ASL), runway coordinates with unique codes which are compared during the flight. The aircraft type is also uploaded with weight and stalling speed. To collect payments from an aircraft owner’s account the aircraft arrives over a GPS ID code point and follows a predetermined sequence of unique GPS beacons which are typically located before the beginning of a runway. These continue along a runway centre line until a critical point which matches another code and confirms that the aircraft reached stalling speed from which an inevitable touched down (contact) on the runway is confirmed. Once the software of a visiting aircraft detects a match of the above parameters, five digital gates in the software close the flight plan and PPR and simultaneously trigger the following aerodrome administration chain: debit of fees through an automated payment system, such as Stripe (RTM), followed by automatic billing and debit of fees from the aircraft owner. This credits an account of aerodrome owner. Additionally, the system completes a register with landing time and runway details in a log which is typically accessed from an aerodrome control tower computer display. When completed, if required by local laws, the aerodrome log book sends details to a governing body or authority, which in the UK is the Department of Civil Aviation. Other end user details include digital statistics in the aerodrome owners digital equipment and these may include duration of aircraft flight to maintenance services. The system may also be configured to trigger a timer to record the beginning of parking time that is closed by departure of the aircraft, for example when reaching 500 feet altitude, which in turn triggers another debit of the aircraft owner’s account and issues a receipt. Figure 2 shows how an aircraft unavoidably crosses beacon coordinates and registers with logic gates. When these match an e-gate provides an output depicted as +++++ . This comprises a: 1st gate register airfield code + and an intent to land; a 2nd gate registers a position over a runway threshold; a 3rd gate confirms track along runway; a 4th gate confirms a technical code whereby a plane ceases to fly and a 5th gate confirms landing. Each provides confirmatory signal which is indicated as a ‘+’. The five +++++ signals together trigger a ‘to pay landing’ request and ramp fees, as well as causing other time, date and location data to be logged for an airfield operator and aircraft owner. Similarly, if the aircraft stalls at beacon 4 then the system detects this and the beacon at the 5thgate is automatically configured to output a ‘+’ and so all gate registers would still indicate a ‘LANDED’ status and output five ‘YES’ results. All transactions are also recorded in the aerodromes bookkeeping software, such as SAGE (RTM). All landings and runways used are recorded in an data file and may be automatically converted to record and analyse statistics of landings, aircraft types, mission, runways used, length of stay and fuel purchased. As mentioned above the software may be configured to account for and manage billing for other services and fixed base operator costs, such as fuel, booking services, baggage handling and passenger transport services. The name aerodrome embodies; small airports, airfields, airstrips, non-towered airports, private and farm airstrips. Aerodrome operators / owners are thus able to download the aerodrome administrative platform onto control tower computers, or mobile devices such as cellular phones and tablets which also allow the aerodrome to be monitored remotely. In one embodiment passwords to access and use the system may be downloaded directly from a bespoke platform or website. Alternatively, these may be sent to a user’s mobile device in a short message service (SMS) as a PIN code or password to enable access to a secure online website or web-based system managed by a local operator, credit agency or airport authority Aerodrome data can be entered by an airfield operators or owners and from pilots’ interface devices, for example via a mobile electronic communication device, such as a smartphone. A preferred embodiment of the pilot APP shows all aerodromes that are participating in the system. On selection of a destination aerodrome pre-authorization parameters and codes are uploaded from a background server onto the mobile device and a PPR is sent. The pilot takes off from the start airfield. On reaching 500 feet, the APP triggers an SMS to the destination airfield showing aircraft class, ID, and estimated time of arrival (ETA) to confirm a PPR sent earlier. The system verifies an aerodrome ID and completes landing to trigger payment of fees. After landing, the system sends multiple digital data and documentation including bills, accounts, logs, statistics to all parties. Thus, the invention useful to general aviation and make unused or private airfields, and non-towered airports gain income. Referring to Figure 3, there is shown conditions required to trigger payment. The table shows the five conditions required to recognise a “Landed” status and trigger payment. Not fulfilling any one of the conditions results in a “not-landed” status and a non-billing event. However, on landing, the logic of the digital gates is that it avoids false billing through: a) aircraft enroute passing overhead along the runway by coincidence; b) aircraft aborting a landing approach (overshoot); and c) a full stop is not required as a runway is required to be vacated immediately. This invention also allows private airstrips to enter the general aviation sector increasing both business and recreational destinations and possible extra emergency landing places. Figure 4 shows an example of a flowchart of the method of collecting airfield landing fees and payments using GPS and airfield parameters compared digitally by logic gates, software, triggering collection and payments according to an embodiment of the invention. Figure 4 (continued) shows examples of a computer screen at airport A and a pilots mobile cellular phone screen and a screen of a mobile electronic communication device of an airport supervisor. Advantages of the invention include for operators and aircraft operators: 1. An automated business system for land and water aerodromes, airports, heliports, ‘verti ports’ and helipads. 2. Carries out multi-tasking through rapidity custom created program software to send PPRs and later confirm and identify a landing. 3. Administer airfields of all types including non-towered airports to bill and collect landing, parking and passenger fees. 4. No staff is required but still enables billing and debiting of aerodrome fees from an aircraft operator account and crediting the same to the aerodrome owner’s account. 5. Eliminates missed landing fees from after-hours landings when a staffed control tower is closed, thus increasing revenue and customer convenience. 6. Adds a new asset to airfields that are unstaffed without any investment costs in hardware, external structures, or extra personnel. 7. Smaller aerodromes can be monitored remotely by owners who can open / close and edit remotely on their mobile devices. 8. Increases safety and efficiency by eliminating the need for air traffic personnel at staffed aerodromes to be distracted from their main duty by acting as cashiers. 9. A digital air traffic logbook is created for each aerodrome with statistics and accounts and can be supplied to any authorities if needed. 10. Enables aerodromes available to general aviation due to the possibility of remote operation of small, unmanned airfields and private airstrips such as farm airstrips and possible emergency landing strips. The invention has been described by way of example only and it will be appreciated that variation may be made to ethe embodiments described without departing from the scope of protection as defined by the claims. Figure 5 is an example of an invoice or ticket printout for accounts or record keeping purposes. For example, variation may be to the invention by applying the method to monitor size (footprint) and tonnage of, and manage, shipping and docking and administer unstaffed or closed docks and berths in order to secure payment of mooring or berthing fees in a similar manner to securing payment of landing fees.
Claims
Claims 1. A method of generating landing data with respect to an aircraft for an airfield operator comprising: a) selecting a destination airfield by the aircraft and generating or receiving two codes with respect to, and being unique to the airfield, and aircraft / aircraft type; b) reading aircraft flight data at intervals, the aircraft flight data including GPS data; c) determining from the aircraft data, the landing status of the aircraft at the airfield by comparing the aircraft flight data with pre-set criteria and determining if the data meet the pre- set criteria; d) from step c) determining confirmation whether the aircraft has landed, and if so, e) generating a landing log data.
2. A method according to claim 1 including the step of sending or storing a message from the aircraft indicative of intent to land at the airfield.
3. A method according to claims 1 or 2 including the step of sending a message from the aircraft indicative of aircraft identification or aircraft type.
4. A method of receiving or generating airfield data and / or access codes, wherein the airfield data optionally includes the pre-set criteria pertaining to destination airfield.
5. A method according to any of claims 1 to 4 where at least a portion of the pre-set criteria is determined by aircraft type and / or the destination airfield.
6. A method according to any of claims 1 to 5 wherein the aircraft flight data includes one or both of aircraft speed and / or height.
7. A method according to any of claims 1 to 6 wherein step c) comprises comparing the aircraft flight data with a plurality of pre-set criteria and / or thresholds; and determining if the aircraft meet the pre-set criteria and / or thresholds.
8. A method according to claim 7 wherein step c) includes determining if the aircraft is within a preset range of one or more pre-set locations.
9. A method according to claim 8 wherein the pre-set locations are pre-determined GPS locations and / or pre-set distances / locations from or along the runway of the airfield.
10. A method according to claim 9 additionally including in step c) comparing the aircraft speed and / or height at one or more of each of the pre-set locations.
11. A method according to claim 10 wherein the speed and height thresholds are specific or vary for at least two preset locations.
12. A method according to any of claims 8 to 11 wherein the pre-set locations are computed and / or stored consequent to step a), and or generated consequent to generation of the computed codes.
13. A method according to any of claims 8 to 12 including the step of determining whether at one or more of the pre-set locations the aircraft is above or below its stalling speed.
14. A method according to claim 13 including the step of consequent to determining if the aircraft at one or more of the pre-set locations is below stalling speed, determining in step d) that the aircraft has landed.
15. A method according to any of claims 1 to 14 wherein step d) or e) is only performed if all of the pre-set criteria are fulfilled.
16. A method according to any of claims 1 to 15 wherein the landing log data comprises one or more of: flight plan / log, aerodrome log, and aerodrome runway statistics, and other aerodrome services, touch down time, flight time, billing data, aircraft identification data.
17. A method according to either claim 2 or 3 wherein the message is sent to a remote server, or as claimed in either claim 4 or 5 wherein the data is generated or received from a remote server or according to any preceding claim wherein the landing log data is generated or sent to a remote server.
18. A device adapted to perform any of the method steps of claims 1 to 17.
19. A device according to claim 18 which is a mobile, portable or handheld device.
20. A device according to claim 19 wherein any of the method steps of claims 1 to 17 are embedded in a downloadable application.