Once Again, No Consequences for Prosecutorial Misconduct
by Jamison Koehler on September 14, 2012
On the morning of trial, the prosecutor finds out that the testimony provided by a police officer at the preliminary hearing was inaccurate. Although the prosecutor himself is not planning to call this particular police officer to testify at trial, he knows that the defense attorney is.
So what does prosecutor do? Does he immediately contact the defense attorney to set things straight? Or does the prosecutor decide to sit on the information, allowing the unwitting defense attorney to call the witness without knowing of the inconsistency?
This was the situation in a case recently considered by the D.C. Court of Appeals in Adrian Thompson v. United States, __ A.2d __ (D.C. 2012) and, in this case, the prosecutor decided to sit on the information. Although it is impossible to say what was going through the prosecutor’s mind, he may have belonged to that group of prosecutors who view criminal prosecutions as a contest – a zero-sum game in which any concession to the defense is a loss to the government.
While not exactly congratulating the prosecutor on his conduct, the Court concludes that his failure to alert the defense did not affect the outcome of the case: “Even if the government improperly delayed its disclosure, reversal is not warranted in this case because appellant was not substantially prejudiced.” It therefore affirmed the defendant’s conviction.
The opinion spends a lot of time discussing the government’s obligation to correct false testimony under the “Napue Doctrine.” Named after the U.S. Supreme Court case in which it was first spelled out, Napue v. Illinois, 360 U.S. 264, 269 (1959), the doctrine prevents the government from knowingly using false evidence, including false testimony, to obtain a conviction. The doctrine also requires the government to correct any false testimony when offered, even when such testimony was not solicited by the government. The Court describes all of this only to point out that, because it was not the government who called the officer and because the officer witness corrected the mistake once he was on the stand, the doctrine did not apply anyway.
The Court summarily dismisses a number of arguments advanced by the defense. Like the trial court, it is skeptical of the defense lawyer’s claim that she would not have called the witness had she been aware of the false testimony. The Court holds it against the defense that, once the discrepancy became apparent, she attempted to turn what could have been damaging testimony before the jury to her advantage. And Brady v. Maryland is mentioned in nothing more than a parenthetical.
Left unaddressed by the Court is the original prosecutor’s failure to correct the testimony at the preliminary hearing and the fact that the case was originally held for trial on the basis of false testimony. Also left unresolved – at least to my satisfaction — was the second prosecutor’s failure to alert the defense attorney as soon as he became aware of the falsity: “We have found no binding precedent, and [the defendant] points us to none, that holds that a prosecutor has a duty to notify defense counsel about prior false testimony before he corrects that testimony in front of the finder of fact.” Do we really believe that such ambush tactics are consistent with the Fifth Amendment’s Due Process Clause? And what about that legal maxim about not being able to benefit from mistakes of your own creation?
“This is not a case where false testimony went uncorrected,” the Court holds, even though the testimony was not corrected until the officer was already on the stand and testifying in front of the jury. Although such a “no harm, no foul” approach may settle matters in this case, it will do nothing to prevent such prosecutorial misconduct from happening in the future.