CIMSS Satellite Blog

GOES-12 visible images

We received the following question on 02 October 2008:

Hello: I sometimes look at the GOES-12 vis nightime images even though they are usually devoid of any light of course. The 03:15 image tonight, however, is showing a meteor-type streak with a comet-like head and tail. I wonder, though, if GOES can actually detect a rapid transient event such as a meteor - or is this some sort of internal reflection caused by another light source or process? Many thanks! Rob Jackson, Hampton, NH

Excellent question, Rob! A sequence of GOES-12 visible images every day at 03:15 UTC from 27 September through 02 October 2008 (above) revealed that an increasing amount of “stray light”  was finding its way to the satellite’s instrument detectors just prior to the time when the GOES-12 satellite was entering the Fall “eclipse period” (when the satellite passes through the Earth’s shadow). During such Spring and Fall season eclipse periods, imagery from the satellite is interrupted, since the solar panels cannot generate the power needed to operate the various instrument packages.

An example of stray light affecting GOES-12 imagery during a Spring season eclipse period can be seen here.

Beginning with GOES-13, larger batteries on-board the satellite allow the instruments to operate through the eclipse periods (when the satellite is still in the Earth’s shadow). However, while imagery is available through the eclipse period, it is still vulnerable to small amounts of stray light which can affect the accuracy of any images or products. An animation of night-time GOES-13 visible imagery (below) shows the impact of stray light during the eclipse period (during that same time period, no imagery was available from GOES-12 between 03:32 UTC and  06:45 UTC).

GOES-13 visible images

Tony Cristaldi at the National Weather Service forecast office at Melbourne, Florida pointed out an interesting feature to us: a clockwise-rotating vortex over the Atlantic Ocean, located just north of the Equator off the northeast coast of Brazil. An animation of GOES-12 visible and 3.9 µm shortwave IR images (above; QuickTime animation) shows the feature as it moved westward on 26 June and 27 June 2008 (producing brief pulses of convection on both days). So, the Question of the Day is: if this was a Mesoscale Convective Vortex (MCV) that was spawned by convection over the tropical Atlantic Ocean, and it was found in the Northern Hemisphere, then wouldn’t such a feature be expected to exhibit a counterclockwise (or “cyclonic” in the Northern Hemisphere) rotation?

The answer to that question (provided via email from the bright minds of Brian Etherton at the University of North Carolina at Charlotte and Brad Barrett at the University of Oklahoma): since this mesoscale circulation possessed a small radius of curvature (implying a large Centrifugal Force) and was located near the Equator (implying a small Coriolis Force), then the flow (as governed by the Gradient Wind Balance equation) would be cyclostrophic (a balance between only the Pressure Gradient Force and the Centrifugal Force) — so the direction of flow into such a circulation could be either cyclonic (counterclockwise in the Northern Hemisphere) or, as in this particular case, anticyclonic (clockwise in the Northern Hemisphere).

In an attempt to identify the source of this curious vortex, we examined GOES-12 visible and shortwave IR imagery at 3-hour intervals during the 23-27 June period (below; QuickTime animation). The imagery seems to suggest that the source of the vortex may have been an area of convection over the tropical Atlantic Ocean, which developed just south of the Equator (centered around 1.5º S / 28.0º W) on 24 June. This convection produced a well-defined outflow boundary, which could be seen propagating northwestward on the 11:45 and 14:45 UTC visible images on 24 June. The vortex first becomes apparent on the 17:45 UTC visible image on 24 June, located some distance behind (south of) the aforementioned outflow boundary. From that point, the vortex is then difficult to follow due to other cloudiness in the region, until it is again obvious on the 11:45 UTC visible image on 26 June (located near 0.5º N / 33.5º W). After 26 June, the feature is more easily tracked using the 30-minute interval images shown above.