A.R. v. Norris

Decision Date10 November 2015
Docket NumberNo. 3:15cv1780,3:15cv1780
PartiesA.R., Plaintiff v. JEFFREY NORRIS, JAMES TALLERICO, and MONTROSE AREA SCHOOL DISTRICT, Defendants
CourtU.S. District Court — Middle District of Pennsylvania

(Judge Munley)

MEMORANDUM

Plaintiff A.R. (hereinafter "plaintiff") asserts Title IX and constitutional tort claims arising from her former teacher, Defendant Jeffrey Norris, allegedly sexually abusing her while a student at Defendant Montrose Area School District (hereinafter "Montrose"), where Defendant James Tallerico served as principal. Before the court for disposition is plaintiff's motion to remand this case to the Court of Common Pleas of Lackawanna County, Pennsylvania. For the reasons that follow, the court will grant plaintiff's motion.

Background

According to plaintiff's complaint, the facts are as follows: In the fall of 2006, plaintiff, then fourteen (14) years old, began her freshman year at Montrose Area High School. (Doc. 1-1, Compl. ¶ 6). Defendant Norris, plaintiff's English teacher, flirted with plaintiff and expressed his desire to begin a sexual relationship. (Id. ¶¶ 10-19). Defendant Norris continued flirting with plaintiff and, in the spring of 2007, engaged in the statutory rape of a minor by having sexual intercourse with plaintiff on two separate occasions. (Id. ¶¶ 19, 27).

Prior to Defendant Norris's statutory sexual assault, plaintiff asserts high school officials, including Defendant Tallerico, knew of the romantic relationship. (Id. ¶¶ 41-55). These school officials, however, summarily dismissed the allegations. (Id. ¶ 75). Moreover, the school officials failed to develop a comprehensive safety plan to protect plaintiff's well-being. (Id. ¶ 55). Rather, the school officials continued to employ Mr. Norris and allowed him to continue teaching students, including plaintiff. (Id. ¶ 56).

Based on these factual allegations, plaintiff filed a four-count complaint pursuant to Title IX of the Education Amendments of 1972, 20 U.S.C. § 1681 et seq., and 42 U.S.C. § 1983 on July 23, 2015 in the Court of Common Pleas of Lackawanna County, Pennsylvania. (Doc. 1-1). On September 11, 2015, Defendant Montrose filed a notice of removal. (Doc. 1). Plaintiff filed a motion to remand on October 1, 2015. (Doc. 9). The parties briefed their respective positions and the matter is ripe for disposition.

Legal Standard

Federal law provides that defendants may remove a civil action filed in a state court if the federal court would have had original jurisdiction over the action. 28 U.S.C. § 1441(a). The removing defendants bear the burden of proving the existence of federal jurisdiction. In re Processed Egg Prods. Antitrust Litig., 836 F. Supp. 2d 290, 294 (E.D. Pa. 2011) (citing Dukes v. U.S. Healthcare, Inc., 57 F.3d 350, 359 (3d Cir. 1995)). Defendants must also establish that all pertinent procedural requirements for removal have been met. Shadie v. Aventis Pasteur, Inc., 254 F. Supp. 2d 509, 514 (M.D. Pa. 2003) (citing Boyer v. Snap-On Tools Corp., 913 F.2d 108, 111 (3d Cir. 1990)). "Because lack of jurisdiction would make any decree in the case void and the continuation of the litigation in federal court futile, the removal statute should be strictly construed and all doubts resolved in favor of remand." Abels v. State Farm Fire & Cas. Co., 770 F.2d 26, 29 (3d Cir. 1985) (citations omitted).

Discussion

To remove a case from state to federal court, a defendant must simply file a notice of removal with the federal district court for the district and division in which the state court action is pending. 28 U.S.C.§ 1446(a). A defendant's notice of removal must "be filed within 30 days after the receipt by the defendant, through service or otherwise, of a copy of the initial pleading setting forth the claim for relief upon which such action or proceeding is based." 28 U.S.C. § 1446(b)(1).

In cases involving multiple defendants, "all defendants who have been properly joined and served must join in or consent to the removal of the action." 28 U.S.C. § 1446(b)(2)(A). The Third Circuit Court of Appeals has held that the failure of all defendants to join in removal is a defect in removal procedure, but not a jurisdictional defect. Balazik v. Cty. of Dauphin, 44 F.3d 209, 213 (3d Cir. 1995). As such, a plaintiff seeking to remand pursuant to a procedural defect must file a motion to remand under 28 U.S.C. §§ 1447(c) and 1446(a). Id.

The decision to enter a remand order on the basis of a defect in removal procedure or for a lack of subject matter jurisdiction is within the discretion of the district court, and, whether erroneous or not, is not subject to appeal. Cook, 320 F.3d at 437 (citing Quackenbush, 517 U.S. at 711-12). The United States Supreme Court has noted that limiting review of remand orders supports "Congress's longstanding policy of not permitting interruption of the litigation of the merits of a removed case."Powerex Corp. v. Reliant Energy Svcs., Inc., 551 U.S. 224, 238 (2007).

