C172 with MKE TRACON experienced multiple go-around events on RNAV (GPS) 28 approach to UES; allegedly due to ATC's vectoring techniques; ATC indicated airspace confinements prohibited better vectors.

Date: 2009-05 · Aircraft: Skyhawk 172/Cutlass 172 · Phase: approach

Anomalies: atc-issue-all-types

Synopsis

C172 with MKE TRACON experienced multiple go-around events on RNAV (GPS) 28 approach to UES; allegedly due to ATC's vectoring techniques; ATC indicated airspace confinements prohibited better vectors.

Narrative

Requested vectors for the RNAV (GPS) 28 approach to UES. Controller seemed reluctant to grant request. Vectored us to an intercept about 3 miles from the FAF and cleared us for the approach. Intercept angle/vector pointed us straight at the FAF with little hope of capture prior to crossing FAF. We declared a missed approach (did not descend) and requested vectors for another attempt. This time we included a request to join the final approach course further out from the FAF. Intercept vector was given 5 miles from FAF but still only allowed for capture to occur at the FAF. Declared missed approach again and requested vectors to the other side of the airport for an ILS 10 circle Runway 28. Landed without incident. During vectors for third approach; Controller asked what the problem was. I explained that we needed better vectors for positive course intercept outside of the FAF to establish proper course tracking prior to descent. Controller explained that he could not offer us any better vectoring without conflicting with Milwaukee International arrival and departure operations. Had I known this previously; we would not have made the request.

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.