Why do air traffic controllers kill themselves

Shortly after the plane took off, traffic controllers were heard on an Internet livestream speaking to a man identified as 'Rich'.

'There is the runway just off your right side in about a mile, do you see that?' the traffic controller said.

'Oh those guys will try to rough me up if I try land there…,' Rich replied. 'I think I might mess something up there too. I wouldn't want to do that. Oh they probably have got anti-aircraft.'

'They don't have any of that stuff, we are just trying to find you a place to land safely.'

'Yeah, not quite ready to bring it down just yet, but holy smokes I need to stop looking at the fuel 'cos it's going down quick.'

'OK, Rich, if you could, could you start a left-hand turn and we'll take you down to the south-east.'

'This is probably jail time for life, huh? I would hope it is for a guy like me. '  

Rich: I've got a lot of people that care about me. It's going to disappoint them to hear that I did this. 

I would like to apologize to each and every one of them. Just a broken guy, got a few screws loose I guess. Never really knew it, until now

Rich: I'm down to 2,100, I started at like 30-something. 

Air traffic control: Rich, you said you had 2,100 pounds of fuel left? 

Rich: Yeah, I don't know what the burnage, burnout? Is like on a takeoff, but yeah, it's burned quite a bit faster than I expected.

Air traffic control: Right now he's just flying around, and he just needs some help controlling the aircraft.

Rich: Nah I mean, I don't need that much help. I've played some video games before. I would like to figure out how to get this… make it pressurized or something so I'm not lightheaded.

Rich: Ah minimum wage. We'll chalk it up to that. Maybe that will grease the gears a little bit with the higher-ups

Rich: Damnit Andrew, people's lives are at stake here.

Air traffic control: Ah Rich, don't say stuff like that.

Rich: I don't want to hurt anyone, I just want you to whisper sweet nothings into my ear.

Rich: Hey do you think if I land this successfully Alaska will give me a job as a pilot? 

Air traffic control: You know, I think they would give you a job doing anything if you could pull this off. 

Rich: Yeah right! Nah, I'm a white guy

Air traffic control: If you wanted to land, probably your best bet is that runway just ahead and to your left. Again, that's McCourt (sic) Field. 

If you wanted to try, that might be the best way to set up and see if you can land there. Or just like the pilot's suggestion, the other option might be over Puget Sound, into the water. 

Rich: Dang, did you talk to McCourt, cause I don't know if I'd be happy with you telling me I could land like that, cause I could really mess some stuff up. 

Air traffic control: Well Rich I already talked to 'em. Just like me, what we want to see is you not get hurt, or anyone else get hurt. So if you want to try to land, that's the way to go. 

Rich: Hey I want the coordinates of that orca, you know, the mama orca with the baby. I want to see that guy.

Rich: Hey, is that pilot on? I want to know what this weather is going to be like in the Olympics (mountains). 

Air traffic control: Well, if you can see the Olympics, the weather's good. I can see the Olympics from my window, and it looks pretty good over there. 

Rich: Alright, 'cause I felt some, what felt like turbulence around Rainer, but there was no clouds hardly. 

Air traffic control: Oh, that's just the wind blowing over all over the bumpy surfaces there.

Captain Bill: Alright Rich, this is Captain Bill. Congratulations, you did that, now let's try to land that airplane safely and not hurt anyone on the ground. 

Rich: Alright, damnit, I don't know man, I don't know. I don't want to… I was kind of hoping that would be it, you know.

Rich: I'm gonna land it, in a safe kind of manner. I think I'm gonna try to do a barrel roll, and if that goes good, I'm just gonna nose down and call it a night. 

Air traffic control: Well Rich, before you do that, let's think about this. I've got another pilot coming up, pilot Joel, in just a minute here I hope. And we'll be able to give you some advice on what to do next.

Rich: I feel like one of my engines is going out or something.

Air traffic control: OK Rich, if you could, you just want to keep that plane right over the water. Maybe keep the aircraft nice and low.

Rich: Just kind of lightheaded, dizzy. Man, the sights went by so fast. I was thinking, like, I'm going to have this moment of serenity, take in all the sights. There's a lot of pretty stuff, but they're prettier in a different context.

