EASA Definition of Reporting for Duty
Thread Starter
Join Date: Dec 2004
Location: UK
Posts: 41
Likes: 0
Received 0 Likes
on
0 Posts
My problem is with the EASA regs, they are more fatiguing than the old regs. Also, some areas I think are important for fatigue mitigation are conveniently vague.
I suspect all OMAs will state a flight duty period begins at report, (mine does). I suspect none will specify where that is, (mine doesn’t). (Crew room, bag drop, security, car park, taxi rank etc - these are just examples to reinforce and illustrate the argument I am making, not that important in isolation but showing a more important lack of guidance.)
I do not have an issue if the rules were to state crew room, but as the time taken to get to the crew room has markedly increased over the years, and now coupled with more tiring EASA regs, I am concerned about the effect this MUST be having on fatigue. All left conveniently in a grey area by the authorities!
I suspect all OMAs will state a flight duty period begins at report, (mine does). I suspect none will specify where that is, (mine doesn’t). (Crew room, bag drop, security, car park, taxi rank etc - these are just examples to reinforce and illustrate the argument I am making, not that important in isolation but showing a more important lack of guidance.)
I do not have an issue if the rules were to state crew room, but as the time taken to get to the crew room has markedly increased over the years, and now coupled with more tiring EASA regs, I am concerned about the effect this MUST be having on fatigue. All left conveniently in a grey area by the authorities!
Only half a speed-brake
I suspect all OMAs will state a flight duty period begins at report, (mine does).
suspect none will specify where that is, (mine doesn’t). (Crew room, bag drop, security, car park, taxi rank etc - these are just examples to reinforce and illustrate the argument I am making, not that important in isolation but showing a more important lack of guidance.)
The EASA FTLs are standing on two feet
- 1 various numerical limits on activities
- 2 existence of effective fatigue management system
both of which are mandatory.
The 1) above are designed with the objective to allow for a great range of aviation activities and business models. For many if not most of them, the demands and practical restriction do not overlap. It is quite accurate to say that 1) was never intended to be exploited in all corners of its envelope in full by one individual or group and if that happens fatigue will ensue.
It is not breaking/extending beyond a certain limit that is reducing safety level below acceptable, working insufficiently alerted is. And indeed one could get fatigued when staying well clear of the boundaries, new rules and the old alike, even before we begin factoring the circumstances of personal and private life that do play a massive role by all means.
Hence the existence of 2). No matter if it's new teeth of your most beloved, or the EU devils who destroyed all that was good, a fatigue management system should contain the undesirable effects before the execution of duties is affected.
1) is not built water-tight to keep you at an acceptable state of alertness, 2) is. Feel free to quote me out of context whoever dares: The EASA FTL numerical limits are designed to enable fatigue (*). It is the mandatory FRMS that is put in place to ensure sufficient alertness levels of the crew on duty.
(*= as an unfortunate consequence of catering for a multitude of industry task patterns, in an all-encompassing manner)
This is not a defence of the EASA FTLs, but rather attempt to show how they are meant to work. A better understanding of which might help you handle the issues at hand with greater success. An anecdote from elsewhere, the regulator having sharper teeth:
a) extension in the planning stage (before the roster is approved and released) is not permitted
b) extension of FDP both before after commencing the duty is allowed up to 2 hours, but any extension beyond 30 minutes requires
- report to the NAA within 10 days by the Safety / Quality department suggesting measures to prevent re-occurrence
- after approval, those measures shall be implemented by the operator within 30 days.
c) there is a daily flight time limit, which is non-extendable (unless already airborne)
Thread Starter
Join Date: Dec 2004
Location: UK
Posts: 41
Likes: 0
Received 0 Likes
on
0 Posts
FlightDetent, I see what you mean about the range of operations using 1, and the monitoring responsibilities of 2. Suppose with the complexities faced, that is as good as we will ever get. Thanks for providing the reply, very much appreciated.
