A flight instructor and his student suffered an near midair collision with another aircraft in an un...

Narrative:

While inbound to ckn my student and I overheard multiple aircraft on their way to ckn. There was one aircraft on a 10 mile final for 31 low approach; another aircraft overflying at about 3000 feet; then a warrior operating north a few miles out for runway 13. There was also a garbled radio call which I couldn't make out. We proceed outbound to make left traffic for 13. The warrior landed and got clear of the runway; and the aircraft overflying the airport overflew it. We were now base to final making radio calls as we go along and coming in for a landing. On upwind we made a radio call and proceeded to the downwind. On downwind we made another call. The other aircraft for 31 was now two miles out on final. This is where someone on the ground made a radio call and stated that there was an aircraft about our same position. We looked around and saw an aircraft that was lower; at our 2 o'clock position and within 500 feet. I took the controls and turned towards base to exit the traffic pattern and made a radio call telling the aircraft on a 31 low approach he had someone coming the opposing direction. I didn't hear a radio call from this aircraft so I'm assuming they we having radio problems.maintaining situational awareness in the traffic pattern and scanning more often would be a corrective action because not everyone can be communicating.

Original NASA ASRS Text

Title: A flight instructor and his student suffered an NMAC with another aircraft in an uncontrolled airport traffic pattern.

Narrative: While inbound to CKN my student and I overheard multiple aircraft on their way to CKN. There was one aircraft on a 10 mile final for 31 low approach; another aircraft overflying at about 3000 feet; then a warrior operating north a few miles out for runway 13. There was also a garbled radio call which I couldn't make out. We proceed outbound to make left traffic for 13. The warrior landed and got clear of the runway; and the aircraft overflying the airport overflew it. We were now base to final making radio calls as we go along and coming in for a landing. On upwind we made a radio call and proceeded to the downwind. On downwind we made another call. The other aircraft for 31 was now two miles out on final. This is where someone on the ground made a radio call and stated that there was an aircraft about our same position. We looked around and saw an aircraft that was lower; at our 2 o'clock position and within 500 feet. I took the controls and turned towards base to exit the traffic pattern and made a radio call telling the aircraft on a 31 low approach he had someone coming the opposing direction. I didn't hear a radio call from this aircraft so I'm assuming they we having radio problems.Maintaining situational awareness in the traffic pattern and scanning more often would be a corrective action because not everyone can be communicating.

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	1200738
Time
Date	201409
Local Time Of Day	1201-1800
Place
Locale Reference	CKN.Airport
State Reference	MN
Environment
Flight Conditions	VMC
Aircraft 1
Make Model Name	Skyhawk 172/Cutlass 172
Operating Under FAR Part	Part 91
Flight Phase	Landing
Flight Plan	None
Aircraft 2
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Operating Under FAR Part	Part 91
Person 1
Function	Instructor
Qualification	Flight Crew Commercial Flight Crew Flight Instructor Flight Crew Instrument
Experience	Flight Crew Last 90 Days 10 Flight Crew Total 240 Flight Crew Type 100
Events
Anomaly	Conflict NMAC
Miss Distance	Horizontal 499 Vertical 100

A flight instructor and his student suffered an near midair collision with another aircraft in an uncontrolled airport traffic pattern.