Landing at the Wrong Airport

On Saturday, June 19th, 2004, Northwest Airlines flight 1152, an Airbus A319 en route from Minneapolis to Rapid City, South Dakota carrying 117 passengers and five crewmembers, touched down smoothly just after 12 p.m. Trouble was, they weren’t in Rapid City. They’d arrived at Ellsworth Air Force Base, a military airfield six miles from the Rapid City Regional Airport.

Remarkable as it might sound, the unannounced landing — which, as my mailbox burstingly attests, did not go unnoticed by news-savvy readers of Salon — was not unprecedented. Years ago a Western Airlines 737 pulled a similar maneuver in Wyoming, and in 1995 a DC-10 touched down in Brussels instead of Frankfurt. A crew once confused the northern Maine outposts of Caribou and Presque Isle, while most recently, in January of this year, a US Airways Express flight bound for State College, Pennsylvania, ended up in Philipsburg, Pennsylvania.

If you’re like me, you wouldn’t know the difference between State College and Philipsburg if you were sitting in the lobby of city hall, but the idea of highly trained aircrews with troves of technology at their behest landing astray sounds, I’ll agree, amusing, quaint, and even patently ridiculous. The letters I’ve received in the past several days are equally aghast, incredulous, and cackling.

How does it happen? Anticipated by some is an answer of tangible malfunction: improperly keyed coordinates or a navigational computer gone crazy. Others suspect a more visceral, seat-of-the-pants explanation: a tired crew mixing up a pair of similar-looking runways.

After the Ellsworth incident, an Air Force spokeswoman reminded a dumbstruck press and media that the crew’s intended runway at Rapid City airport is “just over the hill” from Ellsworth. Implication: pilots find their airport the way a lost motorist finds his way home: second hill on the left, slight bank over the lake, watch for the farmhouse. Comments like these entice you to miss the big picture — in this case the vast context of the airspace system. I’m betting you don’t want a dissertation on the innards of instrument approaches or a glossary of ATC vernacular, but the complexities of even the most ordinary good weather landings are a bit more involved than lazy pilots craning their necks and saying, “Yeah, that looks like the right place, let’s give it a try.”

In addition to whatever human errors catalyze such events, weather and air traffic control (ATC), to name two, can lend a hand in getting from point A to, as it were, point C. In the case of that DC-10 finding its way to Belgium instead of Germany, a confusing string of foul-ups caused controllers essentially to lead the plane astray. By the time the crew realized it was being vectored to the wrong country, they decided to land at Brussels rather than have to recalculate fuel reserves and orchestrate a last-second re-routing. In the end, it was safer to land in Brussels than Frankfurt.

At the same time, yes, pilots cleared for what we call a “visual approach,” a procedure used with fair routine when sky conditions permit, will merely eyeball an airport through the windshield and report “field in sight,” to ATC.

Descending toward Rapid City, the Northwest crew was flying a so-called VOR approach, a fair weather, non-precision instrument procedure designed to guide aircraft toward the general vicinity of the runway, if not to the very threshold as with more accurate ILS approaches. Sixteen miles out, they’d intercepted the inbound course and began tracking it toward the airport. Emerging below a layer of clouds, they identified what was believed to be the correct runway and configured their jet for landing. What they’d seen, of course, was Ellsworth, its runway sharing an almost identical alignment with the intended strip at Rapid City, still about six miles away.

The carrier refuses to comment on who or what may have been responsible for the Ellsworth touchdown, and is keeping mum on everything from the pilots’ names to their levels of experience. This is neither surprising nor unfair, and it’s any investigator’s policy to refrain from passing judgment when events are fresh and particulars still unknown. This is a business where the determined causes of accidents and incidents rarely conform to the earliest suppositions and theories.

Disclaimer out of the way, I’ll tell you what I think: The crew, it appears, committed the simple bungle of assuming one airport was another. “Pilot error,” a buzzword we’re all acquainted with. Here we find it unusually, even shamefully, obvious.

In the winter of 1990 I was part of a crew cleared for a nighttime visual approach to New Haven, Connecticut. Suffice to say that the lights and orientation of Bridgeport appear strikingly similar to those of New Haven, and after a minute or two we realized the error and corrected course. All of this happened far from the runway, and we were flying a 15-seat Beech-99 turboprop, a vintage ’68 relic with as many electronic accoutrements as my mountain bike.

What makes the Northwest example so baffling is the seeming nullification of all the safeguards on hand. At the pilots’ disposal were more than enough cockpit gizmos and published charts reminding them of Ellsworth’s vicinity to Rapid City. Since when do we entrust our lives and fancy planes entirely to the humble predilections of judgment, no matter the complications or contributing factors? People make mistakes, big and small, and technology is intended to catch them. (And, understandably, vice versa). Flight 1152 was a small but relatively state-of-the-art Airbus A319 (a sub-model of the popular and somewhat indistinguishable A320). The captain and first officer sat before a multi-screen panel of high-tech computers and “moving map” guidance systems.

(Still to be determined is why ATC was unable to relay a warning to the wayward Airbus. Both Ellsworth and the Rapid City personnel could have tracked the diversion, though it’s possible the plane had dropped beneath radar coverage.)

“I find it startling,” says a Northwest first officer assigned to the A320, “that the crew managed to do what they did, especially with such an advanced airplane. The proper flight path — right to the very runway — is displayed graphically on the cockpit nav displays, regardless of what instrument procedure is in use. The mistake would have been very apparent.”

Asked if any type of technical miscue may have led to the confusion, the pilot, who asks not to be identified, claims it a virtual impossibility. “The nav displays would not let this happen. I suspect the pilots were simply locked in, visually, to what they saw outside.”

Last year, when an Air Canada jet came close to landing at Vernon, British Columbia, instead of Kelowna, about 40 miles away, we heard similar reasoning. Due to forest fires, the plane had been assigned an unorthodox routing and the crew became fixated on topographical landmarks. “My guess,” said a pilot, “is the guys just had their heads out the window and weren’t aware of where they were.”

The act of landing a plane is at once inordinately simple (subject to no more fancier gizmos than a pilot’s eyes and ears) yet simultaneously beholden to the guidance of technology (high-tech instrument and procedural rigors). Thus, this becomes one of the most challenging phenomenon for a pilot — even one who moonlights as a columnist — to dissect or analogize for the layperson. Call it a cop out, but a part of me wants to shout back at all those emails asking “How the hell does it happen?” with a simple and equally frustrated, “I DON”T KNOW!”


This article is part of a collection that originally appeared on Salon.com. Patrick Smith, 38, is an erstwhile airline pilot, retired punk rocker and air travel columnist. His book, Ask the Pilot (Riverhead) was voted “Best Travel Book of 2004” by Amazon.com. Patrick has traveled to more than 55 countries and always asks for a window seat. He lives near Boston.