Narrative:

Approaching the mke airport; we were vectored for the approach (visual runway 7R) high and we were too high. We didn't expect a short approach. At approximately 1.5 mi from the runway and approximately 850 ft AGL; we did not meet stabilized approach criteria; so I called for a go around. The PF (first officer) hit toga but did not make the appropriate callouts. Go around power flaps 15 degrees. I called positive rate and he called gear up; but I was slow in raising the flaps. Busy trying to turn the heading bug and altitude selector. My mistake was calling the tower before completing the basic go around tasks. We had plenty of altitude and the PF did a good job of flying close to the flap limit speed but it is possible the aircraft exceeded the flap limit speed. The flaps were at 40 degrees. The PF called for flaps 40 degrees (at appropriate speed) in an attempt to set up a stabilized approach. It was shortly after selecting flaps 40 degrees that I called for the go around. We completed the climb check and ATC gave us vectors for another short approach. This one even shorter than the first one! Well inside the FAF. After turning toward the runway; it was immediately obvious the approach wasn't going to work so I called for a second go around. This time it was a textbook go around. We were aware of our fuel situation (about 4.3 ttl) but when we turned downwind to base for the third approach (uneventful) the left fuel indicator low warning illuminated. (It seemed to stay at about 1.93?) of note: the next day; we were holding short of runway 7R for takeoff when an rj had to execute a go around. The tower controller asked 'why...high and fast?' the rj crew replied 'yes.' re possible flap overspd: when discussing the event the following day; the first officer remembered the airspeed indicator was right up against the red limit speed. We remain uncertain if a flap overspd condition existed. After the second go around it was clear to me that I had to be very clear and assertive in telling ATC exactly what we wanted. Time and long vectors to final. They cooperated and the third approach was uneventful. No notice from ATC that we could expect a short approach. My experience with mke was that we always had long downwinds and plenty of time to go down/slow down. I had a 'mindset' for a normal length downwind and also no 'heads up' for a short approach from ATC. Anywhere we fly; an advance notification 'expect short approach' from ATC is very helpful. At other airports where we are cleared for the visual on the downwind; we are able to judge just how much farther we should remain on the downwind in order to position ourselves for a stabilized approach. In mke's case; ATC gave us vectors to base before clearing us for the approach. They seemed very anxious for us to call the field in sight. As captain; I should have applied command authority/authorized and not accepted the unacceptable vectors for a short approach. Especially; the second time. After the first go around; I failed to communication to ATC our need to have an extended downwind. I guess I might have assumed ATC would know that an air transport aircraft cannot safely do a go around/missed approach and land so quickly. End of 12 hour duty day could have compromised my performance. Mke approach should be better acquainted with the safe limits of air transport aircraft and our requirement for and definition of stabilized approach so if they vector us for a visual; the aircraft will be able to meet stabilized approach criteria. A notification from ATC on downwind 'expect short approach' would be very helpful. I recommend they be counseled on the latter. To avoid being rushed after any go around; tell ATC that we need at least an 8 mi downwind to give us time to set up for the next approach (time to orderly complete the climb check; brief passenger/flight attendants; restring the approach; and complete the in-range checklist). Approaching or during the downwind leg; we could ask ATC 'how long is the final?'

Google
 

Original NASA ASRS Text

Title: FLT CREW OF MEDIUM TRANSPORT MUST GAR TWICE DUE TO BEING HIGH AND FAST DURING VISUAL APCHS.

