Fatigue Safety Action Group

Fatigue Safety Action Group (FSAG): Practical Roles, Responsibilities and Review Periods

SAFEJETS Knowledge Team Author
February 23, 2026
Share

Fatigue is a persistent safety risk in aviation that affects decision-making, attention and performance. A Fatigue Safety Action Group (FSAG) is a focused working group inside an operator’s Safety Management System (SMS) that identifies fatigue hazards, evaluates data, and drives corrective actions. This article explains what an FSAG does, who should be involved, and how often it should meet and report. The guidance is practical and aligned with international expectations such as ICAO guidance and regional rules like EASA Flight and Duty Time limitations (Regulation (EU) No 83/2014) and FAA 14 CFR Part 117. Use the steps below to set up a strong FSAG that supports compliance and improves operational safety.

Purpose and core responsibilities of an Fatigue Safety Action Group (FSAG)

An Fatigue Safety Action Group (FSAG) focuses on reducing fatigue-related risk through monitoring, analysis and mitigation. Its core responsibilities include collecting and reviewing fatigue reports, analysing duty patterns and sleep opportunity data, assessing operational changes that may increase fatigue risk, and recommending roster or policy changes. The group should translate operational observations into concrete actions: updating schedules, changing briefing processes, improving rest facilities, or adjusting pairings. It also ensures that fatigue mitigation measures are documented and tracked inside the SMS, and that any changes comply with applicable flight time limitation rules and FRMS guidance.

Members must treat fatigue reports confidentially and avoid punitive responses so staff feel safe to report. The FSAG should also review training and education on fatigue for flight and cabin crew and for rostering staff. Where an operator uses a formal Fatigue Risk Management System (FRMS), the Fatigue Safety Action Group (FSAG) becomes the operational node that implements FRMS processes and demonstrates regulatory compliance through records and trend analysis.

Who should be on the Fatigue Safety Action Group (FSAG) and how it should operate

Choose members who represent the key domains that create and manage fatigue risk: operations, crew scheduling, safety, occupational health/medical, training, and worker representation. A small, consistent core team works best so decisions are practical and timely. The Fatigue Safety Action Group (FSAG) should have a defined chair (often the safety manager or a nominated FRMS lead) and a clear charter that sets decision rights, escalation routes and record-keeping requirements.

Meetings should follow a standard agenda that covers recent fatigue reports, duty pattern reviews, mitigation actions, and outstanding items from previous meetings. Decisions must be recorded with owners, deadlines and measurable success criteria. Data inputs should include reported incidents, voluntary fatigue reports, roster analyses, biomathematical model outputs if used, and feedback from crew. Where regulations require, link Fatigue Safety Action Group (FSAG) outputs to formal reporting to authorities and to the overall SMS risk register. Communicate outcomes to the workforce so staff understand changes and the reasons behind them.

Meeting cadence, review period and continuous improvement

Set a regular meeting cadence based on operation size and tempo. For most operators, a monthly FSAG meeting balances timely response with enough data to detect trends. Larger or higher-tempo airlines may need fortnightly meetings; smaller operators may operate effectively with quarterly meetings supplemented by ad-hoc sessions for urgent events. In all cases, the FSAG must be able to convene immediately when a serious fatigue-related event occurs.

Review the effectiveness of FSAG actions on a defined schedule. Short-term reviews of corrective actions should occur within 6–12 weeks to confirm they are working, and a formal program-level review should take place every 6–12 months. Use clear indicators to measure success, such as reductions in fatigue reports, improved rest opportunity metrics, or compliance metrics tied to EASA/FAA limits and any FRMS performance indicators. Regularly audit the FSAG process as part of your SMS assurance activities to ensure documentation, confidentiality and escalation procedures remain fit for purpose.

Implementing a practical FSAG is an iterative process. Start with a simple charter, defined members, a standing agenda and a clear data collection method. Build evidence over time, focus on measurable improvements and keep regulators and staff informed as needed. If you need templates or a starter charter, consult SMS guidance material or FRMS guidance available from ICAO and regional authorities, or contact SAFEJETS for tailored support.

Conclusion: An effective Fatigue Safety Action Group (FSAG) bridges operational practice and regulatory expectations by turning fatigue data into timely, measurable actions. Maintain a consistent representative membership, a clear meeting cadence, and short and medium-term review cycles to prove effectiveness. Prioritise confidentiality and staff trust so fatigue reporting supports continuous safety improvement.


You can manage your FSAG meetings with SAFEJETS MS – Aviation Compliance and Safety Management Software tool.

Privacy Settings
We use cookies to enhance your experience while using our website. If you are using our Services via a browser you can restrict, block or remove cookies through your web browser settings. We also use content and scripts from third parties that may use tracking technologies. You can selectively provide your consent below to allow such third party embeds. For complete information about the cookies we use, data we collect and how we process them, please check our Privacy Policy
Youtube
Consent to display content from - Youtube
Vimeo
Consent to display content from - Vimeo
Google Maps
Consent to display content from - Google