Something's Up!!
On the day this happend, just before making this post, I checked the FAA Incident Database for N14053, the airplane's registration, which was published by AOPA.
There was no report there, nothing...but there is today. Draw your own conclusions.
please elaborate.
Also, we know that early reports (likely true reports-- the truest reports come immediately after an incident, before the spin!) tell us that the aircraft was 20 second LATE in taking off behind the JAL flight. That would put the Airbus at 140 seconds behind the JAL... 2 minutes and 20 seconds total. Since 2 minutes is optimum space between flights, the turbulence theory would be immediately shot down. But instead, CNN now reports that it was 30 seconds EARLY behind the JAL flight... at 90 seconds total. Very fishy indeed-- and where did CNN get this info?
It would all simply say that Washington wants this crash to be anything BUT terrorism or sabatoge. Why? Well, it spent 15 billion propping up the airline industry. We'd have to spend more for a second terrorist sabatoge act to prop them up. A sabatoge act would cost airlines dearly in increased costs to check out every plane and install new procedures. Secondly, terrorists want terror. And they would get what they want with a second airline disaster.
No, in the end, Washington wants this to be an accident, and it will be an accident whether we want the truth or not. Time will tell, but I say we will never hear this crash to be attributed to sabatoge if it was indeed so.
BTW, I tried your links, and the nasdac.faa.gov server seems to be down right now.
That's a great catch.
Please allow me a question without getting upset. Are you sure that your _first_ search didn't contain any key stroke errors? Did you just do one search? Did you save to disk the results so that you can go back and verify that you didn't make a key stroke error in your query?
I don't mean to be insulting, I'm just trying to rule out an obvious error. I've _often_ done searches and gotten puzzling results until I've reviewed my query and found some unexpected typo.
Mark W.