Patrick G. Hollingsworth v. Department of the Air Force

2014 MSPB 56
Merit Systems Protection Board·Decided July 23, 2014·Published·Cited by 1 cases

Opinion

UNITED STATES OF AMERICA MERIT SYSTEMS PROTECTION BOARD 2014 MSPB 56

Docket No. SF-0752-14-0199-I-1

Patrick G. Hollingsworth, Appellant, v. Department of the Air Force, Agency. July 23, 2014

Patrick G. Hollingsworth, North Las Vegas, Nevada, pro se.

Basil R. Legg, Joint Base Andrews, Maryland, for the agency.

BEFORE

Susan Tsui Grundmann, Chairman Anne M. Wagner, Vice Chairman Mark A. Robbins, Member

OPINION AND ORDER

¶1 The appellant has filed a petition for review of the initial decision that affirmed his removal for tardiness. Because the agency failed to prove that the appellant was tardy, we REVERSE the initial decision. The removal is NOT SUSTAINED.

BACKGROUND ¶2 The appellant was a GS-05 Secretary (Office Automation) for the agency. Initial Appeal File (IAF), Tab 1 at 2, Tab 4 at 11. Effective November 22, 2013, the agency removed him on a charge of tardiness based on a total of 7 hours and 2

30 minutes of absence without leave (AWOL) incurred during four separate instances between September 6 and October 7, 2013. IAF, Tab 4 at 11-13, 24-25. In arriving at the removal penalty, the deciding official considered, among other things, the appellant’s substantial history of progressive discipline for attendance-related problems. Id. at 12, 15, 26. ¶3 The appellant filed a Board appeal and waived his right to a hearing. 1 IAF, Tab 1 at 3-4. The administrative judge affirmed the removal on the written record. IAF, Tab 10, Initial Decision (ID) at 1, 14. He found that the appellant was scheduled to report for duty at 8:30 a.m., but he reported 1 hour late on September 9, 2013, 2 hours late on September 13, 2013, and 2 hours late on October 7, 2013. ID at 4-5; IAF, Tab 9 at 22-23. The administrative judge also found that the appellant would have had to report at 8:00 a.m. on September 6, 2013, in order to meet his 80-hour requirement for the pay period, and that the appellant reported 30 minutes late on that date. ID at 4; IAF, Tab 9 at 22. The administrative judge therefore sustained the charge. 2 ID at 5.

ANALYSIS ¶4 An agency is not required to affix a label to a charge but may simply describe actions that constitute misbehavior in narrative form in its charge letter; however, if the agency chooses to label an act of alleged misconduct, then it must

1 In addition to his removal, it appears that the appellant attempted to challenge his prior 1-, 5-, and 14-day suspensions. IAF, Tab 1 at 4, Tab 4 at 35-36, 42-43, 49-50. None of these actions is directly appealable to the Board because the Board’s chapter 75 jurisdiction extends only to suspensions of more than 14 days. 5 U.S.C. § 7512(2); Stewart v. Department of Defense, 82 M.S.P.R. 649, ¶ 15 (1999). 2 Although the administrative judge found that the appellant was tardy for a total of 5 hours and 30 minutes rather than the 7 hours and 30 minutes that the agency specified in its charge, he did not find this discrepancy to be material. ID at 5; IAF, Tab 4 at 24; cf. Senior v. U.S. Postal Service, 85 M.S.P.R. 283, 289 (2000) (the Board may sustain a charge of AWOL even when the agency fails to prove that the appellant was AWOL for the entire period). 3

