Crew bidding, duty/rest, and qualifications that scale with the fleet.
Part 121 means thousands of pilots, hundreds of training events a week, and a duty/rest regime that has to hold up under inspection. Run the crew side as one system of record — bidding, reserve, open-time, MEL, and FAR 117 — without losing the audit trail.
Launching the first quarter of 2027.
Jump to a feature
Tap any chip to jump to its section below.
- Monthly bid packages
- LINE + rule-based PBS
- Idempotent award engine
- Crew pairing builder
- FAR 117 enforcement
- FAR 121.467 cabin-crew enforcer
- Union / CBA contract overlay
- Crew duty board
- Fatigue risk board
- Reserve crew
- Open-time / trip trading
- MEL — minimum equipment list
- AQP (14 CFR 121 App. Y)
- FA recurrent training
- Recurrent calendar
- Drug & alcohol random draws
- Aircraft program
- Cargo & ULD
- Live aircraft tracking
- Trip-sheet briefings
- Predictive maintenance
- Fleet utilization
- Manager daily digest
- Reports & exports
- Pilot dashboard
- Flight-attendant dashboard
- Crew planner & dispatch
- Manager & compliance
- Maintenance-station routingDev
- Crew-base efficiencyDev
- Weighted efficiency scoreDev
- Explainable swap / re-base suggestionsDev
+9 more supporting features lower on the page
Inside the Part 121 workspace
01Pilot bidding (LINE + PBS)
Monthly bid packages
Build a monthly package per base × equipment × position and move it through DRAFT → OPEN → CLOSED → AWARDED → PUBLISHED, so pilots, the crew desk, and the auditor all know exactly where the bid stands. Pilots bid from the portal; awards publish to them only once the package is PUBLISHED. It replaces the legacy PBS tool whose UI predates the smartphone.
Replaces: the legacy PBS tool whose UI predates the smartphone
- A monthly package per base × equipment × position
- DRAFT → OPEN → CLOSED → AWARDED → PUBLISHED
- Pilots bid from the portal; awards publish only when PUBLISHED
How an operator uses this
A crew planner's bid-close day
The monthly package closed overnight, so the crew planner opens it and runs the awards — a deterministic pass in seniority order, the same package and bids always producing the same lines. A correction comes in, so they re-run; the engine replaces the prior awards cleanly rather than stacking duplicates, and there's no spreadsheet to rebuild by hand.
FAR 117 flight-time caps are checked when a crew member is assigned to a specific trip or session — a crew assignment that would bust the checked caps is blocked at that moment — and flight attendants get the same assignment-time check on the 121.467 duty/rest regime. (The bid-award run itself, which builds pairings and lines, doesn't run a FAR 117/CBA legality check today — that's a scoped follow-up, not yet built.) Pilots without an awardable line fall to the reserve pool, tracked LONG_CALL and SHORT_CALL with callouts.
On the open-time board, a clean trade that creates no duty/rest violation auto-approves so the desk isn't a bottleneck, and an MEL deferral nearing expiry is already on the radar. When the package publishes, pilots see their awards in the portal — and every step is in the audit trail for the next inspection.
Illustrative — every screen reflects what's in your own data, nothing more.
Illustrative — every screen reflects your own data.
02Pilot bidding (LINE + PBS)
LINE + rule-based PBS
Run awards in classic LINE mode or rule-based PBS, processed in seniority order so the senior bidder is served first. PBS reads each pilot's hard and soft preferences from a generic rule catalog, and the same package and bids always yield the same lines. What you get is a fair, explainable award — not the mechanics of how it's computed. It replaces the regional incumbents that force LINE-only.
Replaces: the regional incumbents that force LINE-only
- Classic LINE mode or rule-based PBS
- Processed in seniority order — senior bidder served first
- The same package and bids always yield the same lines
Illustrative — every screen reflects your own data.
03Pilot bidding (LINE + PBS)
Idempotent award engine
The award run is a pure function: feed it the same package and bids and it produces the same lines every time, and re-running cleanly replaces the prior awards rather than stacking duplicates. So you can re-run after a correction without fear of drift. It replaces the spreadsheet the crew desk rebuilds and re-checks by hand.
Replaces: the spreadsheet the crew desk rebuilds and re-checks by hand
- A pure awards function — same inputs, same lines every time
- Re-running replaces prior awards instead of stacking duplicates
- Re-run after a correction without drift
Illustrative — every screen reflects your own data.
04Pilot bidding (LINE + PBS)
Crew pairing builder
Build and edit pairings line by line inside the package; pilots without an awardable line fall to a reserve pool. The pairings drive what each line actually flies. It replaces maintaining pairings in a document disconnected from the bid.
Replaces: maintaining pairings in a document disconnected from the bid
- Build and edit pairings line by line inside the package
- Pilots without an awardable line fall to a reserve pool
- Pairings drive what each line actually flies
Illustrative — every screen reflects your own data.
05Duty, rest & fatigue
FAR 117 enforcement
When a crew member is assigned to a trip or session, the checked flight-time caps are verified first, and an assignment that would bust them is blocked before it saves. This runs at crew-assignment time — the bid-award run that builds pairings and lines doesn't run this check today, so a legality bust in the award itself isn't caught here (a real gap, not yet built). The check is deterministic, so the same assignment always resolves the same way. It replaces FAR 117 legality checked by hand after the fact.
Replaces: FAR 117 legality checked by hand after the fact
- Flight-time caps checked at crew-assignment time
- A busting assignment is blocked before it saves
- Deterministic — the same assignment always resolves the same way
Illustrative — every screen reflects your own data.
06Duty, rest & fatigue
FAR 121.467 cabin-crew enforcer
Flight attendants get the same assignment-time duty/rest enforcement on the 121.467 regime that pilots get on 117, so cabin-crew legality is held to the same standard rather than tracked separately. It replaces the parallel FA duty spreadsheet.
Replaces: the parallel FA duty spreadsheet
- Assignment-time duty/rest enforcement for flight attendants
- The 121.467 regime, parallel to pilots' 117
- Cabin-crew legality held to the same standard, not tracked separately
Illustrative — every screen reflects your own data.
07Duty, rest & fatigue
Union / CBA contract overlay
Most pilot and flight-attendant contracts are stricter than the FAR minimums. Configure your bargaining unit's limits per crew group — minimum rest, maximum duty period, weekly time off, flight-time caps — and the scheduler enforces whichever binds tighter, the regulation or your contract. A contract value can only tighten a FAR limit, never relax it, and a booking that would violate the binding limit is blocked at the source like any other duty/rest bust.
- Per-crew-group limits: rest, duty period, weekly time off, flight-time caps
- The scheduler enforces whichever binds tighter — FAR or contract
- A contract value can only tighten a FAR limit, never relax it
Illustrative — every screen reflects your own data.
08Duty, rest & fatigue
Crew duty board
A live board shows each crew member's duty used, derived from their shifts and flight log, so the desk sees who's running out of legal duty before assigning the next trip. It replaces reconstructing duty totals from paper.
Replaces: reconstructing duty totals from paper
- Live duty used per crew member
- Derived from shifts and the flight log
- Who's running out of legal duty, before the next trip
Illustrative — every screen reflects your own data.
09Duty, rest & fatigue
Fatigue risk board
The fatigue risk board surfaces a per-crew risk view that blends documented duty load with each crew member's self-reported sleep and rest, and every score traces back to the inputs behind it. It is deterministic and explainable — there is no black-box prediction model. It replaces judging crew fatigue by gut feel on long rotations.
Replaces: judging crew fatigue by gut feel on long rotations
- Per-crew risk view from duty load plus self-reported sleep
- Every score traces back to its inputs
- Deterministic and explainable — no black-box prediction model
Illustrative — every screen reflects your own data.
10Reserve, open-time & MEL
Reserve crew
Track reserve crew as LONG_CALL and SHORT_CALL with callout and no-contact handling, so the desk knows who's available and who's been used. Reserve coverage lives in the same system as the lines it backs up. It replaces the reserve list kept on a separate sheet.
Replaces: the reserve list kept on a separate sheet
- Reserve tracked as LONG_CALL and SHORT_CALL
- Callout and no-contact handling
- Reserve coverage in the same system as the lines it backs up
Illustrative — every screen reflects your own data.
11Reserve, open-time & MEL
Open-time / trip trading
Pilots request drops, pickups, and swaps from the open-time board; a planner approves, and a trade that creates no duty/rest violation can auto-approve so the desk isn't a bottleneck on clean trades. Every trade still runs the legality check. It replaces trip trades negotiated over phone and email with no legality backstop.
Replaces: trip trades negotiated over phone and email with no legality backstop
- Drop / pickup / swap from the open-time board
- Planner approval; clean trades can auto-approve
- Every trade still runs the legality check
Illustrative — every screen reflects your own data.
12Reserve, open-time & MEL
MEL — minimum equipment list
Open a deferral against an MEL item and it tracks by category A/B/C/D with an auto-rolling expiry; an expired deferral raises a dispatch banner so the aircraft doesn't fly on a busted item. It replaces the MEL binder reconciled by hand.
Replaces: the MEL binder reconciled by hand
- Deferrals tracked by category A/B/C/D
- Auto-rolling expiry per deferral
- Expired item raises a dispatch banner
Illustrative — every screen reflects your own data.
13Qualifications & recurrent
AQP (14 CFR 121 App. Y)
Run an Advanced Qualification Program with per-fleet proficiency objectives and continuing-qualification enrollments tracked alongside the rest of crew records, so CQ status isn't in a separate tool. It replaces the standalone AQP tracker most carriers keep apart from scheduling.
Replaces: the standalone AQP tracker most carriers keep apart from scheduling
- Per-fleet proficiency objectives
- Continuing-qualification enrollments
- Tracked alongside the rest of crew records
Illustrative — every screen reflects your own data.
14Qualifications & recurrent
FA recurrent training
Flight-attendant training tracks the 121.421 categories — initial, recurrent, type-transition, and overwater — on their cycles, so cabin-crew qualification is held to the same visibility as pilots'. It replaces the FA training tracked on a separate spreadsheet.
Replaces: the FA training tracked on a separate spreadsheet
- 121.421 categories: initial, recurrent, type-transition, overwater
- Tracked on their cycles
- Cabin-crew qualification held to the same visibility as pilots'
Illustrative — every screen reflects your own data.
15Qualifications & recurrent
Recurrent calendar
A four-month grid lays credentials, FA recurrent training, and aircraft inspections on one calendar, so training and maintenance planning see the same upcoming wall of due dates. It replaces three separate calendars that never line up.
Replaces: three separate calendars that never line up
- Four-month grid on one calendar
- Credentials, FA recurrent training, and aircraft inspections together
- Training and maintenance planning see the same due dates
Illustrative — every screen reflects your own data.
16Qualifications & recurrent
Drug & alcohol random draws
Record random drug-and-alcohol selections with a full audit trail, so the program's draws are documented and defensible at audit. It replaces draw records kept loosely in a folder.
Replaces: draw records kept loosely in a folder
- Random drug-and-alcohol selection records
- A full audit trail per draw
- Documented and defensible at audit
Illustrative — every screen reflects your own data.
17Fleet, cargo & dispatch
Aircraft program
Each tail carries its Airworthiness Directives, Service Bulletins, and life-limited parts with inspection clocks, and the fleet view rolls up what's coming due. Airworthiness status stops living in a binder nobody fully trusts. It replaces AD/SB applicability tracked by hand.
Replaces: AD/SB applicability tracked by hand
- ADs, SBs, and life-limited parts with inspection clocks per tail
- Fleet view rolls up what's coming due
- Airworthiness status off the binder
Illustrative — every screen reflects your own data.
18Fleet, cargo & dispatch
Cargo & ULD
ULDs carry their IATA type and an inspection clock styled on AC 120-85's guidance (non-mandatory FAA practice, not a regulation; the cadence is operator-configurable), and the build-up manifest supports hazmat tags, so freight ops live in the same system as crew and fleet. It replaces a separate cargo tool and a clipboard for ULD inspections.
Replaces: a separate cargo tool and a clipboard for ULD inspections
- ULDs carry IATA type and an AC 120-85-styled inspection clock (non-mandatory guidance, operator-configurable cadence)
- Hazmat tags on the build-up manifest
- Freight ops in the same system as crew and fleet
Illustrative — every screen reflects your own data.
19Fleet, cargo & dispatch
Live aircraft tracking
Live position and ETA appear on the ops board via FlightAware's AeroAPI, using your own key — you bring the FlightAware subscription. It replaces calling for position updates.
Replaces: calling for position updates
- Live position and ETA on the ops board
- Via FlightAware's AeroAPI
- Bring your own AeroAPI key
Illustrative — every screen reflects your own data.
20Fleet, cargo & dispatch
Trip-sheet briefings
Generate a print-ready release with current METAR/TAF, NOTAMs, fuel, and a crew signature block, so the crew gets one assembled weather/NOTAM/fuel briefing instead of printouts from several sites. Pax count and cargo weight are captured on the same release, but CG isn't computed or envelope-checked here — that still runs in the dispatcher's own weight-and-balance process. It replaces the trip sheet rebuilt by hand per leg.
Replaces: the trip sheet rebuilt by hand per leg
- Print-ready release per leg
- Current METAR/TAF, NOTAMs, and fuel
- Pax/cargo weight captured — CG itself isn't computed on this page yet
Illustrative — every screen reflects your own data.
21Reliability & reporting
Predictive maintenance
Each tail gets a 0–100 aircraft-on-ground risk score that surfaces which aircraft to look at first, and every score is shown with the factors that contributed to it — airworthiness posture, inspection timing, utilization, and age. It is deterministic and explainable, not a black-box prediction: you see what drove the number, not a mystery output. It replaces guessing which tail is the next surprise AOG.
Replaces: guessing which tail is the next surprise AOG
- A 0–100 AOG-risk score per tail
- Shown with its factors: airworthiness, inspection timing, utilization, age
- Deterministic and explainable — not a black-box prediction
Illustrative — every screen reflects your own data.
22Reliability & reporting
Fleet utilization
Per-tail hours over 30 / 90 / 365 days sit next to an inspection countdown, so planners see which aircraft is overworked and which inspection is closest. It replaces the utilization tally done by hand each month.
Replaces: the utilization tally done by hand each month
- Per-tail hours over 30 / 90 / 365 days
- An inspection countdown alongside
- Which aircraft is overworked and which inspection is closest
Illustrative — every screen reflects your own data.
23Reliability & reporting
Manager daily digest
Managers get a morning email of today's operation and the items that need attention, so the day starts from a brief instead of a cold dashboard. It replaces piecing the morning picture together from several screens.
Replaces: piecing the morning picture together from several screens
- A morning email of today's operation
- The items that need attention
- The day starts from a brief, not a cold dashboard
Illustrative — every screen reflects your own data.
24Reliability & reporting
Reports & exports
Utilization, currency, and completion KPIs roll up across the operation and export to CSV for board packs or your own analysis. It replaces the month-end rebuild across disconnected tools.
Replaces: the month-end rebuild across disconnected tools
- Utilization, currency, and completion KPIs
- Rolled up across the operation
- CSV export for board packs or your own analysis
Illustrative — every screen reflects your own data.
25A dashboard for every seat
Pilot dashboard
When a pilot signs in they land on their own dashboard — not the company ops board. Next flights and duty/rest standing up top, a one-tap check-in to report for duty, their PBS bid (saved / submitted / awarded), a self-filling 61.51 logbook, and currency/credential expiry. Everything a line pilot needs, nothing they don't.
- Next flights and FAR 117 duty standing up top
- One-tap report-for-duty check-in and PBS bid status
- A self-filling 61.51 logbook plus currency/credential expiry
Illustrative — every screen reflects your own data.
26A dashboard for every seat
Flight-attendant dashboard
Flight attendants get their own home: upcoming trips and schedule, 121.421 recurrent-training status with expiry alerts, credentials, report-for-duty check-in, manuals, and a fatigue self-report — scoped to the operation, never mixed with the pilots' or managers' views.
- Upcoming trips and schedule
- 121.421 recurrent-training status with expiry alerts, plus credentials
- Check-in, manuals, and a fatigue self-report
Illustrative — every screen reflects your own data.
27A dashboard for every seat
Crew planner & dispatch
The crew desk and dispatchers run the operation from their own surfaces — build and award bid packages, manage reserve and open-time, and work the live ops / dispatch board — separate from what line crew see.
- Build and award bid packages
- Manage reserve and open-time
- Work the live ops / dispatch board
Illustrative — every screen reflects your own data.
28A dashboard for every seat
Manager & compliance
Managers and compliance staff get the run-the-business layer — fleet and recurrency, FAR 117 oversight, reports, and an audit-ready compliance trail — role-scoped and confined to the active Part, so an airline manager never wades through training-center screens.
- Fleet and recurrency plus FAR 117 oversight
- Reports and an audit-ready compliance trail
- Role-scoped and confined to the active Part
Illustrative — every screen reflects your own data.
29Network-aware scheduling In development
Maintenance-station routingIn development
As pairings and aircraft routing are built, the board checks each tail's next-due maintenance check against the stations that are both reachable and rated for that check, and flags any tail whose check won't fit a capable station before its limit. The at-risk chip surfaces on the routing view so the crew desk catches a stranded check while there's still time to swap the routing. It is advisory: it flags the risk on the board, it does not block or prevent a dispatch. It composes with — never replaces — the FAR 117 / 121.467 legality the scheduler already enforces at assignment time. It replaces discovering a misrouted check after the line is already flying.
Replaces: discovering a misrouted check after the line is already flying
- In development — will check each tail's due check against capable stations
- Advisory at-risk chip on the routing view — never blocks dispatch
- Composes with the FAR 117 / 121.467 legality the scheduler already enforces
Illustrative — every screen reflects your own data.
30Network-aware scheduling In development
Crew-base efficiencyIn development
Pairings are scored against your crew bases, surfacing deadhead legs and out-of-base overnights, so the desk can favor pairings that begin and end at a crew member's domicile and feed that into the bidding award run. It replaces judging which pairings strand crew away from base by reading the lines one at a time.
Replaces: judging which pairings strand crew away from base by reading the lines one at a time
- In development — will score pairings against your crew bases
- Surfaces deadhead legs and out-of-base overnights
- Favors pairings that begin and end at a crew member's base
Illustrative — every screen reflects your own data.
31Network-aware scheduling In development
Weighted efficiency scoreIn development
The board rolls the soft factors — deadhead legs, out-of-base overnights, aircraft repositioning, and maintenance-fit slack — into a single weighted score, shown as abstract points where lower is better. The weights are configurable per center, so the operation decides what to optimize; the score is a planning signal, not a dollar figure. It replaces comparing pairing constructions by gut feel.
Replaces: comparing pairing constructions by gut feel
- In development — will roll soft factors into one weighted score
- Abstract points, lower is better; weights configurable per center
- A planning signal, not a dollar figure
Illustrative — every screen reflects your own data.
32Network-aware scheduling In development
Explainable swap / re-base suggestionsIn development
When an aircraft swap or a re-base would lower the efficiency score without creating a maintenance-routing risk, the board proposes it and shows the reasoning behind it — what it changes and how many points it saves. The suggestions are deterministic and explainable heuristics: the same inputs always produce the same proposals, and each one traces back to its inputs. They are not AI, not a solver, and not a claim of the single optimal schedule — they are ranked, transparent improvements you choose to apply. It replaces rebuilding pairings by hand just to test whether a change helps.
Replaces: rebuilding pairings by hand just to test whether a change helps
- In development — will propose swaps and re-bases that lower the score
- Every suggestion shows its reasoning and traces to its inputs
- Deterministic, not AI and not a guaranteed optimum
Illustrative — every screen reflects your own data.
In every operation
The platform backbone, under every Part
The platform-wide backbone — the same under every FAR Part.
Auto-fills from completed flights, manual entry, and ForeFlight CSV import/export.
Certificates, ratings, medicals, and type ratings with auto-expiry alerts and document storage.
Priority/status/assignee work orders, parts with reorder thresholds, vendors, and purchase orders.
Every requirement on a Compliant → Due-Soon → Overdue timeline with a weekly admin digest.
Utilization, currency, and activity KPIs with CSV export.
Every mutation recorded with actor, entity, and timestamp — searchable and exportable.
Read-only links for FAA/POI/external auditors that expire automatically — no shared logins.
Bearer-token REST API (scoped) and HMAC-signed outbound webhooks for HRIS, ERP, and ops integrations.
Tenant isolation, role-based access, per-employee surface restrictions, TOTP 2FA, and GDPR data export/erasure.
Today
What's slowing you down
- Bidding run in a legacy PBS tool whose UI predates the smartphone
- Reserve and open-time tracked in a spreadsheet the crew desk rebuilds nightly
- FAR 117 legality checked by hand, after the line is already built
With AviationAlley
What changes
- One workspace for bidding, reserve, open-time, and MEL
- FAR 117 flight-time caps checked at crew-assignment time
- Award runs are idempotent — the same inputs always produce the same lines
Why operators switch
What we have. What incumbents don't.
| AviationAlley | Status quo |
|---|---|
| Modern PBS UI built this decade | Legacy crew suites (CrewTrac-era) carry decades-old UIs |
| LINE and rule-based PBS modes | Many regional incumbents force LINE-only |
| Public REST API + signed webhooks | Bespoke integrations, multi-month engagements |
| Modular by FAR — pay for what you use | Monolithic suites; pay for unused modules |
Recommended for Part 121
Enterprise plan
Unlimited seats · priced to your fleet
Every module — Part 121 pilot bidding, AQP, multi-base. For regional carriers and multi-center training networks.
- All operation modules
- Full PBS with the contract rule library
- Multi-base + AQP
- Per-center white-label
- Dedicated customer success manager
Frequently asked questions
Part 121 — common questions
Does AviationAlley do PBS pilot bidding for Part 121?+
Yes. Bidding runs in classic LINE mode or rule-based PBS, processed in seniority order, with monthly packages per base × equipment × position. The award run is deterministic — the same package and bids always produce the same lines — and pilots bid from the portal.
Is the bidding award deterministic and re-runnable?+
Yes. The award engine is a pure function: the same package and bids always produce the same lines, and re-running cleanly replaces the prior awards rather than stacking duplicates — so you can re-run after a correction without drift.
Is FAR 117 enforced before a bid-award pairing is built?+
Not today. Flight-time caps are checked at crew-assignment time — when a specific crew member is assigned to a trip or session — and a busting assignment is blocked at that point. The bid-award run that builds pairings and lines doesn't run this check yet; wiring legality into the award step is a scoped follow-up, not yet built. Flight attendants get the same assignment-time enforcement on the FAR 121.467 regime.
Does AviationAlley predict fatigue with AI?+
No. The fatigue risk board is deterministic and explainable — it blends documented duty load with crew members' self-reported sleep, and every score traces back to its inputs. There is no black-box prediction model.
Does it handle reserve, open-time, and MEL too?+
Yes. Reserve crew tracks LONG_CALL / SHORT_CALL with callouts, open-time supports drop / pickup / swap (a clean trade with no duty/rest violation can auto-approve), and MEL deferrals track by category A/B/C/D with auto-rolling expiry — an expired item raises a dispatch banner.
Built for Part 121.
See it on your operation. Request a demo or join the waitlist.