GA pilot reported an near midair collision on approach prior to communications transfer from ARTCC t...

Narrative:

My student and I were on an IFR flight plan to mko. We received clearance from ATC (fort worth center) to descend to 3;500 ft. MSL from 5;000 ft. MSL and were cleared direct to pokyo for the RNAV runway 13 into mko. When we were about 5nm west of pokyo; ATC warned us of an airplane at our 12 o'clock; heading towards us about 5nm away. We looked for the traffic but were unable to see the reported traffic. We were in VMC conditions with broken clouds around us about at our same altitude. Visibility was unlimited. About a minute or two later ATC again warned us of the traffic and when we reported we were unable to see the traffic; ATC instructed us to turn right 40 degrees to avoid the oncoming traffic. Upon initiating the turn; I saw aircraft Y fly about 300 ft. Below us. Once the aircraft passed us and was no longer a factor; we were cleared back direct to pokyo and cleared for the approach. We then executed a hold in lieu of a procedure turn and continued the approach. Once we were about 3 miles from the final approach fix (culad); ATC cleared us to change to the advisory frequency and advised us to cancel our IFR flight plan on the ground or with them in the air. We elected to cancel our IFR flight plan in the air with ft. Worth center since we were in VMC conditions had visual contact with the airport. Once we switched over to CTAF; our traffic alert system alerted us of traffic at our same altitude and location. We started to look around and I saw aircraft Y to the west of us; at our same altitude; and about half a mile away initiating a bank away from us. My student announced our location and intentions on CTAF and the pilot of aircraft Y replied 'we've almost hit you guys twice now and you should be talking on CTAF when you're operating close to an airport.' I replied that we were on an IFR flight plan talking with ft. Worth center and they had just switched us over to CTAF. The aircraft Y pilot then replied that we should be monitoring the CTAF frequency anyway. I thanked the pilot for his advice and for not running into us twice. Mko is class G airspace until 700 ft. AGL and then class east after then.

Original NASA ASRS Text

Title: GA pilot reported an NMAC on approach prior to communications transfer from ARTCC to CTAF.

Narrative: My student and I were on an IFR flight plan to MKO. We received clearance from ATC (Fort Worth Center) to descend to 3;500 ft. MSL from 5;000 ft. MSL and were cleared direct to POKYO for the RNAV RWY 13 into MKO. When we were about 5nm west of POKYO; ATC warned us of an airplane at our 12 o'clock; heading towards us about 5nm away. We looked for the traffic but were unable to see the reported traffic. We were in VMC conditions with broken clouds around us about at our same altitude. Visibility was unlimited. About a minute or two later ATC again warned us of the traffic and when we reported we were unable to see the traffic; ATC instructed us to turn right 40 degrees to avoid the oncoming traffic. Upon initiating the turn; I saw Aircraft Y fly about 300 ft. below us. Once the aircraft passed us and was no longer a factor; we were cleared back direct to POKYO and cleared for the approach. We then executed a hold in lieu of a procedure turn and continued the approach. Once we were about 3 miles from the final approach fix (CULAD); ATC cleared us to change to the advisory frequency and advised us to cancel our IFR flight plan on the ground or with them in the air. We elected to cancel our IFR flight plan in the air with Ft. Worth Center since we were in VMC conditions had visual contact with the airport. Once we switched over to CTAF; our traffic alert system alerted us of traffic at our same altitude and location. We started to look around and I saw Aircraft Y to the West of us; at our same altitude; and about half a mile away initiating a bank away from us. My student announced our location and intentions on CTAF and the pilot of Aircraft Y replied 'We've almost hit you guys twice now and you should be talking on CTAF when you're operating close to an airport.' I replied that we were on an IFR flight plan talking with Ft. Worth Center and they had just switched us over to CTAF. The Aircraft Y pilot then replied that we should be monitoring the CTAF frequency anyway. I thanked the pilot for his advice and for not running into us twice. MKO is class G airspace until 700 ft. AGL and then class E after then.

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	1677868
Time
Date	201908
Local Time Of Day	1201-1800
Place
Locale Reference	MKO.Airport
State Reference	OK
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Make Model Name	Small Aircraft Low Wing 2 Eng Retractable Gear
Operating Under FAR Part	Part 91
Flight Phase	Initial Approach
Route In Use	Direct
Flight Plan	IFR
Aircraft 2
Make Model Name	Small Transport
Flight Phase	Initial Approach
Person 1
Function	Pilot Not Flying Instructor
Qualification	Flight Crew Multiengine Flight Crew Instrument Flight Crew Commercial Flight Crew Flight Instructor
Experience	Flight Crew Last 90 Days 212 Flight Crew Total 870 Flight Crew Type 220
Events
Anomaly	Conflict NMAC Deviation - Procedural Published Material / Policy
Miss Distance	Horizontal 0 Vertical 300

GA pilot reported an near midair collision on approach prior to communications transfer from ARTCC to CTAF.