Introduction

Electrification of volcanic ejecta is a consequence of particle-scale interactions directly at the vent and at higher altitude within ash-rich volcanic plumes (Mather and Harrison 2006). Electrical breakdown in volcanic clouds leads to lightning discharges, some of which can be measured by long-range detection systems operating in the 3–30 kHz band. The emergence of global lightning networks has made a baseline of volcanic eruption detection possible, even in remote regions. The drawback of the global networks is that only the most energetic strokes can be detected, which do not necessarily reflect the near-vent charging process (Behnke and McNutt 2014). Less energetic activity, such as continual radio frequency emissions, requires a lightning mapping array to be installed locally (Thomas et al. 2007; Behnke et al. 2018). Detections of volcanic lightning, in addition to their value for monitoring, also offer a window into the dynamics of volcanic plumes (Behnke and Bruning 2015; Van Eaton et al. 2016).

Recent major eruptions in Alaska have produced detectable volcanic lightning on both local and global lightning sensors, including the 2006 Augustine (Thomas et al. 2007) and 2009 Redoubt (Behnke et al. 2013; Behnke and McNutt 2014) eruptions. Bogoslof, a mostly submarine volcano in the Bering Sea, Alaska, produced a prolific amount of volcanic lightning during its eruption sequence from December 2016 to August 2017 (Van Eaton et al. 2020), which was detected globally. Coombs et al. (2019) provide an overview of the entire eruption sequence. Detections on global lightning networks were used in real time at the Alaska Volcano Observatory for monitoring the eruption of Bogoslof (Coombs et al. 2018). In fact, of the 70 explosive events that occurred over the course of the eruption, 31 produced lightning detected on global networks (Van Eaton et al. 2020) and one event was detected by volcanic lightning only (Coombs et al. 2018).

Although volcanic lightning has received a great deal of attention in recent years, the associated phenomenon of volcanic thunder had not been documented until the Bogoslof eruption (Haney et al. 2018). This is in contrast to meteorological thunder, which has been studied using combined lightning and infrasound data sets (Assink et al. 2008; Johnson et al. 2011; Arechiga et al. 2014). The omission for the volcanic case is in large part due to the difficulty of unequivocally identifying thunder signals in acoustic data during eruptive activity, since eruptions themselves radiate intense sound waves due to the ejection of magmatic products at the vent. For the Bogoslof eruption, an array of microphones located 60 km from the volcano allowed precise direction-of-arrival information to be derived from acoustic waves during the eruption. Analysis of the directional information indicated some of the sound waves originated from a different direction than the volcanic vent, thereby implicating thunder as their source (Haney et al. 2018). Moreover, the distance of the microphone array from the volcano (60 km) placed it within the range where measurements of thunder signals can be expected (Campus and Christie 2009).

Volcanic thunder turns out to be only one manifestation of volcanic lightning in ground-based geophysical data streams, such as infrasound data. In their study of Tungurahua Volcano in Ecuador, Anderson et al. (2018) highlighted the occurrence of electromagnetic pulses in infrasound data due to volcanic lightning. Similar glitches were observed in seismic data during the 1992 eruption of Mount Spurr by McNutt and Davis (2000). Arechiga et al. (2014) also noticed this phenomenon in a study of meteorological lightning and referred to it as electromagnetic interference pickup. We refer to these electromagnetic pulses as glitches throughout this paper, since they appear as high-amplitude interruptions in the geophysical data streams. They are noise insofar as they interfere with geophysical data, but we use them here as signal to analyze the occurrence of volcanic lightning, as done previously by Anderson et al. (2018). In the following sections, we apply a detection algorithm to continuous acoustic data to produce a lightning catalog based on glitches for the entire Bogoslof eruption. We also present new observations of volcanic thunder not examined previously by Haney et al. (2018) and investigate the source of lightning-related signals measured on a moored hydrophone on the northeast slope of Bogoslof. Taken together, these observations give a more complete picture of electrical activity during the 2016–2017 Bogoslof eruption and provide further insight into the imprint of volcanic lightning on geophysical data streams. Such knowledge can be used in real-time monitoring of explosive volcanic eruptions worldwide, in order to detect the occurrence of volcanic lightning as early as possible.

Data and methods

We focus primarily on acoustic data from a 4-element microphone array named OKIF on the eastern slope of Okmok Volcano (Fig. 1). These data have also been analyzed and described by Fee et al. (2020), Lyons et al. (2019, 2020), and Schwaiger et al. (2020b). Here, the four individual elements are referred to as OK01, OK02, OK03, and OK04. At the time of the eruption, the sensors comprising the array were Chaparral 25Vx microphones sampled in time at 100 Hz and each sensor was connected to a wind reduction system consisting of a series of porous hoses (Petersen et al. 2006). The 100-Hz sample rate means that both infrasound (< 20 Hz) and audible acoustic (> 20 Hz) signals are recorded. The digitizer is located near the central node (OK04) and the other three elements (OK01, OK02, and OK03) are connected to the digitizer via shielded Okonite cabling set beneath thick vegetation, but not buried in soil. The array has an aperture of approximately 100 m and has a triangular shape with one of the array elements at the center (OK04). In addition to the Okmok microphone array, we also analyze data from a moored hydrophone located 7 km to the northeast of Bogoslof (Fig. 1). The hydrophone instrumentation is similar to the deployment described by Bohnenstiehl et al. (2013).

