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

GoMoos Sensor History for Sensor: UMECB118

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

Deployed on Mooring: F0134

Mooring Details: from 2021-06-15 00:20:00 to 2022-10-17 20:43:00
Time Event: 2021-06-15 00:20:00, Redeployed by R/V Connecticut.
Time Event: 2022-10-17 20:43:00, Recovered by M/V Warren

Sensor Performance: From 2021-06-15 00:20:00 to 2022-10-17 20:43:00
Data_type: int_temp and Depth: 0 m

Deployed on Mooring: F0133

Mooring Details: from 2020-11-10 21:53:00 to 2021-06-14 11:20:00
Time Event: 2020-11-10 21:53:00, Redeployed by R/V Connecticut
Time Event: 2021-06-14 11:20:00, Recovered by R/V Connecticut.

Sensor Performance: From 2020-11-10 21:53:00 to 2021-06-14 11:20:00
Data_type: int_temp and Depth: 0 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: int_temp and Depth: 0 m

Deployed on Mooring: E0136

Mooring Details: from 2017-12-09 18:15:00 to 2018-04-23 16:00:00
Time Event: 2017-12-09 18:15:00, Redeployed by R/V COnnecticut.
Time Event: 2017-12-15 02:00:00, Serial data instruments becoming very intermittent (Gill, BAE GPS, Aanderaa, RDIWH, SBE37, SUNA).
Time Event: 2018-03-13 12:00:00, GOES messages have been missing for some weeks, except for truncated garbled messages. Now 5:20 min late garbled messages are coming in.
Time Event: 2018-04-23 16:00:00, Recovered - control box replacement from R/V Ira C

Sensor Performance: From 2017-12-09 18:15:00 to 0000-00-00 00:00:00
Data_type: int_temp and Depth: 0 m

Deployed on Mooring: E0134

Mooring Details: from 2016-07-09 14:50:00 to 2016-12-07 15:15:00
Time Event: 2016-07-09 14:50:00, Redeployed by R/V Connecticut.
Time Event: 2016-11-22 00:00:00, Missing, corrupt or intermittent data from most sensors; problem appears to be with datalogger.
Time Event: 2016-12-07 15:15:00, recovered (box swap) by R/V Ira C.

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

Deployed on Mooring: E0132

Mooring Details: from 2014-09-19 23:03:00 to 2015-06-05 22:10:00
Time Event: 2014-09-19 23:03:00, Redeployed by R/V Connecticut.
Time Event: 2015-04-21 09:00:00, Last communication from this buoy (tower damaged).
Time Event: 2015-06-05 22:10:00, Recovered by R/V Connecticut. Tower was missing; remainder of equipment was recovered intact.

Sensor Performance: From 2014-09-19 23:03:00 to 0000-00-00 00:00:00
Data_type: int_temp and Depth: 0 m

Deployed on Mooring: E0131

Mooring Details: from 2014-06-02 17:12:00 to 2014-09-19 15:45:00
Time Event: 2014-06-02 17:12:00, Redeployed by R/V Connecticut.
Time Event: 2014-09-12 13:30:00, Buoy has started to move slowly to the west. After watching positions, it is clear that the buoy has broken free from its anchor - all data continue to report (including 87m SBE16)
Time Event: 2014-09-19 15:45:00, Recovered by R/V Connecticut at 43 22N, 69 57W (buoy adrift). Shackle below 87m SBE16 cage was completely missing.

Sensor Performance: From 2014-06-02 17:12:00 to 0000-00-00 00:00:00
Data_type: int_temp and Depth: 0 m

Deployed on Mooring: E0129

Mooring Details: from 2012-04-15 01:35:00 to 2013-06-24 10:45:00
Time Event: 2012-04-15 01:35:00, Redeployed by R/V Delaware II
Time Event: 2013-06-24 10:45:00, Recovered by R/ V Connecticut

Sensor Performance: From 2012-04-15 01:35:00 to 0000-00-00 00:00:00
Data_type: int_temp and Depth: 0 m

Deployed on Mooring: MDS02

Mooring Details: from 2009-11-05 16:50:00 to 2010-10-12 22:50:00
Time Event: 2009-11-05 16:50:00, Redeployed by R/V Connecticut
Time Event: 2010-08-24 10:00:00, Buoy moved about 400m to SW during past 20 hours during storm.
Time Event: 2010-10-12 22:50:00, Recovered by R/V Connecticut.

