C172 pilot reported that an aircraft announcing final in the opposite direction resulted in a reject...

Narrative:

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.

Original NASA ASRS Text

Title: C172 Pilot reported that an aircraft announcing final in the opposite direction resulted in a rejected takeoff and evasive action.

Narrative: 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.

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.

Attributes
ACN	1700541
Time
Date	201911
Place
Locale Reference	AVQ.Airport
State Reference	AZ
Aircraft 1
Make Model Name	Skyhawk 172/Cutlass 172
Operating Under FAR Part	Part 91
Flight Phase	Takeoff
Flight Plan	None
Aircraft 2
Make Model Name	Gulfstream Jet Undifferentiated or Other Model
Flight Phase	Landing
Flight Plan	IFR
Person 1
Function	Single Pilot
Qualification	Flight Crew Private
Experience	Flight Crew Last 90 Days 45 Flight Crew Total 555 Flight Crew Type 555
Events
Anomaly	Conflict Ground Conflict Critical Deviation - Procedural Published Material / Policy Ground Incursion Runway

C172 pilot reported that an aircraft announcing final in the opposite direction resulted in a rejected takeoff and evasive action.