Narrative:

While on a simulated engine failure to a straight-in landing at runway 2l1; I called larimore traffic 5 mi out and announced my position (5 mi west; 3500 ft descending) and intentions. PA28 announced they were also at larimore; over the field at 2400 ft going to be entering a left downwind for runway 12. 2l1 runway 12 is a r-hand pattern; so I verified this with the other aircraft that they were in fact on a left downwind for runway 12. PA28 confirmed they were overflying the field and entering a left downwind for runway 12. My student and I began scanning the area where the traffic reported in order to find it. I announced my position again at 2.5 mi west of the field at 2500 ft; as well as intentions to land straight-in runway 12. At this time; PA28 said; 'we have larimore traffic in sight;' and passed roughly 100 yards off my right wing. This placed them on a high; extended right downwind for runway 12. The landing took place without incident. Contributing to this was that my student and I concentrated our scan on the area of the left downwind where the traffic reported itself; and omitted the rest of the sky. We would probably have seen the traffic earlier had we continued to scan the rest of the sky. Also; at the announcement there was traffic at larimore; and not having them in sight; I should've broken off the simulated engine failure and entered the pattern in a standard direction; rather than the straight-in we were attempting. Had I done this; the conflict may not have taken place. I would note; however; that proper position reporting is essential while in the traffic pattern. Based on the reports of PA28's position; I figured we would be into the airport before he exited his downwind; which is why I continued the approach. However; due to him improperly reporting his position; this incident occurred.

Related reports:

Google
 

Original NASA ASRS Text

Title: PA28 INSTRUCTOR PLT WHILE GIVING ENG OUT INSTRUCTION ENCOUNTERS ANOTHER ACFT ON FINAL AND TAKES EVASIVE ACTION.

Narrative: WHILE ON A SIMULATED ENG FAILURE TO A STRAIGHT-IN LNDG AT RWY 2L1; I CALLED LARIMORE TFC 5 MI OUT AND ANNOUNCED MY POS (5 MI W; 3500 FT DSNDING) AND INTENTIONS. PA28 ANNOUNCED THEY WERE ALSO AT LARIMORE; OVER THE FIELD AT 2400 FT GOING TO BE ENTERING A L DOWNWIND FOR RWY 12. 2L1 RWY 12 IS A R-HAND PATTERN; SO I VERIFIED THIS WITH THE OTHER ACFT THAT THEY WERE IN FACT ON A L DOWNWIND FOR RWY 12. PA28 CONFIRMED THEY WERE OVERFLYING THE FIELD AND ENTERING A L DOWNWIND FOR RWY 12. MY STUDENT AND I BEGAN SCANNING THE AREA WHERE THE TFC RPTED IN ORDER TO FIND IT. I ANNOUNCED MY POS AGAIN AT 2.5 MI W OF THE FIELD AT 2500 FT; AS WELL AS INTENTIONS TO LAND STRAIGHT-IN RWY 12. AT THIS TIME; PA28 SAID; 'WE HAVE LARIMORE TFC IN SIGHT;' AND PASSED ROUGHLY 100 YARDS OFF MY R WING. THIS PLACED THEM ON A HIGH; EXTENDED R DOWNWIND FOR RWY 12. THE LNDG TOOK PLACE WITHOUT INCIDENT. CONTRIBUTING TO THIS WAS THAT MY STUDENT AND I CONCENTRATED OUR SCAN ON THE AREA OF THE L DOWNWIND WHERE THE TFC RPTED ITSELF; AND OMITTED THE REST OF THE SKY. WE WOULD PROBABLY HAVE SEEN THE TFC EARLIER HAD WE CONTINUED TO SCAN THE REST OF THE SKY. ALSO; AT THE ANNOUNCEMENT THERE WAS TFC AT LARIMORE; AND NOT HAVING THEM IN SIGHT; I SHOULD'VE BROKEN OFF THE SIMULATED ENG FAILURE AND ENTERED THE PATTERN IN A STANDARD DIRECTION; RATHER THAN THE STRAIGHT-IN WE WERE ATTEMPTING. HAD I DONE THIS; THE CONFLICT MAY NOT HAVE TAKEN PLACE. I WOULD NOTE; HOWEVER; THAT PROPER POS RPTING IS ESSENTIAL WHILE IN THE TFC PATTERN. BASED ON THE RPTS OF PA28'S POS; I FIGURED WE WOULD BE INTO THE ARPT BEFORE HE EXITED HIS DOWNWIND; WHICH IS WHY I CONTINUED THE APCH. HOWEVER; DUE TO HIM IMPROPERLY RPTING HIS POS; THIS INCIDENT OCCURRED.

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