Date: 202102
Local time of day: 0601-1200
Location: HOU.Airport, TX
Flight conditions: VMC
Aircraft: Challenger 300
Operator: Fractional
Operating under: Part 135
Flight plan: IFR
Flight phase: Taxi
ATC / advisory: Ground HOU
Second aircraft: Medium Transport; Low Wing; 2 Turbojet Eng
Reporter organization: Fractional
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Communication Breakdown
Second reporter function: Pilot Not Flying; First Officer
Anomaly: ATC Issue All Types; Conflict Ground Conflict; Critical; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Took Evasive Action
Contributing factors: Procedure
Primary problem: Procedure

Narrative: During taxi to Runway 31L; ground control told us to hold short of the approach end of Runway 22 at Taxiway Z. As another aircraft was landing; ground told us to cross Runway 22 In front of the aircraft on landing roll and told that aircraft to give way to us. As we began to cross in front of the aircraft on landing roll; there was no indication that the aircraft was slowing down to give way to us. So I stopped our aircraft and the aircraft on landing roll passed in front of us. Ground said that we shouldn't have stopped.This event was caused by ground control setting up a disaster scenario by wanting us to cross in front of the aircraft on landing roll. If anything went wrong; like brake failure of the landing aircraft; then there would have been a potentially catastrophic aircraft accident.In the future; ground shouldn't cross aircraft in front of other aircraft on landing roll unless they are positive that the aircraft on landing roll has slowed down sufficiently to be safe.


Second narrative: We were instructed to taxi from FBO to '[Runway] 31L via Zulu; hold short approach end [Runway] 22 at Zulu'. We exited the FBO ramp onto Zulu; turned left towards [Runway] 22 and noticed that [Taxiway] Zulu terminates before the approach end of [Runway] 22; and it becomes [Taxiway] Yankee. We discussed this on the flight deck that the taxi instructions should have been clearer because you can't really hold short of [Runway] 22 on Zulu; you would actually either hold short of [Runway] 22 approach on Yankee; or hold short of Yankee on Zulu. In any case; the Captain as PF (Pilot Flying) exercised some good judgement and decided to stop a bit back from Yankee; at least from the sign anyways. It's hard to figure where Zulu actually ended. That way we could respond to Ground if they modified their instructions to hold back further. Whatever is the case with Zulu or Yankee; we stopped and awaited further instructions. We noticed a bizjet (Aircraft Y) landing on [Runway] 4 so we suspected we were being held from crossing the approach end of [Runway] 22 (same as rollout end of [Runway] 4) due to the landing traffic. After a short wait; we heard ground instruct Aircraft Y which was now rolling out to 'give way to Aircraft X; he will be crossing at the end of the runway in front of you'. I cannot recall if the other aircraft acknowledged. The next thing we both heard was 'Aircraft X; cross Runway 22 and continue via Kilo'. I turned all the lights on and the Captain started to move forward. I looked right to clear and noticed the landing Aircraft Y was very close; it seemed to me he was past Bravo and Kilo 2 where I presumed he would have turned off; that his reversers were still deployed; and he was rolling very fast for so close to the end of the runway. I said 'STOP; we're not clear' or words to that effect and the Captain immediately stopped as he was now seeing Aircraft Y appear large in my windshield. It may have been hidden beside my windshield side pillar previously. We both agreed it would not have been pretty had we gone across the runway as it clearly appeared Aircraft Y was landing fast and rolling out long; and more importantly; evidently not giving way to us. After just a few seconds; Ground said 'Aircraft X; you're not moving' and we responded that it was not safe to do so. Ground replied; 'Aircraft Y is giving way to you' or words to that effect; and we replied that wasn't the case. After a few more seconds Aircraft Y exited onto Kilo in front of us; and Ground then instructed us to cross the runway and continue onto Kilo on our taxi to [Runway] 31L. Ground and Tower frequencies were combined per ATIS onto tower frequency 118.7; we were always using it; but when Aircraft Y cleared in front of us and we followed him until we turned left onto Charlie; we never heard him. Our subsequent taxi and departure was uneventful.The confusing or incorrect taxi instructions provided (i.e.; is it Zulu or Yankee to hold short) started us off with noticing ATC peculiarities as we spoke to Ground. The other aircraft not giving way to us; or appearing to do so; was the major cause of this averted conflict. Combining Tower and Ground on one frequency may also have caused some confusion; because the tower cab can hear everything but in the aircraft we can only actively hear the frequency we're currently using.First off; I think our alertness was the link in the chain that prevented an incident (or worse). I think that ATC made a procedural error in directing us to cross in front of the landing traffic without adequate time/distance to do so. I recommend [Company] request an official copy of the tape from the FAA if possible for review and development of lessons learned.


Synopsis: CL-300 Flight Crew reported ATC created a runway incursion resulting in a critical ground conflict.