Small aircraft taxies onto runway with instruction to taxi 'to.'

Attributes
ACN	233205
Time
Date	199302
Day	Sat
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : rdu
State Reference	NC
Altitude	agl bound lower : 0 agl bound upper : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	general aviation : personal
Make Model Name	Small Aircraft, High Wing, 1 Eng, Fixed Gear
Flight Phase	ground other : taxi
Flight Plan	None
Person 1
Affiliation	Other
Function	flight crew : single pilot
Qualification	pilot : private
Experience	flight time last 90 days : 100 flight time total : 300 flight time type : 300
ASRS Report	233205
Person 2
Affiliation	government : faa
Function	controller : ground
Qualification	controller : non radar
Events
Anomaly	incursion : runway non adherence : far non adherence : clearance
Independent Detector	other controllera
Resolutory Action	none taken : detected after the fact
Consequence	faa : reviewed incident with flight crew
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

I received my VFR clearance. I then contacted raleigh ground control and requested to 'taxi to the active with ATIS information -- entering at NR6 with runup completed.' ground control informed me to hold short of taxiway alpha. This was to allow an air carrier to enter the active runway -- 23L -- for departure. Ground control informed me 'caution jet blast!' as I held short of taxiway alpha. After the jet was airborne, ground control requested I 'taxi to 23L,' whereupon I taxied onto runway 23L. I was then informed that I had not been cleared to taxi onto the runway. (After I apologized, I was then told to contact the tower after arriving at my destination airport.) I was then cleared for takeoff. Cause: nr-6 being close to the runway 23L, I thought I was being cleared to taxi onto the runway even though I was still with ground control. Remedy: I believe that ground control should always include 'hold short of runway' in the instruction. This is particularly imperative at a busy airport like rdu. Another approach would be to have a sign 'hold short until tower clearance.' both remedies would not be too much.

Original NASA ASRS Text

Title: SMA TAXIES ONTO RWY WITH INSTRUCTION TO TAXI 'TO.'

Narrative: I RECEIVED MY VFR CLRNC. I THEN CONTACTED RALEIGH GND CTL AND REQUESTED TO 'TAXI TO THE ACTIVE WITH ATIS INFO -- ENTERING AT NR6 WITH RUNUP COMPLETED.' GND CTL INFORMED ME TO HOLD SHORT OF TXWY ALPHA. THIS WAS TO ALLOW AN ACR TO ENTER THE ACTIVE RWY -- 23L -- FOR DEP. GND CTL INFORMED ME 'CAUTION JET BLAST!' AS I HELD SHORT OF TXWY ALPHA. AFTER THE JET WAS AIRBORNE, GND CTL REQUESTED I 'TAXI TO 23L,' WHEREUPON I TAXIED ONTO RWY 23L. I WAS THEN INFORMED THAT I HAD NOT BEEN CLRED TO TAXI ONTO THE RWY. (AFTER I APOLOGIZED, I WAS THEN TOLD TO CONTACT THE TWR AFTER ARRIVING AT MY DEST ARPT.) I WAS THEN CLRED FOR TKOF. CAUSE: NR-6 BEING CLOSE TO THE RWY 23L, I THOUGHT I WAS BEING CLRED TO TAXI ONTO THE RWY EVEN THOUGH I WAS STILL WITH GND CTL. REMEDY: I BELIEVE THAT GND CTL SHOULD ALWAYS INCLUDE 'HOLD SHORT OF RWY' IN THE INSTRUCTION. THIS IS PARTICULARLY IMPERATIVE AT A BUSY ARPT LIKE RDU. ANOTHER APCH WOULD BE TO HAVE A SIGN 'HOLD SHORT UNTIL TWR CLRNC.' BOTH REMEDIES WOULD NOT BE TOO MUCH.

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.