EMB120 taxiing for departure at yum crossed runway without ATC clearance.

Attributes
ACN	581549
Time
Date	200305
Day	Tue
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : yum.airport
State Reference	AZ
Altitude	agl single value : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	Brasilia EMB-120 All Series
Operating Under FAR Part	Part 121
Flight Phase	ground : taxi
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : instrument pilot : commercial pilot : multi engine
Experience	flight time last 90 days : 150 flight time total : 3500 flight time type : 2500
ASRS Report	581549
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Events
Anomaly	incursion : runway non adherence : clearance non adherence : far
Independent Detector	other flight crewa
Resolutory Action	controller : issued new clearance flight crew : became reoriented
Consequence	faa : reviewed incident with flight crew
Supplementary
Problem Areas	Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

While taxiing for takeoff on runway 21L, we inadvertently taxied onto and across the active runway 21L. Possible causes of this occurrence are: 1) runway construction -- several runways and txwys were closed and poorly marked, leading to confusion. 2) unfamiliar runway -- due to runway closures, we were assigned an unfamiliar runway and were taxiing without progressive instructions. 3) division of attention -- this incursion occurred while I was completing my taxi checks and dividing my attention between my checks and my captain's taxi route. 4) CRM/confusion -- while doing my taxi checks, I saw we were approaching runway hold short lines, but was unsure which runway they idented. I asked my captain if he wanted me to confirm we were cleared to cross this runway. He said no, this was runway 21R, and we were cleared to cross it and all runways en route to runway 21L. We proceeded. It was then that we inadvertently crossed runway 21L. Tower then rerouted us back to runway 21L and cleared us for takeoff. Nothing further was mentioned regarding this issue.

Original NASA ASRS Text

Title: EMB120 TAXIING FOR DEP AT YUM CROSSED RWY WITHOUT ATC CLRNC.

Narrative: WHILE TAXIING FOR TKOF ON RWY 21L, WE INADVERTENTLY TAXIED ONTO AND ACROSS THE ACTIVE RWY 21L. POSSIBLE CAUSES OF THIS OCCURRENCE ARE: 1) RWY CONSTRUCTION -- SEVERAL RWYS AND TXWYS WERE CLOSED AND POORLY MARKED, LEADING TO CONFUSION. 2) UNFAMILIAR RWY -- DUE TO RWY CLOSURES, WE WERE ASSIGNED AN UNFAMILIAR RWY AND WERE TAXIING WITHOUT PROGRESSIVE INSTRUCTIONS. 3) DIVISION OF ATTN -- THIS INCURSION OCCURRED WHILE I WAS COMPLETING MY TAXI CHKS AND DIVIDING MY ATTN BTWN MY CHKS AND MY CAPT'S TAXI RTE. 4) CRM/CONFUSION -- WHILE DOING MY TAXI CHKS, I SAW WE WERE APCHING RWY HOLD SHORT LINES, BUT WAS UNSURE WHICH RWY THEY IDENTED. I ASKED MY CAPT IF HE WANTED ME TO CONFIRM WE WERE CLRED TO CROSS THIS RWY. HE SAID NO, THIS WAS RWY 21R, AND WE WERE CLRED TO CROSS IT AND ALL RWYS ENRTE TO RWY 21L. WE PROCEEDED. IT WAS THEN THAT WE INADVERTENTLY CROSSED RWY 21L. TWR THEN REROUTED US BACK TO RWY 21L AND CLRED US FOR TKOF. NOTHING FURTHER WAS MENTIONED REGARDING THIS ISSUE.

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.