777 strikes approach lights on departure 9/15

I get that, thank you for sharing.

This is more for @MikeD with this philosophy, it would be appropriate to then have the runway verification a checklist item?

I think what you're missing is that it's more about uploaded takeoff performance data and being during you have the appropriate RNAV fixes to avoid a loss of separation.

"Tacos. See, my math works." :)
 
I'd prefer an "Expect Runway (whatever)" on the PDC like some airports have.

Beech 1900, you can send me virtually anywhere. But you start tinkering with a highly automated airplane at the last minute a lot of those "holes in the Swiss cheese" start lining up pretty quick.
 
I think what you're missing is that it's more about uploaded takeoff performance data and being during you have the appropriate RNAV fixes to avoid a loss of separation.

"Tacos. See, my math works." :)

I get that.

But with the thought processes in the other thread by @MikeD I wouldn't think he would expect those to be checklist necessary.
 
I'd prefer an "Expect Runway (whatever)" on the PDC like some airports have.

Beech 1900, you can send me virtually anywhere. But you start tinkering with a highly automated airplane at the last minute a lot of those "holes in the Swiss cheese" start lining up pretty quick.
Canada is great that way.

Code:
USE SID BANFF1* DEPARTURE RUNWAY 35L
 
If you don't have the balls to stand up to a Qatari Sheik and say "no, that's not safe", you have no business in a cockpit.
This isn't a union making a Just Satety culture issue.

That sounds good, and I, personally, agree with you wholeheartedly. However, it's a whole different thing for many, many folks when they know their employment and livelihood is on the line. Doing the right thing is always easy when there are no exigent circumstances and no skin in the game. Slaves, whether wage slaves or actual slaves, rarely have the capacity to stand up for what's right... that's a big part of what makes them slaves, hmm? (If everyone always did the right thing the world would be a much better place, and if a frog had wings it wouldn't bump it's ass a-hoppin'.) I'm not defending that weakness, only stating that the weakness exists ... broadly. Worst of all, in a world of increasing wealth and power disparity, that weakness is increasingly being accepted as normal.
 
I was going to split the grudge match from the topic and put it in the other thread, but I'm lazy today.

I can't play hall monitor all damned vacation.
That's the trouble with gardening... too damned much weeding!
 
@Crop Duster Id retort, as pilots, employed overseas, we are not slaves. Ideological or literal.
Now the FA's and other logistical support TCN's, yes they are slaves to the big airlines.

Standing up for the right things, isn't always the easiest choice.
If you'd rather stay at $150,000 per annum job in Doha, and continue to risk the lives of those behind you, so you can keep your lifestyle, I'd question your integrity.

Edited to add: Doha isn't Dakar.
 
Last edited:
Is that really to much to ask! Seriously.

I've been at the top of the alley in DTW about to hear out to somewhere like MSP which would generally be the west complex, then ground gives us a runway change and a complex, non-standard taxi instruction to 21R including intersections, taxiing on runways, crossing a runway with a "pass behind A", "B will wait" your "sequence is behind C", "Contact ground at D" and you can just smell your copilots brain sizzle.

So now you have to both confirm you've heard the right thing, someone's head's in the FMS, sending for new performance data and re-inserting runways.

I'm "that guy" taxiing slowly or asking for somewhere to pull off and get caught up that you've complained about.
 
I've been at the top of the alley in DTW about to hear out to somewhere like MSP which would generally be the west complex, then ground gives us a runway change and a complex, non-standard taxi instruction to 21R including intersections, taxiing on runways, crossing a runway with a "pass behind A", "B will wait" your "sequence is behind C", "Contact ground at D" and you can just smell your copilots brain sizzle.

So now you have to both confirm you've heard the right thing, someone's head's in the FMS, sending for new performance data and re-inserting runways.

I'm "that guy" taxiing slowly or asking for somewhere to pull off and get caught up that you've complained about.
Thank you for relieving the guy who is doing the mad typing on the right side from having to be "that guy."

