Any "Latest & Greatest" about Endeavor?
Gets Weekends Off
Joined: Nov 2012
Posts: 997
Likes: 0
From: CaptFo
[QUOTE=Woger Wabbit;2409894]
If it goes as far as a collision, yes, obviously. But there's a couple more BIG safe guards that have to fail before that happens. One, ATC has to miss it (in all cases the error was trapped here). 2, both crews would have to disregard their TCAS RAs before an actual midair went down.
I'm not advocating it's okay by any means, just simply implying that it's the lesser of the three scenarios IMO.
And no need for caps and exclamation points. My hearing is still good.
lol the Caps is for your eyes 👀 not your 👂's. In my humble opinion which probably means absolutely nothing, turning the wrong way on a RNAV departure is just as bad as the other scenarios. Just as dangerous. The fact that ATL revoked RNAV departures for EDV for a couple weeks is simply unacceptable.
If it goes as far as a collision, yes, obviously. But there's a couple more BIG safe guards that have to fail before that happens. One, ATC has to miss it (in all cases the error was trapped here). 2, both crews would have to disregard their TCAS RAs before an actual midair went down.
I'm not advocating it's okay by any means, just simply implying that it's the lesser of the three scenarios IMO.
And no need for caps and exclamation points. My hearing is still good.

Line Holder
Joined: Apr 2017
Posts: 28
Likes: 0
[QUOTE=CBreezy;2409934]
Air Canada nearly landed on a taxiway with multiple aircraft on it. Yes, that’s very disturbing. But what’s that have to do with RNAV departures out of ATL?
[QUOTE=Yumyum;2409936]
lol the Caps is for your eyes 👀 not your 👂's. In my humble opinion which probably means absolutely nothing, turning the wrong way on a RNAV departure is just as bad as the other scenarios. Just as dangerous. The fact that ATL revoked RNAV departures for EDV for a couple weeks is simply unacceptable.
Ahh, for my eyes. Thanks for your consideration. Was picturing you screaming those last couple words.
Getting revoked is certainly nothing to be proud of, but I find this all kind of interesting. When we started flying RNAVs out of DFW, this was a hot topic back then because crews were making very similar mistakes, and I don't recall them revoking our privileges.
Anyway, my productivity break is wrapping up. Play nice y'all.
[QUOTE=Yumyum;2409936]
lol the Caps is for your eyes 👀 not your 👂's. In my humble opinion which probably means absolutely nothing, turning the wrong way on a RNAV departure is just as bad as the other scenarios. Just as dangerous. The fact that ATL revoked RNAV departures for EDV for a couple weeks is simply unacceptable.
Getting revoked is certainly nothing to be proud of, but I find this all kind of interesting. When we started flying RNAVs out of DFW, this was a hot topic back then because crews were making very similar mistakes, and I don't recall them revoking our privileges.
Anyway, my productivity break is wrapping up. Play nice y'all.
Gets Weekends Off
Joined: Jul 2013
Posts: 12,525
Likes: 1,121
Woger, you said if it had gone to a collision, it would have been disturbing. In making that point, you appear to say that it's only disturbing if it does get to that point. Just because you don't hit someone or trigger an RA, blatantly disregarding a clearance at one of the busiest airspaces in the world is troubling and disturbing. It doesn't have to just lead to a collision.
On Reserve
Joined: Apr 2014
Posts: 122
Likes: 0
Disturbing? I'd call it a little embarrassing maybe. If those were the only mistakes we were making I'd say we're not doing too bad. Disturbing is getting the shaker multiple times at 390 cuz u went to flight idle to slow and left it there. Disturbing is operating a flight without weather radar activated and going through whatever-T-F that flight in the latest FOU went thru. Pray I'm not on any of those flights
How embarrassed will you be when the FAA suspends your license to give you time to think about it? Will that be not too bad as well?
Somebody here added something like "TCAS will keep you out of trouble if you mess up anyway". Come on people. Work on a better reputation for a change.
Pro tip: There's a page in your ATL jepps, 10-3-1 (AAUP pg. 2 of 2), that tells you the runway the departure will USUALLY use. Take advantage of it.
Verify the runway and legs as a crew; it should only take about 10 seconds but there's -always- sufficient time to get it done no matter what's going on. None of you should be advancing any throttles for takeoff until you do. Consider A/P use and actually observing sterile cockpit.
Gets Weekends Off
Joined: Apr 2016
Posts: 505
Likes: 0
I don't get why people are making a big deal out of this. Clearance verification is what we are supposed to do. The pilot who didn't program the FMS is also supposed to verify the legs pages with the legs on the paper flight plan. If that is not being done then those crews only have themselves to blame.
You should never accept a clearance that you aren't ready to take. I have been sat #1 short of 13 in LGA and my DP has been changed along with a line up and wait clearance twice in one day. Both times that happened to me I had no problem telling the controller "unable lineup we need to verify the new departure and reprogram the FMS, it should take us less than 5 minutes." Never got pulled out of sequence. Never got *****ed at. It took a grand total of 90 seconds to enter the new DP and brief it each time.
If you are blocked out and getting paid then who cares if ATC pulls you out of sequence. My favorite phrase when ATC decided to change the departure/arrival runway, SID, or STAR at the last second is "unable, we need to get new numbers."
The fact that these crews DID NOT DO THEIR JOB is infuriating. Don't ever let ATC bully you into doing something you don't want to do. This topic really needs to come to a close.
You should never accept a clearance that you aren't ready to take. I have been sat #1 short of 13 in LGA and my DP has been changed along with a line up and wait clearance twice in one day. Both times that happened to me I had no problem telling the controller "unable lineup we need to verify the new departure and reprogram the FMS, it should take us less than 5 minutes." Never got pulled out of sequence. Never got *****ed at. It took a grand total of 90 seconds to enter the new DP and brief it each time.
If you are blocked out and getting paid then who cares if ATC pulls you out of sequence. My favorite phrase when ATC decided to change the departure/arrival runway, SID, or STAR at the last second is "unable, we need to get new numbers."
The fact that these crews DID NOT DO THEIR JOB is infuriating. Don't ever let ATC bully you into doing something you don't want to do. This topic really needs to come to a close.
The commute is either by car or train... Better bet would be to apply to Piedmont and be based where you live.
Thread
Thread Starter
Forum
Replies
Last Post