Fig. 1
figure 1

Regional map of Bogoslof volcano and neighboring islands with inset showing the location of Bogoslof in the Alaska region. The microphone array located on the eastern slope of Okmok volcano is indicated with a yellow star. A red square shows the location of a moored hydrophone 7 km northeast of Bogoslof

At a range of 60 km from the volcano, the four-element Okmok array is the closest microphone array to Bogoslof in the AVO network. In fact, the data from the Bogoslof eruption at the Okmok array are among the closest microphone array recordings of any volcanic eruption in Alaska. Only the array located at frequently active Cleveland volcano in Alaska has captured explosive activity at closer range (15 km). Thus, although the wind and temperature structure of the atmosphere can strongly affect sound propagation over the 60 km range from the Okmok array to Bogoslof (Schwaiger et al. 2020a; Iezzi et al. 2019; Schwaiger et al. 2020b), the recordings give a rare opportunity to make detailed array measurements of the acoustic wavefield from a shallow submarine eruption.

We process the acoustic waves measured on the Okmok array using least-squares beamforming (Olson and Szuberla 2005). In this method, we cross-correlate all possible pairs of acoustic elements and find the time-delay corresponding to the maximum value of normalized cross-correlation. When the normalized cross-correlation exceeds a certain value (e.g., 0.5), we accept the time-delay measurement as being of high quality. If enough delay times meet this criterion to uniquely determine a slowness vector, we form a vector of the delay times and linearly relate them to apparent slowness across the array:

$$ \overrightarrow{\Delta \mathrm{t}}=\mathrm{G}\overrightarrow{\mathrm{s}}=\mathrm{G}{\left[{\mathrm{s}}_{\mathrm{NS}},{\mathrm{s}}_{\mathrm{EW}}\right]}^{\mathrm{T}} $$
(1)

where sNS and sEW are the values of apparent slowness in the north-south and east-west directions, respectively, and G is the matrix of apparent distances (Johnson et al. 2013; Haney et al. 2018). For the four-element Okmok array, as many as six delay time measurements could contribute to the lefthand side of eq. (1). Thus, G could be as large as a 6-by-2 matrix. To find the apparent slowness across the array, we multiply both sides of eq. (1) by the transpose of G and solve the equation in the least-squares sense. Once sNS and sEW have been obtained, we find the trace velocity across the array using

$$ \mathrm{v}=1/\sqrt{{\mathrm{s}}_{\mathrm{NS}}^2+{\mathrm{s}}_{\mathrm{EW}}^2} $$
(2)

and the backazimuth θ with

$$ \uptheta ={\tan}^{-1}\left({\mathrm{s}}_{\mathrm{EW}}/{\mathrm{s}}_{\mathrm{NS}}\right) $$
(3)

where error estimates can also be found on these parameters (Szuberla and Olson 2004). An additional consideration for beamforming is choice of frequency band. Previously, Haney et al. (2018) beamformed acoustic data in the 4–8 Hz band to detect volcanic thunder. Such a choice was a tradeoff between higher frequencies with better signal-to-noise for thunder versus the use of lower frequencies for which good coherence can be maintained across the microphone array. In the Results section, we show beamforming over several frequency bands to illustrate which parts of the spectrum are dominated by the eruptive source versus volcanic thunder.

In addition to beamforming, we process the microphone array data with a multichannel short-term average/long-term average (STA/LTA) filter to detect broadband electromagnetic pulses, or glitches, induced by lightning. The electromagnetic pulse associated with lightning represents a strong disturbance in the electric field that propagates outward at the speed of light. This is the same disturbance measured directly by sensors in global lightning location networks, including the GLD360 operated by Vaisala (Said et al. 2010) and the World Wide Lightning Location Network or WWLLN (Hutchins et al. 2012). The propagating disturbance can in turn interfere with geophysical equipment such as cabling, leaving a characteristic imprint on the data stream. For comparison to lightning data, we utilize both WWLLN and GLD360 catalogs for the Bogoslof eruption in our analysis. Both catalogs provide location (latitude and longitude) and origin times of detected strokes, with the GLD360 catalog additionally giving measurement of lightning peak current and polarity. Additional network details are provided in Van Eaton et al. (2020).

We detect glitches on the Okmok microphone array by applying the STA/LTA filter to the envelope of the acoustic data in the 35–45 Hz band. We choose this frequency band since it is where the glitches have the highest signal-to-noise ratio (SNR), with other forms of low-frequency acoustic signal or noise (e.g., background noise, Bogoslof events) being diminished in this band. Since the Okmok data are sampled at 100 Hz, we are only able to analyze the glitches up to 50 Hz; it is possible that the glitches have even better SNR in higher-frequency bands. Wind noise is a persistent problem in all frequency bands and, when it is present, detections of the glitches are hindered. For the length of the STA and LTA time windows, testing on individual glitches has shown that 0.5 and 2.5 s, respectively, yield accurate timing since the duration of the glitches is on the order of 1 s or less. A trigger is declared when the STA/LTA ratio exceeds a particular value for three of the four elements of the Okmok microphone array, and when there has been no trigger for 1 s previously. In a subsequent quality control step, we also require that a trigger has a maximum over a time window from 2 s before the trigger to 4 s after that occurs within ± 0.4 s of the trigger time. These last steps result in triggers that are relatively well-recorded and isolated from other triggers. However, there is the possibility that multiple glitches closely spaced in time are filtered out.

