GoMOOS Moored Sensor History Physical Oceanography Group School of Marine Sciences University of Maine

GoMoos Sensor History for Sensor: UMECB120

Manufacturer: University_of_Maine,
Model: GOM01
Purchase Date: 2002-01-01

Deployed on Mooring: A0148

Mooring Details: from 2024-08-17 02:50:00 to 2024-12-14 17:14:00
Time Event: 2024-08-17 02:50:00, deployed by R/V Connecticut
Time Event: 2024-12-14 17:14:00, recovered by R/V Connecticut

Sensor Performance: From 2024-08-17 02:50:00 to 2024-12-14 17:14:00
Data_type: int_temp and Depth: 0 m

Deployed on Mooring: A0146

Mooring Details: from 2022-09-09 15:40:00 to 2023-09-20 16:45:00
Time Event: 2022-09-09 15:40:00, Deployed by M/V Warren
Time Event: 2023-09-20 16:45:00, Recovered by M/V James Goodwin

Sensor Performance: From 2022-09-09 15:40:00 to 2023-09-20 16:45:00
Data_type: int_temp and Depth: 0 m

Deployed on Mooring: A0144

Mooring Details: from 2021-06-17 02:45:00 to 2021-11-02 11:58:00
Time Event: 2021-06-17 02:45:00, Redeployed by R/V Connecticut
Time Event: 2021-11-02 11:58:00, Recovered by M/V Warren
Time Event: 2021-06-18 12:00:00, high battery voltage seen on buoy during daytime. probably solar panel connected to battery directly

Sensor Performance: From 2021-06-17 02:45:00 to 2021-11-02 11:58:00
Data_type: int_temp and Depth: 0 m

Time:2021-06-18 12:00:00, Status: 0

Comments: high battery voltage seen on buoy during daytime. probably solar panel connected to battery directly

Time:2021-06-17 12:00:00, Status: 0

Comments: intermittent missing met data at top of hour after datalogger program change. Corrected 3 days later.

Deployed on Mooring: A0142

Mooring Details: from 2019-11-26 20:25:00 to 2020-10-05 22:12:00
Time Event: 2019-11-26 20:25:00, deployed by the R/V Connecticut
Time Event: 2020-10-05 22:12:00, recovered by the R/V Connecticut
Time Event: 2019-12-15 00:01:00, battery voltage has been falling since deployment, daily lows below 11.5 volts now

Sensor Performance: From 2019-11-26 20:25:00 to 2020-10-05 22:12:00
Data_type: int_temp and Depth: 0 m

Deployed on Mooring: A0140

Mooring Details: from 2018-09-28 05:25:00 to 2019-05-31 18:50:00
Time Event: 2018-09-28 05:25:00, deployed by R/V Connecticut
Time Event: 2019-05-31 18:50:00, recovered by the R/V Connecticut

Sensor Performance: From 2018-09-28 05:25:00 to 2019-05-31 18:50:00
Data_type: int_temp and Depth: 0 m

Deployed on Mooring: A0138

Mooring Details: from 2017-12-08 01:54:00 to 2018-07-10 14:05:00
Time Event: 2017-12-08 01:54:00, deployed by R/V Connecticut
Time Event: 2018-07-10 14:05:00, recovered by R/V Connecticut

Sensor Performance: From 2017-12-08 01:54:00 to 2018-07-10 14:05:00
Data_type: int_temp and Depth: 0 m

Deployed on Mooring: A0136

Mooring Details: from 2016-07-07 20:20:00 to 2017-06-27 16:11:00
Time Event: 2016-07-07 20:20:00, deployed by the R/V Connecticut
Time Event: 2016-12-10 00:00:00, Backup GOES buffers became corrupt despite valid checksums.
Time Event: 2016-12-12 00:00:00, Primary cellphone tranmssions stopped from the buoy. Attempts to contact the phone were unsuccessful although phone was visible on the AT&T network.
Time Event: 2016-12-15 21:06:00, Normal communications resumed from this buoy (both cell and Goes).
Time Event: 2016-07-07 21:00:00, Wave direction and tilt invalid from microstrain directional wave sensor.
Time Event: 2016-10-01 00:00:00, Intermittent spiking seen on primary wind sensor (Gill), generally observed at speeds > 25 kts.
Time Event: 2017-06-22 18:30:00, New program loaded into control box remotely; valid accelerometer wave data being received now from this buoy.
Time Event: 2017-06-27 16:11:00, recovered by the vessel Warren

