Small transport taxies onto runway with traffic on final.

Attributes
ACN	271166
Time
Date	199405
Day	Thu
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : det
State Reference	MI
Altitude	agl bound lower : 0 agl bound upper : 0
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Operator	general aviation : instructional
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Operating Under FAR Part	Part 91
Flight Phase	ground other : taxi
Flight Plan	VFR
Aircraft 2
Make Model Name	PA-28 Cherokee/Archer II/Dakota/Pillan/Warrior
Operating Under FAR Part	Part 91
Flight Phase	descent : approach landing other
Person 1
Affiliation	Other
Function	flight crew : single pilot
Qualification	pilot : instrument pilot : cfi pilot : atp pilot : commercial
Experience	flight time last 90 days : 250 flight time total : 5500 flight time type : 2500
ASRS Report	271166
Person 2
Affiliation	government : faa
Function	controller : ground
Qualification	controller : non radar
Events
Anomaly	incursion : runway non adherence : clearance other anomaly other
Independent Detector	other controllera
Resolutory Action	other
Consequence	Other
Supplementary
Primary Problem	Ambiguous
Air Traffic Incident	Pilot Deviation

Narrative:

While taxiing out of the ramp, tower said 'taxi onto runway 7 and onto runway 33.' there was traffic that was blocking taxiway 'J,' the normal route to 33. I read back his clearance, proceeded onto 7, then 33 and called ready for takeoff. Tower said do a 180 degree turn and exit the runway. A PA-28 was on a 2 mi final for 15. I exited the runway and the PA-28 landed without incident. I then departed. What I read back was not what the controller meant, also there aren't any good hold short lines on intersecting runways. Callback conversation with reporter revealed the following information: reporter states he read back the exact wording he received. Since he was taxiing on runway 7 there would be no hold line for the 33 runway and he taxied onto 33 as instructed. Reporter indicates that the airport gets very busy with freight operations at times and the controllers do 'weird things' to keep traffic moving. He feels he got caught in this situation. No FAA follow-up at this point. Reporter had a hard time remembering details as this was several months ago.

Original NASA ASRS Text

Title: SMT TAXIES ONTO RWY WITH TFC ON FINAL.

Narrative: WHILE TAXIING OUT OF THE RAMP, TWR SAID 'TAXI ONTO RWY 7 AND ONTO RWY 33.' THERE WAS TFC THAT WAS BLOCKING TXWY 'J,' THE NORMAL RTE TO 33. I READ BACK HIS CLRNC, PROCEEDED ONTO 7, THEN 33 AND CALLED READY FOR TKOF. TWR SAID DO A 180 DEG TURN AND EXIT THE RWY. A PA-28 WAS ON A 2 MI FINAL FOR 15. I EXITED THE RWY AND THE PA-28 LANDED WITHOUT INCIDENT. I THEN DEPARTED. WHAT I READ BACK WAS NOT WHAT THE CTLR MEANT, ALSO THERE AREN'T ANY GOOD HOLD SHORT LINES ON INTERSECTING RWYS. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: RPTR STATES HE READ BACK THE EXACT WORDING HE RECEIVED. SINCE HE WAS TAXIING ON RWY 7 THERE WOULD BE NO HOLD LINE FOR THE 33 RWY AND HE TAXIED ONTO 33 AS INSTRUCTED. RPTR INDICATES THAT THE ARPT GETS VERY BUSY WITH FREIGHT OPS AT TIMES AND THE CTLRS DO 'WEIRD THINGS' TO KEEP TFC MOVING. HE FEELS HE GOT CAUGHT IN THIS SIT. NO FAA FOLLOW-UP AT THIS POINT. RPTR HAD A HARD TIME REMEMBERING DETAILS AS THIS WAS SEVERAL MONTHS AGO.

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.