Pilot Bidding and Crew Management, Built for Part 121 Carriers
Pilot Bidding & Crew Management (Part 121) is part of AviationAlley. A Part 121 carrier runs on two things the rest of aviation software ignores: a monthly bid that has to honor seniority to the letter, and a duty-and-rest rulebook that can ground a flight if a single pairing busts a limit. Most operators bolt that onto a patchwork of spreadsheets, a legacy bidding tool, and a crew tracker that doesn't talk to either — so an award gets disputed, a reserve callout goes to the wrong pilot, or an open trip gets picked up by someone who's already out of legality. AviationAlley is being built as airline pilot bidding and crew scheduling software where the bid, the pairings, the duty board, reserve, and trip trading are one connected system, with FAR 117 and FAR 121.467 legality checked by the platform rather than caught by hand. AviationAlley is a pre-launch product opening to a founding cohort of operators, Part 121 included; everything here is what the platform is designed to do for that cohort, not a system carriers run in production today. If you operate under Part 121, you can request founding access at info@roffik.com.
The problem: bidding, crew, and legality that live in separate systems
A Part 121 monthly bid is one of the most consequence-heavy processes a carrier runs. Pilots bid their preferences against a published line of trips, the award has to follow seniority precisely, and the moment a senior pilot believes a junior one got a trip they should have held, the whole process is in question.
When the bid runs in a standalone tool — or worse, a spreadsheet — the award math sits apart from the crew records, the pairings, and the duty data, so reconciling a disputed award means stitching three systems back together by hand.
The harder problem is that the bid is only the start. Once lines are awarded, the carrier still has to staff reserve, cover open and dropped trips, and keep every pilot inside FAR 117 flight-time, duty, and rest limits and the FAR 121.467 constraints that govern the schedule.
When crew status, reserve assignments, and trip trades live in a different system than the legality rules, a perfectly reasonable open-time pickup or reserve callout can quietly push a pilot past a limit — and nobody sees it until a dispatcher does the math, or doesn't.
Underneath all of it is a single-source-of-truth gap. The bid package, the pairings, the duty board, the reserve pool, and open time each hold a piece of the truth, and none of them agree automatically.
Crew planners spend their days as human integration layers, copying an award into a roster, a roster into a legality check, and a legality result back into a callout — which is exactly where errors, disputes, and missed limits creep in.
- A standalone bidding tool that doesn't share data with crew records, pairings, or the duty board
- Seniority-ordered awards that are hard to defend when the award math sits apart from the roster
- Reserve assignments and callouts tracked separately, so the right reserve pilot isn't obvious
- Open and dropped trips picked up without an automatic check that the pilot stays legal
- FAR 117 and FAR 121.467 duty-and-rest limits verified by hand instead of by the system
- No single view that ties the monthly bid to the pairings, reserve pool, and open time it produces
How AviationAlley's pilot bidding and crew management are being built to work
AviationAlley is being designed so the monthly bid and the crew operation are one system, not two. A bid package is built around the carrier's lines, and pilots bid in the mode the operation uses — a straight LINE bid, or a preference-based PBS bid where pilots express what they want and the platform is designed to award seniority-ordered lines from those preferences.
Reserve is part of the same package, so the pilots who don't hold a line land in a reserve pool rather than in a separate list someone maintains by hand. When a planner needs to step in, manual override is built in, so an edge case can be resolved inside the same award rather than outside it.
From the awarded bid, the platform is built to flow straight into running the operation. A crew pairings builder lets planners assemble the trip pairings each line is made of, and a crew duty board is designed to show roster status derived from the actual shifts, flight activity, and duty-and-rest picture rather than a static list.
Reserve crew is handled as long-call and short-call assignments with a dispatcher callout, so when a trip needs covering the right reserve pilot is surfaced instead of guessed. Trip trading and open time let crews drop, pick up, and swap trips, with planner approval in the loop where it's needed.
The thread running through all of it is legality. AviationAlley is being built with deterministic FAR 117 and FAR 121.467 duty-and-rest engines — rule logic, not a prediction — so the platform can check whether an assignment, a reserve callout, or an open-time pickup keeps a pilot inside the limits before it's committed.
A trade that would keep everyone legal can move through without a planner refereeing every swap by hand, while one that wouldn't is flagged rather than quietly allowed. The legality result lives with the same crew and trip data the bid produced, so the carrier isn't reconciling an award in one tool against a limit check in another.
- Monthly bid packages with both LINE and PBS bidding modes, so a carrier runs the process its pilots already use
- Seniority-ordered awards designed to be defensible because the award lives with the crew and pairing data, not in a separate tool
- A reserve pool built into the bid package, plus manual override for the edge cases a planner has to resolve directly
- Crew pairings builder for assembling the trips each awarded line is made of
- Crew duty board with roster status derived from real shifts and duty activity, not a static spreadsheet
- Reserve crew as long-call and short-call assignments with a dispatcher callout that surfaces the right pilot
- Trip trading and open time — drop, pick up, and swap with planner approval, checked against FAR 117 before it's committed
Built Part 121-first, for the founding cohort
Crew and bidding aren't a standalone module bolted onto AviationAlley — they're being built as one connected part of a platform that also covers pilot credentials and currency, compliance records, scheduling, and safety reporting, all scoped to the FAR Part a carrier operates under.
For a Part 121 carrier, that means the same system that runs the monthly bid is the one that holds the duty board, the reserve pool, and the open-time market, so an award, a swap, and a legality check don't have to be reconciled across separate tools.
Because AviationAlley is a pre-launch product, what you see described here is the design intent for the founding cohort, not a record of carriers running it in production today.
The point of opening a founding cohort is to build the bidding and crew workflow alongside the operators who live it — so the LINE and PBS modes, the reserve callout, and the FAR 117 and FAR 121.467 checks match how real Part 121 crew shops actually work, rather than how a generic scheduler assumes they do.
If you operate under Part 121 and want a connected bid-to-duty-to-reserve workflow built around seniority and legality from the start, founding access is open. There is no public pricing during pre-launch; a conversation about your operation comes first. You can request founding access at info@roffik.com.
- One connected platform — bidding, crew, duty, reserve, and trip trading scoped to Part 121, not five disconnected tools
- Pilot credentials, currency, and compliance records sit alongside the bid, so the people being awarded lines are the same records the carrier tracks
- Founding-cohort access means the bidding and crew workflow is shaped with the operators who run it, not delivered as a finished generic product
- Deterministic FAR 117 and FAR 121.467 legality is part of the platform from day one, not a separate add-on
- No public pricing during pre-launch — founding access starts with a conversation about your operation
- Request founding access for Part 121 at info@roffik.com
Frequently asked questions
Is AviationAlley's pilot bidding and crew management available to use today?
AviationAlley is a pre-launch product. The Part 121 pilot bidding and crew management described here — LINE and PBS bidding, the seniority-ordered award, reserve pool, manual override, crew pairings, the crew duty board, reserve crew, and trip trading — is what the platform is being built to do for its founding cohort of operators, not a system carriers run in production today. If you operate under Part 121, you can request founding access at info@roffik.com.
Does it support both LINE and PBS bidding?
Yes — AviationAlley is being built to run a monthly bid in either mode, so a carrier uses the process its pilots already know. A LINE bid awards published lines directly, and a preference-based PBS bid lets pilots express what they want and is designed to award seniority-ordered lines from those preferences. Reserve is part of the same bid package, and manual override is built in so a planner can resolve an edge case inside the same award.
How does AviationAlley check FAR 117 and FAR 121.467 duty and rest?
With deterministic rule engines, not a prediction. AviationAlley is being built to check whether an assignment, a reserve callout, or an open-time pickup keeps a pilot inside the FAR 117 and FAR 121.467 limits before it's committed — a trade that keeps everyone legal can move through, while one that wouldn't is flagged. Because the legality check lives with the same crew and trip data the bid produced, the carrier isn't reconciling an award in one tool against a limit check in another.