CASES (2024)

Allen v. Foxway Transp., Inc.

United States District Court, M.D. Pennsylvania.

ROBERT C. ALLEN, as Administrator of the ESTATES OF T.G.A. and Z.D.A., Plaintiff,

FOXWAY TRANSPORTATION, INC., TEMPEL STEEL, and GATEWAY FREIGHT SYSTEMS, INC., Defendants.

No. 4:21-CV-00156

Filed 12/07/2023

MEMORANDUM OPINION

Matthew W. Brann Chief United States District Judge

*1 This case arises out of a tragic motor vehicle accident which resulted in the death of two children. After the children’s mother hit a deer, their vehicle was disabled in the path of a tractor trailer driven by an employee of Foxway Transportation Inc., a motor carrier retained by Gateway Freight Systems, Inc., to deliver a shipment for Tempel Steel. The ensuing collision killed the Allen children. Plaintiff Robert C. Allen, as the administrator of his minor children’s estates, sued Foxway, Gateway, and Tempel, seeking to hold them liable for his children’s deaths.

Currently pending before the Court are Partial Motions for Summary Judgment filed by Allen as to certain claims against Gateway, and a Motion for Summary Judgment filed by Gateway. Because the Court finds that Gateway, as a broker, is not liable for the actions of Foxway or its driver, but that a material dispute exists regarding whether Gateway negligently entrusted Foxway with the shipment, the Court will deny Allen’s motions in part, grant Gateway’s motion in part, and reserve judgment on the issue of negligent entrustment.

I. RELEVANT PROCEDURAL BACKGROUND

On January 28, 2021, Allen initiated this suit against Defendants Foxway Transportation, Inc., Tempel Steel, Gateway Freight Systems, Inc., and State Farm Mutual Insurance Company.¹ Allen amended his complaint on April 22, 2021,² and the Court denied motions to dismiss the amended complaint filed by Foxway³ and Gateway⁴ on January 27, 2022.⁵ Allen dismissed his claims against State Farm on September 30, 2022.⁶

Against Gateway, Allen brings the following claims for relief: Damages under the Pennsylvania Wrongful Death and Survival statutes (Counts V and VI); vicarious liability (Count VII); “Negligent and/or Reckless Hiring / Supervision / Retention / Negligent Selection” of Volodymyr Frolyak (Count VIII) and Foxway Transportation (Count IX); Negligent Entrustment (Count X); and Joint Venture (Count XI).⁷

On April 13, 2023, Allen filed two partial motions for summary judgment on the issues of vicarious liability⁸ and negligent hiring.⁹ On April 14, 2023, Gateway filed a motion for summary judgment, asking the Court to dismiss all the claims against it.¹⁰ On April 24, 2023, Gateway filed a letter with the Court, requesting a status conference regarding Allen’s reliance on two previously undisclosed expert witnesses in his motions, and asking the Court to adjust the briefing schedule to permit Gateway to retain a rebuttal expert.¹¹ The Court held a status conference and granted Gateway’s request.¹² Then, the Court was once again asked to step in and modify the briefing schedule to accommodate Allen’s request to depose Gateway’s expert.¹³ On October 13, 2023, exactly six months and forty docket entries after the first motion for summary judgment was filed, the final reply briefs trickled in. The motions were finally ripe for disposition.¹⁴

*2 And yet, upon review of the parties’ briefs, the Court noted that they had little to say about the gating issue of this case: whether Voldymyr Frolyak, the Foxway driver, was liable for the accident in the first instance.¹⁵ The Court asked the parties for simultaneous, supplemental briefs on that issue, which were filed on November 20, 2023.¹⁶

II. STANDARDS OF REVIEW

A. Summary Judgment

Under Federal Rule of Civil Procedure 56(a), summary judgment is appropriate where “the movant shows that there is no genuine dispute as to any material fact and the movant is entitled to a judgment as a matter of law.” As expressed by the Supreme Court of the United States in Celotex Corp. v. Catrett, summary judgment is required where a party “fails to make a showing sufficient to establish the existence of an element essential to that party’s case” on an issue that the “party will bear the burden of proof at trial.”¹⁷ Material facts are those “that could alter the outcome” of the litigation, “and disputes are ‘genuine’ if evidence exists from which a rational person could conclude that the position of the person with the burden of proof on the disputed issue is correct.”¹⁸

The party requesting summary judgment bears the initial burden of supporting its motion with evidence from the record.¹⁹ When the movant properly supports its motion, the nonmoving party must then show the need for a trial by setting forth “genuine factual issues that properly can be resolved by only a finder of fact because they may reasonably be resolved in favor of either party.”²⁰ The United States Court of Appeals for the Third Circuit explains that the nonmoving party will not withstand summary judgment if all it has are “assertions, conclusory allegations, or mere suspicions.”²¹ Instead, it must “identify those facts of record which would contradict the facts identified by the movant.”²²

In assessing “whether there is evidence upon which a jury can properly proceed to find a verdict for the [nonmoving] party,”²³ the Court “must view the facts and evidence presented on the motion in the light most favorable to the nonmoving party.”²⁴ Moreover, “[i]f a party fails to properly support an assertion of fact or fails to properly address another party’s assertion of fact as required by Rule 56(c),” the Court may “consider the fact undisputed for purposes of the motion.”²⁵ Finally, although “the court need consider only the cited materials, … it may consider other materials in the record.”²⁶

*3 “ ‘This standard does not change when the issue is presented in the context of cross-motions for summary judgment.’ ”²⁷ “When both parties move for summary judgment, ‘the court must rule on each party’s motion on an individual and separate basis, determining, for each side, whether a judgment may be entered in accordance with the Rule 56 standard.’ ”²⁸

B. Local Rule 56.1

In support of his motions for summary judgment on the issues of vicarious liability and negligent hiring, Allen filed two statements of material facts that run 83 and 107 paragraphs respectively.²⁹ Gateway asks the Court to strike Allen’s statements of facts because they are “replete with legal conclusions, expert analysis, opinion, and mischaracterizations without references to the record or supporting facts.”³⁰ Allen suggests that Gateway is “precluded from asserting any issue with respect to Plaintiff’s concise statement of facts” on the grounds that 1) the Court has already rejected Gateway’s arguments and 2) his statements comply with the Federal and Local Rules.³¹

Local Rule 56.1 requires all motions for summary judgment to be “accompanied by a separate, short, and concise statement of the material facts, in numbered paragraphs, as to which the moving party contends there is no genuine issue to be tried.” The party opposing summary judgment must then include with its papers an answer to the movant’s statement of facts in which it identifies, in corresponding numbered paragraphs, those material facts which the nonmovant contends there is a genuine issue to be tried.³² “Statements of material facts in support of, or in opposition to, a motion shall include references to the parts of the record that support the statements.”³³ Material facts in the movant’s statement “will be deemed to be admitted unless controverted by the statement required to be served by the opposing party.”³⁴

When reviewing statements of facts, the Court first looks to see if the parties agree on a fact. If so, the Court accepts the fact as stated. If not, the Court will look to the parts of the record cited by each party and make its own determination as to whether the fact in question is disputed. If a party has not supported its stated fact or its denial of that fact with a record citation, then the Court will either assume that the fact is disputed or admitted accordingly. No more, no less.

The remedy to a deficient statement of facts is, therefore, simply an adequate response. For instance, to the extent that, as Gateway claims, half of Allen’s statement of facts in support of his motion for summary judgment on the issue of vicarious liability do not “contain any reference, vague or otherwise, to the record,” all Gateway need do is respond to those paragraphs accordingly. Gateway could have simply denied each of the SMFs’ paragraphs with citations to the record or by identifying statements which are simply legal argument and that would have been sufficient to obviate any concerns of a false narrative.

*4 Unfortunately, Gateway did not file such an answer. Instead, perhaps following Allen’s lead, filed “counterstatements of facts.”³⁵ The purpose of Rule 56.1 is to “structure a party’s summary judgment legal and factual theory that permits and facilitates the court’s direct and accurate consideration to the motion.”³⁶ “The movant’s statement and the non-movants response should enable ‘the court to identify contested facts expeditiously.’ ”³⁷ Competing statements of facts, let alone six of them, do not serve this purpose.

Though the impulse to correct the record is understandable, it is unnecessary. A party opposing summary judgment need not correct the record to survive summary judgment. Instead, the non-movant simply must show that there is a genuine dispute of material fact. If the non-movant wants to present its own narrative, then it may file its own motion for summary judgment (as Gateway did).

In any case, Gateway is not harmed by any deficiencies in Allen’s statements of facts because Allen does not rely on his statements of facts in his briefs. Rather than refer to his statements of facts in his briefing, Allen simply incorporates the cited portions of the record into his brief. Rather than “facilitating direct and accurate consideration to the motion,” this results in statements of fact that are mere surplusage.

Accordingly, though the parties’ statements and counterstatements of fact are of limited utility here, the Court will consider them to the extent that they are helpful.

C. Conflicting Expert Witness Opinions

