Am I right in understanding that you have FieldA triggering a lookup to populate FieldB which should then be triggering a lookup to populate FieldC, etc.?  

I've had issues with stacked lookups like this.

If I've misunderstood the situation, then this information won't help much.  But if it is the case, then maybe this could be useful:

1. I had a similar issue while in 10.1 update 3 - where a lookup was triggered off of a field that was being populated by another lookup, and it was not consistently triggering the change event of the first field and thus not consistently calling the trigger ('change') to kickoff the second lookip.  I ended up working around it by creating database views and stored procedures to eliminate a step in my process and reduce the number of lookups.  I don't know if that would work for you though.

2. Alternately, you may want to consider upgrading to version 10.2 because it added event listeners for lookupstarted and lookupcomplete (whereas 10.1 update 3 only has a listener for completion of lookups occurring with form load, onloadlookup).  If you were to upgrade to 10.2, the Javascript would be something like this (you would change the 'Field1' to whatever field is kicking off the very first lookup - this assumes it is #q1):

$(document).on("lookupcomplete", function (event) {
  if (event.triggerId == "Field1") {
    $('.hf-fly-from-filter input').val($('.travel-type input').val());
    $('.hf-fly-from-filter input').trigger('change');
  }
});