ProblemWhat it solves
The problem this tool solves
Pilots who self-track duty/rest had no way to recall their logged periods mid-chat. This surfaces the open period and recent history, honestly reporting "no log" when nothing is entered — distinct from dispatcher-side getDutyOutlook and caller-input getCrewRestRequirements.
Example interaction
Pilot asks
What duty periods have I logged this week?
Copilot responds
Open period since 0600Z under §135.267 (FDP 4.2 h so far). 3 closed periods in the last 14 days. Self-logged and advisory — verify against your operator’s duty/rest program.
RegulationCited reference
Related FAR
14 CFR 135.267
Related features
Where this tool surfaces in the product.
Duty & Rest self-tracking
Try getSelfLoggedDutyStatus in the Copilot
The Copilot reaches for this tool whenever the conversation calls for it.