PA34 practice approach to rap experienced near midair collision on short final.

Attributes
ACN	574404
Time
Date	200302
Day	Thu
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : rap.airport
State Reference	SD
Altitude	agl single value : 400
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tower : rap.tower tower : bwi.tower
Operator	general aviation : personal
Make Model Name	PA-34-220T Turbo Seneca III
Operating Under FAR Part	Part 91
Navigation In Use	ils localizer & glide slope : 32
Flight Phase	descent : approach
Route In Use	approach : instrument precision
Flight Plan	VFR
Aircraft 2
Controlling Facilities	tower : rap.tower
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Operating Under FAR Part	Part 91
Flight Phase	descent : approach
Person 1
Affiliation	other
Function	observation : passenger
Qualification	pilot : private pilot : instrument pilot : multi engine
Experience	flight time last 90 days : 25 flight time total : 1084 flight time type : 120
ASRS Report	574404
Person 2
Affiliation	other
Function	flight crew : single pilot oversight : pic
Events
Anomaly	conflict : airborne critical conflict : nmac non adherence : far
Independent Detector	other flight crewa other flight crewb
Resolutory Action	flight crew : executed missed approach
Miss Distance	horizontal : 0 vertical : 150
Supplementary
Problem Areas	Flight Crew Human Performance ATC Human Performance
Primary Problem	ATC Human Performance

Narrative:

2 pilots, no passenger on board. Pilot #1 PIC and safety pilot. Pilot #2 flying practice ILS runway 32 to rapid city regional airport using vision limiting device. This was the third practice approach during this session. We were under VFR flight rules. However, we wre talking to ellsworth approach/departure control and to the rapid city tower. Ellsworth vectored us for the ILS runway 32 approach, cleared us for the approach and handed us off to the tower. We contacted the tower. They advised us to 'call ranch OM inbound.' we called 'ranch' and tower cleared us for the option to runway 32. As we were nearing the end of the approach, another aircraft contacted the tower and transmitted something to the effect 'where do I go, there is another aircraft on short final?' at the same time, I (pilot #1) saw the aircraft and immediately told the pilot (#2) flying 'my airplane.' I pwred up and started a climbing left turn to avoid any further potential conflict. We passed 150-200 ft directly over the top of the other aircraft that was turning a short final for runway 32. We contacted the tower and said 'where did that guy come from?' no response from the tower. We then called a missed approach and tower handed us off to ellsworth with no other comment. We do not know where the other aircraft went. I assume he landed. We do not remember any tower communications with the other aircraft. We did not receive any TA from the tower about this aircraft.

Original NASA ASRS Text

Title: PA34 PRACTICE APCH TO RAP EXPERIENCED NMAC ON SHORT FINAL.

Narrative: 2 PLTS, NO PAX ON BOARD. PLT #1 PIC AND SAFETY PLT. PLT #2 FLYING PRACTICE ILS RWY 32 TO RAPID CITY REGIONAL ARPT USING VISION LIMITING DEVICE. THIS WAS THE THIRD PRACTICE APCH DURING THIS SESSION. WE WERE UNDER VFR FLT RULES. HOWEVER, WE WRE TALKING TO ELLSWORTH APCH/DEP CTL AND TO THE RAPID CITY TWR. ELLSWORTH VECTORED US FOR THE ILS RWY 32 APCH, CLRED US FOR THE APCH AND HANDED US OFF TO THE TWR. WE CONTACTED THE TWR. THEY ADVISED US TO 'CALL RANCH OM INBOUND.' WE CALLED 'RANCH' AND TWR CLRED US FOR THE OPTION TO RWY 32. AS WE WERE NEARING THE END OF THE APCH, ANOTHER ACFT CONTACTED THE TWR AND XMITTED SOMETHING TO THE EFFECT 'WHERE DO I GO, THERE IS ANOTHER ACFT ON SHORT FINAL?' AT THE SAME TIME, I (PLT #1) SAW THE ACFT AND IMMEDIATELY TOLD THE PLT (#2) FLYING 'MY AIRPLANE.' I PWRED UP AND STARTED A CLBING L TURN TO AVOID ANY FURTHER POTENTIAL CONFLICT. WE PASSED 150-200 FT DIRECTLY OVER THE TOP OF THE OTHER ACFT THAT WAS TURNING A SHORT FINAL FOR RWY 32. WE CONTACTED THE TWR AND SAID 'WHERE DID THAT GUY COME FROM?' NO RESPONSE FROM THE TWR. WE THEN CALLED A MISSED APCH AND TWR HANDED US OFF TO ELLSWORTH WITH NO OTHER COMMENT. WE DO NOT KNOW WHERE THE OTHER ACFT WENT. I ASSUME HE LANDED. WE DO NOT REMEMBER ANY TWR COMS WITH THE OTHER ACFT. WE DID NOT RECEIVE ANY TA FROM THE TWR ABOUT THIS ACFT.

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.