GSE Maintenance Management: A Complete Guide for Aviation Ground Operations
What GSE maintenance covers
GSE maintenance is the servicing, inspection and repair of the equipment used to support aircraft on the ground, from the tug that pushes an aircraft back to the steps passengers walk down.
What separates it from most other asset environments is that almost nothing stays still. Tugs, belt loaders, ULD loaders, passenger steps, ambulifts, ground power units, de-icers and lavatory service units move between stands and terminals through the day, get shared between teams and shifts, and are used hard by operators working to a departure time rather than to a maintenance manual. Non-motorised assets such as dollies and trailers move most freely of all, and are usually the least well tracked.
Why GSE maintenance is harder than it looks
The equipment itself is not exotic. A belt loader is a diesel engine, a hydraulic system and a structure, and any competent workshop can service one. The difficulty sits in the operation around it.
The fleet is distributed and moving. Assets sit wherever the last job left them, and locating a specific serial number can take an engineer longer than the repair.
Demand peaks when the workshop is quietest. Equipment is worked hardest during the morning wave and sits idle overnight, which is exactly when there is capacity to service it. Aligning those two things is the central scheduling problem in GSE maintenance.
There is no slack in the turnaround. Ground time is compressed by design, so an unserviceable loader becomes a departure delay almost immediately.
Access is restricted. Airside permits, security clearance and stand availability all limit which engineer can reach which asset and when.
Several organisations have a stake. Handling agents, airlines and airport operators all care about the same equipment, and performance is often contracted with penalties attached.
Operations run continuously. There is no shutdown window, which is why shift handover becomes such a significant point of failure in GSE environments.
Who maintains GSE, and why the model matters
GSE fleets are looked after under two arrangements, and the operational requirements differ.
In-house engineering teams maintain equipment their own organisation owns. Ground handlers and airport operators with their own workshops need planned maintenance scheduling, asset registers, statutory compliance tracking, parts control and internal downtime reporting. This is CMMS territory.
Third-party maintenance providers maintain equipment for other organisations. OEM service arms and independent contractors need contract and SLA management, chargeable job costing, quoting and customer reporting across multiple sites. This is field service management territory.
Plenty of larger operations run both, because the in-house team also sells spare capacity to other operators on the airfield. The distinction matters when choosing a system, since software built for one model tends to make the other awkward.
Where GSE maintenance operations lose control
Most downtime in airport GSE environments has little to do with technical capability. It comes from gaps in visibility and coordination, and the same handful recur across operations of very different sizes:
- Assets that cannot be located, so engineers spend productive hours searching and supervisors judge availability on what they last saw
- Faults reported verbally and lost at shift change, which means no job, no history and an apparently sudden failure weeks later
- Work orders without consistent structure, so jobs get duplicated, missed or closed with no record of what was done
- Planned services that keep losing the argument against breakdowns until assets are well past their intervals
- Parts held in stores, on vans and in a mezzanine, with no reliable view of what is available
- Performance data that arrives monthly, describing a problem that has already happened
We have gone through each of these, and what to do about them, in the most common causes of GSE downtime.
Why equipment condition is a safety question too
Reliability and safety are the same conversation on a ramp. IATA's ground support equipment programme reports that GSE operations account for up to 40% of global aircraft ground damage, with belt loaders, ULD loaders, passenger stairs and boarding bridges together accounting for around 40% of incidents.
Anti-collision systems, inching controls and proximity sensors reduce that risk when they work. Keeping them calibrated belongs in the service schedule alongside brakes and hydraulics, rather than being treated as fitted equipment that looks after itself.
The numbers that tell you whether it is working
Pick a small set and track them properly:
- Equipment availability by type and station, measured as serviceable units against required units at the start of each wave
- Planned versus reactive hours, the clearest single indicator of whether the programme is holding
- PPM compliance, meaning scheduled services completed inside their window
- Mean time between failures by equipment type, which exposes problem models and problem stations
- First-time fix rate, which reflects dispatch quality and parts availability together
- Equipment-attributed delay minutes, reconciled against the delay codes your airline customer uses
That last one deserves attention. IATA's Airport Handling Manual sets out the industry delay codes, and equipment unserviceability has its own entries. Your airline customer already measures your equipment reliability, whether or not you do. What those delays cost is covered in reactive versus preventive GSE maintenance.
Compliance obligations you cannot schedule around
Much GSE counts as lifting equipment in law. In the UK, the Lifting Operations and Lifting Equipment Regulations 1998 require thorough examination by a competent person at defined intervals, and the HSE is explicit that a scheduled service does not satisfy it. Its guidance on thorough examination states that inspections carried out as part of a preventive maintenance scheme are not a thorough examination.
Ground handling providers also work to IATA standards, with AHM 913 covering GSE maintenance and ISAGO audits assessing how well those management systems work in practice. Audits test evidence rather than intent, so an auditor asking for the last four services on one serial number expects it produced in minutes.
Improving a GSE maintenance operation
No single change fixes equipment availability. The operations that get there tend to work in this order:
- Build an accurate asset register, including serial numbers, locations and current certificate status
- Get daily pre-use checks off paper, since this generates the defect data everything else depends on
- Bring planned services, statutory examinations and open defects into one queue supervisors and engineers both see
- Fix parts availability for the most common planned services, which lifts first-time fix immediately
- Ring-fence engineer capacity for planned work and report weekly on the planned to reactive split
- Review by equipment type quarterly, and replace the models consuming disproportionate maintenance hours
Steps three and five are where most programmes come apart, because planned work keeps losing the argument against whatever broke that morning. We have covered how to protect it in preventive maintenance for GSE.
Read next
- Preventive maintenance for GSE, on building a planned programme that survives a busy season
- The most common causes of GSE downtime, on what actually costs you availability across terminals
- Reactive versus preventive GSE maintenance, on what equipment failures cost an airport operation
- Shift handover in airport GSE maintenance, on the information lost between shifts
FAQs
What is GSE maintenance?
GSE maintenance is the servicing, inspection and repair of ground support equipment used during aircraft turnaround, covering tugs, loaders, passenger steps, ground power units, fluid handling units and non-motorised equipment. It combines planned servicing, statutory examination and reactive repair.
Why is GSE maintenance more difficult than other asset maintenance?
Because the fleet is distributed and constantly moving, demand peaks when workshop capacity is lowest, airside access is restricted, and there is no shutdown window. Equipment failures also translate into aircraft delays almost immediately, so tolerance for downtime is very low.
What causes most GSE downtime?
Gaps in visibility and coordination rather than technical failure. Assets that cannot be located, defects reported informally, inconsistent work order records and planned services that keep getting rescheduled account for more lost availability than the repairs themselves.
What is the difference between GSE preventative maintenance and reactive maintenance?
Preventive maintenance is planned servicing carried out before failure, triggered by operating hours, mileage, lift cycles or elapsed time. Reactive maintenance is repair after a breakdown, which on a ramp usually means during live operations when no spare unit is available.
Who is responsible for GSE maintenance at an airport?
It depends on ownership. In-house engineering teams at ground handlers and airport operators maintain their own fleets, while third-party providers and OEM service arms maintain equipment under contract. Larger operations frequently do both.
What software do GSE maintenance teams use?
In-house teams generally need a CMMS covering planned maintenance scheduling, asset registers, parts and compliance tracking. Providers maintaining equipment for customers need GSE maintenance software with contract, SLA and job costing capability. Both models need mobile access for engineers working airside.
How do you measure GSE maintenance performance?
Equipment availability by wave, the split between planned and reactive engineer hours, PPM compliance, mean time between failures, first-time fix rate and equipment-attributed delay minutes. The planned to reactive split is the most useful single number for judging whether a programme is holding.
Getting control of GSE maintenance
The technical side is rarely the constraint. Your engineers know how to service the equipment. What determines availability is whether the right asset, the right engineer, the right part and the right paperwork come together at a time that does not clash with a departure.
If you want a starting point, work out what share of your engineers' hours last month went to planned work rather than breakdowns. Most operations that have never measured it find the answer lower than expected, and it is the number that moves everything else.
Service Geeni's aviation and GSE maintenance software brings assets, jobs, engineers, stock and compliance dates into one system, with separate FSM and CMMS models depending on whether you maintain equipment for customers or run your own fleet.
Before changing anything, it is worth establishing where your operation currently sits.
How mature is your GSE maintenance operation?
Most improvement conversations stall because nobody agrees on the starting point. The four stages below describe how GSE maintenance operations typically develop, and each has a test you can apply honestly in about five minutes.
Level 1: Reactive
Work arrives as breakdowns. There is a schedule somewhere, but the operation runs on whatever failed this morning.
How to tell. Ask how many planned services were completed inside their window last month. If nobody can answer without working through a spreadsheet by hand, you are here.
What is happening underneath. No reliable asset register, faults reported verbally, and no usable service history. Equipment availability is discovered rather than known.
Level 2: Structured
Work gets written down, but after the fact. Jobs are captured in a system, an asset register exists without being complete, and the maintenance schedule lives in a workbook one person owns.
How to tell. You can produce a service history for an asset, but it takes a day and involves asking an engineer what they remember.
What is happening underneath. Records exist for compliance and invoicing rather than for decisions. Statutory examination dates are tracked separately from services, which is how equipment ends up airside with an expired certificate.
Level 3: Visible
The schedule drives the work. Services are triggered by hours and usage as well as the calendar, pre-use checks are digital, and defects create jobs automatically.
How to tell. You know your split between planned and reactive engineer hours, and you review it more often than monthly.
What is happening underneath. Parts are reserved against planned jobs, engineers arrive with the history on screen, and first-time fix rates climb because dispatch decisions are informed.
Level 4: Optimised
Planned work is protected rather than negotiable. Availability is managed by wave, reliability data drives replacement decisions, and compliance dates fire alerts before they expire.
How to tell. You can say what equipment availability was at 05:30 last Tuesday, by equipment type, and reconcile your own downtime record against the delay codes your airline customer is using.
What is happening underneath. Maintenance has become a planning function rather than a response function. Most operations that reach this stage did so by fixing coordination rather than by hiring more engineers.
Very few operations sit cleanly in one stage. It is common to be at level 3 on motorised equipment and level 1 on dollies and non-motorised assets, which is worth establishing before deciding what to fix first.
The playbook below sets out the same four levels alongside the seven biggest downtime drivers in airport GSE operations, in a single document you can share with your team.
Download Full PDF
Read More…
Book Your Demo Today
