Yep, I’ve got a comment on another thread with my attempt to layout this same thing.
It was funny to watch Duffy try to blame this on an L3 Harris contractor who’d installed a new router… untill someone told him that guy is a military veteran, and now he’s including that detail in his rambling ‘we are looking at everything but do not have a definitive cause as of yet’ panicked explanations.
It is very obvious that they tried to run an insanely demanding amount of data through hardware that Duffy literally said he knew could not handle it, then panicked and shut down everything when in all likelihood that was not necessary, because they could have just shut down their newfangled vibecoded SMARTslop system… and everywhere other than O’Hare’s legacy systems would have kept working as well as they have been, at worst.
Duffy said that there was ‘inconsistent radar and comms’. But multiple pilots and ATCs, I’ve seen reports of them saying no, that was all fine.
Duffy said that the new SMART auto-flight-planning system was disagreeing with what TRACONs were reporting. This is two different systems disagreeing as to where aircraft are.
Airport TRACONs are the actual radar, and are basically mostly localized to major airports that have them… the super duper networked SMART system was disagreeing with this more local and tangible, more reliable and more accurate data, and then Duffy panicked and ordered a near total groundstop… when he could have just shut off his newfangled broken bullshit.
I am 95% sure that basically this is what happened.
Like yes, its technically true that a lot of the hardware for these old systems need to be better maintained, switched over to more modern hardware, have redundant failsafes… but plugging in an entirely new software stack at the same time you’re doing a retrofit of the old systems is catastrophically stupid.
From what I can tell, my guess is that… ok so basically, apparently, the maintenance logs for actual hardware work done at O Hare are only kept on paper. It apparently took them 45 minutes to get the actual paper log indicating that (and presumably when) the L3 Harris router had been replaced… so… if somebody just said ‘yep its all good to go, trust me bro’, and they flipped the SMART system on at O Hare, but before the new router was actually fully installed/online…
Lemmy in general seems to think the FAA pulled the trigger nationwide on an untested system, and then confabulates about what it did/does.
This portion of the SMART rollout was only using it to suggest optimized routes, which a human has to approve, a solid use case for AI. It doesn’t control anything and no ATC operator has to approve its output. This was working fine for over two months in DC and Florida, and was fine for three days of full deployment before the grounding.
If SMART data disagreed with TRACON, why could they not simply ignore the new system and go on as usual?
Yep, I’ve got a comment on another thread with my attempt to layout this same thing.
It was funny to watch Duffy try to blame this on an L3 Harris contractor who’d installed a new router… untill someone told him that guy is a military veteran, and now he’s including that detail in his rambling ‘we are looking at everything but do not have a definitive cause as of yet’ panicked explanations.
It is very obvious that they tried to run an insanely demanding amount of data through hardware that Duffy literally said he knew could not handle it, then panicked and shut down everything when in all likelihood that was not necessary, because they could have just shut down their newfangled vibecoded SMARTslop system… and everywhere other than O’Hare’s legacy systems would have kept working as well as they have been, at worst.
Duffy said that there was ‘inconsistent radar and comms’. But multiple pilots and ATCs, I’ve seen reports of them saying no, that was all fine.
Duffy said that the new SMART auto-flight-planning system was disagreeing with what TRACONs were reporting. This is two different systems disagreeing as to where aircraft are.
Airport TRACONs are the actual radar, and are basically mostly localized to major airports that have them… the super duper networked SMART system was disagreeing with this more local and tangible, more reliable and more accurate data, and then Duffy panicked and ordered a near total groundstop… when he could have just shut off his newfangled broken bullshit.
I am 95% sure that basically this is what happened.
Like yes, its technically true that a lot of the hardware for these old systems need to be better maintained, switched over to more modern hardware, have redundant failsafes… but plugging in an entirely new software stack at the same time you’re doing a retrofit of the old systems is catastrophically stupid.
From what I can tell, my guess is that… ok so basically, apparently, the maintenance logs for actual hardware work done at O Hare are only kept on paper. It apparently took them 45 minutes to get the actual paper log indicating that (and presumably when) the L3 Harris router had been replaced… so… if somebody just said ‘yep its all good to go, trust me bro’, and they flipped the SMART system on at O Hare, but before the new router was actually fully installed/online…
Yeah, I think that’d do it.
Lemmy in general seems to think the FAA pulled the trigger nationwide on an untested system, and then confabulates about what it did/does.
This portion of the SMART rollout was only using it to suggest optimized routes, which a human has to approve, a solid use case for AI. It doesn’t control anything and no ATC operator has to approve its output. This was working fine for over two months in DC and Florida, and was fine for three days of full deployment before the grounding.
If SMART data disagreed with TRACON, why could they not simply ignore the new system and go on as usual?