Welcome to Flightinfo.com

  • Register now and join the discussion
  • Friendliest aviation Ccmmunity on the web
  • Modern site for PC's, Phones, Tablets - no 3rd party apps required
  • Ask questions, help others, promote aviation
  • Share the passion for aviation
  • Invite everyone to Flightinfo.com and let's have fun

declaring an emergency

Welcome to Flightinfo.com

  • Register now and join the discussion
  • Modern secure site, no 3rd party apps required
  • Invite your friends
  • Share the passion of aviation
  • Friendliest aviation community on the web
I just remembered something. About 15 years ago I was at an air show in Twin Falls Idaho. Bob Hoover was performing in his P-51, I was listening to the tower frequency, which was also the show control frequency.

All of sudden he rolled out of a manuver and said "Mustang has an emergency, I'm losing coolent". Sure enough, I saw a small vapor trail coming out of the engine.

He had plenty of energy, and I have no doubt whatsoever he could have just landed and 99% of the people wouldn't have noticed anything. He didn't even need traffic priority.

As he turned base he said "why haven't you rolled the trucks?" He shut down the engine on rollout and coasted to the turnoff, stopping in front of show center.

I guess if Bob Hoover isn't too proud to declare an emergency, then I'm not either.


Jim
 
JimNtexas said:
I guess if Bob Hoover isn't too proud to declare an emergency, then I'm not either.

:cool: Well said.
 
In Avbugs defense there is quite a difference losing one engine in a turboprop vs 747-400.

Our company policy(approved by FAA- probably 50 years ago) is not to declare an emmergency for 1 engine failure...I am sure the captain would depending on the circumstances.

My personal thoughts and experience- I have never seen anyone criticized for declaring.. I have seen the faa step in when in their opinion they think you should have declared and even taken certificate action.
(im moving and have packed my books) but somewhere in the AIM-emmergency section they have a paragraph encouraging people to declare an emmergency and to take advantage of the assistance atc can give before the situation deteriates.( What good does it do to declare an emmergency right before you go down in flames? It is a little to late)
Also it is a required report when certain failures occur..Plus your company will have to report these... so you are not going to hide anything.. you might as well help yourself a little and C.Y.A
 
Y'all can put away the lynch ropes. We've had this conversation before. Just because you don't have the experience, don't knock the insight.

Do I consider an engine failure an emergency? In most cases, most of the engine failures I've had, no. I've had them in single engine piston airplanes, and multi engine turbine airplanes, and not yet has one become an emergency. That's not to say it won't. However, it hasn't yet. Those who are going to blast me for such a "cowboy" or "cavalier" attitude should tell me all about their vast experience having engine failures or inflight fires, and I'll be happy to listen.

It has nothing to do with being "macho." That's for wet behind the ears kids to who such things mean a tinkers **CENSORED****CENSORED****CENSORED****CENSORED**. For me, it makes no difference.

Two years ago I experienced five engine failures in a four month period. Before anyone yaks off about poor maintenance issues, make sure you know what you're talking about and have experience in extreme environments where these things occur, lest you speak far out of turn. I've heard it all before, and usually by those without the experience to talk, or the place to stand in.