Sensor Performance: From 2009-11-05 16:50:00 to 0000-00-00 00:00:00
Data_type: int_temp and Depth: 0 m

Deployed on Mooring: C0216

Mooring Details: from 2008-04-17 11:15:00 to 2009-03-23 11:50:00
Time Event: 2008-04-17 11:15:00, Redeployed By FV Delaware II
Time Event: 2008-11-21 01:00:00, Last cellphone transmission received.
Time Event: 2008-11-24 06:00:00, Goes messages being received again (still intermittent).
Time Event: 2008-11-24 08:00:00, Cellphone messages being received once again.
Time Event: 2008-11-25 13:00:00, Problems are being experienced with communications from this buoy. There have been periods of neither cellphone nor satellite transmissions lasting from several hours to several days.
Time Event: 2009-03-23 11:50:00, Recovered by R/V Argo Maine.

Sensor Performance: From 2008-04-17 11:15:00 to 0000-00-00 00:00:00
Data_type: int_temp and Depth: 0 m

Deployed on Mooring: C0214

Mooring Details: from 2007-03-25 14:59:00 to 2007-11-18 21:15:00
Time Event: 2007-03-25 14:59:00, Mooring C0214 Redeployed by R/V Delaware II
Time Event: 2007-11-18 21:15:00, Recovered by R/V Argo Maine.

Sensor Performance: From 2007-03-25 14:59:00 to 2007-11-18 21:15:00
Data_type: int_temp and Depth: 0 m

Deployed on Mooring: C0211

Mooring Details: from 2006-04-11 17:30:00 to 2006-09-12 17:10:00
Time Event: 2006-04-11 17:30:00, redeployed by NOAA Ship Delaware II
Time Event: 2006-09-12 17:10:00, Recovered by R/V Argo Maine.

Sensor Performance: From 2006-04-11 17:30:00 to 2006-09-12 17:10:00
Data_type: int_temp and Depth: 0 m

Deployed on Mooring: C0208

Mooring Details: from 2005-02-24 21:45:00 to 2005-06-01 03:15:00
Time Event: 2005-02-25 21:45:00, Redeployed by R/V Argo Maine.
Time Event: 2005-05-09 00:00:00, Cellphone calls becoming somewhat intermittent, problem appears to be with antenna or cellphone coverage in Casco Bay.
Time Event: 2005-06-01 03:15:00, Recovered by R/V Argo Maine.

Sensor Performance: From 2005-02-25 21:45:00 to 2005-06-01 03:15:00
Data_type: int_temp and Depth: 0 m

Time:2005-05-09 00:00:00, Status: 0

Comments: Cellphone calls becoming somewhat intermittent, problem appears to be with antenna or cellphone coverage in Casco Bay.

Deployed on Mooring: C0206

Mooring Details: from 2004-10-07 14:30:00 to 2005-01-07 22:10:00
Time Event: 2004-10-07 14:30:00, Mooring redeployed by R/V Argo Maine.
Time Event: 2004-10-07 14:00:00, No Goes transmissions being received since deployment.
Time Event: 2004-12-20 10:00:00, Cell phone becoming intermittent.
Time Event: 2005-01-07 21:50:00, recovered by R/V Argo Maine

Sensor Performance: From 2004-10-07 14:30:00 to 2005-01-07 21:50:00
Data_type: int_temp and Depth: 0 m

Time:2004-12-20 10:00:00, Status: 1

Comments: Cell phone becoming intermittent.

Deployed on Mooring: J0207

Mooring Details: from 2004-04-29 00:15:00 to 2004-05-13 15:10:00
Time Event: 2004-04-29 00:15:00, Redeployed by R/V Argo Maine.
Time Event: 2004-05-13 15:30:00, Control box replaced.

Sensor Performance: From 2004-04-29 00:15:00 to 2004-05-13 15:30:00
Data_type: int_temp and Depth: 0 m

Deployed on Mooring: J0206

Mooring Details: from 2004-02-18 15:10:00 to 2004-04-28 21:30:00
Time Event: 2004-02-18 15:00:00, J0206 redeployed by R/V Argo Maine.
Time Event: 2004-02-18 15:00:00, Redployed by R/V Argo Maine.
Time Event: 2004-04-28 21:30:00, Recovered by R/V Argo Maine.

Sensor Performance: From 2004-02-18 15:00:00 to 2004-04-28 21:30:00
Data_type: int_temp and Depth: 0 m

