by Rick Mofina
Cole opened the first cabinet. It was empty. So was the second.
“These were filled with files and material. Where is it?”
“Hold on.” Liz reached for her phone.
She made a call, then turned away from Cole to talk privately, which he took as a bad sign, as he searched among the other items. He touched things that had belonged to his wife and to his daughter. In this place, it made him realize how short and fragile life was.
“Sir?”
Cole turned to her. His heart skipped.
“We usually recycle all paper material, and that’s where my sons are now, at the recycling plant. They had a large load and added your material to it.”
“So it’s gone?”
“No. I stopped them, but if they bring the load back, that’ll be an additional cost.”
“I’ll pay it! Get them back here as soon as possible, please!”
For thirty-five tense minutes Cole waited with Liz, until the dogs barked and a five-ton truck grinded up to the hut’s back door. As country music leaked from the truck—Johnny Cash—Liz and her sons helped Cole locate his property. After he’d agreed to a payment of four hundred dollars, they’d helped him load his pickup truck.
During the long, lonely drive back to Clear River, Cole considered all of his items bundled in the bed of his truck.
I don’t know if I still have the skill to develop an answer to the system’s weakness. His hands tightened on the wheel. And do I have the time before the next tragedy?
Thirty-Five
Manhattan, New York
Kate worked at her desk, mining the article for useable information.
It was a report in the Chicago Tribune on a speech President Bush had given to air industry workers at O’Hare International Airport a few weeks after the terrorist attacks on September 11, 2001.
The president’s remarks had focused on strengthening air safety and security. Kate went to the link for the White House archives and printed off the full speech. In it, the president had promised action on a number of fronts.
Kate underlined one key section.
“We will look at all kinds of technologies to make sure that our airlines are safe,” the president had said, “including technology to enable controllers to take over distressed aircraft and land it by remote control.”
Remote control? What happened to this technology? Was it ever used? Kate chided herself for not finding this piece of information earlier and using it in her reports on EastCloud and Shikra.
It was there all this time and I missed it.
Chuck Laneer was not at his desk when she placed her printouts of her research on his chair. “I think we could have a story here,” she wrote in the yellow note she stuck to the package.
Thirty minutes later, Chuck called her.
“This will work,” he said. “And I have an idea on what we can do.”
He called Kate into his office, along with Hugh Davidson from the business section. Hugh reported on computer technology and was known as Newslead’s Emperor Nerd. He was partial to bow ties and pastel shirts.
Chuck had Tim Yardley with Newslead’s Washington bureau and Noah Heatley with the London bureau on the line. He turned on his speaker.
“You’ve all had a chance to look at the older clips. We’re going to build a story on this. Kate will lead. Hugh and Tim and Noah, I want you to feed whatever you can find on the subject to Kate.”
“Excuse me, but this issue’s been around,” Hugh said. “What exactly is new here? What’s the context?”
“We’ll build our story in relation to the questions surrounding Shikra’s crash in London and the near disaster with EastCloud at LaGuardia,” Chuck said. “Whatever happened to this remote-control technology the president promised? Does it exist? Could it have helped, or could it have somehow been in play and abused by some criminal group? We’ll come at the story fresh.”
“Why didn’t we do this earlier?” Noah asked from London. “Why didn’t we, or anyone else for that matter, pick up on this? I mean, there have been long-standing arguments in the aviation industry about the possibility of cyber hijacking, and conspiracy theories, all of these things.”
Chuck hesitated, glanced at Kate, thought for a moment.
“Besides,” Noah continued, “everyone here thinks Shikra was caused by a double engine failure due to an electrical malfunction arising from poor maintenance. Why is there such a desperate push for this odd angle? Is it because of the Zarathustra message Newslead received?”
“What Zarathustra message?” Hugh asked.
“All right, some background,” Chuck said. “This is confidential, but I’m not surprised that some of you know this. Newslead’s aware of two threats, emails, by someone claiming responsibility for Shikra and EastCloud. The one Kate received after the EastCloud story broke was from someone identifying themselves as Zarathustra. They claimed responsibility and wanted us to do a story crediting them or they’d cause harm to another aircraft.”
No one spoke as Chuck provided more context on the Zarathustra and Kuwait emails. When he’d finished, silence followed.
“If you were already aware, fine,” Chuck said. “If you weren’t, my apologies. We had to keep this tight. So consider yourself informed. None of this has been reported because the emails are unsubstantiated and we don’t want to create alarm in the commercial airline industry. We’ve alerted the FBI, which is assessing them.”
Chuck paused, inviting any comments, before he continued.
“There’s a strategic reason I want to proceed this way with this story.”
“Are you going to share that with us?” Hugh asked.
“Later. For now, we’ll take this one step at a time and we will make no mention of the emails unless we have confirmation of their credibility. Any questions?”
None were voiced.
“All right, let’s get busy.”
* * *
Kate drafted a list of sources and experts she intended to go to for the story. She reached out to Nick Varner at the FBI for any updates. There were none. She called the NTSB, the FAA, EastCloud, Richlon-Titan, Shikra and Talal Nasser, her source with Kuwait’s Aviation Safety Department. Kate also called Erich, asking if he had any updates. He said he was working on it.
Soon, copy came in from London and Washington.
Noah Heatley’s team filed chilling commentary from cyber experts from around the world claiming they could—in theory—hijack a jetliner remotely. Industry officials refuted those claims.
Yardley in Washington confirmed that Congress had approved five hundred million dollars for the fiscal year 2002 to go to the Transportation Department, to allow the air industry to fortify cockpit doors, ensure continuous operation of aircraft transponders in an emergency, and to provide “other innovative technologies to enhance aircraft security,” which many industry insiders interpreted as remote-control technology.
Working with Hugh, Kate interviewed leading aviation experts. She hit pay dirt when she reached Fred Winston, who headed an airline industry consulting firm in Los Angeles.
“That technology the president discussed evolved into the Continuous Autopilot System,” Winston told her. “It works like this—should the crew feel the plane is under threat of being hijacked physically, they throw a switch, allowing remote control of the plane by the ground, traffic control, which can remotely employ other auto features to land the plane safely. That system cannot be interrupted by anyone or anything in the cockpit or on the ground.”
“So what happened to the technology?” Kate asked.
“Several major airlines hold patents on variations of it,” Winston said. “But it was never applied, installed, or used in the commercial air industry.”
“Why not?”
�
��Safety issues,” Winston said. “Chief among them is the fear that somehow someone could hack the system—override and take control of a jetliner.”
“Could that happen?”
“I know a lot of experts might disagree, but I wouldn’t rule out the possibility,” Winston said. “In fact, there were rumors that the military, which can control aircraft remotely, had also developed a top secret remote auto-control system for landing distressed commercial jets, but that it somehow got leaked, or was stolen, creating fears it had fallen into the wrong hands and would be used to crash airliners.”
“What?”
“That’s the rumor, and many credible experts place it in the realm of conspiracy theories, so I don’t know how you would confirm that.”
Taking careful notes, Kate talked with Winston for several more minutes before thanking him and ending the call.
Pen clamped in her teeth, she began typing up the significant points of her interviews. As she weaved in the copy coming to her from Hugh, Washington and London, her heart raced.
This is shaping up to be a hell of a story.
Thirty-Six
Manhattan, New York
Kate’s face swam in and out of focus on the big screens throughout CTNB’s New York studio in the Time Warner Center at Columbus Circle.
She was perched on a stool at the desk, shoulder-to-shoulder with two other panelists, Cal Marshall, a former NTSB investigator, and Stuart Shore, a retired commercial airline pilot, now an air security consultant.
“We’re just four people discussing commercial air security,” said Reese Baker, the CTNB moderator, after glancing up from the monitor under the glass desktop. “Forget the cameras and talk to me like you’re talking to neighbors over the back fence.”
“Twenty seconds, everyone!” a voice called out.
“Kate, that was a great article yesterday. Excellent.” Reese smiled.
Kate’s story had explored the president’s security promise of remote-control technology, but it had also raised the fear of its use against commercial airliners. She’d set it within the context of the Shikra crash at Heathrow and the EastCloud incident at LaGuardia.
Working closely with Chuck, and never mentioning the two threatening emails they believed were sent by Zarathustra, Kate had produced a nuanced article, a “situational,” on the theory that the two flights could have been targets of cyber hijacking. She’d backed it up with balanced, on-the-record comments from experts and built it on the president’s pledge.
Let’s see what happens, Chuck had said.
Interest in the story had been strong, yielding a high level of pickup by subscribers across the US, in Europe, South America, the Middle East and Asia. It had prompted CTNB producers to request that Kate be a panelist the next day on Beyond the Headlines with Reese Baker.
The show’s guests had gone through makeup and a sound level test; camera angles had been checked and set. The theme music played, seconds were counted down and the program went live.
“Good afternoon. Mystery still envelops the Shikra Airlines crash at Heathrow, which claimed fifteen lives, and the chilling close call with an EastCloud flight to New York’s LaGuardia Airport. Could these two incidents be linked to potential hacking and a presidential promise to introduce remote-control technology in jetliners? That’s the subject of today’s panel. I’m Reese Baker and this is Beyond the Headlines.”
Reese turned from one camera and introduced a setup segment of CTNB news reports on the London and New York cases that ran for four minutes. When the producer threw it back to Reese, she introduced Cal Marshall, Stuart Shore and Kate.
“Let me take you back to September 27, 2001, two weeks after the terrorist attacks. President Bush, in a speech on aviation safety to air industry workers at O’Hare in Chicago, promised to introduce technology that would enable controllers on the ground—I’m quoting the president—‘to take over distressed aircraft and land it by remote control.’ Stuart, I’ll start with you. As a former commercial pilot and expert on airline security, does this technology exist?”
“Yes and no. Several airlines have the patents for it, but it hasn’t been applied in the commercial airline industry. Military applications are another issue, with drones and other types of aircraft, but the technology we’re talking about here, for commercial aircraft, is not employed today.”
“Cal, you’re a former investigator with the NTSB, a highly qualified expert. Tell us, could this technology somehow have been developed surreptitiously and used to take control of the Shikra and EastCloud planes?”
“Reese, first I want to stress that at this time we don’t know what happened in the cases of the Shikra and EastCloud flights. We’re not privy to all the evidence, data and facts. Only the people investigating are. And I can assure you that these investigations are meticulous and they take time. To be honest, to theorize about them, sitting here with no information at a desk in your studio, is a fool’s game.”
Reese smiled, acknowledging his point.
“Absolutely, but we’re free to address the implications of the type of technology promised by the president.”
“Let’s be clear,” Cal said. “The aim of the technology we’re talking about is the safe landing of a troubled plane by remote control.”
“Could it conceivably make a plane ‘hijack-proof’?” Reese asked.
“If we’re talking in-flight, then yes, I’d say it could,” Cal said.
“Could such technology be hacked?”
“No,” Cal said. “The design and the systems in aircraft make it impossible for a hacker to gain entry to the flight-management system to engage and control the aircraft. It’s just not possible.”
“But Cal,” Stuart said, “you can’t rule out all possibilities. If you could control a plane remotely from the ground, then your system is vulnerable to attack.”
The panel debated the subject until the show neared its end.
“I’m afraid we’re running out of time,” Reese said. “I’d like to close with you, Kate. You touched on this with your story. Why has this technology not been put into use? Let’s look at the Japanese airliner that disappeared over the Pacific a year ago, and the Argentine jetliner that crashed into the Andes. Some theories hold that they were hacked.”
“Well, in researching the story, we found a number of reasons why the system has not been installed.”
Kate explained that pilots had objected to it. In some cases, there were concerns that controllers couldn’t see all that pilots see in the cockpit, which could create a hazard. There were arguments that the skies were too crowded to make remote navigation safe.
“And there’s the fear that the system could be hacked?” Reese added.
“Yes, the fear that the system could be hacked was a major concern. However—” Kate looked directly to the camera “—while there are many conspiracy theories, claims and debates, there has yet to be a single confirmed case of a commercial aircraft being cyber hacked.”
“And that’s our time,” Reese said. “Thank you all for joining us. News is next.”
Thirty-Seven
San Francisco, California
Veyda Hyde and Seth Hagen worked on their laptops at San Francisco International Airport while awaiting their return flight to Washington National.
Veyda suddenly seized her computer because their seats had shaken violently. Her first thought was: Earthquake. Wrong. The force was a boy who’d slammed his body into the seat beside her.
“Here! Mom! I wanna sit right here!” He smashed his fists repeatedly into the seat, causing Veyda’s to bounce.
“We made it just in time.” The boy’s mother sighed as she arrived, struggling with their bags. The preboarding area for Washington, DC, passengers was next to the gate for an Atlanta-bound flight. The mother was e
ither oblivious or indifferent to her son’s behavior.
“Give me a cookie, now!” The boy jumped up and down, knocking over Veyda’s take-out coffee cup, which emptied around her feet. Aware of his crime, the boy met Veyda’s ice-cold glare, considered his situation, then pointed at her and said, “You made a mess!”
“No, you made a mess. Now, what do you say for being so rude?”
The boy’s eyes narrowed in defiance.
“Mom! That strange lady’s talking to me!”
“Oh, just look away, Billy. We’ll be leaving in a minute.”
The boy stuck out his tongue at Veyda, who glared back with such intensity the boy recoiled, retreating under his mother’s arm.
“Mom! That lady’s scaring me!”
The mother turned to Veyda, assessed her then pulled her son closer.
“Excuse me,” the woman said, “do you have a problem with my child?”
“Was your son deprived of oxygen at birth?”
The mother’s jaw dropped and Veyda stared at her for an uneasy moment, until the Atlanta flight was called.
“That’s us, Billy.” The mother stood. “Let’s get away from here.”
“I’ll pray for you,” Veyda said.
“What?” The mother stopped. “What did you say?”
“I’ll pray.” Veyda smiled. “That your plane doesn’t crash.”
Puzzled and unable to discern the full meaning of Veyda’s comment, the woman scowled and left with her cookie-eating offspring. Veyda shot the woman and her spawn a parting glare.
Some people shouldn’t be permitted to breed.
Veyda resumed her work, pleased that Seth had possessed the wisdom not to intervene. They’d come to the Bay Area to pick up a critical component they needed to complete the next phase of their operation, a highly advanced integrated circuit that was in the final stages of development. Seth knew people in Mountain View with access to one and had arranged to buy it. He’d concealed it in a small case that resembled a USB key, which he was now admiring.
