Argument preview: A look at “state secrets”
The Supreme Court at 10 a.m. Tuesday will hold one hour of oral argument on the government’s use of the “state secrets” doctrine to limit a Pentagon contractor’s claim for payment after a military project has been halted before completion. The consolidated cases are General Dynamics Corp. v. U.S. (09-1298) and Boeing Co. v. U.S. (09-1302). Arguing for the two companies will be Carter G. Phillips of the Washington office of Sidley Austin. Acting U.S. Solicitor General Neal K. Katyal will argue for the federal government.
For nearly 60 years, the Supreme Court has opted to stay largely on the sidelines of a controversy that has continued to swirl around one of the most potent legal weapons that the federal government has available to protect its defense and other national security secrets. It is called the “state secrets” doctrine, and the Court has not examined the full scope of the doctrine since 1953, when it decided U.S. v. Reynolds. It allows the government to short-circuit a lawsuit against it, if the evidence that is key to the claim is a “state secret” and cannot be brought into court without risking its public exposure. In 1953, it was understood as a limit on specific items of evidence; more recently, it has been applied to end some cases altogether, without a trial.
Several times recently, the Court has refused to reconsider the doctrine in cases seeking to challenge government actions during the “war on terrorism.” Later in this Term, it will consider whether to take up one such case — a dispute involving the alleged program of secretly capturing terrorism suspects, and sending them to foreign countries for interrogation or detention (Mohamed, et al., v. U.S., et al. 10-778).
But the Court in September did agree to rule on a new “state secrets” dispute, involving the use of that doctrine to shield weapons technology secrets from two major defense contractors for use in their multi-billion-dollar claim against the Pentagon. As that case reaches the Court, it does not involve a direct challenge to the “state secrets” doctrine; the contracting firms do not contest the Pentagon’s view that it needed to assert the doctrine, but they do argue that they cannot be penalized because of that. Upwards of $4 billion — the companies’ claims and the Pentagon’s claims, combined — rides on the outcome.
Two huge contractors, General Dynamics Corp. and Boeing Co., raised a number of issues in tasking the case to the Supreme Court, involving some key questions about the law governing federal contracting. But the Court granted review only of the “state secrets” issue, so that is where the case will remain focused.
The case’s origins go back to January 1988, when General Dynamics and McDonnell Douglas Corp. (since merged into Boeing) were awarded a fixed-price contract to design and built a Navy aircraft to be called the “A-12 Avenger.” That was to be an aircraft carrier-based version of the Air Force’s land-based “stealth” fighter plane. The word “stealth” here means an aircraft capable of flying below an enemy’s radar detection system. The Pentagon said the work could rise to a ceiling price of $4,777.330,294, which supposedly would cover the design, building and testing of eight prototypes of an A-12, each of which, as produced, would be more complex than the one before.
Because it was to be based on an aircraft carrier, there were significant limitations on how much the craft could weigh. There were other major challenges in designing the A-12 as the two companies worked on it, and they started falling behind on”milestone” dates by which certain tasks were to be completed, including delivery of the first prototype; the first was due in June 1990.
The companies began pleading with the Navy to renegotiate the contract from a fixed-price agreement to one that would cover the companies’ costs. They insisted they could not do the job for the agreed ceiling price. As controversy built between the companies and the Navy’s contracting officer on the job, the whole project was increasingly jeopardized. The companies would later contend that the project had lost political support in the upper echelons of the Pentagon, so officials there wanted out. The Cold War was over, and the Pentagon was recalculating its priorities; the A-12 would be a casualty of that.
Ultimately, in January 1991, the Navy terminated the contract. It claimed the companies had defaulted on the contract for failure to make mandated progress, including failing to meet “milestone” dates. The companies had complained, as they would later put it, that they had been “forced to reinvent the wheel” and that the task proved impossible, as a practical matter. They might be able to do it, they had said along the way, if the Air Force would share with them the technology it had developed in the creation of the land-based “stealth” fighter. The Air Force refused — contrary, the companies claimed, to an earlier promise to share that technology.
As the controversy has built since then, it is central to the legal issues that the Navy chose to end the contract by claiming default. For military contractors, that is the harshest outcome: the contractor is denied any payment for costs that had not yet been reimbursed, may be required to return to the government at least some of the money already paid them, and is thereafter at risk of being barred from getting future contracts, or at least treated less favorably than other bidders.
By contrast, if the Navy had cut off the A-12 contract “for convenience,” instead of for default, the Navy would have had to reimburse the contractor for some of the costs and the government is insulated from any claim that it breached the contract; it can simply walk away from the deal.
The companies have argued that they were spending up to $150 million a month of their own money as they worked to develop the A-12. They have said they were told that the government would not reimburse any of that, totaling more than $1.2 billion. In addition, the government has demanded the return of $1.35 billion in progress payments it had made, and seeks interest on that sum, with total interest now rising above $1.5 billion.
Under the federal Contract Disputes Act, companies doing business with the federal government may challenge a default termination in the Curt of Federal Claims, forcing the government to justify its termination for that reason. If the government fails to prove the point, the contract is not revived, but is terminated “for convenience,” with the clearly different outcome.
Initially, the Claims Court ruled for the A-12 contractors, finding no default; the contract ended when high-level officials abandoned it, the Court concluded. It ordered the Pentagon to reimburse some $1.2 billion in the contractors’ outlays. That was overturned by the Federal Circuit Court, with orders for a new trial to determine whether the default termination was actually justified. (The Supreme Court in 2000 refused to hear an appeal on that point.)
At the second trial, the Claims Court upheld the default conclusion. The companies had tried to defend themselves in that proceeding by arguing that they were hampered in developing the A-12 by the Air Force’s refusal to share its “stealth” technology. That was “superior knowledge” that should have been shared, and denial of access to it was solely to blame for any delays, the contractors contended. They sought to use the discovery process for that trial to get access to the technology. The Pentagon, however, invoked the “state secrets” doctrine, saying there was a risk that disclosing that information to the contractors would expose military secrets. The Claims Court thus refused to consider the “superior knowledge” argument by the contractors.
That ruling was upheld on a second trip to the Federal Circuit Court, which upheld the denial of “superior knowledge” defense, but for the second time ordered a new trial on the default issue. Once again, at the new trial, the default finding was upheld, and the Federal Circuit, in its third decision in the case, agreed with that result. Afterward, the Pentagon sent its bill to the companies, seeking reimbursement plus interest for the progress payments.
General Dynamics and Boeing (as successor to McDonnell Douglas) filed separate petitions for review in the Supreme Court.
Petitions for Certiorari
Last April 23, the contractors asked the Supreme Court to take on the case, each contending that the Federal Circuit had changed the law of contracting in the midst of the dispute, and arguing that it was a violation of constitutional due process guaranteed by the Fifth Amendment for the government to make financial demands while at the same time invoking the “state secrets” privilege to deny a chance to mount a defense to such demands.
On the first point, they argued, as Boeing’s petition put it, that the Federal Circuit has “thrown previously settled law in a critical area of government contracts into complete disarray. If allowed to stand, the court’s rulings may well unjustly deprive contractors of billions of dollars.”
But, in laying out their grievances, both petitions also put heavy focus on the denial of due process that they saw in the Pentagon’s use of the “state secrets” privilege. Boeing, for example, noted that the issue arises “at a time when the state secrets privilege is being asserted with growing frequency, and the need for clarity and uniformity on its scope and impact could not be more compelling.” To buttress this point, the petition cited to a series of lower court rulings arising out of the “war on terrorism,” but added that the issue was presented in a case that is “less politically charged.”
General Dynamics’ petition argued that the Federal Circuit had “disregarded the clear teachings of this Court’s state-secrets jurisprudence, basic principles of due process, and numerous contrary rulings from other circuits.”
The contractors noted that the Supreme Court, in its last ruling on the “state secrets” doctrine in Reynolds in 1953, had declared that it would be “unconscionable” for the government to ” ‘prosecute[ ] an accused’ while at the same time using the privilege to ‘deprive the accused’ of a defense.” The Court also had said then, it added, that, where the government is “the moving party,…a court will not permit the government to ensure its own victory — and its opponent’s punishment – through the government’s exercise of the virtually unreviewable discretion to identif yand protect state secrets. Thus, the government must choose between invoking the privilege and pursuing its claim.”
While General Dynamics conceded that it and Boeing were the suing parties in the case, the government on its side is asserting a claim — the validity of the default termination of the A-12 contract — and the companies clearly face a penalty — the payment or loss of “enormous sums” — if the government prevails. “The contractors’ claim here is in every meaningful sense an effort to oppose a claim by the government,” that petition added.
Supporting the petitions, the National Defense Industrial Association, a contractors’ trade group, arguing that the Federal Circuit ruling threatens such companies “to the sever consequences of default termination, based not on contract performance but on waning political or economic support.” The U.S. Chamber of Commerce also joined in supporting the contractors, focusing on the holding on the “state secrets” issue. This case, the Chamber argued, would not call that doctrine into question, but would only determine “what litigation consequences follow from the government’s invocation of the privilege.”
The Justice Department, in replying last August, urged the Court not to hear either of the petitions. The contractors’ complaints about the Federal Circuit’s ruling on the contract law issues, Acting U.S. Solicitor General Neal Katyal argued, involved only “fact-bound” issues keyed to well-established principles of default termination of government. “After nearly two decades of litigation,” Katyal argued, the case should end, especially since there are no lower court conflicts on those issues.
On the challenge to the consequences of the “state secrets” invocation, the government contended that the Reynolds decision’s comments about “unconscionable” denial of a defense as a result of that privilege applied only to criminal prosecutions. The contractors’ lawsuit over the A-12 contract, the brief argued, “cannot properly be analogized to a criminal prosecution brought by the United States.” It was they who sued, not the government, it noted. And they are suing in a civil, not a criminal forum, and their liberty is not at stake, Katyal said.
The contractors’ reliance on Supreme Court precedents protecting the right of a civil case defendant to use every available legal defense was misplaced, the government brief said. None of those decisions, it added, involve the use of evidentiary privileges, or, specifically, the “state secrets” privilege. Moreover, Katyal contended, the contractors had a full opportunity, in each of their trials in the Claims Court and before the Federal Circuit, to challenge the government’s proof on which default termination was based.
The Court, in its first grants of the new Term, on Sept. 28 agreed to hear both petitions, but limited its review to the “state secrets” issue — Question 1 in General Dynamics’ petition, Question 2 in Boeing’s. The cases were consolidated for argument.
With the case now focused, by the Court’s limited grant, on the “state secrets” issue, the General Dynamics brief on the merits went to considerable lengths to try to show that government officials and their lawyers in the Claims Court had sought to manipulate the issue of defense secrets to the government’s litigation advantage, and that the Claims Court judge had warned the federal lawyers about such tactics.
The aim of this discussion, of course, was to show that the “state secrets” doctrine — whatever its merits as a way to shield legitimate defense secrets — is also potentially subject to abuse in the courthouse combat over a lawsuit. Page after page of the General Dynamics argument sought to show how the contractors’ primary defense — that the contract performance problems were entirely due to denial of access to “stealth” technology — eroded as the government repeatedly invoked its evidentiary privilege to shape the case its way.
The Boeing brief was much more focused on the legal issues surrounding the invocation of the privilege in the contracting context, and cautioning the Court against allowing the federal judiciary itself to “become an instrument of an injustice” by ruling in favor of the government where, had a lawsuit been fully and fairly tried, a government victory was not warranted. Boeing’s brief also sought to refute the government’s petition-stage arguments that this case was different, because it was a civil, not a criminal, proceeding. The string of lower court cases involving the “state secrets” doctrine in war-on-terrorism disputes, Boeing noted, are themselves civil cases.
Both briefs sought to leave the Court with no doubt that the Constitution’s guarantee of fair procedures must lead courts to put an end, entirely, to a lawsuit where one side’s litigating opportunity has been stifled by the other’s use of a privilege claim. They asked the Court to reinstate the Claims Court’s original ruling that the termination for default should be turned into a termination “for convenience,” to give them recovery of their costs and the denial of the government’s claims for reimbursement.
The Justice Department’s brief on the merits focused primarily upon the argument that, in a Contract Disputes Act case where a contractor is suing the government, the government is not the “moving party” so the Reynolds decision’s discussion of the remedy for shutting down a case by invoking “state secrets” should not apply. But, even if the government in such a case is treated as the “moving party,” the federal brief contended, the remedy for a “state secrets” invocation that limits a contractor’s legal defense should not result in an automatic win for the contractor, but should depend upon whether the government has proved its side of the case on the merits — as the Department insisted its lawyers had done here.
Describing the federal government as a victim, if the courts grant automatic relief to a contractor who has not proved its case but claims to have been thwarted by the “state secrets” doctrine, the Department’s merits brief suggested that Supreme Court validation of the contractors’ claim here would lead other contractors to abuse the “superior knowledge” defense in order to provoke the government into invoking its privilege, thereby giving the contractors the win.
The Department brief also sought to dissuade the Court from accepting the contractors’ claims that federal lawyers had unfairly manipulated the “state secrets” doctrine by the way they used it in the trial here. The Federal Circuit addressed that contention, and rejected it, the brief said.
Moreover, the government brief sought to counter the contractors’ claims that the ultimate cost to them if they lose could be upwards of $5 billion. The Department said that the contractors have been allowed to keep more than $1.3 billion in progress payments for work that they had already completed, even though they never delivered even one A-12 prototype aircraft. The $1.2 billion in progress payments it is demanding be reimbursed, the brief said, is for work the contractors did not complete.
If the Court, in the end, opted to overturn the Federal Circuit’s ruling that this contract was defaulted, the Department asserted, the Court should not reinstate the finding of “termination for convenience,” but should send the case back to lower courts to consider other defenses tp the challenge by the contractors that the Pentagon still can raise.
In reply briefs, the contractors said the government’s legal arguments amounted to a “government always wins” approach whenever it invokes the “state secrets” privilege.
Once again, the National Defense Industrial Association and the U.S. Chamber of Commerce join as amici supporting General Dynamics and Boeing. Also joining in the case on their side are the Constitution Project, urging the Court to clarify the”state secrets” doctrine and to narrow its scope, arguing that the potential for its abuse is considerably heightened today
Groups that have had their cases in lower courts frustrated by the “state secrets” doctrine also have joined in the case as amici in support of limits on the doctrine. Those groups, noting that the Justice Department in opposing review of these cases had implied that the Court should put the “state secrets” doctrine on a constitutional foundation, to support Executive Branch authority, argued that the Court should do no such thing without full briefing and argument on that question. The doctrine, as of now, is simply an evidentiary privilege, not a constitutional prerogative of the Executive, those groups assserted.
The Court’s review of the scope of the “state secrets” doctrine has been so sparing in modern times that any case raising that issue has the potential, if the Court grants review, to become more important than its own particular confines. The A-12 contract case does not require the Court explicitly to outline the limits of the privilege, although the Court may at least have to ponder that as it weighs the consequences that it will permit to flow from its invocation.
The point is very subtly made, both in the Justice Department’s opposition to review and in its merits brief, that the privilege is intimately linked to the President’s Article II powers, but — as one of the amicus briefs pointed out — that may be a way to introduce into this case the question of whether the privilege is constitutionally based. That is not necessary, but it does indicate how “state secrets” cases can take on unusual significance for the Court.
As the case has been briefed, however, the Court may well be content to confine its review closely to the issue of whether the Reynolds precedent applies at all when the government has been sued — rather than when it is suing — in government contracts lawsuits. The Justice Department’s submission in the case have placed very heavy stress on the “moving party” issue, as a way to keep the Court from checking the government’s authority to invoke the “state secrets” privilege.
Whether the Court is fully willing to accept the government’s assurances that federal officials will not abuse or manipulate the privilege may depend on how the Justices react to the specific evidence, stressed mainly by General Dynamics, showing that the Claims Court judge was troubled by the litigating strategy of federal lawyers and the secrets they were seeking to shield.
If this is a Court that, as some critics suggest, is business-oriented, it may well read the recitation of that evidence as an indication that the privilege needs to be placed under some new restrictions. That could point toward a reversal of the default determination by the Federal Circuit, but not necessarily lead to the Justices themselves dictating the remedy. A reversal seems more likely to lead to a return of the case to the lower court, to analyze more carefully the claim that the privilege has been abused in this specific case.
Recommended Citation: Lyle Denniston, Argument preview: A look at “state secrets”, SCOTUSblog (Jan. 14, 2011, 2:52 PM), http://www.scotusblog.com/2011/01/argument-preview-a-look-at-state-secrets/