Products
Agents for every organisation at the airport.
Ground handlers first, then security providers and airport operators. For each: what the agent does, from which records, what it delivers, the indicator you judge it on — and the unit we bill.
01 · Ground handlers
Three processes where the evidence is worth money.
You work under contract with the airlines and under the airport’s rules — and from 27 March 2028 under EU safety rules of your own. Every turnaround produces milestones, every occurrence a report, every member of staff a training record, and every dispute comes down to the records.
1.1 · Proof of service
Every turnaround documented against the contract, before anyone disputes it.
Your SGHA and its service-level annex set what you owe each airline, station by station. The agent reads the turnaround as it happens and compiles the file that shows what was delivered, when — and, when there is a delay, the evidence on whose it was.
On-block, doors, unloading, loading, off-block: each milestone set against the service standards agreed with the airline; deviations timestamped, with the cause proposed from the records.
When a delay is attributed to handling, the milestones, messages and requests that confirm or contest it, assembled for the station manager to sign or send back.
Towing, extra staff, services requested on the day: reconciled with the charges in Annex B, the billing line prepared for approval before the billing run.
Each indicator of the service-level agreement, calculated from the flight files, every figure traceable to the turnarounds behind it.
1.2 · Damage and occurrences
From the ramp event to the report, inside 72 hours, with the evidence attached.
More than 29,000 aircraft ground damage events were reported to IATA in 2025. In the EU, each one means a report due within 72 hours, often a claim, and a question the airline will ask. The agent assembles the answer while the facts are fresh.
Ground damage, incorrect loading, dangerous goods, fuel spillage: the report coded in the ECCAIRS taxonomy, the 72-hour deadline computed, statements, photos and equipment data attached. Filing remains a human act.
The sequence of events rebuilt from the milestones and the rosters, the evidence organised for the airline and the insurer, the questions of liability laid out against the contract.
Where the analysis finds a safety risk, preliminary results are due to the authority within 30 days and final results in principle within three months: the agent tracks both, and the corrective action until a person closes it.
Damage and loading errors by cause, stand, shift and type of equipment — the figures your safety review needs, each one traceable to its reports.
1.3 · The 2028 rules
Part-ORGH readiness, built from your operation rather than written for the audit.
From 27 March 2028, Delegated Regulation (EU) 2025/20 applies to ground handling organisations: a declaration, a management system, safety reporting, competent personnel, documents and records. The agent builds that evidence continuously, so the declaration describes what you actually do.
Each point of Part-ORGH set against your manuals, records and contracts: what already exists, what is missing, who owns the gap. The rules, point by point
Airside driving, dangerous goods, de-icing, security: who is qualified for what, which expiries fall due, who is rostered with a lapsed qualification.
Audit findings, occurrences, changes to the operation: each one with its owner, its deadline and its corrective action, until a person closes it.
Daily checks of ground support equipment, shift handovers: what was done, what is missing; the maintenance ticket prepared.
Evidence organised the way each auditor will ask for it, with the register of variations from the IATA Ground Operations Manual (IGOM) and the action plan.
02 · Security providers
Certifications, tests and incidents kept current every day.
Your screeners are certified, trained recurrently, tested; your equipment is tested daily; your incidents are reported within 24 or 72 hours. Every requirement produces a record — and the airport and the authority will both ask for it.
Screener certification, initial and recurrent training, clearances: who is current, which expiries are due, which files are complete for the authority; sessions to schedule proposed. The agent never issues or revokes a certification.
Daily tests of walk-through detectors, X-ray units and trace detectors, handovers, checkpoint incidents: what was done, what is missing, what is inconsistent; the ticket prepared.
Airport, authority or internal tests: result logged, cause proposed, corrective action followed until a person closes it.
In the common template: class proposed, deadline computed by impact (24 hours, 72 hours or monthly), sources attached. Filing remains a human act.
Tests, waiting times, incidents, trained headcount: the report your contract requires, every figure traceable.
03 · Airport operators
Six operational areas, inside your systems.
Airside, security, baggage, passengers, safety, environment: for each area, what the agent does every day, from which systems, what it delivers, and the indicator you already track. Billed per site.
3.1 · Airside and movement areas
Every inspection logged, every finding turned into a work order.
Inspections, runway condition, wildlife, FOD, lighting: the work gets done. What is missing is the time to log it, reconcile it and turn it into work orders.
Per area and per inspection round: done, missing, incomplete. Every finding — lighting, markings, pavement, FOD — becomes a work order drafted in your CMMS, with the position and the photo.
From the observations entered by the duty officer: a draft report with the runway condition code per third, to validate before transmission. It never transmits itself.
Wildlife strike, FOD, runway incursion, damage by ground equipment: the report drafted in the right taxonomy, deadline computed, sources attached, ready to sign.
Sightings, dispersals, strikes per movement; the periodic report compiled from the log, every figure traceable.
3.2 · Security
Tests, certifications and incidents ready before anyone asks.
Screening checkpoints, access control, ID passes, daily tests: every requirement produces a record, and every missing record becomes a finding at the next audit.
Daily tests of walk-through detectors, X-ray units and trace detectors, handovers, checkpoint incidents: done, missing, inconsistent. The ticket to maintenance or IT is drafted with the log excerpt.
In the common template: class proposed, deadline computed — 24 h, 72 h or monthly by impact —, sources attached. Filing with the authority remains a human act.
Initial and recurrent training, certifications, airport ID passes: who is current, who expires within 30, 60 and 90 days, which files are complete for the ID office. It never issues or revokes anything.
The way the national quality control programme auditor will ask for it: procedures, records, tests, training — with the gap register and the draft corrective action plan.
3.3 · Baggage
Every missing bag explained, every system stoppage logged.
When a bag goes missing, the explanation is scattered across scans, flight data and the system log. When a line stops, the incident report waits.
Scans at check-in, loading, transfer and delivery, flight data, system events: where and why the bag left its path. The file is ready for the airline or the handler, with a proposed cause.
Hold-baggage screening alarms, conveyor stoppages, jams, missed reads: the incident report drafted from the system log, the maintenance ticket prepared.
Unaccompanied hold baggage identified from check-in and boarding data, for the security officer to decide. It never triggers an offload itself.
Mishandled bags by airline, by cause and by point in the journey; system incidents and downtime — every figure traceable to the files behind it.
3.4 · Passengers and PRM
Assistance on time, every complaint answered on the facts.
The airport managing body is responsible for assistance to persons with reduced mobility and publishes its quality standards. Every case waits for a reply someone can stand behind.
Airline pre-notifications, pick-ups, waiting time at the meeting point: every case tracked against your published quality standards; deviations flagged to the provider in time to act.
Waiting times at screening and check-in reconciled with flights and open positions; the overruns documented for the morning meeting.
Complaints and lost-property requests classified, a case opened with its deadline, a draft reply from your procedures. A person reviews and sends.
PRM assistance, queues, complaints: the reports for the airport users’ committee and the authority, compiled from the register, every figure traceable.
3.5 · Safety and compliance
A safety management system that lives every day.
Reports within 72 hours, hazard register, corrective actions, the aerodrome manual, audits by the authority. The evidence exists; it is scattered across ten systems and three mailboxes.
From the shift log, the radio or the mailbox: report in the taxonomy, class proposed, deadline computed, sources attached. The responsible person edits and signs.
Occurrences grouped, hazards updated, corrective actions followed until a person closes them, reminders drafted.
For the safety review: occurrences by type, incursions, FOD, wildlife strikes, overdue actions — from the register, not from memory.
Evidence pack the way the authority will ask for it; gaps between the aerodrome manual and the practice on record; draft corrective action plan.
3.6 · Environment and neighbours
Every complaint linked to the flight, every report compiled from the data.
Noise complaints, flight tracks, periodic reports, emissions monitoring, local commitments: obligations that are proven with data you already produce.
Time, place and description reconciled with movements and noise measurements; a draft reply grounded in the facts, for a person to approve.
Complaints by area and period, night movements, noise measurements, energy and emissions: the reports for the consultative committee and the authority.
Extracts, tables and supporting documents for your declarations and certifications, every figure traceable to its source.
04 · Other actors
The same agents, for everyone who shares these obligations.
Airlines and stations
The turnaround report and service evidence on the airline side, the station’s occurrence reports, baggage claim files — in the station’s own tools.
Regulated agents and cargo
The register of trained and certified staff, consignment security declarations, the file ready for the authority’s inspection — Implementing Reg. (EU) 2015/1998, Chapter 6.
Maintenance contractors
Preventive-maintenance evidence for lighting, security equipment and conveyors, reconciled with the plan; work orders created from inspection findings.
Pricing
You pay for documented work, never for seats.
We publish how we bill before we publish a price: the price depends on the scope, and we quote it before day one. The structure does not change.
Pilot project
One process, six weeks from the day access opens, one indicator agreed before day one. A fixed price for a defined scope, quoted before we start. If the target is not met, we stop — and you keep everything produced.
In production
An annual fee per station or per site — connections, the ledger and a volume of documented work included — then a price per unit beyond it: a documented turnaround, an occurrence file, a person on a register. Never per seat, never by the hour.
Our commitment
The pilot’s indicator is written into the production contract. If it slips for reasons attributable to us, a service credit applies, as the contract sets out. Your ledger and deliverables stay in your systems, in open formats, whatever happens.
The rules every agent shares.
A Khelion agent is not a chatbot. It has inputs, outputs, a warrant, and a person it hands over to.
It may
Read the systems the warrant names. Draft, classify, reconcile, compute a deadline, prepare a work order, a ticket, a reply, a report. Write only where the warrant allows it.
It never
Files a report with an authority. Transmits a runway condition report. Issues or revokes a pass. Triggers an offload. Sends a letter. Closes a ticket or a finding. Changes what a witness wrote.
It records
Every action, every refusal and every stop in a ledger you export. Outside the warrant, it stops and notifies a named person — with its reasoning attached.
Not on the list? We build the agent.
A local reporting rule, a contractor onboarding, a recurring return to an authority. If it is written down, repeated, and someone can say what “done” looks like, we build the agent around it — same warrant, same ledger. How the pilot project runs