Every Part 135 operator knows the basics: flight time limitations, rest requirements, the currency rules that govern who can fly what. The regulatory framework is well-defined, and most operators get it right.
What they get wrong is almost never the FARs. It's the operational system around them — how trips get staffed, how crew availability is tracked, how last-minute changes get communicated. The regulatory compliance is sound; the informal processes around it aren't.
Here are the most common crew scheduling mistakes in Part 135 operations, and what they actually cost.
Treating the bench as a backup plan instead of a core resource
The most operationally damaging mindset in charter crew scheduling is thinking of your bench pilots as the option you turn to when things fall apart. In a healthy Part 135 operation, the bench isn't the emergency plan — it's part of the normal staffing model.
Demand in on-demand aviation is, by definition, uneven. Trip requests cluster around holidays, weather windows, and event calendars in ways you can't fully predict. An operator who staffs only for average demand will constantly find themselves scrambling during peaks. An operator with a well-maintained bench can absorb those peaks without the scramble.
The mistake is failing to invest in the bench during slow periods — not adding new pilots, not keeping contact details current, not tracking who's current on what aircraft — and then expecting the bench to perform under pressure when you actually need it. Effective Part 135 crew scheduling means treating bench management as an ongoing operational function, not a reactive one.
Currency tracking that lives in memory
Ask most charter operators where they track pilot currency — medicals, flight reviews, type-specific training, instrument currency — and the answer is usually some combination of a spreadsheet, a folder of PDFs, and the chief pilot's memory.
That works until it doesn't. Currency lapses in a 135 operation create two problems simultaneously: a compliance problem and a crew shortage. The pilot you were counting on for a trip is suddenly unavailable, and you either scramble for a replacement or discover the issue after the trip is already booked.
The fix isn't complicated. Currency dates need to live somewhere accessible, with some mechanism to flag expirations before they happen. Pilot availability tracking in a structured roster — with expiration dates you can actually see — is the difference between a manageable schedule and a compliance surprise.
Sequential outreach when simultaneous would work
When a trip comes in, many operators work through their bench one at a time: call the first pilot, wait for a response, call the next if they're unavailable, repeat. On a relaxed schedule with advance notice, this works fine. Under time pressure — a same-day trip, an AOG replacement, a late add-on leg — it's too slow.
The better model for short-notice staffing is simultaneous outreach: send the trip details to your relevant bench pilots at the same time, with a clear reply-to-confirm mechanism, and take the first confirmed response. Purpose-built pilot scheduling software makes this straightforward — you fill the seat faster and pilots don't sit waiting to hear whether they got the trip.
Sequential calling is how you staff trips when you have four hours. Simultaneous notification is how you staff them when you have forty minutes.
No record of who flew what
Part 135 operations have record-keeping requirements, and most operators satisfy them. What often doesn't get recorded is the operational history that's useful for running the operation — not for compliance, but for making better decisions.
Which bench pilots showed up on time and performed well? Which ones committed and then cancelled last minute? Which pilots have flown your specific aircraft and know your operation versus which ones are coming in cold? This information shapes who should get the first call on the next trip, but it only helps if you have it.
Without it, every staffing decision is made with the same information: qualifications and a phone number. The operators who staff trips consistently well are the ones who track more than that.
Scheduling confirmation that relies on verbal agreements
A pilot says "I'm good for the trip" on the phone. The trip is logged. The client is confirmed. Then on the day of the operation, there's a miscommunication about show time, or the pilot thought it was a different date, or the details changed and nobody sent an update.
Verbal confirmation in a fast-moving Part 135 operation is a reliability risk. The details of a trip — departure time, aircraft, route, hotel if applicable, pay — should be communicated in writing so there's a shared record and no ambiguity. SMS is fine. Email works. What doesn't work is a phone call that neither party documented.
The common thread
These aren't exotic problems. They're the predictable failure modes of informal systems that were built incrementally, worked well enough during lower-volume periods, and then didn't scale when the operation grew or demand spiked.
The Part 135 operators who run consistently clean operations — fast trip staffing, low last-minute scrambles, solid record of who flew what — have usually built something more systematic around their crew coordination. Not necessarily complicated, but intentional: a pilot roster with real data in it, a notification process that doesn't depend on the chief pilot's memory, and a way to confirm trips that creates a paper trail. That's the structural difference, and it compounds over time.