Small aircraft helicopter is cleared for takeoff westbound from hover position runway 5 and makes ru...

Narrative:

I and my student had flown over to allegheny county airport from pittsburgh metropolitan airport in order to shoot touch and go lndgs. It was to be an exercise for the student working in a busy control tower environment. After making initial contact with agc tower, they informed us that they would be unable to allow us to do touch and go lndgs. Traffic was very heavy at this time. My student and I accepted a landing on the numbers of runway 5. While hovering over the numbers, the tower asked us our intentions. We requested a takeoff for return to pittsburgh metropolitan airport. The controller cleared us for a wbound departure. This is where the soup begins to stick to the spoon. My student and I proceeded with our takeoff down runway 5, with the intention of getting airborne and then making a left turn wbound. But apparently this is not what the controller had in mind. His intention was to have us proceed directly due west from the numbers and stay south of the approach path for runway 10. When the controller saw us initiate our takeoff down runway 5, he ordered us to abort our takeoff because he thought there might be a traffic conflict with an aircraft on short final. When he saw there would be no conflict, he told us to disregard. He reminded us that northeast was not west. That evening I called the shift supervisor and we had a little talk. He seemed to think that I was at fault and I agreed with him. I told him that I definitely learned something from the incident. He also told me that the tower reviewed the phraseology used to clear me for takeoff. As far as extenuating circumstances are concerned, I think the fact that I am a high time fixed wing pilot (9000 hours) and a low time helicopter pilot (400 hours) worked against me. I am more or less conditioned to make a dash down the runway and getting airborne before turning on course. A classic case of negative transfer. While I was hovering on the numbers waiting for takeoff, the tower did not have me in view. Their view of this portion of runway 5 is blocked by bldgs. If the controller had included a restriction in my clearance, like 'remain south of runway 10', it would have definitely got my attention and this little day ruiner wouldn't have happened.

Original NASA ASRS Text

Title: SMA HELICOPTER IS CLEARED FOR TKOF WESTBOUND FROM HOVER POSITION RWY 5 AND MAKES RUN ON 5 BEFORE TURNING WEST THUS CONFLICTING WITH INTERSECTING RWY TRAFFIC PATTERN.

Narrative: I AND MY STUDENT HAD FLOWN OVER TO ALLEGHENY COUNTY ARPT FROM PITTSBURGH METRO ARPT IN ORDER TO SHOOT TOUCH AND GO LNDGS. IT WAS TO BE AN EXERCISE FOR THE STUDENT WORKING IN A BUSY CTL TWR ENVIRONMENT. AFTER MAKING INITIAL CONTACT WITH AGC TWR, THEY INFORMED US THAT THEY WOULD BE UNABLE TO ALLOW US TO DO TOUCH AND GO LNDGS. TFC WAS VERY HEAVY AT THIS TIME. MY STUDENT AND I ACCEPTED A LNDG ON THE NUMBERS OF RWY 5. WHILE HOVERING OVER THE NUMBERS, THE TWR ASKED US OUR INTENTIONS. WE REQUESTED A TKOF FOR RETURN TO PITTSBURGH METRO ARPT. THE CTLR CLRED US FOR A WBOUND DEP. THIS IS WHERE THE SOUP BEGINS TO STICK TO THE SPOON. MY STUDENT AND I PROCEEDED WITH OUR TKOF DOWN RWY 5, WITH THE INTENTION OF GETTING AIRBORNE AND THEN MAKING A LEFT TURN WBOUND. BUT APPARENTLY THIS IS NOT WHAT THE CTLR HAD IN MIND. HIS INTENTION WAS TO HAVE US PROCEED DIRECTLY DUE W FROM THE NUMBERS AND STAY S OF THE APCH PATH FOR RWY 10. WHEN THE CTLR SAW US INITIATE OUR TKOF DOWN RWY 5, HE ORDERED US TO ABORT OUR TKOF BECAUSE HE THOUGHT THERE MIGHT BE A TFC CONFLICT WITH AN ACFT ON SHORT FINAL. WHEN HE SAW THERE WOULD BE NO CONFLICT, HE TOLD US TO DISREGARD. HE REMINDED US THAT NE WAS NOT W. THAT EVENING I CALLED THE SHIFT SUPVR AND WE HAD A LITTLE TALK. HE SEEMED TO THINK THAT I WAS AT FAULT AND I AGREED WITH HIM. I TOLD HIM THAT I DEFINITELY LEARNED SOMETHING FROM THE INCIDENT. HE ALSO TOLD ME THAT THE TWR REVIEWED THE PHRASEOLOGY USED TO CLEAR ME FOR TKOF. AS FAR AS EXTENUATING CIRCUMSTANCES ARE CONCERNED, I THINK THE FACT THAT I AM A HIGH TIME FIXED WING PLT (9000 HRS) AND A LOW TIME HELI PLT (400 HRS) WORKED AGAINST ME. I AM MORE OR LESS CONDITIONED TO MAKE A DASH DOWN THE RWY AND GETTING AIRBORNE BEFORE TURNING ON COURSE. A CLASSIC CASE OF NEGATIVE TRANSFER. WHILE I WAS HOVERING ON THE NUMBERS WAITING FOR TKOF, THE TWR DID NOT HAVE ME IN VIEW. THEIR VIEW OF THIS PORTION OF RWY 5 IS BLOCKED BY BLDGS. IF THE CTLR HAD INCLUDED A RESTRICTION IN MY CLRNC, LIKE 'REMAIN S OF RWY 10', IT WOULD HAVE DEFINITELY GOT MY ATTN AND THIS LITTLE DAY RUINER WOULDN'T HAVE HAPPENED.

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.

Attributes
ACN	138876
Time
Date	199003
Day	Thu
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : agc
State Reference	PA
Altitude	msl bound lower : 1000 msl bound upper : 2000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tower : agc
Operator	general aviation : instructional
Make Model Name	Helicopter
Flight Phase	climbout : takeoff
Flight Plan	None
Person 1
Affiliation	Other
Function	instruction : instructor
Qualification	pilot : commercial pilot : cfi pilot : instrument pilot : flight engineer pilot : atp
Experience	flight time last 90 days : 200 flight time total : 9000 flight time type : 400
ASRS Report	138876
Person 2
Affiliation	Other
Function	instruction : trainee
Qualification	pilot : student
Events
Anomaly	non adherence : clearance other spatial deviation
Independent Detector	other controllera
Resolutory Action	controller : issued new clearance other
Consequence	Other
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Small aircraft helicopter is cleared for takeoff westbound from hover position runway 5 and makes run on 5 before turning west thus conflicting with intersecting runway traffic pattern.