Schedule
Connect the crew calendar once. Family sees days, cities, and the pairing — not a guess from memory.
For crew families
You shouldn’t have to guess when you can call.
The published trip, said plainly. Where crew are. When a call is likely. When they’re coming home.
The problem
Pairings move. Families shouldn’t have to decode them.
Layovers shift. Last legs slip. People at home need the published plan — not a hallway screenshot.
What the app does
Three things. Said plainly.
Live context
Reachability comes from the crew phone. If it can’t reach the network, we don’t pretend it did.
Getting Home
Last duty, a commute option, and the drive. We estimate the door. Not a ticket. Not a jumpseat. Not a seat for sale.
On the trip vs family
Same trip. Two jobs.
Pilot and crew
Connect the calendar. Approve who follows. The phone publishes the trip when it can. Family sees that — not the rest of the calendar.
Family
Open the trip. Day, layover, and whether a call is likely. No seat maps. No airline logos. No tail numbers.
What we never claim
We do not over-claim.
Updates arrive when the crew phone can reach the network. A locked bag is silent.
A scheduled commute is a possibility. Not a booking. Not a jumpseat.
No carrier branding. No seat maps. No real tail numbers. The family sees the plan.