Narrative:

Flight was inbound to iln and received information delta: O7Z 1000 2500 10Z-/66/60/0304/runway 22. At 15 mxq DME received clearance for visibility approach and proceeded straight in runway 22. At 10 mxq DME cancelled IFR with dayton TRACON reported airbo inbound landing on unicom 122.8 and received wind advisory. After landing dayton TRACON requested that the crew make a phone call to speak to controller. Controller was called by phone. He said the active runway and landing was 4, not 22. Further, he said he had advised on initial contact runway 4 was active and the visibility approach clearance specified runway 4. I replied the flight crew neither understood or acknowledged by readback that runway 4 was intended for landing. He stated that our landing on runway 22 had caused some problems for his traffic management.

Google
 

Original NASA ASRS Text

Title: MDT LNDG AT UNCONTROLLED ARPT WHILE UNDER CONTROL OF TRACON LANDS ON RWY NOT INTENDED BY CTLR.

Narrative: FLT WAS INBND TO ILN AND RECEIVED INFO DELTA: O7Z 1000 2500 10Z-/66/60/0304/RWY 22. AT 15 MXQ DME RECEIVED CLRNC FOR VIS APCH AND PROCEEDED STRAIGHT IN RWY 22. AT 10 MXQ DME CANCELLED IFR WITH DAYTON TRACON RPTED AIRBO INBND LNDG ON UNICOM 122.8 AND RECEIVED WIND ADVISORY. AFTER LNDG DAYTON TRACON REQUESTED THAT THE CREW MAKE A PHONE CALL TO SPEAK TO CTLR. CTLR WAS CALLED BY PHONE. HE SAID THE ACTIVE RWY AND LNDG WAS 4, NOT 22. FURTHER, HE SAID HE HAD ADVISED ON INITIAL CONTACT RWY 4 WAS ACTIVE AND THE VIS APCH CLRNC SPECIFIED RWY 4. I REPLIED THE FLT CREW NEITHER UNDERSTOOD OR ACKNOWLEDGED BY READBACK THAT RWY 4 WAS INTENDED FOR LNDG. HE STATED THAT OUR LNDG ON RWY 22 HAD CAUSED SOME PROBS FOR HIS TFC MGMNT.

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