Flight crew confused on runway clearance crosses without permission at alb.

Attributes
ACN	183116
Time
Date	199107
Day	Tue
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : alb
State Reference	NY
Altitude	agl bound lower : 0 agl bound upper : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	Medium Large Transport, Low Wing, 2 Turbojet Eng
Flight Phase	ground other : taxi
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 200 flight time total : 18000 flight time type : 3000
ASRS Report	183116
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : atp
Experience	flight time total : 8000 flight time type : 1500
ASRS Report	182953
Events
Anomaly	incursion : runway non adherence : far non adherence : clearance
Independent Detector	other flight crewa
Resolutory Action	none taken : anomaly accepted
Consequence	faa : reviewed incident with flight crew
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

Captain understood to taxi to runway 19 (west/O crossing runway restrictions). However, first officer understood clearance was to runway 01 (he conducted the communications with ground control). Xed runway 28 (in the vicinity of far end en route to runway 19). Visly confirmed that absolutely no traffic was coming from either direction prior to crossing (WX was unlimited ceiling and visibility). First officer was conducting checklist and noted that he thought we were going to wrong runway as we passed halfway through runway 28. No incident or problem, but crew coordination was impacted by the conduct of before takeoff checklist. This case is a reminder that, while we try to eliminate needless extra communication with tower, perhaps it is necessary to always confirm clearance to cross every runway even when clearance supposedly is 'all the way,' since the crew may be going all the way to a runway which the tower did not intend. This crew was returning from an 'on duty all night' trip, which surely did not help. Again, no conflict resulted due to visibility checking of the runways.

Original NASA ASRS Text

Title: FLT CREW CONFUSED ON RWY CLRNC CROSSES WITHOUT PERMISSION AT ALB.

Narrative: CAPT UNDERSTOOD TO TAXI TO RWY 19 (W/O XING RWY RESTRICTIONS). HOWEVER, F/O UNDERSTOOD CLRNC WAS TO RWY 01 (HE CONDUCTED THE COMS WITH GND CTL). XED RWY 28 (IN THE VICINITY OF FAR END ENRTE TO RWY 19). VISLY CONFIRMED THAT ABSOLUTELY NO TFC WAS COMING FROM EITHER DIRECTION PRIOR TO XING (WX WAS UNLIMITED CEILING AND VISIBILITY). F/O WAS CONDUCTING CHKLIST AND NOTED THAT HE THOUGHT WE WERE GOING TO WRONG RWY AS WE PASSED HALFWAY THROUGH RWY 28. NO INCIDENT OR PROB, BUT CREW COORD WAS IMPACTED BY THE CONDUCT OF BEFORE TKOF CHKLIST. THIS CASE IS A REMINDER THAT, WHILE WE TRY TO ELIMINATE NEEDLESS EXTRA COM WITH TWR, PERHAPS IT IS NECESSARY TO ALWAYS CONFIRM CLRNC TO CROSS EVERY RWY EVEN WHEN CLRNC SUPPOSEDLY IS 'ALL THE WAY,' SINCE THE CREW MAY BE GOING ALL THE WAY TO A RWY WHICH THE TWR DID NOT INTEND. THIS CREW WAS RETURNING FROM AN 'ON DUTY ALL NIGHT' TRIP, WHICH SURELY DID NOT HELP. AGAIN, NO CONFLICT RESULTED DUE TO VIS CHKING OF THE RWYS.

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.