Part 142 · Simulator & scheduling
Conflict-free calendar
Book a session in two clicks against a week view with one column per device; briefing and debrief blocks are built into the booking so the calendar reflects the real bay time, not just the sim run. Double-booking a device is flagged the moment it would happen instead of being discovered at 6 a.m. It replaces the shared spreadsheet two schedulers edit at once.
Launching the first quarter of 2027.
Illustrative — every screen reflects your own data.
Who it's for
Schedulers at a Part 142 center who book the day across multiple devices and need the calendar to reflect real bay time, not just the sim run.
What it replaces
The shared scheduling spreadsheet two schedulers edit at once, where a double-booking only surfaces the morning the crew shows up.
What conflict-free calendar gives you
- Week view with one column per device
- Briefing + debrief blocks built into every booking
- Double-bookings flagged before they post
A week view, one column per device
A scheduler works the day against a week view with one column per device and books a session in two clicks. Briefing and debrief blocks are built into each booking, so the calendar shows the real bay time a session occupies rather than just the sim run.
- Week view with one column per device
- Briefing + debrief blocks built into every booking
Conflicts caught before they post
If a booking would double-book a device, it's flagged the moment it would happen — not discovered at 6 a.m. when the first crew arrives. The conflict surfaces before the booking posts, so the day is laid out cleanly instead of being untangled on the floor.
- Double-bookings flagged before they post
- Caught the moment a conflict would happen, not the morning of
How an operator uses this
A scheduler works the day against a week view with one column per device, booking a session in two clicks. Briefing and debrief blocks are built into each booking, so the calendar shows the real bay time rather than just the sim run. If a booking would double-book a device, it's flagged the moment it would happen — not discovered at 6 a.m. when the first crew shows up.
Illustrative — every screen reflects what's in your own data, nothing more.
How it works
Conflict-free calendar, step by step
Open the week view, where each device gets its own column.
Book a session in two clicks; the briefing and debrief blocks are built into the booking automatically.
If the booking would collide with another on the same device, it's flagged before it posts.
Read the calendar as real bay time — sim run plus brief and debrief — instead of just the device hour.
Questions
Conflict-free calendar — frequently asked
Does the schedule account for briefing and debrief time?
Yes. Briefing and debrief blocks are built into every booking, so the calendar reflects the real bay time a session occupies, not just the sim run.
When are double-bookings caught?
The moment they would happen. A conflict on a device is flagged before the booking posts, instead of being discovered the morning of.
Keep exploring
Other features in Part 142
Device inventory
FFS Level A–D and FTD with Part 60 qualification levels; AATD and BATD tracked by their LOA instead.
Deep diveUtilization reporting
Per-sim hours, sessions, and by-type breakdown — no month-end rebuild.
Deep diveNSP evaluation cycles
Each device's recurring Part 60 eval auto-rolls its next-due date with 30/60-day reminders.
Deep diveInstructor currency
Per-instructor CFI / CFII / ATP currency on the Due-Soon → Overdue pipeline.
Deep diveFAA inspection mode
Read-only navigation for a POI/PMI visit, scoped to the records they need.
Deep diveTS document control
Sections (A001 / A002 / B055 …) with DRAFT → PROPOSED → APPROVED and POI sign-off captured; append-only revision log.
Deep diveInstructor authorization matrix
Who's authorized on which course on which device — every sign-off an audited event.
Deep diveFAA Form 8710 / IACRA prep
Pre-fills from completed training records; CSV export ready for IACRA upload.
Deep diveAQP (14 CFR 121 App. Y)
Per-fleet proficiency objectives and CQ-cycle tracking (add-on module).
Deep diveEvery Part 142 workspace also includes the platform-wide backbone — logbook, credentials, compliance, reporting, and audit trail.
See the backboneSee conflict-free calendar on your operation.
It's part of the Part 142 workspace. Request a demo or join the waitlist.