HOW TO BE MARRIED TO A MARINE FIGHTER PILOT--A Marine Corps pilot's wife: F-4s, F/A-18s and aviators from my perspective.
Showing posts with label Mike Sullivan. Show all posts
Showing posts with label Mike Sullivan. Show all posts

Tuesday, November 30, 2010

Aviator Brief VII: No Guts, No Glory

On a day of such crappy weather even the seagulls stayed grounded on the grass between the runways, Colonel Sullivan turned for takeoff from Runway 7 at MCAS El Toro. Pushing forward the throttle and kicking in the afterburner, he lifted off from the surly bonds of earth into a flock of seagulls startled by the decibels of an F-4 turbine.
 
Three hundred seagulls funneled into a jet engine were a problem of compressibility. Blood and feathers, guts and bones don’t pack well into the relatively small space of a Phantom’s engine.
With one turbine destroyed and unsure of the damage to the other, the colonel looked at the land near the base. If the jet stopped being able to fight gravity and he had to jump out, the hunk of steel and explosive jet fuel would twist and burn into homes, schools and/or stores. Not a good option.
 
Good pilots make good decisions in the worst of circumstances. He pointed his radome south and flew the crippled bird with its many mangled birds to Yuma, Arizona, where he managed to land safely.
 
The CO of the squadron appreciated the decision to divert, preventing a potential public relations disaster. He also appreciated the skill of the pilot in preserving a valuable piece of machinery. Engines could be replaced. A plane crashed and burned was unrecoverable.
 
Yuma, the day Col. Sullivan landed, had a high of 105-degrees. Yuma registered 105-degrees the next day, too. The plane, with its multiple bird strike, FODded engine, sat on the flight line in the heat for two days.

Then the maintenance officer, Snatch, flew to the desert to inspect the extent of the damage to the engine.
 
The guys in Yuma working on the tarmac were happy to see him. A wide area had been cleared around the colonel’s aircraft. No one wanted near the miasma of gull guts rotting in the gutted turbine blades. 

Neither did the hapless maintenance officer.
 
Snatch got the guts. Col. Sullivan the glory.

I never thought about this story much before re-reading it this week, but the troops were the ones who had to use the pressure hoses and replace the engine in the Yuma heat with the smell to high heaven. The AMO would have supervised, and had to deal with the smell, but the guts were on other hands. Snatch says the plane still stunk for awhile afterward, which would have made the airframe one of the least favorite to win in the “What am I flying today?” lottery.

So who am I in my life? Am I the person who in the nick of time and with derring-do flies a plane away from those who could be hurt by it if it crashed and burned? Am I the maintenance officer who has to supervise the rotting guts of the disaster and repair it to fly again? Or am I the troop on the ground who actually gets my hands dirty fixing what the magic flyboys wreck (even when it is no fault of their own?)

I’d never have made a good pilot. My reaction time is slow in an emergency. I don’t panic, but I don’t automatically react with split second decision making. In a disaster, time slows waaa-aay doowwwnnnn. I usually get to a good solution, but I’m afraid the plane might be in twisted bits if I were at the controls. I’m no Col Sullivan.

I would have made a good maintenance officer. I like to know how things work and I like to fix my life and those of my friends. I’d much rather tell someone else how to fix things than get seagull guts all over me. I don’t much like taking orders.

So I’d probably not make a very good troop. God bless them for what they do and the shit they take. The troops help keep the derring-doers and the other pilots like my husband up in the air and back down again for safe landings.

So who are you? In your life and relationships do you fly through bird flocks, but recover well? Do you analyze a situation and figure out how to fix it? Do you like to give orders or just follow them?

Saturday, February 23, 2008

Aviator Brief III: Squadron Jobs (continued)


The Ops O--Operations Officer--held a lot of power in the squadron because he wrote the flight schedule. Everything depended on getting as many hops--flying the planes--as possible.

The AMO--the Maintenance Officer, Aircraft Maintenance Officer--held a position of respect. As stated before: Everything depended on getting as many hops as possible. If planes were broken, they couldn’t be flown. A good relationship with the man in charge of the troops who fixed the planes the pilots flew was therefore essential.

The Safety Officer’s job also involved keeping planes flying--safely. The ASO--Aircraft Safety Officer--had done his job when there were no accident reports for the quarter, the year, or so many hours of planes in the air. Somehow, AMOs and ASOs had different ideas of how to accomplish this objective. A Safety Officer who micromanaged every little hydraulic fluid leak and stuck valve into a downed airplane created negative attitudes in the AMO, the pilots who wanted maximum hops, and the troops. An airplane taken off flight status meant a pilot and a RIO not flying it. It also meant the troops had to work longer hours repairing it.

Colonel Mike Sullivan maintained, “If twelve aircraft takeoff down the runway everyday, nothing else matters.” Corollary: When all the planes fly, the troops are happy--because when planes are in the air, they don’t have to be fixed, loaded, unloaded, or fueled, and ordinance guys could lift weights and the maintenance guys could jaw-jack, shoot the breeze, and bullshit each other--what they liked to do when all the planes were in the air.

As a Marine wife, I had my own planes to ready for takeoff down the runway everyday--my husband and children. In the early days, I didn’t work outside the home--notice I did not say I did no work--and so my squadron job was support for the troops, my troops, my guy and our three little girls.

I already knew how to bake bread and make cookies, but learning to cook a family meal took a very different skill set and little praise. Many would ooh and aah over homemade wheat bread. Cookies? The cook was a hero who made cookies. But no one applauded casseroles and baked chicken. More likely they’d whine, “Macaroni and cheese tuna casserole, again?” or “I’m allergic to succotash.” No one was really allergic to corn or lima beans in my family; they’d just break out in a bad case of the I-don’t-want-to-touch-those-with-these-lips-itis.

I turned to my main resource of support and information--just like the squadrons are supported by H&MS--other wives. Potlucks are the best way to acquire new recipes--they’re time-tested, family tested, and almost always easy. Besides, at a potluck there was lots of food, but I only had to make one thing; and there were lots of sympathetic ears.

Food to eat and friends to listen. Can’t get much better than that.