Airport Smackdown: Jethead vs. LaGarbage

What better to beat the blistering heat of a Jethroplex summer than a float in your own ce-ment pond? You bid the later-in-the-day flights and you’re senior enough to hold them. That means the morning run–helps you sit still for the 6 or 7 hours you’ll be in the air–and an early afternoon swim. Then, reality check waiting on the iPhone:

You knew that. LaGarbage today, tomorrow too–then LAX the next day. That’s your work week. Get ready.

That’s the current radar picture in the New York metro area. The stuff just north of Tom’s River will be a problem if it doesn’t move out to sea. You can tell there’s a front line between Jersey and NYC somewhere–just look at the temperature difference. Cold air slipping under warm air produces big boomers, and it doesn’t take much of that to disrupt the inbound flow to Kennedy, Newark and of course, LaGuardia. Shrug. Deal with it when you get there–but prepare for it before you take-off: more fuel.

Of course, that’s a double-edged sword too: LaGuardia is a short runway with virtually no overrun on either end–just Flushing Bay. No, it’s not as extremely short as Burbank, John Wayne-Orange County or The Dreaded 33 in Washington (5,000′). But it’s short enough–especially if it’s wet–to make landing weight important. DFW: 13,000 feet of concrete, overruns and clear zones beyond. LaGarbage? A friction overlay on the end of 22 and 13, (wanna test that out?) murky water everywhere else.

Preserve your options: arrive with enough fuel for holding and a go-around. The 737 is a good stopping jet–as is the MD80–and the 737 is very stable on approach. No big worries about airspeed control or pitch.

Confer with Flight Dispatch: they have you flight planned in the mid-thirty thousands because of previously reported chop. Fine, but we’ll check ahead en route and decide if we can’t cruise higher and save more fuel. Plus, our route will arc north, then east, picking up more tailwind as we go. Should put us over upstate New York fat on fuel.

Board 160 passengers. Preflight. Taxi out. Climb.

Life settles down to cruise: fuel flow, ETAs, routing. As expected, the ride is reported smooth in the low 40s by aircraft there now, so we climb and save more fuel, plus put ourselves above most of the weather trying to build itself into the stratosphere from the sun’s climbing radiance.

Radar watch is beginning to turn up signs of the frontal clash converging on the northeast. Super radar–good picture out beyond 300 miles, has it’s own GPS so it knows where all topographical features are and screens them out of the radar image. Good to be sure that what we’re seeing is nothing but weather.

Lunch? Dinner? Whatever–it’s the last food you’ll see today. Everything at LaGarbage will either be closed or out beyond security, which you don’t have time for: they’ll be clamoring to board 160 passengers outbound as soon as you get there. Speaking of which, within an hour of landing, we can get the current weather at LaGuardia and print it out:

Fine. Planning on 22; landing south and into the wind, no real storm threats or complications. Set up nav aids, discuss the approach with the F/O. Verify the runway in the Flight Management System (FMS) and the Heads Up Display (HUD). Validate all of the altitude and airspeed restrictions on the arrival.

The FMS begins its backward countdown of miles to go and upward count of vertical velocity required to satisfy the arrival restrictions. Cool?

Not so fast. Just checking onto a new frequency and you hear holding instructions being given to some unlucky aircraft. Now, that either means someone south of you (Atlanta? Philly?) or someone north (Boston?) has an inbound backup. Or–it’s New York Center airspace that’s enjoying a traffic jam at altitude. You bring up the holding page on the FMS display. Here it comes.

“American 738, hold west as published at MIGET. Expect further clearance at  0115.” Figures. Well, okay–holding endurance? Like you haven’t thought of that already. At altitude, we’re at an incredibly low fuel burn.

We can loiter for the better part of an hour. One thing about EFCs (Expect Further Clearance) you can count on is–you can’t count on them. So plan accordingly. On your side is your altitude, fuel flow and fuel reserve. The jets cruising lower enter holding there and burn more fuel as a result. Set up the entry and the hold:

EFCs are a best guess by Air Traffic Control, but they can be very pessimistic. Even if you can’t hold as long as they predict, you can hold till your endurance runs out and you need to bingo (divert to your alternate). Some pilots I know like to “Go Ugly Early:” if you think there’s a good chance you’ll have to divert, beat the rush for fuel and a turnaround at the divert station.

I’d rather stay high and slow and see what shapes up. We all still divert when you reach Bingo fuel, it’s just a difference in strategy.

New York Center is offering “Rockdale,” a navigation point north of  LaGarbage and in Boston Center’s airspace. Get released from holding immediately and approach from the north is the deal they’re offering, and some jets are taking it. I don’t think so; we have a good, high altitude perch here with a low fuel burn. Rockdale requires a lower cruise, inevitably, with higher burn–and no guarantees when you get there. Sure, maybe Boston Center has less aircraft but you still have to eventually get sequenced into new York Center’s flow.

It’s like switching lines at the grocery store: pick the short line and someone will need a price check or will have a zillion coupons to verify. Meanwhile, some jets below are starting to Go Ugly early–Philly’s going to be a mess. And the winds are shifting at LaGarbage–they’re switching landing runways:

Refiguring the approach is not a big deal. But it’s a bad sign: runway changes take time and lead to a huge backup on the ground at LaGuardia. Plus shifting winds mean unpredictable weather due to frontal passage. Alright, plan “B” is the runway 4 approach. Reprogram the FMSs, the courses and the nav radios.

Holding is eating up fuel, which is actually easing the stopping distance–but check it anyway. And use the chart for a wet runway while you’re at it. Figure on the worst case and the most Autobrakes, say 3 or maybe even max.

More jets at the bottom of the stack are heading for Philly; we’re still sound fuel-wise. Patience.

Finally! Released from holding, cleared downline. Do the numbers: what fuel will you arrive with but more importantly, assuming a go-around at LGA, what will you land with at JFK (that’s the plan) after? Numbers show actually about a 1-2 thousand pound surplus. Perfect.

Now we’re committed–not going to climb back into the enroute sector (too much fuel burn). And now the glass shows what the radar has been painting.

The ugly blotches here are actually the towering cumulus we’re sinking into here:

Already have the crew strapped in, all passengers down. Actually, the bad weather is a relief in a way: everything slows down as radar separation is increased. Plus, the approach is a straight-in, precision approach rather than the hairpin visual approach that is officially called the “Expressway Visual:”

Lots more fun from a pilot standpoint, but definitely more hectic. Finally, the wide swing to finally. Configure. In the slot: altitude, airspeed, configuration, glide slope, localizer.

Minimums: see the runway, land carefully; immediate reverse.

Now, the elephant walk to the gate. Park.

No time for relaxing–it all starts again in 50 minutes, outbound with another 160 passengers impatiently waiting to board. The inbound holding and the LaGarbage ground congestion has already set us behind schedule, and passengers have connections to make at DFW.

That’s the workday–only another 1300 air miles to go. Let’s get to work.

Summer air travelers, beware: he’s out there!

Summer air travelers, beware: he’s out there.

I mean that guy. The one who will make your travel a little less pleasant, probably unknowingly, but still.

For example, cruising at 40,000 feet northwest bound, the cabin interphone chimes. The First Officer and I exchange glances that ask hot, cold, or stupid? It’s too soon for crew meals—that’s where we’re stupid for eating them, but it’s something to do—and only minutes ago someone called to say it’s too hot in back.

