Narrative:

On an IFR flight plan to jyo. I was tracking inbound on localizer 17, called airport in sight to ATC at approximately 6.5 NM from runway threshold. ATC cleared us for change to advisory with a 'no traffic between you and airport or traffic pattern observed' advisory. At 5.5 NM I canceled IFR. I had already been making calls and monitoring unicom since 25 NM out with no response to my position/intention calls. Since we were near iad (9 NM) and on localizer 17 and at very close range (on final) for runway 17, we elected to continue with our straight-in approach. We called 4.5 NM final and at that moment, just after our call, an aircraft called 'turning base runway 17.' I immediately started looking for aircraft while advising on unicom of our 4.5 NM position. We acquired the traffic making a 'short approach' tight over the threshold of runway as if he wanted to 'squeeze in' before us. As we prepared for a balked landing, the aircraft abandoned the landing approach with a go around. The pilot of other aircraft (appeared to be a high wing cessna) proceeded to complain to us on unicom while we continued with our landing and post-landing procedures. We maintained radio silence after exiting the runway (to not create frequency congestion with non traffic communications). I expected to meet the other pilot for a possible debrief at the FBO but he never showed up during the 50 mins we spent in the lobby. At no point was our aircraft in danger of collision. We were exercising active scanning and acquired traffic with ample time for maneuvering. We landed normally on our approach.

Related reports:

Google
 

Original NASA ASRS Text

Title: A KING AIR PLT'S RPT ON A C172'S ENTRY PATTERN AND FAILURE TO GIVE RIGHT-OF-WAY WHILE ON APCH TO JYO, VA.

Narrative: ON AN IFR FLT PLAN TO JYO. I WAS TRACKING INBOUND ON LOC 17, CALLED ARPT IN SIGHT TO ATC AT APPROX 6.5 NM FROM RWY THRESHOLD. ATC CLRED US FOR CHANGE TO ADVISORY WITH A 'NO TFC BTWN YOU AND ARPT OR TFC PATTERN OBSERVED' ADVISORY. AT 5.5 NM I CANCELED IFR. I HAD ALREADY BEEN MAKING CALLS AND MONITORING UNICOM SINCE 25 NM OUT WITH NO RESPONSE TO MY POS/INTENTION CALLS. SINCE WE WERE NEAR IAD (9 NM) AND ON LOC 17 AND AT VERY CLOSE RANGE (ON FINAL) FOR RWY 17, WE ELECTED TO CONTINUE WITH OUR STRAIGHT-IN APCH. WE CALLED 4.5 NM FINAL AND AT THAT MOMENT, JUST AFTER OUR CALL, AN ACFT CALLED 'TURNING BASE RWY 17.' I IMMEDIATELY STARTED LOOKING FOR ACFT WHILE ADVISING ON UNICOM OF OUR 4.5 NM POS. WE ACQUIRED THE TFC MAKING A 'SHORT APCH' TIGHT OVER THE THRESHOLD OF RWY AS IF HE WANTED TO 'SQUEEZE IN' BEFORE US. AS WE PREPARED FOR A BALKED LNDG, THE ACFT ABANDONED THE LNDG APCH WITH A GAR. THE PLT OF OTHER ACFT (APPEARED TO BE A HIGH WING CESSNA) PROCEEDED TO COMPLAIN TO US ON UNICOM WHILE WE CONTINUED WITH OUR LNDG AND POST-LNDG PROCS. WE MAINTAINED RADIO SILENCE AFTER EXITING THE RWY (TO NOT CREATE FREQ CONGESTION WITH NON TFC COMS). I EXPECTED TO MEET THE OTHER PLT FOR A POSSIBLE DEBRIEF AT THE FBO BUT HE NEVER SHOWED UP DURING THE 50 MINS WE SPENT IN THE LOBBY. AT NO POINT WAS OUR ACFT IN DANGER OF COLLISION. WE WERE EXERCISING ACTIVE SCANNING AND ACQUIRED TFC WITH AMPLE TIME FOR MANEUVERING. WE LANDED NORMALLY ON OUR APCH.

Data retrieved from NASA's ASRS site as of July 2007 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.