Aviapros replaces the email chains behind a turnaround — connecting operators, FBOs and service providers to one live record of what was requested, delivered and approved.
Built for the people who turn aircraft around
A handling request today lives across a dozen emails, a spreadsheet and someone’s memory. Aviapros gives every arrival, departure and turnaround a single record — with the services, staff, parking, documents and approvals attached to it, and an audit trail behind every change.
See the platformEvents carry everything the turnaround needs — flights in and out, the services requested, who is assigned, where the aircraft is parked and what still needs approval.
Each service is recorded against the event with its own status, so billing and disputes work from the same record as operations.
Arrival, departure, turnaround, overflight or local flight — with your own reference format applied automatically.
Offline-capable by design, so the ramp keeps working when the connection does not.
Each outlet has its own airport, timezone and parking — hangar or apron — with allocation handled per movement.
Send sign-off to the right person automatically and keep the movement progressing.
Movements, service delivery and incidents roll up per station and across the network — the same data operations enter, without a second system.
Widgets for assignments, upcoming events, reminders and services — laid out per user, saved per account.
Flight movements, service delivery and incidents modelled for reporting, not scraped from operational tables.
Scheme and outlet level roles, 65+ permission scopes, and custom roles for contractors and third parties.
Send an email, post to Slack, call a webhook, create a reminder, assign a user, update a status or raise an incident.
Incidents, documents and every change to a record are captured in the course of normal operations — so an audit is a report you run, not a project you staff.
Safety, security, environmental, operational or ground handling — with severity, comments and status history.
| Event | Aircraft | Station | Time |
|---|
Operations, safety, finance and leadership work from one dataset instead of reconciling four.
Create the event, attach the flights, request the services, assign the crew and allocate the stand. Everyone sees the same state, and external parties can be sent a secure share link rather than another email thread.
Raise incidents against the event they belong to, with category, severity and a full status history. Document expiry is tracked and renewals are chased automatically, and every change is attributable.
Services are logged against the movement as they are performed, so invoicing works from the operational record. Usage, entitlements and plan limits are metered per scheme.
Everything in the product is available programmatically over REST with an OpenAPI schema, secured by API keys, with webhooks for downstream systems and SSO for access.
// create a turnaround and attach its services
const event = await aviapros.events.create({
outletId, type: 'TURNAROUND',
arrival: { flightNumber: 'ABC123', eta },
departure: { flightNumber: 'ABC124', etd },
})
await aviapros.services.request(event.id, [
'FUEL', 'CATERING', 'GPU',
])
// react to delivery downstream
aviapros.webhooks.on('service.delivered', (e) => {
billing.record(e.eventId, e.serviceId)
})Something not covered? Reach us at info@aviapros.com and we will come back to you.
FBOs, ground handlers and aircraft operators — anyone coordinating turnarounds across operations, safety and finance. It is built around aviation concepts rather than a generic scheduler adapted to fit: events, flights, movements, stands, services and incidents are first-class.
Your organisation is a scheme, and each station is an outlet with its own airport, timezone, parking and staff. Users hold roles at scheme level, outlet level or both, so a network manager and a single-station supervisor see appropriately different views.
Yes. There are 65+ individual permission scopes covering events, services, calendar, users, roles, billing and more, and you compose them into custom roles. Contractors and third parties can be given narrow access rather than a general login.
No. You can issue a secure, expiring share link for a single event so crew, operators or service providers see the live record without being provisioned as users. That is the main mechanism for cutting the email chain.
The application is offline-capable, so ramp and dispatch work continues during a loss of connectivity and syncs when the connection returns.
Workflows are built visually from triggers, conditions and actions — send an email, post to Slack, call a webhook, create a reminder, assign a user, update an event status or raise an incident. Approvals can be routed as part of the same flow.
Yes — a REST API with a published OpenAPI schema, authenticated with API keys, plus webhooks so downstream systems react to changes. SSO is available for user access.
Actions are written to an activity log tied to the outlet and the acting user, documents are stored against the records they relate to, and expiry dates are tracked with renewal notifications.
We are onboarding FBOs and ground handlers now. Join the waiting list and we will get in touch to walk through your stations and how you work today.