Sensor Performance: From 2016-07-07 20:20:00 to 0000-00-00 00:00:00
Data_type: int_temp and Depth: 0 m

Deployed on Mooring: A0135

Mooring Details: from 2015-10-26 22:11:00 to 2016-07-07 14:08:00
Time Event: 2015-10-26 18:11:00, Deployed by R/V Connecticut
Time Event: 2016-07-07 14:08:00, Recovered by R/V Connecticut. Signs of apparent collision with following damage to tower: RMYoung missing tail section, Gill missing electronics, Goes antenna chipped. RDI external batt 41V.

Sensor Performance: From 2015-10-26 18:11:00 to 0000-00-00 00:00:00
Data_type: int_temp and Depth: 0 m

Deployed on Mooring: A0133

Mooring Details: from 2014-10-25 23:32:00 to 2015-06-03 22:05:00
Time Event: 2014-10-25 23:32:00, Redeployed by R/V Connecticut.
Time Event: 2015-01-27 19:00:00, Buoy drug anchor 100m to S during storm.
Time Event: 2015-06-03 22:05:00, Recovered by R/V Connecticut. RMYoung wind sensor missing; rest of sensors recovered without problems.

Sensor Performance: From 2014-10-25 23:32:00 to 0000-00-00 00:00:00
Data_type: int_temp and Depth: 0 m

Deployed on Mooring: A0131

Mooring Details: from 2013-10-29 20:42:00 to 2014-06-03 19:45:00
Time Event: 2013-10-29 20:42:00, Redeployed by R/V Connecticut
Time Event: 2014-06-03 19:45:00, Recovered by R/V Connecticut without problems or damage.

Sensor Performance: From 2013-10-29 20:42:00 to 0000-00-00 00:00:00
Data_type: int_temp and Depth: 0 m

Deployed on Mooring: A0129

Mooring Details: from 2012-10-23 12:05:00 to 2013-06-19 23:40:00
Time Event: 2012-10-23 12:05:00, Redeployed by R/V Connecticut.
Time Event: 2013-06-19 23:40:00, recovered by R/V Connecticut
Time Event: 2013-06-20 01:00:00, Instruments missing on this buoy when recovered include RMY49996, SBEDO430432, SBE5T053703, UMESB001, AANDO232.

Sensor Performance: From 2012-10-23 12:05:00 to 0000-00-00 00:00:00
Data_type: int_temp and Depth: 0 m

Deployed on Mooring: A0127

Mooring Details: from 2011-10-08 14:50:00 to 2012-04-16 12:38:00
Time Event: 2011-10-08 14:50:00, Redeployed by R/V Connecticut
Time Event: 2012-04-16 12:38:00, Recovered by R/V Delaware II.

Sensor Performance: From 2011-10-08 14:50:00 to 2012-04-16 12:38:00
Data_type: int_temp and Depth: 0 m

Deployed on Mooring: A0125

Mooring Details: from 2010-10-13 22:42:00 to 2011-06-01 14:45:00
Time Event: 2010-10-13 22:42:00, Redeployed by R/V Connecticut
Time Event: 2011-06-01 14:45:00, Recovered by R/V Connecticut. The cable between the inductive coupler and the serial bridge/optode was found damaged; otherwise all instruments recovered intact.

Sensor Performance: From 2010-10-13 22:42:00 to 0000-00-00 00:00:00
Data_type: int_temp and Depth: 0 m

Deployed on Mooring: A0123

Mooring Details: from 2009-09-23 16:55:00 to 2010-06-03 14:09:00
Time Event: 2009-09-23 16:25:00, redeployed by R/V Argo Maine
Time Event: 2010-06-03 14:09:00, recovered by RV Argo Maine

Sensor Performance: From 2009-09-23 16:55:00 to 0000-00-00 00:00:00
Data_type: int_temp and Depth: 0 m

Deployed on Mooring: A0121

Mooring Details: from 2008-10-01 14:35:00 to 2009-03-20 19:28:00
Time Event: 2008-10-01 14:35:00, Redeployed by R/V Argo Maine.
Time Event: 2009-03-20 19:28:00, Recovered by R/V Delaware II.

Sensor Performance: From 2008-10-01 14:35:00 to 0000-00-00 00:00:00
Data_type: int_temp and Depth: 0 m

Deployed on Mooring: A0119

