Narrative:

I filed flight plan with kankakee FSS feb/wed/03 at about XA30 from madison, wi, from a cell phone, from ryv to I23. When finished, I asked for a standard briefing including NOTAMS. Briefer gave available information and said no NOTAMS at this time, call back tomorrow. When getting ready for flight, I ran a computer generated flight plan. It stated no NOTAMS for I23 on record. Flight was routine until dayton approach control stated I23 was closed due to snow on runway, so I elected to go to my alternate, iln, which dayton approach advised not to go to. (I didn't look this up in AFD information which I should have.) so I elected to go to I66 and got vectors from dayton to I66. They gave me position report which I said I had I66 in sight. Asked if dayton showed any traffic between my position and I66 and they said no, so I canceled IFR, reported downwind for runway 3 and set airplane up for approach and landing. After I reported on final as I got to the numbers, I realized I was about to land on runway 4L at iln instead of runway 3 at I66 so, I quickly looked up the tower frequency for iln, called tower and told them my situation and mistake. I think they only said ok and I flew runway heading until turning to the north and landed uneventfully at I66. At no time was the airplane I was flying or any other aircraft in the area in any danger nor were there any near misses (no other flying aircraft were observed by me). But, I almost landed at a control twred airport by accident. Once we landed at I66 and my passenger ride appeared, that person said he had been at our original destination airport (I23) and said the runway had been plowed and not just recently.

Related reports:

Google
 

Original NASA ASRS Text

Title: WRONG ARPT APCH AFTER AN UNAUTH UNCOORD PENETRATION OF CLASS D AIRSPACE BY A PA34 PLT ATTEMPTING A DIVERSION TO ALTERNATE ARPT I66, AT ILN, OH.

Narrative: I FILED FLT PLAN WITH KANKAKEE FSS FEB/WED/03 AT ABOUT XA30 FROM MADISON, WI, FROM A CELL PHONE, FROM RYV TO I23. WHEN FINISHED, I ASKED FOR A STANDARD BRIEFING INCLUDING NOTAMS. BRIEFER GAVE AVAILABLE INFO AND SAID NO NOTAMS AT THIS TIME, CALL BACK TOMORROW. WHEN GETTING READY FOR FLT, I RAN A COMPUTER GENERATED FLT PLAN. IT STATED NO NOTAMS FOR I23 ON RECORD. FLT WAS ROUTINE UNTIL DAYTON APCH CTL STATED I23 WAS CLOSED DUE TO SNOW ON RWY, SO I ELECTED TO GO TO MY ALTERNATE, ILN, WHICH DAYTON APCH ADVISED NOT TO GO TO. (I DIDN'T LOOK THIS UP IN AFD INFO WHICH I SHOULD HAVE.) SO I ELECTED TO GO TO I66 AND GOT VECTORS FROM DAYTON TO I66. THEY GAVE ME POS RPT WHICH I SAID I HAD I66 IN SIGHT. ASKED IF DAYTON SHOWED ANY TFC BTWN MY POS AND I66 AND THEY SAID NO, SO I CANCELED IFR, RPTED DOWNWIND FOR RWY 3 AND SET AIRPLANE UP FOR APCH AND LNDG. AFTER I RPTED ON FINAL AS I GOT TO THE NUMBERS, I REALIZED I WAS ABOUT TO LAND ON RWY 4L AT ILN INSTEAD OF RWY 3 AT I66 SO, I QUICKLY LOOKED UP THE TWR FREQ FOR ILN, CALLED TWR AND TOLD THEM MY SIT AND MISTAKE. I THINK THEY ONLY SAID OK AND I FLEW RWY HDG UNTIL TURNING TO THE N AND LANDED UNEVENTFULLY AT I66. AT NO TIME WAS THE AIRPLANE I WAS FLYING OR ANY OTHER ACFT IN THE AREA IN ANY DANGER NOR WERE THERE ANY NEAR MISSES (NO OTHER FLYING ACFT WERE OBSERVED BY ME). BUT, I ALMOST LANDED AT A CTL TWRED ARPT BY ACCIDENT. ONCE WE LANDED AT I66 AND MY PAX RIDE APPEARED, THAT PERSON SAID HE HAD BEEN AT OUR ORIGINAL DEST ARPT (I23) AND SAID THE RWY HAD BEEN PLOWED AND NOT JUST RECENTLY.

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.