As a result of the sample rate of the acoustic data and the typical time duration of the glitches, it is correct terminology to associate each glitch with a lightning flash event (i.e., from one to several strokes) and not an individual stroke. There is the possibility for several strokes to comprise a single lightning flash, and we do not have the time resolution from the glitches to discern individual strokes occurring within the time period of a glitch. Thus, when we refer to the lightning detected by the glitches, we use the term lightning flash. In contrast, we refer to lightning detected by the global lightning catalogs as lightning strokes, since individual strokes in those catalogs have not been grouped into flashes.

Results

Before discussing volcanic lightning catalogs derived from electromagnetic glitches, we first describe a new observation of volcanic thunder from the Bogoslof eruption that was not investigated in Haney et al. (2018). We focus on the eruptive event of May 17, 2017 (event 39), which was the first activity at Bogoslof following a 2-month-long hiatus. The main portion of the event lasted for over an hour and was clearly recorded on the Okmok microphone array. In Fig. 2, we plot several parameters from this event derived from acoustic and lightning data. Figure 2 a–c show detections from least-squares beamforming in 3 non-overlapping frequency bands: 1–2 Hz, 2–4 Hz, and 4–8 Hz. We plot backazimuth of the detection from the array, with a backazimuth of 0° pointed toward the volcano. Negative backazimuths correspond to locations to the west of Bogoslof, and positive backazimuths indicate eastward locations. Backazimuths to the lightning locations from the Vaisala catalog, relative to the Okmok array, are shown in Fig. 2d. To simplify the plot, we have only shown backazimuths for lightning strokes with absolute values of peak current greater than 5 kA. We take this approach because Haney et al. (2018) showed that volcanic thunder should only be measurable at the Okmok array for lightning strokes exceeding that peak current value. Strokes with smaller peak current are not expected to produce measurable volcanic thunder at 60-km range, since lightning peak current has been shown to scale with acoustic power (Assink et al. 2008). The yellow shaded time periods in Fig. 2a–d are from Wech et al. (2018) and indicate when the volcano was inferred to be actively erupting. Finally, Fig. 2e is a spectrogram of the acoustic data from the central element of the array (OK04).

Fig. 2
figure 2

Measurements from the May 17, 2017 eruptive event, indicating the occurrence of volcanic thunder. ac Backazimuths of detections on the Okmok microphone array in 1–2, 2–4, and 4–8 Hz bands. d Backazimuths relative to the Okmok microphone array of GLD360 lightning locations with peak current greater than 5 kA. In ad, a backazimuth of 0° points at Bogoslof. Yellow regions in ad are times of eruptive activity from Wech et al. (2018). Red arrows in b show moveout of volcanic thunder signals. The lightning origin times are delayed by their GLD360 location assuming a nominal acoustic speed of 335 m/s. e A spectrogram of acoustic data from the central element of the array

As seen in Fig. 2, the different frequency bands are sensitive to sources with varying backazimuths over the course of the eruptive event. We conclude from Fig. 2a that the lowest frequency band from 1 to 2 Hz is dominated by the volcanic eruption process related to mass ejection at the vent. The times of detections in Fig. 2a match closely with the eruption times shaded in yellow from Wech et al. (2018). In fact, the existence of coherent low frequency infrasound from Bogoslof was the basis for the interpretation of eruption activity by Wech et al. (2018). Figure 2b shows that the 2–4 Hz band is sensitive to the same eruptive process as in Fig. 2a; however, it is also sensitive to another phenomenon which continues in the two time periods after the volcano stops erupting (marked with red arrows in Fig. 2). We interpret this pattern as being due to volcanic thunder continuing in the eruption plume after activity has ceased. We base this partly on the patterns observed by Haney et al. (2018), but also on the fact that the backazimuths systematically shift toward the west as indicated by the red arrows. The shift to the west agrees with the backazimuths of lightning strokes relative to the Okmok array in Fig. 2d. The westward shift also agrees with radiosonde measurements of wind direction collected at Cold Bay, Alaska. In particular, note that by 8:00 UTC the backazimuths in Fig. 2b and d have both deviated from the direction of the volcano by 30°, clearly indicating that the signals are not being produced at the volcanic vent. This is a much larger backazimuth deviation than observed for the June 10 event by Haney et al. (2018), which was on the order of 3°. The time moveout of the red arrows in Fig. 2b is approximately 2° per minute, which corresponds to a speed of ~ 10 m/s for a source at 60 km range. Figure 2c shows that in the 4–8 Hz band, volcanic thunder dominates over eruption infrasound, since the same backazimuth patterns for thunder are present as in Fig. 2b. Especially interesting is that the 4–8-Hz detections begin at a time coincident with the onset of lightning detections (Fig. 2d). This suggests that the primary source of infrasound in this frequency range for event 39 was from volcanic thunder. Note that such frequency partitioning is not necessarily the same for each eruptive event. As shown by Haney et al. (2018), the June 10, 2017 eruptive event generated significant infrasound in the 4–8 Hz band prior to the onset of lightning due to the eruptive process. The May 17 eruptive event had overall lower frequency content than the June 10 eruption, enabling volcanic thunder to be even more visible in the 4–8 Hz band. This constitutes the third documented instance of volcanic thunder during the Bogoslof eruption, the others occurring on March 8 and June 10, 2017 (Haney et al. 2018).