Mooring Details: from 2007-09-23 14:40:00 to 2008-04-15 21:54:00
Time Event: 2007-09-23 14:40:00, Redeployed by R/V Argo Maine.
Time Event: 2008-04-15 23:59:59, Mooring A0119 Recovered By FV Delaware II, RMY Missing, Gill Damaged, Tower Bent, SBE16 & SBE44-optode smashed together

Sensor Performance: From 2007-09-23 14:40:00 to 0000-00-00 00:00:00
Data_type: int_temp and Depth: 0 m

Deployed on Mooring: A0117

Mooring Details: from 2006-09-13 21:35:00 to 2007-03-23 11:25:00
Time Event: 2006-09-13 21:35:00, Redeployed by R/V Argo Maine.
Time Event: 2007-03-23 11:25:00, Mooring A0117 Recovered By RV Delaware II

Sensor Performance: From 2006-09-13 21:35:00 to 2007-03-23 11:25:00
Data_type: int_temp and Depth: 0 m

Deployed on Mooring: L0105

Mooring Details: from 2004-06-04 14:45:00 to 2004-10-02 10:55:00
Time Event: 2004-06-04 14:45:00, Redeployed by R/V Argo Maine.
Time Event: 2004-10-02 10:55:00, Mooring recovered by R/V Argo Maine.

Sensor Performance: From 2004-06-04 14:45:00 to 2004-10-02 10:55:00
Data_type: int_temp and Depth: 0 m

Deployed on Mooring: C0203

Mooring Details: from 2003-04-25 16:30:00 to 2003-10-09 22:45:00
Time Event: 2003-04-25 16:30:00, Redeployed by R/V Argo Maine

Sensor Performance: From 2003-04-25 16:30:00 to 2003-10-09 22:45:00
Data_type: int_temp and Depth: 0 m

Deployed on Mooring: F0103

Mooring Details: from 2002-01-08 16:55:00 to 2002-10-03 18:30:00
Time Event: 2002-01-08 17:00:00, Redeployed mooring at site F.
Time Event: 2002-10-03 18:48:00, Recovered F0103.

Sensor Performance: From 2002-01-08 17:00:00 to 2002-10-03 18:48:00
Data_type: int_temp and Depth: 0 m

Non-Deployment Sensor Events:

Time Event: 2024-08-06 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2022-08-08 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2022-08-08 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2021-05-28 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2021-05-28 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2021-05-28 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2019-10-08 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2018-08-21 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2018-08-21 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2017-09-30 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2017-09-30 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2017-09-30 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-09-01 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2015-09-01 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2015-09-01 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2015-09-01 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2015-09-01 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2015-09-01 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2015-09-01 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2015-09-01 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-27 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2014-08-17 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2014-08-17 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2013-10-22 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2013-10-04 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2013-10-04 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2012-08-28 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2012-08-28 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2012-08-28 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2012-08-22 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2012-08-22 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: 2011-08-26 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2011-08-23 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2011-08-23 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2011-06-14 00:00:00, Event: Post-Recovery

Comments: Data file downloaded

Time Event: 2010-08-25 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2010-08-25 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2010-08-25 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2010-08-25 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2010-08-17 00:00:00, Event: Post-Recovery

Comments: Data file downloaded

Time Event: 2009-08-17 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2009-08-17 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2009-08-17 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-06-09 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2009-06-03 00:00:00, Event: Post-Recovery

Comments: Data file downloaded

Time Event: 2008-09-10 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2008-09-08 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2008-09-08 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-23 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2007-07-23 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2007-07-23 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2007-05-23 00:00:00, Event: Post-Recovery

Comments: Data file downloaded

Time Event: 2006-09-07 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2006-09-07 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2006-09-07 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2006-09-07 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2006-09-07 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2006-08-11 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2006-08-11 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2006-08-11 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2006-06-05 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-06-01 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2006-04-19 00:00:00, Event: Post-Recovery

Comments: Data file downloaded

Time Event: 2006-01-19 00:00:00, Event: Post-Recovery

Comments: Data file downloaded

Time Event: 2005-09-12 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2005-09-09 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2005-09-09 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2005-09-09 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2005-09-02 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2005-08-19 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2005-08-09 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2005-06-21 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2005-06-21 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2005-06-21 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2005-06-21 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2004-11-22 00:00:00, Event: Post-Recovery

Comments: Data file downloaded

Time Event: 2004-10-22 00:00:00, Event: Post-Recovery

Comments: Data file downloaded

Time Event: 2004-05-27 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2004-05-27 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2004-01-16 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2003-12-15 00:00:00, Event: Prepared

Comments: Ready for deployment