Pilot deviation operational deviation involving air carrier and uga.

Attributes
ACN	291666
Time
Date	199412
Day	Sat
Local Time Of Day	0601 To 1200
Place
Locale Reference	atc facility : phx
State Reference	AZ
Altitude	agl bound lower : 600 agl bound upper : 600
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : phx tower : phx
Operator	common carrier : air carrier
Make Model Name	Commercial Fixed Wing
Operating Under FAR Part	Part 135
Flight Phase	descent : approach landing : go around
Route In Use	approach : visual enroute : on vectors
Flight Plan	IFR
Aircraft 2
Make Model Name	Commercial Fixed Wing
Operating Under FAR Part	other : unknown
Flight Phase	ground : holding ground other : taxi
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : atp pilot : cfi
Experience	flight time last 90 days : 165 flight time total : 2900 flight time type : 165
ASRS Report	291666
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Events
Anomaly	other anomaly other other anomaly other
Independent Detector	other flight crewa
Resolutory Action	other
Consequence	Other
Supplementary
Primary Problem	ATC Human Performance
Air Traffic Incident	Pilot Deviation Operational Deviation

Narrative:

We were landing at phx. Landing runway 8L. The last transmission from approach control was 'cleared for the visual, maintain 160 KTS to the highway.' I was the PF. On about a 1 1/2 to 2 mi final I asked the captain (PNF) for confirmation that we were cleared to land. The captain then realized that we were still on approach frequency. The captain then asked approach if they wanted us on tower frequency. Approach control at that time told us to switch to tower, which we then did. While this was happening, I noticed an aircraft pulling out onto the runway. Tower then had us do a go around, and to contact departure. Departure had us make left traffic for runway 8L. On downwind we were once again cleared for the visual approach. Once again, we were never told to contact tower. As we turned base we asked approach if they wanted us to change to tower frequency. At that time, they had us switch and we were then cleared to land. On both occasions, me and the captain do not recall being told to contact tower, until we asked if they wanted us to. I'm not sure how the problem arose but I seriously believe that was miscom between approach and tower.

Original NASA ASRS Text

Title: PLTDEV OPDEV INVOLVING ACR AND UGA.

Narrative: WE WERE LNDG AT PHX. LNDG RWY 8L. THE LAST XMISSION FROM APCH CTL WAS 'CLRED FOR THE VISUAL, MAINTAIN 160 KTS TO THE HWY.' I WAS THE PF. ON ABOUT A 1 1/2 TO 2 MI FINAL I ASKED THE CAPT (PNF) FOR CONFIRMATION THAT WE WERE CLRED TO LAND. THE CAPT THEN REALIZED THAT WE WERE STILL ON APCH FREQ. THE CAPT THEN ASKED APCH IF THEY WANTED US ON TWR FREQ. APCH CTL AT THAT TIME TOLD US TO SWITCH TO TWR, WHICH WE THEN DID. WHILE THIS WAS HAPPENING, I NOTICED AN ACFT PULLING OUT ONTO THE RWY. TWR THEN HAD US DO A GAR, AND TO CONTACT DEP. DEP HAD US MAKE L TFC FOR RWY 8L. ON DOWNWIND WE WERE ONCE AGAIN CLRED FOR THE VISUAL APCH. ONCE AGAIN, WE WERE NEVER TOLD TO CONTACT TWR. AS WE TURNED BASE WE ASKED APCH IF THEY WANTED US TO CHANGE TO TWR FREQ. AT THAT TIME, THEY HAD US SWITCH AND WE WERE THEN CLRED TO LAND. ON BOTH OCCASIONS, ME AND THE CAPT DO NOT RECALL BEING TOLD TO CONTACT TWR, UNTIL WE ASKED IF THEY WANTED US TO. I'M NOT SURE HOW THE PROB AROSE BUT I SERIOUSLY BELIEVE THAT WAS MISCOM BTWN APCH AND TWR.

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.