Gateway also objects to the opinions of Allen’s proffered expert witnesses, Jon Paul Dillard and Kenneth Lacey.³⁸ Allen relies heavily on the opinions of Dillard and Lacey in his motions.³⁹ In response, Gateway retained a rebuttal expert, Lane VanIngen.⁴⁰ Where issues turn on opposing expert reports, “a genuine issue of fact patently exists preventing summary judgment.”⁴¹

Predictably, Allen and Gateway both suggest that the Court should simply disregard their opponent’s expert opinions. Though the parties have identified issues that may require the Court to exclude the experts’ opinions, that issue is not properly before the Court. Neither party has filed a motion to exclude an opposing expert and the objections raised in the parties’ papers are insufficient to allow the Court to permit the Court to exclude the evidence under Federal Rule of Evidence 702. The Third Circuit has emphasized that, prior to excluding expert evidence on a motion for summary judgment, that the Court must “provide the [parties] with sufficient process for defending their evidentiary submissions.”⁴²

*5 Gateway emphasizes that its motion “is not at all reliant on Mr. VanIngen or any other expert analysis—it relies solely on the facts of the case.”⁴³ But the Court cannot simply overlook expert testimony that Allen offers in opposition to Gateway’s motion.

However, “an expert cannot testify to [a] legal conclusion”⁴⁴ and, to the extent that the parties’ experts do so, the Court will disregard such opinions.⁴⁵ In such instances, the Court will instead look to the facts and conclusions underlying the expert’s opinion to determine whether there is a material issue of fact.

III. FACTUAL BACKGROUND⁴⁶

On October 20, 2019, Darlene L. Allen, with her children T.G.A. and Z.D.A. in the back seat, struck a deer while driving on New York State Route 17 in Tioga County, New York.⁴⁷ Ms. Allen’s Mitsubishi Mirage was disabled as a result, and came to a rest in the right-hand lane of SR-17.⁴⁸ Traveling behind Ms. Allen, was Volodymyr Frolyak, operating a commercial tractor trailer carrying a load of steel laminations.⁴⁹ Unfortunately, despite its name, Ms. Allen’s Mirage was no optical illusion and Frolyak was unable to stop, or adequately slow his vehicle before it violently collided with the Allen’s vehicle, killing the two children.⁵⁰

Frolyak, an employee of Foxway Transportation, Inc. and driving a 2016 Freightliner owned by Foxway, was delivering a shipment that originated at Tempel Steel’s Canadian location to two locations in Pennsylvania.⁵¹ Gateway, on Tempel’s behalf, had retained Foxway to handle the shipment.⁵² The parties agree on little else regarding the relationship between the parties, as will be discussed below.

IV. ANALYSIS

A. Driver Liability

Gateway argues in support of its Motion that Allen “has failed to adduce any facts indicating that any person or entity is actually culpable and at fault for either collision.”⁵³ Whether Frolyak himself is liable for the accident is the threshold issue in this case: Gateway cannot be vicariously liable unless Frolyak himself is liable in the first instance. Opposing Gateway’s Motion, Allen suggests, without any citation to the record, that it is “undisputed” and “unrefuted” Frolyak caused the accident when he was “inattentive, fatigued/distracted and otherwise operating the Freightliner in an unsafe, dangerous, and reckless condition.”⁵⁴ The first citation to the record follows a reference to testimony by Deputy Samuel Warner that the crash “could have been ‘an avoidable crash, rather than an unavoidable crash,’ ” but for Frolyak’s inattentiveness.⁵⁵ Allen then cites the report of his expert, Kenneth Lacey, who Allen says “opined there is no evidence of any other cause of the crash but driver unfitness, impairment, or exhaustion.”⁵⁶

*6 Both statements mischaracterize the record. The cited testimony of Deputy Warner was elicited by a line of questioning in which counsel asked Warner to speculate as to what may have caused the accident, or how the accident could have been avoided.⁵⁷ In his report, Lacey concludes that Gateway’s failure to properly investigate Foxway “was reckless, dangerous and directly resulted in the October 20, 2019 crash and its resulting injuries.”⁵⁸ He offers no opinion regarding the crash itself.

The Court, worried that, in the midst of extensive briefing on derivative issues such as vicarious liability and negligent entrustment, Allen had missed the forest for the trees, requested the parties file supplemental briefing on the issue of whether Frolyak himself was liable for the accident.⁵⁹

In his supplemental brief, Allen now suggests that “Frolyak reported fog at the time he collided with the Allen vehicle” and that, with his cruise control set at 64.5 mph, he was traveling at an unsafe speed given the conditions.⁶⁰ Allen relies heavily on the opinion of Accident Reconstruction Expert Joseph Hudak.⁶¹ Mr. Hudak’s report is dated November 20, 2023, a week after the Court requested the supplemental briefing.

This is now the second time that Allen has filed a brief relying on previously undisclosed expert opinion. As discussed above, the Court indulged Allen once, permitting him to belatedly complete his expert disclosures.⁶² It will not do so again.

Federal Rule of Civil Procedure 26(a)(2) requires a party to complete its expert disclosures “at the times and in the sequence that the court orders.”⁶³ A failure to do so precludes the party from relying on that witness “to supply evidence on a motion … unless the failure was substantially justified or is harmless.”⁶⁴ The Third Circuit has instructed, “[i]n considering whether the exclusion of evidence is an appropriate sanction for failure to comply with discovery duties, [courts] must consider four factors: (1) the prejudice or surprise of the party against whom the excluded evidence would have been admitted; (2) the ability of the party to cure that prejudice; (3) the extent to which allowing the evidence would disrupt the orderly and efficient trial of the case or other cases in the court; and (4) bad faith or willfulness in failing to comply with a court order or discovery obligation.”⁶⁵

All four factors support excluding Hudak’s report. As noted its brief, “[t]o Gateway’s knowledge the only reconstruction performed to date is by the New York State Police.”⁶⁶ Gateway has not had the opportunity to evaluate Hudak’s claims, or challenge them directly in a deposition and providing that opportunity would result in further delaying resolutions of motions filed in April.⁶⁷ There is no justification for, after nearly three years of litigation, failing to identify an expert witness on the core issue of this case until after the parties had completed briefing on motions for summary judgment.

Nevertheless, the record is insufficient to determine at summary judgment whether the conditions present at the time of the accident were severe enough to require Frolyak to reduce his speed. Therefore, the Court will continue to the balance of the parties’ arguments.

B. Vicarious Liability

1. Common Law Employee-Employer

*7 “Under Pennsylvania law, to establish vicarious liability, a plaintiff must show a master-servant relationship existed.”⁶⁸ “The Pennsylvania Supreme Court set forth an array of factors to be considered when examining the employer-employee relationship:”

(1) control of the manner in which the work is done; (2) responsibility for the result only; (3) terms of agreement between the parties; (4) nature of the work/occupation; (5) skill required for performance; (6) whether one is engaged in a distinct occupation or business; (7) whether the work is part of the regular business of the alleged employer; (8) which party supplies the tools/equipment; and (9) whether the alleged employer has the right to terminate the employment at any time.⁶⁹

“Not all factors are required to establish an employment relationship.”⁷⁰ The factors entitled to the most weight are “whether the purported employer has the right to hire and fire the employee; whether the employer has the right to direct the manner of the employee’s performance of the work; and whether the employer has the right to control the work to be completed.”⁷¹ Allen does not argue that Gateway supplied the truck or had the right to terminate Frolyak.⁷²

Allen argues that “Gateway exercised, or had the right to exercise, the requisite degree of control over Mr. Frolyak such that Gateway must be deemed his common law “employer” and, therefore, vicariously liable for his conduct.”⁷³ Nowhere in the twenty pages that Allen devotes to this issue does he cite any authority regarding what suffices to establish the “requisite degree of control.” Instead, Allen offers a prime example of why requesting extra words from a court is not a substitute for exercising editorial discretion as he gets lost along the way and argues, not that Gateway had control over Frolyak, but that Gateway was a “motor carrier.” That is a separate issue, which the Court discusses separately, and says nothing about the level of control Gateway had over Frolyak.

The only substantive mention of Frolyak in this section of Allen’s brief is where he argues that, because Gateway communicated with Tempel regarding the timing of the product and that it was an “exclusive truckload,” Gateway was “responsible for all aspects of the management of the freight … including the dispatching and routing of Mr. Frolyak.”⁷⁴ There is no evidence that Gateway instructed Frolyak to take a specific route, and that Gateway “handled the … time frame in which the product was to be picked up”⁷⁵ “does not, without more, create the control necessary for the employer-employee relationship.”⁷⁶

On the contrary, Foxway assigned Frolyak and a city driver, Gurvinder Singh, to the Tempel load, without any direction from Gateway.⁷⁷ Foxway owned the Freightliner that Frolyak was driving. Contrary to Allen’s frivolous argument that Gateway provided the route because Frolyak’s route was constrained by the requirements that the shipment make it from “A to B” in a certain time window—preventing him from taking a route “through California and then to Pennsylvania”⁷⁸—Foxway provided the route.⁷⁹

