Boi approach controller reported of an unsafe situation when one aircraft did not have the same rout...

Attributes
ACN	1397509
Time
Date	201610
Local Time Of Day	1801-2400
Place
Locale Reference	BOI.TRACON
State Reference	ID
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Make Model Name	Medium Large Transport
Operating Under FAR Part	Part 121
Flight Phase	Initial Approach
Route In Use	Other RNAV Z Runway 10R STAR BEWTE2
Flight Plan	IFR
Aircraft 2
Make Model Name	Medium Large Transport
Operating Under FAR Part	Part 121
Flight Phase	Initial Approach
Route In Use	Vectors Visual Approach
Flight Plan	IFR
Person 1
Function	Approach
Qualification	Air Traffic Control Fully Certified
Experience	Air Traffic Control Time Certified In Pos 1 (yrs) 19
Events
Anomaly	ATC Issue All Types Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types

Narrative:

Aircraft X was inbound from the northwest on the BEWTE2 arrival (STAR). Requested and was issued the rvav (rnp) Z to runway 10R. This arrival transitions from the fixes libby to camml to onexe. Arrival descends to 4500. Aircraft Y inbound from the west descending to 6000 approximately 10 miles behind the flight path of aircraft X. Aircraft Y had aircraft X in sight and was instructed to maintain visual separation and given the visual approach to runway 10L. Pilot acknowledged the instruction. I noticed aircraft X was west of his expected course and appeared to be proceeding to the fix jimmi which is not on that leg of the approach but is part of the approach from the west. I canceled the approach clearance and issued an altitude of 5000. Aircraft X was now southbound crossing the final approach course and requested a right 270 back to final for the visual approach. This was given as requested. By this time aircraft Y had passed over the top of aircraft X and was not a factor. At this time I advised the pilot that our charts showed that he should have flown libby; camml; onexe and then inbound. He stated that is not what his chart showed. I do not have access to the jeppesen charts so I have no way of researching this but I will bring it to the attention of our quality assurance office. At no time was there a loss of standard separation.check the charts that [company] is using to verify they are the same we have available on our nids (national information display system).

Original NASA ASRS Text

Title: BOI Approach Controller reported of an unsafe situation when one aircraft did not have the same routing as the Controller did. The pilot turned unexpectedly on a different route than the Controller was expecting.

Narrative: Aircraft X was inbound from the Northwest on the BEWTE2 arrival (STAR). Requested and was issued the RVAV (RNP) Z to Runway 10R. This arrival transitions from the fixes LIBBY to CAMML to ONEXE. Arrival descends to 4500. Aircraft Y inbound from the West descending to 6000 approximately 10 miles behind the flight path of Aircraft X. Aircraft Y had Aircraft X in sight and was instructed to maintain visual separation and given the visual approach to Runway 10L. Pilot acknowledged the instruction. I noticed Aircraft X was west of his expected course and appeared to be proceeding to the fix JIMMI which is not on that leg of the approach but is part of the approach from the West. I canceled the approach clearance and issued an altitude of 5000. Aircraft X was now southbound crossing the final approach course and requested a right 270 back to final for the visual approach. This was given as requested. By this time Aircraft Y had passed over the top of Aircraft X and was not a factor. At this time I advised the pilot that our charts showed that he should have flown LIBBY; CAMML; ONEXE and then inbound. He stated that is not what his chart showed. I do not have access to the Jeppesen charts so I have no way of researching this but I will bring it to the attention of our Quality Assurance office. At no time was there a loss of standard separation.Check the charts that [Company] is using to verify they are the same we have available on our NIDS (National Information Display System).

Data retrieved from NASA's ASRS site 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.

Boi approach controller reported of an unsafe situation when one aircraft did not have the same routing as the controller did. The pilot turned unexpectedly on a different route than the controller was expecting.