When MDL Judges Come To Visit

by Reed Smith
Contact

We wrote a post not too long ago recommending that MDL defendants seriously consider limiting so called “Lexecon (read the prior post if you don’t know what that means) waivers” to single plaintiff trials and to exclude punitive damages.  We included a caveat that “this idea wouldn’t have worked” in all situations, if the MDL judge is bound and determined to chase down a non-waiving defendant in the original transferor district.  See Eghnayem v. Boston Scientific Corp., 873 F.3d 1304 (11th Cir. 2017) (MDL judge trying out-of-district case as visiting judge).

We were assuming, of course, that the MDL court could engineer a temporary appointment as a visiting judge under 28 U.S.C. §292(d) – something we’d first brought up a long time ago.  Indeed, the Manual for Complex Litigation (4th) mentions this possibility.  See Id. §20.132, at 247 (Fed. Jud. Ctr. 2005).

We should have researched that assumption first, or at least gone back through our own old posts.  It turns out that the only appellate authority on MDL judges trying cases as visiting judges says you can’t do it.  See In re Motor Fuel Temperature Sales Practices Litigation, 711 F.3d 1050 (9th Cir. 2013) (“MFT”).  Not only that, we actually blogged about the MFT ruling when it was decided.  If we hadn’t been preparing an MDL best practices project for Duke Law School, our forgetful ignorance would have continued.

Anyway, we figure if we can forget something like that – although we actually wrote about it – you might, too.  So with the problem of multi-plaintiff consolidated punitive damages MDL show trials fresh in our minds, here’s a refresher:

MFT refused to approve a “temporary assignment” designation sought by an MDL judge to try a case that was otherwise precluded by Lexecon, even though Lexecon was not totally on point

Lexecon dealt with venue, not judicial case assignment.  The Lexecon Court held that a plaintiff is entitled to select the venue where the case will be tried, and this right can’t be undermined by having the case transferred for pre-trial proceedings under the MDL process.  Venue is important for a number of practical reasons, such as ease of access to the forum by plaintiffs and their lawyers and, perhaps most important, selection of the jury pool.  Venue does bear on which judge will be assigned to the case, as one of the judges of that district will normally preside, but there’s no guarantee of that.

711 F.3d at 1054.  Nonetheless there was “some force” to the argument “that allowing the MDL judge to follow the cases after the conclusion of pre-trial proceedings resuscitates the self-referral practice that the Supreme Court unanimously repudiated in Lexecon.”  Id.  Just not enough force to win the point on that basis, since Lexecon itself did not dictate the outcome.

Instead, MFT looked to the Guidelines for the Intercircuit Assignment of Article III Judges promulgated under the Chief Justice’s authority the year before.  These guidelines set out specific criteria for allowance of intercircuit transfers, and letting an MDL judge try cases s/he otherwise couldn’t wasn’t one of them.  Rather such transfers are permitted only under very specific circumstances.  “Only severe or unexpected over-burdening, as happens when a judge dies or retires, when the district is experiencing a judicial emergency or when all the judges are recused because of a conflict, will warrant bringing in a visiting judge.”  MFT, 711 F.3d at 1053.

While we would ordinarily include a link to the guidelines themselves, they’re not independently available either on the Internet or on the Federal Judicial Center’s website. Helpfully, they are attached as “Appendix A” to the MFT decision.  These guidelines do not provide any support for an MDL judge taking the initiative to ride shotgun on remanded cases:

  • The “primary source of intercircuit assignments should be senior judges.”
  • The first choice for designating a visiting judge is “from another court within the circuit.”
  • Assignments are not controlled by the would-be visiting judge, but rather selected by the chief justice and the Committee on Intercircuit Assignments, in order “to avoid the appearance of impropriety or conflict of interest.”
  • “The appropriate way to initiate a formal request for an intercircuit assignment is for the circuit chief judge to send a Certificate of Necessity to the Chair [of the Committee on Intercircuit Assignments].”

Thus MFT rejected the request of an MDL judge to retain authority over a remanded case:

[T]he process of transferring judges between circuits, as delimited by the Chief Justice’s Guidelines, is directed strictly toward meeting judicial necessities, whereas the transfer in this case would serve a different purpose. . . .  [H]aving the district judge who conducted MDL pre-trial proceedings also preside over the trial of the case can improve judicial efficiency, preserve scarce judicial resources and enhance MDL judges’ control over their proceedings.  These are worthy goals, to be sure, but not ones in any way reflected in the Guidelines.

MFT, 711 F.3d at 1054.  Allowing a transfer would effectively divest the judges of the transferor district of cases ordinarily assigned to them.  There is “no authority empowering the chief judge of the circuit to re-assign cases pending before other judges, or to remove cases from the district’s assignment wheel” in the absence of recusal.  Id. Short of amending the guidelines (which doesn’t seem to have happened since 2013) there wasn’t “any way” to “constru[e]” them to allow an MDL judge to engineer his or her own assignment to a specific post-remand case.  Id. at 1055.

Since it was decided in 2014, MFT hasn’t been cited except in the Ninth Circuit – as we suppose befits such an arcane decision.  It may well be, as a commentator has commented, that visiting judge “requests are often granted routinely by circuit chief judges” in MDL situations.  Sherman, “When Remand Is Appropriate in Multidistrict Litigation,” 75 La. L. R. 455, 460 (2014).  However, “intercircuit transfers based on efficiency could encroach on the authority of transferor judges to resume rightful control over their cases upon completion of pretrial proceedings.”  Id.  See MacFarlane, “The Danger of Nonrandom Case Assignment:  How the Southern District of New York’s ‘Related Cases’ Rule Shaped Stop-and-Frisk Rulings,” 19 Mich. J. Race & L. 199, 213 (2014) (“the visiting judge [under §292(d)] would be expected to help relieve that burden, rather than dictate what types and number of cases he or she is willing to hear”).