Traditionally, within minutes, one of the other four Flight Attendants who don’t seem to be able to talk to each other will call and say it’s too cold.

But I answer the phone and this time, it’s stupid: “We just found a passport in seatback 30-A.” No, it’s not the flight attendant that’s stupid—it’s the passenger who on some previous flight for some odd reason decided to stash his passport in the seatback pocket.

Before our flight, the jet had come in from JFK. Maybe an international arrival, and now someone is enroute somewhere without a passport.

That’s where you come in: you’re in line at Mexican Customs in Los Cabos, and you’re sweating like a fat lady in a vinyl chair, waiting, waiting, waiting—because the guy ahead of you in line talking to the taciturn Customs agent is suddenly aware that he doesn’t have a passport. Your vacation is on hold just a little longer because like me in the super market, you got in the wrong line (“Price check on lane seven!”) while passengers to your right and left are breezing through and claiming their luggage (and maybe yours), heading for the beach.

Sure, it’s going to be worse for him—without a passport he’s not getting back into the United States without a major hassle and, you hope as payback for your delay, a strip search. But the lingering question is, why would anyone put anything of value in a seatback pocket on a plane?

But you’d be amazed at what you’d find back there after a flight. Well, what someone else would find back there: I’d sooner stick my hands into a trash can in a crack den than risk the snot rags and barf bags or kids’ diapers or half eaten ham sandwich that will be stuffed in there.

 

Still, people for some odd reason nonetheless sit down, empty their pockets, stash wallet, iPod, keys, camera, travel documents, passport—you name it, into the seatback pocket as if it were their glove compartment on their family car (okay, there may be a ham sandwich in mine, I admit).

Never mind the hassles going forward to recover a lost item, a headache made all the more difficult because the jet will crisscross several thousand of miles before the discovery of a missing item is made (call the lost and found in Seattle, Chicago and New York). The important thing is that the Stupid One is delaying your vacation.

And unbeknownst to you—he may already have delayed you. Remember sitting at the gate well past departure time? I can’t tell you how many times five or ten minutes from pushback to a resort destination in Mexico or the Caribbean when the agent steps into the cockpit and says “we have a problem.”

Let me guess: someone confirmed on the flight is in a bar somewhere starting on the umbrella drinks and about to miss their flight to the actual resort. Why? Because they can’t read a ticket? Don’t know their own itinerary? Can’t do the math on a time zone change? Are intellectually low functioning and were finished off by the TGI Friday’s Bloody Marys in the airport bar?

Doesn’t really matter. The point is, if they’re not on board we get to sit at the gate while the ground crew sorts through the cargo compartments crammed with the luggage of 160 passengers to pull their bags off. That takes a while. You get to wait, I get to wait, both of our days becomes a little longer.

Yes, it’s the lowest common denominator that dictates when we leave and when you arrive in paradise.

But there is justice in the situation, as I witnessed once at a departure gate as I waited for my inbound jet. Airport police officers had pulled a couple off to the side as passengers boarded a jet for Cancun.

Apparently the man and woman had been to the airport bar, and the man had clearly had a few too many. Federal law prohibits the boarding of any passenger who even appears to be intoxicated, and the airline agents had done the right thing: when in doubt, call law enforcement to sort out the situation in accordance with the law.

Sorry ma’am,” I heard an officer say as the man was being detained, “he’s going to be placed under arrest for public intoxication.”

I couldn’t hear the exact back and forth between the steamed woman and the officers, but in the end, it seemed the officers weren’t the cause of her anger: she grabbed her boarding pass, shot a pointed glance back at her handcuffed partner—then boarded the flight.

Just as well: he’d probably realize in the Customs line in Mexico that his passport was missing anyway.

After the storm: fly home–but not so fast.

After the divert to Wichita Falls, time to gas and go: Flight Dispatch says DFW is accepting arrivals. That’s all we needed to hear–we’re refueled and refiled with Air Traffic Control. As soon as we’re released by tower, we’re in the black night and headed south to DFW at 280 knots.

Would be flying faster, but 280 is the best turbulence penetration speed and though the ride’s not overly bumpy, the latticework of cloud to cloud lightning straight ahead promises roughness. We’re making a beeline for one of the four arrival corner posts for DFW at 10,000 feet.

Things will happen fast on a 70 mile flight, and the First Officer is flying: he’s sharp, and that allows you as captain to oversee all of the preparation, the checklists, the navigation and most importantly, the radar. Approaching midnight, we’re now 12 hours into our pilot duty day, but regardless, there is still the same roster of tasks to be accomplished–and they don’t care how tired you are, they must be accomplished correctly.

Getting a good look at the current radar sweep and things look ugly. The cells have broken up and are scattered like mercury all over the place. The DFW airport arrival information is automated: weather, winds, runway–all printed out from the on-board data link printer. The DFW info says landing south–so you set up frequencies, courses and descent altitudes in both sides of the Flight Management System, as well as both pilot panels. While he flies, you brief the approach.

Have to swing wide around storms–request a descent to get below scud blow-off you can’t see on radar, but which you detect because it’s blocking the pattern of ground lights you know should be Denton. As soon as we begin descent, the master caution light glares in front of your face, along with a pressurization clue. A quick glance at the pressurization control panel above the F/Os head shows we’re holding cabin pressure fine, it’s just that we never reached the programmed cruise altitude and the computer is confused.

“Off schedule descent,” you say, punching off the warning light. Reset the cruise altitude to 5,000, which is lower than where you are, to let the computer recalculate and catch up.

“Radar vectors to 35 Center,” says the air traffic controller. Dammit–we set everything up for a south landing per the DFW info.

“ATIS says DFW landing south,” you say, making sure there’s absolutely none of the annoyance you feel in your voice.

Pause, wherein you can imagine the controller saying to someone the ATIS is wrong. “I’ll check on that, but plan north.

Redo the courses, rebrief for the F/O, reinsert the proper approach in the FMS and extend the centerline for intercept. Complete the checklist down to configuration, validate the Heads Up Display Data. Staring at the lights of The Ballpark in Arlington miles south, doing the math on descent rates versus final turn altitude based on a left turn thereabouts. Looking good.

A loud snap as the autothrottles kick off. “I’ve got them back on,” you say, reaching up to reinstate the system. F/O nods, concentrating on flying.

Now ask yourself why they tripped off. No failures annunciated–they wouldn’t have reinstated with an internal failure. And it’s not that choppy. Has to have been a power interruption. Glance up–sure enough, there it is.

The left generator bus source is gone. Is it the generator or the bus that’s failed? Regardless, we’re flying with only one electrical source–the right generator. Not good.

First instinct is to start the Auxiliary Power Unit (APU), a small jet engine in the tail that can provide electrical power and pressurization air–but wait.

If the fault is in the left electrical bus, adding the APU generator could either cause a fire, or take down the APU generator. Be patient.

Although you know the right generator has assumed the power load–so the bus must be okay–why take chances?

“We’ve lost the left generator,” you say, reaching for the Quick Response Handbook. “I’ll take care of it. “F/O nods.

The procedure confirms what you deduced. Within a couple minutes, you have the APU running and power restored. Follow the QRH procedure exactly; better to have two electrical sources–if you’re down to one, if it fails, it’s going to get dark and ugly: flying with limited instruments and systems on 30 minutes of battery back up. In the weather, at night. We can do it–but would rather not.

