As a new administration arrives in the nation’s capital amid heightened scrutiny over conflicts between government service and personal business interests, a little-used law—the Stop Trading on Congressional Knowledge Act (the “STOCK Act”)—is deservedly getting renewed attention.
Although enacted in 2012 primarily to eliminate the then-existing doubt that insider trading prohibitions applied to congressional members and their staff, the STOCK Act also explicitly confirmed the ban on insider trading by members of the executive (and judicial) branch as well.
We’ve counted down our top posts from 2015, from American Apparel to Dr. Robert Schuller. Now, we look at the issues in executive disputes that are likely to draw the most attention in 2016.
Last November, we covered the Supreme Court oral argument in the case of Department of Homeland Security v. MacLean. As a refresher, MacLean was an air marshal who was fired by the Transportation Security Administration (TSA) after he blew the whistle to MSNBC on the agency’s plan to cancel marshal missions to Las Vegas. After the argument, Prof. Steve Vladeck of American University predicted that the TSA would lose the case.
He was right. On Wednesday, the Supreme Court issued its opinion, in which it held in favor of MacLean. The TSA argued that it could fire MacLean because his disclosures were “specifically prohibited by law” in two ways: first, it had adopted regulations on sensitive security information, which applied to the information MacLean disclosed; second, a provision of the U.S. Code had authorized TSA to adopt those regulations. Chief Justice Roberts, writing for the Court, rejected both arguments.
As to the regulations, he wrote, Congress could have said that whistleblowers were not protected if their disclosures were “specifically prohibited by law, rule, or regulation,” but did not. Thus, its choice to only use the word “law” appeared to be deliberate. Further, interpreting the word “law” broadly “could defeat the purpose of the whistleblower statute,” because an agency could insulate itself from liability by promulgating a regulation that prohibited whistleblowing. And as to the argument that Congress-passed “law” prohibited the disclosure, Chief Justice Roberts wrote that the statute in question did not prohibit MacLean’s disclosures. Instead, it was the agency’s exercise of discretion, not the statute, that determined what disclosures were prohibited.
A whistleblower generally shouldn’t break the law in order to prove his claims. Indeed, the Whistleblowers Protection Blog says that this is a “basic rule,” and cautions that an employee who breaks the law while whistleblowing in order to get evidence will suffer from attacks on his credibility and may even be referred for criminal prosecution. However, the parameters of this rule aren’t always so easy to follow, as the Supreme Court heard last week in the case of Department of Homeland Security v. MacLean.
The MacLean case arose from a warning and text message. In July 2003, the Transportation Security Administration (TSA) warned MacLean, a former air marshal, and his colleagues about a potential plot to hijack U.S. airliners. Soon after, however, the TSA sent the marshals an unencrypted text message, canceling all missions on overnight flights from Las Vegas. MacLean was concerned about this reduction in security, and eventually told MSNBC about it. The TSA then issued an order stating that the text message was sensitive security information (SSI). When it found out that MacLean was the one who disclosed the message to MSNBC, it fired him.
MacLean didn’t take this while reclining; he challenged his dismissal before the Merit Systems Protection Board. But he lost. The Board decided that TSA didn’t violate the federal Whistleblower Protection Act by firing MacLean for his disclosure, because MacLean’s disclosure violated a TSA regulation that prohibited employees from publicly disclosing SSI.
Talk about your inter-family disputes: one federal agency – the Department of Labor – has filed suit against the United States Postal Service, an independent federal agency (but one of the few explicitly authorized by the Constitution). The reason for the federal lawsuit, filed in Missouri: the Postal Service’s alleged poor treatment, firing, and alleged harassment of an employee who claims he blew the whistle on safety hazards in a mail facility.
Here’s the background, delivered despite any contrary weather: Thomas Purviance worked for the Postal Service for 35 years, most recently as a maintenance supervisor at a mail distribution center near St. Louis. He had no record of disciplinary or performance issues. In late December 2009, Purviance complained to his supervisors about what he perceived to be carbon monoxide and fuel oil leaks from some of the equipment at the center, as well as a pile of oil-soaked rags which he thought was a safety hazard. Getting no response, Purviance eventually called the local fire marshal and made a 911 call to report the carbon monoxide leak.
Yesterday, we reviewed a recent decision by a federal court in Richmond in the case of Vanterpool v. Cuccinelli (yes that one), and when firing a government employee for speech or political affiliation may be okay under the First Amendment. The answer is that it may be okay if the employee is in a policymaking position. The court’s decision spells out why and what it means to have such a position. The case is also a helpful reminder that staking out one position in litigation may undermine another.
In her first complaint, Vanterpool apparently did not want to say that she posted the comment criticizing Cuccinelli on the Washington Post because she had denied doing so when she was confronted about the comment by one of Cuccinelli’s deputies, Charles E. James, Jr., who was also a defendant in the case. James later questioned Vanterpool’s credibility and asked her to resign or be terminated. If Vanterpool alleged in the complaint that she personally posted the comment, then that could have bolstered a defense by Cuccinelli and James that she wasn’t fired for speaking freely but for being dishonest.
Earlier this month, a federal court in Richmond dismissed the lawsuit of a lawyer named Samantha Vanterpool who worked in the Virginia Office of Attorney General when Republican Ken Cuccinelli was Virginia’s AG and was running to be governor. (Democrat Terry McAuliffe won last November in a race that made national headlines.) Vanterpool claimed that she was fired on the basis of her political affiliation in violation of the First Amendment.
Vanterpool is a Republican but apparently not a Cuccinelli fan. She was fired after she allegedly posted a comment to a May 2012 Washington Post story about Bill Bolling, who was then challenging Cuccinelli for the Republican nomination. You can still see the comment (from “bzbzsammy”), which accuses “Cuccinelli of promoting Cuccinelli” while “Bolling is helping the GOP,” and of “NEVER [being] in the AG’s office and solely us[ing] the position for self promotion.”
In the first part of this series, we raised the question of whether a public employee’s rights under the First Amendment to the Constitution – primarily the right to speak freely on public issues – is limited by the fact that she works for the government. It’s the curious mix of the Constitutional rights we all enjoy, and the duty of the government to act as an employer when it hires and manages people to get things done. We looked briefly at how the Supreme Court addressed this issue: in short summary, public employees keep their rights to free speech on issues of public concern – but when they are speaking as part of their official duties, or their speech creates a disruptive atmosphere for the government agency, the employee can be fired for speaking out.
Two recent cases dealing with deputy attorneys-general illustrate this difficult intersection between public employment and speech. In both cases, the attorneys – a breed not known for silence – lost their jobs for speech: one for speaking out, and the other for refusing to speak when she was told to do so. Let’s see how their cases against their public employers are faring.
Some days when I look over the possible stories here, they’re filled with disputes between attorneys. It almost makes me think that my fellow editors at Suits-by-Suits and me are the only attorneys that can get along. Most of the time, at least.
Because if you are, or have ever dealt with, Attornicus Americanus, then you know two things about our profession: 1) we don’t like to be told to be quiet when we have something important to say; and 2) even worse, though, is telling us we have to say something that we don’t want to say. The two cases at issue in this two-part series feature lawyers working for the government who were in just those situations, and were fired. We look at recent interesting developments in their claims for retaliation. In passing, too, we’ll note what one of these lawyers was fired for saying, and what the other lawyer was fired for refusing to say.
All in all, these are posts about whistleblowing and retaliation claims by public employees – and not just attorneys, either. The public nature of the employment here is important because government employees keep some of their First Amendment rights to free speech when they go to work for the government. The government employer, for its part, has some limited right to limit its employees’ speech in order to get its mission accomplished. So before we turn to the two cases, a brief tour through the First Amendment rights of public employees is in order.
As the regulatory and business environments in which our clients operate grow increasingly complex, we identify and offer perspectives on significant legal developments affecting businesses, organizations, and individuals. Each post aims to address timely issues and trends by evaluating impactful decisions, sharing observations of key enforcement changes, or distilling best practices drawn from experience. InsightZS also features personal interest pieces about the impact of our legal work in our communities and about associate life at Zuckerman Spaeder.
Information provided on InsightZS should not be considered legal advice and expressed views are those of the authors alone. Readers should seek specific legal guidance before acting in any particular circumstance.