It may seem extreme that an MDL judge would react to Lexecon – and lack of an appropriate waiver − by seeking to chase the parties back to their home districts, but such an extreme situation is precisely when our clients may feel compelled to invoke MFT to try to end the chase.  We hope our clients never need it, but if they do, remember that the only actual precedent out there rejects letting MDL judges maintain control over cases after remand.

DISCLAIMER: Because of the generality of this update, the information provided herein may not be applicable in all situations and should not be acted upon without specific legal advice based on particular situations.

© Reed Smith | Attorney Advertising

Written by:

Reed Smith
Contact
more
less

Reed Smith on:

Readers' Choice 2017
Reporters on Deadline

"My best business intelligence, in one easy email…"

Your first step to building a free, personalized, morning email brief covering pertinent authors and topics on JD Supra:
Sign up using*

Already signed up? Log in here

*By using the service, you signify your acceptance of JD Supra's Privacy Policy.
Custom Email Digest
Privacy Policy (Updated: October 8, 2015):
hide

JD Supra provides users with access to its legal industry publishing services (the "Service") through its website (the "Website") as well as through other sources. Our policies with regard to data collection and use of personal information of users of the Service, regardless of the manner in which users access the Service, and visitors to the Website are set forth in this statement ("Policy"). By using the Service, you signify your acceptance of this Policy.

Information Collection and Use by JD Supra

JD Supra collects users' names, companies, titles, e-mail address and industry. JD Supra also tracks the pages that users visit, logs IP addresses and aggregates non-personally identifiable user data and browser type. This data is gathered using cookies and other technologies.

The information and data collected is used to authenticate users and to send notifications relating to the Service, including email alerts to which users have subscribed; to manage the Service and Website, to improve the Service and to customize the user's experience. This information is also provided to the authors of the content to give them insight into their readership and help them to improve their content, so that it is most useful for our users.

JD Supra does not sell, rent or otherwise provide your details to third parties, other than to the authors of the content on JD Supra.

If you prefer not to enable cookies, you may change your browser settings to disable cookies; however, please note that rejecting cookies while visiting the Website may result in certain parts of the Website not operating correctly or as efficiently as if cookies were allowed.

Email Choice/Opt-out

Users who opt in to receive emails may choose to no longer receive e-mail updates and newsletters by selecting the "opt-out of future email" option in the email they receive from JD Supra or in their JD Supra account management screen.

Security

JD Supra takes reasonable precautions to insure that user information is kept private. We restrict access to user information to those individuals who reasonably need access to perform their job functions, such as our third party email service, customer service personnel and technical staff. However, please note that no method of transmitting or storing data is completely secure and we cannot guarantee the security of user information. Unauthorized entry or use, hardware or software failure, and other factors may compromise the security of user information at any time.

If you have reason to believe that your interaction with us is no longer secure, you must immediately notify us of the problem by contacting us at info@jdsupra.com. In the unlikely event that we believe that the security of your user information in our possession or control may have been compromised, we may seek to notify you of that development and, if so, will endeavor to do so as promptly as practicable under the circumstances.

Sharing and Disclosure of Information JD Supra Collects

Except as otherwise described in this privacy statement, JD Supra will not disclose personal information to any third party unless we believe that disclosure is necessary to: (1) comply with applicable laws; (2) respond to governmental inquiries or requests; (3) comply with valid legal process; (4) protect the rights, privacy, safety or property of JD Supra, users of the Service, Website visitors or the public; (5) permit us to pursue available remedies or limit the damages that we may sustain; and (6) enforce our Terms & Conditions of Use.

In the event there is a change in the corporate structure of JD Supra such as, but not limited to, merger, consolidation, sale, liquidation or transfer of substantial assets, JD Supra may, in its sole discretion, transfer, sell or assign information collected on and through the Service to one or more affiliated or unaffiliated third parties.

Links to Other Websites

This Website and the Service may contain links to other websites. The operator of such other websites may collect information about you, including through cookies or other technologies. If you are using the Service through the Website and link to another site, you will leave the Website and this Policy will not apply to your use of and activity on those other sites. We encourage you to read the legal notices posted on those sites, including their privacy policies. We shall have no responsibility or liability for your visitation to, and the data collection and use practices of, such other sites. This Policy applies solely to the information collected in connection with your use of this Website and does not apply to any practices conducted offline or in connection with any other websites.

Changes in Our Privacy Policy

We reserve the right to change this Policy at any time. Please refer to the date at the top of this page to determine when this Policy was last revised. Any changes to our privacy policy will become effective upon posting of the revised policy on the Website. By continuing to use the Service or Website following such changes, you will be deemed to have agreed to such changes. If you do not agree with the terms of this Policy, as it may be amended from time to time, in whole or part, please do not continue using the Service or the Website.

Contacting JD Supra

If you have any questions about this privacy statement, the practices of this site, your dealings with this Web site, or if you would like to change any of the information you have provided to us, please contact us at: info@jdsupra.com.

- hide
*With LinkedIn, you don't need to create a separate login to manage your free JD Supra account, and we can make suggestions based on your needs and interests. We will not post anything on LinkedIn in your name. Or, sign up using your email address.