Flight crew has runway incursion.

Attributes
ACN	548163
Time
Date	200205
Day	Thu
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : svmi.airport
State Reference	FO
Altitude	agl single value : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tower : svmi.tower
Operator	common carrier : air carrier
Make Model Name	A320
Operating Under FAR Part	Part 121
Flight Phase	ground : taxi ground : position and hold
Flight Plan	IFR
Aircraft 2
Controlling Facilities	tower : svmi.tower
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Flight Phase	landing : go around
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : atp
ASRS Report	548163
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Events
Anomaly	conflict : ground less severe incursion : runway non adherence : clearance
Independent Detector	other controllerb
Resolutory Action	none taken : detected after the fact
Consequence	faa : reviewed incident with flight crew
Supplementary
Problem Areas	ATC Human Performance Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

While taxiing for takeoff runway 9 at ccs, tower asked us if we were ready for immediate takeoff. We responded yes. Tower then cleared us into position and hold, be ready for immediate takeoff, which we acknowledged. I checked final and saw commuter aircraft traffic on final. Pointing it out to the captain, I said, 'you sure you want to do that?' or something to that effect. Captain said yes, and we both felt that given the range and speed of the traffic on final, there should be no conflict as long as there was no delay. At this point the tower sends the commuter traffic around. The tower taxies us down the runway to turn off and try again. The tower asks us why we took the runway. We told him what we both heard. He said 'no, you were cleared into position and hold after landing traffic.' the controller's english was very bad, but the captain and I were confident in what we heard. It took a lot of concentration to understand this controller. The quality of this controller's english was the most significant factor in this incident. Additionally, this controller spoke to other aircraft in the pattern in spanish, including the traffic on final, which reduced our overall situational awareness.

Original NASA ASRS Text

Title: FLC HAS RWY INCURSION.

Narrative: WHILE TAXIING FOR TKOF RWY 9 AT CCS, TWR ASKED US IF WE WERE READY FOR IMMEDIATE TKOF. WE RESPONDED YES. TWR THEN CLRED US INTO POS AND HOLD, BE READY FOR IMMEDIATE TKOF, WHICH WE ACKNOWLEDGED. I CHKED FINAL AND SAW COMMUTER ACFT TFC ON FINAL. POINTING IT OUT TO THE CAPT, I SAID, 'YOU SURE YOU WANT TO DO THAT?' OR SOMETHING TO THAT EFFECT. CAPT SAID YES, AND WE BOTH FELT THAT GIVEN THE RANGE AND SPD OF THE TFC ON FINAL, THERE SHOULD BE NO CONFLICT AS LONG AS THERE WAS NO DELAY. AT THIS POINT THE TWR SENDS THE COMMUTER TFC AROUND. THE TWR TAXIES US DOWN THE RWY TO TURN OFF AND TRY AGAIN. THE TWR ASKS US WHY WE TOOK THE RWY. WE TOLD HIM WHAT WE BOTH HEARD. HE SAID 'NO, YOU WERE CLRED INTO POS AND HOLD AFTER LNDG TFC.' THE CTLR'S ENGLISH WAS VERY BAD, BUT THE CAPT AND I WERE CONFIDENT IN WHAT WE HEARD. IT TOOK A LOT OF CONCENTRATION TO UNDERSTAND THIS CTLR. THE QUALITY OF THIS CTLR'S ENGLISH WAS THE MOST SIGNIFICANT FACTOR IN THIS INCIDENT. ADDITIONALLY, THIS CTLR SPOKE TO OTHER ACFT IN THE PATTERN IN SPANISH, INCLUDING THE TFC ON FINAL, WHICH REDUCED OUR OVERALL SITUATIONAL AWARENESS.

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.