*8 The Court also rejects Allen’s conclusory arguments that driving a tractor-trailer does not require special skills or that Frolyak’s work was an integral part of Gateway’s regular business. As to the former, the Court is skeptical that “the ability to drive” a car translates to the ability to drive a tractor-trailer. As to the latter, Allen’s “argument would essentially remove any distinction between brokers and motor carriers by making anyone involved in the shipment process an employee of the broker.”⁸⁰

In support of its own motion, Gateway argues that Allen’s failure to “adduce any facts indicating Gateway directed or controlled Frolyak or had the right to do either.”⁸¹ In his opposition, Allen largely repeats his own arguments which, again, say very little about Gateway’s relationship with Frolyak.⁸² Instead, Allen suggests that Gateway “has failed to provide even a scintilla of evidence” in support of its position that “it cannot be a motor carrier.”⁸³ As above, whether Gateway is a motor carrier is a separate question, which the Court will address below.

2. Statutory Employee

In the alternative, Allen argues that Gateway functioned as the de facto motor carrier and statutory employer of Frolyak. To determine whether an entity acted as a broker or a carrier, “courts look to ‘how the party acted during the specific transaction at issue, which includes the understanding among the parties involved [and] consideration of how the entity held itself out.’ ”⁸⁴ “Thus, ‘[w]hether a company is a broker or a carrier is not determined by what the company labels itself, but by … its relationship to the shipper.’ ”⁸⁵ In making this determination, “the crucial question is whether the party has legally bound itself to transport goods by accepting responsibility for ensuring the delivery of the goods.”⁸⁶ Factors which inform this inquiry are:

(1) whether the entity promised to personally perform the transport and therefore legally bound itself to transport;

(2) the type of services the entity offers;

(3) whether the entity held itself out to the public as the actual transporter of goods; and

(4) whether the entity’s only role was to secure a third party to ship plaintiff’s goods.⁸⁷

Courts also look to “who arranged the details of the transport process” such as handling the route, packing the product, coordinating the travel and release of goods, whether the party acted as a go-between or served as a central point of communication for both the carrier and the shipper, and if the shipper knew who exactly was carrying the load.⁸⁸

*9 There is no evidence in the record that Gateway promised to personally perform the transport. On the contrary, when Tempel reached out to Gateway and asked Gateway to arrange for shipping, Gateway responded that it would “schedule and advise carrier name.”⁸⁹ When Tempel reached out to Gateway, “it [was] known by Tempel that Gateway is only a broker.”⁹⁰ Tempel understood Gateway to be offering its services as a broker, and not a carrier.⁹¹

Allen’s expert, Dillard, suggests that Gateway had advertised itself as a “transportation provider” rather than a broker.⁹² Even if the Court assumes Dillard is correct, whether Gateway held itself out to the public as a carrier is of limited significance here, where Tempel already knew Gateway was a broker. This is not a case where a shipper had been deceived by a broker’s “attempt to gain business and revenue disguised as a motor carrier.”⁹³ Allen’s argument on this point also proves too much. If Gateway is, as Dillard opines, misrepresenting its services by promoting itself as a carrier despite being only a broker, that is evidence that Gateway is, in fact, a broker. Whether Gateway’s website runs afoul of the Federal Motor Carrier Safety Regulations may be an interesting question, but it is not one before the Court.

Allen argues that Gateway was responsible for the details of the shipping process, and therefore its role was beyond that of a mere middleman whose only role was to secure transportation for Tempel’s goods. Allen notes that, once Tempel provided Gateway with the origin and delivery points of the shipment, it did not handle the route.⁹⁴ Neither did Gateway; Foxway did.⁹⁵ Allen observes that Foxway did not pack the product.⁹⁶ Again, neither did Gateway; Tempel did.⁹⁷ Allen suggests that no entity other than Gateway “was involved in the planning process” then immediately contradicts himself, stating that “the terms of the shipment were dictated by Tempel and Gateway with no input from Foxway.”⁹⁸ Gateway’s involvement in the “planning process” was limited to finding a carrier within two hours of Tempel’s request so that Tempel could be “sure that [Gateway] would be able to move the product for them.”⁹⁹ It was Tempel who dictated when and where the shipment needed to be delivered.¹⁰⁰

The Court is not aware of a bright line rule for distinguishing a “go-between” from a “central point of communication,” but the above scenario illustrates the role of a broker. Gateway was “employed as a middleman to transact business … between different merchants.”¹⁰¹ Allen cannot avoid this conclusion by cherry picking examples of actions not taken by Foxway or Tempel, and automatically assigning the responsibility for those actions to Gateway.

*10 Further, while Tempel did not know that Foxway itself was carrying the load, they did know that Gateway was not. Responding to Tempel’s request for Gateway to find a carrier for the shipment, a representative from Gateway responded that she would advise Tempel of the carrier’s name.¹⁰² Gateway’s apparent failure to follow up and inform Tempel that Foxway was carrying the load amounts to little more than a clerical error and is insufficient to render Gateway liable to the Allen family.

Resisting the inevitability of the conclusion that Gateway is a broker, Allen extensively discusses several documents, including bills of lading, terms of service, service agreements, pack lists, and invoices. There is less to Allen’s seventy-page brief than meets the eye.

Gateway being listed as the “carrier” on documents it did not prepare or execute is insufficient to create an issue of material fact.¹⁰³ Terms and Conditions that bind Tempel and the customers who purchase its products are not relevant to the separate transaction of Tempel shipping the product. Invoices between Gateway and Tempel and Foxway are consistent with its role as a broker.¹⁰⁴

During civil litigation, particularly litigation involving multiple corporate entities, the parties will produce countless documents. There will inevitably be documents that, if squinted at hard enough, give rise to all manner of colorable arguments. Though the material fact and reasonable juror standards may be low, they are not toothless. “If the evidence is merely colorable, … or is not significantly probative, … summary judgment may be granted.”¹⁰⁵

The whole of the evidence relied on by Allen is less than the sum of its parts. Again, the inquiry is guided by the understanding of the parties to the transaction. None of the documents cited by Allen are sufficiently probative to controvert the clear understanding among Tempel, Foxway, and Gateway as to the roles of each as shipper, carrier, and broker respectively in the subject transaction. This fact is dispositive and is what distinguishes this case from those upon which Allen relies.¹⁰⁶ Gateway did not communicate with Frolyak, Foxway’s driver and employee, or ask him to identify himself as an employee of Gateway.¹⁰⁷ Gateway did not bind itself to physically transport the shipment.¹⁰⁸

*11 Therefore, the Court will deny Allen’s Motion as to the issue of vicarious liability and grant Gateway’s Motion as to Count VII.¹⁰⁹

C. Negligent Hiring, Selection, Retention, or Supervision

These theories of liability under Pennsylvania law are predicated upon an employer-employee relationship.¹¹⁰ “The Third Circuit has taken this ‘clear feature’ of these claims within Pennsylvania’s body of negligence law ‘to be dispositive.’ ”¹¹¹ As the Court has established as a matter of law that there is no employer-employee relationship between Gateway and Frolyak, the Court will deny Allen’s Partial Motion on Negligent Hiring, Selection, and Entrustment as to Counts VIII and IX and grant Gateway’s Motion as to those Counts.

D. Negligent Entrustment

Pennsylvania has adopted the standard for negligent entrustment that is set out in Section 308 of the Restatement of the Law (Second) of Torts:

It is negligence to permit a third person to use a thing or to engage in an activity which is under the control of the actor, if the actor knows or should know that such person intends or is likely to use the thing or to conduct himself in the activity in such a manner as to create an unreasonable risk of harm to others.¹¹²

Allen argues that Gateway “knew or should have known that Foxway was negligent in retaining its drivers, including Volodymyr Frolyak.”¹¹³ He asserts that, despite having access to the “Carrier411” system which would have alerted it to “the unsafe history of both Foxway and Volodymyr Frolyak,” “Gateway entrusted a Commercial Motor Vehicle to Volodymyr Frolyak.”¹¹⁴

Gateway argues that “no material facts indicate that Gateway controlled or had the right to control the shipment, the Foxway Freightliner, or any operator of the same, including Frolyak.”¹¹⁵ Gateway stresses that “[t]he facts demonstrate an absence of a Gateway relationship with the Freightliner itself.”¹¹⁶ Further, Gateway argues that the record does not support Allen’s assertion that Gateway “knew or should have known” that Foxway or Frolyak presented “an unreasonable risk of harm.”¹¹⁷

The Court finds that, by possessing the authority to assign the shipment, and ultimately assigning it to Foxway, Gateway had the requisite control over the “activity” of shipping the goods. Allen, in support of his motion and in opposition to Gateway’s, relies heavily on the expert opinion of Kenneth Lacey who opines that “Gateway made no effort to make certain Foxway, or any other motor carrier to which it entrusted its freight, operated safely, or [in] complian[ce] with federal or state regulations.”¹¹⁸ Gateway, through its own expert, argues that “Lacey’s report contains opinions contrary to the FMCSR and industry standards.”¹¹⁹

