Close proximity GA-small aircraft GA-small aircraft both making same practice IAP into ryn.

Attributes
ACN	87726
Time
Date	198805
Day	Fri
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : ryn
State Reference	AZ
Altitude	msl bound lower : 4700 msl bound upper : 4700
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : tus
Operator	general aviation : instructional
Make Model Name	Small Aircraft, Low Wing, 2 Eng, Retractable Gear
Flight Phase	descent : approach
Flight Plan	None
Aircraft 2
Make Model Name	Small Aircraft, High Wing, 1 Eng, Fixed Gear
Flight Phase	descent : approach
Flight Plan	None
Person 1
Affiliation	Other
Function	instruction : instructor
Qualification	pilot : cfi
Experience	flight time last 90 days : 90 flight time total : 6000 flight time type : 200
ASRS Report	87726
Person 2
Function	instruction : trainee
Events
Anomaly	conflict : nmac
Independent Detector	other flight crewa
Resolutory Action	flight crew : took evasive action
Consequence	Other
Miss Distance	horizontal : 100 vertical : 0
Supplementary
Primary Problem	Flight Crew Human Performance

Narrative:

Flying a practice NDB D approach into ryan under tucson approach control, starting procedure turn outbnd, an small aircraft B aircraft was approaching from the right. We turned left to avoid collision and thereafter continued with our procedure turn. After completion of procedure turn inbound, the same aircraft appeared ahead of us. We maintained altitude and shortly thereafter started a missed approach procedure to avoid conflict with this traffic. On ryan unicom frequency we noted that the other aircraft obviously was flying the same type approach procedure. Tucson approach did not have the other traffic on radar. (No transponder, or transponder not switched on?) suggestion: any time an aircrew intends to fly an IAP, they should: use ATC facilities if available, squawk appropriate transponder mode/code, in VMC keep a continuous lookout for other traffic.

Original NASA ASRS Text

Title: CLOSE PROX GA-SMA GA-SMA BOTH MAKING SAME PRACTICE IAP INTO RYN.

Narrative: FLYING A PRACTICE NDB D APCH INTO RYAN UNDER TUCSON APCH CTL, STARTING PROCEDURE TURN OUTBND, AN SMA B ACFT WAS APCHING FROM THE RIGHT. WE TURNED LEFT TO AVOID COLLISION AND THEREAFTER CONTINUED WITH OUR PROCEDURE TURN. AFTER COMPLETION OF PROCEDURE TURN INBND, THE SAME ACFT APPEARED AHEAD OF US. WE MAINTAINED ALT AND SHORTLY THEREAFTER STARTED A MISSED APCH PROCEDURE TO AVOID CONFLICT WITH THIS TFC. ON RYAN UNICOM FREQ WE NOTED THAT THE OTHER ACFT OBVIOUSLY WAS FLYING THE SAME TYPE APCH PROCEDURE. TUCSON APCH DID NOT HAVE THE OTHER TFC ON RADAR. (NO XPONDER, OR XPONDER NOT SWITCHED ON?) SUGGESTION: ANY TIME AN AIRCREW INTENDS TO FLY AN IAP, THEY SHOULD: USE ATC FACILITIES IF AVAILABLE, SQUAWK APPROPRIATE XPONDER MODE/CODE, IN VMC KEEP A CONTINUOUS LOOKOUT FOR OTHER TFC.

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