Narrative:

While taxing to the end of runway 19 at kpwt (bremerton; wa) I observed a single engine (aircraft Y) taking off. This same aircraft was in the pattern and conducting (training) touch and go landings upon my arrival to kpwt 15 minutes earlier as I entered the traffic pattern behind this aircraft and landed to purchase fuel and then continue back out to my destination. I observed aircraft Y conduct at least three touch and go landings on runway 19 as I fueled my plane. During the approximate 15 minutes at kpwt I observed at least 4 other aircraft operating into and out of the airport. All aircraft were using the calm wind runway 19 with left traffic. I fueled up and taxied out to 19 for departure; I observed the same aircraft I originally landed behind continue to conduct touch and go landings as it once again took off from runway 19. I stopped short of the runway and performed a systems check and run-up and heard aircraft Y announce it was turning left upwind. After my systems check I observed aircraft Y turning the beginning phase of its left downwind at an estimated altitude of 700-800 ft AGL and 2 miles away. The single engine pilot or instructor then announced it was going to conduct a simulated engine failure to runway 19 which it was then turning a left downwind for. I was holding short of runway 19 and announced my intention to taxi into position for takeoff. I started to enter the runway end of 19 and the pilot or instructor of aircraft Y asked over the radio if I was going to takeoff? I replied with an affirmative and advised he was not a factor considering he was downwind for 19. He replied; 'we are conducting a simulated engine failure to runway 1'. I then replied that he originally announced that his simulation was going to be conducted to the active runway 19. He then turned left towards the runway end of runway 1 and asked if I was going to takeoff anyway? I replied no; I will pull back off the runway end. I turned my aircraft 90 degrees and started to leave the runway end of 19. He then announced he was going to go around. I observed him cross the runway end of runway 1 at an altitude of approximately 500 ft and turn right downwind for runway 19. I turned my aircraft back around and taxied back into position for takeoff on runway 19 and departed. This event could have been avoided for a number of reasons. Starting with the fact that 'reversing the traffic pattern for a simulation at an uncontrolled airport with multiple aircraft obviously operating from the already established active runway is not the safest thing to be doing'. In an emergency it makes perfect sense to get back to the runway anyway you can. However; conducting simulated engine failures back to a runway opposite of active traffic is a recipe for disaster unless you are positive you are the only aircraft using the airport. The other issue was communications. Aircraft Y pilot or what sounded like the instructor in this event; although both pilots were making calls which was confusing. The instructor was very hostile in his tone and really did not understand the confusion he created with his poor communication regarding which runway they were conducting their simulated engine failure too. This aircraft as well as other aircraft were conducting touch and go landings to runway 19 for at least 30 minutes or more prior to this brief event. Just making an announcement of your simulated intentions is not a clearance for priority over all other aircraft operating normally at an uncontrolled airport with the traffic pattern already 'established'. This aircraft which had just departed runway 19 for the 5th time apparently thought that his communications were 'heard by all' and feels that gave him priority to reverse the flow of traffic momentarily.

Related reports:

Google
 

Original NASA ASRS Text

Title: General aviation aircraft awaiting departure from PWT had a potential conflict when traffic in the pattern elected to simulate an opposite direction emergency landing requiring the reporter to taxi off the runway.

Narrative: While taxing to the end of Runway 19 at KPWT (Bremerton; WA) I observed a Single Engine (Aircraft Y) taking off. This same aircraft was in the pattern and conducting (Training) touch and go landings upon my arrival to KPWT 15 minutes earlier as I entered the traffic pattern behind this aircraft and landed to purchase fuel and then continue back out to my destination. I observed Aircraft Y conduct at least three touch and go landings on Runway 19 as I fueled my plane. During the approximate 15 minutes at KPWT I observed at least 4 other aircraft operating into and out of the airport. All aircraft were using the calm wind Runway 19 with left traffic. I fueled up and taxied out to 19 for departure; I observed the same Aircraft I originally landed behind continue to conduct touch and go landings as it once again took off from Runway 19. I stopped short of the Runway and performed a systems check and run-up and heard Aircraft Y announce it was turning left upwind. After my systems check I observed Aircraft Y turning the beginning phase of its left downwind at an estimated altitude of 700-800 FT AGL and 2 miles away. The Single Engine pilot or instructor then announced it was going to conduct a simulated engine failure to Runway 19 which it was then turning a left downwind for. I was holding short of Runway 19 and announced my intention to taxi into position for takeoff. I started to enter the Runway end of 19 and the pilot or instructor of Aircraft Y asked over the radio if I was going to takeoff? I replied with an affirmative and advised he was not a factor considering he was downwind for 19. He replied; 'We are conducting a simulated engine failure to Runway 1'. I then replied that he originally announced that his simulation was going to be conducted to the active Runway 19. He then turned left towards the Runway end of Runway 1 and asked if I was going to takeoff anyway? I replied no; I will pull back off the Runway end. I turned my Aircraft 90 degrees and started to leave the Runway end of 19. He then announced he was going to go around. I observed him cross the runway end of runway 1 at an altitude of approximately 500 FT and turn right downwind for Runway 19. I turned my aircraft back around and taxied back into position for takeoff on Runway 19 and departed. This event could have been avoided for a number of reasons. Starting with the fact that 'Reversing the traffic pattern for a simulation at an uncontrolled airport with multiple aircraft obviously operating from the already established active Runway is not the safest thing to be doing'. In an emergency it makes perfect sense to get back to the runway anyway you can. However; conducting simulated engine failures back to a runway opposite of active traffic is a recipe for disaster unless you are positive you are the ONLY aircraft using the airport. The other issue was communications. Aircraft Y pilot or what sounded like the instructor in this event; although both pilots were making calls which was confusing. The instructor was very hostile in his tone and really did not understand the confusion he created with his poor communication regarding which Runway they were conducting their simulated engine failure too. This aircraft as well as other aircraft were conducting touch and go landings to Runway 19 for at least 30 minutes or more prior to this brief event. Just making an announcement of your simulated intentions is not a clearance for priority over all other aircraft operating normally at an uncontrolled airport with the traffic pattern already 'Established'. This Aircraft which had just departed Runway 19 for the 5th time apparently thought that his communications were 'Heard by all' and feels that gave him priority to reverse the flow of traffic momentarily.

Data retrieved from NASA's ASRS site as of April 2012 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.