Saabs

Will we not have the CVR because the flight went on to LHR?

450knotOffice

That would be my guess.

Edit: although I am reading now that the NTSB recommended 25 hour recording ability in 2018 due to scenarios just like this. Whether or not this recommendation was adopted, I’d have no idea. Maybe?

at6d

Couple of questions from a SWA guy.

—So on this flight if I understand it a third crew member was present? As in required or a jumpseater? Was this person up on comms? What is this persons role during taxi? See something say something?

—Was the taxi route briefed? Verbalized?

—Did the captain verbalize something along the lines of “clear to cross 31L?” (Wrong runway?)

—Would the FO be conducting a prepare for takeoff PA during a runway crossing?

—Is the FO new? Unfamiliar? Been to JFK before?

Im close to upgrade and this stuff is what bothers me the most. The flying isn’t supposed to be an issue at this level—it’s turning the damn wrong way on the ground!

Im very glad the controller caught it—even though wouldnt someone have seen a 777 holding short of the wrong crossing runway?

To make a point—1000 feet separation is five runway edge lights, and a 737 is at takeoff thrust and 80 knots before you leave the touchdown zone markers.

Im not sure what to think about departing after that one. Obviously the media blew up by the time they got to LHR.

madmax757

[QUOTE=at6d;3572989]Couple of questions from a SWA guy.

And most importantly. Were they taxiing at 50 knots like we do at SWA ?

OpieTaylor

10000% this.

biigD

The third crewmember was required and should be just as involved in what's going on as the other two. It should have all been briefed, and nothing should have been happening as they were crossing the runway. Of course I'm using the word 'should' in each case, but I'm giving them the benefit of the doubt. The crew was JFK based, but that doesn't necessarily mean they're all familiar. That said, I find it very unlikely that all three were new to operating at JFK.

Of course I don't know, but this feels like expectation bias. I'll bet they did exactly what they briefed.

Sunvox

Sorry to hear that's a "thing" at AA. Not saying things like that never happen at United, and CERTAINLY not implying it was at issue in this instance, but that's the whole point of the years and years of training we've been getting in this industry regarding Cockpit Leadership or Cockpit Resource Management or whatever it's called at different companies. Hopefully by now most captains at the majors understand that being overbearing can cause EXACTLY this type of mistake. Far better to have a crew working as a team than a crew worried about p1ss1ng off or even worse afraid of the captain.

highfarfast

I've kinda wondered the same thing here but I'm not JFK familiar.

ImSoSuss

I imagine AA is a very different pilot group than United and even Delta. It is the most senior pilot group and also the most fractured from the fact that there have been so many mergers in the recent past. It makes it very frustrating for everybody "below the line" who has to deal with the politics of what happened before we got here.

AllYourBaseAreB

It’s not necessarily overbearing but with the very recent manual change (1/3/2023), it could literally be the FO’s 1st PA in over 20 years. A lot of CA’s are probably just trying to be helpful, since this was a rollout of changes, with zero training