Narrative:

I contacted glenview naval on 126.2. Made contact and through several garbled xmissions was not aware that I should have been 126.3, which was gary air traffic area. Upon my recognition of the error, I passed directly over gyy, 1000' above the pattern. Frequencys are too close together--126.2 and 126.3. Also, glenview was not clear (45 mi away) and in fact cleared me through the air traffic area; i.e., reported 6 northeast, cleared through the air traffic area. It took several mins before I recognized and the controller at glenview recognized the error. Obviously I will be extra cautious in the future.

Google
 

Original NASA ASRS Text

Title: REPORTER STATES CLEARED BY NBU APCH CTLR THROUGH GYY ATA.

Narrative: I CONTACTED GLENVIEW NAVAL ON 126.2. MADE CONTACT AND THROUGH SEVERAL GARBLED XMISSIONS WAS NOT AWARE THAT I SHOULD HAVE BEEN 126.3, WHICH WAS GARY ATA. UPON MY RECOGNITION OF THE ERROR, I PASSED DIRECTLY OVER GYY, 1000' ABOVE THE PATTERN. FREQS ARE TOO CLOSE TOGETHER--126.2 AND 126.3. ALSO, GLENVIEW WAS NOT CLR (45 MI AWAY) AND IN FACT CLRED ME THROUGH THE ATA; I.E., RPTED 6 NE, CLRED THROUGH THE ATA. IT TOOK SEVERAL MINS BEFORE I RECOGNIZED AND THE CTLR AT GLENVIEW RECOGNIZED THE ERROR. OBVIOUSLY I WILL BE EXTRA CAUTIOUS IN THE FUTURE.

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.