United States v. Arundel Corp.

814 F.2d 193
CourtCourt of Appeals for the Fifth Circuit
DecidedApril 10, 1987
DocketNo. 85-4948
StatusPublished
Cited by1 cases

This text of 814 F.2d 193 (United States v. Arundel Corp.) is published on Counsel Stack Legal Research, covering Court of Appeals for the Fifth Circuit primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
United States v. Arundel Corp., 814 F.2d 193 (5th Cir. 1987).

Opinion

EDITH H. JONES, Circuit Judge:

In this action under the Miller Act, 40 U.S.C. § 270a et seq., a general contractor, the electrical subcontractor, and their sureties appeal the district court’s findings of liability and dismissal of their cross-actions and counterclaims. We affirm in part, reverse in part, and reverse and remand in part.

I. BACKGROUND

Defendants The Arundel Corporation, Guy F. Atkinson Company, and Gordon H. Bell, Inc., d/b/a Dillingham Heavy Construction, Inc., joint venturers (hereinafter referred to as Arundel), contracted with the Army Corps of Engineers in 1978 for the construction of Lock B of the Tennessee-Tombigbee Waterway Project in Smith-ville, Mississippi. As general contractor, Arundel subsequently entered into a subcontract with defendant Lar Electric, Inc. (“Lar”), whereby Lar would perform certain electrical, instrumentation, control, and communications work on the project. Lar subsequently contracted with Control Systems, Inc. (“Control”) for the purchase of certain control and electrical power systems for the project.

On April 25, 1979, the Corps issued Change Order Request No. C-21 to Arundel, and the changes required by C-21 drastically affected the SCADA1 system to be installed by Control under the Lar subcontract. After a period of negotiations involving all the parties, the Corps issued the Notice to Proceed on C-21 to Arundel on November 5, 1980. Arundel delivered this notice to Lar some time later, and Lar delivered it to Control on May 3, 1981. Although the prime contract required the project to be “functionally operational” by January 18, 1982, the project was not accepted by the Corps as “functionally operational” until June 3, 1982, and the SCADA system and other work performed by Control were not substantially completed until August or September of 1982.

The Corps, acting pursuant to the prime contract, assessed liquidated damages of $70,720 against Arundel for untimely performance. In an attempt to recoup its losses, Arundel withheld from Lar $89,263 due under the subcontract, on the grounds that Lar was responsible for the project’s delay. Making similar allegations, Lar subsequently refused to pay Control $132,-747.22 on the supply contract.

In June 1984, Control filed this action against Lar for breach of contract, including Arundel and its sureties as defendants under Arundel’s Miller Act payment bond. Lar responded with a counterclaim against Control for breach of contract and a cross-action against Arundel for the $89,262.91 due under the subcontract. Arundel similarly filed cross-actions against Lar and a counterclaim against Control for approximately $200,000, representing Arundel’s delay damages on the project.2

After a bench trial, the district court entered judgment for Control against Lar and Arundel for $132,747.22 plus interest and costs, and assessed $25,000 in punitive damages against Lar. The court also awarded Lar the $89,262.91 due under the subcontract, and dismissed the remaining counterclaims and cross-actions. Arundel and Lar now appeal.

II. CLAIMS MADE BY ARUNDEL

A. Arundel’s Claim Against Lar

Arundel asserts claims against Lar for both the liquidated damages assessed by the Corps of Engineers and the increased overhead costs allegedly resulting from Lar’s delay. Further, Arundel sought indemnification from Lar in the event Control prevailed on its Miller Act claim [196]*196against Arundel. We analyze each of these claims in turn.

1. Liquidated Damages — The prime contract between Arundel and the Corps of Engineers required the project to be “functionally operational” by January 18, 1982, and further provided for liquidated delay damages of $520 per day. As noted above, the project was not deemed “functionally operational” by the Corps until June 3, 1982, and thus Arundel was assessed liquidated damages of $70,720. Arundel charges that as the delay was caused by Lar or Lar’s supplier Control, Lar is liable for this amount.

However, two crucial findings of the district court render Arundel’s contentions on this point meritless. First, the court found that the project could become “functionally operational” without the SCADA system, and thus any delay in the completion of the SCADA system had no effect on the date the project became “functionally operational.” Second, the court found that neither Lar nor Control did anything on the project after January 18, 1982 that would have affected the project’s “functionally operational” status. As there is evidence in the record to support these findings of fact, we cannot say that they are clearly erroneous. See Glass v. Petro-Tex Chemical Corp., 757 F.2d 1554, 1559 (5th Cir.1985). Once these findings of fact are accepted, the district court’s conclusion that neither Lar nor Control was responsible for the delay in the project’s becoming “functionally operational” must also stand, and thus Arundel cannot look to Lar for the liquidated damages assessed by the Corps.3

2. Overhead Damages — The district court also found that, as a result of the delay in completing the SCADA system, Arundel incurred increased overhead expenses. However, the court found that Arundel was the “real culprit” whose actions caused the damages from the delay, because Arundel did not request an extension of time from the Corps after issuance of the C-21 change order. Arundel challenges this conclusion on the grounds that the subcontract, as a matter of law, made Lar liable for all losses or damages caused by Lar’s untimely performance.

We agree. Under the subcontract,4 it was incumbent on Lar to request any extension of time needed for the C-21 changes affecting Lar’s responsibilities. See Sime Construction Co. v. Washington Public Power Supply System, 28 Wash. App. 10, 621 P.2d 1299 (1981). Whatever [197]*197rights Lar may have had to an extension of time were waived when Lar failed to make a timely written request for an extension, and when Lar signed the C-21 change order without reservation. The district court expressly found that Lar’s failure to give Control prompt notice to proceed with C-21 caused a delay in the completion of the SCADA system. Lar’s untimely performance falls within the scope of the subcontract’s delay damages provision.

While the district court found that Arundel had suffered increased overhead costs as a result of delay, it made no findings regarding the amount of such damages or delay attributable to Lar’s actions. We therefore remand these issues to the district court for further findings.

3. Indemnification — Arundel and its sureties also sought indemnification from Lar in the event that Control prevailed in its Miller Act claim. This portion of Arundel’s cross-action was summarily dismissed when the district court ruled that Lar was not in breach of the subcontract.5

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

Related

Cite This Page — Counsel Stack

Bluebook (online)
814 F.2d 193, Counsel Stack Legal Research, https://law.counselstack.com/opinion/united-states-v-arundel-corp-ca5-1987.