Planning buffers: why the CAR asks for them
A roster planned right up to the limits has no room for a late arrival. Why your FDTL Scheme sets planning buffers below the CAR limits, and how to use them.
The limits in the FDTL CARs are the most a crew member may do. They are not a target to plan to. A sector that leaves 20 minutes late, a hold for weather or a slow turnaround all add to the duty on the day, and a roster planned right up to the limit has no room for any of it.
That is why an operator’s FDTL Scheme carries planning buffers: values below the CAR limits that the roster is planned against. Para 4.1 of CAR 7-J-III sets out what the Scheme must cover, and buffers are part of it.
What a buffer looks like
A buffer is a margin you choose, written in your Scheme. For example, a Scheme might plan cumulative duty to 55 hours in 7 days, where the CAR limit is 60 hours, or keep every planned FDP at least 30 minutes inside its limit.
| Limit | CAR | Planned to | Margin for the day |
|---|---|---|---|
| Duty in 7 days | 60 hours | 55 hours | 5 hours |
| FDP, 5 landings | 11:30 | 11:00 | 30 minutes |
The values are yours to set and to justify to your regulator. Short sectors with many landings, stations with frequent weather or long taxi times, and seasonal schedules all argue for a larger margin.
Why the CAR does not leave it to extensions
The CARs allow a commander to extend flight time and FDP in unforeseen circumstances (para 16 of both CARs), with caps over any 28 days and more rest afterwards. That is a safety valve for the day, not something to plan on. A roster that only works if an extension is used is not a legal roster.
There is a second reason to keep a margin. If discretion is used for similar reasons on more than 20% of the occasions a route or route pattern is flown, the operator must review the schedule (CAR 7-J-III para 17.4; under CAR 7-J-IV, para 18.3.1 for scheduled commuter operators). Buffers keep the roster from depending on discretion in the first place.
Warnings, not violations
A buffer is a planning rule, so crossing it is a warning rather than a violation. The duty is still within the CAR; the scheduler is told the margin is thin and decides.
Take a duty with five landings and an FDP of 11:15 against an 11:30 limit, with a 30-minute buffer. It is legal, with 15 minutes to spare, and it is inside the buffer, so it is flagged. The scheduler can accept it with a recorded acknowledgement, or move a sector to restore the margin.
How AeroLarke uses your buffers
- Buffers are part of your Scheme in AeroLarke, entered in the Scheme editor beside the CAR value they sit under, and changed only through maker-checker approval.
- Every assignment is checked against the CAR, your Scheme and your buffers before it saves. Crossing a buffer raises a Planning warning, marked as such, with the limit, the planned value and the margin.
- Accepting a warning is recorded in the audit trail, with who accepted it.
- The go-live checklist will not let an operator go live with no planning buffers set.
- Planned duties never rely on an extension. Extensions are recorded only on actual times, with the commander’s discretion noted.
If you are choosing buffers for the first time, start from what your approved Scheme already says, then look at your actual times: where duties regularly run over plan, the buffer there is too small.