Ryan v. Defense

CourtCourt of Appeals for the Federal Circuit
DecidedFebruary 13, 2019
Docket18-1524
StatusUnpublished

This text of Ryan v. Defense (Ryan v. Defense) is published on Counsel Stack Legal Research, covering Court of Appeals for the Federal Circuit primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Ryan v. Defense, (Fed. Cir. 2019).

Opinion

NOTE: This disposition is nonprecedential.

United States Court of Appeals for the Federal Circuit ______________________

JAMES THOMAS RYAN, Petitioner

v.

DEPARTMENT OF DEFENSE, Respondent ______________________

2018-1524 ______________________

Petition for review of the Merit Systems Protection Board in No. DC-0752-17-0673-I-1. ______________________

Decided: February 13, 2019 ______________________

JOHN SILVERFIELD, Garden City, NY, for petitioner.

P. DAVIS OLIVER, Commercial Litigation Branch, Civil Division, United States Department of Justice, Washing- ton, DC, for respondent. Also represented by ELIZABETH MARIE HOSFORD, ROBERT EDWARD KIRSCHMAN, JR., JOSEPH H. HUNT; ELIZABETH PAVLICK, Office of General Counsel, Washington Headquarters Services & Pentagon Force Pro- tection Agency, United States Department of Defense, Washington, DC. ______________________ 2 RYAN v. DEFENSE

Before LOURIE, BRYSON, and MOORE, Circuit Judges. PER CURIAM. James Ryan appeals from a decision of the Merit Sys- tems Protection Board (“the Board”) sustaining three charges against Ryan for lack of candor, conduct unbecom- ing a police officer, and unauthorized use of a computer, and removing him from service as a police officer in the Pentagon Force Protection Agency (“PFPA”). See Ryan v. Dep’t of Def., No. DC-0752-17-0673-I-1 (M.S.P.B. Nov. 15, 2017). Ryan disputes whether substantial evidence sup- ports each of the conclusions of the Board’s Administrative Judge (“AJ”) with respect to these charges, and he further argues that the AJ failed to find a nexus between the ad- verse action and his service and that the AJ’s action vio- lated his rights under the Due Process Clause and the Whistleblower Protection Act (“WPA”). Because we con- clude that substantial evidence supports the AJ’s findings and that Ryan’s other arguments lack merit, we affirm. I. BACKGROUND Ryan was employed as a police officer with the PFPA from February 2009 until his removal on June 6, 2017. In 2015, Ryan filed a complaint with the Equal Employment Opportunity Commission (“EEOC”), concerning his em- ployment with the PFPA, which is not at issue in this ap- peal. In the course of that proceeding, Ryan was required to sign a Notice of Rights and Responsibilities for the EEOC complaint process. By signing the notice, Ryan was given access to a Report of Investigation (“ROI”) from the EEOC, which contained the personnel file of another police officer (“SV”). The ROI included the following warning:

v. The ROI contains personal data and is to be treated in a confidential manner. You may not show your copy of the ROI, in whole or in part, to a third party except your designated representative. Violations of privacy safeguards RYAN v. DEFENSE 3

may result in disciplinary action, a fine of up to $5,000, or both (Public Law 93-576 1). J.A. 148. Ryan did not heed this warning. Instead, he sent a copy of SV’s personnel file to eight members of the PFPA, as well as the PFPA Office of Professional Responsibility, as an attachment to an October 12, 2016, memorandum in which he asserted that SV received a fraudulent cash bo- nus of $2,050 from a sergeant “in exchange for allowing [SV’s duty post] to become a location for unauthorized con- gregating, food delivery, and eating to take place.” J.A. 417. Ryan had previously reported SV and others on sepa- rate occasions for such unauthorized congregating around SV’s duty post. In the memorandum, Ryan denigrated SV’s perfor- mance based on Ryan’s own observations, SV’s personnel file, and records of SV’s incident reports stored in the PFPA’s Record Management System (“RMS”), which Ryan had accessed. However, Ryan never provided any evidence of this purported quid pro quo beyond his complaints about SV’s performance and allegedly undeserved bonus and pos- itive evaluation from the sergeant. 2 In response, the PFPA issued a notice of proposed re- moval to Ryan on February 7, 2017. The PFPA asserted that the removal was justified because, among other charges, Ryan: (1) lacked candor by making an untrue and unsupported allegation about SV and the sergeant; (2)

1 The ROI’s citation of the Privacy Act of 1974 con- tains a minor error and should have read “Public Law 93- 579.” See Privacy Act of 1974, Pub. L. No. 93-579, 5 U.S.C.A. § 552a (West through Pub. L. No. 115-281). 2 Importantly, Ryan admitted he never reviewed SV’s Officer Performance Rating, which was the basis for SV’s performance rating and bonus. 4 RYAN v. DEFENSE

violated the law and departmental policy by distributing SV’s personnel file, which is conduct unbecoming a police officer; and (3) misused a government computer by access- ing SV’s police reports in the RMS system without author- ization. The deciding official (“DO”) sustained the charges at issue in this appeal and removed Ryan from service on June 6, 2017. Ryan then appealed to the Board. The AJ credited the DO’s testimony and therefore sustained the charges and Ryan’s removal. The AJ also rejected Ryan’s affirmative defense under the WPA. While Ryan did not present an argument that his removal violated his due process rights, the AJ credited certain statements at the hearing as rais- ing the issue. Specifically, Ryan alleged at the hearing that the DO’s personal knowledge that another of Ryan’s accu- sations—that two other PFPA officers abuse alcohol while off-duty—was baseless constituted ex parte information to which Ryan must be given notice. See Stone v. FDIC, 179 F.3d 1368, 1376–77 (Fed. Cir. 1999) (holding that a DO’s consideration of an ex parte communication may violate an employee’s right to due process where it introduces new and material evidence). The AJ rejected Ryan’s due pro- cess argument because the specification directly concern- ing this accusation was withdrawn by the PFPA and, with respect to the sustained charges, the ex parte information was both immaterial and cumulative to the remainder of the record. The AJ’s decision became the decision of the Board be- cause Ryan did not appeal to the full Board, which at that time lacked a quorum. This appeal followed. We have ju- risdiction under 28 U.S.C. § 1295(a)(9). II. DISCUSSION The scope of our review of an appeal from a decision of the Board is limited. We must affirm the Board’s decision unless we find it to be “(1) arbitrary, capricious, an abuse of discretion, or otherwise not in accordance with law; RYAN v. DEFENSE 5

(2) obtained without procedures required by law, rule, or regulation having been followed; or (3) unsupported by sub- stantial evidence.” 5 U.S.C. § 7703(c). A finding is sup- ported by substantial evidence if a reasonable mind might accept the evidence as adequate to support the finding. Consol. Edison Co. v. NLRB, 305 U.S. 197, 229 (1938). Credibility determinations are within the discretion of the Board and are “virtually unreviewable” on appeal. King v. HHS, 133 F.3d 1450, 1453 (Fed. Cir. 1998). The burden of establishing reversible error in a Board decision rests upon the petitioner. See Harris v. Dep’t of Veterans Affairs, 142 F.3d 1463, 1467 (Fed. Cir. 1998). We address Ryan’s challenges to the sufficiency of the evidence, his due process challenge, and his affirmative de- fense under the WPA in turn. A.

Free access — add to your briefcase to read the full text and ask questions with AI

Related

Cite This Page — Counsel Stack

Bluebook (online)
Ryan v. Defense, Counsel Stack Legal Research, https://law.counselstack.com/opinion/ryan-v-defense-cafc-2019.