Air traffic control: Do you have any idea of how much fuel you have left? 

Rich: Oh man, not enough. Not enough to get by. Like, uh, 760? 760 pounds?

Air traffic control: Just flying around the plane, you seem comfortable with that?

Rich: Oh hell yeah, it’s a blast. I’ve played video games before so I know what I’m doing a little bit.

Air traffic control: OK, and you can see all the terrain around you, you’ve got no issue with visibility or anything?

Rich: Naw, everything’s peachy, peachy clean. Just did a little circle around Rainer, it’s beautiful. I think I’ve got some gas to go check out the Olympics (mountains).

Rich: I wouldn’t know how to land it, I wasn’t really planning on landing it.

Rich: Sorry, my mic came off, I threw up a little bit. I’m sorry about this, I hope this doesn’t ruin your day.

Rich: Man, have you been to the Olympics? These guys are gorgeous, holy smokes.

Air traffic control: Ya, I have been out there, it’s always a nice drive.

Rich: (inaudible)

Air traffic control: Hey I bet you do. I haven’t done much hiking over there. But if you could start a left turn, and back towards the east. I know you’re getting a good view there, but if you go too much farther in that direction I won’t be able to hear you anymore.

Rich: Hey pilot guy, can this thing do a backflip, you think?

Rich: I wouldn’t mind just shooting the s**t with you guys, but it’s all business, you know?  

This post originally appeared in WIRED.

On Friday, Sept. 26, 2014, a telecommunications contractor named Brian Howard woke early and headed to Chicago Center, an air traffic control hub in Aurora, Illinois, where he had worked for eight years. He had decided to get stoned and kill himself, and as his final gesture he planned to take a chunk of the U.S. air traffic control system with him.

Court records say Howard entered Chicago Center at 5:06 a.m. and went to the basement, where he set a fire in the electronics bay, sliced cables beneath the floor, and cut his own throat. Paramedics saved Howard’s life, but Chicago Center, which controls air traffic above 10,000 feet for 91,000 square miles of the Midwest, went dark. Airlines canceled 6,600 flights; air traffic was interrupted for 17 days. 

Howard had wanted to cause trouble, but he hadn’t anticipated a disruption of this magnitude. He had posted a message to Facebook saying that the sabotage “should not take a large toll on the air space as all comms should be switched to the alt location.” It’s not clear what alt location Howard was talking about, because there wasn’t one. Howard had worked at the center for nearly a decade, and even he didn’t know that.

At any given time, around 7,000 aircraft are flying over the United States. For the past 40 years, the same computer system has controlled all that high-altitude traffic—a relic of the 1970s known as Host. The core system predates the advent of the Global Positioning System, so Host uses point-to-point, ground-based radar. Every day, thousands of travelers switch their GPS-enabled smartphones to airplane mode while their flights are guided by technology that predates the Speak & Spell.

If you’re reading this at 30,000 feet, relax—Host is still safe, in terms of getting planes from point A to point B. But it’s unbelievably inefficient. It can handle a limited amount of traffic, and controllers can’t see anything outside of their own airspace—when they hand off a plane to a contiguous airspace, it vanishes from their radar.

The FAA knows all that. For 11 years the agency has been limping toward a collection of upgrades called NextGen. At its core is a new computer system that will replace Host and allow any controller, anywhere, to see any plane in U.S. airspace. In theory, this would enable one air traffic control center to take over for another with the flip of a switch, as Howard seemed to believe was already possible.

NextGen isn’t vaporware; that core system was live in Chicago and the four adjacent centers when Howard attacked, and this spring it’ll go online in all 20 U.S. centers. But implementation has been a mess, with a cascade of delays, revisions, and unforeseen problems. Air traffic control can’t do anything as sophisticated as Howard thought, and unless something changes about the way the FAA is managing NextGen, it probably never will.

