FKB/AERI/M1 - Hatch controller failure

Hatch controller did not report correctly during entire deployment, likely due to a failed 
monitoring switch in unit.  Please review monthly mentor reports for information on when the 
hatch was open or closed.

• hatchOpen

• hatchOpen

• hatchOpen

• hatchOpen

FKB/MWRHF/M1 - Dew formation on window

During night time, when the humidity is very high (RH ~ 100%) data are strongly affected 
by dew formation on the window. 
This results in a smooth and large (80-150 K) increase of the brightness temperature from 
early night to sunrise. Data are affected mostly at night.

• Sky brightness temperature (90 GHz)(tbsky90)
• Sky brightness temperature (150 GHz)(tbsky150)

FKB/MWRHF/M1 - Reprocess: Surface Relative Humidity too low

The surface relative humidity readings are too low when compared with the MWRP and the 
tower sensor.

• Humidity, relative(rh)

FKB/NFOV/M1 - Intermittent problem with channel 870

At times channel 870 is erratic.  Fortunately, it is mostly at night when it is not 
functioning properly.  The erratic behavior is infrequent until Sept when it becomes a bit more 
frequent.  Even then, however, very little daytime data are affected.

• Calibrated Zenith Radiance, 870nm(radiance_870nm)
• raw_counts_870nm

FKB/ECOR/M1 - Flux Data Suspect For Some Wind Directions

For some wind directions the horizontal fetch was not representative of the field in which 
the AMF was located.  Therefore, for the wind direction ranges 
40-159 and 176-209 degrees, the fluxes are affected by insufficient fetch and  surfaces, 
buildings, and vegetation that are not similar to the local field conditions.

• friction velocity(ustar)
• Latent heat flux(lv_e)
• Corrected sensible heat flux(h)
• CO2 flux(fc)

FKB/MWRHF/M1 - Questionable calibration

The instrument completed a tip curve calibration on June 30 and it did not calibrate again 
until Oct 13. Data during this time display large residuals (~ 6 K) when compared with 
model computations. It is likely that the tip curve calibration, although successful, 
wasn't good enough to have good accuracy.

Since this instrument is still under testing the users should use the data with caution. 
Although the accuracy of the model itself is still debated, large residuals between the 
measurements and the model between June and October are probably in large part due to the 
poor calibration.

• Sky brightness temperature (90 GHz)(tbsky90)
• Sky brightness temperature (150 GHz)(tbsky150)