Possible track deviation.

Attributes
ACN	295205
Time
Date	199501
Day	Sun
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : las
State Reference	NV
Environment
Flight Conditions	VMC
Light	Dusk
Aircraft 1
Controlling Facilities	tracon : las
Operator	common carrier : air carrier
Make Model Name	B737-200
Operating Under FAR Part	Part 121
Flight Phase	descent : approach
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : atp
Experience	flight time last 90 days : 210 flight time total : 3300 flight time type : 350
ASRS Report	295205
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Events
Anomaly	non adherence : clearance other spatial deviation
Independent Detector	other controllera other flight crewa
Resolutory Action	controller : issued new clearance
Consequence	Other
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation
Situations
ATC Facility	procedure or policy : unspecified

Narrative:

On a flight from den to las, we crossed over hanksville VOR. Instead of the flight plan arrival (STAR) to las, we were given a heading to intercept the localizer inbound to las. We were on our second flight into las in our respective careers, so we were new to the area. As we approached las, we were assigned new headings. We checked on with approach and, as expected, the frequency was busy. We flew our heading and flew past the localizer. As we went to query the controller, he asked if we should have intercepted. We were assigned a new heading to intercept. Being unfamiliar with the area made it difficult to judge where and when to expect our interception to occur. The busy frequency also made it difficult to query the controller. There was no ADF to help us orient, such as the OM. Callback conversation with reporter revealed the following information: the reporter is an first officer on the B-737-200. Since this report, he has flown into las several times from the east. TRACON and center give several heading changes approaching las but never seem to give directions until close in that the headings may be for the localizer. The reporter is accepting open ended vectors. Of course, there have been no repercussions regarding this incident.

Original NASA ASRS Text

Title: POSSIBLE TRACK DEV.

Narrative: ON A FLT FROM DEN TO LAS, WE CROSSED OVER HANKSVILLE VOR. INSTEAD OF THE FLT PLAN ARR (STAR) TO LAS, WE WERE GIVEN A HDG TO INTERCEPT THE LOC INBOUND TO LAS. WE WERE ON OUR SECOND FLT INTO LAS IN OUR RESPECTIVE CAREERS, SO WE WERE NEW TO THE AREA. AS WE APCHED LAS, WE WERE ASSIGNED NEW HDGS. WE CHKED ON WITH APCH AND, AS EXPECTED, THE FREQ WAS BUSY. WE FLEW OUR HDG AND FLEW PAST THE LOC. AS WE WENT TO QUERY THE CTLR, HE ASKED IF WE SHOULD HAVE INTERCEPTED. WE WERE ASSIGNED A NEW HDG TO INTERCEPT. BEING UNFAMILIAR WITH THE AREA MADE IT DIFFICULT TO JUDGE WHERE AND WHEN TO EXPECT OUR INTERCEPTION TO OCCUR. THE BUSY FREQ ALSO MADE IT DIFFICULT TO QUERY THE CTLR. THERE WAS NO ADF TO HELP US ORIENT, SUCH AS THE OM. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: THE RPTR IS AN FO ON THE B-737-200. SINCE THIS RPT, HE HAS FLOWN INTO LAS SEVERAL TIMES FROM THE E. TRACON AND CTR GIVE SEVERAL HDG CHANGES APCHING LAS BUT NEVER SEEM TO GIVE DIRECTIONS UNTIL CLOSE IN THAT THE HDGS MAY BE FOR THE LOC. THE RPTR IS ACCEPTING OPEN ENDED VECTORS. OF COURSE, THERE HAVE BEEN NO REPERCUSSIONS REGARDING THIS INCIDENT.

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.