Jet Wake Turbulence: Distance Ain’t Enough.

Sneaking up behind me, are you? Here’s an infrared view you might need to heed: not the hotspots, but powerful the twin horizontal corkscrews of air current swirling off the wingtips of my jet. They’re wily, dangerous, and not to be trusted.

According to the Flight Safety Foundation, the vortices from a jet can have an internal rotation of up to 300 feet per second and often extend between 2 and 10 nautical miles behind a jet aircraft. The twin tornadoes–that’s literally what they are, horizontal but spinning powerfully–sink at a variable rate, between 300 and 500 feet per minute to an altitude  between 500 and 900 feet below the aircraft’s flight path and can persist for three or more minutes depending on the meteorological conditions.

That’s the problem, but hardly the full situation. Add to this hazard the closely constrained flight path of jet traffic in terminal areas. For instance:

Approaching from the east, you’ll have a traffic stream from the west as well converging on the same runway complex. Not unusual as far as airports go–except that San Francisco International has less than the standard distance separating the two parallel runways. The FAA has waived the normal lateral separation, but you’d better keep that in mind nonetheless because that also means less than normal separation from the vortices of the aircraft next to you. Remember the outward spreading motion of those two tornadoes?

This guy could be your dance partner all the way down final–and if he’s next to you, you aren’t entitled to the separation you’d get if he were ahead of you. Mostly, ATC will “advise” you to “use caution” for the heavy on the west runway, workload and time permitting–but they don’t have to.

And time and workload may not permit any advanced warning, and adverse weather can shroud the entire scene anyway:

Look at the inset on the bottom right corner: Seattle (one of my favorite destination cities!) has three parallel runways grouped together, and you won’t be told which of the three runways you’re landing on until you turn base to final about three minutes from touchdown. Would it make sense or even be possible to keep you informed of the heavies on all three inbound tracks? Add to the mix the typically obscured Seattle visibility, plus the added workload of programming and validating the FMS  sytem approach waypoints at the last second demanded by the late runway assignment and is there a possibility of situational awareness overload, on final approach: was that a heavy in front of us? Or on the outboard runway?

Bring that back to San Francisco, where the standard runway separation is “waived,” like in MSP and many other cities. Now you’ve got a “buddy” laterally whose wake turbulence is drifting outwardly–just as yours is–and just because he’s not a “heavy” doesn’t mean he can’t roll you.

The ICAO worldwide “recommendation” for separation between a “heavy” and a “medium” following aircraft  (say, a 747 and a 737) is 5 NM (9.3 KM); between two heavies, 4 NM (7.4 KM). But the wild card not even mentioned in the separation rules is configuration and maneuvering: simply put, a “dirty” jet (flaps, gear) creates a nastier wake than a “clean” jet, and maneuvering distorts weight. That is, if I level off my 160,000 pound 737 with an addition one-half “G” force, I add to the effective weight another 40 tons of effect. And we’re a medium jet–imagine a heavy maneuvering dirty adding to his effective weight and wake.

That’s the science, now here comes the art. You know the reported winds at the field, but that’s a red herring: your encounter with wake turbulence won’t happen on the field. You need to be aware of the winds on approach, at your altitude. If the lateral wind at your altitude is blowing into the other jet’s wake, here’s what can happen: if the drift equals the outward spread momentum of the wake–and you have to figure the “dirty,” “maneuvering” wild cards mentioned above–the effect will either be to move the wake away more rapidly, or freeze it in place till it dissipates. Which is it?

You can’t see wake turbulence. You can’t be sure where it is, or know it’s strength based solely on the aircraft designation. And sooner or later, you’ll find yourself in it despite your best, most diligent precautions. What are you going to do, captain?

For a true jethead like me, the first answer is always speed–but not so fast (pun intended): you’re configured with restrictive maximum flap speeds. If you’re in a final configuration with 40 degrees of flaps, you’re limited to 162 knots max. But the second instinct is valid: power.

But power alone is only part of the answer: what you’re not doing is going down. Why not? Because we know the vorticies are sinking. If we remain level or climb, we’ll escape the effects. What are they?

The Flight Safety Foundation survey of hundreds of wake turbulence encounters reveals uncommanded roll in trailing aircraft of up to 45 degrees at altitudes below 1,000 above the ground. One thousand feet is another magic number at my airline: stabilized approach  (on speed, on altitude, power set) is mandatory from 1,000 feet to touchdown. On glidepath–not above or below; not accelerating or decelerating, power set to flown speed and stable. And certainly wings level.

Which brings up the next problem of two major headaches you’ll instantly own. First, the right amount of counter-aileron, even if applied prudently, in many jets will bring up the wing spoilers to drop the low wing rapidly, inducing adverse drag, requiring more power.

