Narrative:

Exited runway after landing. Advised by tower to contact ground. Upon contacting ground, was advised that I was 'blocking an active runway.' no further instructions received from ground until I specifically asked twice to confirm taxi clearance. Dwh airport chart shows taxiway on north end of runway 35R, not crossing runway 35R. I had landed on runway 35L. Chart should be changed. Callback conversation with reporter revealed the following information: the reporter reiterated that he was on a private flight and landed at dwh on runway 35L. This was his first flight to dwh and he had reviewed his government charts for the airport diagram ahead of time. He had decided to exit at taxiway east. As he taxied off of runway 35L at taxiway east, he was told by the tower that he was blocking an active runway. When he queried the controller as to which runway he was blocking, the controller would not specify. Feeling at risk for making more mistakes, the reporter would not move his aircraft until he received specific taxi clearance from the controller. All he was told was that he was cleared to taxi to the ramp. The reporter did not recall seeing any lines on the ground to indicate where to hold short for runway 35R or taxi past for runway 35L. On both the commercial and government charts, there does not appear to be any area where taxiway east comes into contact with runway 35R. Callback conversation with dwh tower revealed the following information: the specialist stated that taxiway east merges with the departure end of runway 35R and the approach end of runway 17L. He specified that an aircraft at taxiway east is not clear of the runway. He stated that there are hold short lines depicted on the taxiway.

Google
 

Original NASA ASRS Text

Title: A PVT PLT LANDED AT DWH ON RWY 35L. HE TAXIED OFF OF THE RWY ONTO A TXWY AND CONTACTED GND. GND NOTIFIED HIM THAT HE WAS BLOCKING AN ACTIVE RWY. THE RPTR STATED THAT THE DWH ARPT PLATE SHOULD BE CHANGED.

Narrative: EXITED RWY AFTER LNDG. ADVISED BY TWR TO CONTACT GND. UPON CONTACTING GND, WAS ADVISED THAT I WAS 'BLOCKING AN ACTIVE RWY.' NO FURTHER INSTRUCTIONS RECEIVED FROM GND UNTIL I SPECIFICALLY ASKED TWICE TO CONFIRM TAXI CLRNC. DWH ARPT CHART SHOWS TXWY ON N END OF RWY 35R, NOT XING RWY 35R. I HAD LANDED ON RWY 35L. CHART SHOULD BE CHANGED. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: THE RPTR REITERATED THAT HE WAS ON A PVT FLT AND LANDED AT DWH ON RWY 35L. THIS WAS HIS FIRST FLT TO DWH AND HE HAD REVIEWED HIS GOV CHARTS FOR THE ARPT DIAGRAM AHEAD OF TIME. HE HAD DECIDED TO EXIT AT TXWY E. AS HE TAXIED OFF OF RWY 35L AT TXWY E, HE WAS TOLD BY THE TWR THAT HE WAS BLOCKING AN ACTIVE RWY. WHEN HE QUERIED THE CTLR AS TO WHICH RWY HE WAS BLOCKING, THE CTLR WOULD NOT SPECIFY. FEELING AT RISK FOR MAKING MORE MISTAKES, THE RPTR WOULD NOT MOVE HIS ACFT UNTIL HE RECEIVED SPECIFIC TAXI CLRNC FROM THE CTLR. ALL HE WAS TOLD WAS THAT HE WAS CLRED TO TAXI TO THE RAMP. THE RPTR DID NOT RECALL SEEING ANY LINES ON THE GND TO INDICATE WHERE TO HOLD SHORT FOR RWY 35R OR TAXI PAST FOR RWY 35L. ON BOTH THE COMMERCIAL AND GOV CHARTS, THERE DOES NOT APPEAR TO BE ANY AREA WHERE TXWY E COMES INTO CONTACT WITH RWY 35R. CALLBACK CONVERSATION WITH DWH TWR REVEALED THE FOLLOWING INFO: THE SPECIALIST STATED THAT TXWY E MERGES WITH THE DEP END OF RWY 35R AND THE APCH END OF RWY 17L. HE SPECIFIED THAT AN ACFT AT TXWY E IS NOT CLR OF THE RWY. HE STATED THAT THERE ARE HOLD SHORT LINES DEPICTED ON THE TXWY.

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.