« GRITZ Home | Email msg. | Reply to msg. | Post new | Board info. Previous | Home | Next

Re: Fmr. Air Traffic Controller: DC Crash Was 100% Controller’s Fault 

By: CTJ in GRITZ | Recommend this post (2)
Sat, 01 Feb 25 11:19 PM | 12 view(s)
Boardmark this board | Grits Breakfast of Champeens!
Msg. 03346 of 03359
(This msg. is a reply to 03340 by De_Composed)

Jump:
Jump to board:
Jump to msg. #

The controller mentioned the plane to the helicopter three times. The 1st time was when the plane was about 4 miles south of the runway. Plane was just passing over the Wilson Bridge. It would have been better if controller had told the copter pilot where to look for the plane, ie “at your 2 o’clock”. Just before the collusion the controller told the helicopter to pass behind the plane. Looks like the helicopter pilot was looking at the wrong plane.

Also, Looking at the chart it looks like the helicopter was about a 1/2 mile outside of the flight route it was suppose to be in. And was encroaching into the landing path of the plane. As well as being 175 feet above its ceiling restriction. I think we’ll be hearing more about the helicopter pilot being outside of the route they were cleared for.

Controller 10%
Helo pilot 90%
Plane pilot 0%



- - - - -
View Replies (1) »



» You can also:
- - - - -
The above is a reply to the following message:
Fmr. Air Traffic Controller: DC Crash Was 100% Controller’s Fault
By: De_Composed
in GRITZ
Sat, 01 Feb 25 8:17 PM
Msg. 03340 of 03359

100%? No. The helicopter WAS at 375 feet and climbing. But when an air traffic controller gives an opinion, he's going to ignore things like that and wear his air traffic controller hat. I'm going 50/50 on this accident. The only ones I don't blame are the plane crew and the river.

February 1, 2025

Fmr. Air Traffic Controller: DC Crash Was 100% Controller’s Fault

by M. Dowling
IndependentSentinel.com


A knowledgeable former air traffic controller named Michael Pearson told Greg Kelly on his show last night that the D.C. crash that killed 67 people was 100% the fault of air traffic control because he gave incorrect instructions.

The segment began with Mr. Pearson criticizing then-President Obama’s anti-white rule changes in 2011. You’ll catch a little of that in this clip. However, he then explains why it’s the air traffic controller’s fault.

Here’s some of what he says:

Mr. Pearson, who is now a private pilot, said it is not the fault of the helicopter pilots.

“It’s 100% air traffic control’s fault. It’s not only me, but approximately 45 current FAA managers and air traffic controllers agree with me. I spent about six hours looking at the data track and listening to the voice tapes the very night it happened.

“Before the media, it was very apparent to me, and I can tell you exactly why air trafficking did not issue proper traffic instructions.

Greg Kelly played the short audio of the air traffic controller’s instructions.

Mistake 1
The CRJ is the problem. They didn’t say where that CJR is. One o’clock, two o’clock, five o’clock, low, high, Kelly said.

Mr. Pearson said there are set air traffic rules that tell you exactly how you issue traffic. The problem with saying, do you see an RJ at night is that there are RJs on the runway. There are RJs in the air. He didn’t get the clock position. He didn’t say, off to your right, off to your left. Do you see the RJ in sight?

Pearson said the controller might have done it earlier but doubts it, because of the nature of how fast it moved.

Mistake 2
“Not only that,” Pearson said, “you have to have a means of separation ensured both before and after the application of visual separation; they had none. They should have kept that helicopter at least 500 feet or a mile and a half longitudinally from that airplane.

Mistake3
“Last but not least, the data track shows that the conflict alert was going off as these two airplanes were emerging, courses headed toward each other. There’s a loud CA, and it flashes on your screen, it’s red, and there’s a very loud, it’s like a smoke alarm going off, audible warning in that tower. And it looks to me like that, seven to nine seconds, that was going off, and the controller failed to undertake what’s called merging target procedures.”

Watch:

https://www.independentsentinel.com/fmr-air-traffic-controller-dc-crash-was-100-controllers-fault/


« GRITZ Home | Email msg. | Reply to msg. | Post new | Board info. Previous | Home | Next