Laserfiche WebLink
The following is an itemized list of hazardous materials violations that have not been <br />addressed for FOOD EXPRESS INC as of April 29, 2022. <br />Open violations from February 24, 2022 inspection <br />Violation #5 - Failed to electronically submit hazardous materials inventory for all reportable materials on <br />site. <br />OBSERVATION: The Hazardous Materials Inventory forms contain obsolete categories. <br />REGULATION GUIDANCE :The Hazardous materials inventory information must be current and submitted as part <br />of the business plan. <br />CORRECTIVE ACTIONS: Immediately log into the California Environmental Reporting System (CERS) at <br />http://cers.calepa.ca.gov/, enter the correct or updated information, and submit to the EHD for approval. <br /> <br />Describe actions taken or will be taken to correct violation: <br />¨ This violation will be corrected by (date): ¨ This violation was corrected <br />¨ Supporting documents included <br />Violation #6 - Failed to electronically submit a site map with all required content. <br />OBSERVATION: The site map is incomplete. The following elements are missing/incorrect: Adjacent streets, <br />loading areas, internal roads, strom/ sewage drains and location of used oil and antifreeze. <br />REGULATION GUIDANCE: A site map shall contain a north orientation, loading areas, internal roads, adjacent <br />streets, storm and sewer drains, access and exit points, emergency shutoffs, evacuation staging areas, hazardous <br />material handling and storage areas, and emergency response equipment. <br /> If a site map element is not applicable for your facility then list it on the map and label as “NA". <br />CORRECTIVE ACTION: Immediately log into the California Environmental Reporting System (CERS) at <br />http://cers.calepa.ca.gov/, upload the correct or updated information, and submit to the EHD for approval. <br /> <br />Describe actions taken or will be taken to correct violation: <br />¨ This violation will be corrected by (date): ¨ This violation was corrected <br />¨ Supporting documents included <br />Page 1 of 4