Near midair collision in the traffic pattern at a controled airport with parallel runways.

Attributes
ACN	538811
Time
Date	200202
Day	Fri
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : prc.airport
State Reference	AZ
Altitude	agl single value : 500
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tower : prc.tower tower : sba.tower
Operator	general aviation : instructional
Make Model Name	Skyhawk 172/Cutlass 172
Navigation In Use	other
Flight Phase	descent : approach
Route In Use	approach : traffic pattern
Flight Plan	VFR
Aircraft 2
Controlling Facilities	tower : prc.tower
Operator	general aviation : instructional
Make Model Name	Skyhawk 172/Cutlass 172
Operating Under FAR Part	Part 91
Flight Phase	descent : approach
Route In Use	approach : traffic pattern
Person 1
Affiliation	other
Function	instruction : instructor
Qualification	pilot : multi engine pilot : instrument pilot : commercial pilot : cfi
Experience	flight time last 90 days : 200 flight time total : 450 flight time type : 180
ASRS Report	538811
Person 2
Affiliation	other
Function	instruction : trainee
Events
Anomaly	conflict : nmac
Independent Detector	other controllerb other flight crewa
Resolutory Action	controller : issued new clearance flight crew : took evasive action
Miss Distance	horizontal : 300 vertical : 100
Supplementary
Problem Areas	ATC Human Performance Flight Crew Human Performance
Primary Problem	ATC Human Performance

Narrative:

Returning from a practice area, we reported over prescott valley and requested touch-and-goes. Controller gave us base entry to runway 21L, report 3 mi. We reported 3 mi. Controller had us do a left 360 degree turn, then follow a duchess on extended downwind. After reporting duchess in sight, we were cleared to land on runway 21L, #2 behind the duchess. Approach proceeded normally until final -- about 1 mi from the runway. At that time, I spotted a C172 on left base above us and preparing to turn final. I called the traffic to the controller who immediately sidestepped us to runway 21R. The controller may have seen it at the same time because communications were stepped on. After sidestep, I returned controls to the student who landed without incident on runway 21R. I do not believe this was controller error. At the time I was coaching my student in short-field lndgs and did not hear any change to our landing clearance, or my base traffic. There was a solo student in the pattern at the time, but I did not identify the plane beyond type.

Original NASA ASRS Text

Title: NMAC IN THE TFC PATTERN AT A CTLED ARPT WITH PARALLEL RWYS.

Narrative: RETURNING FROM A PRACTICE AREA, WE RPTED OVER PRESCOTT VALLEY AND REQUESTED TOUCH-AND-GOES. CTLR GAVE US BASE ENTRY TO RWY 21L, RPT 3 MI. WE RPTED 3 MI. CTLR HAD US DO A L 360 DEG TURN, THEN FOLLOW A DUCHESS ON EXTENDED DOWNWIND. AFTER RPTING DUCHESS IN SIGHT, WE WERE CLRED TO LAND ON RWY 21L, #2 BEHIND THE DUCHESS. APCH PROCEEDED NORMALLY UNTIL FINAL -- ABOUT 1 MI FROM THE RWY. AT THAT TIME, I SPOTTED A C172 ON L BASE ABOVE US AND PREPARING TO TURN FINAL. I CALLED THE TFC TO THE CTLR WHO IMMEDIATELY SIDESTEPPED US TO RWY 21R. THE CTLR MAY HAVE SEEN IT AT THE SAME TIME BECAUSE COMS WERE STEPPED ON. AFTER SIDESTEP, I RETURNED CTLS TO THE STUDENT WHO LANDED WITHOUT INCIDENT ON RWY 21R. I DO NOT BELIEVE THIS WAS CTLR ERROR. AT THE TIME I WAS COACHING MY STUDENT IN SHORT-FIELD LNDGS AND DID NOT HEAR ANY CHANGE TO OUR LNDG CLRNC, OR MY BASE TFC. THERE WAS A SOLO STUDENT IN THE PATTERN AT THE TIME, BUT I DID NOT IDENT THE PLANE BEYOND TYPE.

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