View your trip and leg details

Opening a trip from your schedule takes you to its detail screen — the trip summary, your assignment(s), the rest of the crew, and every leg.

Steps

1. Read the trip summary. At the top: the trip id, its overall route (first leg's origin to last leg's destination), and a leg count — how many legs total, how many already flown, how many remaining.
2. Add the trip to your calendar, if you want. The Add to calendar button exports the trip's legs as an .ics file and hands it to your device's share sheet — fully offline, built from the legs already cached on your device. It's disabled with an explanation if no leg has a scheduled time yet.
3. Acknowledge or decline your assignment. See acknowledge or decline an assignment — the buttons live right here, next to your role and report time.
4. See who else is on the trip. The crew roster lists every active assignment on the trip (PIC/SIC/FA), read-only. The mobile app has no crew name directory, so each crew member shows by their identity and role, not a display name.
5. Read each leg's details. For each leg you get: origin → destination, a route map (a real prefetched map image when one is cached, otherwise a schematic route strip — never a broken image), the scheduled departure time, tail number, passenger count, and a live weather glance for both airports pulled from public METAR data. If you're crewing as FA, catering notes and special requests also show.
6. Check the passenger manifest, if available. When the leg carries a named manifest, it lists each passenger; otherwise you just get the headcount — the app never invents names it doesn't have.
7. Log a completed leg to your logbook in one tap. Once a leg is flown (completed/closed), a Log this leg button appears on it. It jumps you into the logbook entry form with from/to, tail, your role, and block minutes already filled in from the leg — you still confirm before it saves.
8. Ping dispatch if you're running late. The Ping dispatch section at the bottom lets you send On my way, Running late, or Unable with one tap. Like acknowledging an assignment, this is queued locally first and synced when you have a connection — it is never silently dropped, and the app never claims dispatch received it until the send actually succeeds.