Commander's discretion at the end of a delayed three-sector day
You are the commander of a two-pilot A320 flight scheduled to report at 05:40 local for three sectors within Europe. Your operator's approved scheme gives a maximum daily FDP of 12 hours for a report time in that window, and you planned 11 hours 30 minutes. The first sector is uneventful. At the outstation, a two-hour slot delay on the second sector eats the buffer, and the third sector picks up a further 40-minute ATC delay. The revised FDP will be 14 hours 10 minutes, so you would exceed the maximum by 1 hour 20 minutes. Weather at the final destination is CAVOK, no alternate required, and there is no possibility of a crew change at the outstation. During the delay your first officer tells you he slept badly, about four hours, and feels 'flat'. He nevertheless says he is fine to fly and does not want to make trouble for the company.
1. What exactly does commander's discretion permit under the applicable EU flight-time rules, and what conditions must be satisfied before it is used?
Read the worked answer
Under Reg. (EU) No 965/2012, ORO.FTL.205(e), the commander may, after consultation with the crew members, extend the maximum daily flight duty period by up to two hours and may reduce the following minimum rest period by up to two hours. The concession exists for unforeseen operational circumstances - a slot delay and an unexpected ATC restriction qualify - not for planning. It cannot be built into a roster, offered as a routine way to finish a programme, or used repeatedly by the same crew.
The conditions are cumulative:
- safety: the commander must be satisfied the flight can be conducted safely, having assessed the actual fatigue of the crew and not merely the clock;
- consultation: the crew must be consulted, and their answers must be capable of changing the decision;
- mitigation: the added fatigue must be offset, typically by extending the subsequent rest, protecting the next duty or arranging a later report;
- recording and reporting: the commander must report the use of discretion to the operator, and the operator must record it and include it in the flight-time monitoring it submits to the competent authority; the operations manual must contain the procedure;
- no pre-planning: discretion may not be used where the operator knew in advance, for example by rostering a schedule that routinely depends on it.
It is a fatigue-management tool of last resort, not a two-hour extension of the roster. The 1 h 20 min overrun here is inside the numerical cap, which is the start of the analysis rather than the end.
2. Do you extend the FDP? Give your decision and the reasoning you would put to the crew and to operations control.
Read the worked answer
Decision: no. The aircraft stops at the outstation and the last sector is not flown by this crew.
The arithmetic fits inside the two-hour cap, but the cap defines the outer limit; it does not create an entitlement. The decisive fact is the first officer. He reports about four hours' sleep and describes himself as flat. The commander must weigh that self-report against the time of day, the length of duty already worked, two hours spent sitting at an outstation, and the fact that the last sector is the third of a day that began at 05:40 and would end around 20:00 local. That is a fatigued crew flying the sector with the highest monitoring risk, and no mitigation is available: no augmented crew, no in-flight rest, no ability to swap.
The consultation requirement is also a trap. Asking the first officer whether he is fine to fly and accepting 'yes' is not consultation if the answer he expects is the one that saves the schedule. Ask him what he actually wants to do, and tell him a fatigue report will be filed either way.
Operations control should be told immediately: position the passengers, arrange a hotel and a replacement crew, and file the commander's report. I would make clear on the record that discretion was considered and refused, so that the judgement is visible rather than appearing as an unexplained cancellation. The company then has to review why the roster had no protection for a two-hour delay; that is a flight-time monitoring question for the operator, not a discretion question for the commander.
3. Suppose the first officer had been fully rested and the predicted overrun had been 1 h 50 min. What would change, and what would not?
Read the worked answer
With a genuinely rested crew and a 1 h 50 min overrun, an extension would be defensible within the two-hour cap, provided every condition was met: unforeseen circumstances, real consultation, mitigation of the additional fatigue such as a later report or protected rest before the next duty, a report to the operator and recording in the flight-time monitoring. It would still be a decision, not an automatic one.
What does not change is the internal logic. The commander must consider:
- the state of the crew at the end of the sector, including whether the extension pushes the duty into a second low point of the body clock;
- the next day's duty, because fatigue accrues across days and discretion must not simply move the problem;
- whether extensions are becoming normal - several uses in a month on the same fleet is evidence of a rostering problem the operator must fix, and the authority will see it in the monitoring data;
- the other limits in the operator's scheme: weekly and 28-day limits, minimum rest and standby must still be respected once the sector is complete.
So the flight would be legal, but the record should show why it was safe on the day. Either way the operator's error is the same: a schedule with a 30-minute buffer on a route with a habitual flow restriction, which puts the crew at the edge of the limit and leaves discretion to absorb the system's inefficiency.