Latest revision 9 October 1998

          Bad LAD 5 Data on TJD 11051

 TJD 11051 = 26 August 1998

At the beginning of TJD 11051, the count rates in both DISCLA and
CONTINUOUS data for LA Detector 5 were much too high.  The reason is 
unknown, but the incident occurred soon after BATSE was turned on again
on TJD 11050 following an interval of GRO spacecraft attitude control 
problems later attributed to an incorrect solar ephemeris.

The bad high count rates began during a data gap (during which there was
no predicted SAA passage) spanning the day boundary, beginning at 
  TJD/SoD = 11050/86096  and ending at  TJD/SoD = 11051/00179.
Before the data gap, the rates had been normal.  The count rates returned
to normal after the the voltages were turned off for an SAA passage at
  TJD/SoD = 11051/01994  and turned on at TJD/SoD = 11051/03190.
In the DISCLA data, the high count rates in Det. 5 seemed to be primarily
in channels 1 and 2.  In the CONTINUOUS data, the channel range was not
investigated but the high rates definitely appear in one or more of 
channels 3 - 5.

No Quality Flag 75 was set for the interval with high count rates in LAD 5.
Quality Flag 78 was set beginning SoD 1950 because of the increasing
background count rates in all detectors for the SAA.

Trigger 7019 occurred at TJD/SoD = 11051/01961, i.e., during the interval
of bad high rates in LAD 5; the triggering detectors (DSELB) were 5 and 7.
The trigger was labeled as "Unknown".  It seemed to be a coincidence
between a spike in det. 5 and a fluctuation in det.7; also, the background
count rates were increasing for all detectors because of the approach to
the SAA.