Flight crew of SBR1 cross runway 32R at ord without clearance.

Attributes
ACN	616923
Time
Date	200405
Day	Tue
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : ord.airport
State Reference	IL
Altitude	agl single value : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	general aviation : corporate
Make Model Name	Sabreliner 65
Operating Under FAR Part	Part 121
Flight Phase	ground : taxi
Flight Plan	IFR
Person 1
Affiliation	company : corporate
Function	flight crew : first officer
Qualification	pilot : atp
Experience	flight time last 90 days : 64 flight time total : 5180 flight time type : 1110
ASRS Report	616923
Person 2
Affiliation	company : corporate
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Events
Anomaly	incursion : runway non adherence : published procedure non adherence : far non adherence : company policies non adherence : clearance
Independent Detector	other flight crewa
Resolutory Action	none taken : detected after the fact
Supplementary
Problem Areas	ATC Human Performance Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

We were taxiing from runway 27L at ord to FBO via taxiway B. We had been instructed to hold short of runway 32R. Our standard procedure is for the PF to repeat any and all hold short instructions. If the PNF does not hear the PF repeat the instructions, PNF repeats it and waits for the PF to repeat. I do not recall hearing the PF repeat the hold short and did not prompt him for it. We were still some distance from runway 32R, so I advised PF that I was going head down to program the departure (something that wasn't necessary at the time). When I looked up, we were already past the runway 32R hold short line. I do not believe that we caused a conflict. Runway 27R was in use for lndgs and I do not believe that runway 32R was in use. I believe that we were asked to hold short of runway 32R because of the limited space between the runways 32R and 27R thresholds. In the future, besides making sure that we follow the repetition/confirmation procedure, I will reconsider the need to ever go head down when we have hold short instructions. If necessary to go head down, it would be wise to reconfirm any hold short instructions at that time.

Original NASA ASRS Text

Title: FLT CREW OF SBR1 CROSS RWY 32R AT ORD WITHOUT CLRNC.

Narrative: WE WERE TAXIING FROM RWY 27L AT ORD TO FBO VIA TXWY B. WE HAD BEEN INSTRUCTED TO HOLD SHORT OF RWY 32R. OUR STANDARD PROC IS FOR THE PF TO REPEAT ANY AND ALL HOLD SHORT INSTRUCTIONS. IF THE PNF DOES NOT HEAR THE PF REPEAT THE INSTRUCTIONS, PNF REPEATS IT AND WAITS FOR THE PF TO REPEAT. I DO NOT RECALL HEARING THE PF REPEAT THE HOLD SHORT AND DID NOT PROMPT HIM FOR IT. WE WERE STILL SOME DISTANCE FROM RWY 32R, SO I ADVISED PF THAT I WAS GOING HEAD DOWN TO PROGRAM THE DEP (SOMETHING THAT WASN'T NECESSARY AT THE TIME). WHEN I LOOKED UP, WE WERE ALREADY PAST THE RWY 32R HOLD SHORT LINE. I DO NOT BELIEVE THAT WE CAUSED A CONFLICT. RWY 27R WAS IN USE FOR LNDGS AND I DO NOT BELIEVE THAT RWY 32R WAS IN USE. I BELIEVE THAT WE WERE ASKED TO HOLD SHORT OF RWY 32R BECAUSE OF THE LIMITED SPACE BTWN THE RWYS 32R AND 27R THRESHOLDS. IN THE FUTURE, BESIDES MAKING SURE THAT WE FOLLOW THE REPETITION/CONFIRMATION PROC, I WILL RECONSIDER THE NEED TO EVER GO HEAD DOWN WHEN WE HAVE HOLD SHORT INSTRUCTIONS. IF NECESSARY TO GO HEAD DOWN, IT WOULD BE WISE TO RECONFIRM ANY HOLD SHORT INSTRUCTIONS AT THAT TIME.

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.