Instructor with spi had close proximity with second aircraft in uncontrolled traffic pattern.

Attributes
ACN	226167
Time
Date	199211
Day	Fri
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : tcy
State Reference	CA
Altitude	msl bound lower : 1000 msl bound upper : 1000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	general aviation : instructional
Make Model Name	Small Aircraft, High Wing, 1 Eng, Fixed Gear
Flight Phase	descent : approach other
Flight Plan	None
Aircraft 2
Make Model Name	Small Aircraft, High Wing, 1 Eng, Fixed Gear
Flight Phase	descent : approach other
Person 1
Affiliation	Other
Function	instruction : instructor
Qualification	pilot : cfi pilot : atp
Experience	flight time last 90 days : 210 flight time total : 3270 flight time type : 950
ASRS Report	226167
Person 2
Affiliation	Other
Function	instruction : trainee
Qualification	pilot : student
Events
Anomaly	conflict : airborne less severe non adherence : published procedure other spatial deviation
Independent Detector	other flight crewa
Resolutory Action	other other
Consequence	Other
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	other

Narrative:

While in the tracy traffic pattern, my student and I were working initially with another small aircraft from our flight school. Another small aircraft X entered the traffic pattern, however, we did not hear his call up, as the CTAF frequency was very congested and I believe his call was 'blocked.' he entered the traffic pattern ahead of our aircraft but apparently flew a wide pattern. We did not see him in the haze and we continued around the pattern making the standard position reporting. As we turned final we heard small aircraft X too close and going around. After we landed the small aircraft X began an early crosswind turn and resumed his pattern work. Suggestions: clearly broadcast intentions and make a standard 45 degrees entry. Use landing light in pattern, especially with lowered visibility. Fly the standard traffic pattern, if making a wide pattern specify 'tracy traffic, XXXX wide downwind 29 tracy.' keep a constant watch for traffic.

Original NASA ASRS Text

Title: INSTRUCTOR WITH SPI HAD CLOSE PROX WITH SECOND ACFT IN UNCTLED TFC PATTERN.

Narrative: WHILE IN THE TRACY TFC PATTERN, MY STUDENT AND I WERE WORKING INITIALLY WITH ANOTHER SMA FROM OUR FLT SCHOOL. ANOTHER SMA X ENTERED THE TFC PATTERN, HOWEVER, WE DID NOT HEAR HIS CALL UP, AS THE CTAF FREQ WAS VERY CONGESTED AND I BELIEVE HIS CALL WAS 'BLOCKED.' HE ENTERED THE TFC PATTERN AHEAD OF OUR ACFT BUT APPARENTLY FLEW A WIDE PATTERN. WE DID NOT SEE HIM IN THE HAZE AND WE CONTINUED AROUND THE PATTERN MAKING THE STANDARD POS RPTING. AS WE TURNED FINAL WE HEARD SMA X TOO CLOSE AND GOING AROUND. AFTER WE LANDED THE SMA X BEGAN AN EARLY XWIND TURN AND RESUMED HIS PATTERN WORK. SUGGESTIONS: CLRLY BROADCAST INTENTIONS AND MAKE A STANDARD 45 DEGS ENTRY. USE LNDG LIGHT IN PATTERN, ESPECIALLY WITH LOWERED VISIBILITY. FLY THE STANDARD TFC PATTERN, IF MAKING A WIDE PATTERN SPECIFY 'TRACY TFC, XXXX WIDE DOWNWIND 29 TRACY.' KEEP A CONSTANT WATCH FOR TFC.

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.