My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Agenda Packets - 2018/03/05
MoundsView
>
Commissions
>
City Council
>
Agenda Packets
>
2010-2019
>
2018
>
Agenda Packets - 2018/03/05
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/28/2025 4:46:46 PM
Creation date
6/13/2018 11:20:48 AM
Metadata
Fields
Template:
MV Commission Documents
Commission Name
City Council
Commission Doc Type
Agenda Packets
MEETINGDATE
3/5/2018
Supplemental fields
City Council Document Type
City Council Packets
Date
3/5/2018
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
115
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
Show annotations
View images
View plain text
ARTICLE IX <br />Events of Default <br />Section 9.1. Events of Default Defined. "Event of Default" means any one or more of the <br />following events, after the non -defaulting party provides sixty (60) days' written notice to the defaulting <br />party of the event, but only if the event has not been cured within said sixty (60) days after written notice <br />of default has been tendered or, if the event is incurable within sixty (60) days, the defaulting party does <br />not, within the sixty (60) day period, provide assurances reasonably satisfactory to the non -defaulting <br />party that the event will be cured as soon as reasonably possible: <br />(a) The Developer or the Authority fails to observe or perform any covenant, condition, <br />obligation, or agreement on its part to be observed or performed under this Agreement; <br />(b) The Developer: <br />(i) files any petition in bankruptcy or for any reorganization, arrangement, <br />composition, readjustment, liquidation, dissolution, or similar relief under the United States <br />Bankruptcy Act or under any similar federal or State law; <br />(ii) except as allowed by Section 3.5(c) hereof, makes an assignment for the benefit <br />of its creditors; <br />(iii) admits in writing its inability to pay its debts generally as they become due; or <br />(iv) is adjudicated as bankrupt or insolvent. <br />Section 9.2. Remedies on Default. Whenever any Event of Default referred to in Section 9.1 <br />hereof occurs, the non -defaulting party may exercise its rights under this Section 9.2 only if the Event of <br />Default has not been cured within sixty (60) days of the non -defaulting party's tender of a notice of <br />default or, if the Event of Default is incurable within sixty (60) days, the defaulting party does not provide <br />assurances reasonably satisfactory to the non -defaulting party that the Event of Default will be cured as <br />soon as reasonably possible: <br />(a) Suspend its performance under the Agreement until it receives assurances that the <br />defaulting party will cure its default and continue its performance under the Agreement. <br />(b) Cancel and rescind or terminate the Agreement. <br />(c) Upon a default by the Developer, the Authority may suspend payments under the TIF <br />Note or terminate the TIF Note and the TIF District, subject to the provisions of Section 9.3 hereof. <br />(d) Upon failure by Developer to timely commence or complete construction of the <br />Minimum Improvements in accordance with Section 4.3 hereof, the Authority may terminate this <br />Agreement; provided, however, that notwithstanding anything herein to the contrary, the Authority <br />acknowledges and agrees that it shall have no remedy of specific performance with regard to the <br />Redeveloper's obligation to commence the construction of the Minimum Improvements. <br />20 <br />51691 rv1 JAE MU205-47 <br />
The URL can be used to link to this page
Your browser does not support the video tag.