An A310 flight crew inadvertently crossed a red hold bar at eddf.

Attributes
ACN	595028
Time
Date	200309
Day	Fri
Local Time Of Day	0001 To 0600
Place
Locale Reference	airport : eddf.airport
State Reference	FO
Altitude	agl single value : 0
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	A310
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 : private pilot : atp
Experience	flight time last 90 days : 60 flight time total : 3500 flight time type : 230
ASRS Report	595028
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 150 flight time total : 19600 flight time type : 3000
ASRS Report	595676
Events
Anomaly	incursion : runway non adherence : clearance non adherence : far
Independent Detector	other controllera
Resolutory Action	controller : issued advisory
Consequence	faa : reviewed incident with flight crew
Supplementary
Problem Areas	Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance

Narrative:

The incident occurred early in the morning at eddf (frankfurt/main), germany. I was first officer loading, engine start was normal. We were given clearance to taxi out of apron on taxiway T, taxiway north, taxiway left, to taxiway a. While taxiing on taxiway a, captain called for before takeoff checklist, which I started to read and accomplish. I noticed he started to turn toward runway 18, which was incorrect, as we were expecting runway 7R -- at which time I told him we needed to go toward taxiway west, which would have been correct routing toward runway 7R. As we did that, the controller came over the radio and stated we had crossed a lit red stop bar! I personally never saw it, as I was reading the checklist 'heads down,' and the captain stated he saw it, but inexplicably taxied past the lights. After stopping we apologized to the controller and continued on the flight normally. I believe the factors that contributed were -- 1) perhaps being tired -- backside of clock flying. 2) unfamiliarity with the airport and taxi route. 3) communication -- controller cleared us to taxi, but never mentioned any 'surprises' as far as stopping short of runway. I believe he did say 'taxi to runway 7R,' but as far as I know, it wasn't clarified to us it was a limit to stop on taxiway a.

Original NASA ASRS Text

Title: AN A310 FLT CREW INADVERTENTLY CROSSED A RED HOLD BAR AT EDDF.

Narrative: THE INCIDENT OCCURRED EARLY IN THE MORNING AT EDDF (FRANKFURT/MAIN), GERMANY. I WAS FO LOADING, ENG START WAS NORMAL. WE WERE GIVEN CLRNC TO TAXI OUT OF APRON ON TXWY T, TXWY N, TXWY L, TO TXWY A. WHILE TAXIING ON TXWY A, CAPT CALLED FOR BEFORE TKOF CHKLIST, WHICH I STARTED TO READ AND ACCOMPLISH. I NOTICED HE STARTED TO TURN TOWARD RWY 18, WHICH WAS INCORRECT, AS WE WERE EXPECTING RWY 7R -- AT WHICH TIME I TOLD HIM WE NEEDED TO GO TOWARD TXWY W, WHICH WOULD HAVE BEEN CORRECT ROUTING TOWARD RWY 7R. AS WE DID THAT, THE CTLR CAME OVER THE RADIO AND STATED WE HAD CROSSED A LIT RED STOP BAR! I PERSONALLY NEVER SAW IT, AS I WAS READING THE CHKLIST 'HEADS DOWN,' AND THE CAPT STATED HE SAW IT, BUT INEXPLICABLY TAXIED PAST THE LIGHTS. AFTER STOPPING WE APOLOGIZED TO THE CTLR AND CONTINUED ON THE FLT NORMALLY. I BELIEVE THE FACTORS THAT CONTRIBUTED WERE -- 1) PERHAPS BEING TIRED -- BACKSIDE OF CLOCK FLYING. 2) UNFAMILIARITY WITH THE ARPT AND TAXI RTE. 3) COM -- CTLR CLRED US TO TAXI, BUT NEVER MENTIONED ANY 'SURPRISES' AS FAR AS STOPPING SHORT OF RWY. I BELIEVE HE DID SAY 'TAXI TO RWY 7R,' BUT AS FAR AS I KNOW, IT WASN'T CLARIFIED TO US IT WAS A LIMIT TO STOP ON TXWY A.

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.