Skyhawk 172/Cutlass 172
Flight Crew Private
Flight Crew Last 90 Days 45; Flight Crew Total 555; Flight Crew Type 555
Communication Breakdown
Conflict Ground Conflict; Critical; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Incursion Runway
Flight Crew Took Evasive Action; Flight Crew Rejected Takeoff
Procedure; Human Factors; Aircraft
I and my instructor had completed run-up at Runway 12 and announced our roll on Runway 12 with left crosswind departure. All traffic; including an inbound jet at about 6 nm northwest were using or planning to use Runway 12. Once we were rolling on Runway 12; Aircraft Y that had not yet been on frequency; announced 4 mile final straight in for Runway 30 (note that Runway 12 is the calm-wind runway; and the wind was calm). I presume Aircraft Y had been with TUS TRACON until that time; then switched to advisory and announced intentions without taking existing traffic at AVQ into account. I aborted my takeoff roll on Runway 12 and announced that I would return to the run-up area for Runway 12 (back-taxi; since that was the quickest option to clear the runway from where I was). Once on the ground on Runway 30; Aircraft Y announced 'clear of 30' while still rolling on the runway. I am convinced that my action to abort takeoff might have prevented an accident. I am also convinced that the pilot of Aircraft Y either did not fully appreciate the situation or was operating under the belief that being in a fast jet exempted him from following proper procedures. Related to this; AVQ is an accident waiting to happen; especially during this week every year when the pattern is loaded with corporate jets for an annual event. AVQ needs a tower; or at a minimum a temporary tower during special events.
C172 Pilot reported that an aircraft announcing final in the opposite direction resulted in a rejected takeoff and evasive action.