737 MAX crashes “linked” by satellite track data, FAA says
How strange that they both had issues at around 6000-8500 feet, briefly recovering, then nose diving.<p>Even more interesting is the recent 767 Amazon cargo flight crash in Texas also did a node dive at around 8000 feet which somehow has escaped the news with this new crash [1].  The pilots decided on a path around weather, were at 11-12000 feet, descended 3000+ feet and then the plane essentially did a similar nose dive. Is this a data problem?<p>&gt; <i>As the plane passed through 12,000 feet at a ground speed of 290 knots (340 mph), the pilots indicated they preferred the westerly route option ATC had given them around the rain; air traffic control told them they would need to descend quickly to 3,000 feet to do so, and radar data reveals the Boeing turned to a heading of 270º as requested and descended through 8,500 feet. One minute later, the controller told the crew they would be past the bad weather in about 18 miles, and to expect a turn to the north. The crew responded &quot;Sounds good&quot; and &quot;Okay,&quot; according to the NTSB, and the plane leveled out at 6,200 feet before rising 100 feet more.</i><p>&gt; <i>That, apparently, is when things went haywire. The aircraft began what the NTSB report described as &quot;small vertical accelerations consistent with the airplane entering turbulence,&quot; according to the flight data recorders recovered from the accident scene. Seconds later, with the plane holding steading at 230 knots (265 mph), the engines went to full power, and the nose of the plane rose four degrees...then the aircraft pitched nose-down for the next 18 seconds, reaching a maximum pitch of –49º in response to the plane&#x27;s elevator inputs. </i><p>The Ethiopia 737 Max has almost the same issue [2]<p>&gt; <i>ADS-B data recorded for ET302 by FlightRadar24 shows that the aircraft, after reaching an altitude of 8,025 feet above sea level, suddenly dipped, plunging 400 feet before recovering briefly. But the aircraft&#x27;s vertical speed remained unstable, and a few minutes later it dove into the ground. For reference, the airport the flight took off from is at 7,631 feet above sea level—so the aircraft never reached more than 500 feet above the ground, not leaving much room for correction.</i><p>All of these planes had issues in the 6000-8500 feet range and then both suffered the same plunging fate after briefly recovering from a dip &#x2F; nose stabilization issue.<p>Hopefully the ADS system is secure and not susceptible to infiltration&#x2F;hacks causing the plane to react to incorrect data at a range that is not recoverable.<p>[1] <a href="http:&#x2F;&#x2F;www.thedrive.com&#x2F;news&#x2F;26933&#x2F;amazon-boeing-767-cargo-plane-was-going-almost-500-mph-in-texas-crash-ntsb-says" rel="nofollow">http:&#x2F;&#x2F;www.thedrive.com&#x2F;news&#x2F;26933&#x2F;amazon-boeing-767-cargo-p...</a><p>[2] <a href="https:&#x2F;&#x2F;arstechnica.com&#x2F;information-technology&#x2F;2019&#x2F;03&#x2F;faa-acting-chief-says-satellite-data-provided-link-between-boeing-crashes&#x2F;" rel="nofollow">https:&#x2F;&#x2F;arstechnica.com&#x2F;information-technology&#x2F;2019&#x2F;03&#x2F;faa-a...</a>