Business Services Industry

Semper paratus?

Approach, June, 2003 by Don Manning

Aviators must be prepared for any eventuality: emergencies, broken planes on man-up, weather, whatever. From day one of primary, our trusty IPs beat the concept of preparation into our heads, either in flight or by covering many "what ifs" during the extensive briefs. How many junior aviators fully appreciate proper preparation? How many of us still think this way after 1,000 hours? If you are standing an overnight alert, do you mentally prepare yourself as if you were going to fly it?

During JTFEX for my third JO deployment, I woke up with the det OinC kicking my rack and yelling at me to wake up for a flight. A quick check of the clock showed 0200, and the realization sunk in that our alert-60 mission actually was being launched. How often does this happen in the HSL community?

While the troopers traversed the aircraft onto the flight deck, my 2P and I went to CIC to see what was up. CIC briefed that a Spruance-class destroyer. 60 miles away, had a subsurface contact. However, a P-3 told them the contact was a wreck or rock formation, not a sub. We were to be the tiebreaker.

I was in the right seat, allowing the H2P to get quality ATO training. After checking in with the DD, we coordinated airspace with the P-3 and got their buoy dope; our assessment agreed with the P-3. It was approaching 0430 as we started home. After we started climbing, the TACAN showed mom and our racks 58 miles away. As I gave the H2P the controls, so he could fly for a while, a mastercaution light lit up our faces. At the same time, we got a right engine chip light. The chip light went out after five seconds.

No secondaries were noted as I mentally juggled the ORM issues. "Hmmmm," I figured, "Mom is 58 miles away, but this DD I'm talking to only is 12 miles behind me."

I called the DD, requested flight quarters, took back the controls, and turned around. My guess was fuzz caused the master-caution light; the DD's mechs would clean it up, and we'd be on the way back to our racks.

You see where this is going, right?

I flew a poor, single-engine (just in case the engine quit) approach to a landing, and the right engine worked like a champ. I got out after we shut down and left the H2P to supervise the APU. While I talked with the local det's maintenance chief, their night-check AD came into the hangar with the chip detector asking, "Was that thing running when you landed?"

"Uh, yes, it was fine," I replied.

"Well, look at this," he said, holding out the chip detector. The filter screen was full of metal; the pieces were big, small, different colors, and some had serial numbers. A sample of every kind of metal in the engine was there, and I knew this sign was not good for my anticipated reunion with my rack.

The DD had two helos in the hangar, so there was no way for us to change an engine of a board. After spending the morning considering the options, our battle-group staff decided to detach the ship from the exercise, go to Norfolk, and crane us off.

As the DD's air det hooked us up with racks, it was time for a crew-gear inventory. I was the only one of the three of us who had a wallet, ID card, credit card or cash ($29 to be exact), and we were headed to Norfolk for an unknown length of time. The DD's air-det was awesome, hooking us up with toiletries and newly purchased underwear from the ship's store.

Our home squadron arranged for the crane-off and sent a rescue det from Mayport. Day four of our alert launch saw the rescue detachment installing our engine, with the help of the local HCS squadron (I never could thank those guys enough).

Days five and six saw us repeatedly FCF the aircraft. I was the det MO and, fortunately, was FCF qualified. We finally got the profile out without a chip-light (from the factory-new engine) on the sixth try.

Woohoo. On day seven, we were out of there. Norfolk is fine, and I saw a bunch of friends, but the three of us really wanted to get back to our favorite toothbrushes. I got a rough idea where the boat was from the home squadron but couldn't raise the ship on the pots line to talk to the OinC. I queried the crew, and we decided that, because the weather was OK for now (forecasted to get worse), we should reposition to Cherry Point and call from there. At least, we would be closer and could move (before the weather) when we got in touch with the boat.

After an uneventful flight to Cherry Point, I got through on the phone to the boat. The plan was to use a CG, which was halfway, as a communications-relay lily pad. Our FFG was beyond our shore-to-ship SOP distance. The CG was expecting us to check in, make a quick call to our squadron CO for a "sounds good to me" approval, and then go. By now, the weather was scattered T-storms everywhere and looking worse by the minute.

During man-up, we noticed a lot of air-wing jets had bingoed into Cherry Point because of the weather. Hmmmm. Well, we're helo guys with radar, and the boss said the weather at the ship was OK. Heck with it, we're going!

Most of the flight was spent working the radar to avoid the continually deteriorating weather. The CG lily pad/communications guard worked great, and we pressed on to mom.


 

BNET TalkbackShare your ideas and expertise on this topic

Please add your comment:

  1. You are currently: a Guest |
  2.  

Basic HTML tags that work in comments are: bold (<b></b>), italic (<i></i>), underline (<u></u>), and hyperlink (<a href></a)

advertisement
Click Here
advertisement
  • Click Here
  • Click Here
  • Click Here
advertisement

Content provided in partnership with Thompson Gale