Apparent lack of interfacility coordination between rno TRACON and ZOA.

Attributes
ACN	309040
Time
Date	199506
Day	Wed
Local Time Of Day	0601 To 1200
Place
Locale Reference	atc facility : irno airport : rno
State Reference	NV
Altitude	msl bound lower : 15000 msl bound upper : 15000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zoa tracon : rno
Operator	common carrier : air carrier
Make Model Name	Commercial Fixed Wing
Operating Under FAR Part	Part 121
Navigation In Use	Other Other
Flight Phase	climbout : intermediate altitude cruise other
Route In Use	departure other departure sid : sid enroute airway : zoa
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp pilot : cfi pilot : commercial pilot : flight engineer pilot : instrument
Experience	flight time last 90 days : 240 flight time total : 12600 flight time type : 7600
ASRS Report	309040
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : instrument pilot : commercial
Events
Anomaly	other anomaly other other anomaly other
Independent Detector	other controllera other flight crewa
Resolutory Action	controller : issued new clearance
Consequence	faa : reviewed incident with flight crew
Supplementary
Primary Problem	ATC Human Performance
Air Traffic Incident	Inter Facility Coordination Failure

Narrative:

Flight from reno to phoenix. Approach control radar was OTS, but ARTCC radar was operating. We received a clearance via the reno 1 departure mustang (fmg) as filed, maintain 13000 ft, etc. (A clearance exactly as I have received a hundred times or more.) normally, prior to reaching wagge intersection, we are given a clearance to fly heading 120 degree, vectors to beaty (bty). Since the terminal radar was OTS, I consulted the terminal data on the SID, which stated 'climb on south localizer course, expect radar vectors to assigned route of first fix,' since there is no published transition on the SID - - there is no further routing after wagge intersection. We contacted oakland ARTCC on 128.8 as we continued to climb on the south localizer course. The center seemed surprised that we were still on runway heading (via localizer course), and asked if we were assigned that heading? We replied no, but were waiting for vectors as per the SID. I sensed a breakdown between terminal and ARTCC concerning our clearance. VFR WX prevailed and there was no conflict.

Original NASA ASRS Text

Title: APPARENT LACK OF INTERFACILITY COORD BTWN RNO TRACON AND ZOA.

Narrative: FLT FROM RENO TO PHOENIX. APCH CTL RADAR WAS OTS, BUT ARTCC RADAR WAS OPERATING. WE RECEIVED A CLRNC VIA THE RENO 1 DEP MUSTANG (FMG) AS FILED, MAINTAIN 13000 FT, ETC. (A CLRNC EXACTLY AS I HAVE RECEIVED A HUNDRED TIMES OR MORE.) NORMALLY, PRIOR TO REACHING WAGGE INTXN, WE ARE GIVEN A CLRNC TO FLY HDG 120 DEG, VECTORS TO BEATY (BTY). SINCE THE TERMINAL RADAR WAS OTS, I CONSULTED THE TERMINAL DATA ON THE SID, WHICH STATED 'CLB ON S LOC COURSE, EXPECT RADAR VECTORS TO ASSIGNED RTE OF FIRST FIX,' SINCE THERE IS NO PUBLISHED TRANSITION ON THE SID - - THERE IS NO FURTHER ROUTING AFTER WAGGE INTXN. WE CONTACTED OAKLAND ARTCC ON 128.8 AS WE CONTINUED TO CLB ON THE S LOC COURSE. THE CTR SEEMED SURPRISED THAT WE WERE STILL ON RWY HDG (VIA LOC COURSE), AND ASKED IF WE WERE ASSIGNED THAT HDG? WE REPLIED NO, BUT WERE WAITING FOR VECTORS AS PER THE SID. I SENSED A BREAKDOWN BTWN TERMINAL AND ARTCC CONCERNING OUR CLRNC. VFR WX PREVAILED AND THERE WAS NO CONFLICT.

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.