Narrative:

While flying a RNAV (GPS) runway 29 approach; I incorrectly identified the runway as runway 22 when calling my distance and altitude on the CTAF. When the close encounter occurred; I was VFR looking at the runway because I was below the visual descent point. Another aircraft was on short final for runway 22 at the same time I was on short final for runway 29. The runways almost intersect at the threshold of each runway with runway 22 glidepath 100 ft. Above the threshold of runway 29. The other aircraft passed ahead and above me while I was on short final for runway 29.I reported on the CTAF that I had the other aircraft in sight and I announced that I was short final for runway 29 and not runway 22. In addition to the landing aircraft; one other aircraft in the traffic pattern was calling its position for runway 22 during my approach to runway 29. I mis-stated my position as being on approach for runway 22 on one other occasion during the final approach phase. The problem was a close encounter of two aircraft approaching intersecting runway glidepaths near the thresholds at the same time. Contributing to the problem was my mis-identification of the runway I was approaching. This created confusion and surprise to the pilot of the other aircraft. To prevent recurrence; I need to check the approach more carefully and correctly identify the runway. My focus on managing the approach when on instruments while hearing other aircraft identify runway 22 in their callouts; distracted me from identifying the correct runway I was approaching as runway 29 and not runway 22.

Related reports:

Google
 

Original NASA ASRS Text

Title: C182 pilot reported a NMAC at a non towered airport.

Narrative: While flying a RNAV (GPS) Runway 29 Approach; I incorrectly identified the runway as Runway 22 when calling my distance and altitude on the CTAF. When the close encounter occurred; I was VFR looking at the runway because I was below the Visual Descent Point. Another aircraft was on short final for Runway 22 at the same time I was on short final for Runway 29. The runways almost intersect at the threshold of each runway with Runway 22 glidepath 100 ft. above the threshold of Runway 29. The other aircraft passed ahead and above me while I was on short final for Runway 29.I reported on the CTAF that I had the other aircraft in sight and I announced that I was short final for Runway 29 and not Runway 22. In addition to the landing aircraft; one other aircraft in the traffic pattern was calling its position for Runway 22 during my approach to Runway 29. I mis-stated my position as being on approach for Runway 22 on one other occasion during the final approach phase. The problem was a close encounter of two aircraft approaching intersecting runway glidepaths near the thresholds at the same time. Contributing to the problem was my mis-identification of the runway I was approaching. This created confusion and surprise to the pilot of the other aircraft. To prevent recurrence; I need to check the approach more carefully and correctly identify the runway. My focus on managing the approach when on instruments while hearing other aircraft identify Runway 22 in their callouts; distracted me from identifying the correct runway I was approaching as Runway 29 and not Runway 22.

Data retrieved from NASA's ASRS site 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.