Mooring Details: from 2021-11-04 18:38:00 to 2023-09-16 10:15:00
Time Event: 2021-11-04 18:38:00, deployed by M/V Warren Time Event: 2023-09-16 10:15:00, buoy missing after passage of Hurricane Lee, not recovered
Sensor Performance: From 2021-11-04 18:38:00 to 2023-09-16 10:15:00
Data_type: conductivity and Depth: 1 m Data_type: temperature and Depth: 1 m
Deployed on Mooring: F0131
Mooring Details: from 2018-09-30 18:40:00 to 2019-06-04 11:46:00
Time Event: 2018-09-30 18:40:00, deployed by R/V Connecticut Time Event: 2019-06-04 11:46:00, recovered by the R/V Connecticut
Sensor Performance: From 2018-09-30 18:40:00 to 2019-06-04 11:46:00
Data_type: conductivity and Depth: 1 m Data_type: temperature and Depth: 1 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: temperature and Depth: 1 m Data_type: conductivity and Depth: 1 m
Deployed on Mooring: I0132
Mooring Details: from 2016-11-08 16:05:00 to 2018-03-24 14:15:00
Time Event: 2016-11-08 16:05:00, Control box swap by R/V Osprey. Time Event: 2017-01-11 00:00:00, Data communications have stopped (both cell and goes), possible problem with data logger. Time Event: 2017-01-11 11:00:00, Data coms have resumed - both cell and goes reporting valid data once again. No data collected during period of no communications (data logger lockup issue suspected). Time Event: 2017-03-03 09:25:00, Apparent problems with control box starting at this time - no data being collected, no cellphone or Goes transmissions being received. Time Event: 2017-03-03 19:30:00, Normal communiucations restored on this buoy (10-hour gap in data). Time Event: 2017-04-14 16:30:00, Last data received from buoy (missing on both cell and Goes transmissions). Time Event: 2017-04-15 00:25:00, Buoy resumed transmissions on both cell and Goes (7 hour gap for all data indicates that logger may have locked up). Time Event: 2017-04-15 15:30:00, Last data received from buoy (missing on both cell and Goes transmissions). Time Event: 2017-04-16 06:30:00, Buoy resumed transmissions on both cell and Goes (15 hour gap for all data indicates that logger may have locked up while retrieving mstrain wave data). Time Event: 2018-01-05 15:34:00, Last data received from buoy (missing cell transmission, Goes failed in May 2017). Time Event: 2018-01-10 08:00:00, tower reported as broken and in water by fisherman. Time Event: 2018-03-24 14:15:00, Recovered by R/V Connecticut. Mooring wire parted during recovery and the 50m IMP and SUNA (along with chain and anchor) were not recovered.
Sensor Performance: From 2016-11-08 16:05:00 to 0000-00-00 00:00:00
Data_type: conductivity and Depth: 1 m Data_type: temperature and Depth: 1 m
Deployed on Mooring: I0131
Mooring Details: from 2016-10-09 18:36:00 to 2016-11-08 14:55:00
Time Event: 2016-10-25 00:00:00, Last data received via cellphone from this buoy (backup Goes had failed before deployment). Phone is not registering on the AT&T network. Time Event: 2016-10-09 18:36:00, Redeployed by R/V PISCES. Time Event: 2016-11-08 14:06:00, Recovered by R/V Osprey (control box swap). Time Event: 2016-11-08 13:30:00, Restarting datalogger when ship was at the buoy did not restart comms.
Sensor Performance: From 2016-10-09 18:36:00 to 0000-00-00 00:00:00
Data_type: conductivity and Depth: 1 m Data_type: temperature and Depth: 1 m
Deployed on Mooring: F0128
Mooring Details: from 2015-10-28 18:45:00 to 2016-10-06 12:31:00
Time Event: 2015-10-28 18:45:00, Redeployed (turnaround) by R/V Connecticut Time Event: 2016-07-12 07:10:00, Last cell phone connection from buoy; backup Goes data stream is still sending good data. Time Event: 2016-07-14 00:00:00, Cellphone transmissions have resumed once again from this buoy. Time Event: 2016-10-06 12:31:00, recovered by R/V Pisces
Sensor Performance: From 2015-10-28 18:45:00 to 0000-00-00 00:00:00
Data_type: conductivity and Depth: 1 m Data_type: temperature and Depth: 1 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: conductivity and Depth: 1 m Data_type: temperature and Depth: 1 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: conductivity and Depth: 1 m Data_type: temperature and Depth: 1 m
Deployed on Mooring: F0122
Mooring Details: from 2011-01-05 02:25:00 to 2012-03-12 21:05:00
Time Event: 2011-01-05 02:25:00, redeployed by R/V Argo Maine Time Event: 2011-01-05 02:25:00, redeployed by R/V Argo Maine Time Event: 2012-03-06 17:30:00, Cell phone communications failed for data logger. Cause is under investigation, but we hope to have data restored from this buoy before 20 March 2012. Time Event: 2012-03-12 21:05:00, Old control box UMECB121 removed.
Sensor Performance: From 2011-01-05 02:25:00 to 0000-00-00 00:00:00
Data_type: conductivity and Depth: 1 m Data_type: temperature and Depth: 1 m
Deployed on Mooring: A0124
Mooring Details: from 2010-06-03 20:25:00 to 2010-10-13 19:35:00
Time Event: 2010-06-03 20:25:00, redeployed by R.V. Argo Maine Time Event: 2010-10-13 20:35:00, Recovered by R/V COnnecticut.
Sensor Performance: From 2010-06-03 20:25:00 to 2010-10-13 19:35:00
Data_type: conductivity and Depth: 1 m Data_type: temperature and Depth: 1 m Table 'instruments.mooring' doesn't exist
