GA pilot reported confusing taxiway markings due to a runway closure resulted in taxiing onto a runw...

Narrative:

Upon landing avq; I was able to exit A3 to assist traffic flow. There were six plus aircraft behind me and three on ground awaiting departure. Because runway 3/21 was notamed closed and the parking area near the [FBO] was under construction numerous taxiways were closed. Upon taxiing south on a; the crossing of runway 3/21 was barricaded and the sign said turn right for FBO. Upon turning right and taxiing west on an uncharted taxiway for runway 3 I came upon another barricade. At that point I advised the rest of our group that they should not exit at A3 but plan to stay on runway 12 all the way to A2. I proceeded to taxi back east bound and announced that I would have to taxi on runway 12 in order to exit at A2. As I entered runway 12 I noticed another aircraft appeared near or on runway 12 but stopped or taxiing slowly; it appeared to be taxiing slowly on runway 12 heading for A2. The aircraft apparently made no announcements. After I was on runway 12; the pilot of that aircraft suddenly started shouting (cursing) on the radio that they were taking off. The aircraft passed directly over my aircraft even though I was on the right side of the runway.the major cause of this situation is due to the inaccurate and improper signs and barricades provided by the airport operations. As we prepared to leave a friend had gone into the FBO to get a suggested taxi plan to runway 12. It requires taxiing from the parking area to cross runway 12 at A2 to taxiway for runway 21 then taxiing around the obstacles blocking runway 21 (closed) then again crossing runway 12 to reach a then taxiing north on a to departure on runway 12. The other thing should involve communication. From my vantage I probably should have confirmed that the other aircraft; who did not announce; what his intentions were. It is possible that he was locally based and just entered the runway 12 from the hangars near A3; perhaps stop and go; or IFR approach practice. Certainly any aircraft should have lifted off and since we were on the right side of a runway 100 foot wide he did not have to fly directly over me.

Original NASA ASRS Text

Title: GA pilot reported confusing taxiway markings due to a runway closure resulted in taxiing onto a runway another aircraft was taking off from at AVQ airport.

Narrative: Upon landing AVQ; I was able to exit A3 to assist traffic flow. There were six plus aircraft behind me and three on ground awaiting departure. Because Runway 3/21 was NOTAMed closed and the parking area near the [FBO] was under construction numerous taxiways were closed. Upon taxiing south on A; the crossing of Runway 3/21 was barricaded and the sign said turn right for FBO. Upon turning right and taxiing west on an uncharted taxiway for Runway 3 I came upon another barricade. At that point I advised the rest of our group that they should not exit at A3 but plan to stay on Runway 12 all the way to A2. I proceeded to taxi back east bound and announced that I would have to taxi on Runway 12 in order to exit at A2. As I entered Runway 12 I noticed another aircraft appeared near or on Runway 12 but stopped or taxiing slowly; it appeared to be taxiing slowly on Runway 12 heading for A2. The aircraft apparently made no announcements. After I was on Runway 12; the pilot of that aircraft suddenly started shouting (cursing) on the radio that they were taking off. The aircraft passed directly over my aircraft even though I was on the right side of the runway.The major cause of this situation is due to the inaccurate and improper signs and barricades provided by the airport operations. As we prepared to leave a friend had gone into the FBO to get a suggested taxi plan to Runway 12. It requires taxiing from the parking area to cross Runway 12 at A2 to taxiway for Runway 21 then taxiing around the obstacles blocking Runway 21 (closed) then again crossing Runway 12 to reach A then taxiing north on A to departure on Runway 12. The other thing should involve communication. From my vantage I probably should have confirmed that the other aircraft; who did not announce; what his intentions were. It is possible that he was locally based and just entered the Runway 12 from the hangars near A3; perhaps stop and go; or IFR approach practice. Certainly any aircraft should have lifted off and since we were on the right side of a runway 100 foot wide he did not have to fly directly over me.

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	1641053
Time
Date	201904
Local Time Of Day	0601-1200
Place
Locale Reference	AVQ.Airport
State Reference	AZ
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Make Model Name	Small Aircraft
Operating Under FAR Part	Part 91
Flight Phase	Taxi
Flight Plan	VFR
Aircraft 2
Make Model Name	Small Aircraft
Operating Under FAR Part	Part 91
Flight Phase	Takeoff
Person 1
Function	Pilot Flying Single Pilot
Qualification	Flight Crew Commercial Flight Crew Flight Instructor Flight Crew Instrument
Experience	Flight Crew Last 90 Days 15 Flight Crew Total 5000 Flight Crew Type 800
Events
Anomaly	Conflict Ground Conflict Less Severe Deviation - Procedural Published Material / Policy Ground Incursion Runway
Miss Distance	Vertical 100

GA pilot reported confusing taxiway markings due to a runway closure resulted in taxiing onto a runway another aircraft was taking off from at avq airport.