How to log a rest period in DaPilot

Rest periods are how DaPilot tells whether you've had your §117.25 weekly rest, your pre-FDP rest, and your §117.3 qualifying rest for acclimation. Logging takes about thirty seconds per rest. The fields are minimal but they matter.

Why this matters

The pre-FDP rest card and the §117.25 weekly-rest card both read the rest record. Without rest periods logged, those cards show "missing data" and the rolling windows operate without context.

For most pilots the rule of thumb is: log a rest after every FDP, and log the long rest at home that satisfies §117.25 every 168 hours.

What you need

Airline Mode enabled.
The actual start and end times of the rest period.
Knowledge of whether the rest crossed your physiological night (defined by §117.3) and your acclimation state during the rest.

The rest period form

1Tap the plus button → Rest period

On the dashboard, tap plus, pick Rest period.

2Enter start and end times

Both default to UTC.

Start: when the rest period began. Most carriers consider this the release time of the previous FDP.
End: when the rest period ended (typically the report time of the next FDP).

If there was no FDP before the rest (e.g., the start of a trip after a few days off), start the rest at the moment your last off-duty period began. If there's no FDP after (e.g., the trip is over and you're going home), the end is whenever you choose to close the entry.

3Mark physiological-night status

Toggle Physiological night if the rest period included the window from 0100 to 0700 in your acclimated time zone (the §117.3 definition). Most overnight rests at home or on a layover with your bedtime in the local zone hit this. A daytime rest between morning and afternoon FDPs does not.

The physiological-night flag matters for several Appendix B and §117.X calculations. DaPilot does not auto-detect it from the start and end times because it depends on which time zone you were acclimated to.

4Set acclimation state

Same options as the FDP form: Acclimated, Not acclimated, Acclimated elsewhere. The acclimation state during the rest determines which time zone DaPilot uses to evaluate the physiological-night window.

5Add a note (optional)

A free-form remarks field for context: hotel name, sleep quality, anything you might want to remember when you read it back.

6Save

Tap Save. The rest appears on the duty list. The §117.25 weekly-rest card and any pending pre-FDP rest comparison refresh.

What DaPilot computes

Pre-FDP rest

When you save a rest period, DaPilot looks at the next FDP that started after the rest ended. The duration of the rest, plus the physiological-night flag and acclimation, feed the pre-FDP rest comparison on that FDP's card.

If the rest is too short, the FDP card surfaces the §117.X paragraph that requires a longer minimum rest given your acclimation state. The pilot is the decider; DaPilot shows the math.

Weekly mandatory rest (§117.25)

The §117.25 card on the dashboard scans rest periods within the trailing 168 hours and finds the longest single rest. If at least one rest is 30 consecutive hours or longer, the card is satisfied. If not, the card shows the longest rest you had and how much further you'd need.

§117.25 is "30 consecutive hours of rest in any 168 hours," and "consecutive" matters. DaPilot computes the consecutive duration of each rest record and uses the longest. If you're on a trip where you have multiple short rests but no single 30+ hour block, the card flags it.

For backups: the rest list on the dashboard exports cleanly via Settings → Export. Useful if your operator ever asks for a personal rest log to corroborate something on a roster trade.

Last updated April 27, 2026 · 6 min read