BE36 pilot deviated track without clearance.

Attributes
ACN	455530
Time
Date	199911
Day	Sat
Local Time Of Day	0601 To 1200
Place
State Reference	PA
Altitude	msl single value : 4000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : mdt.tracon
Operator	general aviation : personal
Make Model Name	Bonanza 36
Operating Under FAR Part	Part 91
Flight Phase	climbout : intermediate altitude
Route In Use	enroute airway : v93.airway
Flight Plan	IFR
Person 1
Affiliation	other
Function	flight crew : single pilot oversight : pic
Qualification	pilot : instrument pilot : private
Experience	flight time last 90 days : 30 flight time total : 965 flight time type : 700
ASRS Report	455530
Person 2
Affiliation	government : faa
Function	controller : radar controller : departure
Qualification	controller : radar
Events
Anomaly	non adherence : far non adherence : published procedure non adherence : clearance other spatial deviation
Independent Detector	other controllera
Consequence	faa : assigned or threatened penalties
Supplementary
Problem Areas	Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

The problem arose when I was xferred from lancaster tower to harrisburg departure. The controller asked me why I was not on runway heading. He said something about pilot deviation. I believe the start of the problem was on the ground. I had a long wait to take off behind 6 other aircraft, in excess of 30 mins. We all waited and it did not seem that busy. Then we all took off in a fairly short time, mixed with other traffic landing. On departure it was a long time before I was changed to departure, and that happened after I asked the tower to change me over, because I thought it more than enough time and I needed to be on departure. My clearance was lns V93. After departing runway heading to 1000 ft above the airport, I turned on a course to join V93 to lvz. I don't believe I was given 'fly runway heading for vectors' in my clearance. If I was or I should have known to do that then I was in error and should have been more careful and questioned the clearance. Another thing I did wrong was not having the correct squawk code. I asked my passenger to install it and I didn't check it. This also could have been a factor. I learned a few things from this. The first is, when things aren't going smooth, be more careful. Second, be absolutely sure of your clearance. Third, check and doublechk all radio and navigation inputs.

Original NASA ASRS Text

Title: BE36 PLT DEVIATED TRACK WITHOUT CLRNC.

Narrative: THE PROB AROSE WHEN I WAS XFERRED FROM LANCASTER TWR TO HARRISBURG DEP. THE CTLR ASKED ME WHY I WAS NOT ON RWY HDG. HE SAID SOMETHING ABOUT PLTDEV. I BELIEVE THE START OF THE PROB WAS ON THE GND. I HAD A LONG WAIT TO TAKE OFF BEHIND 6 OTHER ACFT, IN EXCESS OF 30 MINS. WE ALL WAITED AND IT DID NOT SEEM THAT BUSY. THEN WE ALL TOOK OFF IN A FAIRLY SHORT TIME, MIXED WITH OTHER TFC LNDG. ON DEP IT WAS A LONG TIME BEFORE I WAS CHANGED TO DEP, AND THAT HAPPENED AFTER I ASKED THE TWR TO CHANGE ME OVER, BECAUSE I THOUGHT IT MORE THAN ENOUGH TIME AND I NEEDED TO BE ON DEP. MY CLRNC WAS LNS V93. AFTER DEPARTING RWY HDG TO 1000 FT ABOVE THE ARPT, I TURNED ON A COURSE TO JOIN V93 TO LVZ. I DON'T BELIEVE I WAS GIVEN 'FLY RWY HDG FOR VECTORS' IN MY CLRNC. IF I WAS OR I SHOULD HAVE KNOWN TO DO THAT THEN I WAS IN ERROR AND SHOULD HAVE BEEN MORE CAREFUL AND QUESTIONED THE CLRNC. ANOTHER THING I DID WRONG WAS NOT HAVING THE CORRECT SQUAWK CODE. I ASKED MY PAX TO INSTALL IT AND I DIDN'T CHK IT. THIS ALSO COULD HAVE BEEN A FACTOR. I LEARNED A FEW THINGS FROM THIS. THE FIRST IS, WHEN THINGS AREN'T GOING SMOOTH, BE MORE CAREFUL. SECOND, BE ABSOLUTELY SURE OF YOUR CLRNC. THIRD, CHK AND DOUBLECHK ALL RADIO AND NAV INPUTS.

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.