d01-14

CPUC/ANF Environmental Monitoring Activities

Pacific Pipeline Construction Project

Aspen Environmental Group	Thursday, January 14, 1999

The following is a brief summary of the environmental monitoring activities that were completed between January 14, 1999 1:00 and 1:00 on January 15, 1999. This summary is based on reports directly received from the field and has not been edited. If you have any questions please contact (818) 597-3407. Please note the item number and the correction that should be made. This report is intended to serve as a communication document and as an instrument for quality control.

Segment 1 (Emidio Pump Station to Copco Road): Report for 14 January 1999: The focus of activity today was hydrotest and dewatering of the pipe. Dewatering and drying pigs were done for the section of pipe between Grapevine Station and Emidio Pump Station. Crews worked on stabilizing pressure on the hydrotest between the Warbler Skip and Grapevine Station. Dewatering of the southern most section of this segment occurred into Cuddy Creek. Backfill neared completion of their work on both sides of Grapevine Creek. Welding and x-ray progressed on the surplus pipe strung along Highway 166.

Segment 5 (Lynwood to Long Beach): Report for 1-14-99. Crews at the Edison station bore welded, x-rayed and coated two segments of pipe for the tie-in. In addition, crews excavated the receiving pit and slopped the sides to allow access to the pit. At Lomita Blvd, south of the Tosco refinery, crews continued welding segments of pipe for the Huntway lateral. Within Tosco, electrical crews worked on valve wiring while potholing continued south of the station for the Huntway tie-in. Segment 4B (Lynwood to El Segundo): Crews began a general clean up of the station site removing debris and construction waste. Further, crews began washing the brick face of the south wall while progress was made on the large roll down door to the station.

In the past 24 hours, 2 inspection event(s) were reported for 2 spread(s). Of these inspections, 0 were non-compliance event(s). Also 0 non-compliance resolution report(s) was resolved.