This is what you’re worried about on a Saturday night?

 

And boom goes the dynamite. Al for the win.

 

I find the AA way of pulling new t/o numbers to be fairly tedious personally, and have also seen Capts backtaxi for an extra 200' of takeoff roll on a 10,000' runway in a small narrowbody rather than using the X intersection numbers that had no change.

Also the way AA does their intersection notation is whacky.

 

Agreed. It's way more complicated than it needs to be. But we've always done it that way. #facepalm

 

You must really have a pitiful life.

 

English please? The first sentence still has my wondering what you are trying to say. Edit and delete it.

 

“Has my wondering”? English please? I have no idea what you’re trying to convey with that. Edit and delete please.

 

This comes across as an accusation instead of a question. Is there a specific airport that you have run into AA aircraft causing you a problem?

To be legal we have to have the data(as I imagine you do unless the FAA let you have pretty some loose performance procedures.) As the above poster said, sometimes it's easy, sometimes it's not. Sometimes it's quick, sometimes it's not. But, at least on the A320, we set our data before start. We can and often do get and set new numbers, but that opens the door for errors as it's not as easy to cross check while taxiing. A new TPS could have a different flap setting for something as simple as a 200' intersection. Is it worth it at the last minute instead of a quick back taxi? Maybe, maybe not, but again...what has caused you an issue?

Now, what I really want to know is why do UA guys always ask for ride reports every time they check on a new freq.?

 

All this legality talk is utter nonsense. Just get this guy airborne 39 seconds earlier!

 

I would have just ignored the thread entirely but it's too fun to make fun of this guy for totd.