Equipment Malfunction

 Folks, bear with me on this one.  It's going to take quite a bit of setting the stage before I get to the point on this post.  I'll get there, I promise. But I'll start with the hero of the story.

No Beans, Not Princess Leia.  Miss B!

Back in the day my folks would try and teach me the need for trust in the world.  One needed to trust their fellow man to do the right thing else one would spend his entire life looking over his shoulder for protection instead of ahead for opportunity.  

Of course they also taught that once someone had proved themselves untrustworthy...Well, don't trust them.  Ever.  I'm not talking a simple "letting you down", but actual betrayal.  Failing to do their duty to honor their word deliberately regardless of reason.  That was the ultimate sin.

Then I joined the military and realized where that ethos came from.  My instructors insisted on trustworthiness in themselves and their students.  That expectation extended through all members of the military.  If you wore the uniform, your word was your bond.  You may fail, but you failed while giving your best.

Source

 

As a "For Instance", even non-flying readers will realize that an In-Flight Fire is an extremely serious event.  They would not be wrong.  Unlike a sailplane, the engines are the things that keep you aloft.  Without them, you are going to be landing.  Whether on a runway or not, is not generally your choice.  The airplane is coming down. Period.

Ok, how does the USAF address an Engine Fire?  The "Bible" on aircraft operations in the Air Force is affectionately called the "Dash One".  The F-4E Dash One can be found here.  Just as an example of how important that document is, 40 plus years after the last time I read it, looking through the Engine Fire or Overhead during Flight Emergency Procedure, I recognized some subtle changes in the wording and punctuation of the procedure from the previous reading.  That's how serious we took that book. In any case, here's the procedure. (It's found on Page 3-9 at the link above.)

Engine Fire or Overheat during Flight

1. Throttle bad engine - IDLE
2. If warning light goes out - CHECK FIRE DETECTION SYSTEM
Depress fire test button to determine that the fire detecting elements are not burned through.
3. If detection system check is satisfactory (i.e., warning lights illuminate when checked) - LAND AS SOON AS PRACTICABLE
Increasing thrust on the bad engine after the throttle has been retarded and the warning light has been extinguished may cause fire or overheat damage, and/or possible burn through the fire detecting elements.
4. If warning light remains Illuminated or fire detection system is inoperative or fire is confirmed - SHUTDOWN ENGINE
5. If fire persists - EJECT
6 . If fire ceases - LAND AS SOON AS PRACTICABLE 

CAUTION
Do not attempt to restart the bad engine. If the fire ceases, and a landing is to be accomplished, make a single engine landing.

Pay particular attention to #5 in that procedure.  If the fire light does NOT go out, you are to eject from the airplane. Period-Dot-End of Story.

So, juvat, interesting, but where are we going with this story?

Trust, my Friend, Trust.  We had an E-model at Moody that was pretty much a hangar queen. (For the non-familiar, the term indicates the jet has a boatload of mechanical problems which are difficult to ascertain, expensive to fix and the fix may not fix the entire problem.) One of the requirements when a Hanger Queen is thought to be "Fixed" is to give it a "Functional Check Flight" or FCF.  This is always flown by a VERY experienced crew and is flown on a fixed profile with specific parameters to make sure the airplane is fixed and ready to be put on the daily schedule.  This jet had passed it's FCF flight and was back on the schedule.

I'm Flight Lead for a 4 ship range ride to go and drop practice bombs and fire the gun at the gunnery range at Eglin AFB FL.  

No those are not 25Lb Practice bombs, those are inert 500Lb Bombs, but that is Eglin Range. Source

Typically the aircraft is loaded with 12 x 25Lb practice bombs and 100 rounds of 20mm bullets. 

 

Source

 Fighter Pilots, being the competitive type, typically bet on the scores.  Quarter a bomb, nickle a Hole.  So, worst case, one could be out 8 bucks, plus the requirement to buy beer in the Debrief.

Bragging rights, however, were worth much more than that.  So, one tried their very best.

Unfortunately, I've drawn the Hangar Queen and, even with my best body English, couldn't get the bombs very close or the gun to hit the target.  I'm irritated at myself on the way home and we're about halfway there when I simultaneously hear/see the Master Caution light come on and hear the WSO yell something about "Fire" over the intercom.  Suffice it to say, I am focused at this point.  

The right engine fire light is on.  Technically, at this point, I'm supposed to ask the WSO to get into the check list and read me the procedure after which I will perform the procedure.  That works well in the Simulator.  (AFAIK no one has actually died in the Sim.)  I immediately pull the throttle to Idle.  Nothing.  I decide on a count to 10 before skipping to #4 on the Emergency Procedure.  I know it didn't take 10 seconds for that count, more like 1  maybe 2.  

Light's still on.  So I shut down the engine.  Soon as it spools down, the light goes out.  I push the test button, it lights up and goes out when I release the test.  I have one of the wingmen give me a look over.  Nothing, no smoke, no visual damage.  OK we get to skip #5 (Thank you, Lord.  My takeoff #s will continue to match my landing #s.)  

Approach and landing are normal, well, as normal as a single engine approach and landing gets and except for the fire trucks, ambulances and other crash vehicles near the runway, other than that perfectly normal.  Pull into the dearm area.  Dearm crew safes the crucial stuff and give the shutdown signal.  1.6 nanoseconds later, myself and the WSO are on the ground and vacating the immediate vicinity.  

The jet goes back into maintenance, the maintenance repair checklists are applied and she  gets back on an FCF schedule.  The same thing happens.  Back into maintenance and another FCF.  Again a Fire Warning Right Engine.  In that afternoon's Wing Honcho meeting, the Maintenance Commander wants to annotate the problem in the maintenance forms as a "glitch" and keep the jet on the schedule. Maintenance Stats...Gotta love 'em.

At that point in the meeting, the Wing Commander relieved him from command.  As he did so, he said "If the warning light comes on, how does the pilot know that the jet is not on fire? If he stays with the jet and it IS on fire, he and his WSO will likely be killed.  Is your in-service rate worth that?"

In other words, the Maintenance Officer had betrayed our trust.

The jet went to depot maintenance and AFAIK never flew again, at least not at Moody.

BTW, that Wing Commander went on to 3 stars.  IMHO, shoulda had 4.

Interesting story, juvat, but what's behind this story? That would be Miss B's monitoring equipment and sensors.  More knowledgeable medical readers may correct me, but I believe that one of the last organs that develop when a Baby is in the Womb are their lungs.  Therefore, premies, spending less time there, tend to have lung issues after birth.  Miss B is currently on O2 while her lungs get better.  She also wears a Pulse Ox sensor that keeps track of her pulse rate and oxygen saturation level in her blood.  It sets off an alarm when either reading goes below the minimum level. 

That alarm can, and should, be heard throughout the house.

However, the Damn thing goes off ALL THE F.....g time!  The medical equipment company says that's caused by the baby moving.  OK, maybe.  But, then, why does it go off when she's sound asleep and not moving.  AKA one of us is sitting right beside her watching when it goes off.

So...Next they said it's a faulty sensor cord.  OK.  They send a new one.  Except that one is for a different model sensor. 

Top two are the new cable.  Bottom two are the old cable.  I'm not an electrician, but something tells me the new ones won't work.

 They send a new, new one with a technician.  No change.  Course the baby's awake while he's here, so moving.  Later that same day.  No movement, still alarms.  

Drive down to San Antonio to meet with the Pulmonary Docs.  They hook up their device side by side with ours.  There's doesn't squawk and their readings are virtually the same as ours.  Guess what squawks.

I mentioned to them my story about Trust and the fire light and asked what, worst case, might happen in the middle of the night if LJW, being extremely sleep deprived and tired, decided it was a false alarm and rolled over and went back to sleep.

We'll see what the next appointment with them yields. Suffice it to say, the NICU Staff and Docs are on Santa's good list while the Medical Equipment folks...well...aren't!

Nap Time!

Oh, and by the way, as I'm wrapping writing this up Sunday PM, we just got a winter storm warning with icing.  Last year when this happened, electricity was off for quite a while, 3 days for us; up to 6 weeks for some people further in the boonies in the county.  Electricity is needed for Miss B's breathing assistance equipment.  Emergency Action Plans are being developed as we speak.