Second, the option of climbing or even flying level is constrained by the published missed approach: protected airspace may be below you if you are above the missed approach altitude. And laterally, not only is there often parallel traffic, there’s also dangerous terrain you must always monitor and stay clear of:

If you encounter wake effects in a level portion of the approach segment, prior to the aircraft ahead descending, at least you know his vortices will descend eventually below you and in this case, you normally feel the “burble” which now cues you: if the winds are keeping his wake aligned with your flight path, on glidepath you’re likely to fly into the tornadoes again when you’re slow and configured with speed-restricting flaps. Now look at the “mileage separation:” still think distance alone is enough? Still committing to the glidepath?

All of that doesn’t even consider the added, inevitable spoiler in every approach: weather. There’s more than terrain and aircraft for you to avoid in a very constrained airspace.

There’s really only one good answer: up. And “up” may be a s simple as “no more down,” meaning a stopped descent or a slight climb to exit the effects. In any case, if you’re below 1,000 feet you’re no longer “stable” per the mandatory requirements. If you’re above 1,000 feet, you’ve just been cued that the mileage interval, given the meteorological conditions, nonetheless has left you vulnerable to the adverse effects of wake turbulence–and you’re not going to proceed.

Which means, in the immortal words of my old friend the Chief Pilot at my airline addressing my 1991 class of Captain’s “Charm School” (officially, “Captain’s Duties & Responsibilities”) as we sat rapt: you’re going to “get the hell out of town.” Amen.

Back in the cabin? Expect the usual complaints about the delay for the second approach, plus a regular dose of exaggerated “there I was” tales about their wake turbulence encounter. So, don’t tell them–if you’ve done your avoidance and even escape properly, they’ll never know you even had a problem, which is the ultimate goal anyway: detecting and avoiding the problem in the first place.

The end result is, what they don’t know won’t hurt them, because you won’t let it. And that’s kind of why you get the privilege of flying the jet in the first place, isn’t it?

Winter Flying: Faith and Defiance.

I can’t decide if winter flying is is one long act of defiance, or shorter acts of combined faith. On a cold January day with an icy, raggedy ceiling and needle-like freezing rain rasping against the fuselage on taxi-out, on board it’s a steady 75 degrees. People aboard reflect the destination, not our departure point–and act of faith on their part requiring an act of defiance on mine.

It’s actually a worthy challenge, bringing all of the details to a successful conclusion: flight planning, routing, de-icing, preflight, taxi-out and pre-take-off de-icing. There’s a puzzle to assemble, jagged pieces of holdover times for de-icing fluid, precip rates and types–you know what’s reported, but you deal with what’s actually happening–and it’s up to you to account for the difference. Take-off performance degrades; weight limits based on the restrictions of leaving, but with due diligence to the weather conditions 1,200 miles south.

Boeing has given us a marvelous machine that will wake up encased in ice, but in a matter of minutes will operate from the ice box to the tropics. Not magic–just a lot of grunt work by a lot of people.

It’s a lot slower, but more than the temperature is involved: there are more requirements, plus people and machines work slower in the cold. As they should be expected to do, but which often results in frustration for those whose involvement is limited to riding the jet rather than trying to fly it safely. Sorry.

But eventually, we get to this:

Again, that’s going to be slow, too, by necessity. But be patient: the destination must be worth the trip, right? But inevitably, the factors a passenger plans to escape by air don’t make that escape easy.

Half the battle is getting into the air–where the other half is usually just as challenging. Again, the same crud that you want to escape packs a punch from the surface to the stratosphere. We’ll deal with that, too, at 300 knots, or maybe 280 if it’s bumpy. Already told the cabin crew to remain seated till I call them, when I’m sure we’re in safe, stable air. More griping from passengers, I know, but they’re not responsible for not putting a crewmember through a ceiling panel.

This is how it might look if anyone checked ahead (I did) so it wasn’t surprising face to face, really. Which looks more like this, and nobody’s getting to paradise till they work their way through this frontal line.

Eventually, we win: the further south we go, the more miles we put behind us, the weather–and the escape–become reality. You begin to get a glimpse of paradise with your 320 mile digital vision. The 20-20 eyeballs show the passage from land to water, a sure sign of warmer days for 160 souls on board, patient or not.

Soon it’s all blue, with ghostly outlines below that carve the indigo into brown and green, lush islands poking above the mild, warm seas.

Nassau, the Bahamas, straight ahead. Power back, begin the slow, gentle glide from seven miles high to sea level. More islands slide silently below the nose. Never tire of seeing the parade of blues, browns, greens; paradise.

Where’s the snow now? The icy grip of winter? Escape–by the lucky hundred and sixty aboard, each with their own getaway plan, winter runaways we eagerly aid and abet: someone has to break free, to teach winter a lesson.