In Fig. 3, we plot spectrograms of the 4 elements of the microphone array during the 15–20 min following the cessation of eruptive activity on May 17. This is the time period when the backazimuths of acoustic detections dramatically shifted to the west. The diffuse signals between 0 and 20 Hz during the time period from 7:55 to 8:00 UTC are excellent examples of individual volcanic thunder claps. However, there are impulsive broadband signals during this time period, three of which are indicated by arrows in Fig. 3. We interpret these as the electromagnetic glitches caused by volcanic lightning, similar to the ones reported by Anderson et al. (2018). Prior to 7:55 UTC in Fig. 3, there are a multitude of these glitches and they only become easily individually identifiable in the plot after 7:55 UTC. A couple basic properties of the glitches are apparent in Fig. 3. First, although the glitches are broadband, they have a particularly high signal-to-noise ratio in the 35–45 Hz band. In this high-frequency band, other signals are comparatively absent. Secondly, the glitches show up most clearly on element OK01, less clearly on elements OK02 and OK03, and are not even discernable on element OK04.

Fig. 3
figure 3

Waning portion of the May 17, 2017 eruption (event 39) showing broadband glitches on elements 1–3 of the microphone array. The three final electromagnetic pulses from lightning, or glitches, are indicated with arrows

This pattern of relative amplitudes among the four elements of the array was observed for glitches throughout the Bogoslof eruption and has a simple explanation based on the geometry of the Okmok microphone array, as shown in Fig. 4. Volcanic lightning mostly occurred to the north of the array, within ~30 km radius of Bogoslof (Van Eaton et al. 2020). The northerly origin of the lightning maximizes the apparent length of the cable run from the digitizer (closely located to central element OK04) to OK01 in the direction of the lightning. The longer apparent distance from OK01 to OK04 translates into a larger voltage drop across the ends of the cable, as induced by the electromagnetic pulse of the lightning (Petrache et al. 2005; Paolone et al. 2005), than the voltages induced on the shorter apparent distances of the OK02–OK04 and OK03–OK04 cable runs. Since OK04 is itself virtually co-located with the digitizer, negligible voltage is induced. From the geometry of the array, we can estimate that the induced voltage on element OK01 should be approximately twice the induced voltages on OK02 and OK03. Shown in the inset of Fig. 4 is an example of a single electromagnetic glitch on all four elements during the June 10, 2017 eruption. Indeed, in agreement with the estimate, the amplitude of the glitch on OK01 is about two times larger than on OK02 and OK03. No glitch is evident on element OK04. These patterns suggest that a controlling factor of the glitch amplitude was the projection of the cable run in the direction of the lightning flash, an idea also invoked by McNutt and Davis (2000) to explain glitches in seismic data during the 1992 eruption of Mount Spurr.

Fig. 4
figure 4

Schematic of the Okmok microphone array and representative glitch signal from the June 10, 2017 eruption (event 48). The microphone array has an aperture of approximately 100 m. Text within the figure provides a first-order explanation for the relative amplitudes of the glitches on the four elements of the microphone array

Here, we exploit the occurrence and pattern of glitches for the bulk processing of the four Okmok array elements over the entire 9-month-long Bogoslof eruption sequence, with the goal of defining a lightning catalog for Bogoslof based on glitches. To detect the glitches, we use the STA/LTA approach discussed previously and widely used in producing event triggers and automatically picking first breaks in seismic data processing. We apply the algorithm to envelopes of 35–45 Hz bandpassed acoustic data on the Okmok array. We have computed two different catalogs: one requiring an STA/LTA ratio of 2.8 to trigger, called Glitch Catalog A, and the other using a lower value of 2.3 for the ratio, called Glitch Catalog B. The value of 2.3 is the same as used in standard real-time processing of seismic data at AVO (Dixon et al. 2013) and will generally yield more detections than the value of 2.8. A detail is that the STA/LTA algorithm we employ also requires a quiet time before a trigger (1 s), and so in some rare cases, the use of a lower STA/LTA triggering ratio can result in a new trigger being generated immediately before a trigger obtained with a higher ratio, thereby arresting the later trigger. However, in general, lower values of STA/LTA ratio result in more triggers. The tradeoff in the two catalogs is that Glitch Catalog A, which uses the ratio of 2.8, has fewer false detections. Glitch Catalog B, with a ratio of 2.3, detects more glitches and is preferable for retrospective data analysis, but results in more false detections (i.e., false alarms). Thus, the STA/LTA ratio used in Glitch Catalog A would likely be better suited for real-time implementation, when false alarms are a greater concern. We discuss and analyze both catalogs in the remainder of this section.

