Runway incursion when the PIC of a beech jet turns onto runway 4R thinking it is taxiway a at mdw, i...

Attributes
ACN	547809
Time
Date	200205
Day	Tue
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : mdw.airport
State Reference	IL
Altitude	agl single value : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	general aviation : personal
Make Model Name	Beechjet 400
Operating Under FAR Part	Part 91
Flight Phase	landing : roll
Flight Plan	IFR
Person 1
Affiliation	other
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 120 flight time total : 5400 flight time type : 1500
ASRS Report	547809
Person 2
Affiliation	other
Function	flight crew : first officer
Qualification	pilot : atp
Experience	flight time last 90 days : 100 flight time total : 3000 flight time type : 670
ASRS Report	547810
Events
Anomaly	incursion : runway non adherence : clearance non adherence : far non adherence : published procedure
Independent Detector	other controllera other flight crewa
Resolutory Action	controller : issued new clearance 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:

We had just landed on runway 31C. (Runways 31L, 31C and 31R were in use.) we missed taxiway Y and made a left turn on runway 4R/22L. PNF immediately advised the tower. We missed txwys Y and V when the tower responded. They advised to continue to the end of runway 4R, which we did. We were never asked to call the tower. As we taxied in, we heard a commercial carrier having a similar problem. We studied the airport diagram prior to landing and read the 'hot spots.' our plan was to exit at taxiway a, which was the second taxiway turnoff. With no marking to indicate the crossing runway, I guess runway 4R looked like a taxiway. Then, being slightly disoriented initially and concerned about clearing the runway quickly, we missed taxiway K. We restudied the diagram again, and will do so twice before landing at midway in the future.

Original NASA ASRS Text

Title: RWY INCURSION WHEN THE PIC OF A BEECH JET TURNS ONTO RWY 4R THINKING IT IS TXWY A AT MDW, IL.

Narrative: WE HAD JUST LANDED ON RWY 31C. (RWYS 31L, 31C AND 31R WERE IN USE.) WE MISSED TXWY Y AND MADE A L TURN ON RWY 4R/22L. PNF IMMEDIATELY ADVISED THE TWR. WE MISSED TXWYS Y AND V WHEN THE TWR RESPONDED. THEY ADVISED TO CONTINUE TO THE END OF RWY 4R, WHICH WE DID. WE WERE NEVER ASKED TO CALL THE TWR. AS WE TAXIED IN, WE HEARD A COMMERCIAL CARRIER HAVING A SIMILAR PROB. WE STUDIED THE ARPT DIAGRAM PRIOR TO LNDG AND READ THE 'HOT SPOTS.' OUR PLAN WAS TO EXIT AT TXWY A, WHICH WAS THE SECOND TXWY TURNOFF. WITH NO MARKING TO INDICATE THE XING RWY, I GUESS RWY 4R LOOKED LIKE A TXWY. THEN, BEING SLIGHTLY DISORIENTED INITIALLY AND CONCERNED ABOUT CLRING THE RWY QUICKLY, WE MISSED TXWY K. WE RESTUDIED THE DIAGRAM AGAIN, AND WILL DO SO TWICE BEFORE LNDG AT MIDWAY IN THE FUTURE.

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.

Runway incursion when the PIC of a beech jet turns onto runway 4R thinking it is taxiway a at mdw, il.