Deployed on Mooring: K0104

Mooring Details: from 2003-05-28 20:12:00 to 2003-09-24 11:55:00
Time Event: 2003-05-28 16:12:00, Redeployed by R/V Argo Maine.
Time Event: 2003-09-24 11:55:00, Recovered by R/V Argo Maine.

Sensor Performance: From 2003-05-28 16:12:00 to 2003-09-24 11:55:00
Data_type: int_temp and Depth: 0 m

Deployed on Mooring: I0102

Mooring Details: from 2002-01-06 17:15:00 to 2002-07-24 09:20:00
Time Event: 2002-01-06 17:00:00, Deployed.
Time Event: 2002-07-24 09:45:00, Buoy I0102 was recovered by R/V Argo Maine.

Sensor Performance: From 2002-01-06 17:00:00 to 2002-07-24 09:45:00
Data_type: int_temp and Depth: 0 m

Non-Deployment Sensor Events:

Time Event: 2024-04-24 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2024-01-11 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2024-01-11 00:00:00, Event: Prepared

Comments: Ready for deployment

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

Comments: Ready for deployment

Time Event: 2021-06-14 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2021-06-14 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: 2019-05-17 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-02-02 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2017-02-02 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2016-06-03 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2016-06-03 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: 2014-09-19 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2014-05-14 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2014-05-12 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2014-05-12 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2012-04-02 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2012-03-29 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2012-03-29 00:00:00, Event: Prepared

Comments: Ready for deployment

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

Comments: Ready for deployment

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

Comments: Ready for deployment

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

Comments: Ready for deployment

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

Comments: Ready for deployment

Time Event: 2010-12-21 00:00:00, Event: Post-Recovery

Comments: Data file downloaded

Time Event: 2009-11-03 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2009-11-03 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2009-11-02 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2009-11-02 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2009-11-02 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2009-11-02 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2009-11-02 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2009-05-13 00:00:00, Event: Post-Recovery

Comments: Data file downloaded

Time Event: 2009-04-09 00:00:00, Event: Post-Recovery

Comments: Data file downloaded

Time Event: 2008-03-25 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2008-03-06 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2008-03-05 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2007-11-19 00:00:00, Event: Post-Recovery

Comments: Data file downloaded

Time Event: 2007-03-16 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2007-02-28 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2007-02-28 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2007-02-28 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2007-02-22 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2006-12-13 00:00:00, Event: Post-Recovery

Comments: Data file downloaded

Time Event: 2006-12-13 00:00:00, Event: Post-Recovery

Comments: Data file downloaded

Time Event: 2006-03-21 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2006-02-02 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2006-02-02 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2006-02-02 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2005-11-28 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2005-11-28 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2005-11-28 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2005-11-28 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2005-11-28 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2005-11-28 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2005-11-10 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2005-11-10 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2005-10-21 00:00:00, Event: Post-Recovery

Comments: Data file downloaded

Time Event: 2005-06-01 00:00:00, Event: Post-Recovery

Comments: Data file downloaded

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

Comments: Ready for deployment

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

Comments: Ready for deployment

Time Event: 2005-03-03 00:00:00, Event: Post-Recovery

Comments: Data file downloaded

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

Comments: Ready for deployment

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

Comments: Ready for deployment

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

Comments: Ready for deployment

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

Comments: Ready for deployment

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

Comments: Ready for deployment

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

Comments: Ready for deployment

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

Comments: Ready for deployment

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

Comments: Ready for deployment

Time Event: 2005-02-01 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-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-02 00:00:00, Event: Prepared

Comments: Ready for deployment

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

Comments: Ready for deployment

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

Comments: Ready for deployment

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

Comments: Ready for deployment

Time Event: 2004-08-16 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-07-16 00:00:00, Event: Post-Recovery

Comments: Data file downloaded

Time Event: 2004-07-16 00:00:00, Event: Post-Recovery

Comments: Data file downloaded

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

Comments: Ready for deployment

Time Event: 2004-02-17 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2004-02-17 00:00:00, Event: Prepared

Comments: Ready for deployment

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

Comments: Ready for deployment

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

Comments: Ready for deployment

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

Comments: Ready for deployment

Time Event: 2003-11-07 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2003-11-07 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2003-11-07 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2003-11-07 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2003-11-07 00:00:00, Event: Prepared

Comments: Ready for deployment

Time Event: 2003-11-07 00:00:00, Event: Prepared

Comments: Ready for deployment