Hacker News new | past | comments | ask | show | jobs | submit login

Note the different scales. They were really floundering and never got up to anything like their intended altitude. They also continued the crazy-low altitude for over 5 minutes before final impact.



Looks like they climbed and maintained ~5000 feet after takeoff, presumably to figure out what was going on before returning to the airport. Wouldn't call that crazy low.


The interesting question is going to be: why didn’t the pilot abort the takeoff? Did the problem become obvious only in flight, or were the warning signs on the runway before it was too late?


Hmm... Why would that be an interesting question? It seems most likely that the issue occurred either during the climb out, or after V1 on the runway.

https://en.wikipedia.org/wiki/V_speeds


Because if the plane was down on power, the pilot might have had a chance before he hit V1.

This is obviously speculative, but I’ll be curious to find out what happened.


From the very limited telemetry available, it doesn't look like a power issue, it looks like a control issue.

It's certainly not impossible that there was an obvious fault before V1, but it's _way_ down the list of likely scenarios.


Ah, a control issue would indeed be pretty much impossible to diagnose before V1. That makes sense.

I have heard of issues that were discoverable before V1. Famously there was the Russian hockey team that was killed because the pilot was riding the brake and didn’t abort in time.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: