← Back to the platform
How it fits
How it fits
Fits alongside what you run today.
ThruFly runs on its own. A pilot does not require an integration project, and it does not replace your flight information, resource management or A-CDM systems.
What a pilot needs
- A station and a sponsor
- One or two turnaround procedures
- A small group of crew with phones or tablets
- A point of contact on each side
What it does not need
- An integration or IT build to start
- Access to your flight or resource systems
- Passenger personal data
Where we could go next
Connections we would scope with a pilot partner.
ThruFly has not been integrated with other systems. These are candidates we would choose and scope together, based on what your station needs most. We will not promise an integration we have not built.
| System | What it could provide | Status |
|---|---|---|
| Flight schedule or AODB | Flight and stand data, so turns appear without manual entry | Not built yet |
| A-CDM milestones | Turnaround milestones shared with the airport collaborative process | Not built yet |
| Resource or workforce management | Crew assignments brought in from the system you already use | Not built yet |
| Safety and quality reporting | Turn records passed to the tools your safety team uses | Not built yet |
| Single sign-on | Staff sign in with the identity they already have | Not built yet |
Questions your IT team will ask
We answer these in writing before a pilot starts, and where the honest answer is "not yet" we will say so:
- Where is data hosted, and who can access it?
- How are users, roles and access controlled?
- How is data protected in transit and at rest?
- How long is data kept, and what happens at the end of a pilot?
- What is logged, and who sees the logs?
- Which third-party services are involved?
See Security and data, or email info@thrufly.com.
Tell us what you run today.
We will say honestly what a pilot would and would not connect to.