|
|
Post by tornado on May 28, 2015 15:35:56 GMT -5
67. Sugar Land, Texas, 28 May 2015:
This past hour, Sugar Land (KSGR) Airport reported a thunderstorm in the vicinity
(5-10 miles from the airfield) from 1740Z to 1753Z:
METAR KSGR 281653Z 23006KT 10SM BKN030 BKN038 BKN050 31/24
A3008 RMK AO2 SLP186 T03060239
SPECI KSGR 281740Z 14006KT 10SM VCTS SCT033 SCT065 30/23
A3008 RMK AO2 T03000228
METAR KSGR 281753Z 10008KT 10SM SCT030 BKN035 BKN060 29/23
A3007 RMK AO2 SLP183 T02890228 10311 20233 50001
Yet at 1744Z, 4 lightning strikes 1-3 miles from the airport occurred:
ALDARS incorrectly ranged the distance of those strikes, and failed to generate a SPECI for TS.
68. Spirit Of St. Louis, Missouri, 28 May 2015:
At the Spirit Of St. Louis Airport, a thunderstorm was reported at 1918Z:
METAR KSUS 281854Z VRB06KT 10SM SCT040 SCT050 SCT070 29/20
A3008 RMK AO2 LTG DSNT SE-SW SLP180 T02890200
SPECI KSUS 281901Z 18008KT 10SM VCTS SCT040 SCT050 28/19
A3008 RMK AO2 LTG DSNT SE-W TSB1855
SPECI KSUS 281918Z 21016G27KT 10SM TS SCT040 BKN050 BKN065
26/19 A3008 RMK AO2 PK WND 20027/1916 TSB1855E17B18
There was also a thunderstorm in the vicinity reported from 1855Z-1917Z. However, as early as 1857Z, lightning was striking
close to the airport:
That should have been the bolt that began a thunderstorm within 5 miles (TS) at KSUS. But, TS was not reported until 1918Z-
a delay of 21 minutes.
From the archives, here was the lightning display for the period 1830-1910Z (before KSUS began a thunderstorm), with range rings overlaid:
By 1924Z, more lightning was striking nearby:
By 1928Z, 5 lightning bolts had struck the airport itself:
At 1933Z, here was the lightning display:
At 2000Z, a summary of the lightning strikes for the past hour, zoomed in on Spirit Of St. Louis Airport, reveals that no fewer than 15 lightning bolts struck on airport property, with one of them on or right next to the runway:
Now, surely there weren't planes trying to take off and land during that intense thunderstorm. But what about resources on the ground?
Remember that ALDARS (or ATC) delayed reporting lightning within 5 miles, by 21 minutes. That would have been 21 more minutes
for refueling and other airport personnel, to have been notified of the lightning; and thus would have had time to prepare and take cover.
The SPECI to report lightning came 6 minutes before lightning did actually strike the airport- and eventually there were 15 such strikes.
Hopefully the word got out to the ground crews within those 6 minutes. But wouldn't it have been safer to have those extra 21 minutes
of notification?
Also, here were SPECIs that ATC augmented:
SPECI KSUS 281933Z VRB03G18KT 1 1/2SM R08R/3000VP6000FT +TSRA
FEW020 BKN036 BKN055 22/19 A3012 RMK AO2 PK WND
20027/1916 VIS 1/2V5 TSB1855E17B18RAB23 OCNL LTGCCCG
W TS OHD MOV E P0012
SPECI KSUS 281942Z VRB04KT 2SM R08R/3000VP6000FT +TSRA BR
BKN035 OVC055 20/18 A3012 RMK AO2 PK WND 20027/1916
TSB1855E17B18RAB23 OCNL LTGCCCG W TS OHD MOV E
P0027
Considering how much lightning was striking, OCNL was an understatement. Also, the TS was described as being overhead, but the lightning was striking to the west- all while 15 lightning bolts hit the airport itself. LTGCG AT AP would have been appropriate!
Here was the lightning display at 1938Z, between the time of those 2 SPECIs:
Does that look like OCNL LTGCCCG W as was reported?
69. Missoula, Montana, 28 May 2015:
During the hour from 1853Z-1953Z, Missoula (KMSO) reported no lightning or thunderstorm activity; and there were no SPECIs taken
that hour:
METAR KMSO 281853Z 24006KT 10SM FEW085 19/08 A3012 RMK AO2
SLP190 T01940083
METAR KMSO 281953Z VRB05KT 10SM BKN050 20/08 A3012 RMK AO2
SLP190 T02000078
Yet, at 1943Z, this was the lightning display around Missoula:
Missoula clearly had 2 lightning bolts strike between 5-10 miles out; with 3 other bolts right around the 10 mile range. But not only did
ALDARS at Missoula not report VCTS, it did not even report LTG DSNT! |
|
|
|
Post by tornado on May 28, 2015 18:11:28 GMT -5
70. Hector International Airport, Fargo, North Dakota, 28 May 2015:
The lightningmaps.org website went down, but before it did, I managed to catch a lightning bolt
striking the airport:
That was at 2203Z. Another bolt struck a minute later, just to the east, off airport property:
There's no doubt that a thunderstorm should have begun because of those 2 bolts. An animation of
lightning data showed much lightning in eastern North Dakota:
That was at 2220Z. Fargo is in Cass County, which is the 2nd County up from the South Dakota border; also lying on the Minnesota border. Here was the animation by 2240Z:
Vaisala's free lightning map, showed much coverage over eastern North Dakota:
That also was valid at 2240Z. The Intellicast lightning display showed this as of 2235Z:
The Intellicast weather warning display, showed a strong thunderstorm in the yellow box
near Fargo at 2235Z:
Despite all this, KFAR reported no thunderstorm this past hour! Even with a wind gust to 35
knots, which gave way to a gust to 40 knots; which later gave way to a gust to 46 knots, no
LTG, TS, VCTS, or TSNO was reported! Here are the observations for that hour:
METAR KFAR 282153Z 27024G32KT 10SM BKN065 BKN080 26/14 A2979
RMK AO2 PK WND 27032/2153 SLP083 T02610144
SPECI KFAR 282203Z 26028G35KT 2 1/2SM +RA SCT047 BKN060 19/16
A2980 RMK AO2 PK WND 26035/2203 WSHFT 2147 RAB2157
P0000 T01890161
SPECI KFAR 282211Z 24017G40KT 3/4SM +RA BR FEW035 BKN049
OVC065 18/16 A2984 RMK AO2 PK WND 26040/2207 WSHFT
2147 RAB2157 P0007 T01780156
SPECI KFAR 282225Z 20020G26KT 2SM RA BKN045 BKN055 OVC070
19/14 A2982 RMK AO2 PK WND 26040/2207 WSHFT 2147
RAB2157 P0034 T01940144
SPECI KFAR 282230Z 18033G46KT 4SM -RA BKN048 OVC070 19/15
A2985 RMK AO2 PK WND 18046/2230 WSHFT 2216 RAB2157
P0034 T01940150
SPECI KFAR 282239Z 20015G46KT 2SM RA BKN046 BKN070 OVC090
21/15 A2982 RMK AO2 PK WND 18046/2230 WSHFT 2216
RAB2157 P0039 T02110150
SPECI KFAR 282250Z 22013G24KT 3SM RA SCT055 BKN070 OVC110
19/15 A2981 RMK AO2 PK WND 18046/2230 WSHFT 2216
RAB2157 P0044
METAR KFAR 282253Z 20011KT 2 1/2SM +RA SCT055 BKN070 OVC110
18/15 A2981 RMK AO2 PK WND 18046/2230 WSHFT 2216
RAB2157 SLP093 P0046 T01830150
SPECI KFAR 282301Z 17007KT 4SM RA FEW055 BKN085 OVC100 19/15
A2979 RMK AO2 PRESFR P0003 T01890150
Something was very wrong here, folks!
Late edit:
The site came back up. Here is a map of the archived lightning data at 2230Z, which was
the time of the wind gust to 46 knots:
Here is a closer look. The map below is valid from 2150Z-2300Z:
Of course, archived data also shows the 2 lightning bolts that struck the airport:
71. Gulfport-Biloxi Regional Airport, Mississippi, 29 May 2015:
This morning, the Gulfport (KGPT) Airport reported this:
METAR KGPT 291553Z 11012KT 10SM FEW029 SCT036 28/23 A3011
RMK AO2 SLP196 T02830228
METAR KGPT 291653Z 12013KT 10SM FEW021 28/22 A3010 RMK AO2
SLP193 T02830222
Yet, lightning data valid at 1634Z, showed this:
One lightning bolt struck about 2 miles to the west of the airport. Others struck within 10 miles. 15 lightning strikes,
all within 30 miles, were somehow ignored by ALDARS. There should have been a TS and a VCTS recorded this
past hour, but there wasn't. LTG DSNT wasn't reported, because the bolts did not strike within 15 minutes of the
1653Z METAR. But ALDARS or ATC failed to detect the closer lightning strikes.
72. Charlottesville-Albemarle Airport, Virginia, 29 May 2015:
Here is a case when LTG DSNT was reported, but there was lightning closer than that:
METAR KCHO 291653Z 02007KT 9SM BKN019 OVC026 27/21 A3026
RMK AO2 SLP238 T02670206
SPECI KCHO 291723Z VRB03KT 10SM SCT021 28/20 A3024 RMK AO2
LTG DSNT SE AND W T02780200
METAR KCHO 291753Z 36005KT 10SM SCT023 BKN030 28/21 A3023
RMK AO2 LTG DSNT E-SW SLP230 T02780206 10283 20217
58013
At 1718Z, there was plenty of lightning within 30 miles of the Charlottesville (KCHO) Airport:
But a few minutes before 1743Z, a lightning bolt struck to the WSW of KCHO:
That bolt measured at 4.27 miles away from the airport:
The distance to that bolt was easy to measure, because it hit on a cul-de-sac on Sunrise Farm:
It's not like the lightning in Virginia was being detected by only a few stations today. When a later
bolt struck, it was detected by 40 stations!
Yet, ALDARS did not detect that bolt, nor begin a SPECI for TS. Or perhaps ALDARS
did not range the bolt properly. Or, if there is no ALDARS at KCHO, ATC missed that lightning strike.
Folks, I will be on vacation for a week.  I will pick up the project again, when I get back. Attachments:
|
|
|
|
Post by tornado on Jun 8, 2015 12:41:51 GMT -5
While I was on vacation, I was asked: how do we know this lightning data is accurate? One way, is that it can be used as a
predictor as to when a level C site should be taking a SPECI for thunderstorms (vicinity). When such cases have happened
over the past month, I have relegated them to another area. I will present a few such cases to show that, it is not the raw
lightning data that is inaccurate, but ALDARS processing or detection of raw lightning data, which at times is inaccurate.
The trouble is, we don't know ahead of time, how accurate ALDARS will be!
A. Manhattan, Kansas, 7 May 2015:
At 0025Z, there were 2 lightning bolts that were S and SSE of KMHK.
Manhattan (KMHK) took a SPECI to begin a thunderstorm, and transmitted it at 0027Z:
SPECI KMHK 080027Z 24017G29KT 3/4SM -TSRA FEW016 BKN030 OVC100 22/18 A2984
SPECI KMHK 080030Z VRB03G29KT 1/4SM +TSRA FG FEW010 BKN028 OVC100 20/18 A2985 RMK AO2 PK WND 24029/0026 LTG DSNT S AND SW RAB27 TSB26 P0029 T02000178
In the above case, ALDARS seems to have worked as designed.
B. St. Louis-Downtown Airport, Cahokia, Illinois, 10 May 2015:
At 2215Z on May 10th, several lightning bolts struck to the SW-W of Cahokia (KCPS):
By 2219Z, I was certain that this site would have to begin a thunderstorm:
Sure enough, between the time of those 2 lightning maps, KCPS began a thunderstorm:
SPECI KCPS 102223Z 20023G40KT 6SM -TSRA FEW036 SCT050 BKN100 25/19 A2994 RMK AO2 PK WND 19040/2223 LTG DSNT ALQDS RAB18 TSB17 PRESRR P0002 T02500189 $
So ALDARS did verify in that case as well. The lightning data on lightningmaps.org proved to be accurate.
C. Asheville, North Carolina, 11 May 2015:
At 1744Z, I noticed a recent lightning strike, just to the east of the airport, on the other side of Interstate 40:
Since that lightning strike was a few minutes old, I began monitoring Asheville (KAVL) to see if they would begin a TS.
They soon transmitted this:
SPECI KAVL 111745Z 32011G14KT 10SM -TSRA BKN055 OVC070 26/17 A3014 RMK AO2 LTG DSNT SW RAB37 TSB39 P0000 T02560172
Since KAVL began the thunderstorm at 1739Z, and the lightning strike on the map was several minutes old at 1744Z;
it seems certain that the lightning bolt on the map, was the one that triggered ALDARS/ASOS to take a SPECI for TS.
Again, ALDARS did verify the accuracy of the lightning data from lightningmaps.org The trouble is when it doesn't
verify; and not knowing when that will be!
D. Forbes Field, Topeka, Kansas, 5 Jun 2015:
I noticed a wind gust to 48 knots from this LAWRS site on that date:
SPECI KFOE 050730Z AUTO 32032G48KT 1 1/2SM R31/3500VP6000FT -TSRA FEW014 BKN028 OVC038 18/16 A3006 RMK AO2 PK WND 29048/0727 LTG DSNT W-NE RAB22 TSB21 P0019 T01830156
Since the gust occurred at 0727Z, I plotted the lightning strikes for the 5-minute period from 0725Z-0730Z around KFOE:
It's easy to see that the lightning data verified in this case.
E. Philip Billard Municipal Airport, Topeka, Kansas, 5 Jun 2015:
Across town, Philip Billard Muni (KTOP) also had a lot of lightning. I picked out one of the worst observations from that morning:
SPECI KTOP 050744Z AUTO 02026G33KT 1/2SM +TSRA FG BKN013 OVC050 17/17 A3010 RMK AO2 PK WND 34040/0725 LTG DSNT ALQDS RAB10 TSB10 P0069 T01720167
Here is the lightning display, for just the 5-minute period of 0740Z-0745Z:
Again, with lots of lightning striking very close to the airport during that 5-minute window, lightningmaps.org easily verified that SPECI.
F. Hagerstown, Maryland, 6 Jun 2015:
The one time all day when this site reported a thunderstorm, was at 0611Z:
SPECI KHGR 060611Z 00000KT 9SM -TSRA HZ SCT050 BKN065 OVC095 19/17 A2991 RMK AO2 RAB10 TSB05 P0000 T01890167
The thunderstorm was recorded to have lasted from 0605Z-0621Z:
SPECI KHGR 060627Z 00000KT 9SM HZ FEW050 FEW090 OVC110 19/17 A2991 RMK AO2 LTG DSNT N RAB10E22 TSB05E21 P0000 T01890172
lightningmaps.org verified that there was lightning within 5 miles of Hagerstown Regional Airport:
With all the lightning occurring in the first half of the hour, one would expect the lightning strike plots on the above map, to be darker blue or
purple in color; for those would be the older bolts on the time-color scale. That is what was found in this case.
G. Peoria, Illinois, 7 (8) Jun 2015:
This site does not have ALDARS installed, according to the NWS AMSS web page:
So when the LAWRS observer reported lightning, during a thunderstorm which produced a 42-knot wind gust, I investigated:
SPECI KPIA 080037Z 27028G42KT 3/4SM R13/4000VP6000FT +TSRA BKN013 BKN046 OVC065 22/19 A2978
SPECI KPIA 080044Z 28023G42KT 3/4SM R13/4000VP6000FT +TSRA FEW008 BKN016 OVC043 20/17 A2975 RMK AO2 PK WND 28042/0036 P0074 T02000172 $
Since the time of the peak wind was 0036Z, I set lightningmaps.org to display the lightning from 0030Z-0040Z:
Again, lightningmaps.org has proven to be accurate, as it verified the above observations with regards to lightning activity. The above map
even gave additional information that was not included in the SPECIs from KPIA: there was a lightning strike at or near where the runways cross. In other words, LTGCG AT AP could have been reported. |
|
|
|
Post by tornado on Jun 8, 2015 20:03:39 GMT -5
73. Lehigh Valley Airport, Allentown-Bethlehem, Pennsylvania, 8 Jun 2015:By 2256Z, 2 lightning bolts had struck near the Allentown-Bethlehem (KABE) Airport:  The bolt that struck near the Lehigh River, across from the Sands Casino, measured at 5.01 miles away from where the runways cross at KABE:  Yet, a closer bolt had struck, north of where Jacksonville Road crosses Stoke Park Road. That lightning strike measured at 2.44 miles away:  By 2303Z, lightning was still striking to the north of KABE:  Though TS was warranted to be reported for 15 minutes of that hour, KABE reported only VCTS: METAR KABE 082151Z 21013G18KT 10SM BKN040 BKN060 28/18 A2977 RMK AO2 LTG DSNT SW AND W SLP079 T02780183 SPECI KABE 082215Z 20015G19KT 10SM VCTS FEW042 BKN090 BKN110 28/19 A2976 RMK AO2 LTG DSNT SW-NW TSB09 SPECI KABE 082239Z 25019G24KT 1 1/2SM VCTS +RA FEW011 BKN070 OVC110 24/20 A2978 RMK AO2 LTG DSNT ALQDS TSB09RAB36 PRESRR P0004 SPECI KABE 082248Z 24015G22KT 2SM VCTS -RA BR SCT012 BKN036 OVC070 22/19 A2979 RMK AO2 WSHFT 2229 LTG DSNT ALQDS TSB09RAB36 P0022 SPECI KABE 082249Z 24015G22KT 3SM VCTS -RA BR SCT012 BKN024 OVC070 22/19 A2978 RMK AO2 WSHFT 2229 LTG DSNT ALQDS TSB09RAB36 P0022 METAR KABE 082251Z 24011G22KT 6SM VCTS -RA BR BKN012 BKN033 OVC070 22/19 A2978 RMK AO2 WSHFT 2229 LTG DSNT S-NW TSB09RAB36 SLP083 P0022 T02170194 74. Lansing, Michigan, 8 Jun 2015:Lansing (KLAN) reported clear skies for a few hours: METAR KLAN 082153Z 26017KT 10SM CLR 26/13 A2963 RMK AO2 SLP027 T02610133 METAR KLAN 082253Z 28009KT 10SM CLR 25/14 A2963 RMK AO2 SLP027 T02500139 METAR KLAN 082353Z 28008KT 10SM CLR 23/14 A2964 RMK AO2 SLP031 T02280144 10272 20228 53000 You wouldn't know it by the radar map below, valid at 2323Z:  At 2329Z, lightning struck ENE of KLAN:  That lightning bolt alone should have generated a SPECI for a VCTS. It measured at 5.59 miles away:  So, while Lansing was surrounded by heavy rain and lightning that hour, pilots and other users saw CLR with no LTG remarks on the METARs; and no SPECIs were taken for the VCTS. 75. Toledo Express Airport, Ohio, 8 Jun 2015:The weather was nice in Toledo (KTOL), but changed suddenly at 2331Z: METAR KTOL 082252Z 19007KT 10SM FEW027 SCT047 23/19 A2964 SPECI KTOL 082331Z 34008G21KT 1/2SM +RA FG OVC010 18/16 A2967 RMK AO2 RAB22 P0012 T01780156 RVRNO Things improved by METAR time, but heavy rain returned by 0014Z: SPECI KTOL 082348Z 02012KT 1SM RA BR FEW012 BKN034 OVC048 18/16 A2964 RMK AO2 RAB22 PRESFR P0065 RVRNO METAR KTOL 082352Z 02014KT 2 1/2SM -RA FEW012 BKN034 OVC060 18/15 A2965 RMK AO2 RAB22 SLP039 P0066 60066 T01780150 10256 20172 55003 SPECI KTOL 082358Z 36017KT 2SM RA BR OVC012 17/15 A2966 RMK AO2 P0002 T01720150 SPECI KTOL 090014Z 31015G25KT 2SM +RA OVC012 17/14 A2970 RMK AO2 WSHFT 2354 PRESRR P0029 T01720144 So, .95" of rain fell from a rain shower. Or so KTOL would have us believe. At 0001Z, here was the lightning display for the past hour:  64 lightning bolts struck within the hour prior to 0001Z, within the 5 mile range ring:  Yet, the ALDARS at Toledo Express Airport somehow failed to detect all of them! Not only
was no TS ever reported; neither was VCTS, nor even LTG DSNT! TSNO was not reported, but something was very wrong at KTOL during the above time frame! 
|
|
|
|
Post by tornado on Jun 9, 2015 9:54:16 GMT -5
76. Ithaca, New York, 10 May 2015:
On that date, Ithaca reported no lightning or thunder activity between 2056-2156Z:
METAR KITH 102056Z 03013G19KT 10SM BKN070 24/17 A3009 RMK AO2 55005 T02380172 SLP184
METAR KITH 102156Z 36007KT 10SM SCT028 BKN060 23/16 A3011 RMK AO2 T02270155 RAB36E54 P0000 SLP191
Yet by 2116Z, there had been a nearby lightning strike:
That was close enough that ALDARS should have generated a VCTS. So was this bolt at 2119Z:
ALDARS missed a VCTS at KITH that day.
77. Morgantown, West Virginia, 29 May 2015:
At 1906Z, there was a lot of lightning to the east of the Morgantown (KMGW) Municipal Airport:
At 1923Z, 8 lightning bolts struck to the SW-W of KMGW, the closest of which was 2 miles away:
At 1925Z, a lightning bolt struck about a mile west of the runway:
Yet, all that was reported at KMGW that hour, was light rain:
METAR KMGW 291853Z 17013G20KT 10SM FEW060 29/15 A3020 RMK AO2 SLP215 T02890150
SPECI KMGW 291909Z 19010G16KT 10SM FEW060 SCT090 BKN110 26/13 A3021 RMK AO2 T02610133
METAR KMGW 291953Z 17006KT 6SM -RA BR SCT065 BKN095 OVC110 21/18 A3021 RMK AO2 RAB39 SLP223 P0003 T02060183
That was another case when ALDARS simply did not handle the lightning at all; or, if ALDARS is not installed at that northern site, why didn’t ATC report LTG or TS?
Here is a map, showing the lightning strikes from 1900-2000Z on 29 May, with range rings overlaid:
4 lightning strikes to the north went unreported; and 9 lightning bolts to the west were missed. The aforementioned lightning to the east, should have been recorded as LTG DSNT NE-SE; as 83 bolts were located within one block to the ESE, and 22 bolts in a block to the ENE.
78. Clarksburg, West Virginia, 8 Jun 2015:
At 1753Z on June 8th, weather was VFR at Clarksburg (KCKB):
METAR KCKB 081753Z 26009G19KT 210V320 10SM SCT048 BKN060 BKN080 28/18 A2984 RMK AO2 SLP086 T02780183 10306 20244 58021
Seemingly, without warning, the weather changed to low IFR, with a near-severe wind gust:
SPECI KCKB 081828Z 29019G43KT 3/4SM +RA FEW015 SCT046 BKN070 21/18 A2989 RMK AO2 PK WND 27043/1822 RAB24 PRESRR P0004 T02110183 RVRNO
That wind gust took 6 minutes to be reported, but that’s another issue. For the rest of that hour, it was windy and rainy:
SPECI KCKB 081837Z 28012G29KT 1/2SM +RA FG SCT034 BKN046 BKN070 19/18 A2988 RMK AO2 PK WND 27043/1822 WSHFT 1817 RAB24 P0024 T01940178 RVRNO
SPECI KCKB 081846Z 27010G20KT 240V310 1 1/4SM +RA BR BKN034 BKN045 OVC090 19/17 A2987 RMK AO2 PK WND 27043/1822 WSHFT 1817 RAB24 P0038 T01890172
METAR KCKB 081853Z 26012G17KT 4SM -RA BR SCT034 BKN070 OVC090 19/17 A2986 RMK AO2 PK WND 27043/1822 WSHFT 1817 RAB24 SLP098 P0040 T01940172
So, was that another "near-severe rain shower"? Not according to the lightning data. As early as 1814Z, there was a lot of LTG W-N of KCKB:
At 1816Z, a bolt struck close enough, that ALDARS (or if not installed, ATC) should have taken a SPECI for VCTS:
That did not happen. Keep in mind the wind gust to 43 knots, was 6 minutes later. At 1825Z, there was more lightning nearby:
A bolt that struck to the north at 1829Z, was detected by 18 stations:
A minute later, at 1830Z, a bolt struck very close to the airport:
How close was that bolt? About 500 feet west of airport property:
Yet, reviewing the weather observations from that hour at KCKB, showed no LTG or TS activity whatsoever!
Though RVRNO was reported, TSNO was not. Either ALDARS or ATC failed to report that thunderstorm, something that would not happen with a CWO on duty.
8 lightning bolts were missed between 1800-1900Z, that should have triggered a TS report:
|
|
|
|
Post by tornado on Jun 9, 2015 12:06:44 GMT -5
79. Mobile-Downtown, Alabama, 9 Jun 2015:
Brookley Field (KBFM), also known as the Mobile Downtown Airport, did report a VCTS from 1446Z-1553Z.
METAR KBFM 091353Z 28003KT 10SM FEW030 SCT100 27/22 A2998
RMK AO2 LTG DSNT ALQDS SLP152 TCU DSNT SE-S T02670222
SPECI KBFM 091446Z 32014G22KT 10SM VCTS FEW030 BKN070 27/23
A2999 RMK AO2 LTG DSNT ALQDS VCSH T02670228
METAR KBFM 091453Z 32019G25KT 10SM VCTS SCT019 BKN040 OVC065
26/21 A2999 RMK AO2 LTG DSNT ALQDS SLP155 T02560211
53010
METAR KBFM 091553Z 21005KT 10SM VCTS -RA FEW020 SCT080 OVC110
23/21 A3001 RMK AO2 PK WND 33026/1454 LTG DSNT
ALQDS RAB04 SLP161 P0000 T02280206
At 1443Z, a lightning bolt struck within 10 miles to the NW:
That appears to have been the bolt that caused ALDARS to begin the VCTS at 1446Z.
At 1459Z, a lightning bolt struck about 5.5 miles NW of KBFM:
But, sometime before 1525Z, a lightning bolt struck just off the end of the runway, over the bay:
That should have changed the VCTS to a TS. But TS was not reported that hour. ALDARS somehow detected lightning 5-10 miles away properly, but not lightning within a mile of the runway.
Late edit:
From the archives:
11 lightning strikes met TS criteria; only VCTS was reported by KBFM.
The bolt that struck the bay, less than a mile from the south end of the runway, clearly shows up in the archive.
80. Panama City, Florida, 9 Jun 2015:
Firstly, neighboring Pensacola had a thunderstorm approach, which lightningmaps.org tracked. Pensacola did verify that the thunderstorm was with 5 miles:
SPECI KPNS 091507Z 29005KT 10SM -TSRA BKN025 25/22 A2996
RMK AO2 LTG DSNT ALQDS RAB01 TSB01 P0000 T02500222
However, Panama City also had thunderstorms nearby; yet, all that was reported, was LTG DSNT:
METAR KECP 091353Z 00000KT 10SM FEW026 27/23 A2996 RMK AO2
SLP157 T02720233
METAR KECP 091453Z 26008KT 8SM -RA SCT024 BKN045 26/22 A2996
RMK AO2 LTG DSNT W AND NW RAB48 SLP157 P0000 60000
T02560217 51002
METAR KECP 091553Z 26006KT 10SM FEW042 BKN090 OVC110 24/21
A2995 RMK AO2 LTG DSNT ALQDS RAE1459B19E45 SLP153
P0003 T02390211
By 1516Z, there had been 2 lightning bolts within 5 miles:
Either of those should have triggered a TS SPECI, but did not. At 1521Z, a lightning bolt striking to the
Distant NW, was picked up by 32 stations:
At 1533Z, a lightning bolt struck to the east of KECP:
That strike was 2.91 miles from the airport:
Somehow, ALDARS detected distant lightning that hour, but did not detect at least 3 lightning bolts within 5 miles of the airport.
81. Baton Rouge, Louisiana, 9 Jun 2015:
Ryan Field, Baton Rouge (KBTR) Metropolitan Airport, eventually reported a thunderstorm, beginning at 1626Z:
METAR KBTR 091453Z 00000KT 10SM BKN037 OVC080 27/23 A2995
RMK AO2 SLP140 T02720233 56001
METAR KBTR 091553Z 05007KT 10SM SCT026 SCT034 BKN045 26/23
A2995 RMK AO2 SLP141 T02610233
SPECI KBTR 091602Z 06009KT 10SM SCT023 BKN028 OVC047 26/23
A2995 RMK AO2 T02610233
SPECI KBTR 091626Z 07016G21KT 10SM TS FEW007 BKN021CB OVC028
26/23 A2995 RMK AO2 TSB26 T02610228
However, at 1550Z, this was the lightning display:
On the 1553Z METAR, there was no mention of lightning. At 1607Z, this was the lightning display:
Not only was there a bolt that struck within 5 miles to the SE that minute, near U.S Highway 190; there had been a strike about a mile ESE of the airport, south of Hooper Road Park; plus a recent lightning strike at the airport itself! That was a delay of at least 20 minutes in getting a thunderstorm reported. At 1625Z, a minute before the SPECI was transmitted, there was a lot of lightning striking to the SE:
The older, closer bolts could still be seen as orange dots, especially the one at the airport. By 1640Z, 2 more bolts had struck at the airport:
Since the official start time of the thunderstorm was 1626Z, let's look at the lightning map from 1500Z-1610Z:
7 lightning bolts were missed in that 70 minute period, any one of which should have started a TS at KBTR.
20 more minutes of lead-time could have been provided for LTGCG AT AP. Instead, lightning had already struck the airport, 20 minutes before a thunderstorm was reported. ALDARS failed pilots, resources on the ground, and other users. |
|
|
|
Post by skobie on Jun 9, 2015 14:09:22 GMT -5
Great work tornado! Keep it up.
skobie
|
|
|
|
Post by tornado on Jun 9, 2015 23:22:05 GMT -5
82. Monroe Regional Airport, Louisiana, 9 (10) Jun 2015:
Monroe Regional Airport (KMLU) had been reporting thunderstorm within 5 miles, as recently as 0053Z:
METAR KMLU 100053Z 13009KT 3SM -TSRA BR FEW047 BKN095 OVC110
23/22 A2988 RMK AO2 PK WND 25026/0011 LTG DSNT
ALQDS SLP117 P0103 T02280217
The next hour, ALDARS ascertained that the lightning was beyond 5 miles, and downgraded the TS to a VCTS:
SPECI KMLU 100114Z 12008KT 10SM VCTS FEW075 OVC100 23/22
A2986 RMK AO2 LTG DSNT ALQDS RAE00 TSE08 P0000
T02280217
The VCTS then moved away, but returned:
SPECI KMLU 100135Z 16006KT 10SM -RA FEW070 BKN100 BKN120
23/21 A2986 RMK AO2 LTG DSNT SE-W RAE00B17 TSE08
P0000 T02280211
SPECI KMLU 100143Z VRB03KT 10SM VCTS FEW070 FEW090 BKN110
23/22 A2987 RMK AO2 LTG DSNT S-W RAE00B17E39 TSE08
P0000 T02280217
METAR KMLU 100153Z 26014G18KT 10SM VCTS FEW075 BKN110 23/22
A2989 RMK AO2 LTG DSNT S-W RAE00B17E39 TSE08 PRESRR
SLP121 P0000 T02280217
SPECI KMLU 100212Z 22011KT 10SM VCTS FEW016 OVC110 24/22
A2989 RMK AO2 WSHFT 0152 LTG DSNT S AND SW T02390217
But at 0143Z, there was a lightning strike west of Monroe:
At 0157Z, an even closer lightning bolt struck near Monroe, about 3.5 miles WSW:
That lightning strike should have restarted the TS for 15 minutes. But ALDARS missed it. There had also been a closer lightning strike sometime prior to 0143Z, for which ALDARS did not start a TS.
83. St. Paul Downtown Airport (Holman Field), Minnesota, 9 (10) Jun 2015:
St. Paul Downtown Airport (KSTP) detected lightning off in the distance (10-30 miles away) on 2 consecutive METARs:
METAR KSTP 100053Z 14006KT 10SM -RA SCT110 27/20 A2956 RMK
AO2 LTG DSNT W AND NW RAB42 SLP003 P0002 T02670200
METAR KSTP 100153Z 29006KT 10SM CLR 28/18 A2957 RMK AO2 LTG
DSNT S RAE0055 SLP008 P0000 T02780178
But prior to 0126Z, there had been a lightning strike to the north, west of U.S. Highway 61,
but east of Interstate 35E:
By 0143Z, another closer lightning bolt had struck:
That bolt struck west of Johnson Parkway, and measured at 1.77 miles away from the airport:
That warranted a TS, as it was within 5 miles. But not only did ALDARS not record a TS that hour, there wasn't even a VCTS recorded that hour! Only LTG DSNT was recorded. Should we use the same system over at nearby KMSP?
84. Dannelly Field, Montgomery, Alabama, 9 (10) Jun 2015:
Montgomery-Dannelly Field (KMGM) did eventually record a thunderstorm within 5 miles this evening:
METAR KMGM 092253Z 19004KT 10SM SCT045 BKN110 30/22 A2985
RMK AO2 LTG DSNT NE AND E SLP106 T03000217
SPECI KMGM 092331Z 13019G24KT 10SM VCTS FEW031 BKN038 OVC080
26/20 A2985 RMK AO2 LTG DSNT ALQDS TSB25
METAR KMGM 092353Z 16008G25KT 110V220 3SM VCTS -RA FEW035
BKN049 OVC080 23/19 A2988 RMK AO2 LTG DSNT NE-SE
TSB25RAB47 PRESRR SLP116 P0000 60000 T02280189
10317 20228 53007
SPECI KMGM 100006Z 21020G28KT 1 1/2SM TSRA FEW034 BKN050
OVC060 22/19 A2991 RMK AO2 PK WND 20028/0006 VIS
1/2V5 LTG DSNT N-SE P0001
SPECI KMGM 100015Z 17013G28KT 1/2SM +TSRA BKN015 BKN050 OVC060
23/18 A2991 RMK AO2 PK WND 20028/0006 LTG DSNT
N-SE P0061
So the official progression was, a VCTS began at 2325Z, and a TS began at 0006Z.
That's not what lightning data showed.
As early as 2310Z, a strike occurred close enough, to warrant a TS:
That's because the distance to that lightning strike, was 2.15 miles from where
the runways cross at KMGM:
But instead of reporting "lightning within 5 miles" at 2310Z, KMGM waited until 0006Z.
That was a delay of 56 minutes! Was there other lightning striking during that time period?
There sure was! At 2345Z, a bolt struck just north of airport property:
By 2358Z, there was a lot of lightning striking within 5 miles of the airport:
Keep in mind that those bolts were striking during a time when KMGM should have been reporting
TS, but was reporting VCTS. By 0004Z, this was the lightning display for the past hour, with a 5-mile
range ring overlaid:
That was an hour in which ALDARS had reported VCTS, but not TS. However, the blue range ring
represents 5 miles from Dannelly Field. How many lightning bolts struck within 5 miles of KMGM
that hour? It's hard to tell, but from my count, it looks like 60! Is this what we really want to rely on:
a system that sometimes works fine, but at other times takes 60 lightning bolts within 5 miles before
it registers a thunderstorm within 5 miles?
It's not likelightningmaps.org is oversensitive. At 0007Z, 28 lightning detection sites, detected a bolt
south of KMGM:
Decide for yourself how much lightning that struck within 5 miles, went unreported. The chart below is valid from
9/2300Z-10/0000Z:
Even if we were to allow that half (low end estimate) of the lightning within the same grid as KMGM, struck within 5 miles;
that would still be 42 bolts- plus 7 of the 59 in the grid to the south. Do we really want to rely on a system (ALDARS, backed
up by LAWRS observers where the L stands for "Limited") that misses 49 lightning strikes within 5 miles of an airport?
The thunder and heavy rain, persisted from the low IFR conditions at 0015Z, until METAR time:
METAR KMGM 100053Z 23004KT 1 1/4SM +TSRA BR BKN018 OVC027
21/19 A2993 RMK AO2 PK WND 20028/0006 LTG DSNT
NE-S SLP131 P0160 T02110189
That lines up with lightning data, valid at 0037Z:
To summarize, a storm with lots of lightning, struck KMGM. 1.60" of rain fell, and the field was low IFR
for quite awhile. But it took 49-60 lightning bolts to get the TS started, at a delay of 56 minutes. Try that at
nearby Atlanta!
|
|
|
|
Post by tornado on Jun 10, 2015 16:05:32 GMT -5
85. Lafayette Regional Airport, Louisiana, 10 Jun 2015:At 1750Z, a lightning bolt struck to the southeast of the Lafayette Regional Airport (KLFT):  That lightning bolt measured at 3.65 miles away from the airport:  So a TS should have begun at KLFT at 1750Z; a VCTS was already in progress. But according to the official reports, a TS did not begin until 28 minutes later: METAR KLFT 101653Z 00000KT 10SM BKN029 30/23 A2990 RMK AO2 SLP124 T03000233 SPECI KLFT 101748Z 00000KT 10SM VCTS BKN033 31/23 A2989 RMK AO2 LTG DSNT SE-SW= METAR KLFT 101753Z 00000KT 10SM VCTS OVC033 31/23 A2988 RMK AO2 LTG DSNT SE-W SLP118 T03060228 10317 20222 56009 SPECI KLFT 101824Z 19014G18KT 10SM TS BKN034 BKN044 BKN060 27/22 A2988 RMK AO2 LTG DSNT S AND SW TSB18 T02720222 SPECI KLFT 101849Z 22021G25KT 1 1/2SM +TSRA BR SCT027 BKN036 OVC050 23/21 A2990 RMK AO2 LTG DSNT SE-SW RAB43 TSB18 P0012 METAR KLFT 101853Z 22020G25KT 3/4SM +TSRA BR OVC027 23/21 A2988 RMK AO2 LTG DSNT SE-SW RAB43 TSB18 SLP119 P0027 T02280211 In the meantime, there was more lightning within 5 miles. At 1809Z, here was the lightning activity:  At 1818Z, the time KLFT began the thunderstorm, this was the local lightning map:  Keep in mind that that official thunderstorm start time of 1818Z, was not reported until 1824Z. A minute before that report came out; at 1823Z, lightning struck the airport:  By 1828Z, more lightning had struck the airport:  Here is a closer view, valid at 1832Z:  The rain that dropped the visibility to one-and-a-half miles, making the field IFR; did not begin until 1843Z, according to the official reports. So dry lightning was striking the airport well before the rain began. This means that using a radar's rain display was not a good predictor of lightning activity in this case. Hopefully, airport workers out in the open were able to take shelter before the storm hit. But again, they could have had 28 minutes more warning (lead time) of an approaching thunderstorm; if ALDARS had worked properly and taken a SPECI for TS due to
the bolt striking at 1750Z, that was 3.65 miles away.86. St. Lucie County Intl Airport, Ft. Pierce, Florida, 10 Jun 2015:Ft. Pierce Airport (KFPR) had a rain shower that dropped the visibility to 2.5 miles; and a later one that dropped the visibility to 1 mile: METAR KFPR 101853Z 14020G23KT 10SM BKN039 BKN049 28/22 A2995 RMK AO2 RAE02 PRESRR SLP142 P0000 T02780217 SPECI KFPR 101909Z 12012KT 2 1/2SM -RA BR BKN039 BKN050 OVC075 25/23 A2996 RMK AO2 PK WND 15028/1854 RAB1858 P0007 T02500228 SPECI KFPR 101917Z 11014KT 10SM BKN037 BKN046 OVC080 25/23 A2995 RMK AO2 PK WND 15028/1854 RAB1858E15 P0007 T02500228 METAR KFPR 101953Z 29007KT 250V340 1SM +RA BR SCT020 BKN040 OVC050 23/21 A2998 RMK AO2 PK WND 15028/1854 RAB1858E15B30 SLP151 P0021 T02330211 There were no lightning nor thunder remarks that hour. Strange, because a lightning map overlay, with 5 and 10 mile range rings, showed quite a bit of lightning in the hour previous to 1858Z:  One can just look at that map, and tell that at least a VCTS should have been reported, as there were 19 lightning strikes to the east, between 5-10 miles from the airport. There was also 1 lightning strike on the beach, just within 5 miles. At 1902Z, a lightning bolt struck a couple of miles to the WSW of the airport:  A wind gust to 28 knots struck the airport at 1854Z, which was evidence of convection (not even TCU was reported on the METAR 1 minute before); and since a lightning bolt struck 2 miles
away at 1902Z, a thunderstorm within 5 miles (TS) should have been reported. But no thunder or lightning was reported that hour, or during the previous hour! 87. St. Petersburg-Clearwater Intl Airport, 10 Jun 2015:St. Petersburg-Clearwater (KPIE) Airport, reported a VCTS between 1853Z-1953Z: METAR KPIE 101853Z AUTO 36009KT 10SM SCT035 BKN048 OVC065 27/23 A2993 SPECI KPIE 101906Z 01006KT 10SM VCTS BKN036 BKN046 OVC060 28/22 A2993 RMK AO2 LTG DSNT NE-S T02780222 SPECI KPIE 101921Z 08011KT 10SM VCTS BKN029 BKN036 OVC046 27/23 A2994 RMK AO2 LTG DSNT NE-S T02670228 SPECI KPIE 101946Z 10012G18KT 10SM VCTS FEW008 SCT015 OVC025 25/23 A2994 RMK AO2 LTG DSNT ALQDS T02500228 METAR KPIE 101953Z 08013G20KT 10SM VCTS FEW009 SCT015 OVC025 25/23 A2993 RMK AO2 LTG DSNT ALQDS SLP135 T02500228 That could have been based on the lightning activity to the east (valid 1801Z):  But at 1938Z, a lightning bolt struck at the southern end of the airport:  ALDARS should have generated a SPECI, to promote the VCTS to a TS; yet, VCTS was still being reported at 1946Z and 1953Z. ALDARS missed that TS.88. Dannelly Field, Montgomery, Alabama, 10 Jun 2015:At 1936Z, a lightning bolt struck within 2 miles ESE of the airport:  Yet, only VCTS was recorded that hour: METAR KMGM 101853Z 13004KT 10SM VCTS BKN020 28/22 A2991 RMK AO2 LTG DSNT ALQDS TSB10 SLP125 T02830222 SPECI KMGM 101903Z 00000KT 10SM VCTS SCT024 29/22 A2990 RMK AO2 LTG DSNT ALQDS METAR KMGM 101953Z 20010KT 10SM SCT024 26/19 A2992 RMK AO2 LTG DSNT ALQDS TSE49 SLP127 T02560194 That should have been a thunderstorm from 1936Z-1951Z. Instead, ALDARS at KMGM ended even the VCTS at 1949Z. It shouldn't have:  The above map was valid at 1954Z. ALDARS missed a TS at KMGM.
|
|
|
|
Post by tornado on Jun 10, 2015 23:41:53 GMT -5
89.a. Toledo Express Airport, Ohio, 10 (11) Jun 2015:While monitoring a line of thunderstorms that had just passed through Chicago, I noticed a new line of storms forming in southern Michigan:  The last panel on that animation was valid at 0010Z on the 11th, which was the evening of the 10th. By 0035Z, several lightning bolts had struck to the east of Toledo Express Airport (KTOL), including one about a mile away:  By 0052Z, more bolts had struck, including 2 certainly within 3 miles of the airport:  Yet, though there was rain recorded by KTOL that hour, there was no mention of any lightning or thunder activity (and there were no SPECIs): METAR KTOL 102352Z 23007KT 10SM BKN060 BKN075 29/18 A2972 RMK AO2 SLP059 T02940183 10311 20294 53001 METAR KTOL 110052Z 00000KT 10SM BKN055 OVC070 28/20 A2972 Somehow, ALDARS (if installed) missed all that lightning nearby.89.b. Toledo Express Airport, Ohio, 10 (11) Jun 2015:Looking at the lightning animation below, one can see the storms in case 89.a. departing; but a new set of storms moved in:  That animation runs from 0210Z on the 11th, to 0350Z. Also, the Vaisala free lightning map showed this at 0320Z:  Clearly, there was a lot of lightning in the Toledo area for a second time this evening. At 0327Z, lightning struck about a mile south of the airport:  At 0335Z, lightning was still striking within 5 miles of the airport:  Yet, here were the reports coming out of Toledo Express Airport: METAR KTOL 110152Z 27003KT 10SM -RA BKN048 BKN065 OVC110 24/22 A2976 METAR KTOL 110252Z 25009KT 10SM BKN070 22/19 A2979 RMK AO2 RAE15 SLP082 P0000 60016 T02220194 53022 SPECI KTOL 110330Z VRB04KT 2 1/2SM +RA BR FEW029 SCT049 BKN110 21/20 A2983 RMK AO2 WSHFT 0313 RAB0254 P0004 T02110200 SPECI KTOL 110335Z 30007KT 280V340 1 1/4SM +RA BR SCT031 BKN049 21/20 A2984 RMK AO2 WSHFT 0313 RAB0254 P0017 T02110200 SPECI KTOL 110342Z 24008KT 2SM -RA BR BKN034 BKN050 BKN100 21/20 A2983 RMK AO2 WSHFT 0313 RAB0254 P0029 T02110200 SPECI KTOL 110350Z VRB05KT 10SM -RA SCT034 SCT048 BKN060 22/19 A2982 RMK AO2 WSHFT 0313 RAB0254 P0029 METAR KTOL 110352Z VRB05KT 10SM -RA SCT034 SCT048 BKN065 22/19 A2982 RMK AO2 WSHFT 0313 RAB0254 SLP095 P0029 T02170194 So, while lightning was striking as close as a mile away from the airport, ALDARS at KTOL again failed to detect any lightning! Or, if ALDARS is not installed, ATC failed to detect it! 2 thunderstorms passed over this airport this evening, according to lightning data; but KTOL failed to report them both.That is also what archived gridded lightning data, valid 10/2300-11/0100Z, shows:  90. Hawkins Field, Jackson, Mississippi, 10 (11) Jun 2015:I began monitoring this site around 0131Z. They had already had a nearby lightning strike:  But while this site reported light rain, and a wind gust to 28 knots, no thunder was reported. Only distant lightning was reported: METAR KHKS 110053Z 08016G23KT 10SM BKN041 BKN050 26/18 A2987 RMK AO2 LTG DSNT E-S SLP106 T02560183 SPECI KHKS 110110Z 13019G28KT 10SM -RA SCT039 BKN050 OVC065 24/20 A2990 RMK AO2 PK WND 14028/0106 WSHFT 0050 LTG DSNT E-S RAB08 P0000 T02390200= SPECI KHKS 110134Z 23010KT 10SM -RA BKN060 OVC090 23/19 A2993 RMK AO2 PK WND 14028/0106 WSHFT 0114 LTG DSNT E AND SE RAB08 P0000 T02280194 METAR KHKS 110153Z AUTO 25011KT 10SM -RA SCT065 BKN075 OVC100 23/20 A2993 RMK AO2 PK WND 14028/0106 WSHFT 0114 LTG DSNT E RAB08 SLP126 P0000 T02280200 However, at 0145Z, a lightning bolt struck within 2 miles west of the airport, southwest of the Shady Oaks Country Club:  So there was a lightning strike both before I began monitoring KHKS, and afterwards; either of
which should have triggered ALDARS to report a TS. But not even a VCTS was reported during that time period!
91. Ithaca, New York, 10 (11) Jun 2015:Like KHKS, here was another site that reported distant lightning (10-30 miles from the site), but nothing closer: METAR KITH 110156Z 16007KT 10SM CLR 22/16 A2976 RMK AO2 T02160161 SLP073 METAR KITH 110256Z AUTO 18009KT 10SM CLR 22/16 A2976 RMK AO2 58006 T02220161 LTG DSNT NW-NE SLP070 METAR KITH 110356Z AUTO 17008G16KT 090V210 10SM -RA SCT032 BKN055 OVC070 22/16 A2976 RMK AO2 T02220161 402720105 OVC V BKN LTG DSNT NE AND E RAB37 P0000 PK WND 30032/0334 PRESFR SLP072 ATC went home for the evening, and left it to ALDARS to report the approaching storms. However, in the same lightning animation used earlier for Toledo, one can see a line of thunderstorms near Rochester, New York; moving southeastward towards Ithaca: At 0314Z, a bolt struck within 2 miles to the northeast of KITH:  That should have begun a TS, but that didn't happen. By 0329Z, quite a bit of lightning was striking to the north of Ithaca:  ALDARS decided all that lightning was beyond 10 miles, as it never took a SPECI for VCTS, let alone TS. By 0336Z, there were 2 more close lightning bolts:  Yet, while there was a gust to 32 knots at 0334Z, ASOS did not generate a SPECI that hour. It should have. ASOS/ALDARS missed another thunderstorm.Attachments:
|
|
|
|
Post by tornado on Jun 11, 2015 12:32:31 GMT -5
92. Grand Strand Airport, N. Myrtle Beach, South Carolina, 9 Jun 2015:
On 9 Jun, Grand Strand Airport (KCRE) began a thunderstorm which produced a gust to 26 knots,
and took the airfield IFR:
METAR KCRE 091753Z 20017KT 10SM FEW046 SCT060 29/24 A2988
RMK AO1 LTG DSNT SW-N SLP117 60000 T02890244 10294
20256 58016
SPECI KCRE 091829Z 21017G26KT 10SM VCTS FEW010 SCT040 BKN060
27/24 A2987 RMK AO1 PK WND 22026/1826 LTG DSNT
NE AND SW AND W T02720239
METAR KCRE 091853Z 21017KT 10SM TS FEW039 27/24 A2987 RMK
AO1 PK WND 22026/1826 LTG DSNT NE AND S AND SW
RAB32E47 TSB46 SLP114 P0000 T02670239
SPECI KCRE 091914Z 23010G23KT 2SM -TSRA FEW011 SCT040 BKN060
24/22 A2986 RMK AO1 LTG DSNT NE RAB03 P0005 T02440217
The official start time of the thunderstorm was 1846Z. That registered as the time lightning was observed
within 5 miles. Prior to that, lightning within 10 miles had been detected as early as 1829Z.
However, at 1823Z, this was the lightning map:
Somehow, ALDARS ranged those bolts, as striking 5-10 miles from the airport. We can deduce this from the fact
that ALDARS and ASOS, without human input, takes 5 minutes to process a SPECI, and 1 minute to transmit a SPECI.
1823Z + 6 minutes = 1829Z, which was the time of the SPECI that began the VCTS. But the 1823Z map shows 4 lightning
bolts within 2 miles or so of the airport. 3 more lightning bolts struck at 1825Z, and one of those was on airport property:
ALDARS mistakenly ranged all those lightning bolts, as 5-10 miles from KCRE. A minute later, a nearby lightning bolt was detected by 24 stations:
So, the time between the first bolt within 5 miles, to the time ALDARS registered a TS, was 23 minutes. Users on the ground
could have used that extra 23 minutes of warning, because another bolt struck at the airport:
Another thing to note, is that if a SPECI had been transmitted right after the first bolt struck near the airport, it would have let
pilots know a thunderstorm was within 5 miles. The strongest wind gust produced by that cell, was at 1826Z. That was before
both the VCTS and the TS reported by KCRE. Look at the 1823Z chart again:
A contract weather observer would likely have taken a SPECI for any one of the 5 lightning strikes from the SW-W that were
a bit older (orange circles). Somehow, ALDARS missed those as well.
93. Augusta, Georgia, 9 Jun 2015:
Bush Field (KAGS) at Augusta, was reporting a thunderstorm in the vicinity (5-10 miles from the site) until 2013Z:
METAR KAGS 091853Z 13014KT 10SM VCTS BKN040 31/24 A2985 RMK
AO2 LTG DSNT ALQDS SLP105 T03110239
METAR KAGS 091953Z 13011KT 10SM VCTS SCT037 BKN060 BKN090
24/21 A2985 RMK AO2 LTG DSNT ALQDS RAB37E48 SLP106
P0000 T02440206
SPECI KAGS 092019Z 32017KT 9SM -TSRA FEW027 BKN039 25/20
A2988 RMK AO2 LTG DSNT ALQDS RAB17 TSB13 PRESRR
P0000 T02500200
SPECI KAGS 092024Z 34006G20KT 1 1/2SM +TSRA FEW015 SCT027
BKN038 24/20 A2988 RMK AO2 LTG DSNT ALQDS RAB17
TSB13 P0003 T02440200
SPECI KAGS 092029Z 11005KT 3/4SM +TSRA SCT017 BKN027 BKN038
23/19 A2989 RMK AO2 LTG DSNT ALQDS RAB17 TSB13
P0023 T02280194 RVRNO
However, KAGS should have begun the thunderstorm earlier. Here was the lightning display from 1950Z:
The first thing to note, is that there had been a lightning strike on the west side of the airport, within the past hour.
Yet, VCTS was all that was reported. Several new lightning strikes occurred to the E-S at 1950Z, at least 3 of
which were within 5 miles. Again, no TS was reported, until 23 minutes later. At 1953Z, 2 more lightning bolts
struck near the airport:
Those bolts were 20 minutes before the official start of a thunderstorm within 5 miles at KAGS that afternoon.
Pilots in the air, and resources on the ground, deserve better!
Late edit:
The time of the lightning strike to the west side of the airport, was 1927Z. This case is therefore upgraded to a level 5 on the FLAWD scale.
94. Lakefront Airport, New Orleans, Louisiana, 11 Jun 2015:
This morning, a brand new thunderstorm developed near Lakefront Airport (KNEW) just before 1612Z:
A thunderstorm was not officially reported until 1626Z:
METAR KNEW 111553Z 33007KT 10SM SCT042 BKN050 BKN080 31/22
A2995 RMK AO2 SLP134 T03060217
SPECI KNEW 111632Z 32013G22KT 8SM -TSRA BKN040 BKN050 OVC060
28/20 A2995 RMK AO2 PK WND 29028/1620 RAB21 TSB26
P0001 T02780200
That was a delay of 14 minutes. By 1621Z, there had been LTG SW-NW-NE:
More lightning struck even closer to the airport by 1632Z:
The faster lightning data can be properly detected and disseminated, the sooner pilots will be prepared for situations as above. Also, a peak wind of 28 knots, was never reported in the body of a SPECI that hour; it appeared in remarks 12 minutes after it occurred. A SPECI taken because of the 1612Z lightning, would have reported TS before that peak wind occurred- thus, pilots would have been more aware that wind gusts were possible upon takeoff or landing. |
|
|
|
Post by tornado on Jun 12, 2015 15:34:40 GMT -5
95. Cheyenne, Wyoming, 11 Jun 2015:Cheyenne (KCYS) recorded some light rain between 173Z and 1853Z on the 11th: METAR KCYS 111753Z 36009KT 10SM -RA FEW027 SCT045 BKN060 17/11 A2998 RMK AO2 RAB46 SLP084 P0000 60000 T01670111 10183 20139 55000= METAR KCYS 111853Z 35007KT 7SM -RA FEW060 BKN080 BKN095 14/12 A2999 RMK AO2 SLP090 P0001 T01440117 However, lightning data at 1812Z, with 5 and 10 mile range rings overlaid, showed that 3 lightning bolts struck within 5 miles of the airport, and 18 more struck from 5-10 miles away:  There should have been TS and VCTS recorded at KCYS sometime before 1812Z on the 11th. But, ALDARS
failed to record those strikes, and didn't even report LTG DSNT. 96. Grand Junction, Colorado, 11 Jun 2015:Grand Junction (KGJT) reported VCTS from 1846Z-1906Z on June 11th: METAR KGJT 111753Z 31011G15KT 10SM FEW023 SCT075 BKN120 20/15 A2996 RMK AO2 LTG DSNT SW SLP094 VCSH 60000 T02000150 10200 20139 58002 SPECI KGJT 111813Z 28011KT 10SM SCT024 SCT049 BKN095 19/14 A2997 RMK AO2 WSHFT 1753 LTG DSNT S VCSH T01890139 SPECI KGJT 111846Z 29009KT 10SM VCTS FEW047 BKN065 BKN090 17/14 A2996 RMK AO2 WSHFT 1753 LTG DSNT SE-SW VCSH T01670144 METAR KGJT 111853Z 29007KT 10SM VCTS SCT020 BKN049 OVC070 16/14 A2996 RMK AO2 WSHFT 1753 LTG DSNT S SLP101 VCSH T01610139 SPECI KGJT 111906Z 30009KT 9SM -RA SCT070 OVC085 16/14 A2997 RMK AO2 RAB01 P0000 T01560144 However, by 1835Z, lightning had clearly struck about 2 miles east of the airport:  At 1839Z, a bolt struck 3.32 miles NE of the airport:   That could have been that bolt that ALDARS used to begin the VCTS at 1846Z. If so, ALDARS ranged the
distance to the bolt incorrectly, and should have taken a SPECI for TS instead of VCTS.97. Erie, Pennsylvania, 12 Jun 2015:By 1920Z, a line of thunderstorms could be seen approaching Erie from the west, across Lake Erie:  Surely a convective sigmet was issued for that line of storms. The lightning showed up on Vaisala at 1920Z as well:  So it should have been no surprise, that this was the local lightning map at 1922Z:  At 1927Z, a lot of lightning was still striking nearby:  At 1936Z, 3 lightning bolts struck just south of the airport:  Despite all the lightning, here were the reports to come out of KERI that hour: METAR KERI 121851Z 22012G16KT 10SM SCT055 31/19 A2979 RMK AO2 SLP084 T03060189 SPECI KERI 121917Z 27020G41KT 2 1/2SM R06/5000VP6000FT -RA SQ FEW005 BKN060 BKN100 23/18 A2987 RMK AO2 PK WND 27041/1914 RAB14 PRESRR P0000 T02330183 SPECI KERI 121919Z 28023G41KT 1/2SM R06/2200VP6000FT +RA SQ FEW005 BKN060 OVC100 21/18 A2987 RMK AO2 PK WND 27041/1914 RAB14 PRESRR P0004 T02110183 SPECI KERI 121923Z 28018G41KT 1/4SM R06/1200VP6000FT +RA FG BKN010 BKN060 OVC100 21/18 A2985 SPECI KERI 121926Z 27017G36KT 1/4SM R06/1200VP6000FT +RA FG FEW005 BKN020 OVC090 21/19 A2985 RMK AO2 PK WND 27041/1914 WSHFT 1912 RAB14 P0047 T02060189 SPECI KERI 121932Z 26011G32KT 3/4SM R06/4500VP6000FT RA BR FEW005 BKN031 OVC100 21/19 A2986 RMK AO2 PK WND 27041/1914 WSHFT 1912 RAB14 P0051 T02060189 SPECI KERI 121940Z 25010G18KT 3SM RA FEW005 BKN070 OVC110 21/18 A2986 RMK AO2 PK WND 27041/1914 WSHFT 1912 RAB14 P0053 T02110183 METAR KERI 121951Z 25011KT 3SM -RA BR FEW044 OVC085 21/19 A2986 RMK AO2 PK WND 27041/1914 WSHFT 1912 RAB14 SLP107 P0055 T02110189 ALDARS at KERI (if installed) failed to detect any lightning at all! Or, if ALDARS is not installed at KERI,
ATC somehow missed reporting all that lightning. Also, there was a wind gust (squall) to 41 knots, at 1914Z, even before the lightning arrived. A contract weather observer would have likely reported 10SM SCT055CB along with movement, at 1951Z, to give users lead time for the bad weather moving towards the airport. Do we really want to give up lead time in such cases? Do we really want to rely on ALDARS, when there are times when it completely misses the lightning near airports? This is how much lightning it missed:  Note the valid time of the map, is displayed with the color scale below the top right corner. it is valid for the hour from 1900-2000Z on June 12th. Most of the 59 lightning bolts in the block to the east of KERI, are within the green 10-mile range ring; all of the 54 lightning strikes in the same block as KERI are within the green 10-mile range ring, and most of those are within the red 5-mile range ring.
|
|
|
|
Post by tornado on Jun 13, 2015 20:29:34 GMT -5
98. Aspen, Colorado, 13 Jun 2015:
Between 2053Z and 2153Z, Aspen (KASE) reported a thunderstorm in the vicinity:
METAR KASE 132053Z VRB04KT 10SM SCT075 BKN100 24/03 A3004
RMK AO2 LTG DSNT N AND SW SLP050 T02440028 58018
SPECI KASE 132102Z 34010G17KT 10SM VCTS SCT075 BKN100 24/04
A3004 RMK AO2 T02440044
METAR KASE 132153Z 08009G17KT 10SM SCT090 BKN110 21/05 A3004
RMK AO2 LTG DSNT ALQDS TSB12E13E49 SLP060 T02060050
However, the ALDARS malfunctioned, as evidenced by the remark on the 2153Z METAR. It read,
TSB12E13E49. That doesn't match the beginning time of the VCTS, which was 10 minutes earlier
at 2102Z. If ALDARS was trying to record a thunderstorm within 5 miles, a SPECI was never sent
nor generated for that reason. A 1-minute thunderstorm (TSB12E13) is against FAA rules anyway.
So, what happened?
At 2055Z, there was a lightning bolt that struck in the mountains to the northeast, close enough that
ALDARS/ASOS sent a SPECI 7 minutes later:
That appears to be the bolt that triggered ALDARS to take the SPECI. 2055Z + 1 minute for ALDARS
to process the data, + 5 minutes for ASOS to generate a SPECI, + 1 minute for ASOS to transmit the
SPECI, = 2102Z; which was the time of the SPECI. So far, so good.
At 2129Z, however, there were 2 lightning bolts that struck near KASE. The one to the northeast was
about a mile from the runway:
ALDARS either did nothing with that lightning bolt; or somehow failed to generate a SPECI, while
retaining the data as valid to begin a thunderstorm. For, if the latter is true, we would expect the same
7 minute processing time for ALDARS and ASOS to end the TS, + the 15 minutes of the TS itself.
That would bring us to 2151Z. However, the bolt that actually struck at 2129Z was the bolt to the east;
the bolt a mile to the northeast was slightly older. It seems that it was 2 minuets older. It was still
bright yellow on the map; and subtracting 2 minutes would bring the ending time of the thunderstorm
to 2149Z- the second ending time in the remark on the 2153Z METAR! So, pilots and users on the ground
should have been alerted to lightning within 5 miles; but somehow, ALDARS failed to disseminate the
proper SPECI. So when we see ALDARS reporting remarks that include 2 ending times, without an intervening thunderstorm beginning time; it appears that there is an internal issue with the lightning algorithm in such cases. 99. Aurora, Illinois, 13 Jun 2015:As early as 2319Z, ATC should have been aware that there was lightning nearby:  Surely there was a convective SIGMET out for those storms:  By 2345Z, there had been a lot of lightning near KARR in the past hour:  At 2345Z, here was an overlay showing the lightning strikes around Aurora (KARR):  But, here were the reports from Aurora IL from that hour. Notice the complete lack of anylightning data: METAR KARR 132252Z 00000KT 1 1/4SM HZ CLR 27/22 A2990 RMK AO2 PRESRR SLP119 T02720222 $ SPECI KARR 132302Z 00000KT 8SM FEW065 FEW075 SCT110 27/22 A2989 RMK AO2 T02670217 $ METAR KARR 132352Z 18009KT 10SM SCT029 SCT040 BKN090 24/19 A2992 RMK AO2 RAB10E20 SLP128 P0000 60000 T02390189 10294 20239 53002 $ As documented on page 49 of the "More quality from the ATCT" thread, the 2302Z SPECI was transmitted to fix a glitch in the ASOS visibility sensor that occurred on the 2252Z METAR. ATC didn't notice the glitch for several minutes (and didn't check the METAR before it transmitted); and ATC didn't notice nearby lightning. The overlay referred to above, shows 1 (possibly 2) lightning strikes within 5 miles, but no TS was reported.
The overlay also shows 9-12 lightning strikes from 5-10 miles away, but no VCTS was recorded. Beyond that,
there was more lightning within 30 miles to the east through south, but LTG DSNT E-S was not recorded. ALDARS
simply failed to properly detect lightning near KARR that hour!Archived gridded lightning data, showed 1152 lightning strikes in a grid to the south of Aurora. How many of those bolts met LTG DSNT criteria?  According to the position of the blue 30-mile range ring, most of them! 100. Dannelly Field, Montgomery, Alabama, 13 (14) Jun 2015:At Dannelly Field (KMGM) near Montgomery, it was a warm, partly cloudy afternoon: METAR KMGM 132153Z 12007KT 10SM SCT047 SCT065 BKN090 32/22 A3004 RMK AO2 SLP168 T03220222 But the next hour, ATC signed off ASOS: METAR KMGM 132253Z AUTO 11004KT 10SM FEW047 SCT055 31/22 A3006 RMK AO2 SLP175 T03060222 TSNOThe TSNO remark indicated no thunderstorm information was available. That's degradation of service right there. Why they would sign off, when there were thunderstorms approaching?  The next several reports, were SPECIs due to moderate-heavy rain, dropping the airfield into IFR conditions: SPECI KMGM 132315Z 14019G30KT 1/2SM +RA FEW016 BKN060 27/22 A3008 RMK AO2 PK WND 14030/2314 RAB10 PRESRR P0001 T02720222 SPECI KMGM 132327Z 03006KT 1 1/4SM +RA BKN018 BKN050 OVC060 26/22 A3009 RMK AO2 PK WND 14030/2314 RAB10 P0033 T02560217 SPECI KMGM 132329Z VRB06KT 2SM RA BKN020 BKN048 OVC060 26/22 A3009 RMK AO2 PK WND 14030/2314 RAB10 P0033 T02560217 SPECI KMGM 132338Z 14009KT 3SM RA SCT020 BKN034 OVC050 26/22 A3011 RMK AO2 PK WND 14030/2314 RAB10 PRESRR P0040 T02560217 METAR KMGM 132353Z 12004KT 10SM -RA SCT033 BKN075 OVC110 25/21 A3011 RMK AO2 PK WND 14030/2314 RAB10 SLP194 P0040 60040 T02500211 10339 20244 53020 By 2315Z, ATC had signed back on to ASOS, and a SPECI with low IFR conditions and a wind gust to 30 knots, was transmitted. There were no thunderstorm or lightning data on any report that hour- although putting ASOS into TSNO mode would preclude it from reporting such data. Nor was there any LTG nor TS data on the next hourly report: METAR KMGM 140053Z 00000KT 10SM SCT095 SCT120 24/22 A3012 RMK AO2 RAE04B24E43 SLP197 P0000 T02440217 Yet, as of 0008Z, lightning data clearly showed many lightning strikes near KMGM:  An overlay of range rings onto the map above, shows this:  There were 4 lightning strikes within 5 miles, that should have generated a thunderstorm, but didn't. There were an additional 26
lightning strikes from 5-10 miles from the airport, that should have generated a VCTS; that didn't happen either. There were many
other lightning strikes that should have been reported as LTG DSNT E-S AND W-N, but weren't. Is this because ATC put ASOS into
AUTO/TSNO mode? Or was this an ALDARS failure? Either way, it's unacceptable, and our pilots deserve better! This habit of ATC putting ASOS into AUTO mode, when thunderstorms approach the airport, is dangerous enough at level C sites; let alone larger airports! |
|
|
|
Post by tornado on Jun 16, 2015 14:55:45 GMT -5
After documenting 100 cases of ALDARS issues at LAWRS sites (though ALDARS may not be installed at many LAWRS sites),
I will stop documenting marginal cases. If I see something serious, I will continue to document it.
Here's something a bit different.
101. Ogden, Utah, 15 Jun 2015:
Hinckley Field at Ogden (KOGD) has been in AUTO mode for several days- ever since this report:
METAR KOGD 112153Z 15015KT 10SM BKN060 23/13 A2992 RMK AO2
RAB18E29 SLP079 P0000 T02330128
Yesterday, I monitored this site, as there was a strong thunderstorm nearby:
 
