F100 crew had runway incursion at runway 31 at bna.

Attributes
ACN	495378
Time
Date	200012
Day	Tue
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : bna.airport
State Reference	TN
Altitude	agl single value : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tower : bna.tower tower : iad.tower
Operator	common carrier : air carrier
Make Model Name	Fokker 100
Operating Under FAR Part	Part 121
Navigation In Use	other
Flight Phase	ground : taxi
Flight Plan	IFR
Aircraft 2
Controlling Facilities	tower : bna.tower
Operator	common carrier : air carrier
Make Model Name	Light Transport
Operating Under FAR Part	Part 125
Flight Phase	descent : approach
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 150 flight time total : 11000 flight time type : 800
ASRS Report	495378
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : multi engine pilot : instrument pilot : flight engineer pilot : commercial
Experience	flight time last 90 days : 200 flight time total : 9000 flight time type : 4400
ASRS Report	495377
Events
Anomaly	incursion : runway non adherence : clearance other anomaly other
Independent Detector	other controllera other flight crewa other flight crewb
Resolutory Action	controller : issued alert controller : issued new clearance flight crew : executed go around none taken : detected after the fact
Consequence	faa : reviewed incident with flight crew
Supplementary
Problem Areas	Flight Crew Human Performance ATC Human Performance Airport
Primary Problem	ATC Human Performance
Situations
Airport	markings : bna.airport signage : bna.airport

Narrative:

We were told to taxi to runway 31. We read back, taxi to runway 31, I taxied past runway 31 approach hold lines because we did not hear, did not read back, and ATC did not confirm we were to hold at the approach runway 31 hold line. I was going to hold short of 31 at the red runway 31/13 hold short sign. ATC cleared us for takeoff. They then turned a commuter off of the approach to runway 31 for another runway. I called the bna tower and the supervisor said that they had listened to the tape. He said that it was their fault because the controller failed to verify the hold point. He also stated that they have had numerous problems there and that they would like a red approach runway 31 hold sign to replace the amber sign, but, is unaware of the status of their request.

Original NASA ASRS Text

Title: F100 CREW HAD RWY INCURSION AT RWY 31 AT BNA.

Narrative: WE WERE TOLD TO TAXI TO RWY 31. WE READ BACK, TAXI TO RWY 31, I TAXIED PAST RWY 31 APCH HOLD LINES BECAUSE WE DID NOT HEAR, DID NOT READ BACK, AND ATC DID NOT CONFIRM WE WERE TO HOLD AT THE APCH RWY 31 HOLD LINE. I WAS GOING TO HOLD SHORT OF 31 AT THE RED RWY 31/13 HOLD SHORT SIGN. ATC CLRED US FOR TKOF. THEY THEN TURNED A COMMUTER OFF OF THE APCH TO RWY 31 FOR ANOTHER RWY. I CALLED THE BNA TWR AND THE SUPERVISOR SAID THAT THEY HAD LISTENED TO THE TAPE. HE SAID THAT IT WAS THEIR FAULT BECAUSE THE CTLR FAILED TO VERIFY THE HOLD POINT. HE ALSO STATED THAT THEY HAVE HAD NUMEROUS PROBS THERE AND THAT THEY WOULD LIKE A RED APCH RWY 31 HOLD SIGN TO REPLACE THE AMBER SIGN, BUT, IS UNAWARE OF THE STATUS OF THEIR REQUEST.

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.