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.


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?
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.”
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?
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.

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.
We start engines, a ground man pulls the chocks and salutes: clear to go.
You’re traveling by air this summer? Good. But there are a few things you should know and be sure of BEFORE you get to the airport. And, of course, some shortcuts and time-savers and more things you should be aware of once you get to the airport to avoid an ugly surprise on check-in.
Combine that with tight customer service staffing and you have the makings of a travel headache–which is preventable. Read on.
2. Know your status. That is, are you protected from cancellations or delays? If you have a deadline at your destination–say, a time sensitive event (wedding, graduation, business meeting, etc) or follow-on reservations (a resort or cruise booking, or flight on another carrier), what protection do you have in the event of a delay or cancellation?
Be aware that most airlines offer compensation or modified travel in the event of situations within their control (say, flight cancellations or mechanical delays), but most people don’t seem to know that airlines and federal regulations do not stipulate any accommodation for weather-related delays or cancellations. Thunderstorms at a major hub, in summer–what are the chances? Pretty darn good, unfortunately. And along with rain, hail, and damaging winds, storms usually bring delays, cancellations and misconnects.
Are you prepared to sleep on the floor of the terminal if weather delays you inbound and the last flight of the day to your destination has already departed? Don’t plan tight connections–or in my opinion, any connections to the last flight of the day, for exactly that reason. But if you must, be prepared to find an airport hotel on your own or, sleep in the terminal. Ugh.
One further note about “knowing your status,” and this is important: did you buy your ticket from an online source other than the airline itself? If so, read the “conditions of carriage” before you agree to the purchase of a ticket: many of the larger online travel sites sell bargain basement seats–but they are for a specific flight, with no recourse if you miss the flight. In other words, the deeply discounted seat does not come with any airline follow-on obligation–that’s how the online site got the cheap pricetag they sold you on. But again, if you misconnect for any reason, your travel is over.
First, sign up for whatever notification app your airline offers. Not only will this automatic function give you an immediate heads-up on your assigned gate and departure time via text message or email, many major airlines will also notify you of a cancellation or significant departure or arrival delay long before the delay appears on monitors in the terminal.
Want to play Superman? Turn your cell phone on as soon as allowed after landing. You’ll be notified by text or email of any cancellation on your itinerary–then you can call the re-booking number on taxi-in and start damage control to save your trip. Same goes for the hours before your origination–keep listening for the text alert regarding your flight. Even if things go well, you’ll want to know what gate you’re scheduled to depart from. In all cases, have your reservation info handy for re-booking–an agent on the phone or face-to-face can access your itinerary instantly if you can provide the record identifier (usually a series of letters and/or numbers) on first contact.
It’s going to be a busy summer for air travel this year, with record crowds and limited customer service options in the case of weather-related delays. But these three simple steps will put you well ahead of the crowd all rushing to rebook flights or deal with a delay. Secure your seat, know your options, stay informed and be ready to rebook.














Sure, he says it goes into a vein in my arm and I won’t feel a thing, but I’ve been screaming my head off from the examining room to the lab just in case–because I don’t believe him. And you just know everything’s going to go haywire and oops, sorry about the needle in your eye and it hurts like hell, doesn’t it?
Now, how to answer that? “Well I’d have to say that around the Ohio Valley/Rust Belt which on the timeline is about your teen years, things could get ugly.” Because we have a coast-to-coast sea of roiling air miles ahead and yes, the teenage years may be bumpy, expect a little declining baldness near the middle-aged Great Plains of your life and God knows you can’t even dream of the desert spread of yawning cracked scorched earth mesas and desolation which lies before the emerald paradise coast, then the endless blue above and below and beyond. You know you really shouldn’t have asked. Newborns can’t, five-year-olds don’t; thirty-somethings shouldn’t but that’s the downside of holding the needle for a living.
Because in the great yawning maw of the sky and life and the dreamy arc of flight–ain’t no smooth rides. But how do you tell someone, convince a person, that the needle isn’t going to stick in his eye? Still, though, life’s going to get downright bumpy enroute but just hang on.
Twenty-five thousand feet, puffy clouds above and below and the red dirt pancake of West Texas sprawled wide as the eye can see. Aloft in the “two thousand pound dog whistle” jet trainer, Air Force Flight School, filling my oxygen mask with sweat; my helmet chafing, ejection seat cinching me tight.
Which doesn’t seem like a good idea to do in a jet. But it’s part of the syllabus: you need to learn how to do this, to get out of this before you fat-splat onto Prairie-dise below. Because you’re going to fly solo once you master it–or you’re going to wash out if you can’t.
Ignore the blur, take the right steps: slam the stick forward; opposite rudder, power on, recover from the dive. And from that moment on, own the sky. No matter what.