Left base turn from an angling downwind. Mike’s doing a good job–he sees the bad angle and is slowing and calls for dirtying up with flaps and gear. The runway’s coming into view on my side. Good altitude and speed; the intercept of glideslope and course will be fine.

Tower calls the winds “130 at 18.”

Dammit. The limit is 15. With the 50 degree offset, we’re close. Legal, but you don’t like flirting with limits. Even on a long runway.

“Continue,” you say to Mike’s inquiring look–he’s done the math too. But you’re just about decided to abandon the approach. But no need to rush anything. Rushing is never good.

“I’ll rebug you to 40” you say, changing configuration as required by the tailwind, “and brakes 3.” He nods.

At a thousand feet, it’s clear that the tailwind is unstable and variable–you can tell from our ground speed versus the airspeed.

No good. “Let ‘s take it around,” you say. He nods, adds power–the descent stops.

“Here comes flaps 15,” you recite the litany for him,”positive rate, gear coming up. Missed approach altitude set.”

“American 245 is on the go,” you tell the tower.

“Fly runway heading, maintain two thousand,” says the tower.

Fine; nearly there–reset the throttles from N1 to speed, reset both FMC from climb to capture. Reset both course windows and MDA–because we’re going to land south. Reprogram the FMS for the 17s.

“I’m going to teardrop you out to the east, then bring you around for a final to the south,” says the controller. “Can you do that?”

Eyeballing the radar: nastiness to the northeast, but there’s some room.

“Give us five miles,” you answer. No need to rush–make this correct, hit every step. F/O nods. “Then turn us back in.”

Slowing, getting dirty. Left sweeping turn.

“Do you see the runway?” asks tower. You do–you give a thumbs up to Mike. He nods.

“Affirmative,” you answer.

“Cleared visual approach, cleared to land, 17 Right.”

Confirm the Right runway freqs, MDA and courses set. “I’ll bug you back up to 30,” you say, changing configuration again: don’t need a whole lot of drag without the tailwind and with a possible wind shear. Mike nods.

Glideslope is rough. You’re on a hair trigger to go around again–there’s plenty of fuel to hold or go north to Oklahoma City or south to Austin. Be alert, be patient.

Increasing wind; good sign–but it has to stay within controllable limits. Mike’s doing a fine job wrestling the jet onto glidepath. The Boeing is a steady machine–an MD80 would be a bucking bronco in this.

Below 500 feet–you’re call: it’s stable enough, we’re good. If Mike wants to go-around, we sure will, but we’re good.

Over the threshhold, Mike puts it down; speedbrakes deploy, he yanks in full reverse, the jet slows.

“Nice job,” you say, taking over as we slow to 80 knots.

After landing checklists, taxi in. Careful, do the job right all the way to the chocks. Engine shutdown.

Passengers deplaning, our shutdown checklists complete. You’re writing up the left generator in the maintenance logbook, a mechanic is already on the jetbridge waiting.

“You can take off, Mike,” you say, “I’ll finish up here.” Meaning you’ll do the final “after all passengers have deplaned” checklist items to power down the aircraft. That’s a courtesy you do–you’re the captain, you leave last. He did a great job tonight–respect that.

We fist bump, he leaves.

You finish up: packs off, recirc fans off, cockpit power off. Grab your bags. Slip out of the gate area past the 160 passengers who have no idea what transpired between Wichita Falls and their safe landing a few minutes ago. Nor should they–that’s what they pay you for.

Fresh air feels good, outside waiting for the employee bus to the parking lot. Nearly 1am, got to get home and get some rest–flying again tomorrow.

Summer Storms, Airline Flight, and YOU as Captain.

Well that’s going to be trouble, your air sense tells you as you wing westbound.

Because you have to turn around and come back once you reach LAX–and this stuff, you can feel it: it’s growing. In a few hours, it will stand between you and “homeplate”–DFW for you–and it will be your job to thread the needle between, above and around the towering wall of what will be full-blown thunderheads by the time you return.

But the weather-guessers say the storms will stay south and west of the Jethroplex, right?

Yeah, my ass. Sorry–been fooled before. Now, we deal with gut feel and radar. Forecasts? Farther out than a couple hours–pretty well useless. Keep flying.

LAX, first stop: got to have a cup of the strong Brioce Bakery coffee. Kind of crave it flying to LAX. Westbound passengers happily herding off; First Officer about his business on the ramp, catering, cleaners. You?

Stout cup of Brioce and radar, your best friend. Which helps you set up your next best friend: jet fuel.

But here’s where your air sense–and 17,000 flight hours–comes in: the storms forming up and marching west to east aren’t really a front passage. Rather, they’re a boundary collision that the cold front is barely strong enough to move. Those storms will stagnate wherever they form–my best guess–so there’s not going to be a quick close-then-open, 40-50 minutes of holding.

Hedge your bets: approach from the northwest in fact, route north over Albuquerque and see if you can beat the frontal passage, or be positioned to slip in immediately after. Plus, from behind the squall, all of your divert options will have a clear path. So in this case, northern route, an hour of holding fuel, see how it plays out.

The first round of bad news comes up on the data link printer in Arizona: “0300 DFW tempo 1ovc tstm lgtctcctg 34012g25 29.77 prsfr.”

Duh: “airport expecting one hundred overcast around 10pm in thunderstorms lightning cloud to cloud, cloud to ground; winds from the north gusting to 25, surface pressure falling rapidly.”

Trouble in front of the front. Cross the Rio Grunge eastbound, nice tailwind rocketing the aluminum tube across the ground at 500+ miles per hour.

My F/O is smart, sharp, quick. A good asset in forming a plan, then a backup, then another. I like options. I choose my words carefully: “Hey, you want any coffee? I’m buying?”

I like the way Angela makes coffee, the old-fashioned DC-10 technique: a splash of club soda on the bottom of the pot before brewing–eases the acidity, gives a smooth flavor. Hell, no rush here–I hate redoing stuff. The radar picture won’t be too well defined until about 300 miles out, even better at 160. Have a cup of Boeing brew and relax.

Okay, now we’ve got something to work with. Did I mention how much I love the 737-800 radar? It has its own GPS system, always plotting where it is–and it knows the terrain everywhere it finds itself and miracle: it screens out ground clutter–and does its own tilt for each range. What you see is what’s there–how cool and smart is that?

This picture is looking southeast. The blob over HIKAY is the nasty storm cell headed for the airport. As I figured, we’ll either beat it, or the airport will close–and it did as we approached 100 miles out. We expected that.

The good news is that we’re assigned a holding pattern over Wichita Falls. Sheppard has a couple of long runways and jet fuel available. Once we’re established in holding at 33,000 feet–a good altitude for fuel economy–I call the Sheppard tower on another radio: how late are you open tonight? How late is the fueler open?

Eleven o’clock for the tower, all night for the fueler. It’s just after 10pm. We’ve got fuel for 40, maybe 50 minutes of holding, then we need about 4,000 pounds to fly north to Oklahoma City.

But we’re right on top of Wichita falls/Sheppard. I can see it–perfect weather. No additional fuel for the divert–we just spiral down.F/O concurs. We start setting up navaids, approaches.

Our holding racetrack--right over an excellent divert spot.

DFW approach updates the airport re-opening projection: midnight.

The mass exodus begins from various holding stacks because no one has that much loiter fuel. Most on the north side are heading for Oklahoma City.  “Put Wichita Falls on request,” I tell the F/O, as we continue all divert prep and logistics with our dispatcher in Fort Worth.