A world away, if only but the blink of an eye in a lifetime, it’s nonetheless an eyeful. I’m happy for those who’ll stay, at least for a while.

Welcome to Nassau. For me, it’s a few moments of sunshine and sea air on the ramp while ground crews unload cargo, reload, refuel and get us turned around and ready for launch back to the north. Too soon, in a way, but not soon enough in another: this isn’t my escape–it’s my job.  From which, for the vagabond pilot, home is the escape. Will be back here, back and forth, all winter.

He’s headed home, too, a longer way back, but with a couple hundred aboard not facing the cold quite yet. But likely missing the scenery shrinking below as we climb and arc away to the north.

So long to paradise, hello radar scan; fuel burn, overwater navigation, peaceful cruise until you face the enemy line you already slipped through once today. Still there, waiting. The sun gives up, slips into the muck and so do you, both promising another trip around the globe another day.

There’s the final act of defiance, or maybe faith: through the choppy, sleet-streaked darkness, at 200 knots, toward the runway you better know is below the 200 foot ceiling.

Then it’s all about home, after appeasing the winter gods (“We brought at least as many back from paradise–you can ruin the rest of their season, plus make them wistful for the tropics the rest of the year!”) yet again. A healthy respect goes both ways; careful defiance, faithful flight. Starts again tomorrow.

Un-Pilotish: Just Say No.

Top of descent with a hundred knots of tailwind. You’ve been asking for a descent for the last forty miles with no success, and you know why: outbounds are climbing below you and worse, they’re staying low nose to nose because of what’s been a tailwind for you since the west coast–but which would be a headwind for them westbound.

So it’s the double-whammy: high, and hot; closing on the altitude crossing restrictions are cramping the descent algorithm–there’s not enough “forward” left to to execute a civilized “down.”

“Cross Fever at 11,000 and 250 knots,” comes the ATC instructions, and I immediately think of a captain I used to fly with in the 1980s who would have, without hesitation, answered, “We can do it–but we’ll have to leave the airplane behind.” Instead, I just say, “Unable.”

I know, I know: we probably could make the crossing restriction, but why play the odds? And if you’ve flown long enough, you know the odds are about 90% that this ain’t the end of the story: the Dreaded Hypotenuse. That is:

You’re going to get cleared direct to another point, shaving off the miles of “forward” you were counting on to execute the “down” at a civilized rate–with the same crossing restriction. Last month up in New York Center I heard a commuter pilot on frequency asking for relief on a crossing restriction he had innocently enough accepted fifty miles back: “Can we get relief on that crossing restriction?”

Without missing a beat, NY Center replied, “Absolutely not.” Now who wishes they were a heretic–or wants to leave the airplane behind?

And there’s the problem: “unable” is, well, un-pilotish. Which is actually not a bad thing to strive for. Here’s what I’m thinking: for some reason, the “cultural” aspect of being a pilot has insidiously taken on a life of its own: we can do anything, best any challenge, defy gravity, wear ridiculously big watches

–which is a latent “Flavor Flav” urge driving many pilots, which I’ve never understood–and sometimes we forget in the “never say no”  to a challenge mindset that one person we should more often say no to is ourselves. Still with me? Let’s have a new captain flashback.

Fog creeping up the Rio Grande Valley like a ghost; moonless night dark as space. Tons of gas, literally, and paper calculations that equal one good approach to minimums, then divert to San Antonio. Tidy plan. Works well on paper.

Unable? My ass: can do!

After the first missed approach (wow, the ceiling really is below the minimum descent altitude) the new captain consults the F-100′s “Progress–Fuel Predict” readout, which shows enough endurance for a second approach–then a divert to San Antonio.

Today’s captain voice-in-the-head, some 20 years more experienced, says, “Tell yourself no, stupid!” Divert now. For the record–then and now–I’ve never had a big pilot watch, or aviator sunglasses, or a creepy mustache, or any of the other silliness that seems to be part of the pilot stereotype. But I did have that “never back down from a challenge” mentality that I guess lands you in the cockpit in the first place.

“We’re requesting one more ILS, with clearance on request to San Antonio on the missed approach,” the intrepid First Officer relayed to the Approach Controller. Fine, thought the new captain; we can do this.

Second approach, same result: pea soup. On the second missed approach, Departure control sends us to Enroute: “State your request.”

We’d like to go direct San Antonio at 14,000′. San Antonio is now 1/8th mile visibility in fog.  You planning to hold?

Actually, planning to just say no–first to myself, then anyone else offering an uncertain gamble, challenge or no, in flight from now on. How unpilotish–and yet, common-sensical.

We raced the sinking temperature-dewpoint spread blanketing the state south to north with fog and landed in Austin with less fuel than I’d ever seen on the gages before–although my base Chief Pilot, over a couple of beers, told me he’d actually landed with less. He’s a “say no” guy now, too.

And that’s the whole deal: say “no” early–and often. Let Air Traffic Control manage their own airspace congestion without expecting an airshow on your part. Talk yourself out of any bad bets before anyone can even suggest you play the odds.

And above all–avoid the pilot stereotype.  It really doesn’t fly well, despite the mythology.

The WordPress.com stats helper monkeys prepared a 2012 annual report for this blog:

Here’s an excerpt:

About 55,000 tourists visit Liechtenstein every year. This blog was viewed about 170,000 times in 2012. If it were Liechtenstein, it would take about 3 years for that many people to see it. Your blog had more visits than a small country in Europe!

Click here to see the complete report.

Flying into Hurrcane Sandy’s Wake

You get the call from Crew Schedule. You don’t have to take the flight–but you do: it’s time to bring jets back into the New York metro area, ravaged as it is by Hurricane Sandy.

Means a different kind of thinking for you: more fuel (you’ll take any excuse for more fuel, won’t you?) for more loiter time and options depending on the weather, because you know the navigation aids and ground-based approach equipment has been damaged or may be without power.

There are twenty deadheading crewmembers on the flight roster, needing to get home, plus a half dozen others trying to commute to the three crew bases there (LGA, EWR, JFK) not to mention tons (literally) of backlogged cargo waiting to head east. All of that raises the jet’s zero fuel weight, but fuel is primary. You get hit up by commuting crewmembers–”Can you agree to land with less fuel?” No, I shouldn’t, I can’t, I won’t. You’re the captain, so you’re the asshole; you’re the asshole, so you’re the captain: all you want to see when the gear goes down on final approach is plenty of fuel to go somewhere else if need be. What a dick.

The First Officer today is one of the guys I really like flying with: serious, quiet, pragmatic; ex-Navy fighter jock, good guy. He’s one hundred percent behind the “Fuel is God” philosophy. Makes it easier.

We blast across the southern United States, bang a left at Atlanta, head for Tidewater Virginia then up the coast. Sandy’s loafing her way north and west, leaving the curved cirrus as her calling card up the eastern seaboard.

We grab the high ground, the 40,000 foot level to keep the fuel burn low and the tailwind high. As soon as we turn north over Norfolk, we begin to pick up Sandy’s claw marks along the coastline: even from seven miles up, starting around northern the Maryland coast, the shore looks as if a giant hand had raked the sand from right to left, east to west, as Sandy’s hurricane-force roar washed the sea and sand inland.

Lower now, abeam Atlantic City, New Jersey, we’re peeking through cloud breaks in Sandy’s sloppy remnants, and the view is ugly: the shoreline is swept clean of anything man made, and you know from a hundred flight through here that the shoreline was much more “humanized” until Sandy clawed it clean.

Sinking through ten thousand feet, the disaster takes on a detailed face: boats piled in front of houses; the normal geometry of streets and blocks skewed by wreckage, things that don’t belong; jumbles of homes, cars, boats; you name it.

Sand driven blocks inland. Cars strewn akimbo. Roofs ripped off. No lights; no warning lights–and no navigation signals, due to no electricity. You see the couple of blocks burned to the ground by uncontrollable gas fires.

Humanity, flashing by at 160 miles per hour. I don’t have time to look–but I can’t help seeing the destruction below. These photos are courtesy of a deadheading flight attendant, taken sideways from the “A” seat just forward of the left wing.

No worries up front in the 21st-century jet: our navigation and approach guidance is all based on satellites, processed on board and projected right in front of my fat face:

We lumber to our gate, with a mixture of relief and satisfaction: we’ll get the normal jet service up and running once again, get people moving, unstranded, reunited, home.

And we’ll ferry another 160+ souls westbound, away from the storm and the shipwreck that is the northeast coast. There are crowds inside “Fort Kennedy” who are waiting like refugees to move west, to go home. We’ll do the fuel numbers, the flight performance calculations, the take-off numbers down to a rat’s ass to make it work–and work right. If; no–when that makes me the asshole again, so be it: we will be safe, we will fly smart.

We’ll get that bird’s eye, god’s eye view of the coast one more time, at dusk, and try not to worry–but how can you not?–that in the gathering darkness, there are few if any lights below. We put that behind us at .8 Mach, but the human face doesn’t go away no matter how high you climb or how fast you go.

Can’t help but feel for those left behind. And those you know, stalwarts of Jethead like Miss Giulia and her husband Mike, the voice of Jethead Live: the remnants of the super-hurricane are headed their way; Peggy Willenberger, stormchaser who has made such extreme weather her stock in trade; Cedar Glen–didn’t he mention Ohio once, now taking a pounding?

And the millions left behind, salvaging what they can, rebuilding. We’re a quiet ark sailing westward, away from the storm, to a different and better now for the lucky ones making their escape.

Keep the fires burning; navigate, light the way west. Do it right–that’s your job, your part in this journey. Follow the night sky home.

JetHead Live! with Fighter Pilot & Author Ed Rasimus

Ed Rasimus, author and a fighter pilot

with 250 combat missions over North Vietnam

discusses his role as co-author of “Fighter Pilot.”

To download and/or save, click here.

Never miss an episode–catch up on previous interviews.

Just click the iTunes icon below.

Wolfpack Flight Revisited

Thirty plus years together flying in the Air Force and the airlines,

the Wolfpack Flight looks back–and forward:

To download or save, click here.

A Wing and a Prayer, and the Everlasting Moon.

Only poets and saints have ever flown like this, riding a wing and a prayer. Darkness like sadness, spread to the end of the world, save the glow of cathode ray tubes painting the hearbeat of the seventy ton schooner, riding the howling eastbound jet stream.

That’s always a rush, surfing that gale, especially this time of year. But that’s what it takes, that’s what the 160 folks in back expect; never mind the details of turbulence and winds and fuel flow–those are yours to deal with alone. Just the way you like it.

You catch a glimpse back there now and again, but the view’s better ahead; quieter, a vortex of unseen electrical, pneumatic and hydraulic function, the lifeblood of the jet, blooming through the animated tapestry sprawled from bulkhead to bulkhead and overhead and nowadays you don’t know where the jet ends and you begin. Not that it matters: you’re comfortable in your second skin, aluminum and titanium, blood and bone–it’s one and the same for now.

And in the reassuring light of the cabin, what they don’t know won’t hurt them: through the night, an alabaster glow fires up the undercast ahead, swelling and spreading like a false dawn. The spectral blister swells to bursting and time reels backward for you–the western Pacific; the South China Sea, a world of time and distance ago.

Dark as deep space, a cloud deck below, the endless nothing above. Jets everywhere, formations in and out, stacked and you busy with courses and altitudes, your jet’s performance–then that ghostly glow below; angry rising–before you think you say it, as soon as you do you’d beg the words back on your life: “What the hell is that?“

Ivory-bone light melts up through a swirling veil of striated cirrus laid like a blanket on the Korean countryside frozen cold in the dead of winter.

“The moon,” comes the deadpan reply from another aviator. And you just let that smolder and die in the darkness; betrayed by the indifferent moon climbing it’s sky arc just like you did yours. What the hell–we’re pals–we’re going to be, through thousands of air miles over years and skies around the globe.

And it’s the aviation childhood still: less than a thousand hours of flight time; everything’s a wonder, an answered prayer or a silent wish playing out across a thousand miles at Mach speed. Like today: major league tailwind drives the groundspeed up to nearly 700mph.

Unseen from above, the miles past so fast sometimes. And that glow below, now a thousand years later and as many miles hence, you just know. Time to start down–just as your old friend climbs up. We’ll trade spots in the sky, share one more curtain call.

And surely we’ll cross paths again, however many more times we can. No surprise now–but just as stunningly bright as ever. It’s all too familiar, but in a good way: a wing and a prayer and the everlasting moon; the the essence of flight that never loses its brightness.

From flying fighter jets in the Netherlands to the captain’s seat on a KLM jetliner, Captain Martin Leeuwis has done a lifetime of amazing flying.

We go one-on-one with him on our audio podcast next week.

And later this month: 3-time space shuttle astronaut Mike Mullane joins us on JetHead Live.

Subscribe now for updates!

Podcast: What’s it like to be a Boeing-777 Captain?

Ever wonder what it would be like to be a Boeing 777 captain for a major airline?

Want to know how the 777 stacks up against the DC-10 and MD-11 from a guy who’s flown all three?

Here it is:

 To use your own player: click here to listen (or right click and “save” to download).

Don’t have an audio player?  Click here to listen on Pod-o-Matic!

(running time approximately 28 minutes)

Wednesday:

From flying low-level fighters in the Royal Dutch Air Force to the captain’s seat at KLM,

Captain Martin Leeuwis shares his flying stories on JetHead Live!

Also Coming Soon:

What’s it like to fly the space shuttle: my interview with 3 time shuttle astronaut Mike Mullane. Subscribe now!

Pilot Report: Boeing 737 vs. McDonnell-Douglas MD-80

Now that I have nearly a thousand hours in the left seat of the Boeing 737-800, and having as well over 15,000 in the MD-80, I feel qualified to make some judgments about how the two stack up against each other.

For me, there’s one hands-down winner. I’ll get to that.

But first, looking at it from a hands-on pilot perspective, let me say what I think are the crucial factors in both jets, then compare them. And I’ll do it in order of importance from my line-swine pilot view:

1. Power: never mind the technology difference between the General Electric JT8D turbo fans on the Maddog and the CFM-56 high-bypass fans on the 737. It’s the thrust difference I want in my right hand when I’m trying to lift 170,000 pounds off a runway. And technology aside (I’ll get to that), the three full power options (22,000, 24,000, and 26,000 pounds of thrust) plus the bonus kick up to 27,000 pounds per engine on the 737 for special use beats the snot out of the 19,000 flat rated and standard de-rated engines on the MD-80. Yes, the -80 weighs less than the 737 (max of 150,000 vs. 174,000 pounds), and no, I don’t have each plane makers’ specs, but the thrust-to-weight performance from the left seat feels substantially more secure and significant from the 737.

You notice that right away when you do a static takeoff with the 737 at all weights: you’ve got buttloads of giddyup (I think engineers call it “acceleration,” but then they don’t actually feel it on paper versus in the cockpit blasting forward–that’s “a buttload of giddyup”) shortening  those critical moments of vulnerability between brake release and V1.

I have no idea what engineers think of when they look at thrust and take-off advantages, but any pilot with experience knows that those seconds before reaching flying speed are the most vulnerable, particularly close to max abort speed, because I’d rather take any problems into the air than have to wrestle them to a stop on a runway. The MD-80 has good smash at mid to light weights, but in crucial situations (Mexico City, for example, or on a short runway on a hot day) the 737′s CFM56′s rule. I need the shortest possible period of on-runway vulnerability; I know engine hot-section limits and longterm life are important too, but the CFM56 achieves better on-wing engine endurance in operation than the JT8Ds, year over year.

Ditto for a go-around or windshear options: the MD-80 is famous for it’s slow acceleration–I’ve been there MANY times–and when you’re escaping from windshear or terrain, I can promise you the pucker factor of the “one, Mississippi, two Mississippi” on up to six to eight seconds will have your butt chewing up the seat cushion like horse’s lips. Not sure if that’s due to the neanderthal 1970′s vintage hydro-mechanical fuel control (reliably simple–but painstakingly slow to spool) or the natural limitation of so many rotor stages. But the 737′s solid state EICAS computers reading seventy-teen parameters and trimming the CFMs accordingly seem to give the performance a clear edge. And a fistful of 737-800 throttles beats the same deal on the Maddog, period. Advantage, Boeing.

2. Wing: let me go back in time. I also flew the F-100 for a couple years as captain. That was a great jet, with a simple wing: no leading edge devices. Coming from jets with slats the feel was clearly different on take-off, where there was a distinct (if you’re a seat-of-the-pants guy, and that’s all I’ve ever been) translational period between rotate and lift-off due to the hard wing. Ditto in the flare and in some reversals in flight like on a go-around. Not a bad thing, just something you had to anticipate, but not a warm-fuzzy in the seat of your aerodynamic pants.

Stretched jet, stretched wing.

That’s a good analogy between the Boeing versus the Douglas wing: you feel the generous lift margin in the 737. That’s because when Boeing stretched the jet to the -800 length, they expanded the wing as well. That wing was already loaded much lighter than the DC-9 wing which Douglas didn’t enlarge when they added to two fuselage plugs plus about 15,000 pounds to the MD-80. Longer and with better cambered  (look at the DC-10, and no dihedral) airfoil is the Boeing design and I’m grateful for their foresight and superior engineering–especially at the top end of the performance envelope: you need anti-ice? No problem–turn it on. The Maddog? Better be 2,000 feet below optimum, or prepare for stall recovery–and anyone on the -80 fleet knows I’m not exagerating. Wing performance? No contest: Boeing.

3. Handling: again let me go back in time. Flew the T-37 like every new Air Force pilot up until recently–then moved on to the T-38. Using standard Tweet inputs on The Rocket would bang your helmet off the canopy because of the boosted flight controls, giving you 720 degrees of roll in a second at full deflection.

That’s the 737 compared to the MD-80: no aileron boost on the -80, and little help from the powered rudder–because of the long fuselage length and relatively short moment arm between the vertical fin and the MAC (Mean Aerodynamic Chord), the rudder seems to only impart a twisting moment that’s pretty useless. So it’s a wrestling match for roll control, in and out of turns with the -80.

I still tend to over control the 737 in acute roll situations (e.g., the 30 degree offset final at 300′ AGL required in and out of DCA) due to previous brain damage caused by years of arm wrestling the MD-80 around tight corners. But with the 737, the seat-of-the-pants security of that generous wing is apparent at all speed and altitudes and the hydraulic aileron boost gives you the muscle to command a smooth and prompt response. Handling? It’s all 737 for me, including on the ground: new MD-80 captains will need Ibuprofen to counter the wrist strain of the nosewheel steering, two-handed in tight spots. I don’t miss that at all.

4. Cockpit layout: okay, give the -80 its due–that was one comfortable nest once you got settled. But that’s as far as it goes for me. Yes, I know the 737 kitbag position is inaccessible. But American Airlines is the first airline certified by the FAA for iPad use from the ground to altitude. Kitbag, what’s a kitbag?

MD-80 left seat–HSI? Where is it?

Trade-off? The MD-80 HSI is obscured by the control yoke. Are you kidding me? Like you might need lateral situational awareness for trivia like, navigating? Flying an approach? I spent 20+ years working around that human factors engineering failure–I’m grateful for the Boeing engineers who gave me seven 9″ CRT flat plate displays with every parameter I could want displayed digitally and God bless them all–a Heads Up Display! Lord have mercy, even a simpleton has a crosscheck in that jet thanks to the God of HUD.

The 737 doesn’t have the elbow room you might like and everyone who I fly with who has come off the big Boeings (757, 767, 777) gripes about that. Fine. I’m all about performance and the flight displays, computers, communications and advanced Flight Management Systems in the 737 avionics suite beat the pants off of the 75 and 76–and the HUD tops the 777 as well. Nuff said: gimme the Guppy cockpit over the Maddog. Boeing put everything I need at my fingertips, and it’s all state-of-the-art, whereas Douglas engineers threw everything they could everywhere in the cockpit and slammed the door.

My 737 home.

So there you have it: power, wing, handling and even by a narrow margin, the cockpit too. I’m a Boeing guy, back from wayward days flying Douglas metal from the DC-10 to the MD-80. In my experience as a pilot, in my hours in both Boeing and Douglas jets, I’m grateful to be flying the best jets in the sky. Now you know which are which.

Flying into the Nor’easter October 29th, 2011: juggle a thousand moving parts.

Ah, the point of universal equality: all of the alternates you’ve loaded into the Flight Management Computer doing a thousand calculations of time, distance, airspeed and fuel flow have reached the same number: 9.5. Which is 9,500 pounds of fuel on the deck at each–if we leave the holding pattern we’re in over the Shenandoah mountains of Virginia.

Yes, that’s a blanket of snow down there, and uncommon October dumping of thick, wet flakes wreaking havoc on the surface: fall foliage still on the trees gathers the fat flakes in a blanket that snaps branches and snags power lines.

The alternates now line up for a second with the same arrival fuel and they’ll tick down that way as we hold, geographically in the middle point between Baltimore, Syracuse, Boston and our destination, LaGuardia.

You tell the First Officer, “When the fuel prediction reaches 7,000 fuel on deck–we divert.” Because 7 eventually shrinks to 5 due to the air traffic glut all competing to get to either a destination or alternate. The fuel prediction should come with a little caveat, “results may vary.” We ain’t stupid–done this a few times before.

Our flight 9409 from Miami checks in on frequency, entering a holding pattern. “We have the Miami Dolphins on board,” the pilot says, pleading with New York Center, “Anything you can do to get us into any of the New York airports would be appreciated.” Must be coming up to play either the Giants or the Jets.

We laugh in our cockpit. “We have the Omaha Women’s Bowling and Quilt Team on board,” I say cross-cockpit, “anything you could do . . .” But New York Center has no options: “Diverts allowed south only,” comes the answer. “Or maybe we can get you Boston or Hartford.”

Crap–looks like Syracuse is out for us. Didn’t want to go there anyway–too small, slow turnaround–but it takes away from my perfect geographical display of options. I like options. Okay, add Richmond. The First Officer is busy reading out loud the terminal forecast for our various divert options, but I tune him out–I don’t give a damn about the forecast an hour ago for an hour from now. But it gives him something to do.

We’re cleared down track, exiting the holding pattern–but don’t get your hopes up: that just means someone in the holding stack 70 miles ahead finally said “uncle,” reaching their fuel bingo, and diverted. A dozen jets are heading for your stack and the controller is shooing you off to the next sector.

Now that’s funny: starting to see holding? We’re in a holding pattern. But there’s the bad news: JFK is landing south which conflicts with the LaGarbage traffic pattern landing north. Crap.

Why does JFK get priority? Because it has a couple dozen westbound transatlantic widebodies inbound and they’ve been in the air for 5 or more hours already. LaGuardia with it’s postage stamp sized runway (7,000 feet versus 13,000 at Kennedy) cannot  land with tailwinds due to stopping distance. So if Kennedy is landing south, LaGuardia arrivals are shut down.

“I can get you Boston or LaGuardia, eventually,” says the air traffic controller to our Dolphins team charter. “Standby,” comes the tense answer, and I know why.

We already did the math: we’ll weigh 132,000 pounds on landing; the runway is wet, so we need 5,660 feet to stop. Gives me 1, 400 as a safety margin–which will require all other perfection–screw the charts–in my mind: not only no tailwind, have to have  some headwind and no bad braking reports or we go to Kennedy (sorry Lufthansa). But the 757 landing distance number will be different, stopping the jet may be a problem. He’s looking closely at his Boeing chart, no doubt.

Which is another piece of the puzzle we both did as captains before launching off into the Nor’easter: take more fuel for increased loiter time, but then know you’ll deal with a heavier landing weight on a crappy surface due to the freak snow storm. Clearly, fuel wins, but he’s dealing with the stopping distance problem. And Newark is flying a complex RNAV approach that I don’t believe the 757 can do. Plus, its minimums are so high and the ceiling so low–it probably won’t work out anyway. That just sends you off on a gas-guzzling low altitude divert.

There’s a screaming headline in the weather-related alphabet soup: 1/4 mile visibility in snow and fog at LaGarbage. And previous American jets reported the ceiling really at 300 feet. Left quartering crosswind  at 14 knots; you get about ten seconds to see the runway, line up and find the touchdown spot.

Jill calls from the cabin: “We have an elderly woman who stepped out of  the lav feeling dizzy; she passed out and we’re giving her oxygen.” First officer stops reciting the weather forecasts and adds, “I sometimes pass out after a huge dump too;” I laugh, Jill doesn’t.

“Keep us posted,” I say, adding one more moving part to the dozens in play: medical attention for the woman, quick landing if she gets worse.

My magic fuel numbers have shifted dramatically: the closer south alternates show less arrival fuel than the more distant and verboten northern divert options. Why? The 125 tailwind we’re riding. That forces a Hobson’s choice: divert earlier to a southern divert base arriving with less fuel into worse weather; or hope to sneak in after the last international Kennedy arrival. If you can wait. Do you feel lucky today, punk?

“I may be able to get one more jet into LaGuardia,” the controller tells the Miami boys. Sure: football takes priority over all things, at least in the northeast. But with the powerlines down, they can’t watch anyway, right?

Jill calls from the back again: “Our lady on oxygen just passed out again. The number four flight attendant is also a nurse, says she’s probably having some blood sugar problems.”

“She’s a nurse?” the F/O asks; “Could she look at this rash on my butt when she gets done there?”

I laugh but Jill doesn’t. “We’ll get her on the gate as soon as possible,” I promise. Still laughing, I tell the F/O cross cockpit. “Let’s grab that one spot he’s talking about–declare a medical emergency and tell them we need LaGarbage.”

We set up the approach; one shot, zero tailwind, some headwind, reliable braking action report or we go right to Kennedy either on the approach or on the missed approach (again, sorry, Lufthansa; this will only take a minute and we’ll be out of your way).

Sit the cabin crew down; the radar is showing angry purple in the frontal clash ahead and below. All checklists done early; anti-ice on. Hang on–she’s gonna buck.

Crappy ride through tangled air: a hundred knot wind out of the south clashes with the nor’easter roaring in with icy air; we’re in the atmospheric rapids, blinded by driven snow which has also not incidentally given me vertigo: looking through the geometric structure of the Heads Up Display on the glass before me, the horizontal snow has my senses screaming that we’re in a left bank of 20 to 30 degrees. And I’m hand flying because the speed changes have the nose pitching more than I’m willing to tolerate at a low altitude as the autopilot struggles to correct.

Patience, concentration; do the job. A glance at the ground speed shows 95 knots; airspeed is 135 knots; Mr. Math says it a 45 knot Nor’easter is winning near the surface. And the 95 knots is making this take a lot longer than I’d like.

The radio altimeter is calling out altitude until go-around; we’re down to a hundred feet above and still in the muck.

“Ground contact,” my F/O says; I pick it up peripherally but not ahead. There–the glow of lead in lights. “I have the runway;” I announce.

“Minimums,” the audible radio altimeter declares. Barely time to check the sink rate–god I love me some Heads Up Display–kick in the rudder to track the nose straight ahead; right main gear, then the left; the nose wants to slam down as max autobrakes grabs with 3,000 psi of hydraulics, but I hold the yoke in my lap, steering  with my feet. We stop.

“Tell ‘em the braking action is good,” I tell the F/O as we start running the after landing checklist. That’ll help the next guys in for planning purposes. Now all we have to do is park, turn around, and fight our way back into the air through de-ice and crappy runway problems.

But that headache is an hour away. A cup of coffee is waiting in the terminal–we’ll worry about the rest later.