B757-300 flight crew has a runway incursion at pbi.

Attributes
ACN	571811
Time
Date	200301
Day	Mon
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : pbi.airport
State Reference	FL
Altitude	agl single value : 0
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	B757-300
Operating Under FAR Part	Part 121
Navigation In Use	other
Flight Phase	ground : taxi
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : commercial pilot : atp pilot : instrument pilot : multi engine
Experience	flight time last 90 days : 200 flight time total : 16300 flight time type : 1700
ASRS Report	571811
Person 2
Affiliation	company : air carrier
Function	oversight : pic
Events
Anomaly	incursion : runway non adherence : far non adherence : clearance non adherence : company policies
Independent Detector	other flight crewa other flight crewb
Resolutory Action	controller : issued new clearance flight crew : became reoriented
Consequence	faa : reviewed incident with flight crew
Supplementary
Problem Areas	Airport Flight Crew Human Performance ATC Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

Tower/ground (combined) issued a clearance to taxi to runway 27R for departure. The captain and I had anticipated runway 9L for departure. The airport was turned around after we contacted clearance/delivery. I informed the captain that I would need to reload new takeoff data into the FMC for runway 27R, and that I would be heads-down. I asked if he would be ok. He said yes. I was heads-down for no more than 30 seconds and then announced I was back up. The captain then told me he missed the turn to the proper taxiway. I said stop, but he ventured beyond the hold line and entered runway 31-13. ATC noticed our mistake and instructed us to taxi down runway 31 to taxiway a, taxiway B, and taxiway C to runway 27R. We did so without further incident. Although runway 27R was the primary runway, it is my belief that runway 31-13 was also in service. I was disoriented from being heads-down. I do not understand why the captain continued onto a runway despite my objection. Kpbi was utilizing combined tower/ground services at the time of the incident. If a dedicated ground controller was on duty, the mistake may have been caught sooner.

Original NASA ASRS Text

Title: B757-300 FLT CREW HAS A RWY INCURSION AT PBI.

Narrative: TWR/GND (COMBINED) ISSUED A CLRNC TO TAXI TO RWY 27R FOR DEP. THE CAPT AND I HAD ANTICIPATED RWY 9L FOR DEP. THE ARPT WAS TURNED AROUND AFTER WE CONTACTED CLRNC/DELIVERY. I INFORMED THE CAPT THAT I WOULD NEED TO RELOAD NEW TKOF DATA INTO THE FMC FOR RWY 27R, AND THAT I WOULD BE HEADS-DOWN. I ASKED IF HE WOULD BE OK. HE SAID YES. I WAS HEADS-DOWN FOR NO MORE THAN 30 SECONDS AND THEN ANNOUNCED I WAS BACK UP. THE CAPT THEN TOLD ME HE MISSED THE TURN TO THE PROPER TXWY. I SAID STOP, BUT HE VENTURED BEYOND THE HOLD LINE AND ENTERED RWY 31-13. ATC NOTICED OUR MISTAKE AND INSTRUCTED US TO TAXI DOWN RWY 31 TO TXWY A, TXWY B, AND TXWY C TO RWY 27R. WE DID SO WITHOUT FURTHER INCIDENT. ALTHOUGH RWY 27R WAS THE PRIMARY RWY, IT IS MY BELIEF THAT RWY 31-13 WAS ALSO IN SVC. I WAS DISORIENTED FROM BEING HEADS-DOWN. I DO NOT UNDERSTAND WHY THE CAPT CONTINUED ONTO A RWY DESPITE MY OBJECTION. KPBI WAS UTILIZING COMBINED TWR/GND SVCS AT THE TIME OF THE INCIDENT. IF A DEDICATED GND CTLR WAS ON DUTY, THE MISTAKE MAY HAVE BEEN CAUGHT SOONER.

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.