A corporate crew on the sna elb 1 was issued an off route clearance after bolde to avoid a conflict ...

Narrative:

I was assigned sector 12 for approximately 50 minutes I was given several tmu reroutes over this course of time; two had already been issued prior to this event. The air carrier was a point out from sector 21 and I was climbing a corporate jet reference the air carrier. I issued a reroute clearance for the corporate aircraft that would de conflict with the air carrier via a route change. I issued to the corporate aircraft after bolde intersection ipl.J2.gbn.elp rest of route. The pilot readback as such and I continued his climb seeing that he was no longer in conflict with the air carrier. Unfortunately after bolde intersection he continued on the ELB1 departure which brought the aircraft back in conflict with the air carrier. The closest proximity appeared to be 5.33 miles at the same altitude. After the next sector had de-conflicted the aircraft once again we asked what the pilot was issued the pilot readback as first instructed. Upon looking at the ELB1 departure there is another fix called baldi intersection that sounded similar to bolde which was further down on the departure. The corporate aircraft took the bolde intersection as 'baldi' and inputted the route change after baldi.I had given this reroute twice before this corporate aircraft and both aircraft had taken the correct intersection as stated. I don't believe there was an issue with the hear-back/readback as the pilot had pronounced it correctly. I would recommend that either the bolde or baldi intersection be renamed to de-conflict the similarity of the name; especially both are on the same departure.

Original NASA ASRS Text

Title: A corporate crew on the SNA ELB 1 was issued an off route clearance after BOLDE to avoid a conflict with an air carrier; but the corporate crew remained on the ELB 1 track recreating the conflict. There may have been confusion between BALDI and BOLDE intersections; 45 miles apart on the ELB 1 SID.

Narrative: I was assigned Sector 12 for approximately 50 minutes I was given several TMU reroutes over this course of time; two had already been issued prior to this event. The air carrier was a point out from Sector 21 and I was climbing a corporate jet reference the air carrier. I issued a reroute clearance for the corporate aircraft that would de conflict with the air carrier via a route change. I issued to the corporate aircraft after BOLDE Intersection IPL.J2.GBN.ELP rest of route. The pilot readback as such and I continued his climb seeing that he was no longer in conflict with the air carrier. Unfortunately after BOLDE Intersection he continued on the ELB1 departure which brought the aircraft back in conflict with the air carrier. The closest proximity appeared to be 5.33 miles at the same altitude. After the next sector had de-conflicted the aircraft once again we asked what the pilot was issued the pilot readback as first instructed. Upon looking at the ELB1 departure there is another fix called BALDI Intersection that sounded similar to BOLDE which was further down on the departure. The corporate aircraft took the BOLDE Intersection as 'BALDI' and inputted the route change after BALDI.I had given this reroute twice before this corporate aircraft and both aircraft had taken the correct intersection as stated. I don't believe there was an issue with the hear-back/readback as the pilot had pronounced it correctly. I would recommend that either the BOLDE or BALDI Intersection be renamed to de-conflict the similarity of the name; especially both are on the same departure.

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.

Attributes
ACN	1141600
Time
Date	201401
Local Time Of Day	1201-1800
Place
Locale Reference	SNA.Airport
State Reference	CA
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Make Model Name	Medium Transport Low Wing 2 Turbojet Eng
Operating Under FAR Part	Part 91
Flight Phase	Climb
Route In Use	SID ELB 1
Flight Plan	IFR
Aircraft 2
Make Model Name	Commercial Fixed Wing
Operating Under FAR Part	Part 121
Flight Phase	Climb
Route In Use	SID IMPER 1
Flight Plan	IFR
Component
Aircraft Component	FMS/FMC
Person 1
Function	Enroute
Qualification	Air Traffic Control Fully Certified
Events
Anomaly	ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Clearance Deviation - Track / Heading All Types

A corporate crew on the sna elb 1 was issued an off route clearance after bolde to avoid a conflict with an air carrier; but the corporate crew remained on the elb 1 track recreating the conflict. There may have been confusion between baldi and bolde intersections; 45 miles apart on the elb 1 SID.