Date: 201911
Local time of day: 0601-1200
Location: TEB.Airport, NJ
Flight conditions: VMC
Light: Daylight
Aircraft: Small Aircraft
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Personal
Flight phase: Final Approach
Airspace: Class D TEB
ATC / advisory: TRACON N90; Tower TEB
Second aircraft: Medium Transport
Reporter organization: Government
Reporter function: Approach
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Confusion; Situational Awareness; Communication Breakdown
Second reporter function: Pilot Flying; Single Pilot
Anomaly: ATC Issue All Types; Conflict Airborne Conflict; Deviation - Altitude Excursion From Assigned Altitude; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Air Traffic Control Separated Traffic; Air Traffic Control Issued New Clearance; Flight Crew Became Reoriented
Contributing factors: Airspace Structure; Procedure; Human Factors
Primary problem: Human Factors

Narrative: Aircraft X was cleared for ILS 6 approach to TEB. Shortly after; I noticed him go through the localizer and called the Tower to give instructions to rejoin approach. At the same time I received a low altitude alert and told the Tower. I called Tower to alert them because it appeared to me he might be heading toward their airport. Shortly after it appeared he was turning west bound towards Aircraft Y and at some point I heard the Tower say over the shout line that he wasn't following instructions. I turned Aircraft Y northwest to try to get away from Aircraft X. To me it looked like Aircraft X was headed right at Aircraft Y so I climbed Aircraft Y to 3;000 feet since I told Tower to have Aircraft X climb to 2;000 feet. This vector brought Aircraft Y into conflict with Aircraft Z. Once it appeared Aircraft Y and Aircraft X were no longer a factor I turned Aircraft Y back to a 340 heading away from Aircraft Z. Separation was re-established between all Aircraft and they were re-sequenced to the airport.If Aircraft X had flown the approach as cleared or been issued the 030 heading to rejoin that I initially issued to the Tower; this would have never happened. I was worried about Aircraft Y and Aircraft X hitting which caused me to turn Aircraft Y into Aircraft Z. In hindsight I could have probably used less of a turn for Aircraft Y so that I would have at least had divergence with Aircraft Z; but at the time was more concerned about Aircraft Y and Aircraft X actually hitting that the loss of separation with Aircraft Z seemed less critical so I can't say I wouldn't do the same thing in the future. As I discussed with my supervisor after the incident the one thing I would do differently is not ship Aircraft X to the Tower so soon. It may not have prevented the incident but may have helped make it easier to control if I didn't have to coordinate with the Tower and was directly talking to the aircraft.


Second narrative: I was cleared for the approach for Runway 06 in TEB. I had the incorrect localizer frequency in my GPS and thought I had the airport visually but saw the incorrect airport. I was given a heading to hold and a new altitude. I followed air traffic's new headings and altitudes and realized the wrong frequency was in. I put the correct frequency in and was re-cleared for the approach. During this there was a near miss and another aircraft had to circle to re-shoot his approach. When I landed; Tower asked me to call the TRACON which I did and a report was filed for this incident. It was VFR conditions and I should have double checked frequency before thinking I had the field since there are so many airports close by TEB.


Synopsis: N90 TRACON Controller and pilot reported the pilot flew through approach course and towards another aircraft before pilot was reoriented and communications restored.