A typical example of how useful chat AI (#chatgpt) is compared to a traditional web search (#google #search - I’m told tagging my posts will increase engagement 😉). I’m debugging some stuff on Windows on an M1 Mac through Parallels. I'm using an MSDN version of Windows but classically MSDN has hundreds of options to choose from. I see “Windows 11 Professional N - Retail” on the list and forget what the “N” means—it's been years since I've used #windows.

A Google search returns links that send me down a rabbit hole.

I ask #chatgpt via @macgpt the same question and answers the question in the second sentence.

Sure the language model learns from the same sources but it has very rarely failed me, whereas Google search fails me more often that I’m happy with.

Quick analysis of the Austin Intl (#KAUS) incident involving #WN708 & #FX1432. From the ATC comms it looks like the Southwest aircraft was cleared for takeoff from RWY 18L with ample time for it to clear the runway for the landing Fedex aircraft. For some reason it took Southwest 708 39s after clearance to start its takeoff roll.

The weather at the time was freezing fog with 0.25 miles visibility (402 meters). Runway Visual Range was 1200 feet (365 meters). The tower controller would not have been able to see the aircraft at the threshold from the tower in these conditions.

Once the controller realised the serious conflict he instructed the Southwest aircraft to abort, and although some of the ATC comms is missing, it is likely that they had reached V1 and had to continue the takeoff sequence.

Soutwest was instructed to fly a heading of 170 which is a slight left turn after passing 500ft. As Fedex was now conduction a missed approach it is required to turn left at 1000ft on a heading of 040. This is why the controller now instructed Southwest to turn right.

Fedex 1432 landed safely after conducting the missed approach and Southwest continued onto Cancun.