Estes Express Lines v. United States

108 Fed. Cl. 416, 2013 U.S. Claims LEXIS 10, 2013 WL 163765
CourtUnited States Court of Federal Claims
DecidedJanuary 15, 2013
Docket11-597C
StatusPublished
Cited by4 cases

This text of 108 Fed. Cl. 416 (Estes Express Lines v. United States) is published on Counsel Stack Legal Research, covering United States Court of Federal Claims primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Estes Express Lines v. United States, 108 Fed. Cl. 416, 2013 U.S. Claims LEXIS 10, 2013 WL 163765 (uscfc 2013).

Opinion

Contract case; Motion to dismiss under RCFC 12(b)(1) and 12(b)(6); Standard of review; Subcontractor lacked privity of contract with the United States; Contractor was not agent of Federal agency; 49 U.S.C. § 13706; Case dismissed for lack of jurisdiction.

OPINION

ALLEGRA, Judge.

This contract case is before the court on defendant’s motion to dismiss the complaint pursuant to RCFC 12(b)(1) or, alternatively, RCFC 12(b)(6). The plaintiff, Estes Express Lines, Inc. (Estes Express or plaintiff), an interstate motor carrier, claims that an arm of the United States Department of Defense breached contracts for transportation services by failing to pay it $147,645.33 in charges. Having carefully considered the parties’ claims, the court hereby GRANTS defendant’s motion under RCFC 12(b)(1), finding that there was no privity of contract between plaintiff and the United States upon which to predicate jurisdiction here.

I. BACKGROUND 1

The facts required here are simple and few.

Estes Express is a duly-licensed federal motor carrier, based in Richmond, Virginia. The Marine Corps Exchange (MCX) is a division of the United States Marine Corps Community Services (MCCS).

On October 31, 2007, MCCS awarded contract number H0107-D-0005 to Salem Logistics, Inc. (Salem) to coordinate its logistics and communicate with motor carriers to carry the products and goods of various shippers to MCX locations throughout the United States. Salem was contracted to provide freight management services with respect to, and in support of, MCCS’s and MCX’s inbound shipments (ie., to ensure that they were picked up at a seller’s location and delivered to an MCX location). The contract required Salem to “make payment to the commercial transportation carriers for services rendered to move products covered by [the contract], in accordance with terms and conditions negotiated between the two parties.” Salem was then to “invoice the MCCS/ MCX destinations for actual transportation expenses and the management fees ... for the shipped merchandise that was successfully delivered to the correct MCCS/MCX destination.” 2 The contract between MCCS and Salem also indicated that Salem “shall not represent itself to be an agent or representative of MR, MCCS or any other agency or instrumentality of the United States.” The contract went on to state that “[a]ny subcontractor used in connection with this contract is the agent of [Salem] and not the agent of MR and MCCS.”

Between June 2008 and February 2009, Salem arranged for Estes Express to carry various shipments for MCX. Though a written contract did not govern the relationship between Estes Express and Salem, the shipments moved pursuant to the former’s “common carrier tariff,” and each shipment was identified by: (i) a bill of lading; 3 (ii) a freight bill; and (iii) a delivery receipt.

*419 Under the bills of lading, various MCX locations were listed as “consignee,” while various third parties (the sellers) were listed as shipper. In some cases, goods were moved from a Navy Exchange (NEX) location to an MCX location, rather than from a third-party service provider to MCX. In the latter cases, government entities were listed as both consignee and shipper. The contract between Salem and MCCS specified that the charges were to be billed, pursuant to the shipping documents, to “Marine Corps Exchange C/O Salem Logistics” and the bills of lading reflected this.

Plaintiff filed, as exhibits to its opposition to defendant’s motion to dismiss, certain exemplar shipping documents. For example, a “Bill of Lading” dated October 30, 2008, contains the following information. The “Ship From” box indicates that the shipper is “MJ SOFFE COMPANY” and lists that company’s address. The “Ship To” box indicates that the destination for the shipment is “MCCS 05100 — NEW MAIN STORE” and lists the address for that location. In a box labeled “Third Party Freight Charges Bill To,” the bill of lading indicates “MARINE CORPS EXCHANGE C/O SALEM LOGISTICS” and provides Salem’s address. The form contains other information about the items being shipped. At the bottom, the bill of lading is signed by the “Shipper” and by the “Carrier.” On this particular bill of lading, the individual that signed for the “Carrier” indicated that he was a representative of Estes Express. It is unclear on the face of the document which entity the individual who signed for “Shipper” represented.

With respect to the same shipment, plaintiff also included an “Original Freight Bill” and a “Delivery Receipt,” both of which indicate that they are “Estes Express Lines” documents because they have the Estes Express logo in the upper-left corners. These documents, like the bill of lading, are dated October 30, 2008. The freight bill indicates that “MCCS 05100 — NEW MAIN STORE” is the “Consignee” and that “MJ SOFFE COMPANY” is the “Shipper.” The freight bill also indicates: “Bill Charges To ... MARINE CORPS EXCHANGE % SALEM LOGISTICS” and lists Salem’s address. Finally, the freight bill contains a listing of the charges associated with the shipment. The delivery receipt lists the same “Consignee” and “Shipper” as the freight bill and contains information about the items being shipped. Unlike the freight bill, the delivery receipt indicates: “Bill Charges To ... MARINE CORPS EXCHANGE” and contains Salem’s city, state, and zip code, but not its street address or, indeed, mention of Salem at all. The delivery receipt is signed by a representative of the MCX location to which the goods were delivered (and by some other unidentified individual).

Each shipment arranged by Salem to be shipped by Estes Express was accepted by the consignee — MCX—without exception, and no claims arising out of the carriage of the specified loads were made against Estes Express. Following the shipments, Estes Express invoiced “MCX, care of Salem” for payment of freight charges. However, Estes Express has not been paid on certain invoices by Salem, MCCS, MCX, NEX, or any other entity.

Estes Express invoiced Salem for freight charges with regard to shipments for MCX in the total principal amount of $66,283.68. When combined with a loss discount of $110,292.93 per the terms and conditions of Estes Express’ “common carrier tariff,” the total amount due to Estes Express was $176,576.61. 4 MCX subsequently paid Estes Express $28,931.28, representing monies owed for which MCX had not yet paid Salem, 5 leaving a total amount due of *420 $147,645.33. 6 MCX refuses to pay Estes Express any amount owed for which MCX claims it paid Salem.

On February 3, 2010, Estes Express filed suit against Salem and other defendants, including government entities, in the United States District Court for the Middle District of North Carolina. Complaint, Estes Express Lines v. Salem Logistics, Inc., No. 10-102 (M.D.N.C. Feb. 3, 2010). On July 8, 2011, the District Court entered an order transferring the ease to this court. Order, Estes Express Lines v.

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

Related

Rudolph and Sletten, Inc. v. United States
120 Fed. Cl. 137 (Federal Claims, 2015)
Estes Express Lines v. United States
739 F.3d 689 (Federal Circuit, 2014)

Cite This Page — Counsel Stack

Bluebook (online)
108 Fed. Cl. 416, 2013 U.S. Claims LEXIS 10, 2013 WL 163765, Counsel Stack Legal Research, https://law.counselstack.com/opinion/estes-express-lines-v-united-states-uscfc-2013.