The first chart was valid at 1649Z; the 2nd chart was valid at 1717Z. The below radar summary was valid at 1730Z:
That radar summary showed a cell with a 45,000 foot top, hail, and a mesocyclone; just SW of KOGD. Archived lightning
data shows much lightning near KOGD yesterday:
 
The first chart was valid at 1700Z, while the 2nd was valid at 1730Z. At 1658Z, live lightning data showed lightning strikes
to the northeast of Ogden:
Overlaying 5 and 10 mile range rings onto the above lightning map, shows that a VCTS should have been reported at KOGD:
Later, at 1744Z, lightning was still striking within 10 miles to the southeast of Ogden:
Yet, here were the reports out of KOGD, which is a level C LAWRS site:
METAR KOGD 151553Z AUTO 31003KT 10SM CLR 26/07 A3000 RMK
AO2 SLP097 T02610072 TSNO
METAR KOGD 151653Z AUTO 35006KT 10SM OVC110 24/09 A3001 RMK
AO2 RAB26E36 SLP107 P0000 T02440094 TSNO
METAR KOGD 151753Z AUTO 16009KT 10SM CLR 24/11 A2998 RMK
AO2 RAB08E28 SLP097 P0000 60000 T02440111 10261
20172 58002 TSNO
Why was this site in AUTO/TSNO mode, with a thunderstorm nearby? Light traffic?
At 1659Z, Allegiant Air 103 had just departed for Phoenix/Mesa. That was an MD-80, which holds 130-180 passengers. The pilots
deserved to have better weather information than an ASOS in TSNO mode. A small plane later had to make a weather diversion:
Those were 2 aircraft that had to deal with the unreported thunderstorms (there were actually 2 cells on either side of KOGD). ATC had time to augment ASOS, but did not. ALDARS, if installed at that site, was turned off. If this sort of thing happens at smaller airports, what will prevent it from happening at larger airports?
Lastly, here is an archived audio feed from LiveATC.net:
KOGD-Jun-15-2015-1700Z.mp3 (3.6 MB)
The valid time of the feed begins at 1700Z, and it runs for about half an hour. Though there is a lot of silence on the feed,
one can ascertain the time of transmissions by looking at the time into the feed, and adding it to 1700Z. About 21-22 minutes
into the audio feed (1721Z or so), the controller & pilot of Asterisk 5038Y discuss weather conditions when 5038Y was 15 miles
to the south. The pilot had information kilo (which should have been the 1653Z METAR, still in AUTO/TSNO mode) The pilot
asked if there was heavy rain on the field; the controller said “on the field, no, there’s none at all, it’s actually moving to the south.”
The rain was actually moving ENE, according to radar! Then they discussed not to go thru Hill AFB airspace; the pilot said he will
go way west and then approach KOGD from the SW. However, that’s where the 45,000-foot thunderstorm cell was! Fortunately
that plane landed safely. But there was no mention of thunderstorm activity during that half hour; and the activity that was there,
wasn't moving south. Should a level C LAWRS airport be in AUTO/TSNO mode, with that much lightning nearby?
102. Allegheny County Airport, Pittsburgh, Pennsylvania, 18 Jun 2015:
Below is the lightning display centered on Allegheny County Airport (KAGC), valid 0215Z on June 19th (which was June 18th local time):
There were 19 lightning strikes within the red range ring. That ring represents 5 miles from KAGC. Most of the strikes were 3-5 miles
away. Still, any or all of those bolts should have triggered a TS at KAGC. They did not:
METAR KAGC 190053Z 25007KT 10SM CLR 26/18 A2994 RMK AO2 SLP134
T02560183
SPECI KAGC 190131Z 28008G25KT 260V330 3/4SM R28/2000VP6000FT
+RA SCT014 SCT030 BKN045 20/17 A2996 RMK AO2 RAB24
P0039 T02000172
SPECI KAGC 190138Z 33008G15KT 5SM R28/4500VP6000FT RA SCT020
BKN041 OVC110 20/17 A2997 RMK AO2 RAB24 P0044
T02000172
METAR KAGC 190153Z 28008KT 5SM RA SCT023 OVC070 20/17 A2999
RMK AO2 RAB24 PRESRR SLP153 P0046 T02000172
METAR KAGC 190253Z 28014G29KT 5SM RA SCT046 BKN075 OVC100
19/16 A3003 RMK AO2 PK WND 28029/0250 SLP167 P0009
60055 T01940161 53028
Those 19 lightning strikes were older, as the brown color indicates. But since they hadn't dropped off the map, they occurred
within the past hour. That means they occurred sometime between 0115Z-0215Z. But, while the METARs and SPECIs above
included moderate-heavy rain, and at 0131Z low IFR conditions due to poor visibility; there was no mention of thunderstorm
or lightning activity during that time frame. ALDARS simply missed all that lightning; or, if ALDARS is not installed at that
site, ATC missed it.
Here's another problem: archived lightning data showed a lot of strikes in the Pittsburgh area at 19/0100Z:
KAGC reported clear skies at 0053Z, and 3/4SM +RA at 0131Z. But no thunder was reported.
Across town, the contract weather observer at Pittsburgh International Airport, did have thunderstorms:
SPECI KPIT 190056Z 31025G46KT 1/2SM R28R/2400VP6000FT +TSRA
FEW025 BKN039CB OVC110 24/20 A2997 RMK AO2 RAB52
PRESRR FRQ LTGICCG OHD TS OHD MOV E P0000 T02440200
SPECI KPIT 190225Z 26015G29KT 1SM R28R/5000VP6000FT +TSRA
BR FEW017 BKN030CB OVC055 20/18 A3003 RMK AO2
PK WND 26029/0225 TSB21 OCNL LTGICCC OHD TS OHD
MOV E P0002 T02000183
So Pittsburgh had a near-severe thunderstorm last evening at one of its airports; and no thunderstorms reported at another. KAGC
definitely should have reported a thunderstorm, based on all the above, plus archived gridded lightning data:
The map above is valid from 0100Z-0300Z on June 19th, which was the evening of the 18th local time. There were 21 lightning strikes within the same grid as KAGC airport. Many of the 25 strikes in the grid to the west, would have met TS criteria; and some of those 134 lightning strikes in the grid to the north, would have met VCTS criteria. KAGC didn't even report VCTS during that time.
103. Athens, Georgia, 18 Jun 2015:
By 1926Z on the 18th, this was the lightning display at Ben Epps Airport (KAHN) near Athens:
Note that there were 13 lightning strikes from 5-10 miles way, from W-N. There was also a bolt that struck about 6 miles ESE.
But the closest bolt was just inside the red 5-mile range ring, to the north. There were older bolts that had struck outside the
green 10-mile range ring, to the NW; but the bolts that had struck within 10 miles were younger. KAHN should have reported
at least a VCTS in this situation. They did not:
METAR KAHN 181851Z VRB03KT 8SM FEW014 FEW110 36/21 A3007
RMK AO2 RAB21E39 SLP172 P0000 T03560206
SPECI KAHN 181909Z 08006KT 1 3/4SM HZ CLR 33/21 A3006 RMK
AO2 T03330211
SPECI KAHN 181912Z 10004KT 3/4SM HZ VV002 33/21 A3006 RMK
AO2 VIS 1/4V5 T03330211
SPECI KAHN 181916Z 11004KT 3/4SM HZ VV015 33/21 A3006 RMK
AO2 VIS 1/4V5 T03280211
SPECI KAHN 181919Z VRB03KT 1SM HZ FEW018 FEW055 33/21 A3006
RMK AO2 T03280211
SPECI KAHN 181922Z VRB05KT 4SM HZ FEW029 SCT055 SCT080 32/22
A3007 RMK AO2 T03220217
METAR KAHN 181951Z 36005KT 6SM HZ FEW045 FEW060 SCT080 28/21
A3006 RMK AO2 RAB23E34 SLP169 P0000 T02780206
SPECI KAHN 182014Z 00000KT 1 1/2SM HZ FEW002 28/20 A3005
RMK AO2 T02830200
SPECI KAHN 182024Z 00000KT 3SM HZ FEW002 29/20 A3004 RMK
AO2 T02890200
METAR KAHN 182051Z 00000KT 10SM CLR 29/19 A3003 RMK AO2 SLP162
60000 T02940194 56020
Instead of reporting VCTS, ASOS had some spurious haze glitches. ATC did not fix those. While haze often occurs
after a thunderstorm, this was out ahead of thunderstorms:
Yes, N414RK made it to KAHN safely, after diverting around the thunderstorm to the W-N of KAHN:
Didn't that pilot deserve to have METAR/SPECIs with accurate thunderstorm information? |
|
|
|
Post by fu on Jun 16, 2015 15:15:22 GMT -5
That is some damn good stuff Tornado.
|
|
I will pick up the project again, when I get back. 
