A GA pilot at a non towered airport reported a NMAC with another aircraft in the pattern not communicating on CTAF.

Date: 2022-12 · Aircraft: Small Aircraft · Phase: approach

Anomalies: conflict-nmac

Synopsis

A GA pilot at a non towered airport reported a NMAC with another aircraft in the pattern not communicating on CTAF.

Narrative

Completed turn from base to final for Runway XX at ZZZ; when a Cessna 172 passed directly beneath me at less than 90 ft. estimated. Took evasive action to avoid collision. Upon landing discussed situation with the CFI and student; who claimed to not hear radio calls from me on CTAF. I stated that I heard no radio calls from them in the pattern; which they did not respond to. Both individuals stated that they didn't see me. Earlier I had heard occasional radio traffic from the C172; but they were inconsistent on position reporting.Approaching ZZZ I announced my position and landing intentions 10 miles out; and 3 miles out. I announced downwind leg; turn to base; and turn to final. Heard no radio traffic from other aircraft in the pattern at ZZZ; but clearly heard it from nearby airports sharing the same CTAF frequency. After taking evasive action to avoid the Cessna 172; I announced the deviation to avoid traffic on short final. I believe that if you have a radio in your aircraft; it is incumbent upon you to use it even at an uncontrolled airport. Announcing your position in the pattern is paramount to safety.

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.