Narrative:

We departed iws in small transport X on an IFR flight plan for the purpose of practice approachs at vct. Approximately 15 mi from the IAF I transmitted on CTAF frequency 122.7 our position, altitude and intentions. Numerous other VFR aircraft were on 122.7. I reported the LOM vc outbnd with altitude on 122.7 and 135.05 with ZHU. On procedure turn we heard center talking to a navy aircraft for approach to vct but didn't get the identify. I cancelled IFR with ZHU 135.05 when inbound on the ILS approach to runway 12L at vct and announced our position on CTAF 122.7. We landed on 12L and parked on the intersection run-up os for debriefing. We noticed a navy small transport Y touch and go on 12L and head for another approach. After taking off on runway 12L, I contacted the navy aircraft and gave our position and intentions of returning to the LOM at 2000' MSL. He rogered our report. We communicated our positions in accordance with aim procedures, but didn't hear any reports of the navy aircraft until inbound from the LOM. We were descending through 1500' MSL inbound on the VOR to 12L when navy small transport Y passed about 300' underneath us from 2 O'clock to 8 O'clock. He called us on 122.7 and stated that this was the second time that we had almost run over him. The WX was about 4000' scattered, 22000' overcast, with 7-10 mi visibility and wasn't a factor. Problem: when aircraft are on IFR clrncs to uncontrolled fields, most of the time the local CTAF/unicom frequency is not used until final fix inbound. Therefore, many aircraft could monitor their positions while VFR, but not know about the IFR aircraft. FAA needs to develop a procedure similar to advising the tower/unicom for approaching IFR cleared aircraft into the uncontrolled traffic pattern. This is especially hazardous on approachs such as vet with procedure turn and missed approach altitudes published as the same altitude.

Related reports:

Google
 

Original NASA ASRS Text

Title: SINGLE ENGINE SMT MAKING PRACTICE APCH AT NON TWR ARPT HAS CONFLICT WITH TWIN SMT ALSO ON PRACTICE APCH AND NOT ANNOUNCING POSITION.

Narrative: WE DEPARTED IWS IN SMT X ON AN IFR FLT PLAN FOR THE PURPOSE OF PRACTICE APCHS AT VCT. APPROX 15 MI FROM THE IAF I XMITTED ON CTAF FREQ 122.7 OUR POS, ALT AND INTENTIONS. NUMEROUS OTHER VFR ACFT WERE ON 122.7. I RPTED THE LOM VC OUTBND WITH ALT ON 122.7 AND 135.05 WITH ZHU. ON PROC TURN WE HEARD CENTER TALKING TO A NAVY ACFT FOR APCH TO VCT BUT DIDN'T GET THE IDENT. I CANCELLED IFR WITH ZHU 135.05 WHEN INBND ON THE ILS APCH TO RWY 12L AT VCT AND ANNOUNCED OUR POS ON CTAF 122.7. WE LANDED ON 12L AND PARKED ON THE INTXN RUN-UP OS FOR DEBRIEFING. WE NOTICED A NAVY SMT Y TOUCH AND GO ON 12L AND HEAD FOR ANOTHER APCH. AFTER TAKING OFF ON RWY 12L, I CONTACTED THE NAVY ACFT AND GAVE OUR POS AND INTENTIONS OF RETURNING TO THE LOM AT 2000' MSL. HE ROGERED OUR RPT. WE COMMUNICATED OUR POSITIONS IN ACCORDANCE WITH AIM PROCS, BUT DIDN'T HEAR ANY RPTS OF THE NAVY ACFT UNTIL INBND FROM THE LOM. WE WERE DSNDING THROUGH 1500' MSL INBND ON THE VOR TO 12L WHEN NAVY SMT Y PASSED ABOUT 300' UNDERNEATH US FROM 2 O'CLOCK TO 8 O'CLOCK. HE CALLED US ON 122.7 AND STATED THAT THIS WAS THE SECOND TIME THAT WE HAD ALMOST RUN OVER HIM. THE WX WAS ABOUT 4000' SCATTERED, 22000' OVCST, WITH 7-10 MI VISIBILITY AND WASN'T A FACTOR. PROB: WHEN ACFT ARE ON IFR CLRNCS TO UNCONTROLLED FIELDS, MOST OF THE TIME THE LCL CTAF/UNICOM FREQ IS NOT USED UNTIL FINAL FIX INBND. THEREFORE, MANY ACFT COULD MONITOR THEIR POSITIONS WHILE VFR, BUT NOT KNOW ABOUT THE IFR ACFT. FAA NEEDS TO DEVELOP A PROC SIMILAR TO ADVISING THE TWR/UNICOM FOR APCHING IFR CLRED ACFT INTO THE UNCONTROLLED TFC PATTERN. THIS IS ESPECIALLY HAZARDOUS ON APCHS SUCH AS VET WITH PROC TURN AND MISSED APCH ALTS PUBLISHED AS THE SAME ALT.

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.