SMA HAS NMAC WITH ACFT ON FINAL APCH AT NON TWR ARPT.

Date: 1994-11 · Aircraft: PA-28 Cherokee/Archer/Dakota/Pillan/Warrior

Anomalies: conflict-nmac|deviation-discrepancy-procedural-other-unknown|deviation-discrepancy-procedural-published-material-policy|other-unspecified

Synopsis

SMA HAS NMAC WITH ACFT ON FINAL APCH AT NON TWR ARPT.

Narrative

I WAS OPERATING AN ARCHER II (PA28/160); I CLOSED PATTERN AT RAMONA ARPT; HAVING JUST MADE MY FIRST TOUCH-AND-GO; ON RWY 27; USING THE STANDARD L PATTERN. WHILE OPERATING IN PATTERN; I CALLED ALL TURNS OVER UNICOM FREQ 122.7; AND CONTINUOUSLY MONITORED THAT FREQ. ON XWIND; AN ACFT APCHED FROM THE SW; ENTERING THE PATTERN BEHIND ME; WITH CALL SIGN AIRTAC. AIRTAC: PLANE ORIGINATES FROM THE FIRE SVC SQUADRON AT RAMONA; AND WAS PLTED BY MR ABC. AS I TURNED DOWNWIND; I HAD A DISTANT VISUAL ON THIS ACFT; WHO JOINED THE PATTERN BEHIND ME (AND WAS A WITNESS: MR ABC). THERE WAS 1 OTHER ACFT IN THE PATTERN; AND COMMUNICATING; WHICH HAD MADE A SHORT APCH AHEAD OF ME; AND WAS ON FINAL WHEN I TURNED BASE. I PROCEEDED AROUND THE PATTERN; CALLING MY BASE TURN AND FINAL TURN; AND ALIGNING WITH THE RWY AT APPROX 1 MI FROM THE THRESHOLD; ALT APPROX 600 FT AGL; AND SPD 70 KTS. AS I ROLLED OUT OF MY TURN; A F- 33 BONANZA PASSED BY MY R WING AT A DISTANCE OF APPROX 75 FT; ON MY HDG; AND AT A HIGHER RATE OF SPD. AT THE SAME INSTANT; I HEARD A RADIO CALL FROM AIRTAC; ADVISING ME OF CONFLICTING TFC. I BANKED L; PERFORMED A GAR; REJOINED THE PATTERN BEHIND A CESSNA 337 SKYMASTER; WHO IDENTED HIMSELF TO ME AS AIRTAC?; WHO HAD BEEN FOLLOWING ME IN THE PATTERN. THE ACFT WITH WHICH I HAD NEARLY COLLIDED HAD MADE A STRAIGHT-IN APCH; WITHOUT BROADCASTING HIS PRESENCE. UPON LNDG; I IDENTED THIS ACFT AS XYZ. AS THIS ACFT WAS TAXIING; HE MADE HIS FIRST BROADCAST; TO THE EFFECT THAT HE WAS NOT REQUIRED TO USE THE RADIO; SINCE HE WAS LNDG AT AN UNCTLED FIELD. I TAXIED TO THE FIRE STATION; AND CONFIRMED WITH MR ABC THAT THE BONANZA HAD MADE A STRAIGHT-IN APCH; AND THAT HE HAD HEARD NO RADIO TFC. HE STATED THAT HE SAW THE INCIDENT; AND TRIED TO WARN ME; WHICH WAS THE BROADCAST I RECEIVED CO-INCIDENT WITH MY FIRST SIGHT OF THE BONANZA OFF MY R WING. MY ANALYSIS: BONANZA MADE A STRAIGHT-IN APCH INTO A BUSY TFC PATTERN; AND DID NOT GIVE WAY TO TFC IN THE PATTERN. THERE WAS AN ACFT ON SHORT FINAL AHEAD OF ME; AND AN ACFT APPROX 2 MI BEHIND ME; IN PATTERN. HE HAD NO ROOM TO ENTER THE PATTERN; WITHOUT FORCING OTHER TFC TO GIVE WAY; ASSUMING THAT TFC HAD SEEN HIM. BONANZA MADE NO RADIO COMS ON APCHING THE PATTERN (WHICH HE CONFIRMED HIMSELF AFTER HE WAS ON THE GND). IF HE WAS MONITORING UNICOM; HE SHOULD HAVE BEEN AWARE OF TFC IN THE PATTERN; AND ITS POS. WHEN I TURNED FINAL; I WOULD HAVE PRESENTED THE FLAT BELLY AND EXPANSE OF MY WINGS TO HIM; AS HE APCHED STRAIGHT-IN. MY INTENTIONS SHOULD HAVE BEEN CLR; EVEN IF HIS RADIO WAS OFF; YET HE CONTINUED INTO THE PATTERN AND INTO DANGEROUS PROX WITH MY ACFT. I FAILED TO SEE THE APCHING ACFT. MITIGATING FACTORS WERE THE L BANK NECESSARY TO TURN FINAL; WHICH RAISED THE R WING AND OBSCURED MY VIEW TO THE R; THE VISUALLY CLUTTERED BACKGND TO THE E OF THE ARPT AT RAMONA; AND THE DIFFICULTY OF SPOTTING AN ACFT APCHING NEAR HEAD-ON; WHERE NONE IS EXPECTED. I WAS PRE-OCCUPIED WITH WATCHING PRECEDING TFC ON SHORT FINAL; MAINTAINING PRECISE AIRSPD; COMMUNICATING WITH OTHER TFC; AND LINING UP ON THE RWY FOR FINAL APCH. I CAN; AND WILL; CORRECT THIS; AND WILL CERTAINLY BE INTENSELY AWARE OF THE POSSIBILITY OF STRAIGHT-IN TFC IN THE FUTURE. I WAS DISMAYED THAT THE PLT OF BONANZA APPARENTLY DID NOT APPRECIATE THE GRAVITY OF THIS INCIDENT; NOR ACKNOWLEDGE ANY RESPONSIBILITY FOR TAKING MEASURES TO AVOID IT. A STRAIGHT-IN APCH TO AN UNCTLED FIELD IS LEGAL; BUT NOT VERY WISE WHEN THERE IS BUSY TFC IN THE PATTERN. ENTERING THE PATTERN WITH A RADIO; AND NOT MONITORING OR USING IT TO ANNOUNCE ONE'S PRESENCE IS ALSO LEGAL; BUT NOT VERY WISE IN A BUSY TFC PATTERN. MAKING A STRAIGHT-IN APCH WITHOUT ANY RADIO CONTACT SEEMS TO ME TO STRETCH THE REGS; AND COMMON SENSE; TO THE LIMIT.

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.