The application of the STA/LTA detector over the entire Bogoslof eruption results in 514 triggers for Glitch Catalog A and 1309 triggers for Glitch Catalog B. Of the 514 and 1309 raw triggers for the two catalogs, 399 and 814 triggers, respectively, occur during time periods of volcanic lightning already known from the existing WWLLN and GLD360 catalogs. As a result, we conclude these are true detections, since they are at times when volcanic lightning was known to be occurring. We define these time windows for each of the 31 Bogoslof events with WWLLN or GLD360 lightning based on the first and the last strokes from the combined WWLLN/GLD360 catalog. However, for Glitch Catalog A, we have examined the raw triggers that occurred outside of these time windows and find that 23 of the remaining 115(=514-399) triggers are in fact new volcanic lightning flashes not represented in the WWLLN/Vaisala catalogs. For Glitch Catalog B, we find that 45 of the remaining 451(=1309-814) triggers are new volcanic lightning flashes. We discuss some of these new flashes later in this section. In fact, four of the new flashes occurred during an eruptive event for which no strokes were detected in the WWLLN or GLD360 catalogs (event 56 on July 2, 2017). Thus, Glitch Catalog A finally consists of 422 total volcanic lightning flashes (422/518 or 81% detection success rate), and Glitch Catalog B consists of 859 (859/1309 or 66% detection success rate). Table 1 gives a summary of the number of detections for both catalogs over all Bogoslof events with glitches.

Table 1 Eruptive events with glitch-detected flashes compared to WWLLN catalog

The remaining glitch triggers are false detections insofar as we cannot unequivocally associate them with instances of volcanic lightning. Many of them are related to meteorological lightning that occurred over the course of the 8-month-long eruption. Meteorological lightning is rare in the Aleutian Islands compared to other regions; however, a significant meteorological lightning storm occurred in the Aleutians on July 16 and 17, 2017 and contributed many of the false detections. A small amount of meteorological lightning occurred at a low background rate throughout the 8 months as well. We hold off on addressing the possibility of filtering out these detections of meteorological lightning for future work.

In Fig. 5, we plot envelopes of all 422 glitch detections comprising Glitch Catalog A in a 6-s time window around the glitch (2 s pre-trigger and 4 s post-trigger). By taking the mean over all the glitches, we obtain the average envelopes shown in Fig. 6. The average envelopes bear out the relative amplitude pattern discussed previously; namely, that glitches on element OK01 are on average larger than OK02 and OK03, and that glitches barely exist on OK04. Note that the amplitude on element OK02 is slightly larger than OK03 in Fig. 6. This may be due to the average backazimuth of volcanic lighting over the entire eruption coming from the direction of Bogoslof, which is roughly 8° west of north. The overall preference for incident azimuths coming slightly from the west increases the apparent distance along the OK02 cable run relative to OK03, thereby increasing the average glitch amplitude. Also note that the glitch amplitude on OK01, being close to 200 counts, corresponds to an induced voltage of approximately 0.5 mV given the digital conversion of the Q330 digitizer at the Okmok array of 419,430 counts/V. We note this value but do not currently have a model to explain the coupling of the propagating electromagnetic field from the lightning flash with the induced voltage, like the one discussed in Petrache et al. (2005) and Paolone et al. (2005). We note that Paolone et al. (2005) apply the theory presented by Petrache et al. (2005) to analyze data from lightning-induced voltages in a buried, shielded cable.

Fig. 5
figure 5

Glitch detections on the Okmok microphone array over a time period covering the entire eruption from December 1, 2016 to September 1, 2017. Envelopes of 35–45 Hz bandpassed acoustic data are plotted with time relative to the STA/LTA trigger onset. As seen in Fig. 4, the glitches are strongest on element OK01 and virtually nonexistent on element OK04

Fig. 6
figure 6

Average envelopes of the glitch detections shown in Fig. 5 for each of the four elements of the Okmok microphone array. The glitch envelope on OK01 is on average approximately twice as large as on OK02 and OK03

Shown in Fig. 7 are time histories of glitch peak amplitude for two of the Bogoslof events, using Glitch Catalog B. In Fig. 7a and b, glitch detections are plotted for the January 31, 2017 eruption (event 29) and May 17, 2017 eruption (event 39), respectively. The yellow shaded areas are the time windows determined from the first and last volcanic lightning strokes in the combined WWLLN/GLD360 catalog. Several new flashes are detected about 10 min before the WWLLN/GLD360 time window for the May 17 event. No such early flashes are found for the January 31 event; however, the glitch catalog includes several flashes prior to 8:00 UTC which were not detected by WWLLN. For the May 17 event, reanalysis of raw GLD360 data with the requirement of only two sensors for detection revealed additional earlier strokes than indicated in Fig. 7 (Van Eaton et al. 2020). The earliest two-sensor GLD360 detection on May 17 occurred at 6:43 UTC (Van Eaton et al. 2020), which falls between the earliest detections in Glitch Catalog B (6:42:02.26 UTC) and Glitch Catalog A (6:44:14.48 UTC).