prove the elements that make up the legal definition of the charge, if any. Otero v. U.S. Postal Service, 73 M.S.P.R. 198, 202 (1997). In this case, the agency charged the appellant with “tardiness.” IAF, Tab 4 at 24. The Board has not established the elements for a charge of tardiness. However, it is not a generic charge such as “improper conduct” or “conduct unbecoming” that does not require specific elements of proof. Cf. Canada v. Department of Homeland Security, 113 M.S.P.R. 509, ¶ 9 (2010) (a charge of “improper conduct” or “conduct unbecoming” has no specific elements of proof; it is established by proving that the employee committed the acts alleged in support of the broad label). A plain and ordinary understanding of the term “tardiness” implies unexcused lateness. Merriam–Webster’s Collegiate Dictionary 1202 (10th ed. 2002) (to be tardy is to be “delayed beyond the expected or proper time”). ¶5 In this case, the administrative judge implicitly analogized the charge of tardiness with a charge of AWOL. ID at 3. He found that to prove a charge of tardiness, the agency must show that: (1) the employee was scheduled for duty; (2) the employee was late for duty for the time charged; and (3) either the employee’s absence was not authorized or his request for leave was properly denied. ID at 3; cf. Boscoe v. Department of Agriculture, 54 M.S.P.R. 315, 325 (1992) (to prove an AWOL charge, an agency must show that the employee was absent from duty, and either that his absence was not authorized or that his request for leave was properly denied). Neither party challenges the administrative judge’s construction of the charge, and we agree that it is appropriate. It is consistent with the Federal Circuit’s construction of a “tardiness” charge in Bryant v. National Science Foundation, 105 F.3d 1414, 1416-17 (Fed. Cir. 1997), and the Board’s construction of the same in Mahnken v. U.S. Postal Service, 34 M.S.P.R. 1, 3-5, aff’d, 835 F.2d 871 (Fed. Cir. 1987) (Table). It is also consistent with the general principle that an agency cannot discipline an employee for approved absences. See Cook v. Department of the Army, 18 M.S.P.R. 610, 611-12 (1984); Watson v. U.S. Postal Service, 4

13 M.S.P.R. 56, 58 (1982). The appellant does not dispute his arrival times on the days in question or directly challenge the appropriateness of the removal penalty for the sustained charge. He disputes only whether the charge should be sustained at all—specifically, whether the arrival times constituted tardiness within the parameters of his flexible work schedule. ¶6 The administrative judge adjudicated this issue as an affirmative defense of harmful error or action taken not in accordance with the law, for which the appellant bears the burden. ID at 6-11; IAF, Tab 7 at 4-5; see 5 U.S.C. § 7701(c)(2)(A), (C); 5 U.S.C. § 1201.56(a)(2)(iii). However, we conclude that it is better construed as an argument that the agency failed to meet its burden of proving an element of its charge, i.e., that the appellant was scheduled to report for duty before the arrival times at issue. See 5 U.S.C. § 7701(c)(1)(B) (an agency bears the burden of supporting a chapter 75 adverse action by preponderant evidence); 5 C.F.R. § 1201.56(a)(1)(ii) (same). ¶7 As explained above, the only dispute in this case pertains to whether the appellant was required to be on duty during the periods for which the agency carried him in AWOL status. For the reasons explained below, we find that the agency failed to prove that he was. ¶8 The parties agree that the appellant was subject to a “Maxiflex” schedule. IAF, Tab 8 at 4, Tab 9 at 5, 21. The Department of Defense (DOD) defines such schedules as follows: Maxiflex. Maxiflex is a flexible work schedule that contains core hours on fewer than 10 work days in the biweekly pay period and in which an employee has a basic work requirement of 80 hours for the biweekly pay period. The employee may vary the number of hours worked on a given workday or the number of hours each week, within the limits established for the organization. 5

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

Patrick G. Hollingsworth v. Department of the Air Force, 2014 MSPB 56 (Miss. 2014).

2014 MSPB 56 (Patrick G. Hollingsworth v. Department of the Air Force) — published by Counsel Stack Legal Research, free access to 12M+ legal documents.

Related

Patrick G. Hollingsworth v. Department of the Air Force
2014 MSPB 56 (Merit Systems Protection Board, 2014)