A B737-800 AT NIP TAXIING TO RWY 27 CROSSED RWYS 27 AND 32 HOLD SHORT LINE NOT REALIZING IT SERVED BOTH RWYS.

Date: 2005-12 · Aircraft: B737-800 · Phase: taxi

Anomalies: deviation-discrepancy-procedural-clearance|deviation-discrepancy-procedural-far

Synopsis

A B737-800 AT NIP TAXIING TO RWY 27 CROSSED RWYS 27 AND 32 HOLD SHORT LINE NOT REALIZING IT SERVED BOTH RWYS.

Narrative

FERRY FLT FROM NIP (JACKSONVILLE NAS)TO ZZZ AT XA10. CLRED TO 'TAXI TO RWY 27' BY GND CTL. EXITED THE RAMP BY BUILDING #1002; TAXIING N TO MAKE A R TURN TO THE E ON TXWY A. CROSSED OVER BOTH HELIPADS AND APCHED RWY 32. WITH CLRNC TO TAXI TO RWY 27; BOTH COPLT AND I VERBALIZED TO EACH OTHER THAT WE WERE CLRED TO CROSS RWY 32 ENRTE TO RWY 27. AFTER XING HOLD SHORT LINE FOR RWY 32 BY ABOUT 20 FT; THE TWR CTLR ADVISED US THAT THE HOLD SHORT LINE THAT WE HAD JUST CROSSED WAS ALSO THE HOLD SHORT POINT FOR RWY 27. WE THEN REALIZED THAT THERE WASN'T ANOTHER HOLD SHORT LINE FOR RWY 27 ON THE E SIDE OF RWY 32. AFTER STOPPING; TWR THEN CLRED US FOR TKOF ON RWY 27. NO CONFLICT CREATED WITH ANY OTHER ACFT. WE DID NOT TAXI ONTO ANY PART OF WHAT I CONSIDERED WAS RWY 27; ONLY THE APCH END OF RWY 32. TXWY/RWY SIGNS AND MARKINGS WERE SPARSE AND UNCLR; AS CAN BE EXPECTED ON MOST MIL BASES. GND CTLR OFFERED NO GUIDANCE OTHER THAN 'TAXI TO RWY 27.' WE WERE USING COPIES OF AIRFIELD CHARTS OBTAINED FROM NIP BASE OPS BECAUSE OUR COMMERCIAL CHART BOOKS DO NOT COVER NIP. THIS WAS NOT A CONTRIBUTING FACTOR. WE SHOULD HAVE REQUESTED PROGRESSIVE TAXI INSTRUCTIONS DUE TO BEING UNFAMILIAR WITH THE AIRFIELD; HOWEVER; THE TAXI RTE FROM CHOCKS TO RWY SEEMED RELATIVELY SIMPLE AND I DIDN'T THINK IT WAS NEEDED.

More incidents for this aircraft family →

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.