Turboprop flight crew reported an issue with conflicting traffic during arrival to myf.

Attributes
ACN	1447809
Time
Date	201705
Place
Locale Reference	MYF.Airport
State Reference	CA
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Make Model Name	Light Transport
Operating Under FAR Part	Part 91
Flight Phase	Initial Approach
Route In Use	Visual Approach
Flight Plan	IFR
Aircraft 2
Make Model Name	Cessna 152
Operating Under FAR Part	Part 91
Flight Phase	Climb
Person 1
Function	Pilot Flying First Officer
Qualification	Flight Crew Multiengine Flight Crew Flight Instructor Flight Crew Air Transport Pilot (ATP)
Experience	Flight Crew Last 90 Days 90 Flight Crew Total 4200 Flight Crew Type 600
Person 2
Function	Captain Pilot Not Flying
Qualification	Flight Crew Air Transport Pilot (ATP)
Experience	Flight Crew Last 90 Days 150 Flight Crew Total 3500 Flight Crew Type 1400
Events
Anomaly	Conflict Airborne Conflict Deviation - Altitude Excursion From Assigned Altitude Deviation - Procedural Published Material / Policy Deviation - Procedural Clearance

Narrative:

We were flying on an IFR flight plan and were cleared for the visual at approximately the extended center line at miramar to 28R at montgomery and to stay at or above 3000 crossing the 52 freeway. We switched frequencies and had trouble checking in due to high traffic volume on the radio frequency. I slowed to approximately 160 knots to give more time to check in and crossed the 52 at approximately 3800 feet. We heard tower talking to a C152 departing downwind calling us out as traffic to them. We still were not able to break into radio traffic and started looking for the 152. We saw the 152 on our TCAS and I stopped our descent at around 3500 feet to look for the traffic. At this time there was a break in radio traffic and montgomery tower called out the 152 traffic to us at the exact time we received an RA from our TCAS and climbed to approximately 3700 feet. The captain answered montgomery tower stating we were performing an RA climb and looking for traffic. Almost immediately I was able to see the traffic out the left side of the aircraft and at that time traffic was no factor. We continued to enter right base for runway 28R and landed uneventfully. We contacted tower to see if we can all work out a better arrival from the north for us so this would not happen again. In the morning at montgomery there is very little if not no traffic when we arrived so a visual to 28R from the north is still feasible. In the afternoon however there is an abundance of traffic and we all decided that it would be better to perform the ILS approach to 28R for traffic confliction. We have unofficially incorporated this procedure into our flights into montgomery and are working to incorporate this into our SOP. It has only been a few days past but this does seem to work better.

Original NASA ASRS Text

Title: Turboprop flight crew reported an issue with conflicting traffic during arrival to MYF.

Narrative: We were flying on an IFR flight plan and were cleared for the visual at approximately the extended center line at Miramar to 28R at Montgomery and to stay at or above 3000 crossing the 52 freeway. We switched frequencies and had trouble checking in due to high traffic volume on the radio frequency. I slowed to approximately 160 knots to give more time to check in and crossed the 52 at approximately 3800 feet. We heard tower talking to a C152 departing downwind calling us out as traffic to them. We still were not able to break into radio traffic and started looking for the 152. We saw the 152 on our TCAS and I stopped our descent at around 3500 feet to look for the traffic. At this time there was a break in radio traffic and Montgomery Tower called out the 152 traffic to us at the exact time we received an RA from our TCAS and climbed to approximately 3700 feet. The Captain answered Montgomery tower stating we were performing an RA climb and looking for traffic. Almost immediately I was able to see the traffic out the left side of the aircraft and at that time traffic was no factor. We continued to enter right base for runway 28R and landed uneventfully. We contacted tower to see if we can all work out a better arrival from the north for us so this would not happen again. In the morning at Montgomery there is very little if not no traffic when we arrived so a visual to 28R from the north is still feasible. In the afternoon however there is an abundance of traffic and we all decided that it would be better to perform the ILS approach to 28R for traffic confliction. We have unofficially incorporated this procedure into our flights into Montgomery and are working to incorporate this into our SOP. It has only been a few days past but this does seem to work better.

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