Narrative:

Aircraft #1 was cleared by ZJX for a VOR approach to allendale county airport (88J) at approximately XA20 EST; and ZJX advised that there were no aircraft in the allendale (ald) VOR area. Aircraft #1 reported to ZJX over ald VOR and proceeded outbound on 320 degree radial for approximately 2 minutes (descending from 3;000 ft to 2;000 ft). Aircraft #1 reversed course with a procedure turn (as published) and proceeded inbound to the VOR on 320 degree radial (140 degrees magnetic course) and continued descent to 1;100 ft. Aircraft #1 announced all turns on CTAF 122.8 to allendale traffic. Aircraft #1 heard no responses from other traffic. (However; later; on short final approach; it was evident that aircraft #1's receiver had gone out intermittently. Apparently; during the 'reverse course procedure turn' of aircraft #1; aircraft #2 had come into the traffic pattern area and was setting up a landing approach to runway 35 and allendale (88J). Aircraft #1 would not see aircraft #2 or another 'unknown' aircraft that had just landed on runway 35 at allendale (88J). Aircraft #2 and unknown aircraft might have called to announce their positions/intentions; but aircraft #1 did not receive the transmissions due to temporary receiver failure. Aircraft #1 made a low approach to 88J and announced on CTAF that it was starting a left circling approach to runway 17. During aircraft #1's left circling approach; no traffic was visible due to the 'blind 6 O'clock position.' it was only on short final/touchdown on runway 17 that aircraft #1 saw aircraft #2 on final approach to runway 35. (Aircraft #2 was approximately 1/2 mile on final approach at approximately 400 ft altitude). Aircraft #1 immediately announced that aircraft #1 was on short final/touchdown on runway 17 and that aircraft #2 should 'go around.' at that instant; aircraft #1's receiver started working (probably due to aircraft #1's landing and activating the 'short circuit' suspected in aircraft #1's receiver). Aircraft #2 made a go around and there was no longer an unsafe scenario. Aircraft #1 advised aircraft #2 that aircraft #1's receiver just started working. It appeared that aircraft #2 (upon realizing that aircraft #1 was not responding to traffic calls) should have executed a go around sooner. Aircraft #1 pilot discussed the event with aircraft #2 pilot on the ramp after the flight

Google
 

Original NASA ASRS Text

Title: Following a non-precision circling approach to 88J; pilot of a small aircraft experiences NMAC with aircraft landing opposite direction on the same runway.

Narrative: Aircraft #1 was cleared by ZJX for a VOR approach to Allendale County Airport (88J) at approximately XA20 EST; and ZJX advised that there were no aircraft in the Allendale (ALD) VOR area. Aircraft #1 reported to ZJX over ALD VOR and proceeded outbound on 320 degree radial for approximately 2 minutes (descending from 3;000 FT to 2;000 FT). Aircraft #1 reversed course with a procedure turn (as published) and proceeded inbound to the VOR on 320 degree radial (140 degrees magnetic course) and continued descent to 1;100 FT. Aircraft #1 announced all turns on CTAF 122.8 to Allendale traffic. Aircraft #1 heard no responses from other traffic. (However; later; on short final approach; it was evident that Aircraft #1's receiver had gone out intermittently. Apparently; during the 'reverse course procedure turn' of Aircraft #1; Aircraft #2 had come into the traffic pattern area and was setting up a landing approach to Runway 35 and Allendale (88J). Aircraft #1 would not see Aircraft #2 or another 'unknown' aircraft that had just landed on Runway 35 at Allendale (88J). Aircraft #2 and unknown aircraft might have called to announce their positions/intentions; but Aircraft #1 did not receive the transmissions due to temporary receiver failure. Aircraft #1 made a low approach to 88J and announced on CTAF that it was starting a left circling approach to Runway 17. During Aircraft #1's left circling approach; no traffic was visible due to the 'blind 6 O'clock position.' It was only on short final/touchdown on Runway 17 that Aircraft #1 saw Aircraft #2 on final approach to Runway 35. (Aircraft #2 was approximately 1/2 mile on final approach at approximately 400 FT altitude). Aircraft #1 immediately announced that Aircraft #1 was on short final/touchdown on Runway 17 and that Aircraft #2 should 'go around.' At that instant; Aircraft #1's receiver started working (probably due to Aircraft #1's landing and activating the 'short circuit' suspected in Aircraft #1's receiver). Aircraft #2 made a go around and there was no longer an unsafe scenario. Aircraft #1 advised Aircraft #2 that Aircraft #1's receiver just started working. It appeared that Aircraft #2 (upon realizing that Aircraft #1 was not responding to traffic calls) should have executed a go around sooner. Aircraft #1 pilot discussed the event with Aircraft #2 pilot on the ramp after the flight

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.