Beech BE1900 pilot has runway incursion at hnl.

Attributes
ACN	725345
Time
Date	200701
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : hnl.airport
State Reference	HI
Altitude	agl single value : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	Beech 1900
Operating Under FAR Part	Part 135
Flight Phase	ground : 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 : 93 flight time total : 5143 flight time type : 128
ASRS Report	725345
Person 2
Affiliation	government : faa
Function	controller : ground
Events
Anomaly	incursion : runway non adherence : clearance
Independent Detector	other controllera other controllerb
Resolutory Action	controller : issued new clearance
Consequence	faa : reviewed incident with flight crew
Supplementary
Problem Areas	Airport Chart Or Publication Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance

Narrative:

Prevailing wind for hnl is consistently northeast but on the day of occurrence; wind was southwest. Runways were switched around from what everyone is most familiar with. I was cleared by ground control to 'hold short of runway 26R at taxiway C and monitor tower.' I correctly complied with this. The tower controller cleared me to cross runway 26R; taxi runway 22L. I misunderstood the controller and crossed runway 26R and went to runway 22L via the intersection of the 2 runways as is commonly assigned to GA aircraft. Another tower controller interrupted radio chatter and notified me of the error as there was an aircraft on approach to runway 26R. Controller instructed me to back-taxi runway 22L which resolved the possible conflict. I feel that this misunderstanding occurred: 1) because the intersection of taxiway C and runway 26R is not clearly marked. Taxiway C intersects the runways at an offset angle. Also; charts incorrectly depict the intersection. The southwest side of taxiway C actually appears to meet runway 26R at the intersection of runway 22L. The controller should have said cross runway 26R into taxiway C and taxi runway 22L. 2) in the 10 yrs of experience operating out of hnl; I have never been asked to cross runway 26R into taxiway C. It is common for GA types to be cleared for an intersection takeoff from the triple intersection of taxiway C/runway 26R/runway 22L.

Original NASA ASRS Text

Title: BEECH BE1900 PLT HAS RWY INCURSION AT HNL.

Narrative: PREVAILING WIND FOR HNL IS CONSISTENTLY NE BUT ON THE DAY OF OCCURRENCE; WIND WAS SW. RWYS WERE SWITCHED AROUND FROM WHAT EVERYONE IS MOST FAMILIAR WITH. I WAS CLRED BY GND CTL TO 'HOLD SHORT OF RWY 26R AT TXWY C AND MONITOR TWR.' I CORRECTLY COMPLIED WITH THIS. THE TWR CTLR CLRED ME TO CROSS RWY 26R; TAXI RWY 22L. I MISUNDERSTOOD THE CTLR AND CROSSED RWY 26R AND WENT TO RWY 22L VIA THE INTXN OF THE 2 RWYS AS IS COMMONLY ASSIGNED TO GA ACFT. ANOTHER TWR CTLR INTERRUPTED RADIO CHATTER AND NOTIFIED ME OF THE ERROR AS THERE WAS AN ACFT ON APCH TO RWY 26R. CTLR INSTRUCTED ME TO BACK-TAXI RWY 22L WHICH RESOLVED THE POSSIBLE CONFLICT. I FEEL THAT THIS MISUNDERSTANDING OCCURRED: 1) BECAUSE THE INTXN OF TXWY C AND RWY 26R IS NOT CLRLY MARKED. TXWY C INTERSECTS THE RWYS AT AN OFFSET ANGLE. ALSO; CHARTS INCORRECTLY DEPICT THE INTXN. THE SW SIDE OF TXWY C ACTUALLY APPEARS TO MEET RWY 26R AT THE INTXN OF RWY 22L. THE CTLR SHOULD HAVE SAID CROSS RWY 26R INTO TXWY C AND TAXI RWY 22L. 2) IN THE 10 YRS OF EXPERIENCE OPERATING OUT OF HNL; I HAVE NEVER BEEN ASKED TO CROSS RWY 26R INTO TXWY C. IT IS COMMON FOR GA TYPES TO BE CLRED FOR AN INTXN TKOF FROM THE TRIPLE INTXN OF TXWY C/RWY 26R/RWY 22L.

Data retrieved from NASA's ASRS site as of January 2009 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.