Date: 202002
Local time of day: 0601-1200
Location: FHU.Airport, AZ
Flight conditions: VMC
Light: Daylight
Aircraft: Small Aircraft
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Training
Flight phase: Landing
Airspace: Class G FHU
ATC / advisory: CTAF FHU
Second aircraft: Small Aircraft
Reporter organization: Personal
Reporter function: Instructor; Pilot Flying
Reporter qualification: Flight Crew Flight Engineer; Flight Crew Flight Instructor; Flight Crew Instrument; Flight Crew Multiengine
Human factors: Communication Breakdown; Confusion; Situational Awareness; Training / Qualification
Anomaly: Conflict Ground Conflict; Critical; Conflict NMAC
Detector: Person Flight Crew
When detected: Other Landing roll out
Contributing factors: Human Factors; Airport; Procedure
Primary problem: Procedure

Narrative: During an instructional period with two primary students onboard and operating in the traffic pattern a pilot flying an instrument approach came dangerously close to our flight while executing the missed approach procedure. As I maneuvered my plane from Right Base to Final of Runway 12; the pilot of a Aircraft Y continued the ILS approach to Runway 26 without acknowledging us; who were already established in the traffic pattern. I made several radio calls on CTAF reporting our position and intentions of making a full-stop landing. The Aircraft Y pilot only made calls stating he is on the ILS approach and his distance to the airport starting at 8 miles and ending at 4 miles. As we touched down on Runway 12; I caught sight of the Aircraft Y at the approach end of Runway 26. I think I heard him call 'Missed Approach' but can't be 100% sure. I applied maximum braking to ensure we would not cross into Runway 26. As we came to a stop just short of the intersection of Runway 12 and 26; we saw the Aircraft Y fly overhead approximately 200 feet and appeared to be climbing. I immediately contacted the pilot on CTAF stating that we were established in the traffic pattern and had reported so. He replied that he had made position calls on final. I reiterated the fact that we were already established in the traffic pattern and implied that he should have avoided his direction of flight. Runway 26 intersects with Runway 12; 4;100 feet from the approach end. Runway 12 intersects Runway 26 approximately 1;800 feet from the approach end. It was obvious to me by his tone; that this pilot felt; just because he was making position reports at those distances; established himself in the traffic pattern and did not have to yield the right of way. It makes me wonder how close we would have been to each other if I had to make a go-around or was unable to stop by the Runway 26/12 intersection. I feel that if this pilot had made his intentions known; we could have worked together to complete our intended training and ensure safety of flight for both. It is my future intention; to query a pilot who is making vague radio calls and ask for specific intentions so that we can avoid or work together while in such proximity. The FAA had sent out an email last year stating the change to the right of way rule. An aircraft established in the traffic pattern; has the right of way of an aircraft on an instrument approach.




Synopsis: An Instructor Pilot landing at an uncontrolled airport reported an aircraft on a missed approach to an intersecting runway flew 200 feet over them.