From the Cockpit to the Dropzone: Why We Built PilotFlows

A pilot’s perspective on bringing aviation and skydiving together

My journey into skydiving started in the cockpit.

After completing my Private Pilot Licence (PPL), I wanted to build flight hours and gain practical experience. I was fortunate enough to be recruited by Skydive Luxembourg, a skydiving club in the north of Luxembourg, where I began flying the GA8 Airvan.

My mornings often started with a ferry flight from Luxembourg International Airport to Noertrange. The flight itself took around 30 minutes, although a fair share of that time was spent on the ground, waiting for the engine oil to reach the right temperature.

Once I landed, the pace changed quickly. As the first passengers boarded, I would often keep the engine running, ready to get airborne again. We would climb to 4,000 metres, release the skydivers, and return to the ground to prepare for the next load.

Repeat. Load after load. Flight after flight.

It was an incredible environment to learn in. But it also gave me a first-hand look at the operational challenges behind a successful skydiving day.

And one thing, in particular, kept coming back to me: why wasn't there a truly great software platform for running a dropzone?

The operational challenge behind every jump

From the outside, skydiving operations can look straightforward. Passengers arrive, the manifest organises the loads, the aircraft takes off, and the skydivers enjoy their jump.

Anyone who has worked at a dropzone knows there is much more to it.

Behind every successful load is a constant exchange of information between manifest, pilots, instructors, aircraft maintenance, and the people managing the wider operation.

Aircraft availability has to align with jump schedules. Loads need to be organised. Pilots need the right information. Mass and balance must be considered. Documents, maintenance records, and reminders must remain up to date. At the same time, the business still needs to manage members, bookings, and accounting.

All these activities are connected, yet they often end up spread across different tools, spreadsheets, paper records, and conversations.

At the time, the software used by the club covered the basics. It did what it needed to do, but it lacked the level of integration, usability, and technological sophistication we have come to expect from modern software.

I spent far too much time on paperwork and coordinating information between people and systems.

I knew there had to be a better way.

Understanding both sides of the operation

Early on, I realised that building a genuinely useful skydiving platform would require understanding more than just the aviation side.

A dropzone is both an aviation operation and a skydiving operation. Treating these as separate worlds creates unnecessary friction.

A manifest system might work perfectly well for organising jumpers, but what happens when aircraft availability changes? How does the pilot receive the information needed for the next load? How do aircraft limitations, weather conditions, and operational planning fit into the same workflow?

The reverse is equally important. Aviation management software alone cannot address the day-to-day realities of manifest, tandem reservations, and skydiving training.

A platform that ignores either side will always be incomplete.

Around this time, a friend challenged me to start an AFF course in Germany. I took the challenge and gained a new perspective on the sport.

Experiencing skydiving from the student's side gave me a much better understanding of the people, processes, and coordination involved beyond the cockpit. It was a valuable experience, and one that confirmed just how much respect the sport deserves.

Although I came to appreciate both perspectives, my strongest expertise and passion remained aviation. That became the foundation of our approach: start with aviation, understand the entire operation, and build the connections that make everything work together.

Building PilotFlows: Aviation first, integration by design

This is where Gilles and I began developing what would become PilotFlows.

Our goal was not simply to create another manifest system or another aircraft management tool. We wanted to build an integrated operational framework that could support the entire dropzone.

We started with the foundations: a central dashboard for managing members, accounting, and the essential administrative side of the organisation.

From there, we developed the aviation framework, focusing on the tools that keep aircraft and operations organised:

• Aircraft management and technical logs
• Maintenance tracking, reminders, and documentation
• Aircraft and operational scheduling
• Centralised access to important records and information

These are not secondary features. They are fundamental to operating aircraft responsibly and efficiently.

Only once these foundations were in place could we bring the aviation and skydiving sides together in a meaningful way.

The result is an integrated platform designed around the actual needs of a dropzone.

Connecting the cockpit with manifest

The skydiving module brings the operational pieces together, helping the people on the ground and in the air work from a more consistent picture of the day's activities.

Our focus includes:

• Manifest management: Organise loads and coordinate daily jumping activities.
• Winds aloft: Make relevant wind information available as part of operational planning.
• Mass and balance integration: Support load planning with the information needed to assess aircraft loading.
• Load sheets: Bring relevant load information into a more organised workflow.
• Skydiving training: Support the administration and organisation of training activities.
• Tandem reservations: Connect bookings with the wider dropzone operation.
• Accounting: Help manage the financial and administrative processes surrounding the operation.

The real value, however, is not simply the number of features.

It is how these features work together.

When information is scattered, people spend time chasing it, checking it, and transferring it between systems. When the right information is connected, coordination becomes easier and the operation can run with greater clarity.

Communication between manifest and pilot is essential. Both need to understand what is happening, what is planned, and what may need attention.

Our aim is to reduce administrative friction, save time for everyone involved, and improve operational awareness across the dropzone.

Built with the people who use it

From the beginning, we have taken a deliberate approach to development.

We take aviation seriously, and we believe the software supporting aviation operations should reflect that responsibility. We do not want to rush a product to market simply to be first. We want to build tools that are reliable, practical, and worthy of the trust people place in them.

That means listening closely to the people who use the platform, testing our assumptions against real operational needs, and continuously refining the experience.

Working closely with our customers has already been an important part of that process. Their feedback helps us identify what matters in day-to-day operations, where existing workflows create unnecessary work, and how we can make the platform more useful.

We have also developed a native iOS app, with Android support planned for the future. Alongside the web experience, this is another step towards making the right information accessible in the environments where people actually work.

Technology should adapt to the operation, not force the operation to adapt to the technology.

Looking ahead with Skydive Luxembourg

Seeing our work take shape alongside the work of our customers has been incredibly rewarding.

With Skydive Luxembourg, we are looking forward to putting the platform into action in the coming season. For us, this is more than a product milestone. It is an opportunity to see the ideas that began in the cockpit become useful tools for the people running a real dropzone.

The vision has always been practical: less time spent on paperwork, better coordination, clearer information, and more efficient operations.

We also know that no two dropzones operate in exactly the same way. Each has its own workflows, priorities, aircraft, and organisational structure.

That is why our next step is to work with a carefully selected group of additional dropzones. We want to collaborate closely with operators who share our commitment to improving how their operations work, learn from their experience, and continue building a platform that addresses real needs rather than hypothetical ones.

Building the tools aviation deserves

PilotFlows started with a simple observation: the people responsible for running a dropzone deserve better tools.

What began as a pilot's frustration with paperwork and disconnected processes has grown into a broader vision for integrating aviation management and skydiving operations in one platform.

We believe the future lies in connecting these perspectives rather than treating them separately.

For us, this is about more than software. It is about respecting the complexity of the operation, understanding the responsibilities of the people involved, and building technology that genuinely makes their work easier.

We are proud of how far we have come, grateful to everyone who has contributed feedback and experience along the way, and excited about what comes next.

We are building PilotFlows for the people who keep dropzones moving — from the manifest to the cockpit, and everywhere in between.

If you operate a dropzone and share our vision for a more connected, efficient operation, we would love to hear from you.

Discover PilotFlows Dropzone at pilotflows.com/dropzone.