GoMoos Sensor History for Sensor: CAMAT042
- Manufacturer: Campbell,
Model: 107_L
Purchase Date: 2009-07-17
Deployed on Mooring: M0134
- Mooring Details: from 2025-07-30 00:16:00 to 0000-00-00 00:00:00
- Time Event: 2025-07-30 00:16:00, deployed by the M/V James K Goodwin
- Data_type: air_temperature and Depth: -3 m
Deployed on Mooring: M0131
- Mooring Details: from 2021-06-12 03:21:00 to 2021-11-04 10:49:00
- Time Event: 2021-06-12 03:21:00, deployed by the R/V Connecticut
Time Event: 2021-11-04 11:49:00, recovered by M/V Warren
- Data_type: air_temperature and Depth: -3 m
Deployed on Mooring: M0130
- Mooring Details: from 2020-11-08 21:05:00 to 2021-04-09 14:00:00
- Time Event: 2020-11-08 20:50:00, Redeployed by R/V Connecticut
Time Event: 2020-11-08 20:51: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-04 00:54:00, SUNAs and IMS begin missing data and becoring badly intermittent. Some noise and corruption.
Time Event: 2021-03-24 20:00:00, Buoy is no longer anchored, slowly moving with all subsurface instruments still reporting. Data flagged as off-station.
Time Event: 2021-04-09 14:00:00, Buoy intercepted by R/V Determination Marine. Subsurface instruments recovered from wire and buoy was towed back to SW Harbor
- Data_type: air_temperature and Depth: -3 m
Deployed on Mooring: M0129
- Mooring Details: from 2019-07-29 16:35:00 to 2020-11-08 16:02:00
- Time Event: 2019-07-29 12:35:00, redeployed by R/V Connecticut
Time Event: 2020-11-08 16:02:00, Recovered by R/V Connecticut
- Data_type: air_temperature and Depth: -3 m
Deployed on Mooring: M0128
- Mooring Details: from 2018-07-09 14:55:00 to 2019-07-27 23:30:00
- Time Event: 2018-07-09 14:55:00, deployed by R/V Connecticut
Time Event: 2019-07-27 23:30:00, recovered (adrift) by the R/V Connecticut
Time Event: 2019-07-19 23:00:00, Mooring has broken free of its anchor and is adrift. All data after this date has been flagged as off-station.
- Data_type: air_temperature and Depth: -3 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
- Data_type: air_temperature and Depth: -3 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.
- Data_type: air_temperature and Depth: -3 m
Deployed on Mooring: M0125
- Mooring Details: from 2015-11-05 04:05:00 to 2016-10-08 11:50:00
- Time Event: 2015-11-05 23:05:00, Redeployed (turnaround) by the R/V Connecticut
Time Event: 2016-10-08 11:50:00, Recovered by R/V PISCES
- Data_type: air_temperature and Depth: -3 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
- Data_type: air_temperature and Depth: -3 m
Deployed on Mooring: M0123
- Mooring Details: from 2014-05-31 14:10:00 to 2014-09-18 16:10:00
- Time Event: 2014-05-31 14:10:00, Redeployed by R/V Connecticut.
Time Event: 2014-09-18 16:10:00, Recovered by R/V Connecticut.
- Data_type: air_temperature and Depth: -3 m
Deployed on Mooring: M0122
- Mooring Details: from 2013-06-23 16:34:00 to 2014-05-31 11:00:00
- Time Event: 2013-06-23 16:34:00, Redeployed by R/V Connecticut.
Time Event: 2014-03-21 12:25:00, Last backup Goes transmission received from buoy. Since the primary Iridium system failed in Jan 2014, no data are presently being received from this site.
Time Event: 2014-05-06 16:15:00, Vist to buoy M01 by R/V Osprey. Considerable water found in well; battery failed. Removed control box; installed trackpack. Air, visibility and RMYoung had been damaged.
Time Event: 2014-05-31 11:30:00, Recovered by R/V Connecticut.
- Data_type: air_temperature and Depth: -3 m
Deployed on Mooring: M0121
- Mooring Details: from 2012-10-25 14:05:00 to 2013-03-30 19:35:00
- Time Event: 2012-10-25 14:05:00, Redeployed by R/V Connecticut
Time Event: 2013-02-09 16:30:00, Buoy is no longer anchored and has drifted off station. Instruments are still reporting but data may not be from the anchor location.
Time Event: 2013-03-30 19:35:00, Recovered by M/V Scarlett Isabella (buoy and top part of the mooring which broke free in early February 2013).
- Data_type: air_temperature and Depth: -3 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
- Data_type: air_temperature and Depth: -3 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
- Data_type: air_temperature and Depth: -3 m
Deployed on Mooring: M0117
- Mooring Details: from 2010-06-09 13:05:00 to 2011-06-03 14:28:00
- Time Event: 2010-06-09 13:05:00, Redeployed by R/V Argo Maine.
Time Event: 2011-06-03 14:28:00, Recovered by R/V Connecticut.
- Data_type: air_temperature and Depth: -3 m
Non-Deployment Sensor Events:
- Time Event: 2017-01-27 00:00:00, Event: Prepared
- Comments: Ready for deployment
- Time Event: 2016-04-05 00:00:00, Event: Prepared
- Comments: Ready for deployment
- Time Event: 2014-01-16 00:00:00, Event: Prepared
- Comments: Ready for deployment
- Time Event: 2013-02-11 00:00:00, Event: Prepared
- Comments: Ready for deployment
- Time Event: 2001-01-01 00:00:00, Event: Prepared
- Comments: Ready for deployment