A Fatigue Risk management system which allows for accurate effectiveness monitoring throughout the duty, together with various advisories, using the PSWM and SAFTE models.
- The ability to define rest periods
- Duty with in-flight rest capability
- Minute-by-minute chart with SAFTE task effectiveness score
- Predictive sleep-wake-model risk categories
Requirements
- Node.js 22+
Run npm install then npm run dev.
The app will be served on localhost:5173 by default.
The SAFTE model models a sleep reservoir with 2880 units (enough for 4 days of continuous wakefulness) as a baseline amount. Every minute awake sleep units are depleted.
Based on the circadian rhythm, sleep propensity and sleep intensity values are updated.
Sleep intensity is also updated by the level of sleep units in the sleep reservoir.
When asleep, the sleep units are increased based on the sleep intensity and propensity. This is all fed into a calculations that calculates the estimated task effectiveness (cognitive) while performing any given task.
The default (for now hardcoded) critical level is 70% which has been shown to exhibit a level of impairement comparable to an BAC (blood alchol level) of 0.08%, which is above the legal driving limit in many jurisdictions.
The model is the one suggested at GM5 CS FTL.1.205 - EASA Rules for Air Operations
This project was created as a free and open-source FRMS that is open for real-world use. I originally developed it for home simulator use, however its algorithms are derived for real-world certified FRMS programs, so it can be used in real-life as well. Do note that I am not responsible for any damages caused by real-life usage of this program.
It is mostly in final form, but will recieve updates from time-to-time. Any feature requests would be highly appreciated.
Current expected roadmap:
- Loaded roster nodes should be viewable as a calendar/day view
- Points where fatigue drops below critical points should be listed
- Handle multiple duties by listing each duty risk.
This project is open to all contributions to improve the project. Before adding any PRs, create relevant issues to demonstrate the need of a particular feature.
Branching conventions are:
fix/{fix}
feat/{feature}
{feature}
{fix}