Overview
Every duty.
One place.
Your flying life, organised — from the next report to your career history.
At a glance
Stored on this deviceNext assignment
Quick actions
My roster
Your upcoming duties and imported calendar entries. Imported entries always require review.
Duty preparation
Your working position
Set a personal working-position label for your next duty. This does not assign official responsibilities.
Personal preparation list
Customise these reminders to your own routine. Do not enter confidential or safety-critical company procedures.
Service workspace
A personal, airline-neutral service record inspired by the original Crew Assist workflows. No airline menu, emergency procedure or passenger identity data is included.
Service workspace
Flight workspace
Orders and personal preparation tasks are stored separately for each selected duty. Select a duty to begin.
Cabin seat layout
Create a basic seat grid for your selected duty. This is an editable personal layout, not an official aircraft seat map.
Seat-based orders
Galley preparation
Service Summary
Flightbook
A personal record of your flying history. Scheduled duties don't count as completed flights.
Rest & Fatigue
Career overview
Calculated only from completed flight records stored on this device.
Most flown routes
Recorded rest totals
Geographic route map and advanced charts will follow after the underlying records and import engine are validated.
Import & protect your records
Calendar import (.ics)
Import a calendar export from your roster or calendar provider. Events are previewed before being added.
Roster CSV import
Upload a CSV with headers flight, from, to, startUTC and optional endUTC. Use ISO dates with Z or a UTC offset; review before saving.
Backup & restore
Export all your Crew Atlas records to a JSON file and keep it somewhere safe. Clearing this browser's data can delete local records.
Privacy & account status
Your data currently stays in this browser. There is no cloud account, automatic backup or cross-device synchronisation in v0.5.1. These require secure backend implementation and testing before release.