Quote:
Originally Posted by amead
Any rust? Finally a bit of good news lol.
Surprisingly little, and none at all in the mechanics of flying. I had a very good landing at SFO and the flight was great, smooth most of the way except for some weather we had to dodge in the Cheyenne, WY area.
I was concerned about the procedures being rusty (e.g. preflighting the cockpit, loading the FMS) but that really wasn’t a problem either. In my crew brief before the flight, I told Sean (the FO) that the biggest threat for our flight was the very little actual flying we had both done in the previous three months. Sean had one other trip about two weeks ago and he also just completed his recurrent sim training in Atlanta, so he was actually pretty current.
I told Sean that we’d slow down the whole process as much as necessary to avoid simple mistakes or omissions. I encouraged him to speak up if there was anything he didn’t like. The beauty of the procedures, coupled with checklists, is that there are several opportunities to catch minor lapses before they become errors. This is one place the crew concept really pays off. It’s not a mistake unless we both make it.
The only thing I forgot was to log on to CPDLC for our route clearance. This became immediately obvious when I got to the point of doing my briefing for the flight. It’s at this point that we discuss how we’ve been cleared, what altitude, etc. Since I had no clearance, I realized I had forgotten to log on so I just did it then, the clearance came through, and we proceeded.
We did get two curveballs thrown at us. As we were pushing back, company Operations called and instructed us to pull back in to the gate for three connecting passengers who had been delayed because at least one was in a wheelchair. Going back wasn’t a big deal, but now we needed new “numbers”, the weight and balance data, required for takeoff performance. This necessitated coordination with our dispatcher and getting the numbers via ACARS, and rebriefing our takeoff parameters (V speeds, flap settings, engine derated power required).
The second curveball is that Ground Control changed our departure runway which meant we needed to again obtain new performance data for the new runway, and we also needed to brief the changes in the departure caused by this change. At this point, it was starting to feel like a sim ride, where the instructor throws these little things at you to make sure you follow procedures for these changes.
The checklists prove their worth in these situations and from that point the flight was without incident. On the return flight, we were on final to runway 22L at JFK at about 8:50 pm. Fireworks were going off all over Long Island. It was a pretty great view.
btw, we had 48 passengers to SFO and 52 on the way back. This particular 757 holds 168.