*12 As discussed above, issues which turn on competing expert testimony are rarely fit for disposition on a motion for summary judgment. Ordinarily, the Court would simply deny the parties’ motions and let the live issues proceed to trial. However, after consulting its crystal ball, the Court foresees the parties filing motions in limine on the eve of trial consistent with the objections they have raised in their briefing, seeking to exclude their opponent’s proffered expert testimony. If either party were to prevail on such a motion, they would assuredly renew their motion for summary judgment.

Rather than kick the expert witness can down the road, the Court will require the parties to file any Daubert motions by December 28, 2023. Until those motions are briefed, the Court will reserve judgment on the issue of negligent entrustment. Further, as the availability of punitive damages turns on the degree that Gateway may have fallen short of the applicable standard of care, the Court will reserve judgment on that issue as well.

E. Joint Venture

Under Pennsylvania law, “[a] joint venture requires that: ‘1) each party must make a contribution of capital, materials, services or knowledge; 2) profits must be shared; and 3) there must be a joint proprietary interest in and right of mutual control over the subject matter of the enterprise.’ ”¹²⁰ “Once a party satisfies the test for a joint venture, the torts committed by one joint adventurer may be imputed upon other joint adventurers.”¹²¹

Gateway asserts that Allen “has failed to adduce facts supporting any necessary element and any intention by and between Gateway, Foxway, and Tempel Steel to enter into a joint venture concerning Frolyak and the subject shipment.”¹²² Allen’s response borders on forfeiture of his claim. Allen suggests that “the use of the equipment in the transportation cycle … [is] akin to a distribution of profits.”¹²³ Allen’s argument, such as it is, would render the second prong of the joint venture test duplicative of the first. The contribution of the equipment, or other capital, services, or knowledge, is distinct from a distribution or sharing of profits.

Allen is the plaintiff, and it is his burden to show that there are material facts on which he could ultimately prevail on his claim. He offers none, nor does he offer any legal authority for his convoluted argument. The Court will therefore grant Gateway’s motion for summary judgment as to Count XI.

V. CONCLUSION

For the forgoing reasons, the Court will deny Allen’s first motion for summary judgment on the issue of vicarious liability; deny Allen’s second motion for summary judgment on the issue of negligent hiring; grant Gateway’s motion for summary judgment as to the issues of vicarious liability, negligent hiring, and joint venture; and reserve judgment on the issue of negligent entrustment pending submissions from the parties regarding whether they wish to move to exclude the opposing parties’ expert witnesses. The parties may file Daubert motions and accompanying briefs by December 28, 2023. Any briefs shall comply with the local rules.¹²⁴ Consistent with those rules, any response briefs are due on January 11, 2024 and reply briefs are due January 25, 2024. If the parties opt not to oppose the admissibility of the expert opinions by the deadline, the Court will enter an order denying the parties’ motions for summary judgment as to the remaining issues.

*13 An appropriate Order follows.

BY THE COURT:

All Citations

Footnotes

¹	Compl., Doc. 1.
²	Am. Compl., Doc. 17.
³	Foxway Mtn. Dismiss, Doc. 22.
⁴	Gateway Mtn. Dismiss, Doc. 37.
⁵	Jan. 27, 2022 Ord., Doc. 51.
⁶	Notice of Dismissal, Doc. 89; Oct. 19, 2022 Ord., Doc. 95.
⁷	Am. Compl., Doc. 125.
⁸	Mot. Summ. J. re: Vicarious Liability (“VL MSJ”), Doc. 111.
⁹	Mot. Summ. J. re: Negligent Hiring (“NH MSJ”), Doc. 113.
¹⁰	Gateway Mot. Summ. J. (“Gateway MSJ”), Doc. 117.
¹¹	Apr. 24, 2023 Gateway Letter, Doc. 119.
¹²	May 4, 2023 Ord., Doc. 128.
¹³	Aug. 11, 2023 Gateway Letter, Doc. 136; Aug 23, 2023 Ord., Doc. 140.
¹⁴	VL Br., Doc. 112; NH Br., Doc. 114; Gateway MSJ Br., Doc. 125; Gateway MSJ Opp., Doc. 131; Gateway MSJ Reply, Doc. 142; VL Opp., Doc. 143; NH Opp., 144; VL Reply, Doc. 149; NH Reply, Doc. 150.
¹⁵	Nov. 6, 2023 Ord., Doc. 154.
¹⁶	Gateway Supp. Br., Doc. 155; Allen Supp. Br., Doc. 156.
¹⁷	477 U.S. 317, 322 (1986).
¹⁸	EBC, Inc. v. Clark Bldg. Sys., Inc., 618 F.3d 253, 262 (3d Cir. 2010) (quoting Clark v. Modern Grp. Ltd., 9 F.3d 321, 326 (3d Cir. 1993)).
¹⁹	Celotex, 477 U.S. at 323.
²⁰	Anderson v. Liberty Lobby, Inc., 477 U.S. 242, 250 (1986).
²¹	Betts v. New Castle Youth Dev. Ctr., 621 F.3d 249, 252 (3d Cir. 2010).
²²	Port Auth. Of N.Y. and N.J. v. Affiliated FM Ins. Co., 311 F.3d 226, 233 (3d Cir. 2002) (quoting Childers v. Joseph, 842 F.2d 689, 694-95 (3d Cir. 1988)).
²³	Liberty Lobby, 477 U.S. at 252 (quoting Schuylkill & Dauphin Imp. Co. v. Munson, 81 U.S. 422, 448 (1871)).
²⁴	Razak v. Uber Technologies, Inc., 951 F.3d 137, 144 (3d Cir. 2020).
²⁵	Fed. R. Civ. P. 56(e)(2); see also Weitzner v. Sanofi Pasteur Inc., 909 F.3d 604, 613-14 (3d Cir. 2018).
²⁶	Fed. R. Civ. P. 56(c)(3).
²⁷	Auto-Owners Ins. Co. v. Stevens & Ricci Inc., 835 F.3d 388, 402 (3d Cir. 2016) (quoting Appelmans v City of Phila, 826 F.2d 214, 216 (3d. Cir. 1987)).
²⁸	Id. (quoting 10A Charles Alan Wright et al., Federal Practice & Procedure § 2720 (3d ed. 2016)).
²⁹	VL Statement of Material Facts (“VL SMF”), Doc. 112-1; NH SMF, Doc. 114-1.
³⁰	VL Opp. 8; NH Opp. 7.
³¹	VL Reply 46; NH Reply 55.
³²	LR 56.1.
³³	Id.
³⁴	Id.
³⁵	Allen, due to the changes in the briefing schedule, filed his opposition to Gateway’s motion prior to Gateway filling its oppositions. Gateway MSJ Counterstatement of Facts (“Gateway MSJ CSF”), Doc. 131-1; VL CSF, Doc. 143-1; NH CSF, Doc. 144-1.
³⁶	Williams v. Pennsylvania State University, 2023 WL 6626789, at 4 (M.D. Pa. Oct. 11, 2023) (quoting Park v. Veasie, 2011 WL 1831708, at 3 (M.D. Pa. May 11, 2011); Hartshorn v. Throop Borough, 2009 WL 761270, at *3 (M.D. Pa. Mar. 19, 2009)).
³⁷	Id. (quoting Park, 2011 WL 1831708, at 3; Pinegar v. Shinseki, 2009 WL 1324125, at 1 (M.D. Pa. May 12, 2009)).
³⁸	VL Opp. 23; NH Opp. 22; Gateway MSJ Reply 13.
³⁹	E.g., VL Br. 40-41, 54-55, 69; NH Br. 6-7, 11-12, 27-29, 32-33, 38.
⁴⁰	VanIngen Report, Doc. 143-2.
⁴¹	In re Sorin 3T Heater-Cooler Sys. Prod. Liab. Litig., 2021 WL 8016522 (M.D. Pa. July 19, 2021) (collecting cases).
⁴²	Padillas v. Stork-Gamco, Inc., 186 F.3d 412, 417 (3d Cir. 1999) (quoting In re Paoli Railroad Yard PCB Litig., 916 F.2d 829, 854 (3d Cir. 1990)).
⁴³	Gateway MSJ Reply 13 n.5.
⁴⁴	M.S. by & through Hall v. Susquehanna Twp. Sch. Dist., 969 F.3d 120, 129 (3d Cir. 2020).
⁴⁵	See, e.g., VL Br. 40 (Allen’s expert, Dillard, opining that Gateway “functioned as the motor carrier in this specific transportation cycle”).
⁴⁶	Due to the nature of the parties’ statements of facts, the Court is presented with six different statements which significantly overlap with one another. The Court will rely on the parties’ statements as to Gateway’s Motion in this section, as Gateway’s Motion encompasses all of the claims against it.
⁴⁷	Gateway MSJ SMF ¶¶ 1, 2; Gateway MSJ CSF ¶¶ 8-10. Allen frames this first collision as “a dear abruptly dash[ing] out into the road, causing [Darlene] to bring her vehicle to a complete stop.” Id. ¶ 9.
⁴⁸	Gateway MSJ SMF ¶ 2, 47; Gateway MSJ CSF ¶ 9.
⁴⁹	Gateway MSJ SMF ¶ 3; Gateway MSJ CSF ¶¶ 4, 7.
⁵⁰	Gateway MSJ SMF ¶¶ 3, 4; Gateway MSJ CSF ¶¶ 8, 11.
⁵¹	Gateway MSJ SMF ¶¶ 3, 26, 48-54; Gateway MSJ CSF ¶¶ 1-2.
⁵²	Gateway MSJ SMF ¶¶ 48-54.
⁵³	Gateway MSJ Br. 19.
⁵⁴	Allen MSJ Opp. 67.
⁵⁵	Id. (citing Warner Dep., Gateway MSJ Pl. Ex. V., Doc. 131-22 at 97:12-102:19).
⁵⁶	Id. 68 (citing Lacey Report, Gateway MSJ Pl. Ex. T, Doc. 131-20, at 13-14).
⁵⁷	Warner Dep. 97:12-102:19.
⁵⁸	Lacey Report 14.
⁵⁹	Nov. 6, 2023 Ord., Doc. 154.
⁶⁰	Allen Supp. Br. 1-2.
⁶¹	See generally id.
⁶²	May 4, 2023 Ord., Doc. 128.
⁶³	Fed. R. Civ. P. 23(a)(2)(D).
⁶⁴	Fed. R. Civ. P. 37(c)(1).
⁶⁵	Nicholas v. Pennsylvania State University, 227 F.3d 133, 148 (3d Cir. 2000).
⁶⁶	Gateway Supp. Br. 11 n.5.
⁶⁷	See Aug. 23, 2023 Ord., Doc. 140 (extending briefing deadlines in response to Allen’s request to depose Gateway’s expert witness).
⁶⁸	Ciotola v. Star Trans. & Trucking, LLC, 481 F. Supp. 3d 375, 390 (M.D. Pa. 2020).
⁶⁹	Id. (collecting cases).
⁷⁰	Id. (quoting Adames v. May Furniture, 2019 WL 8937042, at *7 (M.D. Pa. Nov. 26, 2019)).
⁷¹	Id. (quoting Adames, 2019 WL 8937042, at *7).
⁷²	See VL Br. Section IV.A.1. (discussing only factors 1 through 7).
⁷³	Id. at 15.
⁷⁴	VL Br. 27-28.
⁷⁵	Id.
⁷⁶	Red Line Exp. Co. v. W.C.A.B. (Price), 588 A.2d 90, 96 (Pa. Cmwlth. 1991).
⁷⁷	Foxway Ans. to Am. Compl., Doc. 53 ¶¶ 73-74.
⁷⁸	VL Br. 43-45.
⁷⁹	Foxway Ans. to Am. Compl. ¶¶ 73-74.
⁸⁰	Ciotola, 481 F. Supp. 3d at 392.
⁸¹	Gateway MSJ Br. 28.
⁸²	Gateway MSJ Opp. Section IV.A.1.
⁸³	Gateway MSJ Opp. 31.
⁸⁴	Ciotola, 481 F. Supp. 3d at 392 (quoting Louis M. Marson Jr., Inc. v. Alliance Shippers, Inc., 438 F. Supp. 3d 326, 331 (E.D. Pa. 2020) (additional citations omitted)).
⁸⁵	Id. (quoting Louis M. Marson, Jr., Inc., 438 F. Supp. 3d at 331; Hewlett-Packard Co. v. Brother’s Trucking Enters., Inc., 373 F. Supp. 2d 1349, 1352 (S.D. Fla. 2005)).
⁸⁶	Tryg Ins. v. C.H. Robinson Worldwide, Inc., 767 F. App’x 284, 287 (3d Cir. 2019) (citing Essex Ins. Co. v. Barrett Moving & Storage, Inc., 885 F.3d 1292, 1301 (11th Cir. 2018)).
⁸⁷	Ortiz v. Ben Strong Trucking, Inc., 624 F. Supp. 3d 567, 580 (D. Md. 2022) (citing Tryg Ins. v. C.H. Robinson Worldwide, Inc., 2017 WL 5725057, at 6–7 (D.N.J. Nov. 28, 2017) aff’d*, 767 F. App’x 284 (3rd Cir. 2019)).
⁸⁸	Ciotola, 481 F. Supp. 3d at 392 (citing Louis M. Marson, Jr., Inc., 438 F. Supp. 3d at 331).
⁸⁹	Doc. 118-14 at GFS_0017-18.
⁹⁰	Tempel 30(b)(6) Dep., Doc. 118-7 at 42:7-8; accord 119:25-120:15.
⁹¹	Id. 119:25-120:15.
⁹²	VL Br. 41. In another example of the perils of relying on excess pages, Allen copies the same page-long block quote from Dillard’s report twice in the same section of his brief. Id. at 54-55.
⁹³	Id.
⁹⁴	Id. at 43-45.
⁹⁵	Foxway Ans. to Am. Compl. ¶¶ 73-74.
⁹⁶	VL Br. at 45.
⁹⁷	Tempel 30(b)(6) Dep., Doc. 118-6, 78:12-79:25.
⁹⁸	VL Br. 46.
⁹⁹	Id. (quoting Gateway 30(b)(6) Dep., Doc. 118-5, at 28:4-12).
¹⁰⁰	Doc. 118-14 at GFS_0017-18.
¹⁰¹	Broker, Oxford English Dictionary Online Ed. (accessed Nov. 29, 2023); see also 49 U.S.C. § 13102(2) (defining broker as “a person, other than a motor carrier or an employee or agent of a motor carrier, that as a principal or agent sells, offers for sale, negotiates for, or holds itself out by solicitation, advertisement, or otherwise as selling, providing, or arranging for, transportation by motor carrier for compensation”)
¹⁰²	Doc. 118-14 at GFS_0017-18
¹⁰³	See Delta Stone Prod. v. Xpertfreight, 304 F. Supp. 3d 1119 (D. Utah 2018) (citing Chubb Group of Ins. Co. v. H.A. Transp. Sys., Inc., 243 F.Supp.2d 1064, 1070 (C.D. Cal. 2002)) (invoices and bills of lading prepared by third parties that identify defendant as “carrier” insufficient to create material fact at summary judgment). But see Tryg, F. App’x at 288 (affirming denial of summary judgment and rejecting argument by purported broker that its history with shipper established that defendant was a broker rather than a carrier in the absence of supporting evidence).
¹⁰⁴	See Minsa Corp. v. Almac Sys. Transp., Inc., 2011 WL 12907655, at *5 (N.D. Tex. June 10, 2011) (discussing process in which carrier will ordinarily invoice the broker in case where broker did not remit payment and carrier sought payment from shipper directly).
¹⁰⁵	Gray v. York Newspapers, Inc., 957 F.2d 1070, 1078 (3d Cir. 1992) (quoting Anderson, 477 U.S. at 249–50).
¹⁰⁶	But cf. Tryg, F. App’x at 288; Contessa Premium Foods, Inc. v. CST Lines, Inc., 2011 WL 3648388, at *4 (C.D. Cal. Aug. 18, 2011) (observing that how the purported broker held itself out to the shipper is determinative).
¹⁰⁷	But cf. Ciotola, 481 F. Supp. 3d at 393.
¹⁰⁸	But cf. VL Br. 62 (and authorities cited therein).
¹⁰⁹	The Court accordingly need not address the parties’ arguments regarding whether Allen’s release of Foxway and Foxway’s employees and agents bars any recovery for derivative vicarious liability claims.
¹¹⁰	Adames, 2019 WL 8937042, at *8 (collecting cases).
¹¹¹	Id. (quoting Belmont v. MB Inv. Partners, Inc., 708 F.3d 470, 490 (3d Cir. 2013)).
¹¹²	Phillips v. Lock, 86 A.3d 906, 913 (Pa. Super. 2014).
¹¹³	NH Br. 38.
¹¹⁴	Id.
¹¹⁵	Gateway MSJ Br. 41.
¹¹⁶	Id. at 42.
¹¹⁷	Id.
¹¹⁸	Gateway MSJ Opp. 62.
¹¹⁹	NH Opp. Section V.G.6.
¹²⁰	Ciotola, 481 F. Supp. 3d at 387 (quoting Beavers v. West Penn Power Co., 436 F.2d 869, 873 (3d Cir. 1971)).
¹²¹	Id. (citing Beavers, 436 F.2d at 873; Friedman v. Wilson Freight Forwarding Co., 181 F. Supp. 327, 329 (W.D. Pa. 1960)).
¹²²	Gateway MSJ Br. 44.
¹²³	Gateway MSJ Opp. 75.
¹²⁴	The Court does not anticipate that the parties will need more than the 5,000 words provided for by Local Rule 7.8.

End of Document

Nilles v. DS1 Logistics, Inc., et al

United States District Court, N.D. Indiana, Hammond Division.

EMILY NILLES, as Special Administratrix of the Estate of Steve D. Nilles, deceased, Plaintiff,

DS1 LOGISTICS, INC., THOMAS E. WEBB, STARLINE SOLUTIONS, INC., and C.H. ROBINSON WORLDWIDE, INC., Defendants.

CAUSE NO.: 2:22-CV-54-TLS-JPK

12/18/2023

