Runway incursion by a B727 cargo flight crew at lbb, tx.

Attributes
ACN	545832
Time
Date	200204
Day	Sun
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : lbb.airport
State Reference	TX
Altitude	agl single value : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	B727 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	ground : taxi
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : flight engineer pilot : atp
Experience	flight time last 90 days : 30 flight time total : 8000 flight time type : 220
ASRS Report	545832
Person 2
Affiliation	company : air carrier
Function	flight crew : second officer
Qualification	pilot : atp pilot : flight engineer
Experience	flight time last 90 days : 250 flight time total : 4000 flight time type : 300
ASRS Report	545830
Events
Anomaly	incursion : runway non adherence : far non adherence : published procedure non adherence : clearance other anomaly other
Independent Detector	other controllera
Resolutory Action	controller : issued alert none taken : insufficient time
Consequence	faa : reviewed incident with flight crew
Supplementary
Problem Areas	Flight Crew Human Performance ATC Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

Lubbock ground, tower, and approach control were being worked by 1 controller on the morning of apr/sun/02. Local time was approximately early morning. Ground cleared me to 'taxi to runway 17R by taxiway south' from the cargo apron. I and my crew understood to taxi to runway 17R via taxiway south. Upon approaching runway 17R at taxiway south, ground informed us to hold short of runway 17R at taxiway south. By the time I had the aircraft stopped, I had passed the hold short bar on taxiway south prior to runway 17R. We did not enter runway 17R at any time. In this case the taxi instructions were legally correct but confusing. If the controller had included 'hold short of runway 17R at taxiway south' there would have been no confusion on our part. I would recommend changing ATC phraseology from 'taxi to X runway via X taxiway' with the implied understanding to hold short of X runway if it is the active. A more clear way to explain the intention is to clearly state hold short of X runway. Supplemental information from acn 545830: confused because we didn't consider runway 17R at taxiway south to be taxiing onto active yet.

Original NASA ASRS Text

Title: RWY INCURSION BY A B727 CARGO FLC AT LBB, TX.

Narrative: LUBBOCK GND, TWR, AND APCH CTL WERE BEING WORKED BY 1 CTLR ON THE MORNING OF APR/SUN/02. LCL TIME WAS APPROX EARLY MORNING. GND CLRED ME TO 'TAXI TO RWY 17R BY TXWY S' FROM THE CARGO APRON. I AND MY CREW UNDERSTOOD TO TAXI TO RWY 17R VIA TXWY S. UPON APCHING RWY 17R AT TXWY S, GND INFORMED US TO HOLD SHORT OF RWY 17R AT TXWY S. BY THE TIME I HAD THE ACFT STOPPED, I HAD PASSED THE HOLD SHORT BAR ON TXWY S PRIOR TO RWY 17R. WE DID NOT ENTER RWY 17R AT ANY TIME. IN THIS CASE THE TAXI INSTRUCTIONS WERE LEGALLY CORRECT BUT CONFUSING. IF THE CTLR HAD INCLUDED 'HOLD SHORT OF RWY 17R AT TXWY S' THERE WOULD HAVE BEEN NO CONFUSION ON OUR PART. I WOULD RECOMMEND CHANGING ATC PHRASEOLOGY FROM 'TAXI TO X RWY VIA X TXWY' WITH THE IMPLIED UNDERSTANDING TO HOLD SHORT OF X RWY IF IT IS THE ACTIVE. A MORE CLR WAY TO EXPLAIN THE INTENTION IS TO CLRLY STATE HOLD SHORT OF X RWY. SUPPLEMENTAL INFO FROM ACN 545830: CONFUSED BECAUSE WE DIDN'T CONSIDER RWY 17R AT TXWY S TO BE TAXIING ONTO ACTIVE YET.

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.