Exterior Dry Wash at Trieste Ronchi dei Legionari (LIPQ)

How does airside coordination work at Trieste Ronchi dei Legionari?

The airport operator also functions as the handling agent, so PPR, slot requests and third-party service approvals all flow through the same GA office. Once handling is confirmed we coordinate directly with their duty team to align our arrival with the aircraft's block time. Because there is no separate FBO, the handler escorts our crew airside and designates the stand where we may work.

If the aircraft will remain on the apron overnight or through a maintenance window, the handler confirms GPU availability and ensures our team has the escort and access needed for an extended clean. For quick turns—particularly when the aircraft repositions within an hour or two—we pre-position on the apron before block-in so the dry wash begins as soon as the engines shut down and ground power connects.

All waste goes into sealed containers; we carry it off the airside zone at the end of the job. The handler appreciates that there is no runoff, no hose reel and no request for a wash pad, which simplifies the approval and keeps the apron tidy.

What does the dry-wash process involve on the ramp?

We begin at the nose—canopy, radome and windscreen—then work aft across the fuselage crown, cheat line and belly. Waterless cleaner is applied panel by panel with a pump sprayer, allowed a few seconds to emulsify contaminant, then lifted with a microfibre cloth in straight, overlapping passes. Bug residue on the leading edges and nacelle inlets receives a dedicated pre-treatment; exhaust carbon around the tailpipe gets a heavier degreaser before the final wipe.

Wings, winglets and empennage are cleaned from a stable ladder or platform; we never lean on control surfaces or stand on the wing skin. The belly and gear bays are degreased with a low-residue solvent that cuts hydraulic film and brake dust without leaving streaks. All exterior lights and windows are polished, and any light oxidation on brightwork is touched up by hand.

The entire process is no-touch for avionics bays, static ports and pitot probes. Waste cloths and spent chemistry are bagged and removed; nothing enters a drain or remains on the apron. Duration ranges from three hours for a light super-mid to eight for an ultra-long-range airframe with a cold-soaked belly.

What changes at Trieste Ronchi dei Legionari that affects the service?

The field sits at thirty-nine feet elevation with a single three-thousand-metre runway, 09/27, long enough for any business jet and most ACJ/BBJ variants at typical weights. The low elevation means density altitude is rarely a constraint, even in summer, so departures are not rushed and a longer ground time for cleaning is easier to accommodate.

Because the airport operator is also the handler, there is no competition between FBOs for ramp space or services; stand allocation and third-party approvals follow a single internal process. The GA lounge and office sit in one location, which simplifies crew briefings and paperwork handover after the clean.

Trieste Ronchi lies roughly thirty to forty kilometres north-west of Trieste itself and serves a catchment that includes Gorizia, Udine and towns along the Slovenian border. Flight departments often use LIPQ as a positioning base for meetings in multiple cities, which makes recurring dry-wash schedules practical: the same airframe returns every two to four weeks, and we maintain a standing coordination with the handler's duty desk.

When does a dry wash make sense versus a full wet wash at Trieste?

If the fuselage carries only light dust, exhaust shadow and a few bugs from the last leg, a dry wash restores the finish in a single visit and leaves no water to freeze in door seals or drain masts overnight. When the belly is caked with de-icing fluid residue, the nacelles show heavy carbon build-up, or the entire airframe has been through a season of salt spray, a wet wash or rinseless procedure is the better choice—but that requires a wash bay or dedicated pad, which LIPQ does not advertise as standard infrastructure.

For aircraft in regular service—charter rotations, corporate shuttles, fleet positioning—a dry wash every two to four weeks keeps the exterior presentable and prevents contaminant from bonding to the paint. Flight departments that operate a longer interval between deep cleans use the dry wash as the interim step, preserving the single-stage polish underneath and reducing the labour required when the full detail eventually comes due.

How do we schedule around tight turnarounds or multi-day stops?

For a quick turn—passenger drop, refuel, immediate departure—we ask for wheels-down time and planned block-out as soon as handling is arranged. If the window is ninety minutes or less we bring a larger team and split the fuselage into zones, working nose-to-tail in parallel so the aircraft is clean before the flight crew returns from the terminal. The handler's ground-power cart stays connected throughout, and we keep one team member in radio contact with the ramp supervisor to ensure we are clear of the aircraft ten minutes before engine start.

When the jet remains on stand for maintenance, crew rest or a multi-day charter pause, we schedule the dry wash during daylight hours to ensure proper lighting for quality control. If the aircraft will night-stop, we confirm GPU availability and any curfew or noise restrictions that might affect our access. The handler typically prefers that exterior work finishes before the last inbound commercial service, so we plan arrival and setup accordingly.

Recurring cleans—monthly or bi-weekly—are logged into a standing schedule with the GA office, and we send a reminder forty-eight hours before each planned visit. That cadence works well for fleets using Trieste as a northern-Italy hub or for owner flights that return on a predictable rotation.

What should the flight department tell the handler in advance?

Include our company name, crew size and expected duration in the handling request so the GA office can note the third-party service in the slot file and arrange the airside escort. If the aircraft has any open maintenance—panels off, gear pins in, engine blanks fitted—let both the handler and our team know; we adjust the clean to avoid those zones and coordinate a second visit once the jet is buttoned up.

Confirm whether the aircraft will be on GPU or APU during the work. We prefer GPU because it is quieter and keeps the APU exhaust plume away from our crew on the tail. If a tug or tow is planned immediately after the clean, tell us the block-out time so we can pack our kit and clear the stand without delaying the push.

For night-stops or multi-day visits, share any crew-rest requirements or passenger schedules that affect when we may work near cabin doors or under the wing. The handler will pass that detail to our team lead during the airside briefing, and we shape the workflow to keep noise and foot traffic away from occupied areas.