Signed,

that guy.
 
Thank you for relieving the guy who is doing the mad typing on the right side from having to be "that guy."

Signed,

that guy.

Not a problem.

Almost 100% of the things we talked about during "In Command" that were facepalm-worthy or involved needless aircraft damage involved one of the crewmembers being rushed, low situational awareness, or discounting the other crewmembers concern about something seemingly inconsequential which actually turned out to be a huge issue.
 
Runway changes have become a bigger deal than they once were because of the proliferation of runway dependent RNAV SIDs and arrivals. Mess them up and it really screws up your day. @Seggy it is my opinion that the checklist for runway change items was driven by their expanded use.

My spidey sense tingles when I get a runway change as for me personally, that has been the number one driver for my ASAP reports.

Never anything huge or scary, but to me any runway change raises the TEM flag, so I slow down and double check everything.
 
I'd prefer an "Expect Runway (whatever)" on the PDC like some airports have.

Beech 1900, you can send me virtually anywhere. But you start tinkering with a highly automated airplane at the last minute a lot of those "holes in the Swiss cheese" start lining up pretty quick.
Anchorage is good about that. They say the runway when checking in with a approach, and it is on the ATIS too.
 
Not a problem.

Almost 100% of the things we talked about during "In Command" that were facepalm-worthy or involved needless aircraft damage involved one of the crewmembers being rushed, low situational awareness, or discounting the other crewmembers concern about something seemingly inconsequential which actually turned out to be a huge issue.
My Dad is fond of saying that the only time that anyone has ever been hurt in an airplane or damaged one was because they were any combination of:
(1) tired
(2) in a hurry
(3) distracted/thrown a change.

Which sounds like a lot of "In Command" distilled down to an easily-digestible chunk.
 
Anchorage is good about that. They say the runway when checking in with a approach, and it is on the ATIS too.

Wait until you go to SLC.

Join the localizer for 17

Do you have the airport in sight, cleared visual 16L

Traffic is 2 miles ahead and you have a 50 knot closure, change runways, cleared visual 16R

Wait, we need you back on 17.

Meanwhile, you're high, you're fast and he wants you to slow.


#EarlyCaptainStories.
 
I've been at the top of the alley in DTW about to hear out to somewhere like MSP which would generally be the west complex, then ground gives us a runway change and a complex, non-standard taxi instruction to 21R including intersections, taxiing on runways, crossing a runway with a "pass behind A", "B will wait" your "sequence is behind C", "Contact ground at D" and you can just smell your copilots brain sizzle.

So now you have to both confirm you've heard the right thing, someone's head's in the FMS, sending for new performance data and re-inserting runways.

I'm "that guy" taxiing slowly or asking for somewhere to pull off and get caught up that you've complained about.

I hate taxiing in DTW. One of the most asinine things I've seen in my career is being at 3N going to 21R. Call up on 121.8,"right on U, short U8, contact ground on 119.45."

That's like 50 yards of taxi requiring it's own frequency.

I also love that most captains find 9L approaching M the best time to have me fire up the other engine. "If you don't mind, I'd like to wait until we are on M."
 
My Dad is fond of saying that the only time that anyone has ever been hurt in an airplane or damaged one was because they were any combination of:
(1) tired
(2) in a hurry
(3) distracted/thrown a change.

Which sounds like a lot of "In Command" distilled down to an easily-digestible chunk.

Pretty much it.

I'm sure lots of controllers think I'm an ass for not sticking my neck out and ample use of "unable", but that's alright.
 
Wait until you go to SLC.

Join the localizer for 17

Do you have the airport in sight, cleared visual 16L

Traffic is 2 miles ahead and you have a 50 knot closure, change runways, cleared visual 16R

Wait, we need you back on 17.

Meanwhile, you're high, you're fast and he wants you to slow.


#EarlyCaptainStories.
Thats crazy. It is nice having one runway for departures, and one for arrivals.
 
Back
Top