We exit the holding stack northbound with a descent clearance, all of the divert notifications and nav system reprogramming done, approach briefed–we’re way ahead. The winking lights of two jets above us in the pattern suggest what I’d be thinking if I were them: “Smart bastards–first into Sheppard, first for fuel, first out.”

Yup.

Sheppard Approach: “Plan runway 33 center.”

Me: “Unable.” The center runway is 150 feet wide; our wingspan is around 130. The left runway is 300 feet wide–but the Air Force is using it for night traffic patterns in my ex-girlfriend:

Tough darts, wingnuts: when it was me in the Air Force flying the White Rocket, I’d have said tell the civilians to get lost–we’re busy here. Now, with 160 passengers and a crew of 7 on board, I think differently.

I’m doing the math, checking the descent rate and speed and distance–it’s all coming together nicely, “in the slot” as we say. Over the threshhold, follow the HUD cues projected before me on the glass; little narrow-gauge skid marks from smaller jets slide under the nose, then touchdown.

Clear the runway, set the brakes for a minute–whip out my cell phone and call the fueler, “Landmark Aviation.”

“How much fuel do you need,” asks a friendly voice. We have 5,800 pounds on board, I’d wag 3,000-4,000 to get to DFW, 3,000-4,000 more for delays. Plus some more thousands for peace of mind and the unexpected, two factors that usually don’t work well together.

“We need 12,000.”

“No problem, taxi on down.”

Tight maneuvering on narrow taxiways and a small transient ramp, but slowly, carefully, watching the wingtips–we park. I see the lights of two other airliners approaching from the south. Hah! The fuel truck is already here.

First Officer is outside, doing the exterior inspection. I’m on the phone with dispatch for a clearance plan, on the radio with tower for a proposed launch window, then with DFW approach for an expected route, then the phone again for current DFW weather.

My fuel guess is pretty good: dispatch wants us to have 15,000 pounds of fuel–we have 17,500. I love jet fuel.

Me signing for six tons of jet fuel.

Behind us, a Super-80 waits, an Airbus waiting behind him. I chat with the MD-80 captain in the quaint Wichita Falls terminal–he needs to have flight plan faxed to him; we printed ours on our on-board data link printer. I considered for a moment suggesting the dispatch send his to our jet, but I’m not even sure that’s possible. And we’re ready to blast off.

Supposedly, the terminal folks are on their way back and they’ll fire up the FAX machine for him and his 140 passengers. Too bad you ain’t on the Boeing, I thought but didn’t say.

Carefully, point by point, we check our route, then our performance data. Never mind that it’s nearly midnight, 11 hours into our workday–every single detail will be checked. I will see and he will crosscheck every number put into the performance system.

We start engines, a ground man pulls the chocks and salutes: clear to go.

I have a better idea. We sit with brakes parked and accomplish all pre-takeoff checklists so that I don’t have divided attention taxiing out over the mini-sized taxiways.

Tower clears us for take-off. One last check of numbers–the runway, the rotate speed, the weight, the power setting, all check out. Stand up the throttles, all exterior lights on, punch the take-off power button on the throttles and she leaps forward with a growl.

Off the nose, black sky, more storms; cloud to cloud and cloud to ground lightning weaving a brilliant latticework to the south, where we’re going. Dead ahead, more spot decisions, plans, backups, numbers, radar and ultimately, maybe a cup of coffee to go for the drive home once we navigate the weather gauntlet.

But nothing’s set in stone; we’ll just see what’s what when we get to DFW. The coffee and DFW will just have to wait, but I’m patient, and careful. All in good time–despite all pressures to the contrary, all passenger and crew urgency, fatigue; I tune it all out. Every step carefully, thoughtfully–that’s what summer flying is all about.

Quite a light show in the DFW terminal area, and the hurdles spring up one by one, then in droves. Weird, but I kind of like the challenge. But that’s another story.

Your Kids On An Airliner, Flying Alone? Do It Right.

Little big man standing by the gate, already gone.

Mom’s there, the pain of the thousand miles about to shove themselves between her and the boy draws her eyes into a squint that you know damn well is there for a reason. But he’s already gone, his eyes set elsewhere, the leaving now a mere formality etched in stone beyond his reach or doing. The flight migration of the solo kids: coast to coast, north to south, the sad winds of divorce carry kids aloft.

It’s year round but especially heavy around Memorial Day. Holidays? Summer? Solomon: two halves of one is still less than a whole. But it’s all we got–decreed; so chin up, little nomad.

Way too familiar, and I’m too foolish to pretend I don’t notice. Last minute, before boarding myself and stepping into the cockpit, staying out of everyone’s hair until about ten minutes prior to push, I do what I can. Mom’s there, bereft, dying a little inside, not even hiding her pain. What can I do?

I’ll get to that. But more importantly, what can you do if you’re the parent sending off your child?

According to the Department of Transportation, more than seventy thousand minors will fly unaccompanied this year. Big Fact Two, according to Parenting Magazine, is that parental preparation will make all the difference for those children who do fly solo this year.

There, the authorities have spoken. Now, hear me, the guy standing on the bridge on both ends of the voyage.

First, parents: ante up. All major airlines now have programs to care for kids who fly “Unaccompanied,” or “UM:” Unaccompanied Minor.” They are not not free. But they are essential. Your child will be logged in to the system, your credentials and those of whomever is on the other end will be verified. So whoever picks up your child will be positively identified by official documentation: driver’s license, passport or government issued ID. I watch it every week: our flight attendants will walk your child out and verify that they are delivered to the correct person.

Mid flight? You say you’ve booked them on a thru-flight, meaning no aircraft change enroute? GMAB! I can’t tell you how many times my flight sequence from one coast to the other, same flight number, supposedly same aircraft, gets changed. “Take all of your belongings of the plane,” the agent will say on the P.A., “and proceed from this terminal to the new gate in the other terminal.”

Saved $100 bucks on the U.M. fee, did you, because “TravelSuperDuper.com” promised you a stop but no aircraft change? Don’t even think about it. Because no, the flight attendants won’t take care of the switch because they might not even be scheduled on that next flight. Want to see if your little one can navigate a major airport? Pay the fee.

What you get it this: signatures and verification will follow your child every step of the way. Do I know how many kids are flying alone on my jet? No. Do I know how many officially designated Unaccompanied Minors are on my flight? You bet I do–just as with any special or hazardous cargo or armed individuals, I know who and where they are. And I take it one step further, as I do with armed passengers: I don’t care what I’m “supposed” to be doing, I’ll take the time during boarding to meet eye to eye, say, hello, and tell an Unaccompanied, or “UM” as we call them, by name “we’re glad you’re here. It’s going to be a good flight and if you need anything, you let us know.”

Important to me, hope it is to them. Regardless, when we have the UM vouchers, now my crew knows who they are and where they’re sitting. And someone will hand-carry them to where they need to be.

But even more practical, in my experience, is that the UM process allows you to accompany your child through security and to their boarding gate, as well as permitting someone you designate (have their driver’s license number or other government issued ID info when you check in) meet them at their arrival gate.

Second, send them on board calorized. That is, make sure they’ve eaten recently or have with them some snacks they can manage. Yes, there’s “buy on board” food on many flights–but the transaction is cashless: credit card only. Make sure they have water when they board too–get it on the secure side of the airport because you can’t take it through security.

