Date: 201604
Local time of day: 1801-2400
Location: CNO.Airport, CA
Light: Night
Aircraft: Small Aircraft
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Personal
Flight phase: Initial Climb
Airspace: Class D CNO
ATC / advisory: Tower CNO
Second aircraft: Small Aircraft
Reporter organization: Government
Reporter function: Local
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Workload; Distraction; Confusion; Communication Breakdown; Situational Awareness
Anomaly: ATC Issue All Types; Conflict NMAC; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Clearance
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Took Evasive Action; Flight Crew Returned To Clearance
Contributing factors: Procedure; Human Factors
Primary problem: Procedure

Narrative: Aircraft Y called for departure and VFR squawk code to ZZZ at Runway 26L full length. I issued him the squawk; issued a cautionary wake turbulence call for a [larger aircraft] that had just departed and cleared him for takeoff. After doing so; Aircraft X called ready for departure at Runway 26R for a departure towards 'PRADO.' I observed Aircraft Y not moving and prompted him to begin his departure roll as I had previously cleared a PA28 to land on Runway 26L and the aircraft was turning a left base to a mile final. I told the Cherokee about Aircraft Y departing and to square his base to final turn for spacing purposes. I then went back to Aircraft X; and cleared him for takeoff stating that I would call his left turn on course. Throughout the next couple of minutes while the aircraft were departing; I was dealing with other clearances and traffic calls developing to the southeast for [a] jet inbound. I had expected Aircraft Y to turn left on course to ZZZ and then turn Aircraft X left on course behind Aircraft Y. Unknowingly to me Aircraft Y had made a slight turn to the WNW conflicting with Aircraft X departing the parallel; north runway. Aircraft Y; was not on his discrete beacon code I assigned him prior to takeoff and therefore no conflict alert sounded. Aircraft X alerted me that there was a NMAC approximately 30 seconds ago. I ensured Controller in Charge (CIC) heard what had happened. I observed Aircraft Y had overtaken Aircraft X on his WNW heading. I initially wanted to get Aircraft X away from Aircraft Y so I issued a right 270 degree turn southbound. The CIC told me to issue a left turn. I reluctantly amended my clearance and issued the left turn. I wanted to turn Aircraft X away from Aircraft Y's expected SW flight path. Instead I complied with CIC instructions and issued the left turn. I re-issued squawk code to Aircraft Y and instructed him to contact SCT. I queried Aircraft X about his Prado request. We have a VFR reporting point to the south called Prado Dam; which I assumed he was requesting. Aircraft X really wanted to go to the PRADO IFR navigation fix. Throughout all of this; numerous other operations were occurring creating blocked radio calls; adding to complexity.Change the name of IFR waypoint 'PRADO;' to avoid confusion with VFR reporting point.




Synopsis: CNO Tower Controller reported an NMAC when the Controller was expecting the first departure to turn southwest; but it actually turned WNW towards another departing aircraft.