Narrative:

On approach to ord runway 22L, microburst alert was issued for short final runway 22L. A missed approach was executed. Dispatch was contacted to add a suitable alternate, mke for fuel. We determined we had adequate fuel for 1 additional approach attempt at ord and would then be required to proceed to mke for fuel. On downwind to ord runway 22L, the final controller informed us that no one had completed final since we last attempted and that the tower was still receiving microburst alerts. We elected to proceed to the alternate agreed upon with dispatch (mke) without making the second approach. We sent an ACARS report of our diversion and ETA. We landed at mke, refueled, and returned to ord. Upon arrival ord runway 22R, we again received a microburst alert below 1000 ft. We executed a missed approach and after a delay period returned to ord and landed on runway 22R. During the first missed approach at ord, the departure controller gave us a frequency change at about the same time as we received the SELCAL from commercial radio for our connection to dispatch. When I finished conferring with dispatch and we determined our 'bingo' fuel, I notified ATC that we were ready for our return to ord. The controller asked us to state our position and asked if we were on a missed approach. I said yes and he gave us a new frequency for our return to ord. We did not have any indication of an encounter with a 'microburst' and believe the tower alerts were generated by the strong surface winds blowing across the midwest that afternoon. If a 'microburst alert' is being generated, our company policy and good operating practices says go around. Supplemental information from acn 420012: during a VMC approach to runway 22L at ord, tower reported surface winds of 230 degrees, 25 KTS, gusting to 39 KTS and issued a microburst alert for runway 22L. No evidence of microburst activity was encountered in a missed approach that was initiated as a result of the alert. No microburst activity was encountered and conditions normally associated with microbursts were not present. There was no convective activity in the area and the surface wind and approach wind were nearly the same. The tower reported that the alert had persisted for over 20 mins and no aircraft had landed. We made an uneventful approach and landing encountering light to moderate turbulence normal for the gusty wind conditions, but experienced no windshear.

Google
 

Original NASA ASRS Text

Title: ON APCH TO ORD RWY 22L, A B737 FLC RECEIVE NOTIFICATION OF A LLWAS MICROBURST ALERT AND EXECUTE A MISSED APCH. THE PIC PROCEEDS TO ALTERNATE ARPT WHEN ADVISED MICROBURST RPTS ARE STILL BEING RECEIVED. FLC RETURN TO ORD, RECEIVE ANOTHER ALERT, EXECUTE A MISSED APCH, RETURN LAND, EVEN THOUGH RECEIVING OTHER MICROBURST ALERT.

Narrative: ON APCH TO ORD RWY 22L, MICROBURST ALERT WAS ISSUED FOR SHORT FINAL RWY 22L. A MISSED APCH WAS EXECUTED. DISPATCH WAS CONTACTED TO ADD A SUITABLE ALTERNATE, MKE FOR FUEL. WE DETERMINED WE HAD ADEQUATE FUEL FOR 1 ADDITIONAL APCH ATTEMPT AT ORD AND WOULD THEN BE REQUIRED TO PROCEED TO MKE FOR FUEL. ON DOWNWIND TO ORD RWY 22L, THE FINAL CTLR INFORMED US THAT NO ONE HAD COMPLETED FINAL SINCE WE LAST ATTEMPTED AND THAT THE TWR WAS STILL RECEIVING MICROBURST ALERTS. WE ELECTED TO PROCEED TO THE ALTERNATE AGREED UPON WITH DISPATCH (MKE) WITHOUT MAKING THE SECOND APCH. WE SENT AN ACARS RPT OF OUR DIVERSION AND ETA. WE LANDED AT MKE, REFUELED, AND RETURNED TO ORD. UPON ARR ORD RWY 22R, WE AGAIN RECEIVED A MICROBURST ALERT BELOW 1000 FT. WE EXECUTED A MISSED APCH AND AFTER A DELAY PERIOD RETURNED TO ORD AND LANDED ON RWY 22R. DURING THE FIRST MISSED APCH AT ORD, THE DEP CTLR GAVE US A FREQ CHANGE AT ABOUT THE SAME TIME AS WE RECEIVED THE SELCAL FROM COMMERCIAL RADIO FOR OUR CONNECTION TO DISPATCH. WHEN I FINISHED CONFERRING WITH DISPATCH AND WE DETERMINED OUR 'BINGO' FUEL, I NOTIFIED ATC THAT WE WERE READY FOR OUR RETURN TO ORD. THE CTLR ASKED US TO STATE OUR POS AND ASKED IF WE WERE ON A MISSED APCH. I SAID YES AND HE GAVE US A NEW FREQ FOR OUR RETURN TO ORD. WE DID NOT HAVE ANY INDICATION OF AN ENCOUNTER WITH A 'MICROBURST' AND BELIEVE THE TWR ALERTS WERE GENERATED BY THE STRONG SURFACE WINDS BLOWING ACROSS THE MIDWEST THAT AFTERNOON. IF A 'MICROBURST ALERT' IS BEING GENERATED, OUR COMPANY POLICY AND GOOD OPERATING PRACTICES SAYS GAR. SUPPLEMENTAL INFO FROM ACN 420012: DURING A VMC APCH TO RWY 22L AT ORD, TWR RPTED SURFACE WINDS OF 230 DEGS, 25 KTS, GUSTING TO 39 KTS AND ISSUED A MICROBURST ALERT FOR RWY 22L. NO EVIDENCE OF MICROBURST ACTIVITY WAS ENCOUNTERED IN A MISSED APCH THAT WAS INITIATED AS A RESULT OF THE ALERT. NO MICROBURST ACTIVITY WAS ENCOUNTERED AND CONDITIONS NORMALLY ASSOCIATED WITH MICROBURSTS WERE NOT PRESENT. THERE WAS NO CONVECTIVE ACTIVITY IN THE AREA AND THE SURFACE WIND AND APCH WIND WERE NEARLY THE SAME. THE TWR RPTED THAT THE ALERT HAD PERSISTED FOR OVER 20 MINS AND NO ACFT HAD LANDED. WE MADE AN UNEVENTFUL APCH AND LNDG ENCOUNTERING LIGHT TO MODERATE TURB NORMAL FOR THE GUSTY WIND CONDITIONS, BUT EXPERIENCED NO WINDSHEAR.

Data retrieved from NASA's ASRS site as of July 2007 and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.