One of those failures was a V1 cut. It involved an engine rollback just prior to v1 (which occurs when taking the runway in that operation, because once the power comes up, you're committed). After shutdown, we managed 300' in the pattern for a return and landed. The base rolled crash rescue for us; we were too busy with the airplane to worry about talking to anybody, nor would it have helped. Was that an emergency? It was certainly a handfull, but declaring anything, and talking to anybody was absolutely out of the question at the time.

I recall posting comments about my view on inflight emergencies once some time ago here. I received all kinds of scathing editorials and private messages by those who had experienced the gamut in the simulator, but never in real life. Some time later an individual wrote back and stated that he had learned what it was I was talking about, and I believe him. He has the experience to know, now.

I knew an individual who left a position with an operator to go to work for an airline. He was assigned an experienced captain, for IOE line work. The captain mentioned that he had dealt with an in-flight emergency only a week before. Interested to learn the new business, this individual asked about the emergency. The captain said he had lost his primary inverter.

The individual asked what the emergency had been. That was it. The primary inverter. Ahh. The captain asked the individual what sort of experience he had with emergencies. The individual rattled off a list of things that had occured in the past year, including hydraulic failures, fires, structural cracks and failures, etc. The captain was aghast. The individual quit a few days later; he said he couldn't identify with people who thought something so piddly was an emergency; he went back to the operator to work. In a way, I feel the same.

Then again, I've worked around enough people that feel a spot on their white shirt is an emergency, I have developed a certain level of contempt for them. I've met enough flight instructors who are afraid of the student and the airplane that I'm wary of pilots and instructors until they prove themselves. My present temporary employer hired a pilot last year to fly the airplane I'm flying, doing the job I'm doing. That pilot had his first fire in the airplane, and immediately quit when he landed. During a going fire. He was terrified of the airplane and what he was required to do with it, and the conditions he was required to fly into, and the circumstances under which he had to do it. Quit on the spot after one sortie. To him, I imagine life itself is a big emergency. Better he quit than he kill himself and take a good airplane out of service.

An engine failure is NOT an emergency of itself. Certainly it can be, and I did clearly state before that if emergency authority is necessary, it should be used. However, I have too much experience with these things in actual fact to believe that any one thing is automatically an emergency, bar nothing. It's just not true. I've had fires and fire indications many times, and not yet has one developed into an emergency. I've dealt with them and continued the operation as necessary. This isn't cowboy or macho; it's doing a job professionally and in the manner that the job requires, and getting the job done.

You might think running an airplane down a steep mountain slope in smoke and flame is cowboy, but you'd be wrong. You may think flying an airplane that can't climb but a few hundred feet per minute in rough terrain and high winds is unprofessional, but it would only indicate a lack of experience to say so. You may think that flying under a powerline is foolhardy, but you would have to be very inexperienced in that type of operation to not know it isn't, that it's sometimes necessary in certain kinds of professional aviation.

Don't simply make blanket statements in areas where you have no experience. Certainly don't blast me for stating otherwise, as I do have the experience to make those statements. I was there; the moments didn't constitute an emergency. Perhaps for someone else, or under other circumstances, they might have been emergencies. It is not my place to say.
 
In regards to GA, I've worked both sides of the "declaring an emergency". And in most cases, it's always best to declare an emergency. All in all, it is tax payer's money, but you are getting the benefit of having a skilled crew at your side. I've seen gear-up landings, as well as precautionary landings. If you're in a Bonanza, most likely it won't take more than 20 minutes to remove your aircraft from the active (maybe less from the "other" runway"). With regard to the precautionary landings; sure the fire crews will most likely roll, but all in all it's better to be on the safe side right? With those precautionary landings, the fire crew stay stationed at their "predeterminded areas" and just sit still. And even if it is a "precautionary landing" when the fire crews do roll, all they do is take your personal info (as well as the airport rep) and that is all that it is. Period. Sorry for the long soap box lecture, but in my experience (on both sides) if in doubt, declare an emergency. More often than not (from an a/p mgmt standpoint) if it's nothing major, nothing MAJOR will result from it. But if my flying duties are impared, bottom line, I'll declare an emergency. Most often than not the FAA and the airport admin are most likely willing to work with you.

BOTTOM LINE: If there is a question as to whether or not you should declare an emergency, then by all means DECLARE AN EMERGENCY. It's better to explain on the ground than to have Monday-morning quarterbacks second-guess your logic.
 
Last edited:
One other thing. If any of you have had the unfortunate chance of having an aviation accident give the NTSB a call and request the full file, which is called the docket. Anyway, the number for the NTSB to contact is 202-314-6100. Not sure if they charge for this yet, but it will contain pretty much everything the NTSB and FAA has on your case. Very imformative.

Regards,
-Airnik
 
Last edited:
One last bit of info: I saw one guy land gear-up three (yes three) times in a retract, at KSUS. Upon the third time, he said (basically) that f*** it, i'm going to helicopters. As far as I know, he's been flying R-44's for the past 5 years. Just goes to show you that if you have enough money,.......

regards,
-airnik
 
Wow.

Avbug, in the V1 cut you described...let me make sure I understand. You took (I'm guessing, based on your 300' altitude) a 50% power loss, came back around in the pattern, and landed without saying a word on the radio? I'm not so sure that keeping the guys on the ground completely in the dark is a good idea, no matter how busy you are. (Were you the only guy in the airplane?)

You said over and over that in the situations you've been in, declaring would not have affected the outcome. Then why not do it? It costs you nothing...and could gain you everything. If it's not a question of macho, then what's the problem?

Yeah, I have less than 5,000 hours and haven't had a triple engine failure every month for the last five years. I've never declared an emergency for "a spot on [my] white shirt," either. I did declare for (1) a 100% power loss, (2) a left main that wouldn't extend, (2) a total hydraulic system failure, (4) two flaps-up landings, and (5) a severe turbulence encounter at 500' on base. I hate tooting my own horn, but I believe I handled each of these situations fairly well.

Please explain to me why it was somehow unprofessional of me to declare these emergencies. I'm not out to lynch anybody, I just want to understand this mind-set, because right now, I don't...and I don't see how experiencing any more emergencies is going to change my mind.
 
Last edited:
Typhoon1244

<Please explain to me why it was somehow unprofessional of me to declare these emergencies. I'm not out to lynch anybody, I just want to understand this mind-set, because right now, I don't...and I don't see how experiencing any more emergencies is going to change my mind.Please explain to me why it was somehow unprofessional of me to declare these emergencies. I'm not out to lynch anybody, I just want to understand this mind-set, because right now, I don't...and I don't see how experiencing any more emergencies is going to change my mind.>


If you keep your mouth shut, the FAA will surely have you by the b@lls.

I stilll adamantly believe that it is not only neccessary but prudent to declare an emergency, especially if your "FLYING ABILITY" is impaired. PERIOD.

-Airnik
 
Last edited:
Avbug:

Do you fly passengers for a 121 airline?

PS: I have declared an emergency for an engine-shutdown. I received a letter of commendation. I can guarantee you that if I had not declared, I'd be looking for another job right now and hiring a lawyer to defend my ticket.

Please stop giving poor advice to impressionable young minds.
 
Originally posted by avbug
Two years ago I experienced five engine failures in a four month period.
:eek: I think I'd quit that outfit too. Who are you with, the Honduran Air Force?

Originally posted by DarnNearaJet
Avbug: Do you fly passengers for a 121 airline?
It doesn't sound like he does, no. I can't imagine a professional airline pilot--or any pilot--having this warped a definition of "emergency."
 
Last edited:
I'll throw my 2 cents in. I'm NOT getting into the debate whether to declare an emergency. I am saying that just because you get a Red light that comes on your dash doesn't necessarily an emergency make. Those of you who fly really old dogs know what I mean. There is plenty of young bucks out there who see a light and freak out, declare an emergency, rush though the check list, shut one down ect. ect. when there wasn't a thing wrong with the plane except a swicth or wiring harness that failed. The illuminating of a light means you had better take a deep breath and pay attention to what really is going wrong before you go do something rash that may put you in real danger. Go ahead call me a cowboy and flame away. Before you do spend some serious time flying old stuff that was out of warranty long before you were born. Put yourself in Avbug's shoes before you flame him he is'nt driving a Barbie Jet that still smells new.

KlingonLRDRVR
 
KlingonLRDRVR said:
I am saying that just because you get a Red light that comes on your dash doesn't necessarily an emergency make.
I agree. You don't have to fly old dogs to understand that concept.

There is plenty of young bucks out there who see a light and freak out, declare an emergency, rush though the check list, shut one down ect. ect. when there wasn't a thing wrong with the plane except a swicth or wiring harness that failed.
Anyone who "freaks out" and grabs a microphone as soon as a light comes on doesn't belong in aviation. Period.

The illuminating of a light means you had better take a deep breath and pay attention to what really is going wrong before you go do something rash that may put you in real danger.
I dunno, Klingon, it sounds to me like you and I are nearly in complete agreement. You need to go back and re-read Avbug's posts on this issue. If I understand him correctly, he believes anything short of a crash isn't an emergency.

Say you're at cruise at FL330 and the flight attendant has smoke coming from behind the galley. You kill the power to the galley and the smoke stops. If I'm correct, Avbug would not declare an emergency. I would because I have no way of knowing what might still be burning in there! (And if your "Old Dog's" wiring is as quirky as you suggest, you might have the same problem.) And that doesn't mean the declaration is going to magically fix the problem...but now I'm covered by the FAR's and ATC as I make my way to the nearest place with a long runway and a fire truck.

It's right there in the AIM: the time to declare an emergency is before the situation gets out of control...not after you've already exhausted all your alternatives.

Oh, and let's not resort to this "don't trust anyone under forty-years-old or 5,000 hours" crap. There've been an awful lot of airliners flown into mountains by guys with 10,000+ hours at the top of the seniority list. When I was flying down in Florida, it wasn't the student pilots that scared me. It was the guy in the Bonanza who hasn't cracked a book since he got his ticket back in 1965.
 
Last edited:
Typhoon (et al),

Before you get yourself worked up into a frenzy, yo should note that at NO time have I ever dictated that one should NOT declare an emergency. I stated that the events that I have experienced, in the type of operation and in the situation, (in context) were not emergencies. What you do is your own business.

I was not with the "Honduran Air Force" for the events to which you allude. Those occured during firefighting operations, which put airplanes in some extreme circumstances, and cause stresses and conditions not encountered in other types of flying. Those occured in large four engine airplanes, and were flown with a crew, not single pilot. My experiences in one of those airplanes pale in comparison to a fellow crew in the past month; the airplane exploded for them. (I experienced an explosion on board in that airplane several years previously).

You may not have occasion to be flying on instruments in close proximity to the ground in high winds and severe to extreme turbulence while your engines ingest burning objects that vary in size from a 2X4 to a whole tree. That doesn't mean that those who do fly into those conditions are unprofessional. On the contrary, the flight is in a state of emergency from the time the horn goes off...having an engine shutdown or a small fire to deal with is minor compared to the normal routine...the normal routine IS the emergency.

When you don't deal with it all the time, small things seem like big things. When you do deal with it all the time, big things can become routine. Two airplanes I formerly flew have come apart on the job this year, killing crews I flew with. I'm flying a type design that's had two airplanes of it's own shed wings, too. It's not a maintenance issue; it's the environment. Don't knock it if you haven't been there.

If I went about declaring an emergency for some of the things we've been discussing, I'd declare it when I get the dispatch slip, before taking off, and would reiterate it each time I check in with a new party. I didn't create the emergency, so I don't feel bad about enjoying dealing with it. If you want to see a round engine pilot sweat bullets, let him go three hours without a problem. The suspense is a killer.

Call me "warped" if you will. Until you have the experience to back it up, or have flown a few hours in my boots, then that assesment doesn't mean much to me. My definition is developed by personal experience. It's nothing to do with being "macho," or other kid-stuff. It's to do with having experienced these things before, and knowing what is worth getting excited about, and what isn't.

You may choose to get really excited about an onboard fire. In many cases, this may be warranted. I'm not about to tell someone not to declare an emergency, but I can state that of the fires I've experienced personally, none yet have amounted to much excitement. I've been in structural fires on the ground on a number of occasions, and wildland fires as well, that got my blood pumping a lot more, and that weren't nearly as easily put out. People tend to panic by nature when they see a fire; fire suggests an emergency by it's very essence. This isn't always the case. I've been in fires hot enough to melt the nomex on other firefighters heads, and melt my boots. Putting out a seat cushion or a little fuel fire in many cases just doesn't compare.

Every situation is different, and I have repeatedly stated that if you need to exercise emergency authority, then do it. You should understand that no formal declaration of an emergency is necessary to do this.

I was once in a recurrent class for the Learjet. The instructor, a man with many years in the Lear, was discussing an depressurization at altitude. He asked me the proceedure. I rattled off the litany; oxygen masks don, select one hundred percent. Thrust levers to idle, auto pilot disengage, spoilers extend...yada yada. When the immediate action items are complete, the proceedure goes on to say "if time and conditions permit..." and provides that the pilot should activate the oxygen mask mic switch and notify ATC.

The instructor insisted that this should be done first, before the descent is begun. He noted that one might descend into other traffic, and emphasized the need to communicate. I disagreed, and still do. Get oxygen, get started down, deal with the situation and fly the airplane, and then as the proceedure clearly states, if time and conditions permit, talk.

When I lost power at the V1 cut, it wasn't a 50% loss. It was one engine of four. It was the critical engine. Shutting down a radial engine isn't the same as shutting down a turbojet. Additionally, feathering with a hydromatic system isn't about just pushing a button. You have one shot in the event of oil loss, if that, and if you don't get it timed right, it comes out of feather, or doesn't go in all the way and this is a real problem. 300' is no time at a non-towered field to be wasting time talking to empty space about emergencies. If that prop isn't feathered pronto, and kept feathered, then the flight isn't going to maintain altitude. At 300' do you really think it's a time to be screwing around yodeling about what a bad day you're having, or is it a good time to take care of that airplane?

There's nothing cowboy or cavelier or unprofessional about dealing with the situation at hand and saving the yak-yak for later. To whom would I have declared an emergency? If someone other than a private pilot responded, how do you suppose they might have helped me? This wasn't an international field with crash rescue standing by. It was a normal every day operation that happened to require the full attention of both crewmembers. It so happened that base personnel who watched the departure called a local fire department as soon as we disappeared behind the trees.

Who do I fly for as my regular employment? That doesn't really matter, but I have yet to pass a check with less than flying colors; I have never had an employer or passenger complaint. I work closely with the FAA, and am even an Aviation Safety Counselor...all with no troubles at all. Employers, passengers, check airmen, and the FAA, as well as contracting agencies et al, don't have a problem with me...why do you??

I am temporarily fighting fire again, as it's my passion and love, and by a stroke of good fortune, it's something that I'm good at. I am on a leave of absence from my regular employment, as qualified initial attack pilots are in demand this year due to a high fire state. I don't have the luxury of picking nits over small minor matters. A number of personal associates have died on the job this year, and I'm doing my darndest not to join them. Does that make me cavalier or unprofessional? I'm not dead yet, so you tell me. Perhaps tomorrow, huh?

Poor advice to impressionable young minds? Come on! Let's just celebrate a heritage of inexperience, then. Why bring personal experience and observation in, when we could simply exist on school book plattitudes and lessons learned in the mighty simulator? Why drag real life into it? If these things concern stuff you haven't had to deal with, then perhaps it's worth listening...you might learn something.
 
Stop this crap

AVBUG,

You gotta stop this. Somebody might actually believe this garbage, just not anybody who has experience as a pilot. Your account of your daily emergencies sound like you think you're in a movie or something. I have a strong suspicion that not only are you not a pilot, but that all your piloting 'experience' has been gained by watching movies. How can you actually post garbage like this? If you were taking 2X4's and trees down your engine on a daily basis you'd be dead instead of making up ludicrous garbage to post here.

If I refused to declare an emergency for engine failures and fires I would have failed every checkride I've ever been given. You just don't seem to have any grasp on reality at all. Do you know what would happen if I had an engine failure or fire with passengers on board, made an unscheduled landing not at my planned destination, and then told the chief pilot I didn't feel it warranted declaring an emergency? How about if the situation worsened and I banged up the airplane a little and got investigated by the feds? Man just stop it. I wondered why there was no info at all on your qualifications in your bio. You don't have any. Nor any sense. Go to the pretend pilot board. This one is for ACTUAL pilots.


>>You may not have occasion to be flying on instruments in close proximity to the ground in high winds and severe to extreme turbulence while your engines ingest burning objects that vary in size from a 2X4 to a whole tree.>>

The definition of extreme turbulence is that the airplane is completely UNCONTROLLABLE and will not respond to any inputs made by the pilot. Do you actually expect us to believe you fly close to the ground in an uncontrollable aircraft while ingesting trees into your engine???????

Holy !@#$%^&. Seek counseling.

>>That doesn't mean that those who do fly into those conditions are unprofessional. On the contrary, the flight is in a state of emergency from the time the horn goes off...having an engine shutdown or a small fire to deal with is minor compared to the normal routine...the normal routine IS the emergency. >>

This job I'd quit tomorrow if it really existed.

You're either 12 years old and living a fantasy or just a nutcase.
 
JimNtexas said:
"Mustang has an emergency, I'm losing coolent"..."why haven't you rolled the trucks?"
I'm just getting in on the tail end of this discussion, but this sure puts thing in perspective for me. if that's the criteria for Mr. Hoover, then it's works for me. Thanks for the post, Jim. Where in Tejas are you? I'm serving time in Houston myself. ;)
 
Avbug,

I'm so envious of the lifetime of experience that allows one to treat the situations you describe as "normal". Probably most of the pilots on this board have experienced some types of abnormal situations, and as they handle them, the confidence levels increase, and the next time it happens, it's nbd. "Experience" is such a relative thing. It amounts to being comfortable dealing with whatever situation the aviation gods throw at you, because you've been there before.

I have a friend who experienced his first windshield failure at FL300 a few months ago. Scared him sh%%less. It happened again in a different plane, and the second time, it wasn't such a big deal. Such is the way of experience.

So tell me, when you were a green pilot, DID those first time run-ins with abnormal situations create a pucker factor? Understanding that we never stop learning, but at what point did you begin to feel you were really the master of the aircraft?
 

Latest resources

Back
Top