That is not how I would describe the helicopter's path. And Standard ceiling of helicopters in that air space was top at 200 feet. The collision was said to have been at 400 feet. (assuming that the altimeter on the helicopter was correct, it should never have happened. Terrain in the Potomac river area would affect the reading in one instance, but the chopper was always over the water and it was at the collision.)
Whole string of very costly errors.
- TBD
“Whole string of very costly errors.”
I don’t think it was an error to turn into the aircraft’s flight path and climb double the helicopter’s ceiling to intercept the aircraft. Seems pretty D-d intentional to me.
Reminds me of the homosexual German passenger jet pilot who flew his flight into the ground in an act of spite.
When ppl put their choice of sexual gratification above their duties and obligations it’s quite obvious they intend to impart the consequences to others.
Seems pretty clear what the remedy is.
OK..
Basic traffic rules at an airport...
Once you are cleared to land YOU HAVE THE RIGHT OF WAY!!!
Period.
It is up to the atc and other pilots to get and stay the hell out of the way...
This did not happen, the helo pilot was not even acknowledging commands from the atc.
As an experienced air traffic controller with 30 years in FAA Terminal Towers and Approach control, I agree with this assessment.
1. The FAA Order 7110.65 delineates the correct verbiage to be used with "visual separation" and the exchange between the
two actors isn't even close.
2. The FLM (Supervisor) releasing another controller earlier and combining the Local Control (Tower) with Ground Control
during a congested traffic period is nuts. I wouldn't be surprised to find that the Supervisor was DEI as well.