Flight crew of a widebody transport air carrier aircraft inadvertently crossed an active runway during after landing taxi due to missing the local tower controller instructions to contact ground control.

Home

Browse by month

Random

Latest

About

Contact

Attributes
ACN	246753
Time
Date	199307
Day	Sat
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : mem
State Reference	TN
Altitude	agl bound lower : 0 agl bound upper : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tower : mem
Operator	common carrier : air carrier
Make Model Name	Widebody, Low Wing, 3 Turbojet Eng
Navigation In Use	Other
Flight Phase	ground other : taxi
Flight Plan	IFR
Aircraft 2
Make Model Name	Small Transport
Flight Phase	descent : approach landing : go around
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : flight engineer pilot : atp
Experience	flight time last 90 days : 200 flight time total : 8500 flight time type : 100
ASRS Report	246753
Person 2
Affiliation	company : air carrier
Function	flight crew : second officer
Qualification	pilot : atp pilot : flight engineer
Experience	flight time last 90 days : 150 flight time total : 9000 flight time type : 1500
ASRS Report	246752
Events
Anomaly	incursion : runway non adherence : far non adherence : clearance other anomaly other
Independent Detector	other controllera
Resolutory Action	none taken : detected after the fact
Consequence	faa : reviewed incident with flight crew
Miss Distance	horizontal : 3000 vertical : 100
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

I, as first officer, landed the aircraft and the captain took control at runway turnoff (runway 36R at memphis). We were taxiing via taxiway B to the ramp. Both the captain and I thought we were cleared to taxi to the ramp and remain on tower frequency. As I was finishing part of the after landing checklist, I looked up as we approached the crossing of runway 27. The captain was taxiing at a moderate pace (15 KTS) as we noticed a twin engine aircraft on final for runway 27. Instead of slamming on brakes, the captain continued across because there was no threat of conflict. As we got across we noticed the aircraft had gone around. We contacted tower to see if we had caused the problem. The controller said he had told us to contact ground control and that we had not been cleared across runway 27. He said don't worry about it. I am not sure as to what our clearance was, but at the time I thought we were clear to the ramp, as did the captain. The other aircraft went around from about 1/2 mi on final so it was not a close call situation.

Original NASA ASRS Text

Title: FLC OF A WDB ACR ACFT INADVERTENTLY CROSSED AN ACTIVE RWY DURING AFTER LNDG TAXI DUE TO MISSING THE LCL TWR CTLR INSTRUCTIONS TO CONTACT GND CTL.

Narrative: I, AS FO, LANDED THE ACFT AND THE CAPT TOOK CTL AT RWY TURNOFF (RWY 36R AT MEMPHIS). WE WERE TAXIING VIA TXWY B TO THE RAMP. BOTH THE CAPT AND I THOUGHT WE WERE CLRED TO TAXI TO THE RAMP AND REMAIN ON TWR FREQ. AS I WAS FINISHING PART OF THE AFTER LNDG CHKLIST, I LOOKED UP AS WE APCHED THE XING OF RWY 27. THE CAPT WAS TAXIING AT A MODERATE PACE (15 KTS) AS WE NOTICED A TWIN ENG ACFT ON FINAL FOR RWY 27. INSTEAD OF SLAMMING ON BRAKES, THE CAPT CONTINUED ACROSS BECAUSE THERE WAS NO THREAT OF CONFLICT. AS WE GOT ACROSS WE NOTICED THE ACFT HAD GONE AROUND. WE CONTACTED TWR TO SEE IF WE HAD CAUSED THE PROB. THE CTLR SAID HE HAD TOLD US TO CONTACT GND CTL AND THAT WE HAD NOT BEEN CLRED ACROSS RWY 27. HE SAID DON'T WORRY ABOUT IT. I AM NOT SURE AS TO WHAT OUR CLRNC WAS, BUT AT THE TIME I THOUGHT WE WERE CLR TO THE RAMP, AS DID THE CAPT. THE OTHER ACFT WENT AROUND FROM ABOUT 1/2 MI ON FINAL SO IT WAS NOT A CLOSE CALL SIT.

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.