Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (Cyborg)
  • No Skin
Collapse
Brand Logo

CIRCLE WITH A DOT

  1. Home
  2. Uncategorized
  3. As the news is reporting, sadly there was a terrible plane crash at LaGuardia Airport at 23:38 local last night.

As the news is reporting, sadly there was a terrible plane crash at LaGuardia Airport at 23:38 local last night.

Scheduled Pinned Locked Moved Uncategorized
chillyatcadvent
33 Posts 14 Posters 0 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • chillybot@infosec.exchangeC chillybot@infosec.exchange

    As the news is reporting, sadly there was a terrible plane crash at LaGuardia Airport at 23:38 local last night.

    A Jazz Aviation CRJ900 was landing and a truck was cleared to cross the runway. There seems to be a breakdown in ground comms because the ATC basically begs the truck to stop but the plane still hit the truck.

    Both pilots did not survive. The firefighters did and no reports of passenger fatalities.

    My love goes out to the families of the victims.

    #ChillyATCAdventures

    Link Preview ImageLink Preview ImageLink Preview Image
    chillybot@infosec.exchangeC This user is from outside of this forum
    chillybot@infosec.exchangeC This user is from outside of this forum
    chillybot@infosec.exchange
    wrote last edited by
    #2

    Audio of the incident

    chillybot@infosec.exchangeC 1 Reply Last reply
    0
    • chillybot@infosec.exchangeC chillybot@infosec.exchange

      Audio of the incident

      chillybot@infosec.exchangeC This user is from outside of this forum
      chillybot@infosec.exchangeC This user is from outside of this forum
      chillybot@infosec.exchange
      wrote last edited by
      #3

      Here is a half assed video I threw together last night to show the flight path of the plane synced with the ATC audio

      chillybot@infosec.exchangeC 1 Reply Last reply
      0
      • chillybot@infosec.exchangeC chillybot@infosec.exchange

        Here is a half assed video I threw together last night to show the flight path of the plane synced with the ATC audio

        chillybot@infosec.exchangeC This user is from outside of this forum
        chillybot@infosec.exchangeC This user is from outside of this forum
        chillybot@infosec.exchange
        wrote last edited by
        #4

        Actually Victor made the video already here is his

        - YouTube

        Auf YouTube findest du die angesagtesten Videos und Tracks. Außerdem kannst du eigene Inhalte hochladen und mit Freunden oder gleich der ganzen Welt teilen.

        favicon

        (www.youtube.com)

        chillybot@infosec.exchangeC 1 Reply Last reply
        0
        • chillybot@infosec.exchangeC chillybot@infosec.exchange

          Actually Victor made the video already here is his

          - YouTube

          Auf YouTube findest du die angesagtesten Videos und Tracks. Außerdem kannst du eigene Inhalte hochladen und mit Freunden oder gleich der ganzen Welt teilen.

          favicon

          (www.youtube.com)

          chillybot@infosec.exchangeC This user is from outside of this forum
          chillybot@infosec.exchangeC This user is from outside of this forum
          chillybot@infosec.exchange
          wrote last edited by
          #5

          And Mentour Pilot did a livestream talking about it

          - YouTube

          Auf YouTube findest du die angesagtesten Videos und Tracks. Außerdem kannst du eigene Inhalte hochladen und mit Freunden oder gleich der ganzen Welt teilen.

          favicon

          (www.youtube.com)

          chillybot@infosec.exchangeC 1 Reply Last reply
          0
          • chillybot@infosec.exchangeC chillybot@infosec.exchange

            And Mentour Pilot did a livestream talking about it

            - YouTube

            Auf YouTube findest du die angesagtesten Videos und Tracks. Außerdem kannst du eigene Inhalte hochladen und mit Freunden oder gleich der ganzen Welt teilen.

            favicon

            (www.youtube.com)

            chillybot@infosec.exchangeC This user is from outside of this forum
            chillybot@infosec.exchangeC This user is from outside of this forum
            chillybot@infosec.exchange
            wrote last edited by
            #6

            Video of the actual crash now out. Content warning obviously.

            J nyanbinary@infosec.exchangeN chillybot@infosec.exchangeC 3 Replies Last reply
            0
            • chillybot@infosec.exchangeC chillybot@infosec.exchange

              Video of the actual crash now out. Content warning obviously.

              J This user is from outside of this forum
              J This user is from outside of this forum
              jackryder@infosec.exchange
              wrote last edited by
              #7

              @chillybot omg whoa...

              1 Reply Last reply
              0
              • chillybot@infosec.exchangeC chillybot@infosec.exchange

                Video of the actual crash now out. Content warning obviously.

                nyanbinary@infosec.exchangeN This user is from outside of this forum
                nyanbinary@infosec.exchangeN This user is from outside of this forum
                nyanbinary@infosec.exchange
                wrote last edited by
                #8

                @chillybot thats, uhm, suboptimal

                1 Reply Last reply
                0
                • chillybot@infosec.exchangeC chillybot@infosec.exchange

                  Video of the actual crash now out. Content warning obviously.

                  chillybot@infosec.exchangeC This user is from outside of this forum
                  chillybot@infosec.exchangeC This user is from outside of this forum
                  chillybot@infosec.exchange
                  wrote last edited by
                  #9

                  NTSB Press Briefing on the incident
                  https://www.youtube.com/watch?v=UieRrg2etdY

                  chillybot@infosec.exchangeC 1 Reply Last reply
                  0
                  • chillybot@infosec.exchangeC chillybot@infosec.exchange

                    NTSB Press Briefing on the incident
                    https://www.youtube.com/watch?v=UieRrg2etdY

                    chillybot@infosec.exchangeC This user is from outside of this forum
                    chillybot@infosec.exchangeC This user is from outside of this forum
                    chillybot@infosec.exchange
                    wrote last edited by
                    #10

                    And blancolirio did a video on the crash https://www.youtube.com/watch?v=VnSGMPaJ2OM

                    scottwilson@infosec.exchangeS chillybot@infosec.exchangeC 2 Replies Last reply
                    0
                    • chillybot@infosec.exchangeC chillybot@infosec.exchange

                      And blancolirio did a video on the crash https://www.youtube.com/watch?v=VnSGMPaJ2OM

                      scottwilson@infosec.exchangeS This user is from outside of this forum
                      scottwilson@infosec.exchangeS This user is from outside of this forum
                      scottwilson@infosec.exchange
                      wrote last edited by
                      #11

                      @chillybot I listened to the ATC of this incident. Brutal.

                      1 Reply Last reply
                      0
                      • chillybot@infosec.exchangeC chillybot@infosec.exchange

                        And blancolirio did a video on the crash https://www.youtube.com/watch?v=VnSGMPaJ2OM

                        chillybot@infosec.exchangeC This user is from outside of this forum
                        chillybot@infosec.exchangeC This user is from outside of this forum
                        chillybot@infosec.exchange
                        wrote last edited by
                        #12

                        Okay I watched the second NTSB press briefing twice yesterday and have some juicy deets to dish out for you fine folks. Some of this was previously available/self evident but I wanted to wait a bit for the NTSB to do its thing. Here we go Longer post so maybe bookmark and read later.

                        • First off, as the chairwoman succinctly emphasized: If a airline crash happens, many things likely went wrong. Flying is so safe because it has defense in depth built in. I personally would like to say we must resist the very natural desire to focus on "okay, who f'ed up". This is a search for the truth.

                        • The controller clearly at least twice told the truck to stop before the crash

                        • Two controllers were in the air traffic control tower cab (in layman's terms, the top most part of the tower with windows where the active ATCs oversee things and work) at the time. They had just gone on duty for the "midnight" (22:30-06:30) shift at ~22:30ish local time.

                        • There is conflicting information on which air traffic controller was in charge of operations on the ground.

                        • The controllers at the time were dealing with another emergency on the ground. So there was a heavy workload on controllers who were also working multiple positions. NTSB cautions about talking about "controller distraction" as they were doing their job.

                        • The controllers were doing combined positions since it was the midnight shift. This is the standard operating procedure for a lot of airports, including Newark. (See other #ChillyATCAdventures posts). The chairwoman has concerns about this nationwide common practice and so do I.

                        • Conflicting reports on how many certified ATCs were in the facility overall. ATCs are supposed to take periodic breaks and be relieved by another controller.

                        • The truck did not have a transponder to report its location. The airport did have airport surface detection equipment (ASDE-X) but the ground radar did not alert since the proximity of multiple ARFF trucks caused the system to have low confidence.

                        • The automatic runway status lights were operational and indicated it was not clear to cross the runway

                        • Chairwoman Homendy is awesome, as usual

                        #AvGeek

                        adamshostack@infosec.exchangeA davemwilburn@infosec.exchangeD insidertreat@infosec.exchangeI mlanger@mastodon.worldM user47@vmst.ioU 6 Replies Last reply
                        1
                        0
                        • chillybot@infosec.exchangeC chillybot@infosec.exchange

                          Okay I watched the second NTSB press briefing twice yesterday and have some juicy deets to dish out for you fine folks. Some of this was previously available/self evident but I wanted to wait a bit for the NTSB to do its thing. Here we go Longer post so maybe bookmark and read later.

                          • First off, as the chairwoman succinctly emphasized: If a airline crash happens, many things likely went wrong. Flying is so safe because it has defense in depth built in. I personally would like to say we must resist the very natural desire to focus on "okay, who f'ed up". This is a search for the truth.

                          • The controller clearly at least twice told the truck to stop before the crash

                          • Two controllers were in the air traffic control tower cab (in layman's terms, the top most part of the tower with windows where the active ATCs oversee things and work) at the time. They had just gone on duty for the "midnight" (22:30-06:30) shift at ~22:30ish local time.

                          • There is conflicting information on which air traffic controller was in charge of operations on the ground.

                          • The controllers at the time were dealing with another emergency on the ground. So there was a heavy workload on controllers who were also working multiple positions. NTSB cautions about talking about "controller distraction" as they were doing their job.

                          • The controllers were doing combined positions since it was the midnight shift. This is the standard operating procedure for a lot of airports, including Newark. (See other #ChillyATCAdventures posts). The chairwoman has concerns about this nationwide common practice and so do I.

                          • Conflicting reports on how many certified ATCs were in the facility overall. ATCs are supposed to take periodic breaks and be relieved by another controller.

                          • The truck did not have a transponder to report its location. The airport did have airport surface detection equipment (ASDE-X) but the ground radar did not alert since the proximity of multiple ARFF trucks caused the system to have low confidence.

                          • The automatic runway status lights were operational and indicated it was not clear to cross the runway

                          • Chairwoman Homendy is awesome, as usual

                          #AvGeek

                          adamshostack@infosec.exchangeA This user is from outside of this forum
                          adamshostack@infosec.exchangeA This user is from outside of this forum
                          adamshostack@infosec.exchange
                          wrote last edited by
                          #13

                          @chillybot @paul_ipv6 Thank you!

                          chillybot@infosec.exchangeC 1 Reply Last reply
                          0
                          • chillybot@infosec.exchangeC chillybot@infosec.exchange

                            Okay I watched the second NTSB press briefing twice yesterday and have some juicy deets to dish out for you fine folks. Some of this was previously available/self evident but I wanted to wait a bit for the NTSB to do its thing. Here we go Longer post so maybe bookmark and read later.

                            • First off, as the chairwoman succinctly emphasized: If a airline crash happens, many things likely went wrong. Flying is so safe because it has defense in depth built in. I personally would like to say we must resist the very natural desire to focus on "okay, who f'ed up". This is a search for the truth.

                            • The controller clearly at least twice told the truck to stop before the crash

                            • Two controllers were in the air traffic control tower cab (in layman's terms, the top most part of the tower with windows where the active ATCs oversee things and work) at the time. They had just gone on duty for the "midnight" (22:30-06:30) shift at ~22:30ish local time.

                            • There is conflicting information on which air traffic controller was in charge of operations on the ground.

                            • The controllers at the time were dealing with another emergency on the ground. So there was a heavy workload on controllers who were also working multiple positions. NTSB cautions about talking about "controller distraction" as they were doing their job.

                            • The controllers were doing combined positions since it was the midnight shift. This is the standard operating procedure for a lot of airports, including Newark. (See other #ChillyATCAdventures posts). The chairwoman has concerns about this nationwide common practice and so do I.

                            • Conflicting reports on how many certified ATCs were in the facility overall. ATCs are supposed to take periodic breaks and be relieved by another controller.

                            • The truck did not have a transponder to report its location. The airport did have airport surface detection equipment (ASDE-X) but the ground radar did not alert since the proximity of multiple ARFF trucks caused the system to have low confidence.

                            • The automatic runway status lights were operational and indicated it was not clear to cross the runway

                            • Chairwoman Homendy is awesome, as usual

                            #AvGeek

                            adamshostack@infosec.exchangeA This user is from outside of this forum
                            adamshostack@infosec.exchangeA This user is from outside of this forum
                            adamshostack@infosec.exchange
                            wrote last edited by
                            #14

                            @chillybot @paul_ipv6 Meanwhile in cybersecurity we get reports like “scattered spider vished the mfa and then laterelled and no one could have foreseen it.” Cc @boblord @wendynather

                            chillybot@infosec.exchangeC 1 Reply Last reply
                            0
                            • adamshostack@infosec.exchangeA adamshostack@infosec.exchange

                              @chillybot @paul_ipv6 Meanwhile in cybersecurity we get reports like “scattered spider vished the mfa and then laterelled and no one could have foreseen it.” Cc @boblord @wendynather

                              chillybot@infosec.exchangeC This user is from outside of this forum
                              chillybot@infosec.exchangeC This user is from outside of this forum
                              chillybot@infosec.exchange
                              wrote last edited by
                              #15

                              @adamshostack
                              Yupppp, exactly. Bring back the CSRB! Aviation makes me jealous. We as an industry have much to learn from them.
                              @paul_ipv6 @boblord @wendynather

                              petrillic@hachyderm.ioP tindrasgrove@infosec.exchangeT 2 Replies Last reply
                              0
                              • adamshostack@infosec.exchangeA adamshostack@infosec.exchange

                                @chillybot @paul_ipv6 Thank you!

                                chillybot@infosec.exchangeC This user is from outside of this forum
                                chillybot@infosec.exchangeC This user is from outside of this forum
                                chillybot@infosec.exchange
                                wrote last edited by
                                #16

                                @adamshostack
                                Of course! Thanks for the thanks
                                @paul_ipv6

                                1 Reply Last reply
                                0
                                • chillybot@infosec.exchangeC chillybot@infosec.exchange

                                  Okay I watched the second NTSB press briefing twice yesterday and have some juicy deets to dish out for you fine folks. Some of this was previously available/self evident but I wanted to wait a bit for the NTSB to do its thing. Here we go Longer post so maybe bookmark and read later.

                                  • First off, as the chairwoman succinctly emphasized: If a airline crash happens, many things likely went wrong. Flying is so safe because it has defense in depth built in. I personally would like to say we must resist the very natural desire to focus on "okay, who f'ed up". This is a search for the truth.

                                  • The controller clearly at least twice told the truck to stop before the crash

                                  • Two controllers were in the air traffic control tower cab (in layman's terms, the top most part of the tower with windows where the active ATCs oversee things and work) at the time. They had just gone on duty for the "midnight" (22:30-06:30) shift at ~22:30ish local time.

                                  • There is conflicting information on which air traffic controller was in charge of operations on the ground.

                                  • The controllers at the time were dealing with another emergency on the ground. So there was a heavy workload on controllers who were also working multiple positions. NTSB cautions about talking about "controller distraction" as they were doing their job.

                                  • The controllers were doing combined positions since it was the midnight shift. This is the standard operating procedure for a lot of airports, including Newark. (See other #ChillyATCAdventures posts). The chairwoman has concerns about this nationwide common practice and so do I.

                                  • Conflicting reports on how many certified ATCs were in the facility overall. ATCs are supposed to take periodic breaks and be relieved by another controller.

                                  • The truck did not have a transponder to report its location. The airport did have airport surface detection equipment (ASDE-X) but the ground radar did not alert since the proximity of multiple ARFF trucks caused the system to have low confidence.

                                  • The automatic runway status lights were operational and indicated it was not clear to cross the runway

                                  • Chairwoman Homendy is awesome, as usual

                                  #AvGeek

                                  davemwilburn@infosec.exchangeD This user is from outside of this forum
                                  davemwilburn@infosec.exchangeD This user is from outside of this forum
                                  davemwilburn@infosec.exchange
                                  wrote last edited by
                                  #17

                                  @chillybot

                                  Did you get any sense as to whether they'd be looking at the FAA's practice of granting anticipatory clearance as a potential factor?

                                  chillybot@infosec.exchangeC 1 Reply Last reply
                                  0
                                  • chillybot@infosec.exchangeC chillybot@infosec.exchange

                                    @adamshostack
                                    Yupppp, exactly. Bring back the CSRB! Aviation makes me jealous. We as an industry have much to learn from them.
                                    @paul_ipv6 @boblord @wendynather

                                    petrillic@hachyderm.ioP This user is from outside of this forum
                                    petrillic@hachyderm.ioP This user is from outside of this forum
                                    petrillic@hachyderm.io
                                    wrote last edited by
                                    #18

                                    @chillybot @adamshostack @paul_ipv6 @boblord @wendynather another plug for another group doing yeoman's work... US Chemical Safety and Hazard Investigation Board. I use these constantly to demonstrate how to explain VERY complicated problems to people clearly, and identify fundamental structural changes that can improve things.

                                    https://www.youtube.com/user/USCSB

                                    wendynather@infosec.exchangeW 1 Reply Last reply
                                    0
                                    • chillybot@infosec.exchangeC chillybot@infosec.exchange

                                      Okay I watched the second NTSB press briefing twice yesterday and have some juicy deets to dish out for you fine folks. Some of this was previously available/self evident but I wanted to wait a bit for the NTSB to do its thing. Here we go Longer post so maybe bookmark and read later.

                                      • First off, as the chairwoman succinctly emphasized: If a airline crash happens, many things likely went wrong. Flying is so safe because it has defense in depth built in. I personally would like to say we must resist the very natural desire to focus on "okay, who f'ed up". This is a search for the truth.

                                      • The controller clearly at least twice told the truck to stop before the crash

                                      • Two controllers were in the air traffic control tower cab (in layman's terms, the top most part of the tower with windows where the active ATCs oversee things and work) at the time. They had just gone on duty for the "midnight" (22:30-06:30) shift at ~22:30ish local time.

                                      • There is conflicting information on which air traffic controller was in charge of operations on the ground.

                                      • The controllers at the time were dealing with another emergency on the ground. So there was a heavy workload on controllers who were also working multiple positions. NTSB cautions about talking about "controller distraction" as they were doing their job.

                                      • The controllers were doing combined positions since it was the midnight shift. This is the standard operating procedure for a lot of airports, including Newark. (See other #ChillyATCAdventures posts). The chairwoman has concerns about this nationwide common practice and so do I.

                                      • Conflicting reports on how many certified ATCs were in the facility overall. ATCs are supposed to take periodic breaks and be relieved by another controller.

                                      • The truck did not have a transponder to report its location. The airport did have airport surface detection equipment (ASDE-X) but the ground radar did not alert since the proximity of multiple ARFF trucks caused the system to have low confidence.

                                      • The automatic runway status lights were operational and indicated it was not clear to cross the runway

                                      • Chairwoman Homendy is awesome, as usual

                                      #AvGeek

                                      insidertreat@infosec.exchangeI This user is from outside of this forum
                                      insidertreat@infosec.exchangeI This user is from outside of this forum
                                      insidertreat@infosec.exchange
                                      wrote last edited by
                                      #19

                                      @chillybot obviously I feel for everyone involved but I listened to the ATC recording afterwards and couldn't help feel like that ATC is going to fully blame themselves.

                                      1 Reply Last reply
                                      0
                                      • petrillic@hachyderm.ioP petrillic@hachyderm.io

                                        @chillybot @adamshostack @paul_ipv6 @boblord @wendynather another plug for another group doing yeoman's work... US Chemical Safety and Hazard Investigation Board. I use these constantly to demonstrate how to explain VERY complicated problems to people clearly, and identify fundamental structural changes that can improve things.

                                        https://www.youtube.com/user/USCSB

                                        wendynather@infosec.exchangeW This user is from outside of this forum
                                        wendynather@infosec.exchangeW This user is from outside of this forum
                                        wendynather@infosec.exchange
                                        wrote last edited by
                                        #20

                                        @petrillic @chillybot @adamshostack @paul_ipv6 @boblord Whoa, great callout!

                                        1 Reply Last reply
                                        0
                                        • davemwilburn@infosec.exchangeD davemwilburn@infosec.exchange

                                          @chillybot

                                          Did you get any sense as to whether they'd be looking at the FAA's practice of granting anticipatory clearance as a potential factor?

                                          chillybot@infosec.exchangeC This user is from outside of this forum
                                          chillybot@infosec.exchangeC This user is from outside of this forum
                                          chillybot@infosec.exchange
                                          wrote last edited by
                                          #21

                                          @DaveMWilburn
                                          To explain for others, anticipatory clearance in this case refers to the practice of essentially preventing the runway from being used by anyone other than the plane cleared to land. ATCs in the US do not currently do this while a lot of Europe does.

                                          Regarding the briefing, I do not believe this specifically was discussed. That being said yesterday was the first full day of investigation and I think the NTSB will likely look into it.

                                          davemwilburn@infosec.exchangeD 1 Reply Last reply
                                          0
                                          Reply
                                          • Reply as topic
                                          Log in to reply
                                          • Oldest to Newest
                                          • Newest to Oldest
                                          • Most Votes


                                          • Login

                                          • Login or register to search.
                                          • First post
                                            Last post
                                          0
                                          • Categories
                                          • Recent
                                          • Tags
                                          • Popular
                                          • World
                                          • Users
                                          • Groups