this post was submitted on 26 Jul 2025
600 points (94.6% liked)

Lemmy Shitpost

33439 readers
6123 users here now

Welcome to Lemmy Shitpost. Here you can shitpost to your hearts content.

Anything and everything goes. Memes, Jokes, Vents and Banter. Though we still have to comply with lemmy.world instance rules. So behave!


Rules:

1. Be Respectful


Refrain from using harmful language pertaining to a protected characteristic: e.g. race, gender, sexuality, disability or religion.

Refrain from being argumentative when responding or commenting to posts/replies. Personal attacks are not welcome here.

...


2. No Illegal Content


Content that violates the law. Any post/comment found to be in breach of common law will be removed and given to the authorities if required.

That means:

-No promoting violence/threats against any individuals

-No CSA content or Revenge Porn

-No sharing private/personal information (Doxxing)

...


3. No Spam


Posting the same post, no matter the intent is against the rules.

-If you have posted content, please refrain from re-posting said content within this community.

-Do not spam posts with intent to harass, annoy, bully, advertise, scam or harm this community.

-No posting Scams/Advertisements/Phishing Links/IP Grabbers

-No Bots, Bots will be banned from the community.

...


4. No Porn/ExplicitContent


-Do not post explicit content. Lemmy.World is not the instance for NSFW content.

-Do not post Gore or Shock Content.

...


5. No Enciting Harassment,Brigading, Doxxing or Witch Hunts


-Do not Brigade other Communities

-No calls to action against other communities/users within Lemmy or outside of Lemmy.

-No Witch Hunts against users/communities.

-No content that harasses members within or outside of the community.

...


6. NSFW should be behind NSFW tags.


-Content that is NSFW should be behind NSFW tags.

-Content that might be distressing should be kept behind NSFW tags.

...

If you see content that is a breach of the rules, please flag and report the comment and a moderator will take action where they can.


Also check out:

Partnered Communities:

1.Memes

2.Lemmy Review

3.Mildly Infuriating

4.Lemmy Be Wholesome

5.No Stupid Questions

6.You Should Know

7.Comedy Heaven

8.Credible Defense

9.Ten Forward

10.LinuxMemes (Linux themed memes)


Reach out to

All communities included on the sidebar are to be made in compliance with the instance rules. Striker

founded 2 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] Rivalarrival@lemmy.today 6 points 1 day ago (1 children)

Just to put this into perspective, here's a visualization of the flight data. The two aircraft were never on a collision course. They slightly violated a 5-mile separation requirement: their closest point of approach was 4.85 miles. The pilot did need to respond to the TCAS alert, but that alert was very conservative.

[–] neatchee@lemmy.world 6 points 22 hours ago* (last edited 22 hours ago) (1 children)

These conservative warnings exist for a reason, though. That being hundreds of lives at stake. What I think would be more interesting is to hear how often these types of events occurred before and after the layoffs at the FAA

[–] Rivalarrival@lemmy.today 4 points 17 hours ago (1 children)

Agreed. The point of a conservative warning is to give plenty of time and opportunity to react without bouncing your passengers off the ceiling.

Fault for the loss of separation seems to be on the controllers. Not all separation incidents are the same, though. This one seems to be rather minor. By my estimation, the encroachment was a maximum of 264 yards, and the duration of that encroachment (without pilot or controller intervention) would have been less than 10 seconds. Too tight, yes. It needs addressed so it doesn't become a habitual violation that could lead to more severe encroachment by these controllers. But there was no real danger of bodily harm from this encroachment.

Fault for an overly aggressive maneuver is on the pilot. There was a risk of injury from that overly aggressive response. The pilot's actions elevated a minor, no-risk event to one that risked serious injury to the passengers and crew. But, he was following instructions from a device designed to improve aviation safety, and the nature of the warnings from that device, an over-response is much safer than an under-response. He has to trust his instruments, and his instruments (erroneously) told him to push the nose down, quickly, lest he hit another plane.

TCAS is designed and intended to reduce risk and prevent harm. In this specific incident, though, it seems like the TCAS-RA actually increased the risk of harm, by calling for an immediate action that wasn't actually necessary to prevent harm. Is there a way to improve TCAS?

I, too, would like to know how often TCAS incidents were recorded before and after the layoffs. Those layoffs definitely harmed aviation safety. But if someone were injured in this incident, I don't think I could point the finger at the controllers or lack thereof. This particular incident seems to suggest a shortcoming in the TCAS system.

[–] neatchee@lemmy.world 1 points 14 hours ago

Very thoughtful and informed reply. Thank you for sharing your knowledge!