Real Answers from Real Pilots

June ‘19 Schedule

64 Hours, 82 Credits, 16 Days Off

  1. LAX-PAE
  2. PAE-SAN-PAE
  3. SEA-YEG-SEA
  4. SEA-ICT-SEA-FCA
  5. FCA-SEA-YEG-SEA-BZN
  6. Layover in BZN
  7. BZN-SEA
  8. SEA-GPI-SEA-BIL
  9. BIL-PDX-ONT-PDX-GEG
  10. Layover in GEG
  11. GEG-PDX-OAK-PDX, DH to SEA
  12. SEA-YEG-SEA-YYC
  13. YYC-SEA-STS-SEA-SMF
  14. Layover in SMF
  15. SMF-SAN-SMF-SEA

Looks like a pretty easy going month Tory! Thanks for sharing! Any excitement happen in June?

What do you mean when you say “82 credits”?

Nick,

Means I was paid 82 hours worth of my hourly rate.

Tory

Michael,

June was the month for go-arounds. This may sound hard to believe, but that was my first go-around in part 121 ops. I’ve been flying for over two years now. You’d think I would have done one or two already.

This one in particular was extra interesting. It was night VMC. FO was flying. We were picking up the backcourse localizer. The FO looked at me and said, “Uh…Help me out here.” At that point, I didn’t even bother trying to explain what was going on or what we should do. We were below 2000 feet and descending. I just took the controls and executed an early missed approach.

You may be thinking, “You went missed on an ILS during night VMC? Couldn’t you see the runway?” And I wouldn’t fault you for that. The thing is that our company policy requires us to track an approach to the runway of intended landing at night, no matter what. I’m told that this policy was added to our FOM because years ago a flight flew dangerously close to the ground on a night visual approach in VMC.

The common argument I hear most from pilots about this policy is, “So, it’s safer to go missed in a jet than it is to land at night?” I understand the argument, but I’m not here to go against the grain. If I don’t agree with something, I’ll take it up with the manager of flight ops while I’m safely on the ground. I’m not going to go rogue, in flight, but this is all beside the point. We went missed, at night, and there was a transfer of controls before that happened, and it was the first one that I had ever done outside of the sim. We switched the approach to an RNAV and carried on as normal.

I went around one more time in June, but that one wasn’t as interesting as the first.

Tory

2 Likes

So let me get this straight. Your FO was set up on the back course and was aligned for the opposite runway? Was this ILS vectored or from a fix? If ATC cleared you for the approach to land wouldn’t being on the backside be considered a deviation if you did land?

If that’s the case I would think a go-around would be the right thing to do. When in doubt just climb like a madman and set-up a different approach. I might be mistaken about the deviation part. As PIC its safety first regardless of what ops has to say about it. You were in the right from the way I see it.

We suspect that the tower forgot to activate the correct side of the ILS.

What’s a backcourse localizer? Sounds scary! :wink:

Adam

1 Like

Maybe they forgot to turn the damn thing on altogether?! We honestly don’t know. All we know is when we asked them about it after we had gone missed, they said, “Try it now.”