My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
3800 RIVERFRONT BLVD 2025-07-23
>
Address Records
>
RIVERFRONT BLVD
>
3800
>
3800 RIVERFRONT BLVD 2025-07-23
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
7/23/2025 3:49:01 PM
Creation date
6/18/2025 10:18:28 AM
Metadata
Fields
Template:
Address Document
Street Name
RIVERFRONT BLVD
Street Number
3800
Imported From Microfiche
No
Jump to thumbnail
< previous set
next set >
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
1102
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).
View images
View plain text
1 <br />1 <br />1 <br />1 <br />1 <br />1 <br />�1 <br />Consent Decree Exhibit C <br />purpose of evaluating compliance with the Cleanup Action Plan and to inspect <br />records that are related to the Cleanup Action. <br />6.3.1 Development Management and Approvals <br />Both as the Site owner and as the local development approval authority, the City of Everett is <br />responsible to ensure development is consistent with the requirements of this CAP. <br />6.3.1.1 City Responsibilities for Development Management and Approval <br />The City will perform the following roles and responsibilities in managing potential future <br />development processes: <br />Property Sale or Lease. If the City enters into a purchase and sale or lease agreement <br />with any parties for the Site, the agreements will include requirements for <br />implementation of all CD and CAP requirements. Property agreements will clearly <br />define permitted use(s), and the split of responsibilities for implementation of <br />environmental requirements between the City and developers. The City will maintain <br />responsibility for all CAP and CD requirements unless the Purchaser or Lessee <br />specifically agrees to assure certain responsibilities, becomes a signatory to the CD, and <br />Ecology approves the changes. <br />City Site Manager. One point of contact will be defined within the City to track and <br />coordinate environmental compliance, permitting, development, construction, and <br />property management activities on the Site. This City Site Manager will ensure <br />compliance with environmental requirements, and will coordinate communications with <br />Ecology relative to Site status and activities. <br />Development Management and Oversight. The City will review and approve all <br />development activities proposed and conducted at the Site, to ensure compliance with <br />CAP requirements. Opportunities for Ecology review and comment will be provided at <br />key milestones in the review and approval process. <br />Compliance Monitoring Reporting. City will provide, and/or or ensure the <br />owner/developer provides timely, periodic reporting of results to Ecology for compliance <br />monitoring conducted in accordance with the CMCP. <br />Development Status and Inspection Reports. City will provide timely, periodic <br />reporting to Ecology detailing development activities, development status, permitting <br />status and development inspections. Reporting will accompany compliance monitoring <br />reports to Ecology. <br />6.3.1.2 City and Ecology Responsibilities in Development Approvals <br />City and Ecology responsibilities in the development review and approval process are defined in <br />Table 6-2. <br />Ecology and the City have defined the MTCA requirements that must be met by potential future <br />development on the Site. However, any potential development action proposed for the Site <br />must go through a standard review, approval and permitting process which involves many other <br />Agencies and regulatory requirements. Figure 6-3 depicts the relationship between the MTCA <br />FINAL - March 2001 <br />6-7 Everett Landfill Tire Fire Site <br />Cleanup Action Plan <br />1 <br />
The URL can be used to link to this page
Your browser does not support the video tag.