🇨🇦

  • 9 Posts
  • 572 Comments
Joined 2 years ago
cake
Cake day: July 1st, 2023

help-circle

  • There is no procedure that involves cutting off fuel to both engines while in-flight; one at a time, but not both. Then, there is no procedure that ever involves touching those controls during takeoff. Finally; there would be communication between the pilots discussing any such troubleshooting, they wouldn’t just take it upon themselves to start flipping switches without at the very least letting the other pilot know what they’re doing. Particularly when it comes to troubleshooting; there is a strict set of checklists they go through as a team, with one reading out questions, the other responding with data/answers from the instruments and the first confirming that response.

    These were both experienced pilots with ample flight hours; they knew what they were doing at those controls. I’m not going to throw human error out the window entirely, but it’s not looking very likely unfortunately.

    Either that plane was brought down intentionally, or there was a stunning error in judgment wildly disregarding procedure in that cockpit that was not communicated at all. (note: the mics record to the blackbox continuously, they’re not ptt, if one of the pilots had said something, it’d be on the tape.)



  • Given the mechanical saftey built into those switches, Unfortunately I guess that leaves us with two reasonable possibilities:

    A) One of the pilots was somehow mistaken on the function of those switches and toggled them when they should not have. Then they genuinely thought they hadn’t when asked why they had cutoff fuel.

    Or

    B) One of the pilots chose to cut off fuel supply to both engines, intentionally bringing down the plane. They then lied to the other pilot when asked why they’d cutoff fuel.















  • An $11/yr domain pointed at my IP. Port 443 is open to nginx, which proxies to the desired service depending on subdomain. (and explicitly drops any connection that uses my raw ip or an unrecognized name to connect, without responding at all)

    ACME.sh automatically refreshes my free ssl certificate every ~2months via DNS-01 verification and letsencrypt.

    And finally, I’ve got a dynamic IP, so DDClient keeps my domain pointed at the correct IP when/if it changes.


    There’s also pihole on the local network, replacing the WAN IP from external DNS, with the servers local IP, for LAN devices to use. But that’s very much optional, especially if your router performs NAT Hairpinning.

    This setup covers all ~24 of the services/web applications I host, though most other services have some additional configuration to make them only accessible from LAN/VPN despite using the same ports and nginx service. I can go into that if there’s interest.

    Only Emby/Jellyfin, Ombi, and Filebrowser are made accessible from WAN; so I can easily share those with friends/family without having to guide them through/restrict them to a vpn connection.