Fig. 7
figure 7

Peak amplitude of glitch detections versus time for two explosive eruptions of Bogoslof on January 31 (event 29) and May 17 (event 39), 2017. The glitch peak amplitude on OK01 is plotted on the y-axis, although a and b are at different scales. The time between the first and last stroke detected from a combined WWLLN/GLD360 catalog is shaded in yellow. Note that the glitches detected lightning flashes prior to 8:00 UTC during event 29, which were not detected by WWLLN. The glitches detected several flashes on May 17 in the minutes before the initial stroke in the combined WWLLN/GLD360 catalog

Given the detection times in Glitch Catalog A and Glitch Catalog B, we have attempted to associate the glitches with individual strokes in the GLD360 catalog. To do so, we find the closest origin time of a GLD360 stroke to a glitch detection and associate them if they are within 1 s of each other. In this fashion, 286 of the 422 detections in Glitch Catalog A can be associated with individual GLD360 strokes. Similarly, 528 of the 859 detections in Glitch Catalog B can be associated. In Fig. 8a, we have plotted the time difference between the GLD360 origin time and the glitch detection time for the associated flashes in Glitch Catalog B. On average, the difference is observed to be a small time-delay on the order 0.1 s. We interpret this time-delay as due to the time it takes for the STA/LTA filter to be activated once encountering a glitch. In Fig. 8b, we show normalized histograms of GLD360-computed peak currents for the GLD360 strokes associated with Glitch Catalogs A and B, as well as for all the GLD360 strokes. The associated strokes are observed to be enriched in higher peak currents, suggesting that the glitches tend to be from strokes with higher peak current. This dependence is further explored in Fig. 9, which shows linear regressions on a log-log plot between glitch amplitude on all four array elements and peak current for the associated flashes in Glitch Catalog A. The regressions show a weak dependence between glitch amplitude and peak current for elements OK01, OK02, and OK03, with the scatter indicating that other factors must play a role in determining the glitch amplitude as well. Possible factors include the limited signal bandwidth (35–45 Hz) and the fact that the glitches are aliased by the 100-Hz sample rate of the digitizer.

Fig. 8
figure 8

a Time delay between glitch detections and their association in the GLD360 catalog. The overall small, positive delay time is the result of the filtering action of the STA/LTA filter and shows the precision of the relative times between the glitches and the GLD360 catalog. b Logarithmic plot of normalized histograms versus peak current for the entire GLD360 catalog (blue), the subset of the catalog associated with Glitch Catalog A (black), and Glitch Catalog B (red). The normalized histogram from the glitch-associated strokes is seen to be enriched in higher-peak-current strokes compared to the entire catalog, suggesting that the flashes detected by the glitches are preferentially stronger than the ones that were not detected. This effect also explains why Glitch Catalog A is more enriched in higher peak current strokes than Glitch Catalog B

Fig. 9
figure 9

Logarithmic regression of the root-mean-square glitch amplitude versus the GLD360 peak current. A weak positive correlation exists on OK01, OK02, and OK03, with a power law exponent of approximately 0.25. Element OK04 has less, if any, dependence since it is not as susceptible to the voltages induced by the lightning discharge. This is further evidence, in addition to Fig. 8b, that the strength of the lightning stroke has a general effect on the amplitude of the electromagnetic glitch, although other factors may exist

We show details of previously unknown volcanic lightning activity in Figs. 10 and 11 for the June 10 and July 2, 2017 eruptions (events 48 and 56). Figure 10a depicts a known volcanic lightning stroke that occurred at approximately 13:12 UTC on June 10 (detected by WWLLN and GLD360). Volcanic thunder arrives about 3 min later due to the 60 km range from Bogoslof, shortly after 13:15 UTC. Note that the signal prior to the glitch in Fig. 10a is volcanic thunder from an earlier stroke not shown in the plot. In Fig. 10b–d, we show new flashes found from glitch detections at 11:14, 11:44, and 13:25 UTC. Each of these flashes is followed by volcanic thunder about 3 min later, further confirming that the glitches are produced by volcanic lightning. The 11:14 UTC flash is particularly notable since it occurs over an hour before the first WWLLN or GLD360 detection of lightning for this event. Data from Earth Networks lightning sensors in Dutch Harbor and Adak indicate that the 11:14 UTC flash was intra-cloud, not cloud-to-ground. Although both the 11:14 and 11:44 UTC flashes occurred before the strongest phase of the June 10 event, unrest for the event started at 9:58 UTC, over an hour before the 11:14 UTC flash. This finding demonstrates that glitch detection may have allowed earlier identification of ash-producing activity for this event. Figure 11 shows four glitch detections for the July 2, 2017 eruption, an event for which there was no lightning detected by WWLLN or GLD360. Infrasound propagation between Bogoslof and the Okmok array was poor for this event, so we also plot the Okmok seismic station OKER to illustrate the strongest portion of the eruptive event. Although the first detection appears to occur near the beginning of the event, Tepp and Haney (2019) discuss the fact that subtle precursors had been ongoing for about an hour before the first glitch detection.

Fig. 10
figure 10

