Narrative:

Upon returning using class C services; I was cleared to advisory frequency for hampton roads executive airport. I called seven KM to the northwest of pvg at 2500'msl requesting advisories. I made another radio call over the field making my intentions to enter the traffic pattern for runway 20 (winds were 150/08) known. I noticed on my garmin 430 tis; traffic approximately four NM to the west at the same altitude. I descended to 1500' MSL; then to 1000' MSL because it appeared we were at the same altitude on a converging heading from my right. At this time I had visual contact of the impending traffic now 500' above me. I flew underneath the aircraft; then shortly thereafter; turned to enter into the pattern at pvg. I also made another call stating I was maneuvering for the traffic pattern entry; but didn't hear anything from the other plane; so I assumed they were not monitoring pvg CTAF frequency. When I completed the turn to the 45 degree leg; I noticed that the aircraft turning back into me at approximately the same altitude. It appeared the conflicting traffic changed his heading from east to west while we were in our turn to enter the pattern. I took evasive action in order to avoid the collision. Immediately following the maneuver was the first time I heard the other aircraft make a call on the CTAF frequency stating they were over the landfill just to the west of the airfield. It was never clear to me what the other aircraft's intentions were. If the conflicting traffic made other radio calls identifying itself and intentions much of the problem could have been solved. That pilot should have entered the traffic pattern from the west; rather than continuing to the east until too close to the airfield; then turning back to the west for pattern entry.

Google
 

Original NASA ASRS Text

Title: A Pilot made normal traffic pattern CTAF reports approaching PVG but had a NMAC with another aircraft approaching the airport in a non standard manner that was not making traffic reports.

Narrative: Upon returning using Class C Services; I was cleared to Advisory Frequency for Hampton Roads Executive Airport. I called seven KM to the NW of PVG at 2500'MSL requesting advisories. I made another radio call over the field making my intentions to enter the traffic pattern for Runway 20 (Winds were 150/08) known. I noticed on my Garmin 430 TIS; traffic approximately four NM to the west at the same altitude. I descended to 1500' MSL; then to 1000' MSL because it appeared we were at the same altitude on a converging heading from my right. At this time I had visual contact of the impending traffic now 500' above me. I flew underneath the aircraft; then shortly thereafter; turned to enter into the pattern at PVG. I also made another call stating I was maneuvering for the traffic pattern entry; but didn't hear anything from the other plane; so I assumed they were not monitoring PVG CTAF frequency. When I completed the turn to the 45 degree leg; I noticed that the aircraft turning back into me at approximately the same altitude. It appeared the conflicting traffic changed his heading from east to west while we were in our turn to enter the pattern. I took evasive action in order to avoid the collision. Immediately following the maneuver was the first time I heard the other aircraft make a call on the CTAF frequency stating they were over the landfill just to the west of the airfield. It was never clear to me what the other aircraft's intentions were. If the conflicting traffic made other radio calls identifying itself and intentions much of the problem could have been solved. That Pilot should have entered the traffic pattern from the west; rather than continuing to the east until too close to the airfield; then turning back to the west for pattern entry.

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.