TUCKnTRUCK
That guy
So nearly hitting a bridge full of people and/or running a 757 into a river is less bad than safely landing at the wrong airport.
Right.
I'm not going to hang these guys because that's a nasty circle at night, especially when you're tired. Being that you've never done it before, and don't know how hard EWR is to see at night, maybe you don't really know how easy it is to get lost on that circle. There were probably tons of things that lead up to the situation they were in, but rest assured, this was BAD. Like if the report of somebody in general topics who saw it (and saw them climbing up from BELOW the bridge), or the radar return that said they were at or below 400' at 2.5 miles, then this one was CLOSE.
That being said, it could be me that makes that mistake on my next leg. So instead of talking about how everybody needs to be fired, I'd like to know how we can learn from what they did wrong so that none of us end up in the same situation, because I can very easily see how these guys got into this situation.
Hugz isn't aware that Newark doesn't have any taxiway lights, and directional only runway lights? Maybe if he knew that you can't see 29 from until your nearly inside of 5deg from centerline? Or that the papi is on the right side of the runway (non standard side), and angled so that it can only be seen on final?
If you don't know that circle, it's easy to get yourself in trouble quickly, despot the fact that it relatively benign in nature. The constraints of airspace, proximity to the Hudson vfr corridor etc make it a surprisingly sporty approach.
That being said, if they made it to the docks, then they had way overshot final, an situational airport awareness would tell you that you had missed the runway at that point.
The thing that really makes it worse, CAL has a company built rnp approach that flys the circle for you. If its in their database, prudence would dictate using it as a back up.
I'd be interested to find out what happened, but this will likely stay internal.