Narrative: APCHING THE MKE ARPT; WE WERE VECTORED FOR THE APCH (VISUAL RWY 7R) HIGH AND WE WERE TOO HIGH. WE DIDN'T EXPECT A SHORT APCH. AT APPROX 1.5 MI FROM THE RWY AND APPROX 850 FT AGL; WE DID NOT MEET STABILIZED APCH CRITERIA; SO I CALLED FOR A GAR. THE PF (FO) HIT TOGA BUT DID NOT MAKE THE APPROPRIATE CALLOUTS. GAR PWR FLAPS 15 DEGS. I CALLED POSITIVE RATE AND HE CALLED GEAR UP; BUT I WAS SLOW IN RAISING THE FLAPS. BUSY TRYING TO TURN THE HDG BUG AND ALT SELECTOR. MY MISTAKE WAS CALLING THE TWR BEFORE COMPLETING THE BASIC GAR TASKS. WE HAD PLENTY OF ALT AND THE PF DID A GOOD JOB OF FLYING CLOSE TO THE FLAP LIMIT SPD BUT IT IS POSSIBLE THE ACFT EXCEEDED THE FLAP LIMIT SPD. THE FLAPS WERE AT 40 DEGS. THE PF CALLED FOR FLAPS 40 DEGS (AT APPROPRIATE SPD) IN AN ATTEMPT TO SET UP A STABILIZED APCH. IT WAS SHORTLY AFTER SELECTING FLAPS 40 DEGS THAT I CALLED FOR THE GAR. WE COMPLETED THE CLB CHK AND ATC GAVE US VECTORS FOR ANOTHER SHORT APCH. THIS ONE EVEN SHORTER THAN THE FIRST ONE! WELL INSIDE THE FAF. AFTER TURNING TOWARD THE RWY; IT WAS IMMEDIATELY OBVIOUS THE APCH WASN'T GOING TO WORK SO I CALLED FOR A SECOND GAR. THIS TIME IT WAS A TEXTBOOK GAR. WE WERE AWARE OF OUR FUEL SITUATION (ABOUT 4.3 TTL) BUT WHEN WE TURNED DOWNWIND TO BASE FOR THE THIRD APCH (UNEVENTFUL) THE L FUEL INDICATOR LOW WARNING ILLUMINATED. (IT SEEMED TO STAY AT ABOUT 1.93?) OF NOTE: THE NEXT DAY; WE WERE HOLDING SHORT OF RWY 7R FOR TKOF WHEN AN RJ HAD TO EXECUTE A GAR. THE TWR CTLR ASKED 'WHY...HIGH AND FAST?' THE RJ CREW REPLIED 'YES.' RE POSSIBLE FLAP OVERSPD: WHEN DISCUSSING THE EVENT THE FOLLOWING DAY; THE FO REMEMBERED THE AIRSPD INDICATOR WAS RIGHT UP AGAINST THE RED LIMIT SPD. WE REMAIN UNCERTAIN IF A FLAP OVERSPD CONDITION EXISTED. AFTER THE SECOND GAR IT WAS CLR TO ME THAT I HAD TO BE VERY CLR AND ASSERTIVE IN TELLING ATC EXACTLY WHAT WE WANTED. TIME AND LONG VECTORS TO FINAL. THEY COOPERATED AND THE THIRD APCH WAS UNEVENTFUL. NO NOTICE FROM ATC THAT WE COULD EXPECT A SHORT APCH. MY EXPERIENCE WITH MKE WAS THAT WE ALWAYS HAD LONG DOWNWINDS AND PLENTY OF TIME TO GO DOWN/SLOW DOWN. I HAD A 'MINDSET' FOR A NORMAL LENGTH DOWNWIND AND ALSO NO 'HEADS UP' FOR A SHORT APCH FROM ATC. ANYWHERE WE FLY; AN ADVANCE NOTIFICATION 'EXPECT SHORT APCH' FROM ATC IS VERY HELPFUL. AT OTHER ARPTS WHERE WE ARE CLRED FOR THE VISUAL ON THE DOWNWIND; WE ARE ABLE TO JUDGE JUST HOW MUCH FARTHER WE SHOULD REMAIN ON THE DOWNWIND IN ORDER TO POS OURSELVES FOR A STABILIZED APCH. IN MKE'S CASE; ATC GAVE US VECTORS TO BASE BEFORE CLRING US FOR THE APCH. THEY SEEMED VERY ANXIOUS FOR US TO CALL THE FIELD IN SIGHT. AS CAPT; I SHOULD HAVE APPLIED COMMAND AUTH AND NOT ACCEPTED THE UNACCEPTABLE VECTORS FOR A SHORT APCH. ESPECIALLY; THE SECOND TIME. AFTER THE FIRST GAR; I FAILED TO COM TO ATC OUR NEED TO HAVE AN EXTENDED DOWNWIND. I GUESS I MIGHT HAVE ASSUMED ATC WOULD KNOW THAT AN AIR TRANSPORT ACFT CANNOT SAFELY DO A GAR/MISSED APCH AND LAND SO QUICKLY. END OF 12 HR DUTY DAY COULD HAVE COMPROMISED MY PERFORMANCE. MKE APCH SHOULD BE BETTER ACQUAINTED WITH THE SAFE LIMITS OF AIR TRANSPORT ACFT AND OUR REQUIREMENT FOR AND DEFINITION OF STABILIZED APCH SO IF THEY VECTOR US FOR A VISUAL; THE ACFT WILL BE ABLE TO MEET STABILIZED APCH CRITERIA. A NOTIFICATION FROM ATC ON DOWNWIND 'EXPECT SHORT APCH' WOULD BE VERY HELPFUL. I RECOMMEND THEY BE COUNSELED ON THE LATTER. TO AVOID BEING RUSHED AFTER ANY GAR; TELL ATC THAT WE NEED AT LEAST AN 8 MI DOWNWIND TO GIVE US TIME TO SET UP FOR THE NEXT APCH (TIME TO ORDERLY COMPLETE THE CLB CHK; BRIEF PAX/FLT ATTENDANTS; RESTRING THE APCH; AND COMPLETE THE IN-RANGE CHKLIST). APCHING OR DURING THE DOWNWIND LEG; WE COULD ASK ATC 'HOW LONG IS THE FINAL?'

Data retrieved from NASA's ASRS site as of May 2009 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.