ASRS 1994221

Reporter 1

Landing Runway 35L, I saw Aircraft Y on the taxiway adjacent to the runway, as Taxiway H3 was approaching. It appeared stationary; I can't say with a 100% confidence, but his taxi light was not on. In either case, as I was committing to exit the runway at the high speed Taxiway H3, Ground gave us instruction to take the next Taxiway H2. We were unable to comply, since the clearance was too late. I [saw] Aircraft Y moving slowly and my exit speed was too high to slam on the brakes. I continued my exit by making the right turn on Taxiway Hotel from H3, since that was the safest course of action at that time. I don't know if Aircraft Y was moving slowly or at all, but it appeared to me that he was not. Better planning between Tower and Ground Control would have helped in communicating the exit point. In the future, in the absence of a clearance, I will assume he is moving and take the next high speed.

Reporter 2

While landing Runway 35L at MCO, following a bird strike in the middle of my windscreen at 800 ft. on the roll-out, we planned our exit for Taxiway H3, approximately two-thirds of the way down the runway, on the high speed exit. As we exited, Aircraft Y on parallel on H, after landing ahead of us same runway, had not received a taxi clearance and their landing light was off, were stopped on H facing northbound. As we crossed the runway edge line on H3, Tower Controller called and asked us to roll to H2 much further down the runway. We had not slowed to a speed that would have permitted a safe turn back on to the runway and continued to H2 as the request from ATC was too late into our exit. We continued taxi to park. We could have slowed down with minimal braking and exit closer to the far end of the runway, However, usually this would be an annoyance to the Local Controller, due to aircraft in trail behind us landing having to go-around if we were still on the runway.