One platform for your whole aviation operation.

AviationAlley is an all-in-one operations platform for aviation — one workspace that runs simulator scheduling, NSP and FAR compliance, training records, pilot logbooks, crew bidding and duty/rest, dispatch, parts and work orders, billing, and audit trails. It replaces the spreadsheets, whiteboards, and disconnected tools an operation otherwise stitches together, and the workspace scopes to whichever operation you're in.

AviationAlley is for operators across the FAR Parts — Part 142 training centers, Part 141 flight schools, Part 61 instructors, Part 135 charter, Part 121 airlines, Part 91 corporate flight departments, Part 107 drone operators, helicopter HEMS, and more. Owners, directors of operations and training, schedulers, dispatchers, instructors, pilots, and maintenance leads each get the surfaces their role needs.

No. Part 142 is one of twelve FAR-Part operations the platform runs. You turn on the modules for the Parts you operate — a 142 training center, a 121 airline, a 135 charter, a 91 flight department, or any combination — and the nav and data scope to the active operation. An operation that adds a new Part adds a module instead of switching tools.

The platform splits into FAR-Part modules (PART_142, PART_141, PART_135, PART_121, PART_91, PART_107, and so on) plus cross-cutting add-ons like AQP and the DPE Network. You enable the modules your operation needs; the sidebar hides what you don't run, so a single-rule school never sees airline crew bidding and an airline never misses it. Modules are tied to your plan, not toggled ad hoc, so the source of truth stays on billing.

Every regulatory and recurring requirement sits on one Compliant → Due-Soon → Overdue → In-Progress → Waived timeline, whatever the Part. A 142 center tracks Part 60 NSP evaluation cycles; a 121 carrier checks FAR 117 duty/rest before a pairing posts; a 135 operator watches crew currency and MEL deferrals. A weekly digest emails admins and managers what's overdue and what's coming due so nothing surprises you before an audit.

Yes. For Part 142 / Part 60 operations, NSP evaluations are first-class records: per simulator you log the evaluation date, evaluator name and organization, result, findings, corrective actions, and the next due date — and logging an evaluation rolls the next-due date forward. The Reports page shows your overall NSP pass rate alongside compliance health by category.

Yes. Part 121 operators get seniority-ordered pilot bidding in LINE or rule-based PBS mode with deterministic, re-runnable awards, plus reserve, open-time trip trading, and MEL. FAR 117 duty/rest is checked at assignment time and a violation is blocked before a pairing posts; flight attendants get the same assignment-time enforcement on the FAR 121.467 regime.

Yes. Part 135 charter operators get dispatch, printable trip-sheet briefings, crew currency and duty, MEL, cargo/ULD, and card/ACH billing. Part 91 flight departments get aircraft and crew scheduling, the aircraft program with AD/SB tracking, credentials, and the 61.51 logbook today — with flight planning, weight & balance, and weather briefing in development, targeted for Q1 2027.

Yes. Trainees get a secure portal link (no login required) showing upcoming sessions, program progress, endorsements, and medical-expiry warnings. Pilots and flight attendants get focused workspaces for schedule, duty, credentials, and logbook. B2B client managers — an airline training department or a charter chief pilot — get an org portal with their pilots' schedules, currency, and invoices.

Pricing is tailored to your operation — the simulators or aircraft you track and the modules you turn on — so we set it with you rather than posting a one-size number. Seats are always unlimited: every staff member you want in the system is included. The best next step is a short demo, where we'll walk through a plan that fits your operation (and a 30-day free trial is available once you're set up).

Every record is scoped to a single workspace and filtered by the active operation on the server, so data never crosses tenant boundaries. Access is gated by role — from Owner and Admin down to a read-only Auditor, with operational roles like Scheduler, Dispatcher, Instructor, Pilot, and Maintenance in between — and managers can narrow an individual employee to specific operations and hide specific surfaces on top of their role. TOTP two-factor and GDPR data export/erasure are built in.

Yes. You can grant an FAA POI/PMI or an outside auditor a read-only invite that expires on its own — no shared login and no manual cleanup. Their view is scoped to the records they need, and what they looked at lands in your audit trail, where every change records who did it, what changed, and when.

Yes. The compliance digest emails Owners, Admins, and Managers a summary of overdue items, items due soon, and upcoming evaluations or expiries. Operators can trigger the digest manually from Settings, or rely on the scheduled run each Monday morning. The same alerting drives credential-expiry and recurrent-training reminders.

AviationAlley is delivered as U.S.-hosted web software with no on-site install, so it works wherever you operate. The compliance surfaces are built around the U.S. FAR rule sets, but the operations features — scheduling, training records, parts, work orders, dispatch, and portals — are jurisdiction-agnostic, so operators under equivalent frameworks (for example EASA-approved training organisations) can use them the same way.

Yes. Admins mint scoped API keys from the Integrations settings — each key carries only the scopes you grant (trainees, bookings, work orders, invoices, compliance, flight log, crew, and more), is shown exactly once at creation and stored only as a hash, and is rate-limited, expirable, and revocable. The REST API serves your operation's data over those keys, and outbound webhooks push operational events — bookings, work orders, invoices, trainees, compliance due-soon/overdue, and others — to your endpoints as HMAC-SHA256-signed POSTs, with every delivery attempt logged so you can see exactly what was sent and what your endpoint answered. Developer docs live at /docs/api and /docs/webhooks.

Yes. Every pilot gets a personal 61.51-style flight logbook built to log completed sessions automatically — PIC, SIC, dual given, and dual received bucketed from the crew seat — so nobody enters flight time twice. A sync panel backfills any flown-but-unlogged sessions in one click. The logbook also round-trips with ForeFlight: bring an existing logbook in from a ForeFlight-compatible CSV (duplicates are detected on import), and export yours as a ForeFlight-importable CSV anytime.

Yes — for simulators and aircraft alike. Work orders carry priority and a full status lifecycle (including awaiting-parts), can be assigned to a staff member, and record the parts consumed with the unit cost captured at the time of use. The parts inventory tracks stock against a per-part minimum so low stock surfaces before it grounds a session, with vendors and purchase orders managed alongside. On the aircraft side, each tail's program tracks ADs and SBs and counts down inspections by calendar days or flight hours, and MEL deferrals compute their expiry from the deferral category and surface as they approach it.

Yes. Every booking you create or edit is checked before it posts, on four fronts: the simulator's own window, the instructor's other sessions on any device, the instructor's approved time off, and any blackout — per-simulator or facility-wide. A conflict blocks the save with a plain-language message saying exactly what's in the way, and the same check re-runs when a booking is edited, so a fix never creates a new clash. Because training sessions, check rides, maintenance windows, and NSP evaluations all live on the same calendar, a maintenance block protects its slot exactly like a session does — and a cancelled booking frees its slot automatically.