B737-500 misses assigned taxiway incurs taxiway and runway before calling ground control at bwi.

Attributes
ACN	452358
Time
Date	199910
Day	Wed
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : bwi.airport
State Reference	MD
Altitude	agl single value : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	B737-500
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 : instrument pilot : commercial pilot : atp pilot : multi engine
Experience	flight time last 90 days : 225 flight time total : 9150 flight time type : 3100
ASRS Report	452358
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Events
Anomaly	incursion : taxiway incursion : runway non adherence : far non adherence : clearance
Independent Detector	atc equipment other atc equipment : radar other controllera
Resolutory Action	controller : issued new clearance controller : issued advisory controller : provided flight assist flight crew : became reoriented none taken : detected after the fact
Consequence	faa : reviewed incident with flight crew
Supplementary
Problem Areas	Airport Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

Our flight was given a clearance to taxi to runway 28 at bwi airport, which we acknowledge. We made a left turn out after the pushback, heading toward taxiway P. We missed the turn onto taxiway P and in the confusion we headed onto taxiway east across runway 28 and onto taxiway D. At this point we called ground control and advised them of our position. They told us to hold our position and then advised us we had not conflicted with any traffic and that we could use runway 33L for takeoff. We were then cleared for takeoff on runway 33L. The flight was uneventful. The area in question is a well known and documented area for taxi deviations at bwi airport. The large buildings in front of taxiway P and the close proximity of txwys east and P taxiway intersection to runway 28 make for a confusing sequence of short turns around the building necessary to get on taxiway P without turning onto taxiway east. Perhaps a more specific taxi clearance is required when asked to taxi to runway 28 around the building located in the middle of this busy intersection.

Original NASA ASRS Text

Title: B737-500 MISSES ASSIGNED TXWY INCURS TXWY AND RWY BEFORE CALLING GND CTL AT BWI.

Narrative: OUR FLT WAS GIVEN A CLRNC TO TAXI TO RWY 28 AT BWI ARPT, WHICH WE ACKNOWLEDGE. WE MADE A L TURN OUT AFTER THE PUSHBACK, HEADING TOWARD TXWY P. WE MISSED THE TURN ONTO TXWY P AND IN THE CONFUSION WE HEADED ONTO TXWY E ACROSS RWY 28 AND ONTO TXWY D. AT THIS POINT WE CALLED GND CTL AND ADVISED THEM OF OUR POS. THEY TOLD US TO HOLD OUR POS AND THEN ADVISED US WE HAD NOT CONFLICTED WITH ANY TFC AND THAT WE COULD USE RWY 33L FOR TKOF. WE WERE THEN CLRED FOR TKOF ON RWY 33L. THE FLT WAS UNEVENTFUL. THE AREA IN QUESTION IS A WELL KNOWN AND DOCUMENTED AREA FOR TAXI DEVS AT BWI ARPT. THE LARGE BUILDINGS IN FRONT OF TXWY P AND THE CLOSE PROX OF TXWYS E AND P TXWY INTXN TO RWY 28 MAKE FOR A CONFUSING SEQUENCE OF SHORT TURNS AROUND THE BUILDING NECESSARY TO GET ON TXWY P WITHOUT TURNING ONTO TXWY E. PERHAPS A MORE SPECIFIC TAXI CLRNC IS REQUIRED WHEN ASKED TO TAXI TO RWY 28 AROUND THE BUILDING LOCATED IN THE MIDDLE OF THIS BUSY INTXN.

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.