Narrative:

My aircraft overtook and flew over the top of the PA28. I never saw the other aircraft. I believe the other aircraft had made a radio call on final; but I cannot recall being aware of it. The event occurred on final for runway 7 at ZZZ. I recall reporting downwind and final on the CTAF. The PAPI was OTS (by NOTAM). Runway 7 is right traffic at ZZZ creating a larger blind spot for low wing aircraft than left traffic. The other aircraft informed me that I had overflown him as I crossed the runway threshold. His comment was that it was very close. The other aircraft executed a go around on the right. Considering the other aircraft types in the pattern (PA28; I believe there were 2 or 3) I should have: 1) increased my final leg length (I was a bit high on final). 2) slowed down (I was at 87 KTS) somewhat. 3) had better situational awareness of the other aircraft based on their radio calls. I was at the end of an IFR flight plan with VMC at the destination; pretty much cavu. ZZZ was a new airport for me. I canceled IFR 2 mi from ZZZ and joined the pattern. At first I was on a path for left downwind for runway 7 but corrected that mid field to a right downwind. I flew a 'tight' pattern (within 1 mi). In consideration of existing traffic; a wider pattern would have been more prudent and allowed more time to form a better visualization of traffic. I believe right traffic was a factor in flying the base and final closer in. I am thankful for the chance to share this information. (Both for this program and because I'm still around to tell the story.) this has certainly raised my awareness of how this can happen to anyone.

Related reports:

Google
 

Original NASA ASRS Text

Title: M20 PILOT REPORTS NMAC WITH PA28 THAT IS NEVER SEEN; AT RWY THRESHOLD CAUSING PA28 PILOT TO GAR.

Narrative: MY ACFT OVERTOOK AND FLEW OVER THE TOP OF THE PA28. I NEVER SAW THE OTHER ACFT. I BELIEVE THE OTHER ACFT HAD MADE A RADIO CALL ON FINAL; BUT I CANNOT RECALL BEING AWARE OF IT. THE EVENT OCCURRED ON FINAL FOR RWY 7 AT ZZZ. I RECALL RPTING DOWNWIND AND FINAL ON THE CTAF. THE PAPI WAS OTS (BY NOTAM). RWY 7 IS R TFC AT ZZZ CREATING A LARGER BLIND SPOT FOR LOW WING ACFT THAN L TFC. THE OTHER ACFT INFORMED ME THAT I HAD OVERFLOWN HIM AS I CROSSED THE RWY THRESHOLD. HIS COMMENT WAS THAT IT WAS VERY CLOSE. THE OTHER ACFT EXECUTED A GAR ON THE R. CONSIDERING THE OTHER ACFT TYPES IN THE PATTERN (PA28; I BELIEVE THERE WERE 2 OR 3) I SHOULD HAVE: 1) INCREASED MY FINAL LEG LENGTH (I WAS A BIT HIGH ON FINAL). 2) SLOWED DOWN (I WAS AT 87 KTS) SOMEWHAT. 3) HAD BETTER SITUATIONAL AWARENESS OF THE OTHER ACFT BASED ON THEIR RADIO CALLS. I WAS AT THE END OF AN IFR FLT PLAN WITH VMC AT THE DEST; PRETTY MUCH CAVU. ZZZ WAS A NEW ARPT FOR ME. I CANCELED IFR 2 MI FROM ZZZ AND JOINED THE PATTERN. AT FIRST I WAS ON A PATH FOR L DOWNWIND FOR RWY 7 BUT CORRECTED THAT MID FIELD TO A R DOWNWIND. I FLEW A 'TIGHT' PATTERN (WITHIN 1 MI). IN CONSIDERATION OF EXISTING TFC; A WIDER PATTERN WOULD HAVE BEEN MORE PRUDENT AND ALLOWED MORE TIME TO FORM A BETTER VISUALIZATION OF TFC. I BELIEVE R TFC WAS A FACTOR IN FLYING THE BASE AND FINAL CLOSER IN. I AM THANKFUL FOR THE CHANCE TO SHARE THIS INFO. (BOTH FOR THIS PROGRAM AND BECAUSE I'M STILL AROUND TO TELL THE STORY.) THIS HAS CERTAINLY RAISED MY AWARENESS OF HOW THIS CAN HAPPEN TO ANYONE.

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