Narrative:

On descent into cwa (central wisconsin -- mosinee, wi). Good flight visibility with the field in sight. ZMP gave us a turn to the back course approach runway 26. We advised the field in sight and canceled our IFR. On contacting the tower, he advised us the field was IFR (we still had it in sight). We were set up for runway 35 but he could not clear us in the localizer. I asked for an SVFR, but first misspoke and asked for a contact approach, then the special. We got the special from the tower and landed runway 35. Flight visibility of nearly 10 mi the whole time. Tower wanted us to call up so after shutdown, I called the tower controller. He said he was a VFR tower and could not give contact approachs. I apologized for the miscom. (I don't think I was supposed to know that he was a VFR only tower and couldn't do that.) regardless, it was a miscom. Tower said he had called center prior to our contacting him and he told the center the field was IFR and everyone had to do the approach. He also said he almost had a lack of separation with a departing regional jet in the opposite direction. We were unaware of any departing traffic from center or the tower. He also said on the phone that there was no problem, he just wanted to try and figure out what went wrong so we could try and keep it from happening in the future. Supplemental information from acn 607965: we were planning a visual approach, but minneapolis issued a vector for the back course runway 27 other than runway 35 which we were lined up for and still had easily in sight. We discovered later from tower that center had released an IFR turboprop around this same time.

Google
 

Original NASA ASRS Text

Title: SH33 INBOUND TO SWA REQUESTS VISUAL APCH DURING IFR WX.

Narrative: ON DSCNT INTO CWA (CENTRAL WISCONSIN -- MOSINEE, WI). GOOD FLT VISIBILITY WITH THE FIELD IN SIGHT. ZMP GAVE US A TURN TO THE BACK COURSE APCH RWY 26. WE ADVISED THE FIELD IN SIGHT AND CANCELED OUR IFR. ON CONTACTING THE TWR, HE ADVISED US THE FIELD WAS IFR (WE STILL HAD IT IN SIGHT). WE WERE SET UP FOR RWY 35 BUT HE COULD NOT CLR US IN THE LOC. I ASKED FOR AN SVFR, BUT FIRST MISSPOKE AND ASKED FOR A CONTACT APCH, THEN THE SPECIAL. WE GOT THE SPECIAL FROM THE TWR AND LANDED RWY 35. FLT VISIBILITY OF NEARLY 10 MI THE WHOLE TIME. TWR WANTED US TO CALL UP SO AFTER SHUTDOWN, I CALLED THE TWR CTLR. HE SAID HE WAS A VFR TWR AND COULD NOT GIVE CONTACT APCHS. I APOLOGIZED FOR THE MISCOM. (I DON'T THINK I WAS SUPPOSED TO KNOW THAT HE WAS A VFR ONLY TWR AND COULDN'T DO THAT.) REGARDLESS, IT WAS A MISCOM. TWR SAID HE HAD CALLED CTR PRIOR TO OUR CONTACTING HIM AND HE TOLD THE CTR THE FIELD WAS IFR AND EVERYONE HAD TO DO THE APCH. HE ALSO SAID HE ALMOST HAD A LACK OF SEPARATION WITH A DEPARTING REGIONAL JET IN THE OPPOSITE DIRECTION. WE WERE UNAWARE OF ANY DEPARTING TFC FROM CTR OR THE TWR. HE ALSO SAID ON THE PHONE THAT THERE WAS NO PROB, HE JUST WANTED TO TRY AND FIGURE OUT WHAT WENT WRONG SO WE COULD TRY AND KEEP IT FROM HAPPENING IN THE FUTURE. SUPPLEMENTAL INFO FROM ACN 607965: WE WERE PLANNING A VISUAL APCH, BUT MINNEAPOLIS ISSUED A VECTOR FOR THE BACK COURSE RWY 27 OTHER THAN RWY 35 WHICH WE WERE LINED UP FOR AND STILL HAD EASILY IN SIGHT. WE DISCOVERED LATER FROM TWR THAT CTR HAD RELEASED AN IFR TURBOPROP AROUND THIS SAME TIME.

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.