Flight Crew Sport / Recreational
Flight Crew Last 90 Days 45; Flight Crew Total 98; Flight Crew Type 96
Communication Breakdown; Situational Awareness
Conflict NMAC; Deviation / Discrepancy - Procedural Published Material / Policy
Flight Crew Took Evasive Action
After refueling I was taxiing for departure on runway 18. After viewing the windsock; I made a subsequent transmission on CTAF that I was changing to depart on runway 36. I held short of 36 while conducting a run-up; and then announced on CTAF that I was departing on runway 36. I conducted a scan of both directions of the runway for approaching traffic. Seeing no traffic; I entered runway 36 and commenced my takeoff roll. Just prior to rotation; a crop duster turned onto final for landing on runway 18. I heard no radio calls on CTAF from the aircraft. The aircraft maintained its course for far too long for my comfort. Immediately after rotation I veered right. The other aircraft conducted a go around; and landed on runway 36. I did not observe the tail number. My ADS-B receiver did not indicate the aircraft.I confirmed that the CTAF I had entered was correct. My radio was functioning correctly throughout my flight. I noted that the pilot lounge had a sign admonishing pilots to use the CTAF. The other aircraft did not respond to my subsequent radio calls. I can only assume that they did not use a radio. I did scan the approach for both runway 18 and runway 36. I did not scan the downwind legs for each pattern (left traffic for 18 was in the sun). I did not hear an aircraft in the vicinity prior to starting my engine. It is possible that a more thorough scan of the pattern may have located the other plane.
A general aviation pilot reported a near mid-air-collision during takeoff with an opposite direction landing crop duster that was not communicating on the CTAF.