Fortress Credit Corp. v. Alarm One, Inc.

511 F. Supp. 2d 367, 2007 U.S. Dist. LEXIS 67878, 2007 WL 2668489
CourtDistrict Court, S.D. New York
DecidedSeptember 7, 2007
Docket07-CV-7590 (CM)(RLE)
StatusPublished
Cited by8 cases

This text of 511 F. Supp. 2d 367 (Fortress Credit Corp. v. Alarm One, Inc.) is published on Counsel Stack Legal Research, covering District Court, S.D. New York primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Fortress Credit Corp. v. Alarm One, Inc., 511 F. Supp. 2d 367, 2007 U.S. Dist. LEXIS 67878, 2007 WL 2668489 (S.D.N.Y. 2007).

Opinion

DECISION AND ORDER

McMAHON, District Judge.

Plaintiff Fortress Credit Corp. (“Fortress”) brings this action to foreclose upon its lien on certain assets of defendant Alarm One. Inc. (“Alarm One”). The action stems from a February 11, 2005 Credit Agreement (“Credit Agreement”), pursuant to which various lenders and Fortress provided Alarm One with credit facilities in the aggregate principal amount of approximately $48 million. In order to secure these credit facilities, Alarm One executed a February 11, 2005 Security Agreement (“Security Agreement”) that granted Fortress a “continuing first priority lien on and security interest in” substantially all of Alarm One’s assets.

Before the court is fortress’s application ex parte for an appointment of a receiver, fortress claims that such appointment is necessary because Alarm One is in default of the parties’ Credit Agreement and Fortress maintains a property interest in Alarm One’s assets by virtue of the Security Agreement. Fortress further argues that the Credit Agreement explicitly permits this court to appoint a receiver ex parte.

For the reasons stated below, the court declines to grant the application ex parte and directs Fortress to resubmit it by order to show cause on notice to defendant.

I. Background

A. The Credit Agreement and the Security Agreement

The parties entered into the Credit Agreement on February 11, 2005, under which various lenders and Fortress (in its capacity as agent for the lenders) provided Alarm One with “a Revolving Credit Facility in a principal amount not to exceed $20,000,000, a $17,500,000 Term Loan A Facility, and a $12,500,000 Term Loan B Facility.” (Affidavit of James K. Noble, III (“Noble Aff.”) ¶ 2.) In exchange for this credit. Alarm One assumed certain payment obligations.

That same day, the parties also signed the Security Agreement that granted Fortress a “continuing first priority lien on and security interest in” specified “Collateral subject only to permitted Liens.” (Security Agreement ¶ 2. attached as Ex. 8 to Noble Aff.)

The Security Agreement defines “Collateral” as

*369 all of [Alarm One’s] right, title and interest in ... the following ... property
(i) all now existing and hereafter acquired or arising Accounts, Goods, General Intangibles. Payment Intangibles, Deposit Accounts, Chattel Paper .... Documents, Instruments, Software, Investment Property, Letters of Credit, Letter of Credit Rights, Advices of Credit. Money, Commercial Tort Claims .... Equipment and Inventory. Fixtures and Supporting Obligations ...
(ii) to the extent ... not included in clause (i). each and every other item of personal property and fixtures ... including all licenses, contracts and agreements, and all collateral for the payment or performance of any contract or agreement ...
(iii) all present and future business records and information, including computer tapes and other storage media containing ... computer programs and software.....

(Id. ¶ l(b)(i)-(iii).)

The Credit Agreement establishes certain occurrences that constitute “Events of Default” (Credit Agreement §§ 9.1.1 thru 9.1.15. attached as Ex. 1 to Noble Aff.), as well as the consequences that flow from such defaults. (Id. §§ 9.2.1 thru 9.2.6,) Among these consequences, the Agreement states.

If an Event Default shall occur and be continuing, and whether or not [Fortress] shall have accelerated the maturity of Loans pursuant to any of the foregoing provisions of this Section 9.2, [Fortress] ... if owed any amount with respect to the Loans, may proceed to protect and enforce its rights by suit in equity, action at law and/or other appropriate proceeding ... including as permitted by applicable Law the obtaining of the ex parte appointment of a receiver

(Id. § 9.2.4.)

B. Alarm One’s Defaults

In support of its application, Fortress has submitted an extensive record including the affidavit of Mr. James Noble, Fortress’s Secretary, which details the occurrence of at least two “Events of Default” under the Credit Agreement.

First, “From October 31.2005 to December 21, 2005, Alarm One failed to maintain the ratio of Funded Debt to Consolidated Cash Flow from Operations of 6.0 to 1.0. Alarm One thereby failed to comply with Section 8.2.17 of the Credit Agreement.” (Noble Aff. ¶ 14(a).)

Second, “Alarm One failed to maintain the sum of Availability plus unrestricted cash at no less than $1,000,000 for the period ending October 31, 2005, thereby violating Section 8.2.19.” (Id. ¶ 14(b).)

Alarm One has acknowledged on four separate occasions that these two failures to fulfill its contractual duties constitute Events of Default that “occurred and are continuing.” (See December 21, 2005 Third Amendment to Credit Agreement and Forbearance Agreement ¶¶ B-C, attached as Ex. 4 to Noble Aff.; January 31, 2006 Fourth Amendment to Credit Agreement and Forbearance Agreement ¶¶ B-C, attached as Ex. 5 to Noble Aff.; March 31, 2006 Fifth Amendment to Credit Agreement and Forbearance Agreement ¶7^), attached as Ex. 6 to Noble Aff.; November 21, 2006 Limited Consent and Sixth Amendment to Credit Agreement ¶ D, attached as Ex. 7 to Noble Aff.)

Fortress provided Alarm One with written notice of its Events of Default in five separate letters dated January 27, March 1, May 4, June 15 and August 21, 2006. (See Noble Aff. Ex. 10.)

*370 • The January 27 letter notified Alarm One of the two Events of Default described above.
• The March 1 letter notified Alarm One of an additional event of Default (failure to comply with Section 6(c) of the Fourth Amendment and Forbearance Agreement by failing to complete the sale of the Additional California Accounts on or before February 28.2006: this failure triggered the Agreement’s increased Default interest Rate).
• The May 4 letter notified Alarm One that the parties’ Forbearance Agreement expired April 27, 2006, and expressly reserved Fortress’s rights under the Credit Agreement.
• The June 15 letter notified Alarm One of three additional Events of Default (failure to make interest payments due under the Default Interest Rate, failure to accurately calculate its Borrowing Base, and failure to deliver to Fortress updates to Schedule 6.1.29 of the Credit Agreement).

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

Related

Cite This Page — Counsel Stack

Bluebook (online)
511 F. Supp. 2d 367, 2007 U.S. Dist. LEXIS 67878, 2007 WL 2668489, Counsel Stack Legal Research, https://law.counselstack.com/opinion/fortress-credit-corp-v-alarm-one-inc-nysd-2007.