Narrative:

Enroute under VFR-flight-following to orl at 2;500 MSL direct. [I was] vectored through orlando class B airspace with class B clearance. Approximately 10 miles out from orl; orlando approach requested that I descend to 1;600 feet MSL and report the airport in sight. I reported orl in sight and descended to 1;600 feet MSL. About 3 NM north of orl the orlando approach controller was communicating with another aircraft about what missed approach to fly after a particular approach was flown. This filled the radio with congestion and I couldn't query ATC on providing me a switchover to orl tower. When I had the chance which was when I was now 1 NM from the downwind of the runway in use at orl; I reported again 'I have orl executive in sight.' orlando approach told me to turn right to enter the downwind; to 'descend now;' and then to contact orlando tower. I complied with everything ATC requested of me. When I contacted executive tower; the controller asked why I entered his airspace without talking to him. I informed him that orlando approach told me to enter the downwind and then contact him. Orlando tower told me I couldn't enter class D airspace. I also told the tower controller that I was told to descend. No more questions or statements came from orlando tower to me but I wanted to report this because I feel it was improper ATC procedure of orlando approach to clear me down into the class D airspace below the class B without communicating first with their ATC counterpart at orlando tower. I am under the impression that my communication with orlando approach fulfills my communication requirement for class D in regulation 91.129.

Google
 

Original NASA ASRS Text

Title: A pilot entered ORL Class D Airspace at MCO TRACON's direction and was confronted by a combative ORL Tower Controller for entering the airspace without his clearance even though MCO cleared him in.

Narrative: Enroute under VFR-flight-following to ORL at 2;500 MSL Direct. [I was] vectored through Orlando Class B airspace with Class B clearance. Approximately 10 miles out from ORL; Orlando approach requested that I descend to 1;600 feet MSL and report the airport in sight. I reported ORL in sight and descended to 1;600 feet MSL. About 3 NM North of ORL the Orlando Approach Controller was communicating with another aircraft about what missed approach to fly after a particular approach was flown. This filled the radio with congestion and I couldn't query ATC on providing me a switchover to ORL Tower. When I had the chance which was when I was now 1 NM from the downwind of the runway in use at ORL; I reported again 'I have ORL Executive in sight.' Orlando Approach told me to turn right to enter the downwind; to 'Descend Now;' and then to contact Orlando Tower. I complied with everything ATC requested of me. When I contacted Executive Tower; the Controller asked why I entered his airspace without talking to him. I informed him that Orlando Approach told me to enter the downwind and then contact him. Orlando Tower told me I couldn't enter Class D airspace. I also told the Tower Controller that I was told to descend. No more questions or statements came from Orlando Tower to me but I wanted to report this because I feel it was improper ATC procedure of Orlando Approach to clear me down into the Class D airspace below the Class B without communicating first with their ATC counterpart at Orlando Tower. I am under the impression that my communication with Orlando Approach fulfills my communication requirement for Class D in regulation 91.129.

Data retrieved from NASA's ASRS site as of July 2013 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.