Narrative:

Narrative-chain of events/situation: 15.1 how the situation arose: the situation began while on a long straight-in approach to the runway 17 at coronado airport (4AC). Prior to a 7-8 mi final our aircraft monitored the airport unicom for traffic and active runway. At that time we heard an aircraft (we believe a citabria announced they were 'down-wind runway 17 touch and go.' shortly after, we announced a straight in approach from our north position (about 5-7 mi now) and that we would 'sequence' or accommodate any traffic. The citabria did not acknowledge our xmissions. Next the citabria announced base to runway 17. We then accessed that we would be following the citabria to runway 17 and transmitted as such. Next we asked if the citabria would expedite off active runway to allow our landing. No response. 15.2 contributing factor: the citabria landed, continued a long and slow taxi, no communication. 15.3 how it was discovered: seeing this and our proximity to threshold, we first began slow 'south' turns to allow spacing and time to allow the citabria reasonable time to land and to exit the active runway. The citabria was purposefully using a delaying tactic that would not allow us to not abort our landing so there would be no conflict on the runway. We were about 1-1 1/2 mi from threshold. 15.4 corrective action: knowing that we had heard other traffic earlier calling in from the west, 1 or 2 aircraft (20 mi out) and not knowing if the citabria might decide to make a takeoff we turned right instead of executing a climb over the runway, possibly conflicting with a takeoff by the citabria. The turn to the right (and per the far regarding patterns at uncontrolled airports) would take us to the west to identify and avoid any traffic. We continued to turn right to get a visual on the situation and see if all was ok (no conflicting traffic) and then continued to turn right to the final to runway 17. Landed with no conflict or unsafe situation! The flight instructor in citabria has a personal 'loathing' for 'straight-in' approachs and has no consideration for advisory circular #90-66A! 15.6 summation: this situation did not contribute to any unsafe maneuvers or aircraft conflict. However, since we were on a long straight-in final, initially lower than the citabria, committed to the landing, you could make a case for reckless operation (far 91.13 para a) by the citabria in that he purposely continued to cut us off! Being the lower aircraft initially and on final would have indicated that we technically had the right-of-way, as I think the far's indicate. Our evasive action avoided any further danger to our aircraft! This did not result in any close proximity (conflict) to another aircraft. It resulted in inconsideration by an flight instructor (so called professional!).

Google
 

Original NASA ASRS Text

Title: PF STRAIGHT IN APCH AT NON TWR ARPT BELIEVES INSTRUCTOR PLT DELIBERATELY PROVOKED A GAR.

Narrative: NARRATIVE-CHAIN OF EVENTS/SIT: 15.1 HOW THE SIT AROSE: THE SIT BEGAN WHILE ON A LONG STRAIGHT-IN APCH TO THE RWY 17 AT CORONADO ARPT (4AC). PRIOR TO A 7-8 MI FINAL OUR ACFT MONITORED THE ARPT UNICOM FOR TFC AND ACTIVE RWY. AT THAT TIME WE HEARD AN ACFT (WE BELIEVE A CITABRIA ANNOUNCED THEY WERE 'DOWN-WIND RWY 17 TOUCH AND GO.' SHORTLY AFTER, WE ANNOUNCED A STRAIGHT IN APCH FROM OUR N POS (ABOUT 5-7 MI NOW) AND THAT WE WOULD 'SEQUENCE' OR ACCOMMODATE ANY TFC. THE CITABRIA DID NOT ACKNOWLEDGE OUR XMISSIONS. NEXT THE CITABRIA ANNOUNCED BASE TO RWY 17. WE THEN ACCESSED THAT WE WOULD BE FOLLOWING THE CITABRIA TO RWY 17 AND XMITTED AS SUCH. NEXT WE ASKED IF THE CITABRIA WOULD EXPEDITE OFF ACTIVE RWY TO ALLOW OUR LNDG. NO RESPONSE. 15.2 CONTRIBUTING FACTOR: THE CITABRIA LANDED, CONTINUED A LONG AND SLOW TAXI, NO COM. 15.3 HOW IT WAS DISCOVERED: SEEING THIS AND OUR PROX TO THRESHOLD, WE FIRST BEGAN SLOW 'S' TURNS TO ALLOW SPACING AND TIME TO ALLOW THE CITABRIA REASONABLE TIME TO LAND AND TO EXIT THE ACTIVE RWY. THE CITABRIA WAS PURPOSEFULLY USING A DELAYING TACTIC THAT WOULD NOT ALLOW US TO NOT ABORT OUR LNDG SO THERE WOULD BE NO CONFLICT ON THE RWY. WE WERE ABOUT 1-1 1/2 MI FROM THRESHOLD. 15.4 CORRECTIVE ACTION: KNOWING THAT WE HAD HEARD OTHER TFC EARLIER CALLING IN FROM THE W, 1 OR 2 ACFT (20 MI OUT) AND NOT KNOWING IF THE CITABRIA MIGHT DECIDE TO MAKE A TKOF WE TURNED R INSTEAD OF EXECUTING A CLB OVER THE RWY, POSSIBLY CONFLICTING WITH A TKOF BY THE CITABRIA. THE TURN TO THE R (AND PER THE FAR REGARDING PATTERNS AT UNCTLED ARPTS) WOULD TAKE US TO THE W TO IDENT AND AVOID ANY TFC. WE CONTINUED TO TURN R TO GET A VISUAL ON THE SIT AND SEE IF ALL WAS OK (NO CONFLICTING TFC) AND THEN CONTINUED TO TURN R TO THE FINAL TO RWY 17. LANDED WITH NO CONFLICT OR UNSAFE SIT! THE FLT INSTRUCTOR IN CITABRIA HAS A PERSONAL 'LOATHING' FOR 'STRAIGHT-IN' APCHS AND HAS NO CONSIDERATION FOR ADVISORY CIRCULAR #90-66A! 15.6 SUMMATION: THIS SIT DID NOT CONTRIBUTE TO ANY UNSAFE MANEUVERS OR ACFT CONFLICT. HOWEVER, SINCE WE WERE ON A LONG STRAIGHT-IN FINAL, INITIALLY LOWER THAN THE CITABRIA, COMMITTED TO THE LNDG, YOU COULD MAKE A CASE FOR RECKLESS OP (FAR 91.13 PARA A) BY THE CITABRIA IN THAT HE PURPOSELY CONTINUED TO CUT US OFF! BEING THE LOWER ACFT INITIALLY AND ON FINAL WOULD HAVE INDICATED THAT WE TECHNICALLY HAD THE RIGHT-OF-WAY, AS I THINK THE FAR'S INDICATE. OUR EVASIVE ACTION AVOIDED ANY FURTHER DANGER TO OUR ACFT! THIS DID NOT RESULT IN ANY CLOSE PROX (CONFLICT) TO ANOTHER ACFT. IT RESULTED IN INCONSIDERATION BY AN FLT INSTRUCTOR (SO CALLED PROFESSIONAL!).

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.