Quote:
Originally Posted by BrianL99
I have no where near as many hours in the cockpit as others who have posted, but I do have enough to know that pilots primarily rely on their peripheral vision, which is better able to distinguish "movement", thus the words "scanning for traffic". In an airplane, your head has to be on a slow swivel when searching for traffic. It's usually the only way to pick out a "small speck", 2 miles away. I haven't been in the cockpit since ADS-B was mandated, but I can't imagine it's changed much, as it's primarily "out-going", I believe?
Apparently the 2 pilots in the BH were wearing night-vision googles, which I've been told are something like looking at the world through a toilet paper roll ... little or no peripheral vision.
the specifics that caused that post to be deleted.
take what you can get.
At the same time, the technology has improved dramatically and the hope has always been that the improved technology would make up for the lower standards. I think in this instance, as myself and a number of others have mentioned, ATC is going to take part of the blame and rightly so, in my opinion. With today's technology, two 100% operational aircraft shouldn't collide in the sky.
|
From what I have seen/heard so far, I believe the key factors to this incident will be:
-BH pilots using night vision in a potentially congested area
-non-specific comms from ATC to BH pilots re visual on Regional jet - there was actually 2 RJs in the immediate area.
-Did the ATC view/respond to instrument/radar tracking of the BH critically on a line to the Regional jet?