Pack them sensibly: make sure their bag that they take on board is manageable for them. Don’t count on someone else handling their bag, and make it one that can fit under the seat in front of them, as little ones won’t have much luck with the overhead bins. Anything else you need to send with them–check it at the ticket counter.

Do this: Google “airlines” and “unaccompanied minors,” and be sure to read the airline of your choice’s procedures, plus the many decent parenting articles with tips on UM travel–like this big one I’m going to give you: say your good-byes at home. That’s what the kids are leaving, and that’s where they’ll return. The airport is part of the journey–don’t make it part of the good-bye. Be matter of fact from that point and it will be easier for you and your child.

And finally, show up. I mean on the receiving end, and I mean on time. Flashback, Christmas Eve, a west coast destination, late evening. Our little trooper is standing by the ticket agent as the crew deplanes. The agent has her paperwork, waiting for a late parent. On Christmas Eve. Twenty minutes after our arrival. And we were late.

My crew is tired. Our van is at the curb waiting to take us to the hotel–but nobody’s leaving our little UM. We wait. We hate the parent who didn’t leave two hours early and camp out so as to meet our child at the gate. Be there, whatever it takes.

Back to our departure. Mom ready to crater, her son already on my jet. I approached her from behind.

“We’ll take good care of him. It’ll be all right.” I’m lying. It’s the heart fractured into a thousand shards of smoked glass, hers, that will never be all right ever again. He’ll be okay–the kids usually are once they’re under way. They do their leaving before pushback; the parents are left on the death watch in the terminal. And kids on some level perceive that–so like I said, good-byes are best said at home.

“Look,” I offered, “you want me to call you when we get there? To let you know everything’s fine?’

She put her number into my phone, in tears. I walked onto my jet fighting mine. Parents everywhere get to do this, as some court decreed, over and over till the kids are old enough to decide travel and visitation details for themselves. It’ll never be easy–but make it the best it can be: set them up to be cared for enroute.

I texted the woman after we arrived, watching her little guy walk away with his “other family,” and I imagine she breathed a little easier. Not sure, but I know I did.

Vuelo Loco: Tennyson, Dead Fish and Mexico City.

Listen, I’m a fan of Mexico. Really, I am.

What’s not to like about Mexico City? Always looked forward to those downtown layovers–it was part of my job–but they’re scary dangerous. Probably not for the reason you think though.

I mean, sure, there’s plenty of drug violence. And yes, I did have to dodge through four lanes of traffic to evade a scroungy-looking cop trying to shake me down once, but he was either too lazy or too smart to chase me through the insane downtown traffic.

And yes, plenty of people with questionable intent in a city of 20 million, where you could simply disappear, kind of like the city itself  is doing, slowly sinking into its own aquifer. And okay, maybe I did roll the dice in a sense, as an instructor-evaluator taking pilots down to Mexico City every month, showing them the safe way to fly in and out of the mountain bowl.

Well, it’s not even really this “thread-the-needle-through-mountains” approach and usually, through thunderstorm alley that was like playing craps weekly. And it’s not really that I minded the always slick (memo to Mexico City Airport: the rest of the world cleans the reverted rubber off of their runways every year or two, so get a clue) runway with the puddle in the middle that you hit doing about 150 and exit two thousand feet later at about 149.

More, actually, was requiring the qualifying pilot have a beverage and a Cuban at an outdoor cafe on the traffic circle outside the Presidente Hotel. The bar–Karishma–is where a whole crew got mugged one night. They noticed that suddenly the place was empty save the two airline crews enjoying tapas and the generously poured (“Tell me when to stop pouring, Senor”) refreshments there. Then suddenly, watches, rings, wallets–buh-BYE, as we like to say.

So to be on the “safe” side, we sat outside on the traffic circle–maybe more witnesses?–and since it was my idea, I made sure my back was to the building, so the new guy got to sit with his back to the insane traffic, puffing a Cuban (relaxing–but mandatory) and enjoying a refreshment, maybe getting a shoeshine from the roving vendors who’d magically appear, ignoring the demolition derby mere feet away.

Hey, might as well get the full flavor: massive city (did I mention 20 MILLION people?), exotic neighborhoods of jumbled steel and glass elbowing in between with castellated stone architecture, snarled in the clogged highways like the arteries of a fat man. You watch the traffic and muse over your beverage, how the hell do they do this five way intersection without a traffic light?

And then on the side streets of The Polanco, maybe a quieter sidewalk cafe where I actually did much of my doctoral exam study: outside, books piled, good coffee, usually a thunderstorm in the afternoon that made me glad I wasn’t trying to fly a jet in or out at that moment. Out of nowhere, it seemed, in the afternoon towering big-shouldered thunderheads would roll through the mountain pass with raggedy sheets of torrential rain and thunder that echoed through canyons of concrete and steel, the reverberations so fitting to Tennyson’s “Ulysses” marching across the page before me toward the inexorable doom awaiting us all.

Harder to relax at dinner, though, when you were concentrating on the guard dog staring at your plate and whatever you were having for dinner. The armed guard restraining the dog had his eye on you and the plate alternately, and you had to wonder if either or both of them might figure that the dinner and your wallet might tip the scale in favor of mutiny. It was a stand-off in Mexico: the guard and dog making sure banditos didn’t mug you while you ate–but then the silently menacing pair themselves having to resist the hunger and temptation to rebid the transaction in more favorable terms.

And it’s not even the “one-eye-open” sleep in the airport high rise hotel with the un-level floors from the tipped buildings patiently waiting to tremble and topple in the next big quake they know is coming soon.

You wake up the next morning with the feeling of relief: ahh, The Big One they’ve been expecting didn’t happen while you slept, crushing you in tons of rubble that will take about ten years–if ever–to remove.

No, I’m talking about this:

That’ll eat you alive. But I’m getting ahead of myself.

I was heading down to Mexico City for the umpteenth time and my favorite cousin was there with her husband who worked for the U.S. Department of State. “Hey, want to meet for dinner?”

Okay, I already know why not–I’ve been in the airline crew biz a looooong time: relatives don’t get it, you’re not on vacation; time does matter, sleep too.

“Sure, why not?” Because I’m an idiot–and here’s why. We’re going out for Mexican, traditional, right? I mean, we’re in Mexico-friggin-City, right? Enchiladas? Queso? Fajitas?

No.

We’re doing Mexican-Asian fusion, which means I’m eating raw fish in Mexico: salmon carpaccio, pictured above. Delicious. Amazing! Immodium, amen. That didn’t take long.

The fever lasted about a week. The shower nozzle effect (any chance of scheduling a colonoscopy? I’m prepped, just for the hell of it) lasted a couple weeks. Thanks cuz.

Forget banditos. Who cares about high altitude aircraft performance, up-sloping mountainous terrain and treacherous rolling thunderstorms. The real danger’s on the plate.

Yes, I love Mexico City. Just don’t go there unarmed, okay?

The Flight of The Fatass.

Couldn’t come at a worse time, when each cent spent on fuel strains the budget of every major airline. The fact is, a direct operating cost airlines cannot avoid is fuel usage, which is directly linked to the aircraft’s gross weight. Suddenly, there’s this:

That’s right: double-fudge brownie sundaes–in flight. Which brings us back to the jet’s take-off and climb gross weight. Seriously gross, in some cases.

Back in my Diesel-10 days, I flew with a giant of a captain who shall remain nameless but his initials are Big John. He must have tipped the scales close to three hundred pounds, and I admit, as a First Officer doing the flight control check, I’d purposely pull the yoke back far enough to jiggle his big gut (he’d say, “Whatcha tryin’ to do, boy, loop it?”) hanging over his lap belt.

