PPRuNe Forums - View Single Post - Flysmart EOSID legal status
View Single Post
Old 12th December 2024 | 18:33
  #25 (permalink)  
sonicbum
10 Anniversary
 
Joined: Mar 2012
Posts: 2,605
Likes: 154
From: Having a margarita on the beach
Originally Posted by PENKO
I think every rulebook every written regarding aviation contains a version of the following:





Aviate, navigate, communicate. It’s the nature of the emergency in itself that allows you to deviate from your clearance, not the words mayday in itself. Don’t get me wrong, I have no hesitation to declare an emergency, especially at the early stages of an engine failure after takeoff. I just want to make sure we don’t put the cart before the horse. The controller is not in command, we are.



Really? I thought controllers were in charge. Good to know.


We are not obviously talking about the safest course of action, which we are going to implement regardless of the phraseology being used (so your comment about putting the cart before the horse is irrelevant).
We are discussing the fact that you are not alone in the sky, and that a distress message will allow the necessary actions from ATC and other aircrafts to keep you clear of other traffic whilst maneuvering in the interest of safety.
With that being said, are you starting your EOSID before declaring a mayday? Of course you do (fly navigate communicate as you kindly taught us all) but as soon as the situation allows proper communication is required. Is the failure so catastrophic that there’s no chance to speak a single word to ATC? Fair enough.

Last edited by sonicbum; 12th December 2024 at 18:49.
sonicbum is offline  
Reply