- Joined
- Dec 8, 2017
- Messages
- 11,979
I had fourth Cousin on that plane.
One thing I noticed is that so many talk radio shows had people talking about this disaster. The facts aren't fully out, yet, and I don't see why everyone must be subjected to commentary on this tragic event before an investigation is complete. It's like mental masturbation, just blathering about hunches all day long, plus more "no new news" at the top of the hour news.Some new info: & Some that conflicts earlier information.
https://www.zerohedge.com/political...nother-jet-aborted-landing-1-day-over-chopper
I don't think so. High-ranking officials fly on helicopters all over Washington, DC, all the time. Seemed a pretty reasonable thing for them to say to allay the concerns of all the swamp creatures that one of their cronies might have been aboard.Also interesting that as soon as it happened, Army said, "No high-ranking officers were onboard. That seemed a strange announcement.
Do aircraft often veer off course if they see no reason to? I thought they usually traveled in straight lines as much as possible.That helicopter trajectory was just like that of a missile ... it never veered off course
This would tend to support the conclusion that they didn't realize they were about to collide with anything. Didn't see it, were focused on another close by aircraft and missed the one right in front of their face.even when it was clearly going to collide.
One of the intelligent media people (yeah, I realize that is an oxy-moron ) mentioned that the chopper was gaining altitude, and when one does, it goes tail-up, and nose down.Do aircraft often veer off course if they see no reason to? I thought they usually traveled in straight lines as much as possible.
This would tend to support the conclusion that they didn't realize they were about to collide with anything. Didn't see it, were focused on another close by aircraft and missed the one right in front of their face.
Ummm, that doesn't sound right to me. When tail goes up and nose is down, you're DESCENDING, not ASCENDING. It's controlled by the cyclic stick.One of the intelligent media people (yeah, I realize that is an oxy-moron ) mentioned that the chopper was gaining altitude, and when one does, it goes tail-up, and nose down.
They wouldn't be able to see something in their flight path above them.
I'm pretty sure Super is referring to this typical manner of helicopter takeoff:Ummm, that doesn't sound right to me. When tail goes up and nose is down, you're DESCENDING, not ASCENDING. It's controlled by the cyclic stick.
But what do I know. I only worked on utility/attack military helicopters for my stint in the Marines.
...It was the drones, I tell ya'!!...
Damn dinosaurs. They've ruined many a good helicopter.
Exactly. The chopper requested "visual separation", taking responsibility for separation from other aircraft.For those on this forum who may not know, I have been a "commercial" pilot for roughly 40 years. When in "controlled" airspace, you do NOT tell pilots "Maintain visual spacing". I could be wrong, but I don't think you can enter controlled air space without a transponder. And said transponder turned on, and squawking the code you were given. That (transponder) tells your altitude, and heading and other important information, like your aircraft "type" (and its capabilities).
If the chopper would have had their transponder turned on........ATC would have given them new heading and "cleared" to a new altitude.
They could have told the "short final" jet to abort the landing and enter the flight pattern.
But Alex Jones has been right!Oh FFS. How can anyone listen to Alex Jones? he's gone as nuts as Glenn Beck was a few years ago.
At least Glenn unscrewed his head and dumped the crap out for the most part.
Exactly. The chopper requested "visual separation", taking responsibility for separation from other aircraft.
The planes were lined up in a series, and the chopper was looking at the plane behind them and not the one in front of their face.
The helo complying with the 200 foot altitude protocol, alone, would have saved them. The helo between 300 and 400 feet was in error.I wonder what the instructor was doing, that he did not see the plane. Why did he allow her to fly at that altitude. I think he was operating the radio communication with ATC not her. (slight chance I am wrong about radio).
I don't understand why they were allowed to have the transponder turned off.The helo complying with the 200 foot altitude protocol, alone, would have saved them. The helo between 300 and 400 feet was in error.
I heard chopper pilot say 100 ft could a blast of wind.The helo complying with the 200 foot altitude protocol, alone, would have saved them. The helo between 300 and 400 feet was in error.
The BH was on a COG (continuation of Government) training exercise.I don't understand why they were allowed to have the transponder turned off.
The tower data shows the helo at 200 feet and the airliner at 325 feet.I heard chopper pilot say 100 ft could a blast of wind.
There a mystery about what ATC saw re: the chopper altitude. The transponder was squawking the chopper lower.
I have it many times said...
Anyone can screw up but for a disaster, an engineer has to be involved.
Ben
Retired Engineer
Kind of like, "Anyone can design something that is strong enough. It takes an engineer to design something that is barely strong enough."Anyone can screw up but for a disaster, an engineer has to be involved.
If the helo was at 200 instead of colliding with the aircraft at 325 feet....then it would have been tight, but still a near miss.The tower data shows the helo at 200 feet and the airliner at 325 feet.
The tower normally gets this data from transponder responses......which come from the instruments in the aircraft.
......and yes....even if that had been correct......125 feet is not much of a separation.
There was at least something wrong with some combination of altitude instrumentation/systems in the tower, helo and airliner.
Do you know when that information was released.The BH was on a COG (continuation of Government) training exercise.
That means it was simulating evacuation of senior gov personnel.
about 36 hours ago.Do you know when that information was released.
I very much doubt the helo was at 200 feet.......it was in reality, at much closer to the same altitude as the airliner.If the helo was at 200 instead of colliding with the aircraft at 325 feet....then it would have been tight, but still a near miss.
If they collided, the chopper was obviously at the same altitude as the plane.I very much doubt the helo was at 200 feet.......it was in reality, at much closer to the same altitude as the airliner.
But the instrumentation providing indicated altitude to the tower showed their altitude as 200 feet....... and so it may have also been telling the helo crew they were at 200 feet.
The accident may have been caused by something as dumb as not resetting the area QNH on the altimeters in the BH....... because they were using a truncated takeoff checklist for a COG task/mission.
In COG.....time is of the essence.....seconds count.
The crew is simulating trying to get senior leadership clear of DC with nuclear weapons inbound.
Once you are talking about <100 feet, the size of the aircraft and their moving parts becomes significant.If they collided, the chopper was obviously at the same altitude as the plane.
You can argue with the transponders all you want, but it won't change the facts.
And it is obvious which one was where it shouldn't be.
200, 200 ,200 , 300, 300, 350