Pilot reports of an near midair collision caused by the tower controller sequencing traffic and not ...

Narrative:

We were in the pattern doing touch and goes. We were doing left traffic for runway 31 at pvu. We turned base leg and tower told us to do a right 360 for spacing to put us behind an aircraft on an extended final leg. After we rolled out of the 360 turn on base at approximately 5300 ft MSL I called tower and told him we were re-established on base and ready to turn final. Tower then said continue northeast and then turn left back in to follow the traffic. As he was giving that instruction; I looked out to the right and the aircraft was passing right over the top of us approximately 200 ft above us and right on top of us. There was no lateral separation. The controller then directed us to fly northeast shortly then turn back to the left and in behind the experimental aircraft. By then the aircraft had passed over us so we did as instructed and then turned left to line up on final for 31 at pvu. If we hadn't been instructed to do the 360 turn and just continued downwind further or if the tower controller just put us in front of the traffic; this all may not have happened. The controller had a jet line up and wait anyway on the runway and the aircraft had to do a go around anyway. If we were sequenced in front of the aircraft this probably would not have happened or if he just had us extend downwind further instead of having us do a left 360 it likely would have been avoided.

Original NASA ASRS Text

Title: Pilot reports of an NMAC caused by the Tower Controller sequencing traffic and not issuing traffic.

Narrative: We were in the pattern doing touch and goes. We were doing left traffic for runway 31 at PVU. We turned base leg and tower told us to do a right 360 for spacing to put us behind an aircraft on an extended final leg. After we rolled out of the 360 turn on base at approximately 5300 ft MSL I called tower and told him we were re-established on base and ready to turn final. Tower then said continue northeast and then turn left back in to follow the traffic. As he was giving that instruction; I looked out to the right and the aircraft was passing right over the top of us approximately 200 ft above us and right on top of us. There was no lateral separation. The controller then directed us to fly northeast shortly then turn back to the left and in behind the experimental aircraft. By then the aircraft had passed over us so we did as instructed and then turned left to line up on final for 31 at PVU. If we hadn't been instructed to do the 360 turn and just continued downwind further or if the tower controller just put us in front of the traffic; this all may not have happened. The controller had a jet line up and wait anyway on the runway and the aircraft had to do a go around anyway. If we were sequenced in front of the aircraft this probably would not have happened or if he just had us extend downwind further instead of having us do a left 360 it likely would have been avoided.

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	1216410
Time
Date	201411
Local Time Of Day	0001-0600
Place
Locale Reference	PVU.Airport
State Reference	UT
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Make Model Name	Small Aircraft
Operating Under FAR Part	Part 91
Flight Phase	Final Approach
Flight Plan	None
Person 1
Function	Pilot Not Flying
Qualification	Flight Crew Multiengine Flight Crew Flight Instructor Flight Crew Commercial Flight Crew Instrument
Experience	Flight Crew Last 90 Days 150 Flight Crew Total 800 Flight Crew Type 500
Events
Anomaly	Conflict NMAC
Miss Distance	Horizontal 0 Vertical 200

Pilot reports of an near midair collision caused by the tower controller sequencing traffic and not issuing traffic.