> 1) I was giving Simon a heads up to look for a report out of DEN - if it was anything, I thought it was just something like a (big) compressor stall. That was why so many caveats were there - I wasn't sure at the time that the aircraft had had a problem. I didn't realize it was going to be widely reported until my mother texted me a couple of hours later asking if any of the plane parts came down close to me
> 2) Something I omitted that I should have put in: After I got home I imagined how many thumb-widths at arm's length it would take to occlude it (from memory), and plugged that into similar triangles and the length of a 737 (didn't realize it was a 777) to get an estimated altitude and got 2-4 thousand meters. I thought the cloud deck was only 2000 feet AGL or so, so I didn't believe the numbers. I did change "a couple" to "a few" though. Turns out it was ~8000 feet AGL. I should have believed more in the math!
it's like that old experiment that i cant find source for - wall st traders switched with military guys and wall st outperformed mils because they are used to dealing with uncertain information...
The saying is “aviation regulations are written in blood” because each new regulation is usually in response to crash. https://aviation.stackexchange.com/questions/13081/why-do-pe...
You don’t keep a “paper trail written in blood”.
The excellent safety record of aviation originates from a detailed and pedantic paper trail that is written in blood. It's by learning as much as possible from every incident, without fear of censure or blame, that makes the skies safer for everybody.