Date: 201902
Local time of day: 1201-1800
Location: MCO.Airport, FL
Light: Dusk
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Airspace: Class B MCO
ATC / advisory: TRACON F11
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; Captain
Reporter qualification: Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument
Human factors: Communication Breakdown
Second reporter function: Pilot Flying; First Officer
Anomaly: ATC Issue All Types; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Became Reoriented
Contributing factors: Chart Or Publication
Primary problem: Chart Or Publication

Narrative: ATC issued a clearance to a fix. I read back as 'CRUZE and descend to 1;600 feet;' but the controller meant HEWES. We programmed CRUZE into the box and the aircraft started to turn. Something didn't seem right and I looked at the approach plate and saw the altitude to cross CRUZE was 5;000 feet. I was stating to the First Officer something seemed wrong and he was saying the same thing when all of a sudden ATC started querying where we were going; and then issued an immediate 30 degree turn to the left away from traffic we had in sight. As all this was going on the controller started blaming us telling (other carrier) aircraft 'Company turned the wrong way.' We continued the approach with little more discussion about it but several more times the controller said something to (other carrier) aircraft about us making a mistake; even asking if (other carrier) aircraft wanted to go-around because of the spacing. When the controller switched us to Tower; I stated again; for the record; that we READ BACK CRUZE. The controller came back and agreed that those two fixes sound alike. They ought to fix that. I doubt we're the first ones to do that.


Second narrative: We were initially cleared for visual to 36L. About ten miles ATC asked if we wanted 35R. We accepted and transitioned to 35R and at 4;500 feet heading towards final for 35R (we understood and read back) we were cleared to CRUZE fix on 35R and descend to 1;600 feet. I began a turn to CRUZE but it looked too far out to be at 1;600 feet; and approach plate verified CRUZE at 5;000 feet. I immediately asked PM (Pilot Monitoring) to query the controller as to CRUZE at 1;600 feet. PM asked ATC and they said we were cleared to (HEWES not CRUZE) and we turned wrong way and to immediately turn to HEWES which was to our left. I disconnected autopilot and turned towards HEWES and we were cleared [for the] approach. Another aircraft was outside CRUZE and ATC asked if they needed a go-around. We continued approach to 35R and landed uneventfully. PM told ATC that we understood and read back on radio that we were cleared to CRUZE and ATC did not catch our readback. ATC response was 'Yeah; they (CRUZE and HEWES) sound a lot alike.'


Synopsis: B737 flight crew reported a track heading deviation during approach to MCO airport.  Similar sounding fix names CRUZE and HUWES were cited as a contributing factor.