Narrative:

We had just completed an NDB runway 27 approach into lnn and had been given a vector of 090 degrees and maintain 3000 ft to be vectored for the same approach again. We were approximately 3-4 mi north of lnn airport about 1/2 -- 1 mi off the shoreline of lake erie. Cleveland approach was providing the vectoring for us. While level at 3000 ft and on the assigned vector of 090 degrees I noticed an aircraft landing light at our 12 O'clock position at about our altitude. Cleveland did not advise us of any traffic. Both our taxi and landing lights as well as our strobe lights and beacon were illuminated the entire flight and we were on an IFR clearance. The traffic had now appeared to turn sbound and would not be a hazard to us. Therefore, I took my eyes off of him and monitored the procedures of my student. About 15 seconds later I looked again for this traffic and it was now at our 12 O'clock position and at our altitude and a collision was impending if evasive action were not taken. I pulled hard back on the control wheel to climb and told my student 'my airplane.' we passed slightly above the other aircraft which appeared to be some type of high wing cessna. I immediately notified cleveland approach that we were climbing due to a 'near miss' for opposite direction traffic at 3000 ft. The controller said he didn't have that traffic on radar and the only target he had was south of us at a lower altitude (we had this traffic in sight -- it was no factor). It is my belief that this opposite direction traffic had violated the class D airspace of lnn airport and had its transponder off for this reason which is why cleveland did not have him on radar.

Related reports:

Google
 

Original NASA ASRS Text

Title: RPTR EXPERIENCES NMAC.

Narrative: WE HAD JUST COMPLETED AN NDB RWY 27 APCH INTO LNN AND HAD BEEN GIVEN A VECTOR OF 090 DEGS AND MAINTAIN 3000 FT TO BE VECTORED FOR THE SAME APCH AGAIN. WE WERE APPROX 3-4 MI N OF LNN ARPT ABOUT 1/2 -- 1 MI OFF THE SHORELINE OF LAKE ERIE. CLEVELAND APCH WAS PROVIDING THE VECTORING FOR US. WHILE LEVEL AT 3000 FT AND ON THE ASSIGNED VECTOR OF 090 DEGS I NOTICED AN ACFT LNDG LIGHT AT OUR 12 O'CLOCK POS AT ABOUT OUR ALT. CLEVELAND DID NOT ADVISE US OF ANY TFC. BOTH OUR TAXI AND LNDG LIGHTS AS WELL AS OUR STROBE LIGHTS AND BEACON WERE ILLUMINATED THE ENTIRE FLT AND WE WERE ON AN IFR CLRNC. THE TFC HAD NOW APPEARED TO TURN SBOUND AND WOULD NOT BE A HAZARD TO US. THEREFORE, I TOOK MY EYES OFF OF HIM AND MONITORED THE PROCS OF MY STUDENT. ABOUT 15 SECONDS LATER I LOOKED AGAIN FOR THIS TFC AND IT WAS NOW AT OUR 12 O'CLOCK POS AND AT OUR ALT AND A COLLISION WAS IMPENDING IF EVASIVE ACTION WERE NOT TAKEN. I PULLED HARD BACK ON THE CTL WHEEL TO CLB AND TOLD MY STUDENT 'MY AIRPLANE.' WE PASSED SLIGHTLY ABOVE THE OTHER ACFT WHICH APPEARED TO BE SOME TYPE OF HIGH WING CESSNA. I IMMEDIATELY NOTIFIED CLEVELAND APCH THAT WE WERE CLBING DUE TO A 'NEAR MISS' FOR OPPOSITE DIRECTION TFC AT 3000 FT. THE CTLR SAID HE DIDN'T HAVE THAT TFC ON RADAR AND THE ONLY TARGET HE HAD WAS S OF US AT A LOWER ALT (WE HAD THIS TFC IN SIGHT -- IT WAS NO FACTOR). IT IS MY BELIEF THAT THIS OPPOSITE DIRECTION TFC HAD VIOLATED THE CLASS D AIRSPACE OF LNN ARPT AND HAD ITS XPONDER OFF FOR THIS REASON WHICH IS WHY CLEVELAND DID NOT HAVE HIM ON RADAR.

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.