In the instant matter, plaintiff filed a timely motion to remand under 28 U.S.C. § 1447(c), alleging a procedural defect in Defendant Montrose's notice of removal. Specifically, plaintiff argues each codefendant did not join in the notice of removal or submit with the court their written consent to removal.

Defendant Montrose counters that its notice of removal is proper because Montrose's attorney, in the notice of removal, represented that all properly served codefendants consented to removal. Alternatively, Defendant Montrose argues that remand is unwarranted because, subsequent to removal, Montrose filed with the court email exchanges it had with Defendants Norris and Tallerico, which illustrate Defendants Norris and Tallerico's consent to removal. Therefore, the court must address the form that a codefendant's consent must take and when this consent must be filed with the court.

A. Codefendant's form of consent

The parties dispute what form a codefendant's consent to removal must take. Plaintiff contends that a removing defendant's notice of removal may not verify a codefendant's consent to removal. Rather, eachcodefendant must join in the notice of removal or submit with the court written consent to removal. Defendant Montrose argues removal is proper because, in the notice of removal, Montrose's attorney represented that all properly served codefendants consented to removal. The Third Circuit Court of Appeals has not specifically addressed the issue of what form a codefendant's consent must take. A review of cases from the circuits that have addressed this issue persuades us that a notice of removal is procedurally deficient, and therefore improper, if it merely represents that all properly served codefendants consent to removal.

The Supreme Court has held that removal based on a federal question requires the unanimous consent of all defendants. See Chi., Rock Island, & Pac. Ry. Co. v. Martin, 178 U.S. 245, 248 (1900). The removal statute itself, however, does not speak directly to the issue of what form a codefendant's consent must take, stating only, "A defendant or defendants desiring to remove any civil action from State court shall file . . . a notice of removal signed pursuant to Rule 11 of the Federal Rules of Civil Procedure." 28 U.S.C. § 1446(a). Neither the Supreme Court, Congress, nor the Third Circuit Court of Appeals has clarified what form a codefendant's consent must take, and the circuits are split on this issue.

The Second, Fifth and Seventh Circuits, have found that a defendant may not verify consent to removal on another codefendant's behalf. Pietrangelo v. Alvas Corp., 686 F.3d 62, 66 (2d Cir. 2012) (finding that codefendants satisfied the unanimity requirement of independently expressing consent to removal by submitting letters to the district court within 30-day removal period); Roe v. O'Donohue, 38 F.3d 298, 301 (7th Cir. 1994), abrogated on other grounds by Murphy Bros. v. Michetti Pipe Stringing, Inc., 526 U.S. 344 (1999) (explaining that the removal statute's directive that "all defendants who have been properly joined and served must join in or consent to the removal of the action" means that each codefendant must submit their consent in writing); Getty Oil Corp. v. Ins. Co. of N. Am., 841 F.2d 1254, 1262 n.11 (5th Cir. 1988) (noting unanimity requires "some timely filed written indication from each served defendant or from some person or entity purporting to formally act on its behalf in this respect and to have the authority to do so, that it has actually consented to such action").1 Under this view, it is not enough for the removing partyto simply state that the codefendants consent to or do not oppose removal because this verification cannot legally bind the allegedly consenting codefendant. Roe, 38 F.3d 298 at 301; Getty Oil, 841 F.2d at 1262 n.11.

The Fourth, Sixth, Eighth and Ninth Circuits, on the other hand, have held that a statement in one defendant's timely notice of removal that its codefendants consent to removal is sufficient. Griffioen v. Cedar Rapids & Iowa City Ry. Co., 785 F.3d 1182, 1188 (8th Cir. 2015) (notice of removal signed and filed by attorney for one defendant and representing unambiguously that other defendants consented to removal satisfies the removal statute's unanimous consent requirement); Mayo v. Bd. of Educ., 713 F.3d 735, 742 (4th Cir. 2013) (same); Proctor v. Vishay Intertechnology Inc., 584 F.3d 1208, 1225 (9th Cir. 2009) (same); Harper v. AutoAlliance Int'l, Inc., 392 F.3d 195, 201-02 (6th Cir. 2004) (same). The Fourth, Sixth, Eighth and Ninth Circuits believe the potential for Rule 11 sanctions and a codefendant's opportunity to "alert the court to any falsities in the removing defendant's notice serve as safeguards to prevent removing defendants from making false representations of unanimousconsent and forcing codefendants into a federal forum against their will." Griffioen, 785 F.3d at 1187-88; see also Mayo, 713 F.3d at 724 (explaining that codefendants...

To continue reading

Request your trial

VLEX uses login cookies to provide you with a better browsing experience. If you click on 'Accept' or continue browsing this site we consider that you accept our cookie policy. ACCEPT