Detroit International Bridge Co. v. Federal Highway Administration

666 F. Supp. 2d 740, 2009 U.S. Dist. LEXIS 95035, 2009 WL 3271314
CourtDistrict Court, E.D. Michigan
DecidedOctober 13, 2009
DocketCase 09-13805
StatusPublished
Cited by4 cases

This text of 666 F. Supp. 2d 740 (Detroit International Bridge Co. v. Federal Highway Administration) is published on Counsel Stack Legal Research, covering District Court, E.D. Michigan primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Detroit International Bridge Co. v. Federal Highway Administration, 666 F. Supp. 2d 740, 2009 U.S. Dist. LEXIS 95035, 2009 WL 3271314 (E.D. Mich. 2009).

Opinion

OPINION AND ORDER

PATRICK J. DUGGAN, District Judge.

On September 25, 2009, the Detroit International Bridge Company (“DIBC”) filed a complaint seeking to enjoin the *742 Federal Highway Administration (“FHWA”) and its Michigan Administrator James Steele (“Steele”) from disclosing a 2007 inspection report regarding the Ambassador Bridge. 1 The complaint alleges that disclosure of the report would violate the Freedom of Information Act (“FOIA”), 5 U.S.C. § 552; violate the Critical Infrastructures Protection Act, 42 U.S.C. § 5195c; and amount to a breach of contract. Prior to the filing of the complaint, FHWA informed DIBC of its intent to disclose the report on September 28, 2009, in response to a FOIA request. Presently before the Court is DIBC’s Emergency Motion for a Temporary Restraining Order (“TRO”), filed on September 28, 2009. On September 29, 2009, defense counsel filed his response and the Court heard argument on the motion. On October 5, 2009, DIBC filed a supplemental brief in support of the emergency motion. For the reasons set forth below, the Court denies DIBC’s motion.

I. Factual and Procedural Background

The circumstances giving rise to this case begin with a contract entered into by DIBC, the private owner of the Ambassador Bridge, and the Michigan Department of Transportation (“MDOT”). That contract, the 2004 Gateway Agreement, requires DIBC to provide MDOT with annual inspection reports regarding the safety of the bridge. In anticipation of requests for the report from third parties, the contract provides:

The PARTIES agree that the bridge inspection reports contain sensitive security information, the public disclosure of which would be contrary to the public interest, and that, subject to the ultimate authority of the courts, the reports are exempt from public disclosure under the terms of the Freedom of Information Act. To assure that this exemption is recognized, the DIBC shall prominently stamp or print upon each page of the reports provided to [MDOT]: “CONFIDENTIAL REPORT — THIS REPORT IS EXEMPT AND NOT TO BE DISCLOSED UNDER THE FREEDOM OF INFORMATION ACT, IN ACCORDANCE WITH THE AGREEMENT BETWEEN THE BRIDGE COMPANY AND MDOT FOR THE GATEWAY PROJECT.” If a request is made for access to, or a copy of, a bridge inspection report, by any entity other than the Federal Highway Administration, [MDOT] will promptly notify the DIBC and will assert its exemption from disclosure under the Freedom of Information Act.

(Compl. Ex. A ¶ 24E.) Pursuant to this clause, the 2007 inspection report submitted by DIBC to MDOT contained a stamp on every page reflecting the all-caps language quoted above. Also pursuant to this clause, MDOT released the report to FHWA upon FHWA’s request.

Meanwhile, FHWA has its own procedures for dealing with requests for confidential information. According to federal regulation: “If a request is received for information that has been designated by the submitter as confidential commercial information, ... the submitter of such information will ... be notified expeditiously and asked to submit any written objections to release.” 49 C.F.R. § 7.17(a). Sometime after FHWA acquired the 2007 inspection report from MDOT, Congressman John Dingell requested that FHWA provide him with a copy of the most recent bridge inspection report for the Ambassador Bridge. In light of the stamp denoting the “confidential” nature of the report, FHWA notified MDOT and DIBC of Congressman Dingell’s request in March 2009 *743 and provided each entity an opportunity to submit objections to release of the report.

In the months that followed FHWA’s notification, MDOT deferred to DIBC’s explanations as to why the report qualifies as “confidential” and DIBC engaged in several rounds of correspondence with FHWA regarding its objections to release. In three separate letters to FHWA, DIBC expressed the following objections: (1) release of the report would violate the terms of the 2004 Gateway Agreement; and (2) disclosure of the report to FHWA by MDOT was in breach of the 2004 Gateway Agreement, requiring that FHWA return the “privileged” report to DIBC. DIBC also expressed concern about placing its explanation of the confidential nature of the report in writing out of fear that the explanation itself would compromise the confidential information DIBC seeks to protect.

In a letter dated September 14, 2009, FHWA informed DIBC that it had carefully considered DIBC’s concerns but nonetheless had decided that it would release the report to Congressman Dingell on September 28, 2009. In the letter, FHWA explained that it is not bound by the 2004 Gateway Agreement, that it did not consider MDOT’s disclosure of the report a breach of the 2004 Gateway Agreement, and that it is required to make its own determinations regarding disclosure under the FOIA. FHWA went on to explain that, having conducted its own analysis, it concluded that the report does not qualify as exempt from disclosure as confidential commercial or financial information under Exemption 4 of the FOIA. See 5 U.S.C. § 552(b)(4). Because the 2004 Gateway Agreement indicated that the report contains “sensitive security information,” FHWA’s letter went on to explain that FHWA did not consider release of the report a security risk. In conclusion, the September 14, 2009, letter noted that “[t]he decision to release a copy of the inspection report under FOIA is administratively final. The DIBC has the right to pursue appropriate judicial remedies.” (Defs.’ Resp. Ex. 1.) As noted above, DIBC pursued a judicial remedy by filing this lawsuit on September 25, 2009, and the motion for a TRO on September 28, 2009.

II. Venue

Before addressing the merits of DIBC’s claims and TRO motion, FHWA presents two challenges to the authority of the Court to hear the present lawsuit. In its first challenge, FHWA notes that DIBC’s complaint alleges that “[vjenue is proper in this Court under 28 U.S.C. § 1391(e) because [FHWA] is an agency of the United States that maintains an office within this District at 315 W Allegan St. # 211, Lansing, Michigan.” (Compl. ¶ 6.) The problem with this allegation is that Lansing, Michigan, which is located in Ingham County, is not within the Eastern District of Michigan. See 28 U.S.C. § 102(b).

Even so, the Court concludes that this is an appropriate venue for the case on other grounds. In an action where the United States is named as a defendant — as in this case — the lawsuit may be prosecuted where the plaintiff resides. 28 U.S.C. § 1402(a).

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

Related

John Doe 1 v. Sam Reed
697 F.3d 1231 (Ninth Circuit, 2012)
Smith v. State Farm Fire & Casualty Co.
737 F. Supp. 2d 702 (E.D. Michigan, 2010)

Cite This Page — Counsel Stack

Bluebook (online)
666 F. Supp. 2d 740, 2009 U.S. Dist. LEXIS 95035, 2009 WL 3271314, Counsel Stack Legal Research, https://law.counselstack.com/opinion/detroit-international-bridge-co-v-federal-highway-administration-mied-2009.