Date: 202009
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Skyhawk 172/Cutlass 172
Operator: Corporate
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Final Approach
Airspace: Class G ZZZ
Second aircraft: Osprey (V22)
Reporter organization: Corporate
Reporter function: Pilot Flying
Reporter qualification: Flight Crew Flight Instructor; Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Commercial
Human factors: Situational Awareness; Communication Breakdown
Anomaly: Conflict NMAC; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Procedure; Human Factors
Primary problem: Human Factors

Narrative: I was conducting a discovery flight with a student and we were entering the 45 to the downwind for Runway 5. It was a windy day with winds at 060 14 gusts around 20; but VMC conditions with no clouds. We were descending through about 1200 ft. AGL and I was letting the student fly the pattern while I made radio calls. I made the call we were on the 45 entry to the downwind and then the call that we were on downwind. Around abeam the numbers I did the before landing checklist and around that time took over control of the aircraft. Around 800 ft. AGL; I made my left base turn and called base on frequency. Descending through around 600-700 ft.; I heard a call from an aircraft stating they were turning crosswind; then correction for downwind Runway 5 and that they were a V-22. At that point I didn't consider them a factor and was on final approach at which point I called that I was on final for Runway 5. I was descending through 500 ft. when the ADS-B traffic annunciator came on the screen that an aircraft was 300 ft. above. Prior to this I had not visually seen any aircraft in the pattern; nor did I see anything on the GPS. I made another call that I was on a short final for Runway 5 and the other aircraft was shown at 200 ft. above me. I slipped down from 500 ft. to 200 ft. to lose more altitude but was not over the runway so didn't go too low. At one point; the ADS-B annunciation showed the aircraft 100 ft. above me during the slip or right before I began the maneuver. Supposedly from those who were watching and listening to the frequency; the V-22 had called stating they saw me and were going to maintain visual separation. I didn't know about this until I was on the ground. I do not know how far away horizontally the aircraft was from me during the time when this occurred. Around 1000 ft. from the runway I had the thought that this signal was a ghost signal from the receiver. I didn't realize it was an aircraft until I was on the ground past the hold short line doing the after-landing checklist when I heard the rotors from the aircraft approaching the runway. I think the transponder for the military aircraft may have been off until they were right behind me and that was when I noticed that they were there; and my fight or flight sense kicked in to avoid an NMAC. I didn't hear any radio calls from them once I saw the alert because I was focused on maintaining separation. If I had been able to hear and better understand what they were doing; I think I would have been able to give a better radio call about how high I was and how close to the runway I was. At no point in time did I see the V-22 until I was on the ramp parking. Personally; I believe the V-22 should have gone around. Doing a go around popped in my mind; but I dismissed it because the V-22 was above me and I didn't want to fly into them. I felt rushed to land and get off the runway because at that time I didn't know if they could see me. After talking to people on the ground that saw this and were listening to the radios; I realized I had a little more room that what I thought I had in the plane. An observer stated that the V-22 had called saying they were following me in and that they were well offset from me; behind and above me.




Synopsis: Flight Instructor reported taking evasive action to avoid a mid air collision with another aircraft.