JUDGE THERESA L. SPRINGMANN, UNITED STATES DISTRICT COURT

OPINION AND ORDER

*1 This matter arises out of a motor vehicle collision between Thomas E. Webb, who was operating a semi-tractor–trailer for DS1 Logistics, Inc. (DS1), and Steven D. Nilles, who was driving a motorcycle. Amazon Fulfillment Services, Inc. (Amazon) contracted with C.H. Robinson Worldwide, Inc. (CHRW) for transportation services, and CHRW subsequently brokered the freight shipment at issue to DS1. Webb was operating the semi-tractor–trailer for DS1 pursuant to the contract between CHRW and DS1 at the time of the collision that resulted in Nilles’ death. The Plaintiff alleges that CHRW is responsible for the Plaintiff’s damages by virtue of CHRW’s contract with Amazon, which the Plaintiff alleges makes CHRW vicariously liable for Webb’s negligence. Now before the Court is CHRW’s Motion to Dismiss Plaintiff’s Third Amended Complaint Pursuant to Federal Rule of Civil Procedure 12(b)(6) [ECF No. 71], which is fully briefed. For the reasons below, the Court GRANTS the motion.

LEGAL STANDARD

“A motion to dismiss pursuant to Federal Rule of Civil Procedure 12(b)(6) challenges the viability of a complaint by arguing that it fails to state a claim upon which relief may be granted.” Camasta v. Jos. A. Bank Clothiers, Inc., 761 F.3d 732, 736 (7th Cir. 2014) (citing Fed. R. Civ. P. 12(b)(6); Gen. Elec. Cap. Corp. v. Lease Resol. Corp., 128 F.3d 1074, 1080 (7th Cir. 1997)). When reviewing a complaint attacked by a Rule 12(b)(6) motion, a court construes the complaint in the light most favorable to the non-moving party, accepts the factual allegations as true, and draws all inferences in the non-moving party’s favor. Bell v. City of Chicago, 835 F.3d 736, 738 (7th Cir. 2016). “Factual allegations must be enough to raise a right to relief above the speculative level…on the assumption that all the allegations in the complaint are true (even if doubtful in fact).” Bell Atl. Corp. v. Twombly, 550 U.S. 544, 555 (2007). “A claim has facial plausibility when the plaintiff pleads factual content that allows the court to draw the reasonable inference that the defendant is liable for the misconduct alleged.” Ashcroft v. Iqbal, 556 U.S. 662, 678 (2009) (citing Twombly, 550 U.S. at 556). In reviewing a motion to dismiss, a court considers “the complaint itself” as well as “documents attached to the complaint, documents that are critical to the complaint and referred to in it, and information that is subject to proper judicial notice.” Phillips v. Prudential Ins. Co. of Am., 714 F.3d 1017, 1019–20 (7th Cir. 2013) (quoting Geinosky v. City of Chicago, 675 F.3d 743, 745 n.1 (7th Cir. 2012)). Here, the Court considers the contract between CHRW and DS1, which CHRW attached to its motion to dismiss, as well as the contract between Amazon and CHRW, which the Plaintiff attached to her response brief. Both contracts are critical to and referred to in the Third Amended Complaint.

PROCEDURAL AND FACTUAL BACKGROUND

The Plaintiff filed her Complaint [ECF No. 4] in the Lake County, Indiana, Superior Court on January 31, 2022, against DS1 and Thomas E. Webb, and the case was removed to this Court on March 8, 2022. ECF No. 1. The Plaintiff filed an Amended Complaint [ECF No. 27] on January 11, 2023, adding Starline Logistics, Inc. and Starline Logistics, LLC as defendants; a Second Amended Complaint [ECF No. 36] on February 6, 2023, dropping the new defendants but adding Starline Solutions, Inc. as a defendant; and a Third Amended Complaint [ECF No. 59] on June 8, 2023, adding CHRW as a defendant. The following facts relevant to the Plaintiff’s claim against CHRW are taken from the Third Amended Complaint, the contract between Amazon and CHRW, and the contract between CHRW and DS1.

*2 At all relevant times, DS1 was an interstate motor carrier, and Webb was a truck driver operating DS1’s semi-tractor–trailer under DS1’s authority and logo. ECF No. 59, Ct. I, ¶¶ 1, 3, 4. CHRW agreed to provide transportation services to Amazon, and DS1 agreed to perform transportation and delivery services for CHRW. Id. Ct. II, ¶¶ 4, 6. On September 17, 2021, Webb was operating DS1’s semi-tractor–trailer to transport a shipment pursuant to the agreements when he turned left into Nilles, who was traveling by motorcycle, causing the accident that resulted in Nilles’ death. Id. Ct. I, ¶¶ 4, 6, 10, 13–15, Ct. II, ¶¶ 4–6.

The written agreement between Amazon and CHRW (the Amazon contract) provides that CHRW would arrange for transportation and delivery “Services” to be provided to Amazon. ECF No. 74-1, at 1. “Services” are defined to include “receiving, loading, storing, transporting, unloading and related transportation services.” Id. at 11. Section 4, titled “Representations and Warranties,” provides:

[CHRW] represents and warrants that it and its affiliates will, and that it shall contractually require subcontractors engaged by it to:

(a) perform the Services in a professional, competent and workmanlike manner in accordance with the level of professional care customarily observed by companies rendering similar services on a nationwide basis for Fortune 500 companies;

(b) meet, at a minimum, the Performance Standards;

(c) not violate or infringe any third party’s right in proprietary or confidential information in performing the Services;

(d) comply with all international and United States federal, state and local laws, rules, regulations and orders pertaining to the Services;

(e) hold, and fully comply with, all licenses, permits and approvals required by international and United States federal, state and local authorities to perform the Services;

(f) not be subject to any restriction, penalty, agreement, commitment, law, rule, regulation or order which is violated by its execution and delivery of this Agreement and performance of its obligations under this Agreement;

(g) will promptly notify Amazon of any accident, incident, or event which impairs the safety of, delays delivery of shipments, and also agrees to use reasonable care and due diligence in the protection of the goods or shipments; and

(h) have sufficient equipment (following reasonable advance notice), personnel and resources available to handle all Amazon capacity requirements.

Id. at 3–4 (emphasis added).

Section 10 of the Amazon contract is titled “Personnel; Independent Contractors.” Id. at 7. Section 10.1, titled “Project Assignments,” provides in relevant part:

All personnel furnished by [CHRW] to provide Services are either employees of [CHRW] or independent subcontractors of [CHRW] and are not employees, agents or subconsultants of Amazon….[CHRW] shall engage subcontracted carriers that will have exclusive control over is personnel, its labor and employee relations and its policies relating to wages, hours, working conditions and other employment conditions. [CHRW] will engage subcontracted carriers that will have the exclusive right to hire, transfer, suspend, lay off, recall, promote, discipline, discharge and adjust grievances with its personnel.

Id. at 7 (emphasis added). Section 10.2, titled “Subcontractors,” provides:

Notwithstanding the existence or terms of any subcontract, [CHRW] will remain responsible for the full performance of the Services. The terms and conditions of this Agreement are binding upon [CHRW’s] employees, and affiliates. [CHRW] (a) will ensure that such personnel comply with this Agreement, and (b) will be responsible for all acts, omissions, negligence and misconduct of such personnel. No bill of lading, or other document of any contracted carrier will amend or supersede the terms and conditions of this Agreement.

*3 Id. (emphasis added). Similarly, Section 11.1, titled “Assignment,” provides, in relevant part:

To the extent [CHRW] uses affiliates, subcontractors, or other third parties to perform its obligations under this Agreement, [CHRW] will cause and ensure that any such affiliates, subcontractors, or other third parties will comply with the terms of this Agreement. Notwithstanding the existence or terms of any subcontract, [CHRW] will remain responsible for the full performance of the Services.

Id.

Under the section titled “Performance Standards,” CHRW was responsible for, among other things, on-time delivery performance, scheduling deliveries, on-time pickup performance, and scheduling and attending at least monthly meetings with Amazon regarding statistical reports on its performance of the Agreement, including issues of transit time variability, shipment integrity, and loss and damage. Id. at 11–12. CHRW was also responsible for providing real time reporting, shipping data, and weekly management reports to Amazon. Id. at 12–13.

The written agreement between CHRW and DS1 (the DS1 contract) provides that CHRW is a federally registered property broker engaging DS1 to haul freight as a motor carrier. Def. Ex. A at 2, ECF No. 72-1. In Section 7, titled “Drivers and Equipment,” the DS1 contract provides that “[DS1] shall ensure that its drivers are properly trained and licensed, and are competent and capable of safely handling and transporting [CHRW’s] shipments.” Id. at 5. In Section 9, titled “Compliance with Laws,” the contract provides that DS1 is “solely responsible for any acts, omissions, and/or violations by [DS1], its employees, contractors or agents.” Id. at 6. Finally, Section 12, titled “Independent Contractor,” provides that “[DS1] is an independent contractor and shall exercise exclusive control, supervision, and direction over (i) the manner in which transportation services are provided; (ii) the persons engaged in providing transportation services; and (iii) the equipment selected and used to provide transportation services.” Id. at 8.

