Mooring Details: from 2024-12-15 02:54:00 to 0000-00-00 00:00:00
Time Event: 2024-12-15 02:54:00, deployed by R/V Connecticut
Sensor Performance: From 2024-12-15 02:54:00 to 0000-00-00 00:00:00
Data_type: int_temp and Depth: 0 m
Deployed on Mooring: A0147
Mooring Details: from 2023-09-20 23:11:00 to 2024-08-16 20:36:00
Time Event: 2023-09-20 23:11:00, Deployed by M/V James Goodwin Time Event: 2024-08-16 20:36:00, recovered by R/V Connecticut
Sensor Performance: From 2023-09-20 23:11:00 to 2024-08-16 20:36:00
Data_type: int_temp and Depth: 0 m
Deployed on Mooring: A0145
Mooring Details: from 2021-11-02 18:05:00 to 2022-09-09 10:50:00
Time Event: 2021-11-02 18:05:00, deployed by the M/V Warren Time Event: 2022-01-08 12:00:00, battery voltage low and dropping over time. Not charging during daytime hours. Time Event: 2022-02-04 19:00:00, battery voltage low (<10V, down to 6.2V). data logger stopped sampling met and diagnostics data for about 18 hours. battery may be damaged. Time Event: 2022-09-09 10:50:00,
Sensor Performance: From 2021-11-02 18:05:00 to 2022-09-09 10:50:00
Data_type: int_temp and Depth: 0 m
Deployed on Mooring: A0143
Mooring Details: from 2020-10-06 02:45:00 to 2021-06-16 16:45:00
Time Event: 2020-10-06 02:45:00, deployed by the R/V Connecticut Time Event: 2020-12-15 12:00:00, battery voltage has been falling since Nov, daily lows s/b below 11.5 volts in Jan. Not charging to 14.5V like other buoys. Time Event: 2021-06-16 16:45:00, Recovered by R/V Connecticut
Sensor Performance: From 2020-10-06 02:45:00 to 2021-06-16 16:45:00
Data_type: int_temp and Depth: 0 m
Deployed on Mooring: A0141
Mooring Details: from 2019-06-01 01:21:00 to 2019-11-26 13:40:00
Time Event: 2019-06-01 01:21:00, deployed by the R/V Connecticut Time Event: 2019-07-14 01:10:00, Last cellphone connection received from buoy. Backup GOES transmissions continue to work although certain variables missing from backup data stream (50m O2). Time Event: 2019-11-26 13:40:00, Recovered by R/V Connecticut. The locking rings on the SBE43 DO sensor and pump were loose; otherwise all looked okay.
Sensor Performance: From 2019-06-01 01:21:00 to 2019-11-26 13:40:00
Data_type: int_temp and Depth: 0 m
Time:2019-07-14 01:10:00, Status: 1
Comments: Last cellphone connection received from buoy. Backup GOES transmissions continue to work although certain variables missing from backup data stream (50m O2).
Deployed on Mooring: A0139
Mooring Details: from 2018-07-10 19:50:00 to 2018-09-27 21:15:00
Time Event: 2018-07-10 19:50:00, deployed by R/V Connecticut Time Event: 2018-09-27 21:15:00, recovered by R/V Connecticut
Sensor Performance: From 2018-07-10 19:50:00 to 2018-09-27 21:15:00
Data_type: int_temp and Depth: 0 m
Deployed on Mooring: A0137
Mooring Details: from 2017-06-28 00:50:00 to 2017-12-07 16:42:00
Time Event: 2017-06-28 00:50:00, deployed by the Warren Time Event: 2017-12-07 16:42:00, recovered by the R/V Connecticut
Sensor Performance: From 2017-06-28 00:50:00 to 0000-00-00 00:00:00
Data_type: int_temp and Depth: 0 m
Deployed on Mooring: F0125
Mooring Details: from 2013-06-23 01:04:00 to 2014-06-01 11:10:00
Time Event: 2013-06-23 01:04:00, Redeployed by R/V Connecticut Time Event: 2013-10-28 14:30:00, Last data received from buoy F0125 (both cellphone and GOES). Time Event: 2013-11-04 21:20:00, New program loaded into datalogger; normal operations have resumed (20m and 50m IMs also reporting). Time Event: 2014-06-01 11:10:00, Recovered by R/V Connectictut. Heavily fouled with traps and pot warp; chain looped/knotted about 25' above anchor.
Sensor Performance: From 2013-06-23 01:04:00 to 0000-00-00 00:00:00
Data_type: int_temp and Depth: 0 m
Deployed on Mooring: F0123
Mooring Details: from 2012-03-12 21:45:00 to 2012-04-14 10:08:00
Time Event: 2012-03-12 21:45:00, Time Event: 2012-04-14 10:08:00, Recovered by R/V Delaware II.
Sensor Performance: From 2012-03-12 21:45:00 to 0000-00-00 00:00:00
Data_type: int_temp and Depth: 0 m
Deployed on Mooring: F0121
Mooring Details: from 2009-09-17 16:05:00 to 2011-01-04 21:15:00
Time Event: 2009-09-17 16:05:00, redeplyed by R/V Argo Maine Time Event: 2010-04-12 14:00:00, Last cellphone transmission received from this buoy. Secondary GOES transmissions continue to be okay. Time Event: 2010-04-13 20:00:00, Normal cellphone transmissions have resumed; all data appear okay. Time Event: 2011-01-04 21:15:00, Recovered by R/V Argo Maine.
Sensor Performance: From 2009-09-17 16:05:00 to 0000-00-00 00:00:00
Data_type: int_temp and Depth: 0 m
Deployed on Mooring: F0118
Mooring Details: from 2008-09-26 00:08:00 to 2009-03-25 21:55:00
Time Event: 2008-09-26 00:08:00, redeployed by R.V Argo Maine Time Event: 2009-03-25 21:55:00, recovered by the R/V Delaware II
Sensor Performance: From 2008-09-26 00:08:00 to 0000-00-00 00:00:00
Data_type: int_temp and Depth: 0 m
Deployed on Mooring: F0116
Mooring Details: from 2007-09-22 21:40:00 to 2008-04-22 14:30:00
Time Event: 2007-09-22 21:40:00, Redeployed by R/V Argo Maine. Time Event: 2008-04-22 14:30:00, Recovered by R/V Delaware II.
Sensor Performance: From 2007-09-22 21:40:00 to 0000-00-00 00:00:00
Data_type: int_temp and Depth: 0 m
Deployed on Mooring: F0114
Mooring Details: from 2006-09-15 15:50:00 to 2007-05-10 12:10:00
Time Event: 2006-09-15 15:50:00, Redeployed by R/V Argo Maine. Time Event: 2007-05-10 08:10:00, Recovered by R/V Argo Maine.
Sensor Performance: From 2006-09-15 15:50:00 to 2007-05-10 12:10:00
Data_type: int_temp and Depth: 0 m
Time:2006-12-31 03:00:00, Status: 1
Comments: Water level alarm readings erratic.
Deployed on Mooring: F0112
Mooring Details: from 2006-02-23 19:15:00 to 2006-05-09 20:10:00
Time Event: 2006-02-23 19:15:00, Redeployed by R/V Argo Maine. Time Event: 2006-05-09 20:10:00, Recovered by R/V Argo Maine.
Sensor Performance: From 2006-02-23 19:15:00 to 2006-05-09 20:10:00
Data_type: int_temp and Depth: 0 m
Deployed on Mooring: F0109
Mooring Details: from 2004-10-06 13:10:00 to 2005-05-31 13:50:00
Time Event: 2004-10-06 13:10:00, Mooring redeployed by R/V Argo Maine. Time Event: 2005-05-31 13:50:00, Recovered by R/V Argo Maine.
Sensor Performance: From 2004-10-06 13:10:00 to 2005-05-31 13:50:00
Data_type: int_temp and Depth: 0 m
Time:2005-01-23 10:00:00, Status: 1
Comments: NOTE: Some invalid wave heights being computed during this storm, please use datya with caution.
Deployed on Mooring: K0103
Mooring Details: from 2002-11-14 02:10:00 to 2003-05-28 17:30:00
Time Event: 2002-11-14 01:45:00, Deployed by R/V Argo Maine. Time Event: 2002-11-27 00:00:00, Intermittent cell phone problems Time Event: 2003-01-10 15:00:00, Cell phone calls becoming intermittent from this buoy during periods of cold/windy weather Time Event: 2003-03-12 23:00:00, Last GOES data received. Time Event: 2003-05-28 13:30:00, Recovered by R/V Argo Maine
Sensor Performance: From 2002-11-14 01:45:00 to 2003-05-28 13:30:00
Data_type: int_temp and Depth: 0 m
Non-Deployment Sensor Events:
Time Event: 2024-10-18 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2024-10-18 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2024-10-18 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2024-10-15 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2023-03-16 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2021-10-05 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2020-09-25 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2020-08-25 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2020-08-25 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2020-08-25 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2019-05-17 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2018-05-22 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2017-06-23 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2016-05-28 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2016-05-28 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2016-05-28 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2016-05-28 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2016-05-28 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2016-05-28 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2016-05-28 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2016-05-28 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2016-05-27 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2015-05-08 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2014-08-29 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2014-08-29 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2014-08-27 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2014-08-05 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2014-08-05 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2014-08-05 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2014-08-05 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2013-04-09 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2013-04-09 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2013-04-09 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2013-04-09 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2013-04-09 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2012-06-11 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2012-04-23 00:00:00, Event: Post-Recovery
Comments: Data file downloaded
Time Event: 2012-04-19 00:00:00, Event: Post-Recovery
Comments: Data file downloaded
Time Event: 2012-03-12 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2011-09-09 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2011-09-09 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2011-01-07 00:00:00, Event: Post-Recovery
Comments: Data file downloaded
Time Event: 2010-10-08 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2010-10-08 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2009-09-10 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2009-07-07 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2009-07-07 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2009-07-06 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2009-06-14 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2009-04-09 00:00:00, Event: Post-Recovery
Comments: Data file downloaded
Time Event: 2009-03-26 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2008-09-10 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2008-09-02 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2008-09-02 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2008-09-02 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2008-09-02 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2008-09-02 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2008-09-02 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2008-06-02 00:00:00, Event: Post-Recovery
Comments: Data file downloaded
Time Event: 2007-07-25 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2007-06-18 00:00:00, Event: Post-Recovery
Comments: Data file downloaded
Time Event: 2007-06-04 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2007-06-04 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2006-06-01 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2006-06-01 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2006-06-01 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2006-06-01 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2006-06-01 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2006-06-01 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2006-05-16 00:00:00, Event: Post-Recovery
Comments: Data file downloaded
Time Event: 2006-05-16 00:00:00, Event: Post-Recovery
Comments: Data file downloaded
Time Event: 2006-02-21 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2005-09-16 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2005-09-16 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2005-09-14 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2005-09-13 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2005-09-13 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2005-09-12 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2005-09-12 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2005-09-12 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2005-09-12 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2004-12-21 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2004-10-22 00:00:00, Event: Post-Recovery
Comments: Data file downloaded
Time Event: 2004-10-06 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2004-09-24 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2004-09-24 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2004-09-24 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2004-09-09 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2004-08-12 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2004-08-11 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2004-08-11 00:00:00, Event: Prepared
Comments: Ready for deployment
Time Event: 2003-07-30 15:00:00, Event: Post-Recovery