Airport Ground Handling Operations Software: Proving the Turnaround Was Yours to Win

Why a handler's margin is decided in forty-five minutes and settled sixty days later

An aircraft goes on blocks at 14:12, eight minutes late, against a forty minute turnaround. What follows is a chain: chocks, ground power, doors, disembarkation, offload, cleaning, catering, fuelling, boarding, load, doors closed, pushback. Each step has a team, and each team is shared with the turn on the next stand. The tug that should be free at 14:20 is still at the other end because that turn ran long. Nobody has a live picture of which crew is free, which equipment is serviceable and where, or what the knock-on will be at 14:50.

The aircraft goes off blocks eleven minutes late. Two months later the airline's invoice reconciliation arrives claiming the delay was ground handling, coded as such, with a penalty attached. You believe the delay was late catering, which is not your contract, or a late inbound crew, which is not your problem either. Your evidence is a ramp lead's memory and a paper turnaround sheet that may or may not have been filled in during the turn rather than after it.

INFORM GroundStar, Ink Aviation and TAV Technologies all serve this market and are used by real handlers. The limit operators hit is the gap between a resource allocation engine and the specifics of a station: your licence scope here differs from the next airport, your collective agreement governs break timing and task assignment, your equipment pool is partly shared, and the timestamps that decide your money come from three parties who record them differently.

The commercial reality is that you are paid per turn against agreed rates and penalised against agreed service levels, so your margin is the difference between what you did and what you can prove you did. Most handlers are much better at the first than the second.

Problem 1: the schedule moves all day and the roster was published last week

The roster is built against a flight schedule. By ten in the morning that schedule is fiction: a delayed inbound, a diversion, an extra section, a stand change that adds four minutes of walking. The roster does not move with it, so allocation becomes verbal, done by a duty supervisor with a radio and a printout, and the quality of your operation for that day depends entirely on how good that individual is.

Resource allocation systems exist to solve this and the good ones do reallocate. Where they strain is the constraint set at a specific station: which staff are qualified under your licence scope here, what your agreement says about break windows and mid-shift task changes, which equipment is under maintenance, and which stands are reachable in time on foot or by vehicle. Configuration gets you most of the way. The remainder is the supervisor.

What a custom build does: hold a live picture of every person and piece of equipment with their current task and next free time, evaluate against qualification and agreement rules, and propose reallocation when the schedule moves. The supervisor still decides, but from a screen showing who is genuinely free rather than from an assumption. This is where the first measurable improvement appears, because the commonest cause of a late start is not a shortage of people, it is not knowing which people are available.

Problem 2: delay attribution is an argument you lose without your own timestamps

Delay codes decide money. The airline records milestones in its own system, the airport records some in its collaborative decision making feed, and you record some on paper. When they disagree, the party with the weakest evidence concedes, and that is usually the handler.

This is the highest value problem in the category and it is not a technology problem so much as a capture problem. The timestamps that matter, particularly the boundaries between one party's responsibility and the next, are recorded minutes or hours after they occurred by someone reconstructing the turn.

What a custom build does: capture milestones at the moment they happen, on a device in the hand of the person doing the task, with the identity of the person and the position of the device attached. Chocks on, ground power connected, doors open, first bag on belt, last bag, doors closed, pushback commenced. When the airline's figure differs from yours, you have a record with a source rather than a recollection. Handlers who instrument this properly usually find two things: a share of the delay penalties they were absorbing were not theirs, and a smaller share genuinely were and are now visible in time to fix the underlying cause.

Some disputes are commercial rather than factual, so evidence will not win every one. It changes the default, which is what matters across a year of invoices.

Problem 3: ground support equipment is a pool nobody can see

Belt loaders, tugs, steps, ground power units, water and lavatory trucks, de-icing rigs. The asset base is heavy, expensive and mobile, and at most stations its location is known only to whoever used it last. Serviceability sits in a workshop system if anywhere. Utilisation is unknown, so fleet purchasing decisions rest on the same evidence as an argument.

What a custom build does: bring equipment into the same allocation model as staff, so a turn is assigned people and equipment together and the system knows the tug is committed until 14:35. Telematics on higher value units gives position and running hours, turning maintenance from calendar-based to usage-based and stopping the recurring event where a unit fails on stand because its service was scheduled by date. Utilisation then answers the fleet question honestly, usually saying you hold more of one type than you need and fewer of another.

Problem 4: qualifications and licence scope differ per station, and enforcement is a poster

Ramp work is qualification-bound. Pushback, de-icing, dangerous goods acceptance, loading supervision, driving airside: each needs training and currency, and your licence scope at one airport may not match another. In most handlers enforcement is a supervisor knowing their team, and the evidence is a spreadsheet the station manager updates when they remember.