Count II of the Third Amended Complaint is brought against CHRW, alleging that CHRW is vicariously liable for the negligence of DS1 and Webb and makes the following allegations. ECF No. 59, Ct. II, ¶¶ 2, 14.¹ Webb was working for the “pecuniary benefit” of DS1 and CHRW, DS1 agreed to perform transportation and delivery services for CHRW, and Webb, operating the semi-tractor–trailer under DS1’s motor carrier authority, was in the performance of transportation and delivery services for the “mutual benefit” of DS1 and CHRW at the time of the incident. Id. Ct. II, ¶¶ 2, 4, 5. CHRW agreed to provide transportation and delivery services to Amazon and was in the performance of those services at the time of the incident. Id. Ct. II, ¶ 6. CHRW was responsible for the full performance of the transportation and delivery services, which were being performed by CHRW, DS1, and Webb at the time of the incident. Id. Ct. II, ¶¶ 7, 9. Also, “CHRW was responsible for all acts, omissions, negligence, and misconduct of DS1 and Webb, while DS1 and Webb were in the performance of the transportation and delivery services.” Id. Ct. II, ¶ 8. Nilles’ death was “a direct and proximate result of Defendants’ negligence, willfulness, wantonness, and/or recklessness.” Id. Ct. II, ¶ 10. Finally, “Defendants, DS1 and Webb, were acting within the course and scope of their agency with CHRW, and in furtherance of CHRW’s business interests. CHRW is vicariously liable for the negligence of Defendants, DS1 and Webb.” Id. Ct. II, ¶ 14.

ANALYSIS

*4 The Plaintiff alleges that CHRW, by virtue of its contract with Amazon, is vicariously liable for the alleged negligence of DS1 and Webb during the delivery services that resulted in Steven Nilles’ death. The elements of a negligence claim under Indiana law are “(1) a duty owed to the plaintiff by the defendant, (2) a breach of the duty, and (3) an injury proximately caused by the breach of duty.” Yost v. Wabash Coll., 3 N.E.3d 509, 515 (Ind. 2014) (quoting Pfenning v. Lineman, 947 N.E.2d 392, 398 (Ind. 2011)).² “Absent a duty there can be no negligence or liability based upon the breach.”Goodwin v. Yeakle’s Sports Bar and Grill, Inc., 62 N.E.3d 384, 386 (Ind. 2016). Whether a duty exists is a question of law for the Court. Jeffords v. BP Prods. N. Am., Inc., 963 F.3d 658, 661 (7th Cir. 2020) (citing Byrd v. Blue Ridge Rural Elec. Coop., Inc., 356 U.S. 525, 537 (1958); Dunn v. Menard, Inc., 880 F.3d 899, 906 (7th Cir. 2018)).

CHRW moves to dismiss this state law negligence claim for failure to plead a valid duty under Indiana law. Specifically, CHRW argues that the Plaintiff has failed to plead an exception to Indiana’s long-standing general rule that a principal is not liable for the acts or omissions of an independent contractor. See Bagley v. Insight Commc’ns Co., 658 N.E.2d 584, 586 (Ind. 1995) (citing Prest-O-Lite Co. v. Skeel, 106 N.E. 365, 367 (1914); City of Logansport v. Dick, 70 Ind. 65, 78 (1880)); Ryan v. TCI Architects/Eng’rs/Contractors, Inc., 72 N.E.3d 908, 914 (Ind. 2017) (citing Bagley, 658 N.E.2d at 586). Indeed, there are five exceptions to the rule, and the Plaintiff responds that she is invoking the exception “where the principal is by law or contract charged with performing the specific duty.” Bagley, 658 N.E.2d at 586 (citing Perry v. N. Ind. Pub. Serv. Co., 433 N.E.2d 44, 47 (1982)).³ “The duties associated with these exceptions are considered nondelegable, and the principal is liable for negligence of the independent contractor because the responsibilities are deemed so important to the community that the principal should not be permitted to transfer those duties to another.” Gwinn v. Harry J. Kloeppel & Assocs., 9 N.E.3d 687, 691–92 (Ind. Ct. App. 2014) (quoting Beatty v. LaFountaine, 896 N.E.2d 16, 22 (Ind. Ct. App. 2008)). The exceptions apply to lawsuits brought by employees of the independent contractor as well as by third parties, such as the Plaintiff in this case. See id. at 693 (citing Bagley, 658 N.E.2d at 587–88).

The Plaintiff argues that the Third Amended Complaint pleads sufficient facts to support a plausible claim of vicarious liability against CHRW for the negligence of DS1 and Webb based on CHRW’s contract with Amazon. Vicarious liability “is a legal fiction by which a court can hold a party legally responsible for the negligence of another, not because the party did anything wrong but rather because of the party’s relationship to the wrongdoer.” Sword v. NKC Hosps., Inc., 714 N.E.2d 142, 147 (Ind. 1999). One of several legal theories under which a party may be held vicariously liable is the nondelegable duty doctrine discussed above. Id. (listing respondeat superior, apparent or ostensible agency, and agency by estoppel as other bases for vicarious liability). The Plaintiff reasons that CHRW’s contract with Amazon creates the nondelegable duty that results in CHRW’s vicarious liability for DS1 and Webb’s negligence. In other words, the Plaintiff is not alleging that CHRW did anything wrong but rather that CHRW is responsible for DS1’s and Webb’s negligence based on CHRW’s contract with Amazon.⁴

*5 The Indiana Supreme Court has explained that this exception requires the contract to impose a “specific duty” and to “affirmatively evince[ ] an intent to assume a duty of care.” Ryan, 72 N.E.3d at 913–14; see also Shiel Sexton Co. v. Towe, 154 N.E.3d 827, 834 (Ind. Ct. App. 2020) (“Courts are to infer a contractually assumed duty that contravenes the common law presumption that a contractor has no duty only if the language of the contract ‘affirmatively evinces an intent to assume a duty of care.’ ” (quoting Stumpf v. Hagerman Constr. Corp., 863 N.E.2d 871, 876 (Ind. Ct. App. 2007))). This exception “is not triggered merely because a contractor may have a right to inspect and test the work, approve of the work and/or employees of the general contractor[,] or require the contractor to follow company safety rules.” Shawnee Constr. & Eng’g, Inc. v. Stanley, 962 N.E.2d 76, 82 (Ind. Ct. App. 2011). Rather, the “contract must provide for a specific duty of care.” Id.; see Barrett v. Barry-Wehmiller Design Grp., Inc., No. 1:19-CV-4079, 2022 WL 2805341, at *2 (S.D. Ind. May 17, 2022) (“In determining whether a duty exists, the court examine[s] whether the general contractor’s contract ‘affirmatively evinces’ an intent to assume a duty of care to the plaintiff in relation to the hazards at issue.” (cleaned up)). In Ryan, the Indiana Supreme Court explained that, while precedent from the court of appeals in similar cases can be helpful in guiding a court, the issue is “best settled by a contract interpretation analysis.” 72 N.E.3d at 916.

Accordingly, the Court turns to CHRW’s contract with Amazon to determine whether its provisions imposed a specific duty of care on CHRW for the benefit of third-party motorists for the negligence of CHRW’s independent contractors.When construing a contract, the Court must “ascertain the intent of the parties at the time the contract was made, as disclosed by the language used to express the parties’ rights and duties.” Ryan, 72 N.E.3d at 914 (citing First Fed. Sav. Bank of Ind. v. Key Markets Inc., 559 N.E.2d 600, 603 (Ind. 1990)). The contract is considered “as a whole to determine if a party is charged with a duty of care,” and the court “accept[s] an interpretation of the contract that harmonizes all its provisions.” Id. (citing Kelly v. Smith, 611 N.E.2d 118, 121 (Ind. 1993)). “A contract should be construed so as to not render any words, phrases, or terms ineffective or meaningless.” Id. (citing State Farm Fire and Cas. Co. v. Riddell Nat’l Bank, 984 N.E.2d 655, 658 (Ind. Ct. App. 2013)). Courts may not add provisions not agreed upon by contracting parties. Lake Imaging, LLC v. Franciscan All., Inc., 182 N.E.3d 203, 211 (Ind. 2022).

The Plaintiff asserts that excerpts from two provisions of the contract create a nondelegable duty. First, the Plaintiff cites a portion of Section 10.2, titled “Subcontractors,” in which CHRW agreed to “remain responsible for the full performance of the Services,” which, as she points out, include receiving, loading, storing, transporting, unloading and related transportation services. The Plaintiff also cites a portion of Section 4(a), titled “Representations and Warranties,” in which CHRW agreed to perform the “Services” in a professional, competent, and workmanlike manner and to comply with all federal, state, and local laws, rules, and regulations. The Plaintiff then reasons that “because CHRW was contractually charged with performing a specific duty, i.e. performance of the Services under the Agreement with reasonable care and in compliance with all applicable law, rules, and regulations, this was a nondelegable duty that subjects CHRW to liability for DS1 and Webb’s negligence.” ECF No. 74, p. 8.

