Atx X entered orl control zone without communication.

Attributes
ACN	269984
Time
Date	199404
Day	Fri
Local Time Of Day	1801 To 2400
Place
Locale Reference	atc facility : orl
State Reference	FL
Altitude	msl bound lower : 1100 msl bound upper : 1100
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : mco tower : orl
Operator	common carrier : air taxi
Make Model Name	Commercial Fixed Wing
Operating Under FAR Part	Part 135
Flight Phase	descent : approach
Route In Use	enroute : on vectors
Flight Plan	VFR
Person 1
Affiliation	company : air taxi
Function	flight crew : single pilot
Qualification	pilot : commercial pilot : instrument
Experience	flight time last 90 days : 400 flight time total : 1500 flight time type : 600
ASRS Report	269984
Person 2
Affiliation	government : faa
Function	controller : approach
Qualification	controller : radar
Events
Anomaly	non adherence : published procedure other anomaly other
Independent Detector	other controllera
Resolutory Action	none taken : anomaly accepted
Consequence	faa : reviewed incident with flight crew
Supplementary
Primary Problem	ATC Human Performance
Air Traffic Incident	Inter Facility Coordination Failure other

Narrative:

Small aircraft X 35 DME southeast orl VOR, called orl approach on 119.4 for clearance into class B for landing at executive. Received squawk of XXXX and clearance into class B. Proceeded to the 'power plant' (roughly 10 east of orl) and was instructed to depart the power plant on a heading of 330 degrees and maintain that heading until north of the centerline runway 7/25 at orl. I responded to the instructions with the additional remark that my current heading was '335 degrees' (winds were strong out of the east). I flew heading 330 degrees until north of runway then turned west. Prior to the turn wbound I was well inside the orl air traffic area. After the turn I was practically downwind for runway 7. Being so close to the airport, I quizzed the approach controller for a handoff and he issued the statement to contact the tower. All this time I maintained the squawk and was following his radar directives. Once tower was contacted I was questioned as to my lateness in establishing an initial contact. On taxi in, I was asked to call the tower regarding the incident. It is not safe to assume that orlando approach and orl executive tower have a coordination, landline to effect the handoff? When ATC says fly a heading for vectors to an airport, that's what I'm going to do.

Original NASA ASRS Text

Title: ATX X ENTERED ORL CTL ZONE WITHOUT COM.

Narrative: SMA X 35 DME SE ORL VOR, CALLED ORL APCH ON 119.4 FOR CLRNC INTO CLASS B FOR LNDG AT EXECUTIVE. RECEIVED SQUAWK OF XXXX AND CLRNC INTO CLASS B. PROCEEDED TO THE 'PWR PLANT' (ROUGHLY 10 E OF ORL) AND WAS INSTRUCTED TO DEPART THE PWR PLANT ON A HDG OF 330 DEGS AND MAINTAIN THAT HDG UNTIL N OF THE CTRLINE RWY 7/25 AT ORL. I RESPONDED TO THE INSTRUCTIONS WITH THE ADDITIONAL REMARK THAT MY CURRENT HDG WAS '335 DEGS' (WINDS WERE STRONG OUT OF THE E). I FLEW HDG 330 DEGS UNTIL N OF RWY THEN TURNED W. PRIOR TO THE TURN WBOUND I WAS WELL INSIDE THE ORL ATA. AFTER THE TURN I WAS PRACTICALLY DOWNWIND FOR RWY 7. BEING SO CLOSE TO THE ARPT, I QUIZZED THE APCH CTLR FOR A HDOF AND HE ISSUED THE STATEMENT TO CONTACT THE TWR. ALL THIS TIME I MAINTAINED THE SQUAWK AND WAS FOLLOWING HIS RADAR DIRECTIVES. ONCE TWR WAS CONTACTED I WAS QUESTIONED AS TO MY LATENESS IN ESTABLISHING AN INITIAL CONTACT. ON TAXI IN, I WAS ASKED TO CALL THE TWR REGARDING THE INCIDENT. IT IS NOT SAFE TO ASSUME THAT ORLANDO APCH AND ORL EXECUTIVE TWR HAVE A COORD, LANDLINE TO EFFECT THE HDOF? WHEN ATC SAYS FLY A HDG FOR VECTORS TO AN ARPT, THAT'S WHAT I'M GOING TO DO.

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.