Narrative:

On sep/xa/98 at approximately XA15, I contacted bkl clearance delivery on 121.90 and informed the controller that I was a cessna skyhawk 172/U and requested a VFR departure on a heading of 240 degrees while climbing to 6500 ft MSL. Clearance delivery acknowledged my request and told me to squawk 1200. I then contacted ground control on 121.90 (same as clearance) and requested permission to taxi to the active runway for runup and takeoff. Ground control advised me to taxi to and hold short of runway 6L for my runup and to contact the tower on 124.30. After my runup I contacted the tower, told the controller my runup was complete and that I was ready for takeoff on runway 6L. The tower cleared me for takeoff and advised me to turn to a heading of 240 degrees and to be advised of helicopter traffic over the downtown area at 1300 ft. I acknowledged the turn to a heading of 240 degrees as well as the traffic over the downtown area. After I took off, I initiated my turn to a heading of 240 degrees, as I was climbing between 3000-4000 ft on heading 240 degrees. I noticed that I was within 5 NM of cle airport. Burke lakefront tower at no time advised me to contact ZOB and did not advise me of any frequency change. I remained on my heading of 240 degrees as well as burke lakefront's tower frequency until I was 20 NM north of cmh. At this time I contacted cmh approach and informed them that I was inbound for the full stop at tzr under VFR at 6500 ft. Cmh approach requested that I stay above 3000 ft and to squawk XXXX. After squawking XXXX and identing my transponder, cmh approach acknowledged radar contact and advised me to fly direct to bolton field. At approximately 8.5 NM from bolton, I contacted cmh control to inform them that I was starting my descent to pattern altitude for the full stop at bolton. Cmh control acknowledged my request and advised me to descend at my discretion and to contact bolton tower on 128.10. I contacted bolton tower, they cleared me for landing on runway 22, not able to make the landing due to being 1000 ft MSL above runway 22's threshold. Bolton tower cleared me for the go around and to land behind the pattern traffic. I finally landed at bolton and taxied to the parking area with bolton ground control's permission. My concern is that burke lakefront at no time advised me to contact a ZOB controller while entering or being within cle's class B airspace. After discussing this situation with another pilot, he informed that it might have been my responsibility to contact the ZOB controller. This was my first flight from the cle area. Accustomed to being handed off to a departure frequency from the tower frequency at cmh, I remained on burke lakefront's tower frequency until I was well clear of cle's class B airspace. Burke lakefront's clearance delivery or tower controller could have advised me to contact cle control after takeoff since they were well aware that my heading was going to cut into the class B airspace.

Related reports:

Google
 

Original NASA ASRS Text

Title: PLT IN C172 ADVISES BKL CLRNC DELIVERY THAT HE WANTED A 'VFR DEP' ON A HDG OF 240 DEGS. AFTER TKOF, THE TWR ADVISED THE PLT TO TURN TO HDG 240 DEGS. THE PLT REMAINED ON THE HDG AND WONDERED WHY THE CTLR DIDN'T ADVISE HIM TO CHANGE FREQ.

Narrative: ON SEP/XA/98 AT APPROX XA15, I CONTACTED BKL CLRNC DELIVERY ON 121.90 AND INFORMED THE CTLR THAT I WAS A CESSNA SKYHAWK 172/U AND REQUESTED A VFR DEP ON A HDG OF 240 DEGS WHILE CLBING TO 6500 FT MSL. CLRNC DELIVERY ACKNOWLEDGED MY REQUEST AND TOLD ME TO SQUAWK 1200. I THEN CONTACTED GND CTL ON 121.90 (SAME AS CLRNC) AND REQUESTED PERMISSION TO TAXI TO THE ACTIVE RWY FOR RUNUP AND TKOF. GND CTL ADVISED ME TO TAXI TO AND HOLD SHORT OF RWY 6L FOR MY RUNUP AND TO CONTACT THE TWR ON 124.30. AFTER MY RUNUP I CONTACTED THE TWR, TOLD THE CTLR MY RUNUP WAS COMPLETE AND THAT I WAS READY FOR TKOF ON RWY 6L. THE TWR CLRED ME FOR TKOF AND ADVISED ME TO TURN TO A HDG OF 240 DEGS AND TO BE ADVISED OF HELI TFC OVER THE DOWNTOWN AREA AT 1300 FT. I ACKNOWLEDGED THE TURN TO A HDG OF 240 DEGS AS WELL AS THE TFC OVER THE DOWNTOWN AREA. AFTER I TOOK OFF, I INITIATED MY TURN TO A HDG OF 240 DEGS, AS I WAS CLBING BTWN 3000-4000 FT ON HDG 240 DEGS. I NOTICED THAT I WAS WITHIN 5 NM OF CLE ARPT. BURKE LAKEFRONT TWR AT NO TIME ADVISED ME TO CONTACT ZOB AND DID NOT ADVISE ME OF ANY FREQ CHANGE. I REMAINED ON MY HDG OF 240 DEGS AS WELL AS BURKE LAKEFRONT'S TWR FREQ UNTIL I WAS 20 NM N OF CMH. AT THIS TIME I CONTACTED CMH APCH AND INFORMED THEM THAT I WAS INBOUND FOR THE FULL STOP AT TZR UNDER VFR AT 6500 FT. CMH APCH REQUESTED THAT I STAY ABOVE 3000 FT AND TO SQUAWK XXXX. AFTER SQUAWKING XXXX AND IDENTING MY XPONDER, CMH APCH ACKNOWLEDGED RADAR CONTACT AND ADVISED ME TO FLY DIRECT TO BOLTON FIELD. AT APPROX 8.5 NM FROM BOLTON, I CONTACTED CMH CTL TO INFORM THEM THAT I WAS STARTING MY DSCNT TO PATTERN ALT FOR THE FULL STOP AT BOLTON. CMH CTL ACKNOWLEDGED MY REQUEST AND ADVISED ME TO DSND AT MY DISCRETION AND TO CONTACT BOLTON TWR ON 128.10. I CONTACTED BOLTON TWR, THEY CLRED ME FOR LNDG ON RWY 22, NOT ABLE TO MAKE THE LNDG DUE TO BEING 1000 FT MSL ABOVE RWY 22'S THRESHOLD. BOLTON TWR CLRED ME FOR THE GAR AND TO LAND BEHIND THE PATTERN TFC. I FINALLY LANDED AT BOLTON AND TAXIED TO THE PARKING AREA WITH BOLTON GND CTL'S PERMISSION. MY CONCERN IS THAT BURKE LAKEFRONT AT NO TIME ADVISED ME TO CONTACT A ZOB CTLR WHILE ENTERING OR BEING WITHIN CLE'S CLASS B AIRSPACE. AFTER DISCUSSING THIS SIT WITH ANOTHER PLT, HE INFORMED THAT IT MIGHT HAVE BEEN MY RESPONSIBILITY TO CONTACT THE ZOB CTLR. THIS WAS MY FIRST FLT FROM THE CLE AREA. ACCUSTOMED TO BEING HANDED OFF TO A DEP FREQ FROM THE TWR FREQ AT CMH, I REMAINED ON BURKE LAKEFRONT'S TWR FREQ UNTIL I WAS WELL CLR OF CLE'S CLASS B AIRSPACE. BURKE LAKEFRONT'S CLRNC DELIVERY OR TWR CTLR COULD HAVE ADVISED ME TO CONTACT CLE CTL AFTER TKOF SINCE THEY WERE WELL AWARE THAT MY HDG WAS GOING TO CUT INTO THE CLASS B AIRSPACE.

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.