While Section 4 and Section 10.2 address CHRW’s duty to Amazon to perform the Services, which consisted of services relating to the transportation of material goods, neither section refers to safety, third-party motorists, or personal injury accidents. Moreover, neither Section 10.2 nor any other provision of the Amazon contract provides that CHRW is responsible for the acts, omissions, negligence, and misconduct of independent contractors. Rather, Section 10.2 provides that CHRW will ensure that its own “employees and affiliates” comply with the agreement and that CHRW will be responsible “for all acts, omissions, negligence and misconduct of such personnel,” meaning CHRW’s own employees and affiliates. In contrast, Section 10.2 required CHRW to be responsible for ensuring contractually that its independent contractors were responsible for the acts and omissions of the independent contractor’s own employees and that its independent contractors would comply with the terms of the Amazon contract.⁵ And Section 10.1, which the Plaintiff does not address, provides that CHRW “shall engage subcontracted carriers that will have exclusive control over its personnel.”

*6 The only reference to “third parties” in the provisions of the Amazon contract cited by the Plaintiff is the reference in Section 4(c) to the infringement of proprietary and confidential information: “CHRW represents and warrants that it and its affiliates will, and that it shall contractually require subcontractors engaged by it to:…not violate or infringe any third party’s right in proprietary or confidential information in performing the Services….” Because the Amazon contract intended to create this specific limited duty to third parties, it is material that the contract does not contain language creating a specific duty to third party motorists or to any third party for the negligence of its subcontractors. See generally Jeffords, 963 F.3d at 663 (noting that the contract, taken as a whole, was written to protect property, not people).

Thus, based on settled contract interpretation analysis, there is no language in the Amazon contract that affirmatively evinces an intent by CHRW to assume a duty of care to third parties for the negligence of its subcontractors or independent contractors. The Plaintiff’s contention that CHRW “was…responsible for all of the acts, omissions, negligence and misconduct of DS1 and Webb during their performance of the transportation and delivery services,” ECF No. 74 at 3; see also ECF No. 59, Ct. II, ¶ 8, is not supported by her citation to Section 10.2 or the express terms of the Amazon contract.

The absence of any such language in the Amazon contract is underscored by a comparison of its terms with those of the contract at issue in Gwinn, 9 N.E.3d 687, the only nondelegable duty case cited by the Plaintiff. In Gwinn, the plaintiff was injured when a projection screen fell from the ceiling of the high school classroom where she was teaching. Id. at 688. The plaintiff filed a claim against the general contractor for the negligent installation of the screen, and the general contractor moved for summary judgment on the bases that a subcontractor had installed the screen and that the general contractor owed no duty to the plaintiff. Id. at 688–89. The trial court found no duty as a matter of law. Id. at 689. The appellate court reversed, holding that the general contractor was vicariously liable for the subcontractor’s negligence because the general contractor assumed a nondelegable duty to the plaintiff pursuant to the general contractor’s contract with the school corporation. Id. at 689, 691. The court of appeals found that the general contractor “assumed a duty to supervise the work of its subcontractors and the construction methods employed in a reasonably prudent manner and specifically assumed responsibility for the alleged negligent acts and omissions of its subcontractors.” Id. at 694. The court relied on contract language that made the general contractor “solely responsible for” and gave the general contractor “control over construction means, methods, techniques, sequences and procedures” for the work under the contract. Id. at 692. The court also relied on the contract provision that the general contractor “shall be responsible to the Owner for acts and omissions of…Subcontractors and their agents and employees.” Id.

In contrast, the Amazon contract does not give CHRW any control over the means and methods used by its subcontractors to provide the Services to Amazon. Nor does the Amazon contract contain any language making CHRW responsible for the acts and omissions of its subcontractors. Rather, as discussed above, the Amazon contract required only that CHRW “contractually require subcontractors” to be responsible for their own employees. See Section 4; see also Section 10. Although this comparison of language does not by itself decide this case, it is helpful in guiding the Court’s consideration of the contract terms. See Ryan, 72 N.E.3d at 916. The Plaintiff has identified no provision in CHRW’s contract with Amazon in which CHRW evinces an intent to be vicariously liable for the negligence of a third-party contract carrier, let alone to a class of third-party individuals, like Steven Nilles, for such negligence.

*7 As a separate argument to avoid dismissal of the claim against CHRW, the Plaintiff suggests that the Amazon contract contains provisions that evince an intent to create an agency relationship between CHRW and DS1 rather than the independent contractor relationship set forth in the DS1 contract. The Plaintiff cites general legal principles that, notwithstanding an “independent contractor” label, a contract may contain provisions evidencing an agency relationship and that whether one is an employee or an independent contractor is a question for the trier of fact. See Benante v. United Pac. Life Ins. Co., 659 N.E.2d 545, 548 (Ind. 1995). However, the Plaintiff’s argument that the Amazon contract evinces an intent to create an agency relationship between CHRW and DS1 is based solely on the same assertion made above that “CHRW expressly and unequivocally agreed to maintain a continuing obligation to be responsible for the acts and omissions of DS1 and Webb and further stated that no other document of any contracted carrier would amend or supersede these contract terms.” ECF No. 74, 10–11 (emphasis added). Again, the Amazon contract does not provide that CHRW is responsible for the acts and omissions of DS1 and Webb.

For these reasons, the Court finds as a matter of law that the Amazon contract does not affirmatively evince an intent on the part of CHRW to assume a specific duty of care to third parties, such as Steven Nilles, for the negligence of its independent contractors, such as DS1 and Webb. As a result, the Amazon contract does not constitute an exception to the general rule that a contractor is not liable for the negligence of an independent contractor. Because CHRW did not owe Steven Nilles a duty of care, the Court grants CHRW’s motion to dismiss the Plaintiff’s negligence claim against it. Because the Court finds that the Plaintiff has failed to allege a duty by CHRW, the Court does not reach CHRW’s alternate argument based on preemption.

CONCLUSION

Accordingly, the Court hereby GRANTS C.H. Robinson Worldwide, Inc.’s Motion to Dismiss Plaintiff’s Third Amended Complaint Pursuant to Federal Rule of Civil Procedure 12(b)(6) [ECF No. 71] and ORDERS that the Plaintiff’s claim against Defendant C.H. Robinson Worldwide, Inc. in Count II is DISMISSED with prejudice.

SO ORDERED on December 18, 2023.

s/ Theresa L. Springmann

JUDGE THERESA L. SPRINGMANN

UNITED STATES DISTRICT COURT

All Citations

Footnotes

Count I brought against Webb and DS1 and Count III brought against Starline Solutions, Inc. are not challenged on the instant motion.
As neither party argues otherwise, the Court applies Indiana substantive law to this contract dispute brought under the Court’s diversity jurisdiction. Jeffords v. BP Prods. N. Am., Inc., 963 F.3d 658, 661 (7th Cir. 2020) (citing Erie R.R. Co. v. Tompkins, 304 U.S. 64 (1938); Wood v. Mid-Valley Inc., 942 F.2d 425, 426–27 (7th Cir. 1991)).
The five exceptions to the general rule that a principal is not liable for the acts or omissions of an independent contractor are where (1) the contract requires the performance of intrinsically dangerous work, (2) the principal is by law or contract charged with performing the specific duty, (3) the act will create a nuisance, (4) the act to be performed will probably cause injury to others unless due precaution is taken, and (5) the act to be performed is illegal. Bagley, 658 N.E.2d at 586.
In its opening brief, CHRW cites and applies the three-part balancing test Indiana courts sometimes employ to determine whether a duty exists: “(1) the relationship between the parties; (2) the foreseeability of harm; and (3) public policy concerns.” Goodwin, 62 N.E.3d at 387 (citing Webb v. Jarvis, 575 N.E.2d 992, 995 (Ind. 1991)). However, the test is utilized only when “the element of duty has not already been declared or otherwise articulated.” Id. (quoting N. Ind. Pub. Serv. Co. v. Sharp, 790 N.E.2d 462, 465 (Ind. 2003)). As argued by the Plaintiff, the balancing test is unnecessary in this case because the Plaintiff has declared the element of duty based on vicarious liability through CHRW’s contract with Amazon. Cf. Richardson v. Rasulov, 1:19cv1549, 2021 WL 1429005, at *5–8 (S.D. Ind. Apr. 15, 2021) (applying the balancing test after finding that the complaint failed to allege the elements necessary for a claim of negligent selection or retention of a contractor).
Although not dispositive of whether the Plaintiff has sufficiently alleged CHRW’s nondelegable duty based on the Amazon contract, the Court notes that the Plaintiff does not allege that CHRW failed to contractually require DS1 to be responsible for all acts and omissions of DS1’s employees. In fact, the contract between CHRW and DS1 imposes those very obligations on DS1, providing in Section 9 that DS1 was “solely responsible for any acts, omissions, and/or violations by [DS1], its employees, contractors or agents.” The DS1 contract also provides in Section 12 that DS1, as an independent contractor, “shall exercise exclusive control, supervision, and direction over” the provision of the transportation services, the persons engaged in those services, and the equipment used.

End of Document