Duty Time and Rest After an Unscheduled Diversion
A crew operates a two-sector day from Recife to Belém with a scheduled return. The outbound sector departs 40 minutes late because of weather. On arrival at Belém, the destination weather deteriorates below minima and the return is delayed three hours. The commander, a captain with 11 years of experience, has been on duty since 05:10 and the return sector would land at 22:40 local time. The first officer is on her fourth consecutive duty day. The operator's operations control centre proposes to release the return sector, arguing that the commander may extend the flight duty period at his discretion because the delay was caused by weather beyond the company's control.
1. Assess the operations control centre's argument that the commander may extend the duty period at his discretion.
Read the worked answer
The argument is partly right and partly wrong, and the distinction matters. The commander does have authority to extend a flight duty period in defined circumstances, but that authority is bounded by the operator's approved scheme and by the regulatory maximum, and it is not a general licence to exceed limits whenever a delay has an external cause. Weather is typically a circumstance the scheme may recognize, but the commander must still check the remaining margin, the crew's cumulative duty, and any reduced-rest provisions.
Here the return would land at 22:40 after a duty start at 05:10, a duty period of roughly 17.5 hours before post-flight duties. That is likely beyond the maximum even with an extension, and the first officer's fourth consecutive duty day adds a cumulative-fatigue dimension. The commander should calculate the actual figures against the approved scheme rather than accept the control centre's framing, and should decline the release if the limits are exceeded.
2. Describe the factors the commander should weigh in deciding whether to operate the return sector, and the decision framework.
Read the worked answer
The commander should apply a structured framework rather than a single number. First, compute the actual flight duty period and compare it with the applicable limit and any permitted extension. Second, assess cumulative fatigue: the first officer's fourth consecutive duty day, the early start, the three-hour ground wait, and the weather stress all contribute. Third, consider the operational alternatives: delaying the return to the next day, positioning a relief crew, or canceling and re-accommodating passengers.
The framework should also include a documented fatigue assessment, because the decision may later be reviewed. The commander should record the calculated duty period, the reasons for the decision, and any consultation with the crew. If the limits are exceeded, the correct decision is not to operate; if they are not exceeded but fatigue is evident, the commander may still decline. The discretion exists to protect safety, not to protect the schedule.
3. What should the operator's safety management system capture from this event, and how should it be reported?
Read the worked answer
The event is a reportable occurrence and a useful safety data point. The safety management system should capture the delay cause, the duty-time calculation, the commander's decision, and the outcome, and should analyze whether the schedule design leaves insufficient buffer for routine weather disruption. A pattern of near-limit returns on this route would indicate a systemic scheduling risk rather than an isolated event.
The report should be filed through the operator's internal reporting system and, where the applicable rules require it, to the authority, within the prescribed time. The analysis should avoid blame language and focus on the conditions that produced the pressure. The output should be a safety action: revised scheduling buffers, a clearer extension procedure, or both, with a named owner and a review date.