Originally Posted by
N90-EWR
I like the "overrides your concerns about pushing tin" comment. More like my concerns about tin not hitting more tin. Things to keep in mind reference this case. The controller in this instance is ONLY working JFK departures and he has ZERO control over the other traffic in the adjacent airspace. He has to contain aircraft under his control inside his allocated airspace. The other controllers are busy, and on nights like this very likely to be dealing with their own issues with weather deviations. Controllers workloads skyrocket every time there's deviations like this.
Maybe try listening to LHR controllers when it gets busy with Thunderstorms and deviation required. The guy maybe experienced with a great career but he lost his cool, he screwed up, which is why it got highlighted here and other places. Your loyalty does you credit, but there comes a time when it’s the right thing to do to admit that, on this occasion, he could have done better. Failure to do so is the biggest error as it suggests that we can expect to see a repeat of the poor event. No-one in aviation is perfect - we all have days where we act in a way that we would like to improve on should the situation arise. For this controller, this is one of those moments - he should learn from it and move on. No-one died and that is the big deal, but the attitude could easily have been a contributing factor is a nasty event, a hole in the Swiss cheese. It wasn’t so it becomes a learning point, and if we learn by our mistakes most of us are getting a great education.