The big mystery early in the month we flew together was why did Big John excuse himself from the cockpit at the top of descent point, for at least fifteen minutes? That’s right before we get really busy with descent and approach.

Mystery solved on our first layover: the “galley wench” (that’s the flight attendant who served below decks in the DC-10 lower lobe galley) said he was downstairs with her, hoovering any uneaten food from passenger meals that were left over.

Maybe that comes from the grand tradition of fat sea captains who had to keep themselves well-marbled to survive months bobbing around on a hostile ocean. You never know when you’re going to have to spend two seasons and an eternity of reruns on an uncharted desert isle.

You never know just how long a three hour tour is going to be, right? We were doing a lot of trans-oceanic stuff in the ten, so maybe John was planning to be the only guy surviving in a life raft.

Regardless, Big John was just one of a growing number–literally growing–pilots who over the span of a career, drove up the fuel burn of the airline as his career dragged on.

Why? Go back to the top of the page and face the brownie sundae–my weakness. Okay, I’ll come clean: I’m six feet tall and weight 182 pounds (today anyway), have finished nine of the 26.2 mile marathons, blah, blah, blah.  Point is, I do take part in the aerial hog call pretty regularly. A tour, you say? You’d like a tour? Prepare yourself.

First, there’s the big guns that announce themselves with a “ding” on the flight interphone: “Hey, we’ve got [insert uber-caloric dessert here] in back if you all want some.” Or, it just comes already on your crew meal. Either way, there’s this:

A dense chocolate cake-like pie. Sure, just eat a bite or two, right? You’ll run it off on the layover, right (in Toronto in January? YOU’RE LYING)? You missed lunch too, see, and this is okay therefore, mangia, right?.

Then there’s this:

Coming out of several Florida airline catering kitchens–it’s really decent Key Lime pie. Somebody actually recognized that Key Lime’s are just like any other limes–added for the citrus flavor for the pie, not the color–and it looks and tastes authentic. Probably about 800 calories, too.

I really like this meringue-ish type lemon pie too:

It’s kind of densely creamy with just the right amount of tartness. And another 900 calories, probably. Sometimes the dessert just looks so innocent sitting there on your tray, small and innocuous, looking up, suggesting hey–eat me.

But word gets out when the inflight menu changes: hey–the cheese cake’s back. Burp. And sure, the salad’s always a sensible choice . . .

. . . as long as you don’t chase down it with another fat bomb:

I’m less vulnerable to the cake, which often is dry enough to suck all of the moisture out of your already parched (from the 2% cabin humidity) body.

That and the hermetically sealed bread item could absorb a fuel spill of considerable magnitude. So I find those non-confectionary things easy to avoid. But then there’s the catering out of Mexico:

Always some type of pastry dessert that face it–you’re going to try some of it. And when you do, you’re stuffing all 900 calories into your pie hole.

So, you might well ask, why not just bring your own food? Right? Yeah, like that’s any better, like anyone could be trusted to manage that. Here’s just a couple of bad choices in that regard.

This is The World’s Most Dangerous Pastrami, slapped together lovingly (“Ey–we don’t got all day here, whaddya want?“) in the employee deli in La Garbage Airport, Flushing (is it just me or are these terms all appropriately suggestive?) New York.

Or The Long Haul Meathead Sandwich, good for at least two thousand miles:

But tofu’s healthy, right? Shut up:

Here’s the Blow Your Head Off spicy tofu, an O’Hare exclusive I can’t resist. The heartburn alone will keep you awake for at least a thousand miles, which is kind of the point.

Regardless of whether you bring your own food, the galley ovens are just on the other side of the cockpit door. When the aroma of freshly baked cookies finds it’s way forward, who are you kidding?

You’re eating them. yes, you can defend yourself from any smells . . .

But you’re not gonna avoid cookies, are you? And never mind in flight, what about the junk you bump into hanging out before the flight? Like the old faves stationed around the nation, waiting:

It’s the best breakfast burrito in the nation, waiting for you at a little shop in the Albuquerque airport. Perfect salsa, will light your hair on fire. And in the Portland Airport, “Good Dog Bad Dog,” with sausages you are going to eat no matter what.

Need a closer look? There’s a video look at “Good Dog-Bad Dog” on the bottom of this page. Go there, try one–you’ll be hooked, too. And speaking of dogs, back to basics in the Oklahoma City Airport–Sonic, headquartered in OKC, offers you the essential foot-long chili-cheese-onion dog right across from the gate for your convenience:

This is all leading to a very scary conclusion, fellow fliers: we are destroying the ozone needlessly because of the bulk–literally, the bulk–of those who must be hefted off the ground and into the stratosphere with the fossil fuel burn increase required to haul their fat asses airborne.

Don’t get too smug, either, if you’re not a big butt pilot–we’re only two of 165 butts on my airplane. Yeah, we notice–

The suitcase will fit under the seat–but what about fitting in the seat? Anyway, that’s what’s driving up fuel costs, along with the constant mayhem in the middle east, hurricane rumors near the Gulf, a flu outbreak at a refinery in Jersey–whatever. Those are things Al Gore says we can’t control. Eating in flight is quite another thing.

But actually, it doesn’t look like Big Al’s skipping any meals either. So let’s just forget it–this is The Land of Plenty, to fly across it is going to take plenty of fuel because of all of the plentious butts on board.

Flying is a tough business, in my experience. You deserve a trip to “Good Dog–Bad Dog” in order for fortify yourself for the journey. So click on the video below and enjoy an up close and personal visit to the place.

Me, I’m heading out for yet another long run. I’m personally too cowardly to follow in Big John’s gigantic footsteps–his heart exploded on a layover and he keeled over dead, face down in his angel hair Carabonara.

Bon appetit!

a

Silver Wings, Then Other Things: Part 2.

This is part 2 of a multi-part series putting you in the captain’s seat. Want to start with Part 1? Click here.

.

.

Flight plan? Got it. Fuel load? Fine. Take-off data? Got that too. The ten-yard-long printout of notices and info and weather affecting our flight and route? Folded accordian style. Cup of McDonald’s coffee, black? In the cupholder by your right knee.

Something about that: a simple pleasure, that black coffee, plus an opportunity to make a donation to the Ronald McDonald House at the counter every time. I like the idea of doing something good for kids every time I pass by McD’s in the airport.

But also, in “the bubble,” it’s a cool luxury: taxiing out, steering with feet on the rudder pedals, minimal and exact responses to the required challenge-and-response checklist read by the First Officer–and sipping my coffee. The jet feels loaded up; weighty. You can feel the 112 feet of wing out there, the 40 foot tall rudder buffeted by gusts. Definitely an airship lumbering on the ground. Radios and official responses; taxi clearances and I say “okay” as soon as they’re given so my F/O knows I heard and understand.

Other than that and the radio chatter, silence. Because I don’t want anything on the Cockpit Voice Recorder (CVR) except for official, flight-related verbiage. There’s too much that could get screwed up, too much that needs to be checked before take-off to allow a layer of distraction. Plus, it’s the official policy: “sterile cockpit” below 10,000 feet. That is, no non-flight related talk, period. Saves the bubble, the concentration, for important stuff.

Sterile Cockpit.

