Runway incursion. Runway was active.

Attributes
ACN	317816
Time
Date	199509
Day	Fri
Local Time Of Day	0001 To 0600
Place
Locale Reference	airport : anc
State Reference	AK
Altitude	agl bound lower : 0 agl bound upper : 0
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	B737-400
Operating Under FAR Part	Part 121
Navigation In Use	Other Other
Flight Phase	landing other
Route In Use	approach : visual
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : flight engineer pilot : atp
Experience	flight time last 90 days : 240 flight time total : 18000
ASRS Report	317816
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : atp
Experience	flight time last 90 days : 210 flight time total : 6000 flight time type : 900
ASRS Report	316948
Events
Anomaly	incursion : runway non adherence : clearance
Independent Detector	other controllera other flight crewa
Resolutory Action	none taken : detected after the fact
Consequence	Other
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

We were cleared to land on runway 14 at anc on a wet and rainy night. On final we requested to roll to the end. We were cleared to roll to the end and taxi to our gate. While rolling out, we noticed that the runway getting very dark at end. Sign for taxiway M was lit but txwys left and K were not (runway construction had been going on for 2 months and the controller told us on phone that it was just opened tonight). Runway terminating bars were always at end of runway on taxiway K. We found ourselves taxiing to runway termination bars but construction put them on far side of runway 6L (active runway). Aircraft on final was instructed to go around as we were approaching taxiway K (or what we thought was taxiway K -- it was runway 6L). There were no lights on runway at far end. It was very dark and drizzly. This could have been a real disaster. Supplemental information from acn 316948: runway 14/32 has been under construction for the past 2 months. The first 800 ft of runway 32 has been closed which includes the intersection of taxiway K. Prior to construction, runway 32 approach end terminated adjacent to taxiway K. Construction complete sep/aa/95 (hours before we landed). No runway lights exist after taxiway K!

Original NASA ASRS Text

Title: RWY INCURSION. RWY WAS ACTIVE.

Narrative: WE WERE CLRED TO LAND ON RWY 14 AT ANC ON A WET AND RAINY NIGHT. ON FINAL WE REQUESTED TO ROLL TO THE END. WE WERE CLRED TO ROLL TO THE END AND TAXI TO OUR GATE. WHILE ROLLING OUT, WE NOTICED THAT THE RWY GETTING VERY DARK AT END. SIGN FOR TXWY M WAS LIT BUT TXWYS L AND K WERE NOT (RWY CONSTRUCTION HAD BEEN GOING ON FOR 2 MONTHS AND THE CTLR TOLD US ON PHONE THAT IT WAS JUST OPENED TONIGHT). RWY TERMINATING BARS WERE ALWAYS AT END OF RWY ON TXWY K. WE FOUND OURSELVES TAXIING TO RWY TERMINATION BARS BUT CONSTRUCTION PUT THEM ON FAR SIDE OF RWY 6L (ACTIVE RWY). ACFT ON FINAL WAS INSTRUCTED TO GAR AS WE WERE APCHING TXWY K (OR WHAT WE THOUGHT WAS TXWY K -- IT WAS RWY 6L). THERE WERE NO LIGHTS ON RWY AT FAR END. IT WAS VERY DARK AND DRIZZLY. THIS COULD HAVE BEEN A REAL DISASTER. SUPPLEMENTAL INFO FROM ACN 316948: RWY 14/32 HAS BEEN UNDER CONSTRUCTION FOR THE PAST 2 MONTHS. THE FIRST 800 FT OF RWY 32 HAS BEEN CLOSED WHICH INCLUDES THE INTXN OF TXWY K. PRIOR TO CONSTRUCTION, RWY 32 APCH END TERMINATED ADJACENT TO TXWY K. CONSTRUCTION COMPLETE SEP/AA/95 (HRS BEFORE WE LANDED). NO RWY LIGHTS EXIST AFTER TXWY K!

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.