N52F04
RECEIPT #004
FILED UNDER: DINER-N52F
DATE: 12/11/95
EMPLOYEE #62
I was able to track down Mr. Hazen’s location, and it seems he’s come in from Bixby Park via a private jet. And the scene around the park isn’t great. Mr. Hazen has been wreaking havoc on the surrounding area, causing machines and electronics to malfunction, and causing general chaos. He’s a rather demanding customer, that’s for sure. From my rough estimates, Mr. Hazen has been to the park at least 20 times just today. Of course, that isn’t even counting his trips elsewhere in SoCal.
To serve Mr. Hazen, we will need to figure out a way to charter him a new flight to Ottawa and designate Bixby as a strict no-flight zone. While typically, I’d tip my hat towards #71, I think I might be able to approach this conundrum a bit more technologically. According to Marcelle, one of the new features of our latest CaDCom version is a sort of flight tracker and disruptor. If it works how she says it should work, all I need to do is find the peak of the air traffic near Bixby and then activate the flight disruptor to clue in air control that a public park isn’t a very safe makeshift airport. Obviously, this only works with anomalous airports, but if it works, it’ll make cleaning up the rest of Miss. Andrews’ mess easier.
The only problem is I can’t get my CaDCom to work within 100 feet of Bixby due to the frequency of Mr. Hazen’s numerous trips. So… I’m open to ideas on how to at least get an opening here. After observing his behavior, I feel pretty confident in saying that Mr. Hazen arrived at Bixby around 2 o’clock. I’ve seen him indulge in multiple five-finger discounts around the park. Maybe we can use that to our advantage somehow?