Air carrier first officer questions elp controller's attention to duty when after asking about traffic on final for an intersecting runway, controller issues go around.

Home

Browse by month

Random

Latest

About

Contact

Attributes
ACN	515430
Time
Date	200106
Day	Thu
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : elp.airport
State Reference	TX
Altitude	agl single value : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tower : elp.tower artcc : zma.artcc
Operator	common carrier : air carrier
Make Model Name	Medium Large Transport, Low Wing, 2 Turbojet Eng
Operating Under FAR Part	Part 121
Flight Phase	landing : roll
Flight Plan	IFR
Aircraft 2
Controlling Facilities	tower : elp.tower
Operator	common carrier : air carrier
Make Model Name	B727 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	landing : go around
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : commercial pilot : atp pilot : cfi pilot : instrument pilot : multi engine
ASRS Report	515430
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Events
Anomaly	conflict : ground less severe
Independent Detector	other controllera other flight crewa
Resolutory Action	controller : issued new clearance flight crew : executed go around
Consequence	faa : reviewed incident with flight crew
Supplementary
Problem Areas	ATC Human Performance
Primary Problem	ATC Human Performance
Situations
ATC Facility	procedure or policy : elp.tracon

Narrative:

Upon landing rollout on runway 22, saw a B727 on very short final for landing on runway 4. We expedited to the nearest taxiway as I queried tower about what was going on. He told the B727 to 'go around now,' and then told me that he was not yet cleared to land. It turns out that the tower was hoping that we were going to make the high speed turn-off, then he would clear the B727 to land. We did not make the high speed turn-off. In fact, we had no knowledge of the B727's existence. I believe that he was doing touch-and-go training as we saw him again after we reached the gate. It is very common at el paso to run opposite direction operations. This day, 1 controller was working ground and tower. When we left the next morning on runway 4, air carrier Y was on a visual approach for runway 22. Tower told air carrier Y about our departure, but failed to let us know about them. There is a pattern of very casual operating practices here that should be addressed.

Original NASA ASRS Text

Title: ACR FO QUESTIONS ELP CTLR'S ATTN TO DUTY WHEN AFTER ASKING ABOUT TFC ON FINAL FOR AN INTERSECTING RWY, CTLR ISSUES GAR.

Narrative: UPON LNDG ROLLOUT ON RWY 22, SAW A B727 ON VERY SHORT FINAL FOR LNDG ON RWY 4. WE EXPEDITED TO THE NEAREST TXWY AS I QUERIED TWR ABOUT WHAT WAS GOING ON. HE TOLD THE B727 TO 'GO AROUND NOW,' AND THEN TOLD ME THAT HE WAS NOT YET CLRED TO LAND. IT TURNS OUT THAT THE TWR WAS HOPING THAT WE WERE GOING TO MAKE THE HIGH SPD TURN-OFF, THEN HE WOULD CLR THE B727 TO LAND. WE DID NOT MAKE THE HIGH SPD TURN-OFF. IN FACT, WE HAD NO KNOWLEDGE OF THE B727'S EXISTENCE. I BELIEVE THAT HE WAS DOING TOUCH-AND-GO TRAINING AS WE SAW HIM AGAIN AFTER WE REACHED THE GATE. IT IS VERY COMMON AT EL PASO TO RUN OPPOSITE DIRECTION OPS. THIS DAY, 1 CTLR WAS WORKING GND AND TWR. WHEN WE LEFT THE NEXT MORNING ON RWY 4, ACR Y WAS ON A VISUAL APCH FOR RWY 22. TWR TOLD ACR Y ABOUT OUR DEP, BUT FAILED TO LET US KNOW ABOUT THEM. THERE IS A PATTERN OF VERY CASUAL OPERATING PRACTICES HERE THAT SHOULD BE ADDRESSED.

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.