Flight Crew Private
Communication Breakdown; Situational Awareness; Time Pressure
Conflict Airborne Conflict; Deviation / Discrepancy - Procedural Published Material / Policy
Flight Crew Became Reoriented; Flight Crew Took Evasive Action
Aircraft; Airport; Procedure; Environment - Non Weather Related
After run-up; I requested 'St George traffic; how do you read me.' No response heard. I stated intentions for immediate takeoff and intended route of flight to the east of airport for maneuvering. After clearing for incoming traffic; I proceeded onto Runway 19 and initiated an immediate departure. No other aircraft were in the pattern at the time. At lift off (about 450 ft. down runway) Pilot noticed large aircraft landing lights at far end of Runway 01 (approximately 8;500 ft. away) and made an immediate turn to left at about 300 ft. altitude and 600 ft. east of runway then proceeded south along Runway 19/01 gaining altitude at about 1;000 ft. per minute. Communications were established with aircraft located near the opposite end of runway. The large aircraft then proceeded to the next taxiway and returned to the run-up area to reinitiate its normal departure procedure. Communications were maintained between both aircraft after my departure. This does not mean that the large aircraft did not communicate its intention; but rather that the departing air craft did not receive the communication.Moral of story: Pilot of small aircraft should look both ways before taking the 'active runway' especially in no wind conditions at non-towered airports.
A solo pilot made his CTAF communications before departing SGU then after takeoff noticed a large aircraft taxiing off the far end of the runway. He had not heard a response from that aircraft which apparently did not hear him either.