Crew control desk
The week’s coverage, the gaps to fill with candidates ranked by FTL, the pairing generator from the OPS flights and roster publication, on one screen.

AMASFLY Crew
Crew
AMASFLY Crew builds, checks and publishes the roster of your crews: every assignment goes through the FTL engine before it is saved, and the crew member acknowledges it from their calendar.

Covering pairings with legal crew, publishing with proof and reacting when the day changes is often manual work. Crew puts legality inside the flow.
Pairings are generated by hand or with the generator and checked duty by duty with the FTL engine. An FTL block is not saved.
Every publication has an immutable version and shows the difference with the previous one. The crew member acknowledges it, and control can record the acknowledgement by phone, in person or by message.
After a delay, a cancellation or an AOG, tracking calculates who is at risk and which connections break, and proposes solutions. Always as proposals: nothing changes on its own.
The week’s coverage, the gaps to fill with candidates ranked by FTL, the pairing generator from the OPS flights and roster publication, on one screen.

The regulation is the floor and your airline’s OM-A can be stricter: the most restrictive value always applies. Each version of the scheme is immutable, with an effective date and a log, and you can see its impact before applying it.

Each crew member sees their next duty, the month and the week, their expiries, and requests leave or a duty change. It is a calendar of its own inside the portal; it is not exported to iCal.

The base FTL profiles (RAB, EASA and FAA) are adjusted and validated with each operator before a real roster is published.
Crew shares its account and flights with OPS and the SMS, and reaches the crew’s iPad and iPhone. Each connection is switched on per organization.
You sign in to Crew with your SMS account, through single sign-on.
Crew reads the flights and catalogs from OPS and re-checks FTL when OPS edits a flight.
The published roster, the calendar and the crew member’s notices reach the EFB app, with push notifications.
The approved candidate will arrive in “Pending onboarding” and control will confirm it. The step is built and will be switched on as each airline agrees.
Each connection is switched on per organization, as agreed with your airline.
Crew shares its platform with OPS: it runs on the Cloudflare cloud and is used from the browser.
The FTL engine is deterministic. Every finding carries the article, the value, the limit and the severity, and what the regulation does not cover shows as “no rule”: a value is never invented.
Roles for crew control, planning, chief pilots and chief cabin crew, and crew member. A crew member sees only their own roster and what is general.
FTL checks, publications, acknowledgements and standby calls are kept in immutable records.
The organization comes from the membership and queries are scoped to it, with automated isolation tests. Access is by invitation and sign-in limits attempts.
Demo Airlines has 68 fictitious crew members and sample flights. We show you the roster, the control desk and the crew member calendar with them.
Demo accounts are handed over in the meeting.
crew.amasfly.net
The Demo Airlines rosters and pairings.
Tell us how you schedule your crews today and which FTL scheme your airline applies. It is contracted per airline, tailored to your operation.
You can also write to info@amasfly.com or reach us on WhatsApp at +591 69374523.