Gemmell v. Fairchild Space & Defense Corp.

813 F. Supp. 1152, 1993 U.S. Dist. LEXIS 2742, 61 Fair Empl. Prac. Cas. (BNA) 390, 1993 WL 50920
CourtDistrict Court, D. Maryland
DecidedFebruary 10, 1993
DocketCiv. JFM-92-1520
StatusPublished
Cited by3 cases

This text of 813 F. Supp. 1152 (Gemmell v. Fairchild Space & Defense Corp.) is published on Counsel Stack Legal Research, covering District Court, D. Maryland primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Gemmell v. Fairchild Space & Defense Corp., 813 F. Supp. 1152, 1993 U.S. Dist. LEXIS 2742, 61 Fair Empl. Prac. Cas. (BNA) 390, 1993 WL 50920 (D. Md. 1993).

Opinion

MEMORANDUM

MOTZ, District Judge.

Robert A. Gemmell has brought this action against Fairchild Space & Defense Corporation (“Fairchild”) under the Age Discrimination In Employment Act of 1967, 29 U.S.C. Section 621 et seq. (1988). Discovery has been completed, and defendant has moved for summary judgment.

I.

A. The Events Up To November, 1989

Fairchild hired plaintiff in August 1982 as its manager of test operations. In that *1153 capacity he was responsible for “test resources” (designing manufacturing and production tests) and “production tests” (actual testing of products on the manufacturing floor). Five months after he began work, plaintiff was relieved of his responsibility over production tests and during the next three years he supervised only the test resources function. In 1986 the production test group was again assigned to plaintiff, and he was promoted to the position of Director, Testing Resources/Production Test.

On October 12, 1987, Fairchild hired Richard Bair as vice president in charge in operations. Bair promptly reorganized the department and promoted plaintiff, who was then age 56, into the newly-created

position of director of operations engineering. In that position plaintiffs responsibilities were extended to two additional functions: manufacturing engineering (which established procedures for manufacturing) and industrial engineering (which established the manufacturing plant layout).

In May 1988 Bair formally evaluated plaintiff's performance in his new position. Bair gave plaintiff an overall rating of 3.1 under a rating system where a 3.0 was “competent.” However, plaintiff was given a rating of only 2.7 (placing him in the “fair” range) as to his new responsibilities. 1 The evaluation included goals which plaintiff was expected to meet and Bair’s appraisal of his degree of success in meeting those goals:

MAJOR GOALS

* Assume additional responsibilities for Manufacturing Engineering department, and Industrial Engineering department to consolidate all of operation engineering under one Directorate.

* Develop an Industrial Engineering Department within the Directorate. Start with a Supervisor and four engineers in 1988.

* Job knowledge

* Leadership

BAIR’S ASSESSMENT

This task requires a major strength in technical leadership. In some ways we need to affect a cultural change in how we look at factory support.

The staff is in place, however, the impact of the group is in its infancy. Strong technical leadership is required and cost control is important.

[Plaintiff’s] test expertise is well known. He needs to become a recognized leader in the other disciplines of Operations Engineering.

[Plaintiff] needs to become recognized as the technical leader of Operations in all areas. Work is required.

Over the next months plaintiff failed to meet Bair’s expectations of him. It became increasingly apparent that at bottom there was a fundamental disagreement between the two of them about management style. Plaintiff believed in an essentially passive management approach whereby he would delegate substantial responsibilities to his subordinates and problems would filter up to him through a staged process. According to his deposition testimony, he “believed in using as little supervision as possible” while Bair believed in “using as much supervision as possible.” As plaintiff understood it, Bair believed in manag *1154 ers being “intimately involved in the technical problem solving at the employee level.” Therefore, Bair wanted him to be “the focal point for the major technical problem solving.” Plaintiff, however, thought “that was not possible” and would result in “a bottleneck.” In short, according to plaintiff, Bair expected him “to be the center of everything coming in” whereas plaintiff believed “that if you have good managers under you, that they should be given the reins to do their job and most of the stuff should definitely go through them.”

In December 1988 Bair met with plaintiff and told him of his “extreme displeasure with the way his [plaintiffs] organization was performing.” Bair defined the main problem as “management involvement and attitude” and he warned plaintiff that he “was considering moving [plaintiff] back to his previous assignment.” Plaintiff, however, continued to believe that his management style was correct. Therefore, rather than making any substantive changes to the way in which he approached his responsibilities, he merely increased the flow of information which he provided to Bair. When asked on deposition if he “did ... anything over the next 6 months after this December 1988 meeting, anything significantly different during the following 6 months in the way you approached your job,” he responded:

Well, basically I made sure that I went in more often to him and told him what was happening rather than have the other guys go in and keep him informed. So when he gave somebody an assignment, I made sure that I was aware of it and either I went in myself to tell him what was happening or I went in with the person so that I was more visual with this type of thing____ Like I said, I don’t recall major things. I just made sure that he was more aware of what I was doing. 2

In June 1989 Bair again formally evaluated plaintiff’s performance. He gave him an overall rating of 2.1. The evaluation included the following comments:

We are basically in a reactionary mode. J. German is pushing the program but it could use more of [Plaintiff’s attention], [Plaintiff’s] test expertise is well known but he has not put forth the needed effort to understand the other disciplines of Manufacturing Engineering.
Bob needs to become recognized as the technical leader of Operations in all areas. Work is needed.

Within a week of giving plaintiff his performance appraisal, Bair placed him on formal written probation. Bair’s letter to plaintiff stated as follows:

Your performance as Director of Operations Engineering during the past year has continued to decline and you have not met the expectations or requirements of the job. We had a very serious discussion in December 1988 in which I defined for you my areas of concern about your performance and improvements required. Since I have seen no substantial improvements in the areas defined, I feel that the use of a probationary period is necessary to affect the required improvement in your performance.
The purpose of this letter is to clearly identify my areas of concern, describe needed changes and define the ground rules for the probationary period.

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

Related

Cite This Page — Counsel Stack

Bluebook (online)
813 F. Supp. 1152, 1993 U.S. Dist. LEXIS 2742, 61 Fair Empl. Prac. Cas. (BNA) 390, 1993 WL 50920, Counsel Stack Legal Research, https://law.counselstack.com/opinion/gemmell-v-fairchild-space-defense-corp-mdd-1993.