Help Shape a Better Way to Operate Part 135

Running a Part 135 operation is complicated.

Every trip requires the coordination of aircraft, crew, scheduling, flight planning, maintenance, qualifications, currency, duty and rest requirements, operational releases, records, and dozens of other details. Yet many operators still manage those responsibilities across multiple systems, spreadsheets, emails, text messages, and manual processes.

The result is familiar: duplicated work, information that doesn't always flow where it should, problems discovered later than they should be, and valuable people spending too much time administering the operation instead of operating it.

We believe there is a better way.

ProFlyt Nexus is built as a connected operational platform designed around the way aircraft operators actually work—from the creation of a trip through crew assignment, flight planning, compliance, maintenance readiness, execution, postflight, and records.

But we don't believe the best version of Nexus can be built in isolation.

That's why we're creating The Founding 135.

What is the Founding 135?

The Founding 135 is a group of 135 Part 135 operators who will receive complimentary access to ProFlyt Nexus and a direct relationship with the team building it.

This isn't simply a free trial.

We're looking for operators willing to put Nexus into real operational environments and tell us what they experience.

That feedback will directly influence the evolution of ProFlyt Nexus.

Our goal isn't to tell operators how they should operate.

Our goal is to build ProFlyt Nexus around how great operators actually operate.

What's in it for your operation?

Founding 135 members receive a minimum 18 months of complimentary access to Nexus. More importantly, they gain something that's difficult to obtain from an established software vendor: a seat at the table.

You'll have a direct connection to the Nexus team. Your operational experience will help identify priorities, challenge assumptions and influence future capabilities.

And the objective isn't simply to build more features. It's to produce measurable improvements in the operation.

• For pilots

  Less administrative burden and better quality of life—fewer disconnected workflows, better visibility into schedules and requirements, and less repetitive administrative work.

• For Chief Pilots + operations leadership

  Better operational awareness and fewer surprises across crew legality, qualifications, currency, duty and rest, aircraft availability, maintenance status and trip readiness.

• For owners + executives

  Better economics through more effective use of aircraft and crews, reduced administrative workload, protected revenue opportunities, better visibility, and scalable operations.

What are we trying to accomplish?

We aren't trying to digitize inefficient processes and call that innovation.

We're asking a harder question:

How much of the administrative burden required to operate aircraft can technology eliminate altogether?

If information already exists somewhere in the operation, why should someone have to enter it again?

If ProFlyt Nexus knows an aircraft's status, a pilot's qualifications, a crew member's currency, a duty limitation and the requirements of a trip, why should someone have to manually discover conflicts?

If a problem can be identified hours, days or weeks in advance, why should the operation discover it when it's time to launch?

And if software can give pilots, schedulers, Chief Pilots, maintenance personnel and management a common operational picture, why should everyone maintain their own version of the truth?

Those are the problems we want the Founding 135 to help us solve.

Why only 135?

Because this isn't intended to be an unlimited giveaway.

We want a manageable group of operators with whom we can maintain a meaningful relationship.

Different fleet sizes. Different missions. Different operating models. Different organizational structures. Different ways of solving the same problems.

Those differences matter. They help prevent Nexus from becoming software designed around one operator's workflow and instead help us build a platform capable of supporting the broader Part 135 community.

Once 135 qualified Part 135 operators have joined the Founding 135, the founding group is complete.

What we're asking from you

We're not asking you to redesign our software for us.

Operate.

Use Nexus where it makes sense within your organization. Put it in front of the people who actually do the work. Let pilots use it. Let schedulers challenge it. Let Chief Pilots find its weaknesses. Let management determine whether it's actually making the operation better.

Then tell us the truth.

If something works exceptionally well, we want to know. If something is frustrating, we especially want to know. And if there's something your operation needs that Nexus doesn't yet do, we want to understand why.

That's the value exchange behind the Founding 135.

You bring the operational experience.

We provide the platform, the development resources, and a direct line to the people building it.

Together, we build something better.