C172 instructor pilot reported that another aircraft operating under IFR failed to look for traffic ...

Attributes
ACN	1681262
Time
Date	201909
Local Time Of Day	0601-1200
Place
Locale Reference	PVC.Airport
State Reference	MA
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Make Model Name	Skyhawk 172/Cutlass 172
Operating Under FAR Part	Part 91
Flight Phase	Final Approach
Route In Use	Visual Approach
Flight Plan	None
Aircraft 2
Make Model Name	PA-31 Navajo/Chieftan/Mojave/T1040
Operating Under FAR Part	Part 91
Flight Plan	IFR
Person 1
Function	Captain Instructor Pilot Not Flying
Qualification	Flight Crew Flight Instructor Flight Crew Air Transport Pilot (ATP) Flight Crew Instrument
Experience	Flight Crew Last 90 Days 42 Flight Crew Total 15000 Flight Crew Type 1000
Events
Anomaly	Conflict NMAC Deviation - Procedural FAR Deviation - Procedural Published Material / Policy
Miss Distance	Horizontal 75

Narrative:

I was doing touch and go landings on runway 7 with a student. I was downwind making standard calls when aircraft Y was reporting on the GPS approach to runway 7. I reported my base turn when turning final when aircraft Y said I cut him off. I told him I was in the traffic pattern and he replied that he was IFR. I told him that this was an uncontrolled airport under visual conditions and he was to merge with the local traffic. He said he was IFR so he didn't have to. I referred him to the aim and part 91.being IFR into an uncontrolled airport under visual conditions does not mean one can fly with impunity into a busy traffic pattern. I feel that aircraft Y pilot felt that his IFR clearance gave him priority. That is a dangerous assumption. At [company]; our rule was to fly the traffic pattern. We understand that we had to mix with local traffic.

Original NASA ASRS Text

Title: C172 Instructor Pilot reported that another aircraft operating under IFR failed to look for traffic in the pattern; resulting in a NMAC.

Narrative: I was doing touch and go landings on Runway 7 with a student. I was downwind making standard calls when Aircraft Y was reporting on the GPS approach to Runway 7. I reported my base turn when turning final when Aircraft Y said I cut him off. I told him I was in the traffic pattern and he replied that he was IFR. I told him that this was an uncontrolled airport under visual conditions and he was to merge with the local traffic. He said he was IFR so he didn't have to. I referred him to the AIM and part 91.Being IFR into an uncontrolled airport under visual conditions does not mean one can fly with impunity into a busy traffic pattern. I feel that Aircraft Y pilot felt that his IFR clearance gave him priority. That is a dangerous assumption. At [Company]; our rule was to fly the traffic pattern. We understand that we had to mix with local traffic.

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.

C172 instructor pilot reported that another aircraft operating under IFR failed to look for traffic in the pattern; resulting in a near midair collision.