Fatigue Risk Self-Assessment Checklist

Before the threshold, not at it: the regulatory architecture (117.5's fitness obligation, EASA's equivalent) makes the crew member the final sensor, and the working test is brutal and simple — would you let a colleague operate in your current state? Early calls are scheduling problems solved by reserves; late calls are continued duties flown by someone whose own judgement is the impaired instrument. Non-punitive fatigue policies exist precisely because the alternative is crews hiding the one risk no system can see from outside.

They're the working flags fatigue-risk systems converge on: under six hours of sleep in the last 24, or twelve in the last 48, performance degradation is reliably measurable — reaction time, working memory and risk assessment all slide, with the cruel feature that self-assessment degrades alongside. Below the thresholds, the burden of proof flips: assume impairment and look for disconfirming evidence, not the reverse. That's why this checklist asks the sleep questions first and numerically.

Only you. Entries live in your browser's local storage and never leave your device, so there is no account, no cloud sync and no one else with access. Because the data is device-local, export a CSV backup before clearing browser data or switching computers.

A plain CSV with one row per entry and labelled column headers — the most portable format there is. Spreadsheets open it directly, most specialised software can map it on import, and a printed copy is perfectly legible to a human reviewer. Nothing proprietary means your assessment record is never trapped here.