Narrative:

We taxied out of dtw to runway 22L. Runway 21L was closed for construction. Flts were arriving on runways 22R and 22L. Runway 22L is normally a departure only runway. ATC was talking on 2 frequencys, controling both runways. No aircraft were ahead of us and we anticipated no delay. I was tired after being on duty for 5 days, a short overnight the previous night, a 2 1/2 hour wait in dtw and a large lunch. ATC issued instructions which I thought had been position and hold on runway 22L for our flight. The first officer was heads down double-checking departure frequencys and was anticipating me holding short. When I was crossing the centerline, he realized we were on the runway. He told me we weren't cleared into position. As I asked him to check with tower, I noticed an aircraft on about a 2 mi final. Tower instructed us to clear the runway and we continued across runway 22L exiting on taxiway Z. Contributing factors include captain being tired, (sinking spell after lunch) unusual runway confign, tower controller talking on 2 frequencys, also unusual for dtw. Captain did not use his normal verification of announcing intention before entering runway, anticipating no delay for departure. Supplemental information for acn 621073: we switched to tower frequency and I went 'heads down' momentarily to check the departure procedure. When I looked up, the aircraft had already crossed the runway 22L hold short line. Contributing factors: 'non standard' landing runway confign (runway 22L usually used for departures only), tower controller working multiple frequencys, first officer (me) was heads down at critical phase of taxiing, and captain was working his 5TH consecutive day (fatigue?)

Related reports:

Google
 

Original NASA ASRS Text

Title: MLG CREW HAD A RWY INCURSION ON TAXI OUT AT DTW.

Narrative: WE TAXIED OUT OF DTW TO RWY 22L. RWY 21L WAS CLOSED FOR CONSTRUCTION. FLTS WERE ARRIVING ON RWYS 22R AND 22L. RWY 22L IS NORMALLY A DEP ONLY RWY. ATC WAS TALKING ON 2 FREQS, CTLING BOTH RWYS. NO ACFT WERE AHEAD OF US AND WE ANTICIPATED NO DELAY. I WAS TIRED AFTER BEING ON DUTY FOR 5 DAYS, A SHORT OVERNIGHT THE PREVIOUS NIGHT, A 2 1/2 HR WAIT IN DTW AND A LARGE LUNCH. ATC ISSUED INSTRUCTIONS WHICH I THOUGHT HAD BEEN POS AND HOLD ON RWY 22L FOR OUR FLT. THE FO WAS HEADS DOWN DOUBLE-CHKING DEP FREQS AND WAS ANTICIPATING ME HOLDING SHORT. WHEN I WAS XING THE CTRLINE, HE REALIZED WE WERE ON THE RWY. HE TOLD ME WE WEREN'T CLRED INTO POS. AS I ASKED HIM TO CHK WITH TWR, I NOTICED AN ACFT ON ABOUT A 2 MI FINAL. TWR INSTRUCTED US TO CLR THE RWY AND WE CONTINUED ACROSS RWY 22L EXITING ON TXWY Z. CONTRIBUTING FACTORS INCLUDE CAPT BEING TIRED, (SINKING SPELL AFTER LUNCH) UNUSUAL RWY CONFIGN, TWR CTLR TALKING ON 2 FREQS, ALSO UNUSUAL FOR DTW. CAPT DID NOT USE HIS NORMAL VERIFICATION OF ANNOUNCING INTENTION BEFORE ENTERING RWY, ANTICIPATING NO DELAY FOR DEP. SUPPLEMENTAL INFO FOR ACN 621073: WE SWITCHED TO TWR FREQ AND I WENT 'HEADS DOWN' MOMENTARILY TO CHK THE DEP PROC. WHEN I LOOKED UP, THE ACFT HAD ALREADY CROSSED THE RWY 22L HOLD SHORT LINE. CONTRIBUTING FACTORS: 'NON STANDARD' LNDG RWY CONFIGN (RWY 22L USUALLY USED FOR DEPS ONLY), TWR CTLR WORKING MULTIPLE FREQS, FO (ME) WAS HEADS DOWN AT CRITICAL PHASE OF TAXIING, AND CAPT WAS WORKING HIS 5TH CONSECUTIVE DAY (FATIGUE?)

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.