Make the roster
the easy part.
AuroraCrew builds a legal month of flying for every crew member. Flight duty periods, rest, consecutive days, fleet ratings and licence currency are all enforced while the roster is being written, not audited afterwards.
One sign-in for crew, scheduling, operations control and department heads.
A month of legality, at a glance.
Every seat on every flight, every rest period, every day off. One grid the whole operation reads.
| Crew | 01 | 02 | 03 | 04 | 05 | 06 | 07 | 08 |
|---|---|---|---|---|---|---|---|---|
| CAP · 4471 | 101 | 102 | OFF | OFF | 104 | 105 | SBY | 303 |
| CAP · 3902 | SBY | 201 | 202 | DH | OFF | OFF | 301 | 302 |
| FO · 5518 | 101 | 102 | 304 | OFF | SBY | 104 | DH | OFF |
| FA · 2260 | OFF | 201 | 202 | 203 | 204 | OFF | SBY | 303 |
| FA · 7134 | 301 | OFF | OFF | 101 | 102 | DH | 105 | 304 |
Then the day, tail by tail.
Routes, times and aircraft are edited as one day. Every change is re-checked against the rotation before it reaches anyone, and what doesn't hold up says so.
| Flight | Dep | Arr | Block | Aircraft | Status |
|---|---|---|---|---|---|
| 101 | 06:15 | 07:15 | 1:00 | Aircraft 1 787 | Assigned |
| 201 INTL | 07:00 | 08:30 | 1:30 | Aircraft 2 777 | Assigned |
| 102 | 08:15 | 09:20 | 1:05 | Aircraft 1 787 | Assigned |
| 301 | 09:00 | 09:50 | 0:50 | Aircraft 3 737 | Assigned |
| 202 INTL | 09:30 | 11:00 | 1:30 | Aircraft 2 777 | Assigned |
| 302 | 10:40 | 11:30 | 0:50 | Aircraft 3 737 | Assigned |
| 203 | 11:20 | 12:50 | 1:30 | Aircraft 2 777 | Turnaround 20m |
| 304 | 17:10 | 18:00 | 0:50 | Not assigned | No aircraft |
And when it breaks, one queue.
Delays, unstarted post-flight reports and half-finished ones collect in a single list, ordered by priority and then by how long each has been waiting. Nothing gets chased from memory.
- Overdue 104 Post-flight report not started · landed 14:30 2h 05m Log report
- Delay 203 Delay unresolved · 40 min 3h 35m Update delay
- Incomplete 202 9 fields remaining · 24 of 33 5h 35m Continue
- Incomplete 302 4 fields remaining · 29 of 33 5h 05m Continue
- Ready 303 Flight landed · ready for report 15m Log report
What it does
Three jobs, one platform, one dataset.
Builds the roster
A duty-aware assigner fills a whole month: pairing legs into duties, positioning crew as passengers when they need to be somewhere else, and calling standby only as a last resort. It will not produce an assignment that breaks a rule, so there is nothing to clean up afterwards.
- FDP banded by report time and sector count
- Rest minimum overnight, both directions
- Limits consecutive days, legs per day, monthly block
- Ratings fleet type, international training, currency
Runs the day
A live board of every aircraft and flight, with delays logged against the schedule they actually broke. Post-flight recording covers fuel, times and load; the roster is re-checked against the delayed times, so a late arrival that breaks tomorrow's rest is raised while it can still be fixed.
- Timeline tail by tail, scheduled against actual
- Delays IATA-coded, with knock-on retiming
- Post-flight fuel, block, load, invoices
- Export operations workbooks that reconcile
Reaches the crew
Crew see their own month on their phone, request days off, swap with a named colleague, and sign in for duty. Roster changes settle before they send, so a morning of edits arrives as one summary rather than nine notifications, and the scheduler can see who has acknowledged it.
- Push duty reminders, day-ahead heads-up
- Requests days off and crew-to-crew swaps
- Documents licence, medical and passport expiry
- Offline installs to the home screen
Evaluating it for an airline?
The full platform breakdown is on the overview page: the seven operational roles, the compliance model, security posture, and how it deploys.
Talk to us.
Evaluating AuroraCrew for an airline, want a walkthrough, or have a question about the platform? Send a message; it reaches the operations team directly.
Messages are delivered inside AuroraCrew itself, so there is no inbox to miss.