What a custom build does: hold qualifications with expiry dates as a property of the person, and make assignment impossible where the qualification is missing or lapsed. The allocation engine then never proposes an unqualified assignment, which removes an entire class of finding from your next airline audit. Expiry forecasting matters as much: the system should tell the training coordinator which qualifications lapse in the next six weeks and which shifts that will break, because at most stations recurrent training is booked reactively after somebody has already dropped off the roster.

Problem 5: billing is reconstructed monthly from paper

Your handling agreements define what the turn fee includes and what is charged separately: additional services, extended hours, de-icing by fluid volume, equipment hire, dangerous goods, extra staff for a heavy load. Those extras happen on the ramp, are recorded on paper, then keyed into an invoice weeks later, and anything not written down is not billed.

What a custom build does: capture the chargeable event at the point of service, on the same device that recorded the milestone, so an additional service requested by the airline representative on the day appears on the invoice automatically with the requester's name attached. This is the least exciting feature in the build and it is frequently the one that pays for it, because unbilled extras across a busy station over a year add up to a number that surprises the finance director in the wrong direction.

The second half of billing is the airline-facing report. Handlers who publish SLA performance to their customers proactively, with the evidence attached, negotiate contract renewals from a stronger position than handlers who send an invoice and wait for the dispute.

What this costs and how long it takes

A first release covering turnaround milestone capture on ramp devices, live staff and equipment allocation against a moving schedule, and delay evidence with source attribution runs $70,000 to $150,000 and ships in 12 to 18 weeks. A full platform adding qualification enforcement with expiry forecasting, equipment telematics, chargeable event capture with invoicing against your handling agreements, and airline-facing SLA reporting runs $200,000 to $500,000 phased over 6 to 14 months.

What drives cost up in handling: the number of stations, each with its own licence scope, layout, agreement terms and airport feeds. Airport integration, since a collaborative decision making feed or an operational database is a different interface at every airport and some are politically harder to obtain than technically. Airline integrations, because each carrier's messaging and reporting expectations differ. Ramp hardware, including the offline behaviour a stand with poor coverage demands. And multi-language, which matters more than people expect. What holds cost down: prove milestone capture and allocation at your busiest station first, because the second station costs a fraction of the first and the tenth costs almost nothing.

Build versus buy, and where the line falls

Buy if you run a single station with a handful of airline contracts and a stable schedule. A shared roster, a radio and a competent duty supervisor genuinely handle that, and software would be overhead. Buy GroundStar if you are a large handler whose operation fits its model and you are prepared to configure your processes towards it, because its allocation engine has absorbed a great deal of real-world complexity and reproducing that is not a good use of capital.

Build when two or more of these are true. You operate multiple stations with different licence scopes and no single system covers them all. You regularly absorb delay penalties you believe were not yours because your evidence is weaker than the airline's. Your equipment pool is unmeasured and fleet decisions are made on opinion. Your qualification currency lives in a spreadsheet beside a roster that can assign anyone to anything. Or your chargeable extras are captured on paper and you suspect, correctly, that a meaningful share never reaches an invoice.

Our position: in ground handling the build case is unusually easy to justify because the return shows up in two places you can measure directly, which are delay penalties avoided and extras billed. Both are visible within a quarter of going live at one station. That is rare in operational software, and it means this is a category where you should insist on measuring the return rather than accepting a general efficiency story.

How to choose a developer for ground handling software

Ask them to stand on a ramp for a full shift before quoting. Everything that determines whether this software works is physical: gloves, noise, weather, the distance between stands, where a person can actually stop and tap a screen. A developer who designs this from an office produces an application that stays in the office.

Ask how the system behaves when connectivity drops behind an aircraft, because it will. Offline capture with reconciliation is mandatory, and the reconciliation rules for a milestone that was recorded late need to be explicit rather than improvised.

Ask what they have integrated at an airport, naming the specific system. An operational database or a collaborative decision making feed is a different problem from an airline's messaging, and both differ from equipment telematics. Obtaining a feed is often a commercial negotiation you will have to lead.

Ask how qualifications will block assignment rather than merely report on it. If the system can propose an unqualified assignment and rely on a supervisor catching it, the audit finding will eventually arrive.

Ask who owns the code and settle it before kickoff. You should hold the repository, the infrastructure accounts and the right to bring in another firm. At Digital Heroes the client owns the code from the first commit. In handling this is commercially direct: the timestamp record is your evidence in every delay dispute and every contract renewal, and a vendor who controls access to it controls your negotiating position.