After receiving clearance for a visual approach to runway 13; a crew performed an 'south' turn maneu...

Narrative:

We were approximately 5nm final for runway 13. Jax approach was late handing us off to mco approach so consequently we were slightly high. Immediately on check in with mco approach we were cleared for a visual 13 and told to contact tower. I [pilot in command and pilot flying] started a small south turn to the south while pilot monitoring (pm) was changing frequencies. Wrong frequency was temporarily loaded which added to the confusion. [The] chart listed an ATIS frequency; but no ATIS was being broadcasted; only AWOS. RA event occurred around 2;000 feet in descent during south turn. Other aircraft was on departure 31. After checking in with tower they cleared us for a right downwind runway 31. We climbed to tpa and resumed normal flight and landing with no other issues. I queried ATC and told them mco gave us a visual to 13. Tower said they would call mco and discuss the issue. ATIS could have prevented all of this as well as a proper hand off and coordination between app and tower. Not sure why at xa:00 local time that the tower was not broadcasting an ATIS. If we knew that runway 31 was in use none of this would have happened. According to tower they said they don't have the funding for an ATIS. If that's the case then the chart needs to be updated or a NOTAM needs to be issued.

Original NASA ASRS Text

Title: After receiving clearance for a visual approach to Runway 13; a crew performed an 'S' turn maneuver to lose altitude and experienced a TCAS Resolution Advisory to avoid conflict with an aircraft that had departed the opposing runway. Tower cleared the crew for a downwind approach to Runway 31.

Narrative: We were approximately 5nm final for runway 13. JAX approach was late handing us off to MCO approach so consequently we were slightly high. Immediately on check in with MCO approach we were cleared for a visual 13 and told to contact tower. I [Pilot in Command and Pilot Flying] started a small S turn to the south while Pilot Monitoring (PM) was changing frequencies. Wrong frequency was temporarily loaded which added to the confusion. [The] chart listed an ATIS frequency; but no ATIS was being broadcasted; only AWOS. RA event occurred around 2;000 feet in descent during S turn. Other aircraft was on departure 31. After checking in with tower they cleared us for a right downwind runway 31. We climbed to TPA and resumed normal flight and landing with no other issues. I queried ATC and told them MCO gave us a visual to 13. Tower said they would call MCO and discuss the issue. ATIS could have prevented all of this as well as a proper hand off and coordination between app and tower. Not sure why at XA:00 local time that the tower was not broadcasting an ATIS. If we knew that runway 31 was in use none of this would have happened. According to tower they said they don't have the funding for an ATIS. If that's the case then the chart needs to be updated or a NOTAM needs to be issued.

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.

Attributes
ACN	1261019
Time
Date	201505
Local Time Of Day	0601-1200
Place
Locale Reference	MCO.Airport
State Reference	FL
Environment
Flight Conditions	VMC
Aircraft 1
Make Model Name	Small Transport Low Wing 2 Turbojet Eng
Operating Under FAR Part	Part 91
Flight Phase	Initial Approach
Flight Plan	IFR
Person 1
Function	Pilot Flying Captain
Qualification	Flight Crew Air Transport Pilot (ATP)
Person 2
Function	Pilot Not Flying First Officer
Events
Anomaly	ATC Issue All Types Conflict Airborne Conflict

After receiving clearance for a visual approach to runway 13; a crew performed an 'south' turn maneuver to lose altitude and experienced a TCAS resolution advisory to avoid conflict with an aircraft that had departed the opposing runway. Tower cleared the crew for a downwind approach to runway 31.