Date: 201705
Local time of day: 0601-1200
Location: E63.Airport, AZ
Flight conditions: VMC
Light: Daylight
Aircraft: Small Aircraft; Low Wing; 1 Eng; Retractable Gear
Operator: FBO
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Cruise; Descent; Initial Approach
Airspace: Class G ZAB
ATC / advisory: CTAF E63
Second aircraft: Small Aircraft; High Wing; 1 Eng; Fixed Gear
Reporter organization: FBO
Reporter function: Pilot Not Flying; Instructor
Reporter qualification: Flight Crew Flight Instructor
Human factors: Communication Breakdown; Confusion; Distraction; Situational Awareness; Time Pressure; Workload
Anomaly: Conflict NMAC; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Flight Crew Became Reoriented; Flight Crew Took Evasive Action
Contributing factors: Airport; Human Factors; Procedure
Primary problem: Human Factors

Narrative: Approaching E63 a Cessna landed and made a full stop taxi back. Shortly after takeoff from our touch and go at E63; with the Cessna still holding short of runway 22; our aircraft was on upwind at a few hundred feet AGL when a solo Student Pilot that had failed to call 'solo student' suddenly stated that he would perform a 360 on the 2 mile 45. At this point the Cessna stated he was taking off runway 22. Multiple calls were made to that student pilot on the 45 to try to confirm what he was doing and no response was received. Our aircraft was turned to prevent crossing south of I-8 as the aircraft performing the 360 was now in sight and a turning crosswind call was made. After turning crosswind my student called the solo student again and this time received a response and that student stated he would perform an additional 360 for us. At this point our traffic alert was set off for that aircraft on the 45. We reported turning left downwind and immediately after the Cessna that departed behind us reported turning crosswind. At this point the traffic system did not make any additional warning for that aircraft; likely due to being locked out for the previous traffic warning it was showing. I began looking around the area trying to locate the Cessna to confirm its position in relation to our aircraft. Suddenly both the student and I noticed the Cessna coming directly at us (it would appear that he basically reached the departure end of the runway and immediately turned). At the same time; both the student and I began to apply forward pressure to the yoke to level off our aircraft a couple hundred feet below Traffic Pattern Altitude and begin to break out of the pattern and the Cessna passed directly behind us and only a few hundred feet above us. Multiple calls were made to contact the aircraft but it did not respond to any and as such we were unable to obtain their call sign. We then maneuvered to follow the solo student performing the 360s back into the airport to resume our mission and made contact to coordinate with them that they would be ahead of us and we had them in sight. Remainder of the mission was flown uneventfully and returned to our home base afterward.Likely causes were a combination of things but started with a student making an unnecessary 360 close to the airport on the 45 resulting in radio congestion trying to determine their intentions. Some language barriers might have been a factor in resulting in student not hearing/understanding the call was for them as well as not using the 'solo student' with their call sign as that was why calls were made attempting to contact their instructor to figure out the situation. Secondary and main factor was obviously the Cessna's failure to monitor radio calls and traffic positions prior to making a turn to crosswind resulting in a loss of separation with our aircraft.




Synopsis: An instructor pilot described a near miss with a student pilot who did not comply with CTAF communications and recommended airport pattern procedures at E63.