ARTCC controller cites ATIS frequency overlap reported by a B737 en route from geg, wa, to pdx, or. ...

Attributes
ACN	393719
Time
Date	199802
Day	Tue
Local Time Of Day	0601 To 1200
Place
Locale Reference	atc facility : ykm
State Reference	WA
Environment
Flight Conditions	IMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zse
Operator	common carrier : air carrier
Make Model Name	B737 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	cruise other
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : radar
Qualification	controller : radar
Experience	controller radar : 14
ASRS Report	393719
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Events
Anomaly	other anomaly other
Independent Detector	other flight crewa
Resolutory Action	none taken : anomaly accepted
Consequence	Other
Supplementary
Primary Problem	Navigational Facility
Air Traffic Incident	other
Situations
Navigational Aid	Unspecified

Narrative:

A recent policy has been instituted by the FAA of standardizing (120.625) ATIS frequencys. Today an air carrier midway between pdx and geg was attempting to pick up the geg ATIS (destination). All he could hear was the pdx ATIS. 20 mi later he could pick up the geg ATIS but with a squeal (frequency override). In discussing the problem with airway facilities technicians, they said that everything was operating as specified. ATIS must be usable within 50 mi below 20000 ft. However, most pilots want to know ATIS/WX information long before that point to plan arrival. Within 50 mi the pilots are busy flying and in descent profile. Also, these ATIS transmitters are 10 watt channels -- pretty powerful for something that is only supposed to be assured within 50 mi. So, I anticipate more complaints by pilots, more WX/ATIS requests from en route controller by the pilots. Standardization of frequencys is counter to past FAA practice of assuring no frequency overlap within 200 mi (that's what I seem to remember as being the parameter).

Original NASA ASRS Text

Title: ARTCC CTLR CITES ATIS FREQ OVERLAP RPTED BY A B737 ENRTE FROM GEG, WA, TO PDX, OR. RPTR STATES PROB AS FAA'S POLICY TO STANDARDIZE ATIS FREQS.

Narrative: A RECENT POLICY HAS BEEN INSTITUTED BY THE FAA OF STANDARDIZING (120.625) ATIS FREQS. TODAY AN ACR MIDWAY BTWN PDX AND GEG WAS ATTEMPTING TO PICK UP THE GEG ATIS (DEST). ALL HE COULD HEAR WAS THE PDX ATIS. 20 MI LATER HE COULD PICK UP THE GEG ATIS BUT WITH A SQUEAL (FREQ OVERRIDE). IN DISCUSSING THE PROB WITH AIRWAY FACILITIES TECHNICIANS, THEY SAID THAT EVERYTHING WAS OPERATING AS SPECIFIED. ATIS MUST BE USABLE WITHIN 50 MI BELOW 20000 FT. HOWEVER, MOST PLTS WANT TO KNOW ATIS/WX INFO LONG BEFORE THAT POINT TO PLAN ARR. WITHIN 50 MI THE PLTS ARE BUSY FLYING AND IN DSCNT PROFILE. ALSO, THESE ATIS XMITTERS ARE 10 WATT CHANNELS -- PRETTY POWERFUL FOR SOMETHING THAT IS ONLY SUPPOSED TO BE ASSURED WITHIN 50 MI. SO, I ANTICIPATE MORE COMPLAINTS BY PLTS, MORE WX/ATIS REQUESTS FROM ENRTE CTLR BY THE PLTS. STANDARDIZATION OF FREQS IS COUNTER TO PAST FAA PRACTICE OF ASSURING NO FREQ OVERLAP WITHIN 200 MI (THAT'S WHAT I SEEM TO REMEMBER AS BEING THE PARAMETER).

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.

ARTCC controller cites ATIS frequency overlap reported by a B737 en route from geg, wa, to pdx, or. Reporter states problem as FAA's policy to standardize ATIS frequencys.