<< >> NASA ASRS Report 324170, December 1995

After landing on runway 03 flight crew exited at taxiway C and proceeded toward gate, not realizing that runway 12/30 was being crossed without clearance.

Attributes
ACN	324170
Time
Date	199512
Day	Mon
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : abq
State Reference	NM
Altitude	agl bound lower : 0 agl bound upper : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tower : btr
Operator	common carrier : air carrier
Make Model Name	B737-200
Operating Under FAR Part	Part 121
Flight Phase	ground other : taxi landing other
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : flight engineer pilot : cfi pilot : atp
Experience	flight time last 90 days : 250 flight time total : 14000 flight time type : 8000
ASRS Report	324170
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : atp pilot : commercial
Experience	flight time last 90 days : 240 flight time total : 7500 flight time type : 2500
ASRS Report	324488
Events
Anomaly	incursion : runway non adherence : far
Independent Detector	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:

After landing and clearing the runway, I proceeded via the normal taxi route to the gate. After crossing an intersecting runway, I realized we had not received the normal communication from the tower to either call ground or taxi to the gate. We had crossed the runway without clearance. There was no traffic using that runway, and no conflict occurred. The tower subsequently cleared us across the remaining runway, and to the ramp. We had been on duty by that time for 10 hours. The lone controller in charge of all frequencys was neither a routine nor standard situation. The tower was manned by 1 individual, who controled approach, departure, tower, ground, and clearance delivery position.

Related reports:

• Training flight intended landing at ugn when another trainin...
• A controller was aware of a landing strip which he says is i...
• Gear up landing after animal strike on takeoff from non towe...
• After landing lax runway 25L, a CL65 crew proceeded to cross...

	Enter your search terms Submit search form
	Web www.37000feet.com

Original NASA ASRS Text

Title: AFTER LNDG ON RWY 03 FLC EXITED AT TXWY C AND PROCEEDED TOWARD GATE, NOT REALIZING THAT RWY 12/30 WAS BEING CROSSED WITHOUT CLRNC.

Narrative: AFTER LNDG AND CLRING THE RWY, I PROCEEDED VIA THE NORMAL TAXI RTE TO THE GATE. AFTER XING AN INTERSECTING RWY, I REALIZED WE HAD NOT RECEIVED THE NORMAL COM FROM THE TWR TO EITHER CALL GND OR TAXI TO THE GATE. WE HAD CROSSED THE RWY WITHOUT CLRNC. THERE WAS NO TFC USING THAT RWY, AND NO CONFLICT OCCURRED. THE TWR SUBSEQUENTLY CLRED US ACROSS THE REMAINING RWY, AND TO THE RAMP. WE HAD BEEN ON DUTY BY THAT TIME FOR 10 HRS. THE LONE CTLR IN CHARGE OF ALL FREQS WAS NEITHER A ROUTINE NOR STANDARD SIT. THE TWR WAS MANNED BY 1 INDIVIDUAL, WHO CTLED APCH, DEP, TWR, GND, AND CLRNC DELIVERY POS.

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.