Narrative:

I was entering a left mid-downwind for landing with at least two other aircraft entering left-handed pattern behind me and a falcon jet announced on the unicom frequency it was on a right downwind for landing on [the same] runway.I then started a left base when one of the pilots of the jet requested I extend downwind so he wouldn't run me down on final. I obliged but reminded him there was not much distance available to extend downwind because there is an airspace boundary in this direction at the inner cylinder of class B airspace (surface-1;500 feet altitude) 5 miles from ZZZ.the jet kept unexpectedly extending on right downwind at about the same altitude as my aircraft until I was almost at the edge of the class B cut-out boundary where I immediately initiated a left base to avoid the boundary as shown on the aircraft's garmin 430 navigation display. At about the same time the jet then also started a right base turn and descent; but I estimate it was even closer to the boundary. During the jet's turn to right base the jet pilot requested cancelling IFR; but on the wrong frequency. With both of us converging on base legs this was a conflict; so I immediately announced I was going around maintaining 1;200 feet MSL on the upwind and subsequent traffic pattern. The falcon jet aircraft was visually in sight during it's descent until both of us were aligned on final where he then passed underneath my aircraft. I expect the closest approach was between 200 and 500 feet between the two aircraft at this point as we were both on final. Just prior to landing the jet pilot did thank everyone in the traffic pattern for maneuvering out of his way.as a note; I decided not to make a right turn evasive maneuver as the other aircraft behind me also announced go-arounds using 360 degree right turns and I did not have visual contact with them. In addition I was in a position so far extended on downwind where a 360 turn would not have been a good idea so close to the airspace boundary for ZZZ airspace. Some after-action thoughts:the falcon jet's long extended downwind was an unexpected maneuver. Jet pilots should be instructed by ATC to maintain a closer pattern to runway and not extend close to airspace boundaries when on a visual approach from an IFR arrival as this just causes other pilot's in the pattern to either lose sight of the aircraft or if following these faster aircraft coming in danger of an airspace violation.in a future situation like this; I likely will not extend downwind when landing but immediately initiate a go-around staying at traffic pattern altitude until re-established on subsequent final approach.

Google
 

Original NASA ASRS Text

Title: Decathlon pilot reported traffic pattern conflict with several aircraft at a non-towered airport located in close proximity to Class B airport boundary.

Narrative: I was entering a left mid-downwind for landing with at least two other aircraft entering left-handed pattern behind me and a Falcon jet announced on the UNICOM frequency it was on a right downwind for landing on [the same] runway.I then started a left base when one of the pilots of the jet requested I extend downwind so he wouldn't run me down on final. I obliged but reminded him there was not much distance available to extend downwind because there is an airspace boundary in this direction at the inner cylinder of Class B airspace (Surface-1;500 feet altitude) 5 miles from ZZZ.The jet kept unexpectedly extending on right downwind at about the same altitude as my aircraft until I was almost at the edge of the Class B cut-out boundary where I immediately initiated a left base to avoid the boundary as shown on the aircraft's Garmin 430 navigation display. At about the same time the jet then also started a right base turn and descent; but I estimate it was even closer to the boundary. During the jet's turn to right base the jet pilot requested cancelling IFR; but on the wrong frequency. With both of us converging on base legs this was a conflict; so I immediately announced I was going around maintaining 1;200 feet MSL on the upwind and subsequent traffic pattern. The Falcon jet aircraft was visually in sight during it's descent until both of us were aligned on final where he then passed underneath my aircraft. I expect the closest approach was between 200 and 500 feet between the two aircraft at this point as we were both on final. Just prior to landing the Jet pilot did thank everyone in the traffic pattern for maneuvering out of his way.As a note; I decided not to make a right turn evasive maneuver as the other aircraft behind me also announced go-arounds using 360 degree right turns and I did not have visual contact with them. In addition I was in a position so far extended on downwind where a 360 turn would not have been a good idea so close to the airspace boundary for ZZZ airspace. Some after-action thoughts:The Falcon jet's long extended downwind was an unexpected maneuver. Jet pilots should be instructed by ATC to maintain a closer pattern to Runway and not extend close to airspace boundaries when on a visual approach from an IFR arrival as this just causes other pilot's in the pattern to either lose sight of the aircraft or if following these faster aircraft coming in danger of an airspace violation.In a future situation like this; I likely will not extend downwind when landing but immediately initiate a go-around staying at traffic pattern altitude until re-established on subsequent final approach.

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.