Case Studies
Catarina Airport: integrated executive operations
How an executive aviation operation connects movement records, ground services and management
Mariana Soares · Founder and CEO of Auter
· 7 min read
Executive aviation cannot be captured by a record limited to an aircraft's arrival and departure. A movement may involve ground handling, time on site, specific requests and several people responsible for follow-up. At SP Catarina International Executive Airport in São Paulo, that complexity is part of everyday operations. The management challenge is to preserve a reliable sequence between events at the airport, services delivered and the information later used by the administrative team.
This article examines the operational logic of the case and what it takes to turn records into a usable view of an airport. It does not report a growth rate, staffing savings or a billing improvement: those outcomes would require an audited comparison that is not available here. The account is grounded in Auter's published review of airport asset management, and distinguishes documented experience from the capabilities a platform can provide.
Why executive aviation needs more detail
An executive airport's operation is not just a flight list. An aircraft arrives, occupies space, may require support and eventually departs. Requests may change between those events; services may be completed at different times; more than one person may take part. When every stage is noted in a separate place, reconstructing the sequence becomes a reconciliation exercise rather than a simple lookup.
The team needs to know more than how many movements took place. It needs to know which services belonged to each movement, when they were recorded, who changed them and what still needs approval. One accurate item may still be insufficient to explain an entire engagement. Traceability means preserving the context of an event, including corrections and cancellations, without erasing the history of the record.
At SP Catarina, the executive aviation profile makes it particularly valuable to treat movements and services as connected parts of a workflow. This does not mean that every movement generates the same services or charges. It means that each engagement can be described by what actually happened, with clear rules and responsibilities for every stage.
From the apron to the operational record
The first step toward an operation that can be followed is to record an event where it originates. A movement needs identification, a time and a connection to the aircraft and the relevant engagement. The record should remain available to authorized people continuing the work, even if a shift or responsible person changes before the event is closed.
Recording an event early does not remove the need for review. A time can be corrected, a service added or an entry cancelled. What matters is that a correction leaves a trail: who made it, when and, where appropriate, why. Without that history, an updated spreadsheet may show the final value but not explain the difference between the first entry and the validated one.
A simple distinction is useful: a movement is an operational event; a service is support actually delivered. Linking them helps with review but does not make them equivalent. Commercial and financial decisions should only rely on records checked under the operation's own rules. For a broader explanation of this connection, see Auter's guide to apron-to-finance management.
Ground services with their context intact
Ground services may involve different teams, times and verification steps. If a request lives in a conversation, the execution in another tool and the review in a spreadsheet, people must gather evidence after the fact. The risk is not merely forgetting an item. A service can be assigned to the wrong engagement, entered twice or charged before execution has been confirmed.
A shared record structure makes it possible to associate a service with the correct event and follow its status. Requested does not mean completed; completed does not automatically mean billable. Those states must make sense to those working at the airport and those checking commercial terms, without turning the operation into a sequence of forms that delays service.
In the Catarina case, the scale of activity makes this discipline relevant. Auter's operational account of its AmpliAR experience describes SP Catarina as a live operation with recurring aircraft movements and ground services on the platform since September 2024. The volumes and date in that account are reported by Auter; they are not independent measures of financial performance or productivity.
Check before billing
Between an apron event and a financial document lie decisions that should not be assumed. Teams must establish what happened, which services were confirmed, what terms apply and whether any exceptions exist. Integration can reduce re-entry, but good integration also makes clear which entries are not yet ready to proceed.
A disputed time, an incomplete engagement or an unapproved service should appear as a resolvable item. Otherwise, automation merely accelerates the circulation of an error. The finance team needs a traceable link to the originating record so that it can understand why an item reached review and who approved the operational information behind it.
This article has no audited basis for claiming that Catarina increased revenue, shortened month-end closing or eliminated billing discrepancies. The benefit discussed here is structural: maintaining a trail that makes it possible to review operations and billing from the same events. The wider question of rules and reconciliation is covered in airport billing.
Continuity and support matched to the operation
An airport active at different hours needs to think about continuity, not just data entry. The incoming team should find legible records and identified pending items. Management should be able to distinguish completed work from matters requiring attention without relying on the memory of the person who ended the previous shift.
In Auter's published account of its installed base, SP Catarina is described as having round-the-clock support, seven days a week. This is the support arrangement the company reports for this airport. It does not imply that the other aerodromes it serves have the same profile or that one support configuration suits them all. Scheduling, intensity and operational importance affect that choice.
Continuity also depends on access roles, prepared personnel and clear routes for correcting records. An available interface does not, by itself, resolve who validates a request or authorizes a change. The platform needs to follow the actual process, and the people doing the work need to understand that process.
What can be monitored responsibly
Indicators are useful only when their definitions are stable. Counting movements requires a rule for cancelled or corrected events. Counting services requires distinguishing requests from work done. Comparing periods requires knowing whether the scope of recordkeeping stayed the same. Without these conditions, a visually precise dashboard may invite a misleading conclusion.
A management view may bring together pending work, completed services, reviewed events and records ready for financial review. Every indicator should lead back to its underlying event, rather than showing only a total. This helps answer an immediate operational question: what should be checked before the next decision? A useful dashboard guides work and can explain its own numbers.
There is an important difference between the volume Auter reports and a proven business outcome. A live implementation alone does not establish that the platform caused movements to increase. An impact claim would require a baseline, a measurement method and an account of other changes at the airport. Without those, responsible communication describes how the process works rather than attributing results to a single cause.
One airport operation, not a network
SP Catarina is an independent airport operation. Auter's presence at other aerodromes does not make Catarina part of an integrated operational network with them. In the company's account, the two aerodromes in Mato Grosso do Sul are presented as the network operation, while the assets in Paraná are also described as independent.
This matters because one platform can serve different requirements without forcing every airport into the same management model. For Catarina, this article focuses on traceability within an executive aviation operation. Elsewhere, comparing aerodromes across a portfolio might be the priority. Conflating these contexts would lead to wrong assumptions about governance, shared teams and responsibility for services.
For a view of other applications, explore Auter's airport operations cases and airport management platform. These provide context, not a substitute for independently measuring this airport's outcomes.
What the Catarina case teaches
The case illustrates a basic requirement of airport management: records should follow the operation from aircraft movements through services to administrative review. When the history preserves who did what, when and how events relate, the team can investigate a discrepancy without reconstructing everything from messages and separate files.
That does not justify growth percentages or efficiency claims without supporting evidence. It does allow a discussion of how to design a more verifiable workflow and which questions to ask before automating it. Who documents a service? Who confirms its completion? Where does a correction appear? What prevents a charge based on an unapproved item? Such questions make a system useful to the operation rather than merely adding another screen.
The same thinking applies beyond Catarina. Auter's analysis of airport demand forecasting explains why future decisions need consistently defined records. At Catarina, the starting point is more immediate: understand each engagement in its own context and maintain a trace between work performed and the information used for decisions.