This technology is complicated and novel, but that isn’t the problem. The problem is that NextGen is a project of the FAA. The agency is primarily a regulatory body, responsible for keeping the national airspace safe, and yet it is also in charge of operating air traffic control, an inherent conflict that causes big issues when it comes to upgrades. Modernization, a struggle for any federal agency, is practically antithetical to the FAA’s operational culture, which is risk-averse, methodical, and bureaucratic. Paired with this is the lack of anything approximating market pressure. The FAA is the sole consumer of the product; it’s a closed loop.

The first phase of NextGen is to replace Host with the new computer system, the foundation for all future upgrades. The FAA will finish the job this spring, five years late and at least $500 million over budget. Lockheed Martin began developing the software for it in 2002, and the FAA projected that the transition from Host would be complete by late 2010. By 2007, the upgraded system was sailing through internal tests. But once installed, it was frighteningly buggy. It would link planes to flight data for the wrong aircraft, and sometimes planes disappeared from controllers’ screens altogether.

As timelines slipped and the project budget ballooned, Lockheed churned out new software builds, but unanticipated issues continued to pop up. As recently as April 2014, the system crashed at Los Angeles Center when a military U-2 jet entered its airspace—the spy plane cruises at 60,000 feet, twice the altitude of commercial airliners, and its flight plan caused a software glitch that overloaded the system.

Even when the software works, air traffic control infrastructure is not prepared to use it. Chicago Center and its four adjacent centers all had NextGen upgrades at the time of the fire, so nearby controllers could reconfigure their workstations to see Chicago airspace. But since those controllers weren’t FAA-certified to work that airspace, they couldn’t do anything. Chicago Center employees had to drive over to direct the planes. And when they arrived, there weren’t enough workstations for them to use, so the Chicago controllers could pick up only a portion of the traffic.

Meanwhile, the telecommunications systems were still a 1970s-era hardwired setup, so the FAA had to install new phone lines to transfer Chicago Center’s workload. The agency doesn’t anticipate switching to a digital system (based on the same voice over IP that became mainstream more than a decade ago) until 2018. Even in the best possible scenario, air traffic control will not be able to track every airplane with GPS before 2020. For the foreseeable future, if you purchase Wi-Fi in coach, you’re pretty much better off than the pilot.

A big, high-risk infrastructure upgrade like NextGen will never move as fast as change associated with consumer technology, but the real hurdles are not technical, they’re regulatory. In the private sector, new technologies can be developed freely regardless of whether the law is ready for them. Think of Uber, Lyft, and Airbnb: Outdated regulations slowed them down, but consumer demand is forcing the law to evolve. This back-and-forth is what lets tech companies move fast and break things without risking our safety. But when the government upgrades its technologies, regulations intercede before a single line of code is written.

The government procurement process is knotted with rules and standards, and new technology has to conform to those rules whether or not they’re efficient or even relevant. These issues screwed up HealthCare.gov and are screwing up the Department of Veterans Affairs and a dozen other agencies that need computers and software that work. The current process stifles innovation from the start and mires infrastructures like NextGen, which need to carry us far into the future, in the rules of today.

The government needs to change its procurement process, and it’s got to let go of its stranglehold on air traffic control. Privatization isn’t necessarily the answer. Canada, the UK, Germany, Sweden, and Australia operate air traffic control through various separate entities, from semiprivate to nonprofit to government corporations, that help facilitate the necessary push and pull between technological risk-taking, regulatory caution, and pressure from end users.

The first real pressure on the FAA to show results came, ironically, from Howard. He forced what was essentially the first real-time operational test of the new system. When NextGen faltered, the program faced a level of widespread public scrutiny that it had previously evaded, and the FAA had to respond. The agency published a review of its contingency processes, including new plans to enable control centers to assist each other in emergencies. Brian Howard, hell-bent on destruction, was the best thing to happen to our air traffic control system in years.

More from WIRED:

The Rise and Fall of RedBook, the Site That Sex Workers Couldn’t Live Without

How Parks and Recreation Took Aim at Silicon Valley

Turns Out Boston Cyclists Can Engineer a Pretty Solid Snow Tunnel

This Wireless Explosives Detector Is the Size of a Postage Stamp

A New Way to Tell Stories That Outlive the Media’s Attention Span