Examples of glitches and associated thunder signals during the June 10, 2017 eruptive event. a A glitch from a known stroke in the WWLLN/GLD360 catalogs at approximately 13:12:15 UTC. bd New flashes detected with glitches that do not exist in the WWLLN/GLD360 catalogs. In all panels, volcanic thunder is observed to arrive roughly 3 min after the glitch, further confirming the new detections in bd. In a, volcanic thunder from a stroke prior to the time window arrives before the glitch at approximately 12:12

Fig. 11
figure 11

Volcanic lightning detected from glitches during the July 2, 2017 eruption (event 56). These detections were noteworthy because no strokes exist for this event in the combined WWLLN/GLD360 catalog. Sound propagation from Bogoslof to the Okmok array was poor on July 2, and as a result, no eruptive infrasound or volcanic thunder appears in the microphone array data. Okmok seismic station OKER is included at the bottom to indicate times of strong eruptive activity

In Figs. 12 and 13, we give details of signals observed on the hydrophone at Bogoslof (Fig. 1) that coincide with volcanic lightning during the June 10, 2017 eruptive event. Figure 12 shows a high-frequency (50–300 Hz) hydroacoustic signal associated with the new lightning flash detected in the glitch catalogs at 11:14 UTC. The signal is clearly associated with the lightning flash since no other similar signals are observed during the half-hour around the time of 11:14 UTC. Previously, hydroacoustic signals associated with lightning have been reported in the Gulf of Mexico (Arnold et al. 1984; Hill 1985) and interpreted as due to lightning striking the ocean surface. We find an alternative explanation for the lightning-related hydroacoustic signals at Bogoslof: that the sound wave from thunder generated in the atmosphere undergoes acoustic reflection/transmission at the air-ocean interface and then propagates to the hydrophone. We base this inference on a few observations. The first is that the hydroacoustic wave is typically delayed by approximately 10 s relative to the electromagnetic glitch on the Okmok array, as shown in Fig. 13 for the stroke at 13:12 UTC on June 10, 2017. A delay of 10 s, if the hydroacoustic wave is excited by a lightning strike to the ocean surface, would correspond to a travel distance of 15 km in the ocean. Taking into account the WWLLN and GLD360 lightning locations, which consistently place the 13:12 UTC stroke to the northeast of the volcano and close to the hydrophone, the distance (15 km) corresponding to a 10-s delay is too far from the hydrophone to correspond to a lightning strike on the ocean surface. Secondly, as mentioned previously, data from Earth Networks lightning sensors in Dutch Harbor and Adak indicate that the 11:14 UTC flash was intra-cloud, not cloud-to-ocean. Therefore, the hypothesis of a lightning strike to the ocean surface does not apply to the 11:14 UTC flash, which clearly produced a signal associated with lightning (Fig. 12). Finally, it is worth noting that the transmission coefficient (i.e., ratio of transmitted to incident wave) of a pressure wave passing from air into water at normal incidence is 2 (Brekhovskikh 1980; p. 11). Thus, a pressure wave is in fact amplified during acoustic transmission from air into water. This is in contrast to the transmission coefficient from water into air, which is close to zero at normal incidence.

Fig. 12
figure 12

Hydroacoustic signal during the June 10, 2017 eruption (event 48) associated with the lightning flash at approximately 11:14 UTC. The hydroacoustic signal exists in the relatively high-frequency band from 50 to 300 Hz and is clearly associated with the glitch on OK01 (which it follows by 10 s) since no other high amplitude, impulsive hydroacoustic arrivals are observed during the 34-min time window shown. Okmok seismic station OKER is also displayed to show that no short duration, impulsive signals existed in seismic data

Fig. 13
figure 13

High-frequency (150–300 Hz) hydroacoustic signal following a volcanic lightning stroke during the June 10, 2017 eruption (event 48). The hydroacoustic signal arrives approximately 10 s after the glitch. The glitch occurs within a second of the origin time of the associated stroke in the WWLLN/GLD360 catalogs. The 10 s time delay is too long to be explained by direct propagation in the water column from the lightning location to the hydrophone and suggests the hydroacoustic signal originates as high-frequency thunder that is acoustically transmitted from the atmosphere into the ocean

Given these considerations, our preferred interpretation of the hydroacoustic signals is that they are simply underwater recordings of high-frequency volcanic thunder in the near source region. The 10-s delay time can be explained by the thunder source being distributed at an altitude of a few kilometers. Additional delay on the order of 1–2 s can then be accommodated by propagation within the ocean at the speed of sound in water (1.5 km/s) from the surface to the hydrophone, which was located at 231 m depth.

Discussion

