I seem to be thinking like a zombie this morning, so pray ignore anything I say that's patently ridiculous.
Ignore something? Ridiculous! No, seriously, it's pretty simple but I'm a crummy teacher. It's true tho I'm right and hey, Happy Birthday!


ohno doggie!

Are you sure they'd do all these local records in GMT (UST)?
Not necessarily, but it seems likely. I've studied a few air-related things that tend to use GMT for everything - accident reports, FDR data from US air crashes, etc. NTSB uses GMT as standard, British obviously would, for the stuff that covers large areas, actual flights, etc. It's a coincidence I think 103's explosion time given in GMT as usual was also about exactly at the Greenwich Mean itself local time.
Local airport ops, it might go either way. Passengers might get a wall of clocks, local and neighboring zones, employees in the break room and punch clock maybe local, the luggage system ??? I'm guessing on all this. How does it work in China? Etc, I dunno. On it's own, the time zone is not evident. It's in the clues.
We have the timing for the bag going through station 206 as 13.07, on that actual printout. The finish time for KM180 going through the station was given on the hand-written worksheet as either 13.10 or 13.16. (Or did it say 1.10 or 1.16, I don't remember.) We were told that the coder probably took these times from his watch, which might have been a few minutes out in comparison to the computer clocks.
Huh, true that's what we've heard. Hadn't lines those up yet. To be sure I
double checked and Z (zulu) means GMT or Universal time. So ... they set their watches to GMT? Maybe they switch back to local only as they drive home? Either that or the coders just corrected it to GMT in writing, but 1307 is Z, they've all SAID the two line up, and normal operations would run better if these logs were all on the same system consistently.
I do see where there's a CT possibility here... May be too small a rabbit to chase, but...
Tell me again, slowly, why you think the printout is in GMT.
Rolfe.
Certainly. I'm doing this very slowly, but the best way is to make sure you read it that way.

First, let's ignore if anything in the printout is or isn't in GMT or local time. To be honest I haven't looked it over from all sides. The main thing is that
all times in the printout are internally consistent. They're in the same time zone, whether the Z is there or not.
So, our 8849 gets coded at 1307, stored and then sent to gate 44 at 1523. Something in the top portion called BF reads 1512, so this could be start of loading. Items start going to 44 five minutes later, get loaded we presume, as late as about 1615. The plane moves to gate 41, two items there after 1631. Something called EF, (end loading?) reads 1652. The court had "departure" one minute after that. That too is consistent, if they mean push-off before departure (app. 1700?). The printout was made 2:40 after this if all times are consistent. Do we agree on that?
Now, there are other ways to look at it from there - eg, how does this line up with Heathrow? 103 took off about 18:25 UTC/GMT/local. If the Frankfurt departure of 103A was around 1700 in GMT, this would allow about 1 1/2 hr to get stuff to London and on the other plane. If that was local time, there's 2 1/2 hours. Either makes sense to me.
So we're down to which of those times to London makes more sense, how standard GMT is for record-keeping, how reliably Z means UTC, and whether a 30 min post-explosion search or 2-hours-after routine loading report makes more sense.
Again, happy birthday, and thanks for taking the time to sort this out.
ETA: It might not have helped, I suck at this. Just think about the times until it makes sense.