Mooring Details: from 2024-05-05 16:46:00 to 0000-00-00 00:00:00
Time Event: 2024-05-05 16:46:00, Deployed by R/V Connecticut
Sensor Performance: From 2024-05-05 16:46:00 to 0000-00-00 00:00:00
Data_type: conductivity and Depth: 20 m Data_type: temperature and Depth: 20 m
Deployed on Mooring: N0123
Mooring Details: from 2021-07-20 21:25:00 to 2022-05-18 09:00:00
Time Event: 2021-07-20 21:25:00, deployed by R/V Connecticut Time Event: 2022-05-18 09:00:00,
Sensor Performance: From 2021-07-20 21:25:00 to 2022-05-18 09:00:00
Data_type: conductivity and Depth: 100 m Data_type: temperature and Depth: 100 m
Deployed on Mooring: N0122
Mooring Details: from 2020-11-07 23:41:00 to 2021-06-12 11:30:00
Time Event: 2020-11-07 23:41:00, Redeployed by R/V Connecticut Time Event: 2020-11-07 23:42:00, unable to dial in to iridium modem. Modem will not answer. Can connect occasionally at end of callback session before hangup Time Event: 2020-12-21 06:00:00, main battery voltage suddenly dropped below 10v. Not charging fully. Buoy may go off air soon. Time Event: 2020-12-27 01:00:00, last data from iridium modem. may be from low voltage or from attempts to set lo voltage threshhold. Time Event: 2021-01-01 01:24:00, buoy off the air, last GOES transmission w/data. next two transmissions had empty buffers, then silence. Time Event: 2021-06-12 12:00:00, Recovered by R/V Conneticut Time Event: 2021-01-18 00:00:00, Buoy moved about 300m to the WNW over a 6-hour period. Time Event: 2021-02-02 15:00:00, Buoy moved about 1000 m to the WNW over a 15-hour period. Time Event: 2021-03-02 00:00:00, Buoy moved about 300 m to the ESE. Time Event: 2021-03-29 18:00:00, Buoy moved about 500m over a 3 hour period. Time Event: 2021-04-17 03:00:00, Buoy is adrift (no longer anchored).
Sensor Performance: From 2020-11-08 23:41:00 to 2021-06-12 12:00:00
Data_type: conductivity and Depth: 100 m Data_type: temperature and Depth: 100 m
Deployed on Mooring: M0127
Mooring Details: from 2017-06-28 19:05:00 to 2018-07-09 12:11:00
Time Event: 2017-06-28 19:05:00, deployed by the vessel Warren Time Event: 2018-05-09 05:00:00, Goes tranmissions becoming erratic with bad checksums (3). First part of message and first 2 checksums are okay. Time Event: 2018-05-16 05:00:00, Last Goes transmissions received from buoy (iridium phone still working). Time Event: 2018-07-09 12:11:00, recovered by R/V Connecticut
Sensor Performance: From 2017-06-28 19:05:00 to 2018-07-09 08:11:00
Data_type: conductivity and Depth: 150 m Data_type: temperature and Depth: 150 m
Deployed on Mooring: M0126
Mooring Details: from 2016-10-08 14:50:00 to 2017-02-21 14:30:00
Time Event: 2016-10-08 14:50:00, Redeployed by R/V PISCES Time Event: 2016-10-21 12:00:00, Problems seen with datalogger including corrupt Goes buffers (datalogger issues w/Goes xmitter coms), corrupt visibility and pressure (Goes interference), int. doppler. Time Event: 2017-02-21 14:30:00, Recovered by John and Ian off the Scarlet Isabella, 8 days after breaking free. Tethers cut. Time Event: 2017-02-13 21:30:00, Buoy broke free from its anchor during storm, drifting to the south.
Sensor Performance: From 2016-10-08 14:50:00 to 2017-02-21 14:30:00
Data_type: temperature and Depth: 150 m Data_type: conductivity and Depth: 150 m
Deployed on Mooring: M0124
Mooring Details: from 2014-09-18 18:04:00 to 2015-11-04 14:15:00
Time Event: 2014-09-18 18:04:00, Redeployed by R/V Connecticut. Time Event: 2015-11-04 14:15:00, Recovered (for turnaround) by R/V Connecticut
Sensor Performance: From 2014-09-18 18:04:00 to 0000-00-00 00:00:00
Data_type: conductivity and Depth: 50 m Data_type: temperature and Depth: 50 m
Deployed on Mooring: B0125
Mooring Details: from 2013-06-20 15:45:00 to 2014-06-01 23:30:00
Time Event: 2013-06-20 15:45:00, Redeployed by R/V Connecticut. Time Event: 2014-06-01 23:30:00, recovered by R/V Connecticut
Sensor Performance: From 2013-06-20 15:45:00 to 0000-00-00 00:00:00
Data_type: conductivity and Depth: 20 m Data_type: temperature and Depth: 20 m
Deployed on Mooring: M0120
Mooring Details: from 2012-04-12 22:15:00 to 2012-10-25 11:30:00
Time Event: 2012-04-12 22:15:00, Redeployed by R/V Delaware II Time Event: 2012-10-25 11:30:00, Recovered by R/V Connecticut
Sensor Performance: From 2012-04-12 22:15:00 to 0000-00-00 00:00:00
Data_type: conductivity and Depth: 50 m Data_type: temperature and Depth: 50 m
Deployed on Mooring: M0119
Mooring Details: from 2012-02-04 14:10:00 to 2012-04-12 16:55:00
Time Event: 2012-02-04 14:10:00, deployed by the R/V Connecticut Time Event: 2012-04-12 16:55:00, Recoverd by R/V Delaware II
Sensor Performance: From 2012-02-04 14:10:00 to 0000-00-00 00:00:00
Data_type: conductivity and Depth: 50 m Data_type: temperature and Depth: 50 m
Deployed on Mooring: M0116
Mooring Details: from 2009-10-02 17:10:00 to 2010-06-09 10:10:00
Time Event: 2009-10-02 17:10:00, Redeployed by R/V Argo Maine. Time Event: 2009-12-01 12:00:00, Buoy having problems with iridium phone (calling but having trouble transfering data). Time Event: 2010-06-09 10:10:00, Recovered by R/V Argo Maine.
Sensor Performance: From 2009-10-02 17:10:00 to 0000-00-00 00:00:00
Data_type: conductivity and Depth: 50 m Data_type: temperature and Depth: 50 m
Deployed on Mooring: N0109
Mooring Details: from 2008-04-19 16:15:00 to 2009-03-27 12:25:00
Time Event: 2008-04-19 16:15:00, Deployed from Delaware II Time Event: 2008-06-05 22:00:00, Buoy moved about 250m to the NW; still appears to be anchored. Time Event: 2009-03-27 12:25:00, recovered by R/V Delaware.
Sensor Performance: From 2008-04-19 16:15:00 to 0000-00-00 00:00:00
Data_type: conductivity and Depth: 20 m Data_type: temperature and Depth: 20 m
Deployed on Mooring: F0115
Mooring Details: from 2007-05-10 19:05:00 to 2007-09-22 04:20:00
Time Event: 2007-05-10 19:05:00, Redeployed by R/V Argo Maine. Time Event: 2007-09-22 04:20:00, Recovered by R/V Argo Maine.
Sensor Performance: From 2007-05-10 19:05:00 to 0000-00-00 00:00:00
Data_type: conductivity and Depth: 50 m Data_type: temperature and Depth: 50 m
Deployed on Mooring: M0107
Mooring Details: from 2005-05-18 03:20:00 to 2005-10-04 14:50:00
Time Event: 2005-05-18 03:20:00, Redeployed by R/V Argo Maine. Time Event: 2005-10-04 14:50:00, Recoverd by R/V Argo Maine.
Sensor Performance: From 2005-05-18 03:20:00 to 2005-10-04 14:50:00
Data_type: temperature and Depth: 20 m Data_type: conductivity and Depth: 20 m
Deployed on Mooring: F0108
Mooring Details: from 2004-04-27 16:36:00 to 2004-10-05 03:45:00
Time Event: 2004-04-27 16:36:00, Redeployed by R/V Argo Maine. Time Event: 2004-10-05 03:45:00, Mooring recovered by R/V Argo Maine.
Sensor Performance: From 2004-04-27 16:36:00 to 2004-10-05 03:45:00
Data_type: conductivity and Depth: 50 m Data_type: temperature and Depth: 50 m
Deployed on Mooring: J0201
Mooring Details: from 2001-09-24 17:30:00 to 2002-11-13 11:30:00
Time Event: 2001-09-24 17:30:00, Replaces J0101 in new site Time Event: 2002-11-13 11:30:00, Recovered by R/V Argo Maine.
Sensor Performance: From 2001-09-24 17:30:00 to 2002-11-13 11:30:00
Data_type: salinity and Depth: 10 m
Time:2002-03-05 00:00:00, Status: 1
Comments: 10m SBE37IM data becoming very intermittent.
Time:2002-03-15 15:00:00, Status: 0
Comments: Replaced inductive modem, data looks okay once again
Time:2002-09-06 00:00:00, Status: 1
Comments: Data from 10m SBE37IM becoming intermittent.
Data_type: temperature and Depth: 10 m
Time:2002-03-05 00:00:00, Status: 1
Comments: 10m SBE37IM data becoming very intermittent.
Time:2002-03-15 15:00:00, Status: 0
Comments: Replaced inductive modem, data looks okay once again
Time:2002-09-06 00:00:00, Status: 1
Comments: Data from 10m SBE37IM becoming intermittent.
Deployed on Mooring: J0101
Mooring Details: from 2001-09-19 20:10:00 to 0000-00-00 00:00:00
Time Event: 2001-09-19 20:00:00, Deployed. Time Event: 2001-09-24 16:00:00, Recovered buoy for redeployment in position approved by pilots
Sensor Performance: From 2001-09-19 20:00:00 to 2001-09-24 16:00:00
Data_type: salinity and Depth: 20 m Data_type: temperature and Depth: 20 m
Non-Deployment Sensor Events:
Time Event: 2019-09-04 00:00:00, Event: Post-Recovery
Comments: Data file downloaded
Time Event: 2017-03-15 00:00:00, Event: Post-Recovery
Comments: Data file downloaded
Time Event: 2016-09-16 19:10:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2016-05-11 13:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2015-11-20 00:00:00, Event: Post-Recovery
Comments: Data file downloaded
Time Event: 2014-08-30 18:11:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2013-06-04 19:18:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2013-04-24 15:30:00, Event: In_from_Repair
Comments:
Time Event: 2013-01-25 00:00:00, Event: Out_for_Repair
Comments:
Time Event: 2013-01-24 00:00:00, Event: Out_for_Repair
Comments:
Time Event: 2012-11-16 00:00:00, Event: Post-Recovery
Comments: Data file downloaded
Time Event: 2012-01-20 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2010-06-21 00:00:00, Event: Post-Recovery
Comments: Data file downloaded
Time Event: 2009-09-08 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2009-07-01 00:00:00, Event: Out_for_Repair
Comments:
Time Event: 2009-05-29 00:00:00, Event: Post-Recovery
Comments: Data file downloaded
Time Event: 2008-02-27 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2007-03-16 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2007-02-20 00:00:00, Event: In_from_Repair
Comments: Calibrated at Factory
Time Event: 2007-01-26 00:00:00, Event: Out_for_Repair
Comments: Sent for Calibration
Time Event: 2005-11-09 00:00:00, Event: Post-Recovery
Comments: Data file downloaded
Time Event: 2005-03-29 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2004-10-21 00:00:00, Event: Post-Recovery
Comments: Clock off by 1 hour; data files downloaded
Time Event: 2004-04-14 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2004-03-26 00:00:00, Event: In_from_Repair