The glitch-based catalogs we have developed have both advantages and disadvantages when compared to the WWLLN and GLD360 detections. Overall, the glitch catalogs, both A and B, have a similar detection rate as WWLLN. Simply in terms of the total number of detected volcanic lightning strokes during the eruption, WWLLN (670) falls in between the number of flashes detected by Glitch Catalog A (422) and Glitch Catalog B (859). As seen in Table 1, many of the events with high rates of lightning contain a similar number of detections in the WWLLN and glitch catalogs. However, note that several eruptive events not displayed in Table 1 had WWLLN-detected lightning, but zero glitch detections. Those events tended to occur during stormy winter weather conditions, in December 2016 and January 2017. For some of those events, telemetry for the Okmok microphone array was down and data were not received. However, there were several events without detected glitches in the winter even when the data were transmitted successfully. This observation suggests that glitch detection was more favorable during the summer, while the global lightning networks (both WWLLN and GLD360) detected more strokes during the winter. One example of this is that the glitch catalogs detected flashes for the July 2, 2017 event (Fig. 11) which went undetected by both WWLLN and GLD360. We attribute this seasonal dependence to the higher level of storm and wind noise on the acoustic channels during the winter, which inhibits the STA/LTA detection. Future work is warranted on better glitch detector algorithms than the STA/LTA approach we have utilized in this study. Anderson et al. (2018) have suggested the use of a median filter, a type of nonlinear signal processing that can be used to both accentuate and suppress short-duration, impulsive signals.

During the Bogoslof eruption, the significance of the glitches in the Okmok infrasound data stream was unknown to the staff of AVO involved in monitoring the volcano in real time. Certainly, knowledge of the glitches would have been useful in diagnosing whether an eruption plume was electrified in the many cases where glitches preceded detectable volcanic lightning in the global datasets (e.g., Fig. 7b) and in the one case of glitch detections (July 2, 2017, event 56) when no global detections were made. In fact, the event 56 glitch detections have proven to be useful in the study on the origin of volcanic lightning occurrence at Bogoslof by Van Eaton et al. (2020). Event 56 is an outlier over the entire eruption in terms of its high-altitude plume and lack of lightning detections in the global catalogs; however, the glitch detections show that the event 56 plume did in fact produce volcanic lightning. Knowledge of the glitch detections for event 56 therefore strengthens the hypothesis of Van Eaton et al. (2020) that detectable volcanic lightning was controlled by height of the ash plume relative to freezing temperature levels in the atmosphere.

Our detection of volcanic thunder for the May 17, 2017 eruption (event 39) shown in Fig. 2 brings the total number of Bogoslof events with documented volcanic thunder to three, including the previously reported observations for the March 8 (event 37) and June 10 (event 48) eruptions by Haney et al. (2018). The time frame between March 8 and June 10 appears to have been optimal for volcanic thunder observations, reflecting a tradeoff between more volcanic lightning activity in the winter and early spring (Van Eaton et al. 2020) and better acoustic propagation and lower wind noise in the late spring into summer. A notable exception is event 40 on May 28, 2017, which produced a sizable number of lightning detections in all the catalogs, but no identifiable thunder. Lower level winds at Bogoslof during event 40 were directed toward the northwest, away from Okmok, which hindered acoustic propagation by reducing the transmitted amplitude of infrasound waves from Bogoslof.

Besides the Okmok microphone array, we have looked into whether glitches appeared on other regional microphone arrays and seismic stations. The two closest microphone arrays to Bogoslof, after the one at Okmok, are located near Cleveland and Akutan volcanoes. However, those arrays are sampled at a lower rate (50 Hz) than the Okmok array, which detracts from glitch detection and observations of high frequency thunder signals. It may also be that those arrays do not have good line-of-sight views of Bogoslof and the lower atmosphere above the volcano. In contrast, Bogoslof volcano can be seen visually from the Okmok microphone array in clear viewing conditions. Regarding seismic data streams, we have detected glitches on the network located at Okmok, similar to the observations at Mt. Spurr by McNutt and Davis (2000). However, the glitches appear mostly on analog short-period stations, which can have a complicated telemetry path prior to digitization. Whether the glitches are occurring at the seismic station or at its radio repeater is not straightforward to establish. Moreover, the cabling details (e.g., cable orientation and length) are not known for the seismic stations as they are for the Okmok microphone array. This is on account of the array requiring such geometrical information to be known for array processing, in contrast to single seismic stations. In any case, a future investigation of glitches in seismic data streams is warranted, despite these additional complexities. Future work is also needed on a model of the precise coupling of the electromagnetic pulse from lightning into the cables (Petrache et al. 2005; Paolone et al. 2005) and how to measure or interpret these voltages.

Conclusion

We have investigated the signature of volcanic lightning in ground-based, geophysical data streams during the 2016–2017 Bogoslof eruption. The eruption was a prolific producer of volcanic lightning over the course of its 9-month-long duration, particularly during the first 5 months. A microphone array located ~ 60 km away enabled the observation of volcanic thunder and electromagnetic pulses, or glitches, produced by volcanic lightning. We developed two new catalogs based on the properties of glitches and found numerous new lightning flashes which went undetected by the WWLLN and GLD360 catalogs. We further investigated lightning-associated acoustic signals on a moored hydrophone located on the northeast slope of Bogoslof and clarified the details of their propagation path from the thunder source region to the hydrophone. Taken together, these observations give a more complete picture of electrical activity during the 2016–2017 Bogoslof eruption. These findings should be helpful for diagnosing the occurrence of volcanic lightning in real-time, ground-based geophysical data streams during eruptions monitored by volcano observatories. Furthermore, geophysical stations in the future could be designed to help increase the chance of capturing additional information on volcanic lightning.