A C140 pilot was intending to land at azo, but landed at btl, after being vectored there by grr.

Attributes
ACN	587466
Time
Date	200307
Day	Tue
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : btl.airport
State Reference	MI
Altitude	agl single value : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tower : btl.tower tower : cpr.tower
Operator	general aviation : personal
Make Model Name	Cessna 140
Operating Under FAR Part	Part 91
Navigation In Use	other
Flight Phase	landing : roll
Route In Use	arrival : on vectors
Flight Plan	None
Person 1
Affiliation	other
Function	flight crew : single pilot
Qualification	pilot : multi engine pilot : atp pilot : cfi
Experience	flight time last 90 days : 80 flight time total : 20000 flight time type : 500
ASRS Report	587466
Person 2
Affiliation	government : faa
Function	controller : approach
Events
Anomaly	incursion : landing without clearance non adherence : published procedure non adherence : clearance non adherence : far
Independent Detector	other flight crewa
Resolutory Action	none taken : detected after the fact
Consequence	faa : reviewed incident with flight crew
Supplementary
Problem Areas	Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

North of grand rapids, I contacted grr to transition through the area south to kalamazoo. I was handed off to new frequency south of grand rapids. This controller released me with 118.5 to contact tower. This was a new frequency, as I planned to use 118.3 for battle creek international at kalamazoo. Actually, I was talking to battle creek at kellogg, mi. I was cleared to land on runway 23 at battle creek, kellogg. But, I was planning on runway 23 at battle creek, kalamazoo. Last communication with tower at kellogg was based on where I was since they could not see me. I was about on a 1 mi right base to battle creek, kalamazoo. No check made for a light as I was 'cleared to land.' no conflict with any other air traffic. I did specify transition of grand rapids to kalamazoo. ATC somehow assumed I was going to battle creek, kellogg. I did wonder about frequency of 118.5, since I was planning on 118.3. I assumed 118.5 was a new frequency. I need to be specific about destination. If I had used battle creek or kalamazoo destination, this incident would not have occurred. If ATC had asked what my destination was, it would not have occurred.

Original NASA ASRS Text

Title: A C140 PLT WAS INTENDING TO LAND AT AZO, BUT LANDED AT BTL, AFTER BEING VECTORED THERE BY GRR.

Narrative: N OF GRAND RAPIDS, I CONTACTED GRR TO TRANSITION THROUGH THE AREA S TO KALAMAZOO. I WAS HANDED OFF TO NEW FREQ S OF GRAND RAPIDS. THIS CTLR RELEASED ME WITH 118.5 TO CONTACT TWR. THIS WAS A NEW FREQ, AS I PLANNED TO USE 118.3 FOR BATTLE CREEK INTL AT KALAMAZOO. ACTUALLY, I WAS TALKING TO BATTLE CREEK AT KELLOGG, MI. I WAS CLRED TO LAND ON RWY 23 AT BATTLE CREEK, KELLOGG. BUT, I WAS PLANNING ON RWY 23 AT BATTLE CREEK, KALAMAZOO. LAST COM WITH TWR AT KELLOGG WAS BASED ON WHERE I WAS SINCE THEY COULD NOT SEE ME. I WAS ABOUT ON A 1 MI R BASE TO BATTLE CREEK, KALAMAZOO. NO CHK MADE FOR A LIGHT AS I WAS 'CLRED TO LAND.' NO CONFLICT WITH ANY OTHER AIR TFC. I DID SPECIFY TRANSITION OF GRAND RAPIDS TO KALAMAZOO. ATC SOMEHOW ASSUMED I WAS GOING TO BATTLE CREEK, KELLOGG. I DID WONDER ABOUT FREQ OF 118.5, SINCE I WAS PLANNING ON 118.3. I ASSUMED 118.5 WAS A NEW FREQ. I NEED TO BE SPECIFIC ABOUT DEST. IF I HAD USED BATTLE CREEK OR KALAMAZOO DEST, THIS INCIDENT WOULD NOT HAVE OCCURRED. IF ATC HAD ASKED WHAT MY DEST WAS, IT WOULD NOT HAVE OCCURRED.

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.