Because here’s the problem with advanced flight automation: an input error, left undetected, can have disastrous consequences. A keystroke error can lead to faulty flight guidance commands, from the basics of pitch and bank to the routing errors. The only hedge against the hazard is diligent checking of all input. We did the route check at the gate, remember? Now we verify that the data-linked upload and our own inputs are valid: gross weight, center of gravity, fuel weight, take-off and abort speeds, climb speeds, every number associated with performance. That’s as we’re rolling, and as I’m ensuring we don’t violate anyone’s taxiway or runway space, steering with my feet–sipping my coffee, of course.

Ready for your eye test? "Give way to an RJ on Charlie, then taxi east on Bravo, short of Charlie 3."

Several numbers you must see, every time, before take-off–it’s not enough to have the First Officer read them aloud (“We planned 155,000 pounds, we’re actually 156,500 pounds . . .”). I will physically view the data-linked final weight numbers, I’ve already written the planned weight on my side panel clipboard as a reference, and I HAVE to see the correct number on the Control Display Unit screen. And at the same time, not taxi into the dirt or worse, any other jet. Not so easy at night.

But no worries–if it gets too hectic, timeout: “Let’s hold on the checklist here till we’re stopped.” Ever wonder why there’s a delay before take-off? While other jets are coming and going? Often, this is why. After leaving the gate, I’m completely detached from schedule constraints–we’ll get airborne as soon as all checks are thoroughly and correctly performed. As I tell F/Os when the tendency to rush starts to rear its ugly head, “We don’t get paid to rush. And if anything goes wrong as a result of rushing, no one’s going to be there to bail your ass out.”

Here’s where I like the silence, the bubble: no extraneous concerns beyond this flight. A departure path clear of weather and traffic. Verified speeds and weights in the flight guidance system, so the pitch and bank commands will be valid. But if they’re not, a mental review of what I know are the limits: greater than nine degrees of pitch up will drag the tail on the runway. Doesn’t matter what the flight guidance commands, my hands will not exceed a limit.

Waiting. Quick mental review of high-speed abort items: fire, failure, fear or shear. That is, after 80 knots, only an engine fire or failure, or my split-second judgment that I “fear” the aircraft is structurally not airworthy, or a detected windshear will cause me to abort the take-off before max abort speed, and after that–we’re flying with whatever we have.

I have options a hundred miles down the road, but also for liftoff: best single-engine climb angle, if we need it; left downwind to land south if we do. McChord 20 miles south with lots of runway. Fire and failure litanies. Mt. Ranier, all 14,410 feet of her, and where she is at all times.

Got it? 165 others are assuming that you do–so you’d better.

“American 116, line up and wait.” The tower’s direction. Real quiet now. Last minute runway checklist items. Ease in the power–there may be smaller jets behind us. Swing wide, line up on the center stripe; hold the brakes. Fire, failure, fear or shear. Minimum safe altitude. Engine failure profile. Initial level off altitude. No other thoughts. And no worries–this is gonna be fun.

Departure path is clear. “American 1116, cleared for take-off, runway one-six, wind one-five-zero at ten.”

“Rolling on one-six, American 1116.” All exterior lights on.  Another swig of java–we’ll get back to it on climb out–stand the throttles up; gages spring forward, then toggle take-off power on the autothrottles, hack the elapsed time button on the chronometer.

Both engines growl to take-off power–love that feel as they bite the air, compress it, mix in jet fuel and burn it, shoving us forward. Fifteen hundred miles to DFW–let’s get airborne.

Next Post: Part 3, enroute, and the landing.

aa

Going Down: What’s Up With Airliner Descents?

Feeling less than comfortable, even downright disturbed with all of the sensations of descending in an airliner? Wonder what all the noise, pitch, turning and weirdness is about? Step inside my head for an inside look at what goes on and why.

Here’s where it all starts:

No, seriously–you’re in my head, remember? That’s the “Jethead” thing. And this is where “descent” starts for me: running the half-mile in high school. Stay with me.

I’m a high school sophomore, hiding in the locker room with the other half-milers who like me, have already finished our heats.

We have to hide because Coach just discovered that one of our two-milers has no-showed for his heat, so someone will be pressed into service. Can’t forfeit those points!

“Cougar Manno, report to the starting line,” blares the loudspeaker in the locker room. Damn.

No, my name’s not “Cougar.” It’s just that after nearly two years on the team, Coach Smith–who also sees me every day in geometry which he teaches–still doesn’t even know my first name. We’re the “Del Campo Cougars–” that’s good enough, make him run the two-mile.

Here’s Coach’s mug shot:

Okay, this is Pythagoras (take that, Coach Smith) but this is where we get back to flying and what my sophomoric high school years have to do with it. And Pythagoras is key.

And here's the Del Campo track from a jet I was flying, after so many years and laps watching jets above, swearing I'd fly one too--if I could pass geometry.

Say we’re approaching our destination in an airliner. We’re at cruise altitude. Our destination is ahead by a certain number of miles, we’re a certain number of miles up. Picture starting to form yet?

You can see that we’re going to have to slant our flight path downward and cover the distance to the destination at an angle, right? Two important points on that.

First, because Coach Smith taught that our flight path from altitude to destination is the hypotenuse of this triangle–it is longer than both other distances, right? This, if you care to consider it, is why “air miles” are different from “ground miles:” you fly a hypotenuse up and down from altitude, making the straight line distance between two points longer by two hypotenuses–hypoteni?–whatever, you get it, right?

Second, clearly the nose-down angle is going to need to be steeper if we’re closer to our destination than if we’re farther back, where we can make a very shallow descent. And here’s just a little more math to figure the “where” and “when” of a descent:

You have a certain amount of altitude to lose–for example, ten thousand feet–for a restriction. You have a certain amount of time between now and the crossing point. Index the two–a certain number of feet in a certain number of minutes–and you have the required descent rate in feet per minute. If I have ten thousand feet to lose in five minutes, I need a rate of 2,000 feet per minute.

If only it were that simple.

Okay, sometimes it is, and that’s what you perceive as a smooth descent. But other times, Air Traffic Control has specific requirements regarding how soon you’re allowed to descend. They add restrictions, too: cross a certain point at a particular altitude and speed. Then often some other contingency pops up to screw all the angles and numbers you’ve planned:

There goes your formula as well as your smooth, flat descent angle, and here come the speedbrakes:

They disrupt the clean airflow over the wing, and you can see why–they’re like a board pushed out into the slipstream over the normally smooth wing. So there’s a good deal of rumbly vibration, right? Here’s where they are in the cockpit:

The noise and bumpiness are no big deal–the aircraft is designed for this, and most of the noise and turbulence is from the wind. It’s like when you’re driving down the freeway and open a window–lots of wind noise, which is what a slipstream is: disturbed air. Loud, annoying even, but harmless.

What the speedbrakes are doing, however, is important: they’re catching you up on the formula above when some factor alters one of the numbers in any of the three key variables: time, distance, and altitude.

It’s a three cornered relationship–another triangle, right Coach?–whose sides are constantly in flux due to conditions. I’m always visualizing the three variables and how they are fitting and changing due to circumstances like altered restrictions, winds, and speed changes. The alternative to speedbrakes for increasing a descent, which I recall wistfully from my other flying life, you definitely won’t like, or certainly not the 4-G level-off at the bottom:

Sorry, just another quick flashback. Anyway, starting a descent farther out allows for a shallow, smooth descent–think of the triangle. Delaying the descent necessitates a steeper rate: the combination of feet per mile and thus feet per second. There’s the big angle that feels like a plunge when circumstances dictate a higher than usual descent rate.

