Near midair collision.

Attributes
ACN	218823
Time
Date	199208
Day	Tue
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : bkl
State Reference	OH
Altitude	msl bound lower : 2500 msl bound upper : 2500
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : cle tower : bkl
Operator	general aviation : corporate
Make Model Name	Small Transport, Low Wing, 2 Recip Eng
Flight Phase	climbout : intermediate altitude cruise other
Route In Use	enroute : on vectors
Flight Plan	VFR
Aircraft 2
Operator	general aviation : corporate
Make Model Name	Light Transport, Low Wing, 2 Turbojet Eng
Navigation In Use	Other Other
Flight Phase	cruise other descent : approach
Route In Use	approach : straight in enroute : on vectors
Flight Plan	IFR
Person 1
Affiliation	Other
Function	flight crew : single pilot
Qualification	pilot : atp
Experience	flight time last 90 days : 210 flight time total : 4800 flight time type : 110
ASRS Report	218823
Person 2
Affiliation	Other
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Events
Anomaly	conflict : nmac non adherence : far other anomaly other
Independent Detector	other controllera other other : unspecified
Resolutory Action	none taken : detected after the fact
Consequence	faa : reviewed incident with flight crew
Miss Distance	horizontal : 0 vertical : 500
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

Following a normal departure from bkl 24R ATC clearance was a right turn overhead airport then to proceed on course sebound. Destination was 29G. Apparently, while my aircraft was overhead bkl at 2500 MSL, at light transport landing hopkins airport reported a near miss with me. He was reported as being at 3000 MSL. I had no visual contact and therefore was very shocked when cle radar supervisor contacted me upon arrival at 29G mins later. There was a question regarding contact with cle approach control. The reason is simple why I did not contact them. 1) I was below cle TCA, which in my location started at 3000 ft MSL. My transponder was on and in the mode C confign, however, they were not receiving altitude reporting at the time of occurrence. In future, more caution will be exercised with regards to communication in the cle metropolitan area. It is the light transport's word against mine, I have no recourse in this regard. It's simple. I didn't see him while I was complying with cleveland's burke lakefront tower instructions.

Original NASA ASRS Text

Title: NMAC.

Narrative: FOLLOWING A NORMAL DEP FROM BKL 24R ATC CLRNC WAS A R TURN OVERHEAD ARPT THEN TO PROCEED ON COURSE SEBOUND. DEST WAS 29G. APPARENTLY, WHILE MY ACFT WAS OVERHEAD BKL AT 2500 MSL, AT LTT LNDG HOPKINS ARPT RPTED A NEAR MISS WITH ME. HE WAS RPTED AS BEING AT 3000 MSL. I HAD NO VISUAL CONTACT AND THEREFORE WAS VERY SHOCKED WHEN CLE RADAR SUPVR CONTACTED ME UPON ARR AT 29G MINS LATER. THERE WAS A QUESTION REGARDING CONTACT WITH CLE APCH CTL. THE REASON IS SIMPLE WHY I DID NOT CONTACT THEM. 1) I WAS BELOW CLE TCA, WHICH IN MY LOCATION STARTED AT 3000 FT MSL. MY TRANSPONDER WAS ON AND IN THE MODE C CONFIGN, HOWEVER, THEY WERE NOT RECEIVING ALT RPTING AT THE TIME OF OCCURRENCE. IN FUTURE, MORE CAUTION WILL BE EXERCISED WITH REGARDS TO COM IN THE CLE METRO AREA. IT IS THE LTT'S WORD AGAINST MINE, I HAVE NO RECOURSE IN THIS REGARD. IT'S SIMPLE. I DIDN'T SEE HIM WHILE I WAS COMPLYING WITH CLEVELAND'S BURKE LAKEFRONT TWR INSTRUCTIONS.

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.