A light aircraft pilot reported using the wrong frequency for traffic advisories and then experienci...

Narrative:

I was flying VFR down the hudson VFR corridor for personal sightseeing. I had taken off from teb and was receiving flight following and traffic advisories with teb tower while simultaneously listening and self-announcing on hudson VFR corridor unicom. However; in rush of frequency changes and rapid departure from teb had incorrectly entered 123.075 instead of 123.05 in my COM2. I did not notice that I was broadcasting position reports on the east river frequency as I also had teb tuned and the frequency was congested. I made all position reports on the wrong frequency for about 5 minutes. I was keeping a good look out; following all other rules of the corridor and monitoring my traffic advisory system closely. After turning 180 degrees around the statue of liberty and heading back northbound; I came within about 200-300 feet vertically and laterally of a helicopter. I saw him with plenty of time and turned to build more separation. With good visual tracking there was no real fear of collision (nor would we have come very close without avoidance) but it was closer than I would have liked. A few seconds later another airplane warned that I was on 123.075 instead of 123.05. I promptly switched frequency and started making calls on the correct frequency. I kicked myself for not looking at the tac chart more closely and will pay more attention in the future.

Original NASA ASRS Text

Title: A light aircraft pilot reported using the wrong frequency for traffic advisories and then experiencing an NMAC in the Hudson River corridor.

Narrative: I was flying VFR down the Hudson VFR corridor for personal sightseeing. I had taken off from TEB and was receiving flight following and traffic advisories with TEB Tower while simultaneously listening and self-announcing on Hudson VFR corridor Unicom. However; in rush of frequency changes and rapid departure from TEB had incorrectly entered 123.075 instead of 123.05 in my COM2. I did not notice that I was broadcasting position reports on the East river frequency as I also had TEB tuned and the frequency was congested. I made all position reports on the wrong frequency for about 5 minutes. I was keeping a good look out; following all other rules of the corridor and monitoring my traffic advisory system closely. After turning 180 degrees around the Statue of Liberty and heading back northbound; I came within about 200-300 feet vertically and laterally of a helicopter. I saw him with plenty of time and turned to build more separation. With good visual tracking there was no real fear of collision (nor would we have come very close without avoidance) but it was closer than I would have liked. A few seconds later another airplane warned that I was on 123.075 instead of 123.05. I promptly switched frequency and started making calls on the correct frequency. I kicked myself for not looking at the TAC chart more closely and will pay more attention in the future.

Data retrieved from NASA's ASRS site as of April 2012 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	859312
Time
Date	200911
Place
Locale Reference	TEB.Airport
State Reference	NJ
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Make Model Name	Small Aircraft Low Wing 1 Eng Fixed Gear
Operating Under FAR Part	Part 91
Flight Phase	Cruise
Route In Use	None
Flight Plan	None
Person 1
Function	Pilot Flying Single Pilot
Qualification	Flight Crew Instrument Flight Crew Private
Experience	Flight Crew Last 90 Days 55 Flight Crew Total 550 Flight Crew Type 340
Events
Anomaly	Conflict NMAC Deviation - Procedural Published Material / Policy
Miss Distance	Horizontal 300 Vertical 200

A light aircraft pilot reported using the wrong frequency for traffic advisories and then experiencing an near midair collision in the hudson river corridor.