Hacker Newsnew | past | comments | ask | show | jobs | submit | hajile's commentslogin

https://www.youtube.com/watch?v=c8Kqg6sokz4

Truck declared it was crossing. ATC told it to stop. Truck didn't stop.

This wasn't a communication issue.


Audio in this video is cut, with parts of the recording omitted, see here for the full recording: https://youtu.be/Pbm-QJAAzNY?si=4Kkd8t8VEAsgHmJv&t=149

Timestamps from the video:

2:46 Truck requests crossing

2:51 ATC allows it to cross

2:53 Truck confirms

2:58 ATC: "Frontier 4195 stop there please"

3:02 ATC: "stop stop stop stop truck one stop stop stop"

3:15 ATC: "tower, truck one, stop, ..."

Crash probably a couple seconds later, wouldn't rely on the video for the exact timing.

So it seems that ATC made an error by allowing the truck to cross, and then the order to stop wasn't communicated clearly enough. I wouldn't place much blame on the truck.

Edit: Looking at some other videos with that audio, I'm also not sure if the video I linked represents the time between communications correctly, transmission at 3:15 may have been right after the one at 3:02. Anyway, the best thing is to wait for the investigation.


He asked Frontier 4195 to stop. By the time he asked truck 1 to stop they were entering the runway.

https://www.youtube.com/watch?v=c8Kqg6sokz4

The truck asks permission to cross. It is given. The truck declares it is going to cross, but the ATC replies "just stop there please".

Also, those runway entry lights look red to me. If so, that should have been a HUGE warning sign to the driver.


It was the “truck and company” that was cleared to cross. That’s probably 5+ vehicles you can see following the lead truck that were all approved. All while the jet was on short final. That controller lost situational awareness due to task saturation as a result of emergency aircraft on taxiway parallel to runway 13.

He said "Frontier 4195 stop there please". Then "stop stop stop stop truckon" By the time he clearly tells "truck 1" to stop, they're already entering the runway. Sounds like a bit of confusion.

Only one ATC isn't the issue here.

The emergency vehicle was told to stop and did not. Even a dozen ATC wouldn't have helped in that case.


There is no "the" issue in airline accidents. There are always multiple factors, and all of them had to happen in order for the accident to occur.

Understaffing is absolutely a factor. Had tower and ground not been combined, the erroneous clearance probably wouldn't have been issued.

The ARFF truck not complying with the stop instruction is absolutely a factor. Had they heard and complied, the accident wouldn't have happened.

And there are likely additional factors that will come out in the investigation.

I recommend reading some final aviation accident reports from the NTSB to learn more about how these investigations proceed and what kinds of conclusions and recommendations they include.


The fire truck was cleared to cross the runway, but for an unknown reason it waited for 30 seconds before starting to cross.

I read that the emergency vehicle may have weighed 60,000 lbs. It can't stop quickly any more than an airplane can.

https://www.youtube.com/watch?v=c8Kqg6sokz4

Watch the video.

Other trucks slow down, but truck 1 does not even try to slow down. I'd also argue that driving so quickly that you cannot maintain control is its own problem. Getting to an emergency 20 seconds later almost never matters as much as arriving safely.


Maybe they were talking about the truck going 24mph, but the plane is clearly going WAY faster than that.

I'm not completely sure but it seems like the runway entry lights are red which very clearly indicates the runway is in use. They should have known better.


It's crossing more than its entire length per second, so 36m - 130km/h+ or 80mph+.

This is the article I saw, but I agree it seems like its going much faster in the video https://www.aljazeera.com/news/2026/3/23/air-canada-crash-at...

Overwork is an issue in general, but I don't know that it was the actual issue here.

> In audio from the air traffic control tower at LaGuardia, a staff member can be heard saying: "'Truck One, stop, stop, stop!" in the seconds before the crash.

It sounds to me like either the Cop or the Firefighter (whichever was driving) wasn't listening to ATC and this whole incident was probably completely avoidable.

EDIT: a video of the crash seems to have warning lights that the emergency vehicle ignored.


> Overwork is an issue in general, but I don't know that it was the actual issue here.

One controller working tower duties, ground movement duties, coordinating with other ATC functions off the radio, an active emergency request, and giving clearance amendments all within 2 minutes. It's insane understaffing. On top of it, there was nobody there to take over after the crash. He worked the whole cleanup for the next 30 minutes.

This is an Olympian level elite Air Traffic Controller who was setup to fail.

I've visited towers, center facilities, and have flying (and some instructing) in the San Francisco airspace for 10 years. That kind of failure is systemic way above an individual.


The audio I heard seems to show the firetruck asking if the runway is clear to cross, the controller responding in the affirmative, the firetruck confirming the affirmative, and then 7 seconds later, the controller saying STOP STOP STOP.

https://www.instagram.com/reels/DWOQ8UhgoQR/


https://www.youtube.com/watch?v=c8Kqg6sokz4

It seems like less than 2 seconds from declaring intent to cross until they are told not to cross.

The runway entrance lights look red to me which is also a huge warning flag.


From the description:

> Audio is not synced.

I think the gaps between transmissions have been trimmed, too; this isn't matching other versions of the ATC audio, such as [VASAviation's][1].

> The runway entrance lights look red to me which is also a huge warning flag.

IANA-ATC, but presumably in an emergency, you're permitted to obtain clearance from ATC to enter an active runaway, to get to the emergency. (Which they did, and got, but which ATC later effectively revokes with the command to stop, prior to the accident. Whether ATC should have granted the clearance, well, I'll wait for the NTSB report there.)

[1]: https://www.youtube.com/watch?v=Pbm-QJAAzNY


Lisps aren’t necessarily functional, but don’t need semicolons either.

The syntax of languages like Lisp and Forth are so fundamentally different that they don't need an explicit statement separator. You don't have to think about many other things either, or I should say you don't have to think about them in the same way. Consider how much simpler the order of operations is in those languages.

Lisp has explicit "statement" terminators (just aren't semicolons)

All the lisps I know of have only expressions (no statements).

It seems like PC makers just don't want to invest in quality trackpads.

It's criminal that my now almost decade-old Pixelbook still has a better trackpad than 99% of PCs (including ones that cost way more money).


SIMD workloads on CPU tend to be bursty. If your workload is all SIMD with few other instructions or branches, it's almost certainly going to be faster on a GPU or SME co-processor.

If there's space between the SIMD instructions, then double-pumping or even quad-pumping isn't very expensive (and with 6 SIMD ports, it might even be basically free).


This core was released in the MediaTek 9400 in October 2024 some 16 months ago.

The successor of x925 is C1 Ultra and even that was released 6 months ago in September 2025 with the MediaTek 9500 and GeekerWan even has a phone review they did with that chip last year.


Chips and Cheese covers Apple products in a LOT of their posts.

The real reason is probably because they are supported by patrons and can only get new equipment to review when people donate (either money or sometimes the hardware itself).

If you like what they do (as pretty much the last in-depth hardware reviewers), consider supporting them.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: