Flight crew inadvertently crossed runway hold short line. Unauthorized runway entry.

Attributes
ACN	305707
Time
Date	199505
Day	Tue
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : bwi
State Reference	MD
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	B727-200
Operating Under FAR Part	Part 121
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 : 150 flight time total : 10000 flight time type : 3000
ASRS Report	305707
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : instrument pilot : commercial
Events
Anomaly	incursion : runway non adherence : clearance
Independent Detector	other flight crewa other other : unspecified cockpit
Resolutory Action	flight crew : exited adverse environment flight crew : returned to intended course or assigned course flight crew : became reoriented
Consequence	Other
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation
Situations
Airport	other physical facility

Narrative:

I was captain of air carrier flight X that landed on runway 33L at bwi. After landing, was taxiing southeast on taxiway parallel to runway 33L/15R. Taxiway continued straight across runway 4/22. My intended taxi route was to turn left to taxi on parallel to runway 4/22. I missed the turn slightly and had to turn hard left to make taxiway. Aircraft passed over hold line for runway 4/22, but did not get onto runway 4/22. If there was a runway sign for runway 4/22, I did not see it or a taxiway sign. Callback conversation with reporter revealed the following information: the reporter stated that he could not remember whether he started flying the evening before or after XA00 but did remember that fatigue was not a factor in this situation. This event occurred on taxi in after landing for the last flight of the sequence and the crew was going to the hotel for about 16 hours rest. The taxi problem occurred in early morning and the sun had already come up so night operation was not the problem. The problem was the orientation of the signs with respect to the txwys. The taxiway signs just weren't evident when looking for them the reporter said.

Original NASA ASRS Text

Title: FLC INADVERTENTLY CROSSED RWY HOLD SHORT LINE. UNAUTH RWY ENTRY.

Narrative: I WAS CAPT OF ACR FLT X THAT LANDED ON RWY 33L AT BWI. AFTER LNDG, WAS TAXIING SE ON TXWY PARALLEL TO RWY 33L/15R. TXWY CONTINUED STRAIGHT ACROSS RWY 4/22. MY INTENDED TAXI RTE WAS TO TURN L TO TAXI ON PARALLEL TO RWY 4/22. I MISSED THE TURN SLIGHTLY AND HAD TO TURN HARD L TO MAKE TXWY. ACFT PASSED OVER HOLD LINE FOR RWY 4/22, BUT DID NOT GET ONTO RWY 4/22. IF THERE WAS A RWY SIGN FOR RWY 4/22, I DID NOT SEE IT OR A TXWY SIGN. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: THE RPTR STATED THAT HE COULD NOT REMEMBER WHETHER HE STARTED FLYING THE EVENING BEFORE OR AFTER XA00 BUT DID REMEMBER THAT FATIGUE WAS NOT A FACTOR IN THIS SIT. THIS EVENT OCCURRED ON TAXI IN AFTER LNDG FOR THE LAST FLT OF THE SEQUENCE AND THE CREW WAS GOING TO THE HOTEL FOR ABOUT 16 HRS REST. THE TAXI PROB OCCURRED IN EARLY MORNING AND THE SUN HAD ALREADY COME UP SO NIGHT OP WAS NOT THE PROB. THE PROB WAS THE ORIENTATION OF THE SIGNS WITH RESPECT TO THE TXWYS. THE TXWY SIGNS JUST WEREN'T EVIDENT WHEN LOOKING FOR THEM THE RPTR SAID.

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.