Let's talk about when to declare an emergency. I think there's value in each pilot contemplating this for themselves.
I started thinking about this after my thread about vfr in the mountains. Several people suggested that I should have declared an emergency. I disagree, however, as I say, it made me think about my criteria for when to declare...
My criteria is to declare at the point that I have a reasonable belief that I will have to perform an emergency / abnormal procedure, violate a regulation, or need special consideration or assistance.
In my mountain VFR scenario, I did not declare (and stand by that decision) because I did not yet believe I would need to do anything abnormal, violate a regulation, or request special consideration. Had I run any lower in fuel, there would have been a good chance I would have had to violate a regulation (cloud separation) or need special consideration or assistance, but I was not yet to that point.
However, is where the problem can happen. It's very easy to fall into the invulnerability hazardous attitude and say "it'll be ok, no need to declare yet".
I'll give two more examples, both clearly on either side of the spectrum. It get's harder the closer the scenario gets to the middle.
1. On takeoff, I brief what I will do if there are engine issues on climb out. I will not declare an emergency just because I've identified a potential issue. It is not reasonable to think it is inevitable.
2. I'm in the pattern and my engine is over-speeding. I will declare an emergency even though I think I can easily make the runway. The odds are good enough in my mind that I might need to do all the things in my above criteria, therefore I will declare immediately. This actually happened to me and I did NOT declare. I did request that the aircraft on the taxiway keep the runway clear (un-towered airport), but I should have declared. Going through this exercise has changed my behavior on this. If it happened again, I would definitely do so.
Hope this helps someone think about emergencies differently.
I started thinking about this after my thread about vfr in the mountains. Several people suggested that I should have declared an emergency. I disagree, however, as I say, it made me think about my criteria for when to declare...
My criteria is to declare at the point that I have a reasonable belief that I will have to perform an emergency / abnormal procedure, violate a regulation, or need special consideration or assistance.
In my mountain VFR scenario, I did not declare (and stand by that decision) because I did not yet believe I would need to do anything abnormal, violate a regulation, or request special consideration. Had I run any lower in fuel, there would have been a good chance I would have had to violate a regulation (cloud separation) or need special consideration or assistance, but I was not yet to that point.
However, is where the problem can happen. It's very easy to fall into the invulnerability hazardous attitude and say "it'll be ok, no need to declare yet".
I'll give two more examples, both clearly on either side of the spectrum. It get's harder the closer the scenario gets to the middle.
1. On takeoff, I brief what I will do if there are engine issues on climb out. I will not declare an emergency just because I've identified a potential issue. It is not reasonable to think it is inevitable.
2. I'm in the pattern and my engine is over-speeding. I will declare an emergency even though I think I can easily make the runway. The odds are good enough in my mind that I might need to do all the things in my above criteria, therefore I will declare immediately. This actually happened to me and I did NOT declare. I did request that the aircraft on the taxiway keep the runway clear (un-towered airport), but I should have declared. Going through this exercise has changed my behavior on this. If it happened again, I would definitely do so.
Hope this helps someone think about emergencies differently.