Tuesday, January 20, 2015

Crashed AirAsia flight climbs too fast before disappearing from radar: Indonesia


This same thing was reported by a pilot who is a weatherman for CNN likely Chad Meyers. He said that they likely encountered a 100 mph vertical wind shear or more vertical. This likely would have either ripped off the wings or drove fist size hail through the front windows. Either or both of these things would have ended this flight with a crash into the ocean. This quick an ascent likely would have also ripped off the wings or tail section either of which would have caused the plane to crash. Also, an ascent this fast without a special flight suit built for this type of high G ascent would have rendered unconscious everyone on board whether they were still alive or not just from the G Force. So, likely no one was conscious when the plane crashed into the water. This other possibility is that the pressures would have also ruptured the fuselage which would have ended all life in the plane at that altitude because it would be way below zero degrees outside Fahrenheit at 400 to 500 miles per hour. 

begin quote:
Crashed AirAsia flight climbs too fast before disappearing from radar: Indonesia
English.news.cn   2015-01-21 00:49:06   
JAKARTA, Jan. 20 (Xinhua) -- Indonesia said here Tuesday that the crashed AirAsia flight QZ8501 climbed at an abnormally high rate and plunged suddenly before disappearing from radar.
Addressing the Parliament, Indonesian Transport Minister Ignasius Jonan said " it is not normal to climb like that. It is very rare for commercial planes which normally climb just 1,000 to 2,000 feet per minute."
"It can only be done by a fighter jet," the transport minister added.
What caused the flight to climb too fast remained unknown now.
Flight QZ8501, with 162 people onboard, plummeted into the Java Sea near the Karimata Strait during its journey from Surabaya to Singapore on Dec. 28.
The flight data and cockpit voice recorders, known as black boxes, have been recovered and they are vital to determining the cause of the crash.

No comments: