My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
3 - The Bowery_PUBLIC COMMENT_RAMSEY
Clerk
>
Agenda Packets / Staff Reports
>
Planning Commission (2002-Present)
>
2020
>
05-11-20
>
3 - The Bowery_PUBLIC COMMENT_RAMSEY
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
11/9/2020 10:02:45 PM
Creation date
11/9/2020 10:00:03 PM
Metadata
Fields
Template:
PBA
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.
/
488
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
5.0 Environmental Analysis 5.6 Noise <br />Avion Project SEIR <br />Page 5.6-8 <br />Additionally, empirical data has shown that delays of as little as 5 milliseconds can minimize vibration <br />in very close blasting situations (10 to 25 feet) (Bender 2007). <br />Table 5.6-2 <br />Predicted Blasting Vibration Levels by Charge Weight <br />Distance to <br />Non-Rippable Rock <br />(feet) <br />Predicted Vibration Level by Charge Weight <br />(in/sec PPV) <br />12 lb. 10 lb. 8 lb. 4 lb. 2 lb. 1 lb. 0.5 lb. 0.25 lb. <br />10 130.93 113.16 94.66 54.37 31.23 17.93 10.30 5.92 <br />50 9.97 8.62 7.21 4.14 2.38 1.37 0.78 0.45 <br />100 3.29 2.84 2.38 1.37 0.78 0.45 0.26 0.15 <br />150 1.72 1.49 1.24 0.71 0.41 0.24 0.14 0.08 <br />175 – nearest <br />residence 1.34 1.16 0.97 0.56 0.32 0.18 0.11 0.06 <br />200 1.08 0.94 0.78 0.45 0.26 0.15 0.09 0.05 <br />in/sec = inches per second; PPV = peak particle velocity; lb. = pounds <br />NOTE: Bold numbers indicate an exceedance of 2.0 in/sec PPV, which would be considered an impact. <br /> <br />As shown in Table 5.6-2, the nearest receiver located 175 feet to the northeast of the proposed <br />blasting locations is not anticipated to be exposed to vibration levels in excess of 2.0 in/sec PPV. <br />Although a project-specific blasting plan and exact amount of explosive needed is not known at this <br />time, the project would comply with the County Fire Code and would implement all feasible <br />vibration reduction strategies, including conducting pre- and post-construction surveys of the <br />nearest residence to any blast. The project would also monitor blasting vibrations and overpressure <br />levels, the results of the monitoring would be used to reduce charge weights, increase timing <br />between charges, or other appropriate measures as required to reduce vibrations from blasting. <br />Furthermore, the proposed blasting activities would be subject to the following County Fire Code <br />(County of San Diego 2017) and City requirements: <br />1. Per Section 59.5.0404 of the City’s Noise Abatement and Control Ordinance, construction, <br />including blasting, shall be prohibited between the hours of 7:00 p.m. and 7:00 a.m., or on <br />Sundays, or on legal holidays as specified in Section 21.04 of the San Diego Municipal Code, <br />with exception of Columbus Day and Washington’s Birthday. <br />2. The blasting contractor shall obtain a permit from the Fire Chief of the City of San Diego per <br />the requirements of Section 53.01 of the Municipal Code. <br />3. Blasting activities would follow guidance provided in the General Blasting Management Plan <br />that would include an estimate of air blast overpressure and vibration levels of each shot at <br />the nearest structure. A preliminary General Blasting Management Plan is included as <br />Attachment 1. Blasting shall not commence until the City and Sherriff’s Department has <br />approved the General Blasting Management Plan. <br />4. Each blast shall be monitored and recorded with an air blast over-pressure monitor that is <br />located outside the nearest residence to the blast. <br />5. The City project engineer shall review the request for each blast to verify blasting only of <br />material that requires blasting.
The URL can be used to link to this page
Your browser does not support the video tag.