In my Toronto example above, other traffic below kept us from starting our descent as far out as I’d have liked. Yes, ATC could have vectored that other aircraft out of our way, or even vectored us off to one side. But they didn’t. Suddenly, the time-distance-altitude triangle is changed.

As pilots, we’re always watching that geometric relationship develop in our heads–thanks Coach Smith–and I’m always planning a strategy accounting for the variables like crossing traffic and one I haven’t mentioned yet: tailwind.

Top left corner, “GS 526” means “Groundspeed 526,” even though our true airspeed is in the 400s. That’s because of the “276/107,” which is right above the arrow, which is showing the wind angle. Means that whatever speed we’re showing on our airpeed indicator, add the wind to that, because we’re in the airmass which is itself  moving at 107 knots.

It’s this deal:

No matter what speed they’re paddling, the raft’s in the swift-moving roaring torrent of fluid.

Air is a fluid, and 107 knots is a torrent. Which eats up our hypotenuse quickly and in my triangular mental image–I realize we need drag to descend by the restriction. And probably a steeper deck angle, plus drag like the speedbrakes and if we really need all the drag possible, the landing gear too.

Again, more noise, but the gear hanging is like a drag chute slowing us down–we can really lower the nose and keep the speed under control nonetheless, dropping our jet in the technical terms I’ve perhaps used more than once, “like a turd off a tall moose.”

How about a little privacy here?

But why, you might ask, don’t we start all descents way out from the destination so as to ensure a shallow, comfortable descent?

Well, for a couple of important reasons. First, it makes good business sense to stay at a higher altitude to take advantage of the lower fuel consumption and the favorable tailwinds. But as a pilot, I’m naturally a fuel miser: I want every pound of fuel in reserve for any contingency we might encounter–weather, mechanical, a runway closure, whatever.  Because–another flashback on my part–we can’t just air refuel like back in that other flying life.

"I think a 5,000 pound top-off will do."

Plus, the airspace is crowded more today than ever. If you plan to get into a major airport, you have to do your part to assure the traffic sequencing: increase that descent when Air Traffic Control needs it, and be mindful of the restrictions ahead. Because you folks in back have connections to make and schedules to keep, right?

Which means, of course, skillfully flying the hypotenuse, adjusting the triangle relationship of speed, distance and altitude. Squeeze in the feet per minute required to fit into the traffic mix.

And when you as a passenger on descent hear the noise of the landing gear or speedbrakes, feel the rumble, and notice the deck angle steepening, you can turn to your seatmates with a knowing nod and reassure them by dropping a few phrases since now you know about the “what” and the “why” of the fluid time-altitude-distance triangle.

Just smile and say, “Yup, boards are coming up,” or “guess they needed to catch up on the descent and a speed restriction” or if they still don’t seem reassured, flash a smug grin, then casually turn back to your newspaper with a bored yet oh-so-knowing, “like a turd off a tall moose.” Tell ’em you learned that from Coach “Cougar” Smith back at Del Campo High School.

****

Now, are you still worried about approaches and landings? Stay tuned, stay subscribed: we’ll take the mystery out of both very soon.

Turbulence: A Moment of Silence, Please.

Can we talk for a minute? I mean crew to crew? If you’re not flightcrew, this may be boring. Sorry.

But still, let’s talk about not talking for a minute. Here’s the deal:

We’re flying along fat dumb and happy. Then, it gets bumpy. I turn the seatbelt sign on. What do you NOT do? Or more accurately, what do I wish you wouldn’t do?

Call the cockpit. Seriously. What we get more often than not these days is, bumps, then ding-ding. “It’s for you,” I say to the First Officer, even though I am monitoring the flight interphone in my headset. Then I get the thanks a lot look from the F/O who reluctantly picks up the phone.

But I already know what the flight attendant’s going to say: “How long is it going to be bumpy?” or worse, “it’s really bumpy back here.”

Sigh.

First off, besides being an inane question, it shows a real lack of understanding of what just happened, plus what needs to happen. To begin with, if we knew the turbulence was there ahead of time, do you really think we’d fly into it? And given that we didn’t know it was there, how the heck are we supposed to know how long whatever it is we didn’t know about is going to last?

And truly, is it possible that it’s bumpy in back but not in the cockpit, so you really need to call and let us know?

Worse, either of us having to answer the phone with “we have no idea” or “yeah, it’s bumpy up here too” only prolongs the turbulence. Why? Because here’s what has to happen to get out of turbulence.

First, I have to decide if we can climb or descend. Are we light enough for a higher altitude and at that altitude, what is the margin between high speed and low speed stall? That is, a higher altitude may be habitable in smooth air, but not in turbulence–yes, the charts are broken out into smooth, light, moderate and heavy turbulence because it affects both speed control and the airfoil. Given that we are in turbulence at this geographic location, there’s a darn good chance it extends above and below us here as well.

If the margin between high and low speed buffet–Coffin Corner, as it is known–is sufficiently wide in my judgment, then climbing is one option.

The other is descent but that has a catch as well. Yes, the Coffin Corner spread is more favorable. But now we have to worry about fuel burn, which is higher in the denser air of lower altitude–which is why we cruise at the optimum altitude for fuel burn and Coffin Corner spread. I have to calculate whether the increased fuel burn allows for sufficient arrival fuel to accommodate the destination situation–and that varies.

Going into Omaha? Seldom if ever an arrival delay. Atlanta? Chicago, La Garbage? Better have flexibility and loiter time–which means fuel. Plus, the destination weather: with a low ceiling and visibility, even Omaha isn’t a slam dunk.

The final gotcha about descending to a lower cruise altitude because of turbulence is the increased fuel burn it’s going to take to return to the optimum cruise altitude when it’s reported smooth again.

With me so far? Then we need to call air traffic control and find out the ride report and the winds at a higher or lower altitude. Why? because a higher (or sometimes lower) altitude can have a significantly larger headwind, which again affects fuel burn, never mind arrival time. Anyway, calling takes time, then it takes more time for Air Traffic Control (ATC) to find the info we’re asking for.

Once we know the winds and the reported ride conditions, it’s back to a decision about up or down, based on the fuel endurance and destination weather factors I just explained. That all takes time too.

Once we’ve determined the best option, we request a new altitude from ATC, then wait for them to coordinate a new altitude–which also often comes with a catch: sometimes, they’ll need you to turn off course to gain spacing from another aircraft either in the airspace we need to climb through or at the altitude we’ve requested. Again, more fuel. Can we do that?

And then there’s the climb or descent itself: it takes minutes even after the minutes of calculations, requests and clearances.

None of that starts till we’re off the phone with you. Because in a two-man cockpit, both of us must be fully in the decision loop, as well as the execution of the changes in altitude and heading. And even then, we may find the new altitude is not smooth either–in which case the whole process starts over.

You can trust me on this: once we encounter turbulence, we immediately go to work to find a better ride. But none of this happens while you’re calling us. And we’d do it whether you called or not–so don’t delay the process.

If you’ve ever flown with me, you know this: if I know of any turbulence ahead, I’ll call back and tell you to “grab yourself a buttload of jumpseat–she’s gonna buck.” If I haven’t told you and it is suddenly bumpy–grab yourself a buttload of jumpseat–and wait for us to start the process of finding smooth air.

We’re definitely aware of the turbulence and looking for smoother air. All we need is a moment of silence.