fish group 1: 10/14/03 10:54 through 11/01/03 10:52

5
Fish group 1: 10/14/03 10:54 through 11/01/03 10:52 Fish group 2 11/01/03 14:25 through 11/14/03 10:19 Fish group 3: 11/14/03 13:53 through 11/29/03 09:44 Fish group 4: 11/29/03 13:20 through 12/08/03 02:43 Fish group 5: 12/12/03 12:43 through 12/19/03 10:28 Fish group 6: 12/19/03 11:19 through 12/26/03 09:04 Fish group 7: 12/29/03 10:17 through 01/02/04 10:17 Fish group 8: 01/02/04 11:21 through 01/09/04 10:06 No fish mortality occurred during monitoring period. Six alarm events and two events of interest occurred. Pelican Point, Slocum Creek, Cherry Point Pelican Point, Slocum Creek, Cherry Point MCAS Summary Oct. 14, 2003 to Jan. 9, 2004 MCAS Summary Oct. 14, 2003 to Jan. 9, 2004 Hydrological Events Fish Response

Upload: howie

Post on 06-Feb-2016

42 views

Category:

Documents


0 download

DESCRIPTION

Pelican Point, Slocum Creek, Cherry Point MCAS Summary Oct. 14, 2003 to Jan. 9, 2004. Fish group 1: 10/14/03 10:54 through 11/01/03 10:52 Fish group 211/01/03 14:25 through 11/14/03 10:19 Fish group 3: 11/14/03 13:53 through 11/29/03 09:44 - PowerPoint PPT Presentation

TRANSCRIPT

Page 1: Fish group 1:  10/14/03 10:54 through 11/01/03 10:52

Fish group 1: 10/14/03 10:54 through 11/01/03 10:52Fish group 2 11/01/03 14:25 through 11/14/03 10:19Fish group 3: 11/14/03 13:53 through 11/29/03 09:44Fish group 4: 11/29/03 13:20 through 12/08/03 02:43Fish group 5: 12/12/03 12:43 through 12/19/03 10:28Fish group 6: 12/19/03 11:19 through 12/26/03 09:04Fish group 7: 12/29/03 10:17 through 01/02/04 10:17Fish group 8: 01/02/04 11:21 through 01/09/04 10:06 No fish mortality occurred during monitoring period.Six alarm events and two events of interest occurred.

Pelican Point, Slocum Creek, Cherry PointPelican Point, Slocum Creek, Cherry PointMCAS Summary Oct. 14, 2003 to Jan. 9, 2004MCAS Summary Oct. 14, 2003 to Jan. 9, 2004

Hydrological Events Fish Response

Page 2: Fish group 1:  10/14/03 10:54 through 11/01/03 10:52

Event 1 (10/22/03 23:38 through 10/24/03 12:07): An alarm event was caused by decreasing average depth from increased conductivity. The variable gain amplification did not adequately compensate for the increased conductivity due to fouling of the amplifier conductivity sensor.

Event 2 (11/13/03 21:34 through 11/14/03 0:49): An alarm event was caused primarily by decreased average fish ventilatory depth. The alarm event was at the beginning of a rapid conductivity increase (from 0.60 to 3.28 mS/cm).

Event 3 (11/20/03 12:08 through 11/20/03 12:23): This 15-minute response event was associated with maintenance activities on-site. Water quality (temperature, dissolved oxygen, pH, and conductivity) did not appear to be different than during periods prior to the alarm event.

Page 3: Fish group 1:  10/14/03 10:54 through 11/01/03 10:52

Event 6 (1/6/04 5:36 through 1/6/04 5:51): An alarm event lasting 15 minutes was caused by a decrease in dissolved oxygen, and increases in temperature and conductivity (the latter, from 4.98 mS/cm to 14.18 mS/cm in 2 hours). These environmental changes resulted in rapid increases in fish ventilation rate and cough rate, and a decrease in average depth.

Event 5 (12/02/03 1:20 through 12/07/03 15:43): Alarm events were caused by decreased average depth. A concomitant increase in conductivity did not occur during the alarm. Clogging/fouling of the variable gain conductivity probe was likely the cause of the event, given that average depth recovered during the next monitoring period following maintenance and calibration of the probe.

Event 4 (11/25/03 7:59 through 11/25/03 9:29): An alarm event was caused primarily by decreased average fish ventilatory depth. The event occurred at the beginning of a rapid conductivity increase (from 1.54 to 5.63 mS/cm). An increase in fish ventilation rate was also noted.

Page 4: Fish group 1:  10/14/03 10:54 through 11/01/03 10:52

Event 1 (10/22/03 23:38 through 10/24/03 12:07): An alarm event was caused by decreasing average depth resulting from increased conductivity. The variable gain amplification did not adequately compensate for the increased conductivity, due in part to fouling of the amplifier conductivity sensor.

Event 2 (11/13/03 21:34 through 11/14/03 0:49): An alarm event was caused primarily by decreased average fish ventilatory depth. The event occurred at the beginning of a rapid conductivity increase (from 0.60 to 3.28 mS/cm).

Event 3 (11/20/03 12:08 through 11/20/03 12:23): This response event lasted for 15 minutes, and was associated with maintenance activities on-site. Water quality (temperature, dissolved oxygen, pH, and conductivity) did not appear to be different from conditions during periods prior to the alarm event.

Page 5: Fish group 1:  10/14/03 10:54 through 11/01/03 10:52

Event 4 (11/25/03 7:59 through 11/25/03 9:29): An alarm event was caused primarily by decreased average fish ventilatory depth, and occurred at the beginning of a rapid conductivity increase (from 1.54 to 5.63 mS/cm). An increase was also noted in fish ventilation rate.

Event 5 (12/02/03 1:20 through 12/07/03 15:43): Alarm events were caused by decreased average depth. A concomitant increase in conductivity did not occur. Clogging/ fouling of the variable gain conductivity probe likely caused the event, given that average depth recovered during the next monitoring period following maintenance and probe calibration.

Event 6 (1/6/04 5:36 through 1/6/04 5:51): An event lasting 15 minutes was caused by a decrease in dissolved oxygen, an increases in temperature and conductivity (the latter, from 4.98mS/cm to 14.18 mS/cm in 2 hours). These environmental changes resulted in rapid increases in fish ventilation rate and cough rate, and a decrease in average depth.