Narrative:

Given taxi to taxiway E1 departure runway 19R at mke. Taxied past taxiway E1 and across runway 25R. No conflicts with any traffic. Was then told by tower to continue to end of runway 19R for departure and to call on landline to mke tower upon arrival at destination. Upon talking with tower supervisor, was told no FAA action was being taken. He wanted to know how to prevent further problems. Because he's had several aircraft during the past month which have missed taxiway E1 and taxied on runway 25R -- one during a C172 landing! My suggestions were to change taxiway east to reflect the way most txwys are numbered, ie, taxiway E1 should be the first taxiway from taxiway east to the very end of runway 19R, taxiway E2 would be the second, and taxiway E3 would be where taxiway E1 presently is. Runway 25R should have flashing lights where taxiway east crosses it. Also, the hold short lines for runway 25R should be better highlighted. It might also help to give taxi instructions of 'taxiway E1 short of runway 25R.' this runway 25R has been lengthened recently to allow medium twins and commuters to land on it. This means more traffic with a much greater possibility of a serious conflict! Supplemental information from acn 423204: captain was informed that they have had several aircraft doing the same thing recently, and that they were looking for ways to prevent it in the future. Contributing factors: poorly marked and nonstandard taxiway signs. No 'hold short' flashing lights. I was out of the 'loop' running checklist and making takeoff PA to the flight attendants and therefore could not doublechk the captain's actions. Callback conversation with reporter revealed the following information: first officer stated he did not see runway holding position markings on taxiway east at runway 31/13 or runway 25R/07L intxns. He said there were hold markings on taxiway E1 and taxiway E2. He stated that most of the airport runway and taxiway signs are very confusing.

Related reports:

Google
 

Original NASA ASRS Text

Title: FK10 CREW AT MKE TAXIED OUT TO RWY 19R AT INTXN E1. CAPT BELIEVED E1 WAS AT THE APCH END OF RWY 19R AND INADVERTENTLY CROSSED RWY 25R.

Narrative: GIVEN TAXI TO TXWY E1 DEP RWY 19R AT MKE. TAXIED PAST TXWY E1 AND ACROSS RWY 25R. NO CONFLICTS WITH ANY TFC. WAS THEN TOLD BY TWR TO CONTINUE TO END OF RWY 19R FOR DEP AND TO CALL ON LANDLINE TO MKE TWR UPON ARR AT DEST. UPON TALKING WITH TWR SUPVR, WAS TOLD NO FAA ACTION WAS BEING TAKEN. HE WANTED TO KNOW HOW TO PREVENT FURTHER PROBS. BECAUSE HE'S HAD SEVERAL ACFT DURING THE PAST MONTH WHICH HAVE MISSED TXWY E1 AND TAXIED ON RWY 25R -- ONE DURING A C172 LNDG! MY SUGGESTIONS WERE TO CHANGE TXWY E TO REFLECT THE WAY MOST TXWYS ARE NUMBERED, IE, TXWY E1 SHOULD BE THE FIRST TXWY FROM TXWY E TO THE VERY END OF RWY 19R, TXWY E2 WOULD BE THE SECOND, AND TXWY E3 WOULD BE WHERE TXWY E1 PRESENTLY IS. RWY 25R SHOULD HAVE FLASHING LIGHTS WHERE TXWY E CROSSES IT. ALSO, THE HOLD SHORT LINES FOR RWY 25R SHOULD BE BETTER HIGHLIGHTED. IT MIGHT ALSO HELP TO GIVE TAXI INSTRUCTIONS OF 'TXWY E1 SHORT OF RWY 25R.' THIS RWY 25R HAS BEEN LENGTHENED RECENTLY TO ALLOW MEDIUM TWINS AND COMMUTERS TO LAND ON IT. THIS MEANS MORE TFC WITH A MUCH GREATER POSSIBILITY OF A SERIOUS CONFLICT! SUPPLEMENTAL INFO FROM ACN 423204: CAPT WAS INFORMED THAT THEY HAVE HAD SEVERAL ACFT DOING THE SAME THING RECENTLY, AND THAT THEY WERE LOOKING FOR WAYS TO PREVENT IT IN THE FUTURE. CONTRIBUTING FACTORS: POORLY MARKED AND NONSTANDARD TXWY SIGNS. NO 'HOLD SHORT' FLASHING LIGHTS. I WAS OUT OF THE 'LOOP' RUNNING CHKLIST AND MAKING TKOF PA TO THE FLT ATTENDANTS AND THEREFORE COULD NOT DOUBLECHK THE CAPT'S ACTIONS. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: FO STATED HE DID NOT SEE RWY HOLDING POS MARKINGS ON TXWY E AT RWY 31/13 OR RWY 25R/07L INTXNS. HE SAID THERE WERE HOLD MARKINGS ON TXWY E1 AND TXWY E2. HE STATED THAT MOST OF THE ARPT RWY AND TXWY SIGNS ARE VERY CONFUSING.

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.