An air carrier aircraft flies through the localizer near ord when they had been told to intercept.

Attributes
ACN	430373
Time
Date	199903
Day	Wed
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : or3.airport
State Reference	IL
Altitude	msl single value : 14000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : c90.tracon
Operator	common carrier : air carrier
Make Model Name	Commercial Fixed Wing
Navigation In Use	ils localizer only : 32l
Flight Phase	descent : intermediate altitude
Route In Use	approach : instrument precision arrival : on vectors
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 200 flight time total : 12000 flight time type : 1000
ASRS Report	430373
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : commercial pilot : multi engine pilot : instrument
Events
Anomaly	non adherence : clearance other anomaly other other spatial deviation
Independent Detector	atc equipment other atc equipment : radar other controllera
Resolutory Action	controller : issued alert controller : issued new clearance
Supplementary
Problem Areas	Flight Crew Human Performance Environmental Factor Airspace Structure ATC Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

Approaching ord we received vectors for ord and the runway 32L localizer. The controller may have said, '...vectors for O'hare and to intercept the runway 32L localizer.' the first officer and I discussed the clearance and concluded that we were on vectors and not cleared to intercept the localizer. We both expected a further instruction to intercept the localizer. Conversation on the frequency was non stop and there was no opportunity to clarify our clearance prior to flying through the localizer. In addition, we observed a developing conflict with another aircraft and still were not able to communicate with approach due to frequency congestion. Next time: when I really need to talk to the controller and he is transmitting non stop, I will use the 'identify' feature on the transponder. I think it would be a great idea if this was adopted as a signal to 'call me.' also, I will henceforth clarify any vector for a localizer, with regard to intercept or not.

Original NASA ASRS Text

Title: AN ACR ACFT FLIES THROUGH THE LOC NEAR ORD WHEN THEY HAD BEEN TOLD TO INTERCEPT.

Narrative: APCHING ORD WE RECEIVED VECTORS FOR ORD AND THE RWY 32L LOC. THE CTLR MAY HAVE SAID, '...VECTORS FOR O'HARE AND TO INTERCEPT THE RWY 32L LOC.' THE FO AND I DISCUSSED THE CLRNC AND CONCLUDED THAT WE WERE ON VECTORS AND NOT CLRED TO INTERCEPT THE LOC. WE BOTH EXPECTED A FURTHER INSTRUCTION TO INTERCEPT THE LOC. CONVERSATION ON THE FREQ WAS NON STOP AND THERE WAS NO OPPORTUNITY TO CLARIFY OUR CLRNC PRIOR TO FLYING THROUGH THE LOC. IN ADDITION, WE OBSERVED A DEVELOPING CONFLICT WITH ANOTHER ACFT AND STILL WERE NOT ABLE TO COMMUNICATE WITH APCH DUE TO FREQ CONGESTION. NEXT TIME: WHEN I REALLY NEED TO TALK TO THE CTLR AND HE IS XMITTING NON STOP, I WILL USE THE 'IDENT' FEATURE ON THE XPONDER. I THINK IT WOULD BE A GREAT IDEA IF THIS WAS ADOPTED AS A SIGNAL TO 'CALL ME.' ALSO, I WILL HENCEFORTH CLARIFY ANY VECTOR FOR A LOC, WITH REGARD TO INTERCEPT OR NOT.

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.